From 427fdce0919769ab54284acb7d2dadc5d911d54c Mon Sep 17 00:00:00 2001 From: Yaroslav Halchenko Date: Mon, 7 Oct 2024 12:50:29 -0400 Subject: [PATCH 1/2] Include entity-less "scans.json" into an example of inheritance principle Clarifies #789 --- src/common-principles.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/src/common-principles.md b/src/common-principles.md index 0a42e4a885..716dbd8c6d 100644 --- a/src/common-principles.md +++ b/src/common-principles.md @@ -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": "" } ) }} @@ -773,6 +775,8 @@ 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)