[\<\< Back to Data Package Home](Dummy-Data-Package)
[\<\< Go Back](Dummy-Data-Package)
---
[[_TOC_]]
This is an Wiki page documenting dummy data and metadata. We want to demonstrate what information is important to include next to a data index. There are many variations possible to a Filenaming Convention. The recommendation is to follow standards available in the field or to adapt them if needed, preferrably after discussing it with colleagues. We provide general guidelines in our CRS Primer on [File Naming conventions](https://zenodo.org/records/10091967). A example of a domain-specific standard is [Brain Imaging Data Structure - BIDS](https://bids-standard.github.io/bids-starter-kit/folders_and_files/files.html)
Here a description of file names fields ...
[[_TOC_]]
## Filenaming convention
### Reconstructed images
The following scheme was inferred from the filenames of the image-files starting with "JP\*". The metadata table was created accordingly. Future versions should specify the remaining files or create a separate table for the other type of files available.
_\<field\>_ indicates this is a required field; _\<(field)\>_ fields in brackets are optional and may not appear in every file name; _str_ refers to strings; _num_ to numeric values.
_\<value\>_ indicates this is a required _value_; _\<(value)\>_ _value_ in brackets are optional and may not appear in every file name; _str_ refers to strings; _num_ to numeric values.
#### Convention
`<specID>-<status>-<number of scans>-<(desc)>_<rec><.ext>`
`DS<DummySubjectID>_stat<status>_<number of scans>-<(desc)>_slc<slice><.ext>`
#### Label description
`specID`: _str + num_, specimen ID (e.g., JP01)
`DummySubjectID`: _num_ (e.g., DS01)
`status`: _str_, specimen status (dead | invivo | dying)
`status`: _str_, specimen status (A | B | C)
`scanID`: _num + str_, scan number (e.g., 1scan or scan1)
