Metadata tables

The following sections describes the variables used in the different metadata tables. All tables should be machine-readable. Having key variables consistently named across tables make it possible to automatically bring them together

Data origin descriptors

Describe origin of the data, where, when and by whom they were collected and whether the data package is complete. They should be in all tables: mice information and scan lists

Column name Description
University University affiliation of the group who collected the data (e.g., UZH; see glossary)
Research_group Abbreviation describing the group who collected the data (e.g., TIG; see glossary)
Year Year of data curation
Data_type Abbreviation describing the type of data collected (e.g., SRµCT; see glossary)
Dataproject_ID (optional) Identifier of the project from which the data package derives, e.g., In Vivo CSF
Facility_proposal_ID (optional) Number of the proposal for facility usage e.g., the beamline numbers
Facility_Institution Name or acronym of the institution hosting the main facility (it can be the same as University)
Facility_1 Name or acronym of the main facility (e.g., CLS, SPring-8,etc)
Facility_2 (optional) Additional facility information (e.g., beamline)
Facility_Country Country where the facility is located
Start_date_acquisition DD/MM/YYYY
Status Indicate if ‘complete’ or ‘in progress’
Status_comment (optional) additional comments on the status of these data

Data Storage

These columns are applicable to tables describing where the data are located

Column name Description
Files_type (If applicable) more detailed description of the files depending on the data type. E.g., if data_type is synchrotron: projections, reconstructions or both.
Data_size The total volume of the data stored
File_subjectIDs List which samples (mice) were in this location be precise e.g., CA001-CA030 should be used only if there are really 30 subjects with IDs 001 to 030
Source_server_path Full path to the data (provide the IP-internet protocol server address, e.g.,‘\\123.45.679.01\data\synchrotron\brains’ and not the arbitrary letter used to map the network drive, like ‘O:\data\synchrotron\brains’)
Source_server_type Specify if the path refers to a: disk, tape, server, online repository
Source_server_access Public or private, specify any special access rules
Disk_<research_group>_status Copied if there is a copy at the facilities of this group
Disk_<research_group>_ID Unique identifier of the harddisk, e.g., serial number and model
Disk_<research_group>_speed Copy speed of this disk
Disk_<research_group>_time Track how long did it take to copy the data
Back to top