[ENH] BEP001 - New entity: flip

src/99-appendices/09-entities.md

@@ -17,15 +17,15 @@ each is given in the [Entity Table](04-entity-table.md).
 
 Full name: Subject
 
-Format: `sub-<label>`
+Format: `subject-<label>`
 
 Definition: A person or animal participating in the study.
 
 ## ses
 
 Full name: Session
 
-Format: `ses-<label>`
+Format: `session-<label>`
 
 Definition: A logical grouping of neuroimaging and behavioral data consistent across
 subjects.
@@ -40,7 +40,8 @@ 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 (for example, training).
+often in the case of some intervention between sessions
+(for example, training).
 
 ## task
 
@@ -57,7 +58,7 @@ Those labels MUST be consistent across subjects and sessions.
 
 Full name: Acquisition
 
-Format: `acq-<label>`
+Format: `acquisition-<label>`
 
 Definition: The `acq-<label>` key/value pair corresponds to a custom label the
 user MAY use to distinguish a different set of parameters used for
@@ -69,17 +70,18 @@ In such case two files could have the following names:
 `sub-01_acq-highres_T1w.nii.gz` and `sub-01_acq-lowres_T1w.nii.gz`, however
 the user is free to choose any other label than highres and lowres as long
 as they are consistent across subjects and sessions.
-In case different sequences are used to record the same modality (for example, RARE
-and FLASH for T1w) this field can also be used to make that distinction.
-At what level of detail to make the distinction (for example, just between RARE and
-FLASH, or between RARE, FLASH, and FLASHsubsampled) remains at the
-discretion of the researcher.
+In case different sequences are used to record the same modality
+(for example, RARE and FLASH for T1w)
+this field can also be used to make that distinction.
+At what level of detail to make the distinction (for example,
+just between RARE and FLASH, or between RARE, FLASH, and FLASHsubsampled)
+remains at the discretion of the researcher.
 
 ## ce
 
 Full name: Contrast Enhancing Agent
 
-Format: `ce-<label>`
+Format: `ceagent-<label>`
 
 Definition: The `ce-<label>` key/value can be used to distinguish
 sequences using different contrast enhanced images.
@@ -91,7 +93,7 @@ with the same label.
 
 Full name: Reconstruction
 
-Format: `rec-<label>`
+Format: `reconstruction-<label>`
 
 Definition: The `rec-<label>` key/value can be used to distinguish
 different reconstruction algorithms (for example ones using motion
@@ -101,10 +103,11 @@ correction).
 
 Full name: Phase-Encoding Direction
 
-Format: `dir-<label>`
+Format: `direction-<label>`
 
 Definition: The `dir-<label>` key/value can be set to an arbitrary alphanumeric label
-(for example, `dir-LR` or `dir-AP`) to distinguish different phase-encoding directions.
+(for example, `dir-LR` or `dir-AP`) to distinguish different phase-encoding
+directions.
 
 ## run
 
@@ -121,7 +124,7 @@ When there is only one scan of a given type the run key MAY be omitted.
 
 Full name: Corresponding Modality
 
-Format: `mod-<label>`
+Format: `modality-<label>`
 
 Definition: The `mod-<label>` key/value pair corresponds to modality label for defacing
 masks, for example, T1w, inplaneT1, referenced by a defacemask image.
@@ -133,13 +136,26 @@ Full name: Echo
 
 Format: `echo-<index>`
 
-Definition: Multi-echo data MUST be split into one file per echo.
-Each file shares the same name with the exception of the `_echo-<index>`
-key/value.
+Definition: If constituents of an entity-linked file collection differ as a
+function of `EchoTime` acquisition parameter, the `_echo-<index>` key/value
+pair MUST be used to distinguish individual files.
 Please note that the `<index>` denotes the number/index (in the form of a
 nonnegative integer) of the echo not the echo time value which needs to be
 stored in the field `EchoTime` of the separate JSON file.
 
+## flip
+
+Full name: Flip Angle
+
+Format: `flip-<index>`
+
+Definition: If constituents of an entity-linked file collection differ as a function of
+`FlipAngle` acquisition parameter, the `_flip-<index>` key/value pair MUST
+be used to distinguish individual files.
+Please note that the `<index>` denotes the number/index (in the form of a
+nonnegative integer), not the `FlipAngle` value which needs to be stored in
+the field `FlipAngle` of the separate JSON file.
+
 ## recording
 
 Full name: Recording
@@ -155,14 +171,15 @@ For example: `_recording-contrast`, `_recording-saturation`.
 
 Full name: Processed (on device)
 
-Format: `proc-<label>`
+Format: `processing-<label>`
 
 Definition: The proc label is analogous to rec for MR and denotes a variant of a file
 that was a result of particular processing performed on the device.
 This is useful for files produced in particular by Elekta’s MaxFilter
-(for example, sss, tsss, trans, quat or mc), which some installations impose to
-be run on raw data because of active shielding software corrections before
-the MEG data can actually be exploited.
+(for example, sss, tsss, trans, quat or mc),
+which some installations impose to be run on raw data because of active
+shielding software corrections before the MEG data can actually be
+exploited.
 
 ## space
 
@@ -190,4 +207,4 @@ Instead of a simple renaming, files should be read in and saved under their
 new names with dedicated tools like MNE, which will ensure that not only
 the file names, but also the internal file pointers will be updated.
 It is RECOMMENDED that .fif files with multiple parts use the
-`split-<index>` entity to indicate each part.
+`split-<index>` entity to indicate each part.

src/schema/entities.yaml

@@ -117,8 +117,8 @@ flip:
     `FlipAngle` acquisition parameter, the `_flip-<index>` key/value pair MUST
     be used to distinguish individual files.
     Please note that the `<index>` denotes the number/index (in the form of a
-    nonnegative integer), not the `FlipAngle` value which needs to be stored in 
-    the field `FlipAngle` of the separate JSON file. 
+    nonnegative integer), not the `FlipAngle` value which needs to be stored in
+    the field `FlipAngle` of the separate JSON file.
   format: index  
 recording:
   name: Recording