From 9b03fc4e695232aad2eb64a1b80b137532d05d54 Mon Sep 17 00:00:00 2001 From: Taylor Salo Date: Wed, 16 Sep 2020 13:05:20 -0400 Subject: [PATCH 01/16] Initial reorganization. entities.yaml specifies order, while actual definitions get their own files. --- src/schema/entities.yaml | 152 ++++---------------------------- src/schema/items/acq.yaml | 20 +++++ src/schema/items/ce.yaml | 10 +++ src/schema/items/dir.yaml | 7 ++ src/schema/items/echo.yaml | 11 +++ src/schema/items/mod.yaml | 8 ++ src/schema/items/proc.yaml | 11 +++ src/schema/items/rec.yaml | 8 ++ src/schema/items/recording.yaml | 9 ++ src/schema/items/run.yaml | 9 ++ src/schema/items/ses.yaml | 19 ++++ src/schema/items/space.yaml | 8 ++ src/schema/items/split.yaml | 16 ++++ src/schema/items/sub.yaml | 6 ++ src/schema/items/task.yaml | 9 ++ 15 files changed, 166 insertions(+), 137 deletions(-) create mode 100644 src/schema/items/acq.yaml create mode 100644 src/schema/items/ce.yaml create mode 100644 src/schema/items/dir.yaml create mode 100644 src/schema/items/echo.yaml create mode 100644 src/schema/items/mod.yaml create mode 100644 src/schema/items/proc.yaml create mode 100644 src/schema/items/rec.yaml create mode 100644 src/schema/items/recording.yaml create mode 100644 src/schema/items/run.yaml create mode 100644 src/schema/items/ses.yaml create mode 100644 src/schema/items/space.yaml create mode 100644 src/schema/items/split.yaml create mode 100644 src/schema/items/sub.yaml create mode 100644 src/schema/items/task.yaml diff --git a/src/schema/entities.yaml b/src/schema/entities.yaml index f1b6d1c6c1..1d9cc40354 100644 --- a/src/schema/entities.yaml +++ b/src/schema/entities.yaml @@ -1,138 +1,16 @@ --- -sub: - name: Subject - description: | - A person or animal participating in the study. - format: label -ses: - name: Session - description: | - A logical grouping of neuroimaging and behavioral data consistent across - subjects. - Session can (but doesn't have to) be synonymous to a visit in a - longitudinal study. - In general, subjects will stay in the scanner during one session. - However, for example, if a subject has to leave the scanner room and then - be re-positioned on the scanner bed, the set of MRI acquisitions will still - be considered as a session and match sessions acquired in other subjects. - Similarly, in situations where different data types are obtained over - several visits (for example fMRI on one day followed by DWI the day after) - those can be grouped in one session. - Defining multiple sessions is appropriate when several identical or similar - data acquisitions are planned and performed on all -or most- subjects, - often in the case of some intervention between sessions (e.g., training). - format: label -task: - name: Task - format: label - description: | - Each task has a unique label that MUST only consist of letters and/or - numbers (other characters, including spaces and underscores, are not - allowed). - Those labels MUST be consistent across subjects and sessions. -acq: - name: Acquisition - description: | - The `acq-