Description of tables in BOOKKEEPING schema in the e-Ecology database
The FILES table describes the status of all data-files which have been or need to be processed. This information is used by the bookkeeping service on the e-Ecology website.
|unique file id
|unique file name
|Type of file ie MPR, ECMWF,
|Size of file in bytes
|Status of file ie new, processed, archived
|Time associated with filename as timestamp.
|Timestamp when file was first registered
|Timestamp of last status change
e-Ecology Grid-Store Catalog
The following three tables are used to implement the e-Ecology Grid-Store catalog. If files are being archived or copied the Grid-Storage, this is administratred in the following tables.
For Grid-Storage it is preferable to have a limited number of big files instead of many small files. Therefore files are first collected into bigger archives, which are then stored as archive to the Grid-Storage. This is also maintained in the tables below.
Every file to be stored gets an entry in the FILE_CATALOG table.
|ID for file
|Type of file (MPR, tar, etc)
|Original path of file on Flysafe server
Files can be collected together in archive (usually tar files). These archive files are also registered as files in the FILE_CATALOG table. The ARCHIVE_FILE table contains the information about which files are in what archive file.
|Id of archive file in FILE_CATALOG table
|Id of file in archive in FILE_CATALOG table
|Path of file in archive
The FILE_REPLICA table contains the actual storage location of the stored files. It is possible to have more replicas of the same file.
|References in file_catalog
|replicanumber, ie 1 for first replica, 2 for second etc
|SURL is the storage location.
|timestamp with time of storage
|adler32 checksum of file
The SRMREQUEST table is used when it is requested to have a file or group of files restored from SRM. In this table the status of the request is maintained so that it can be shown on a website. It is also possible to check all requests for a specific user.
|Name of user who requested the restore
|Status of the request
|Timestamp when request was started
|Timestamp when request was changed