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

Include entity-less "scans.json" into an example of inheritance principle #1945

Merged
merged 2 commits into from
Oct 25, 2024
Merged
Changes from all commits
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
8 changes: 7 additions & 1 deletion src/common-principles.md
Original file line number Diff line number Diff line change
Expand Up @@ -739,9 +739,11 @@ A guide for using macros can be found at
"sub-01_task-rest_acq-default_bold.nii.gz": "",
"sub-01_task-rest_acq-longtr_bold.nii.gz": "",
"sub-01_task-rest_acq-longtr_bold.json": "",
}
},
"sub-01_scans.tsv": "",
},
"task-rest_bold.json": "",
"scans.json": ""
}
) }}

Expand Down Expand Up @@ -773,6 +775,10 @@ the value for field "`RepetitionTime`" is therefore overridden to the value `3.0
The value for field "`EchoTime`" remains applicable to that image, and is not unset by its
absence in the metadata file at the lower level (rule 5.b; corollary 3).

A single `scans.json`, without any entity in the filename at the top level,
is applicable to describe columns of the `sub-01_scans.tsv`
and any other `_scans.tsv` potentially present in the dataset for other subjects.

Example 2: Impermissible use of multiple metadata files at one directory level (rule 4)

<!-- This block generates a file tree.
Expand Down