Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ENH] Clarify that data files must be uniquely identified by entities/suffix #1508

Merged
merged 3 commits into from
Jun 15, 2023
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions src/common-principles.md
Original file line number Diff line number Diff line change
Expand Up @@ -196,6 +196,18 @@ as the labels would collide on a case-insensitive filesystem.
Additionally, because the suffix `eeg` is defined,
then the suffix `EEG` will not be added to future versions of the standard.

## No duplicate files under different file extensions

BIDS datasets MUST NOT contain identical data under different extensions.
effigies marked this conversation as resolved.
Show resolved Hide resolved
For example if the files

- `sub-01_ses-01_sample-A_photo.jpg` and
- `sub-01_ses-01_sample-A_photo.tif`

contain a representation of the same data,
then the dataset curator MUST decide for one of the two extensions
and delete the other file from the BIDS dataset.

## Filesystem structure & Filenames richness versus distinctness

BIDS provides a rich filesystem structure and rich filenames by using entities, but it is important to keep in mind that files also have to be readable.
Expand Down