diff --git a/dandi/cli/cmd_validate.py b/dandi/cli/cmd_validate.py
index 9e02aa62b..52325a5ec 100644
--- a/dandi/cli/cmd_validate.py
+++ b/dandi/cli/cmd_validate.py
@@ -21,14 +21,12 @@
     help="Whether to write a report under a unique path in the DANDI log directory.",
 )
 @click.argument("paths", nargs=-1, type=click.Path(exists=True, dir_okay=True))
-@devel_debug_option()
 @map_to_click_exceptions
 def validate_bids(
     paths,
     schema,
     report,
     report_path,
-    devel_debug=False,
 ):
     """Validate BIDS paths.
 
@@ -46,7 +44,6 @@ def validate_bids(
         report=report,
         report_path=report_path,
         schema_version=schema,
-        devel_debug=devel_debug,
     )
     valid = is_valid(validator_result)
     report_errors(validator_result)
diff --git a/dandi/cli/tests/test_cmd_validate.py b/dandi/cli/tests/test_cmd_validate.py
index f97b8f10f..228508e08 100644
--- a/dandi/cli/tests/test_cmd_validate.py
+++ b/dandi/cli/tests/test_cmd_validate.py
@@ -7,7 +7,7 @@ def test_validate_bids_error(bids_examples):
     from ..cmd_validate import validate_bids
 
     expected_error = (
-        "Summary: 2 filename patterns required by BIDS could not be found "
+        "Summary: 1 filename pattern required by BIDS could not be found "
         "and 1 filename did not match any pattern known to BIDS.\n"
     )
     broken_dataset = os.path.join(bids_examples, "invalid_pet001")
diff --git a/dandi/support/bids/__init__.py b/dandi/support/bids/__init__.py
deleted file mode 100644
index e69de29bb..000000000
diff --git a/dandi/support/bids/schema.py b/dandi/support/bids/schema.py
deleted file mode 100644
index 2865d00bd..000000000
--- a/dandi/support/bids/schema.py
+++ /dev/null
@@ -1,153 +0,0 @@
-"""
-THIS MODULE IS BUNDLED FROM THE bids-specification PACKAGE.
-Schema loading- and processing-related functions.
-"""
-from copy import deepcopy
-import logging
-import os
-from pathlib import Path
-
-from ruamel import yaml
-
-from . import utils
-
-lgr = utils.get_logger()
-# Basic settings for output, for now just basic
-utils.set_logger_level(lgr, os.environ.get("BIDS_SCHEMA_LOG_LEVEL", logging.INFO))
-logging.basicConfig(format="%(asctime)-15s [%(levelname)8s] %(message)s")
-
-
-def _get_entry_name(path):
-    if path.suffix == ".yaml":
-        return path.name[:-5]  # no .yaml
-    else:
-        return path.name
-
-
-def dereference_yaml(schema, struct):
-    """Recursively search a dictionary-like object for $ref keys.
-
-    Each $ref key is replaced with the contents of the referenced field in the overall
-    dictionary-like object.
-    """
-    if isinstance(struct, dict):
-        if "$ref" in struct:
-            ref_field = struct["$ref"]
-            template = schema[ref_field]
-            struct.pop("$ref")
-            # Result is template object with local overrides
-            struct = {**template, **struct}
-
-        struct = {key: dereference_yaml(schema, val) for key, val in struct.items()}
-
-    elif isinstance(struct, list):
-        struct = [dereference_yaml(schema, item) for item in struct]
-
-    return struct
-
-
-def load_schema(schema_path):
-    """Load the schema into a dictionary.
-
-    This function allows the schema, like BIDS itself, to be specified in
-    a hierarchy of directories and files.
-    File names (minus extensions) and directory names become keys
-    in the associative array (dict) of entries composed from content
-    of files and entire directories.
-
-    Parameters
-    ----------
-    schema_path : str
-        Folder containing yaml files or yaml file.
-
-    Returns
-    -------
-    dict
-        Schema in dictionary form.
-    """
-    _yaml = yaml.YAML(typ="safe", pure=True)
-
-    schema_path = Path(schema_path)
-    objects_dir = schema_path / "objects/"
-    rules_dir = schema_path / "rules/"
-
-    if not objects_dir.is_dir() or not rules_dir.is_dir():
-        raise ValueError(
-            f"Schema path or paths do not exist:\n\t{str(objects_dir)}\n\t{str(rules_dir)}"
-        )
-
-    schema = {}
-    schema["objects"] = {}
-    schema["rules"] = {}
-
-    # Load object definitions. All are present in single files.
-    for object_group_file in sorted(objects_dir.glob("*.yaml")):
-        lgr.debug(f"Loading {object_group_file.stem} objects.")
-        dict_ = _yaml.load(object_group_file.read_text())
-        schema["objects"][object_group_file.stem] = dereference_yaml(dict_, dict_)
-
-    # Grab single-file rule groups
-    for rule_group_file in sorted(rules_dir.glob("*.yaml")):
-        lgr.debug(f"Loading {rule_group_file.stem} rules.")
-        dict_ = _yaml.load(rule_group_file.read_text())
-        schema["rules"][rule_group_file.stem] = dereference_yaml(dict_, dict_)
-
-    # Load folders of rule subgroups.
-    for rule_group_file in sorted(rules_dir.glob("*/*.yaml")):
-        rule = schema["rules"].setdefault(rule_group_file.parent.name, {})
-        lgr.debug(f"Loading {rule_group_file.stem} rules.")
-        dict_ = _yaml.load(rule_group_file.read_text())
-        rule[rule_group_file.stem] = dereference_yaml(dict_, dict_)
-
-    return schema
-
-
-def filter_schema(schema, **kwargs):
-    """Filter the schema based on a set of keyword arguments.
-
-    Parameters
-    ----------
-    schema : dict
-        The schema object, which is a dictionary with nested dictionaries and
-        lists stored within it.
-    kwargs : dict
-        Keyword arguments used to filter the schema.
-        Example kwargs that may be used include: "suffixes", "datatypes",
-        "extensions".
-
-    Returns
-    -------
-    new_schema : dict
-        The filtered version of the schema.
-
-    Notes
-    -----
-    This function calls itself recursively, in order to apply filters at
-    arbitrary depth.
-
-    Warning
-    -------
-    This function employs a *very* simple filter. It is very limited.
-    """
-    new_schema = deepcopy(schema)
-    if isinstance(new_schema, dict):
-        # Reduce values in dict to only requested
-        for k, v in kwargs.items():
-            if k in new_schema.keys():
-                filtered_item = deepcopy(new_schema[k])
-                if isinstance(filtered_item, dict):
-                    filtered_item = {
-                        k1: v1 for k1, v1 in filtered_item.items() if k1 in v
-                    }
-                else:
-                    filtered_item = [i for i in filtered_item if i in v]
-                new_schema[k] = filtered_item
-
-            for k2, v2 in new_schema.items():
-                new_schema[k2] = filter_schema(new_schema[k2], **kwargs)
-
-    elif isinstance(new_schema, list):
-        for i, item in enumerate(new_schema):
-            if isinstance(item, dict):
-                new_schema[i] = filter_schema(item, **kwargs)
-    return new_schema
diff --git a/dandi/support/bids/schemadata/1.7.0+012+dandi001/README.md b/dandi/support/bids/schemadata/1.7.0+012+dandi001/README.md
deleted file mode 100644
index c3d142cba..000000000
--- a/dandi/support/bids/schemadata/1.7.0+012+dandi001/README.md
+++ /dev/null
@@ -1,500 +0,0 @@
-# BIDS-schema
-
-Portions of the BIDS specification are defined using YAML files, in order to
-make the specification machine-readable.
-
-Currently, the portions of the specification that rely on this schema are
-the entity tables, entity definitions, filename templates, and metadata tables.
-Any changes to the specification should be mirrored in the schema.
-
-## The format of the schema
-
-The schema is divided into two parts: the object definitions and the rules.
-
-The object definitions (files in `objects/`) describe attributes of individual
-objects or data types in the specification.
-Common information in these files includes full names, descriptions, and
-constraints on valid values.
-These files **do not** describe how objects of different types
-(for example file suffixes and file entities) interact with one another, or
-whether objects are required in a given dataset or file.
-
-The rules (files in `rules/`) describe how objects related to one another,
-as well as their requirement levels.
-
-## Object files
-
-The types of objects currently supported in the schema are:
-
--   modalities,
--   datatypes,
--   entities,
--   suffixes,
--   metadata,
--   top-level files,
--   and non-BIDS associated folders.
-
-Each of these object types has a single file in the `objects/` folder.
-
--   `modalities.yaml`: The modalities, or types of technology, used to acquire data in a BIDS dataset.
-    These modalities are not reflected directly in the specification.
-    For example, while both fMRI and DWI data are acquired with an MRI,
-    in a BIDS dataset they are stored in different folders reflecting the two different `datatypes`.
-
--   `datatypes.yaml`: Data types supported by the specification.
-    The only information provided in the file is:
-
-    1.  a full list of valid BIDS datatypes
-    1.  each datatype's full name
-    1.  a free text description of the datatype.
-
--   `entities.yaml`: Entities (key/value pairs in folder and filenames).
-
--   `metadata.yaml`: All valid metadata fields that are explicitly supported in BIDS sidecar JSON files.
-
--   `columns.yaml`: All valid columns that are explicitly supported in BIDS TSV files.
-
--   `suffixes.yaml`: Valid file suffixes.
-
--   `top_level_files.yaml`: Valid top-level files which may appear in a BIDS dataset.
-
--   `associated_data.yaml`: Folders that may appear within a dataset folder without following BIDS rules.
-
-### On re-used objects with different definitions
-
-If an object may mean something different depending on where it is used within the specification,
-then this must be reflected in the schema.
-Specifically, each version of the object must have its own definition within the relevant file.
-However, since object files are organized as dictionaries, each object must have a unique key.
-Thus, we append a suffix to each re-used object's key in order to make it unique.
-For objects with `CamelCase` names (for example, metadata fields), the suffix will start with a single underscore (`_`).
-For objects with `snake_case` names, two underscores must be used.
-
-There should also be a comment near the object definition in the YAML file describing the nature of the different objects.
-
-For example, the TSV column `"reference"` means different things when used for EEG data, as compared to iEEG data.
-As such, there are two definitions in `columns.yaml` for the `"reference"` column: `"reference__eeg"` and `"reference_ieeg"`.
-
-```yaml
-# reference column for channels.tsv files for EEG data
-reference__eeg:
-  name: reference
-  description: |
-    Name of the reference electrode(s).
-    This column is not needed when it is common to all channels.
-    In that case the reference electrode(s) can be specified in `*_eeg.json` as `EEGReference`).
-  type: string
-# reference column for channels.tsv files for iEEG data
-reference__ieeg:
-  name: reference
-  description: |
-    Specification of the reference (for example, 'mastoid', 'ElectrodeName01', 'intracranial', 'CAR', 'other', 'n/a').
-    If the channel is not an electrode channel (for example, a microphone channel) use `n/a`.
-  anyOf:
-  - type: string
-  - type: string
-    enum:
-    - n/a
-```
-
-When adding new object definitions to the schema,
-every effort should be made to find a shared, common definition for the term, should it already exist.
-If the differences between two versions of the same object are subtle or driven by context,
-then you can generally _append_ additional text to the object definition within the associated rendered table in the specification,
-rather than creating a separate entry in the schema.
-
-### `modalities.yaml`
-
-This file contains a dictionary in which each modality is defined.
-Keys are modality abbreviations (for example, `mri` for magnetic resonance imaging),
-and each associated value is a dictionary with two keys: `name` and `description`.
-
-The `name` field is the full name of the modality.
-The `description` field is a freeform description of the modality.
-
-### `datatypes.yaml`
-
-This file contains a dictionary in which each datatype is defined.
-Keys are the folder names associated with each datatype (for example, `anat` for anatomical MRI),
-and each associated value is a dictionary with two keys: `name` and `description`.
-
-The `name` field is the full name of the datatype.
-The `description` field is a freeform description of the datatype.
-
-### `entities.yaml`
-
-This file contains a dictionary in which each entity (key/value pair in filenames) is defined.
-Keys are long-form versions of the entities, which are distinct from both the entities as
-they appear in filenames _and_ their full names.
-For example, the key for the "Contrast Enhancing Agent" entity, which appears in filenames as `ce-<label>`,
-is `ceagent`.
-These keys are also the recommended variable names for their associated entities in BIDS-compliant code,
-since many entities (such as `ce`) have very short filename elements.
-Each key's associated value is a dictionary with five keys:
-
--   `name`,
--   `entity`,
--   `description`,
--   `type`,
--   and either `format` or `enum`.
-
-The `name` field is the full name of the entity. For example, the `name` for `ceagent` is "Contrast Enhancing Agent".
-
-The `entity` field is the entity as it appears in filenames. For example, the `entity` for `ceagent` is `ce`.
-
-The `description` field is a freeform description of the entity.
-The description should apply to _all_ uses of the entity,
-so if there is some additional information about the entity that applies specifically to a subset of suffixes or datatypes,
-then that information should be provided in the specification, rather than the schema.
-
-The `type` field defines the representation type for the value associated with the entity.
-Given that all entities appear in filenames, they should all be strings and the `type` field should always be `string`.
-This is true of both alphanumeric entities (such as `acq-desc`) and numeric ones (such as `run-1`).
-
-The `format` field defines the specific format the value should take.
-Entities are broadly divided into either `label` or `index` types.
-
-When `format` is `index`, then the entity's associated value should be a non-zero integer, optionally with leading zeros.
-For example, `run` should have an index, so a valid key-value pair in a filename would be `run-01`.
-
-When `format` is `label`, then the value should be an alphanumeric string.
-Beyond limitations on which characters are allowed, labels have few restrictions.
-For example, `acq` should have a label, so a valid key-value pair might be `acq-someLabel`.
-
-For a small number of entities, only certain labels are allowed.
-In those cases, instead of a `format` field, there will be an `enum` field, which will provide a list of allowed values.
-
-### `metadata.yaml`
-
-This file contains definitions for all metadata fields (fields which may appear in sidecar JSON files)
-currently supported in BIDS.
-
-Entries in this file contain, at minimum, the following fields: `name`,
-`description`, and a set of fields for describing the field's data type.
-
-The data types include:
-
--   `type`, which MUST have a value of `array`,
--   `string`,
--   `integer`,
--   `number`,
--   `object`,
--   or `boolean`.
-
-There are additional fields which may define rules that apply to a given type.
-
--   `array`: If `type` is `array`, then there MUST be an `items` field at
-    the same level as `type`. `items` describes the data type and rules that
-    apply to the individual items in the array. The same rules that apply to
-    describing data types for the field itself apply to `items`.
-    Additionally, there may be any of the following fields at the same level
-    as `type`: `minItems`, `maxItems`.
-    Here is an example of a field that MUST have three `integer` items:
-    ```yaml
-    ExampleField:
-        name: ExampleField
-        description: |
-            The description of "ExampleField".
-        type: array
-        minItems: 3
-        maxItems: 3
-        items:
-            type: integer
-    ```
-
--   `string`: If `type` is `string`, then there MAY be any of the following
-    fields at the same level as `type`: `pattern`, `format`, and `enum`.
-
-    -   `pattern` defines a regular expression for valid string names.
-
-    -   `format` defines the format for the string at the same level as `type`.
-        Valid values for `format` include:
-
-       -   `uri` (uniform resource identifiers),
-
-       -   `date` (date-times),
-
-       -   `unit` (standard units),
-
-       -   `dataset_relative` (relative paths from dataset root),
-
-       -   `participant_relative` (relative paths from participant folder).
-
-    -   `enum` defines a list of valid values for the field.
-        The minimum string length (`minLength`) defaults to 1.
-        Here is an example of a field with a restricted set of possible values:
-        ```yaml
-        ExampleField:
-            name: ExampleField
-            description: |
-                The description of "ExampleField".
-            type: string
-            enum:
-                - PossibleValue1
-                - PossibleValue2
-        ```
-
--   `integer`: If `type` is `integer`, then there MAY be any of the
-    following fields at the same level as `type`: `unit`,
-    `minimum` (inclusive minimum), `maximum` (inclusive maximum),
-    `exclusiveMinimum`, `exclusiveMaximum`.
-    Here is an example of a field with a minimum value of 0:
-    ```yaml
-    ExampleField:
-        name: ExampleField
-        description: |
-            The description of "ExampleField".
-        type: integer
-        minimum: 0
-    ```
-
--   `number`: If `type` is `number`, then there MAY be any of the following
-    fields at the same level as `type`: `unit`,
-    `minimum` (inclusive minimum), `maximum` (inclusive maximum),
-    `exclusiveMinimum`, `exclusiveMaximum`.
-    Here is an example of a field with a minimum of 0, in units of
-    kilometers per second:
-    ```yaml
-    ExampleField:
-        name: ExampleField
-        description: |
-            The description of "ExampleField".
-        type: number
-        minimum: 0
-        # k stands for "kilo", m stands for "meter", "/" means "per", and
-        # s stands for "seconds"
-        unit: km/s
-    ```
-
--   `object`: If `type` is `object`, then there MAY be any of the following
-    fields at the same level as `type`: `additionalProperties`,
-    `properties`.
-    Objects are defined as sets of key/value pairs.
-    Keys MUST be strings, while values may have specific attributes,
-    which is what `additionalProperties` describes.
-    Here is an example of a field which MUST be an object,
-    with one optional field named "OptionalField" that MUST be a `string`
-    and any number of additional optional fields that MUST be `number`s.
-    ```yaml
-    ExampleField:
-        name: ExampleField
-        description: |
-            The description of "ExampleField".
-        type: object
-        properties:
-            OptionalField:
-                type: string
-        additionalProperties:
-            type: number
-    ```
-
--   `boolean`: If `type` is `boolean`, then the field's value MUST be one
-    of: `true`, `false`. Here is an example:
-    ```yaml
-    ExampleField:
-        name: ExampleField
-        description: |
-            The description of "ExampleField".
-        type: boolean
-    ```
-
-Additionally, if multiple data types are possible for a given field
-(for example, if a field may be a `number` or an `array` of `number`s),
-then an `anyOf` field MUST be used, in which an array of data type
-descriptions MUST be defined.
-Here is an example of one such case:
-```yaml
-ExampleField:
-    name: ExampleField
-    description: |
-        The description of "ExampleField".
-    anyOf:
-        - type: number
-        - type: array
-            items:
-            type: number
-```
-
-Furthermore, if the data type description of a field is reused across fields,
-then it may be defined in a separate field and referenced in each target field with the `$ref` keyword.
-Here is an example of a field definition using `$ref`:
-```yaml
-ExampleField:
-    name: ExampleField
-    description: |
-        The description of "ExampleField".
-    $ref: _ReferenceField
-```
-The target field (`_ReferenceField` in this case) MUST be located in
-the metadata YAML file, and MUST contain all information
-that would be used to describe the field's data type otherwise.
-
-Here is an example of a reference field:
-```yaml
-_ReferenceField:
-    name: _ReferenceField
-    description: |
-        Description of "_ReferenceField".
-    type: string
-    enum:
-        - PossibleValue1
-        - PossibleValue2
-```
-
-The result of including `$ref` makes the `ExampleField` above equivalent to the following format:
-```yaml
-ExampleField:
-    name: ExampleField
-    description: |
-        The description of "ExampleField".
-    type: string
-    enum:
-        - PossibleValue1
-        - PossibleValue2
-```
-
-### `columns.yaml`
-
-This file contains definitions for all TSV columns currently supported in BIDS.
-
-Entries in this file follow the same rules as `metadata.yaml`,
-although column names appear in `snake_case`, rather than `CamelCase`.
-
-### `suffixes.yaml`
-
-This file contains a dictionary in which each suffix is defined.
-Keys are the suffixes (for example, `T1w` for a T1-weighted image),
-and each associated value is a dictionary with three keys: `name`, `description`, and (optionally) `unit`.
-
-The `name` field is the full name of the suffix.
-The `description` field is a freeform description of the type of data stored in files with the suffix.
-
-The `unit` field describes units in which the data may appear.
-When no `unit` field is present, data with that suffix is assumed to be in arbitrary units.
-The `unit` field may use an `anyOf` keyword if multiple valid units are possible.
-
-These entries may also, rarely, include fields defining the range or types of values that are valid for
-files with the suffix.
-For example, `MTRmap` files must have values between 0 and 100, since they represent percentages.
-
-### `top_level_files.yaml`
-
-This file contains a dictionary in which each top-level file is defined.
-Keys are the filenames (without file extensions),
-and each associated value is a dictionary with two keys: `name` and `description`.
-
-The `name` field is the full name of the file.
-The `description` field is a freeform description of the file.
-
-### `associated_data.yaml`
-
-This file contains a dictionary in which each non-BIDS folder is defined.
-Keys are folder names, and each associated value is a dictionary with two keys: `name` and `description`.
-
-The `name` field is the full name of the folder.
-The `description` field is a freeform description of the folder.
-
-## Rule files
-
-The files in the `rules/` folder are less standardized than the files in `objects/`,
-because rules governing how different object types interact in a valid dataset are more variable
-than the object definitions.
-
--   `modalities.yaml`: This file simply groups `datatypes` under their associated modality.
-
--   `datatypes/*.yaml`: Files in the `datatypes` folder contain information about valid filenames within a given datatype.
-    Specifically, each datatype's YAML file contains a list of dictionaries.
-    Each dictionary contains a list of suffixes, entities, and file extensions which may constitute a valid BIDS filename.
-
--   `entities.yaml`: This file simply defines the order in which entities, when present, MUST appear in filenames.
-
--   `top_level_files.yaml`: Requirement levels and valid file extensions of top-level files.
-
--   `associated_data.yaml`: Requirement levels of associated non-BIDS folders.
-
-### `modalities.yaml`
-
-This file contains a dictionary in which each key is a modality abbreviation and the value is a dictionary with one key: `datatypes`.
-The `datatypes` dictionary contains a list of datatypes that fall under that modality.
-
-### `datatypes/*.yaml`
-
-The files in this folder are currently the least standardized of any part of the schema.
-
-Each file corresponds to a single `datatype`.
-Within the file is a list of dictionaries.
-Each dictionary corresponds to a group of suffixes that have the same rules regarding filenames.
-
-The dictionaries have three keys: `suffixes`, `extensions`, and `entities`.
-
-The `suffixes` entry is a list of file suffixes for which all of the extensions in the `extensions` entry
-and all of the entity rules in the `entities` entry apply.
-
-The `extensions` entry is a list of valid file extensions.
-
-The `entities` entry is a dictionary in which the keys are entity names and the values are whether the entity is
-required or optional for that suffix.
-Any entities that are not present in this dictionary are not allowed in files with any of the suffixes in the group.
-In rare occasions, there are restrictions on valid entity values
-(for example, some suffixes may only allow an `acq` value of `calibration`).
-In those cases, the entity's value will be another object, rather than a string indicating the requirement level.
-This object will contain at least two keys: "requirement" and "type".
-
-**NOTE**: The order in which entities appear in these dictionaries does not reflect how they should appear in filenames.
-That information is present in `rules/entities.yaml`.
-
-As an example, let us look at part of `meg.yaml`:
-
-```yaml
-- suffixes:
-  - meg
-  extensions:
-  - .fif
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    run: optional
-    processing: optional
-    split: optional
-
-- suffixes:
-  - meg
-  extensions:
-  - .fif
-  entities:
-    subject: required
-    session: optional
-    acquisition:
-      requirement: required
-      type: string
-      enum:
-      - crosstalk
-```
-
-In this case, the first group has one suffix: `meg`.
-The second group has the same suffix (`meg`), but describes different rules for files with that suffix.
-While the valid extension is the same for both groups (`.fif`), the entities are not.
-
-Specifically, files in the first group may have `task`, `run`, `processing`, and `split` entities,
-while files in the second group may not.
-Also, when files in the second group have the `acq` entity, the associated value MUST be `crosstalk`.
-
-### `entities.yaml`
-
-This file contains a list of entities in the order in which they must appear in filenames.
-
-### `top_level_files.yaml`
-
-This file contains a dictionary in which each key is a top-level file and the value is a dictionary with two keys:
-`required` and `extensions`.
-The `required` entry contains a boolean value (true or false) to indicate if that top-level file is required for BIDS datasets or not.
-The `extensions` entry contains a list of valid file extensions for the file.
-
-In cases where there is a data file and a metadata file, the `.json` extension for metadata file is included.
-
-### `associated_data.yaml`
-
-This file contains a dictionary in which each key is a folder and the value is a dictionary with one key: `required`.
-The `required` entry contains a boolean value to indicate if that folder is required for BIDS datasets or not.
diff --git a/dandi/support/bids/schemadata/1.7.0+012+dandi001/objects/associated_data.yaml b/dandi/support/bids/schemadata/1.7.0+012+dandi001/objects/associated_data.yaml
deleted file mode 100644
index 901e17bda..000000000
--- a/dandi/support/bids/schemadata/1.7.0+012+dandi001/objects/associated_data.yaml
+++ /dev/null
@@ -1,29 +0,0 @@
----
-# This file describes folders that may appear within a dataset folder
-# without following BIDS rules.
-# Information about whether these folders are required or not is present in
-# `rules/associated_data.yaml`.
-code:
-  name: Code
-  description: |
-    A folder in which to store any code used to generate the derivatives from the
-    source data.
-derivatives:
-  name: Derivative data
-  description: |
-    Derivative data
-sourcedata:
-  name: Source data
-  description: |
-    Data before harmonization, reconstruction, and/or file format conversion
-    (for example, E-Prime event logs or DICOM files).
-stimuli:
-  name: Stimulus files
-  description: |
-    The stimulus files can be added in a `/stimuli` folder
-    (under the root folder of the dataset; with optional subfolders)
-    AND using a stim_file column in *_events.tsv mentioning which stimulus file was
-    used for a given event.
-
-    There are no restrictions on the file formats of the stimuli files, but they should be
-    stored in the `/stimuli` folder.
diff --git a/dandi/support/bids/schemadata/1.7.0+012+dandi001/objects/columns.yaml b/dandi/support/bids/schemadata/1.7.0+012+dandi001/objects/columns.yaml
deleted file mode 100644
index 1c34c936b..000000000
--- a/dandi/support/bids/schemadata/1.7.0+012+dandi001/objects/columns.yaml
+++ /dev/null
@@ -1,562 +0,0 @@
----
-HED:
-  name: HED
-  description: |
-    Hierarchical Event Descriptor (HED) Tag.
-    See [Appendix III](/99-appendices/03-hed.html) for details.
-  type: string
-abbreviation:
-  name: abbreviation
-  description: |
-    The unique label abbreviation
-  type: string
-acq_time__scans:
-  name: acq_time
-  description: |
-    Acquisition time refers to when the first data point in each run was acquired.
-    Furthermore, if this header is provided, the acquisition times of all files
-    from the same recording MUST be identical.
-    Datetime format and their anonymization are described in [Units](/02-common-principles.html#units).
-  type: string
-  format: datetime
-acq_time__sessions:
-  name: acq_time
-  description: |
-    Acquisition time refers to when the first data point of the first run was acquired.
-    Datetime format and their anonymization are described in [Units](/02-common-principles.html#units).
-  type: string
-  format: datetime
-age:
-  name: age
-  description: |
-    Numeric value in years (float or integer value).
-  type: number
-  unit: year
-cardiac:
-  name: cardiac
-  description: |
-    continuous pulse measurement
-  type: number
-color:
-  name: color
-  description: |
-    Hexadecimal. Label color for visualization.
-  type: string
-  unit: hexadecimal
-derived_from:
-  name: derived_from
-  description: |
-    `sample-<label>` key/value pair from which a sample is derived,
-    for example a slice of tissue (`sample-02`) derived from a block of tissue (`sample-01`).
-  type: string
-  pattern: ^sample-[0-9a-zA-Z]+$
-description:
-  name: description
-  description: |
-    Brief free-text description of the channel, or other information of interest.
-  type: string
-dimension:
-  name: dimension
-  description: |
-    Size of the group (grid/strip/probe) that this electrode belongs to.
-    Must be of form `[AxB]` with the smallest dimension first (for example, `[1x8]`).
-  type: string
-duration:
-  name: duration
-  description: |
-    Duration of the event (measured from onset) in seconds.
-    Must always be either zero or positive (or `n/a` if unavailable).
-    A "duration" value of zero implies that the delta function or event is so
-    short as to be effectively modeled as an impulse.
-  anyOf:
-  - type: number
-    unit: s
-    minimum: 0
-  - type: string
-    enum:
-    - n/a
-filename:
-  name: filename
-  description: |
-    Relative paths to files.
-  type: string
-  format: participant_relative
-group:
-  name: group
-  description: |
-    Which group of channels (grid/strip/seeg/depth) this channel belongs to.
-    This is relevant because one group has one cable-bundle and noise can be shared.
-    This can be a name or number.
-  anyOf:
-  - type: string
-  - type: number
-handedness:
-  name: handedness
-  description: |
-    String value indicating one of "left", "right", "ambidextrous".
-
-    For "left", use one of these values: `left`, `l`, `L`, `LEFT`, `Left`.
-
-    For "right", use one of these values: `right`, `r`, `R`, `RIGHT`, `Right`.
-
-    For "ambidextrous", use one of these values: `ambidextrous`, `a`, `A`, `AMBIDEXTROUS`,
-    `Ambidextrous`.
-  type: string
-  enum:
-  - left
-  - l
-  - L
-  - LEFT
-  - Left
-  - right
-  - r
-  - R
-  - RIGHT
-  - Right
-  - ambidextrous
-  - a
-  - A
-  - AMBIDEXTROUS
-  - Ambidextrous
-  - n/a
-hemisphere:
-  name: hemisphere
-  description: |
-    The hemisphere in which the electrode is placed.
-  type: string
-  enum:
-  - L
-  - R
-high_cutoff:
-  name: high_cutoff
-  description: |
-    Frequencies used for the low-pass filter applied to the channel in Hz.
-    If no low-pass filter applied, use `n/a`.
-    Note that hardware anti-aliasing in A/D conversion of all MEG/EEG electronics
-    applies a low-pass filter; specify its frequency here if applicable.
-  anyOf:
-  - type: number
-    unit: Hz
-    minimum: 0
-  - type: string
-    enum:
-    - n/a
-hplc_recovery_fractions:
-  name: hplc_recovery_fractions
-  description: |
-    HPLC recovery fractions (the fraction of activity that gets loaded onto the HPLC).
-  type: number
-  unit: arbitrary
-impedance:
-  name: impedance
-  description: |
-    Impedance of the electrode, units MUST be in `kOhm`.
-  type: number
-  unit: kOhm
-index:
-  name: index
-  description: |
-    The label integer index.
-  type: integer
-low_cutoff:
-  name: low_cutoff
-  description: |
-    Frequencies used for the high-pass filter applied to the channel in Hz.
-    If no high-pass filter applied, use `n/a`.
-  anyOf:
-  - type: number
-    unit: Hz
-  - type: string
-    enum:
-    - n/a
-manufacturer:
-  name: manufacturer
-  description: |
-    The manufacturer for each electrode.
-    Can be used if electrodes were manufactured by more than one company.
-  type: string
-mapping:
-  name: mapping
-  description: |
-    Corresponding integer label in the standard BIDS label lookup.
-  type: integer
-material:
-  name: material
-  description: |
-    Material of the electrode (for example, `Tin`, `Ag/AgCl`, `Gold`).
-  type: string
-metabolite_parent_fraction:
-  name: metabolite_parent_fraction
-  description: |
-    Parent fraction of the radiotracer (0-1).
-  type: number
-  minimum: 0
-  maximum: 1
-metabolite_polar_fraction:
-  name: metabolite_polar_fraction
-  description: |
-    Polar metabolite fraction of the radiotracer (0-1).
-  type: number
-  minimum: 0
-  maximum: 1
-# name column for channels.tsv files
-name__channels:
-  name: name
-  description: |
-    Label of the channel.
-  type: string
-# name column for electrodes.tsv files
-name__electrodes:
-  name: name
-  description: |
-    Name of the electrode contact point.
-  type: string
-# name column for dseg.tsv files
-name__segmentations:
-  name: name
-  description: |
-    The unique label name.
-  type: string
-notch:
-  name: notch
-  description: |
-    Frequencies used for the notch filter applied to the channel, in Hz.
-    If no notch filter applied, use `n/a`.
-  anyOf:
-  - type: number
-    unit: Hz
-  - type: string
-    enum:
-    - n/a
-onset:
-  name: onset
-  description: |
-    Onset (in seconds) of the event, measured from the beginning of the acquisition
-    of the first data point stored in the corresponding task data file.
-    Negative onsets are allowed, to account for events that occur prior to the first
-    stored data point.
-    For example, in case there is an in-scanner training phase that begins before
-    the scanning sequence has started events from this sequence should have
-    negative onset time counting down to the beginning of the acquisition of the
-    first volume.
-
-    If any data points have been discarded before forming the data file
-    (for example, "dummy volumes" in BOLD fMRI),
-    a time of 0 corresponds to the first stored data point and not the first
-    acquired data point.
-  type: number
-  unit: s
-pathology:
-  name: pathology
-  description: |
-    String value describing the pathology of the sample or type of control.
-    When different from `healthy`, pathology SHOULD be specified.
-    The pathology may be specified in either `samples.tsv` or
-    `sessions.tsv`, depending on whether the pathology changes over time.
-  type: string
-participant_id:
-  name: participant_id
-  description: |
-    A participant identifier of the form `sub-<label>`,
-    matching a participant entity found in the dataset.
-  type: string
-  pattern: ^sub-[0-9a-zA-Z]+$
-plasma_radioactivity:
-  name: plasma_radioactivity
-  description: |
-    Radioactivity in plasma, in unit of plasma radioactivity (for example, `kBq/mL`).
-  type: number
-# reference column for channels.tsv files for EEG data
-reference__eeg:
-  name: reference
-  description: |
-    Name of the reference electrode(s).
-    This column is not needed when it is common to all channels.
-    In that case the reference electrode(s) can be specified in `*_eeg.json` as `EEGReference`).
-  type: string
-# reference column for channels.tsv files for iEEG data
-reference__ieeg:
-  name: reference
-  description: |
-    Specification of the reference (for example, `mastoid`, `ElectrodeName01`, `intracranial`, `CAR`, `other`, `n/a`).
-    If the channel is not an electrode channel (for example, a microphone channel) use `n/a`.
-  anyOf:
-  - type: string
-  - type: string
-    enum:
-    - n/a
-respiratory:
-  name: respiratory
-  description: |
-    continuous breathing measurement
-  type: number
-response_time:
-  name: response_time
-  description: |
-    Response time measured in seconds.
-    A negative response time can be used to represent preemptive responses and
-    `n/a` denotes a missed response.
-  anyOf:
-  - type: number
-    unit: s
-  - type: string
-    enum:
-    - n/a
-sample:
-  name: sample
-  description: |
-    Onset of the event according to the sampling scheme of the recorded modality
-    (that is, referring to the raw data file that the `events.tsv` file accompanies).
-  type: integer
-sample_id:
-  name: sample_id
-  description: |
-    A sample identifier of the form `sample-<label>`,
-    matching a sample entity found in the dataset.
-  type: string
-  pattern: ^sample-[0-9a-zA-Z]+$
-sample_type:
-  name: sample_type
-  description: |
-    Biosample type defined by
-    [ENCODE Biosample Type](https://www.encodeproject.org/profiles/biosample_type).
-  type: string
-  enum:
-  - cell line
-  - in vitro differentiated cells
-  - primary cell
-  - cell-free sample
-  - cloning host
-  - tissue
-  - whole organisms
-  - organoid
-  - technical sample
-sampling_frequency:
-  name: sampling_frequency
-  description: |
-    Sampling rate of the channel in Hz.
-  type: number
-  unit: Hz
-session_id:
-  name: session_id
-  description: |
-    A session identifier of the form `ses-<label>`,
-    matching a session found in the dataset.
-  type: string
-  pattern: ^ses-[0-9a-zA-Z]+$
-sex:
-  name: sex
-  description: |
-    String value indicating phenotypical sex, one of "male", "female", "other".
-
-    For "male", use one of these values: `male`, `m`, `M`, `MALE`, `Male`.
-
-    For "female", use one of these values: `female`, `f`, `F`, `FEMALE`, `Female`.
-
-    For "other", use one of these values: `other`, `o`, `O`, `OTHER`, `Other`.
-  type: string
-  enum:
-  - male
-  - m
-  - M
-  - MALE
-  - Male
-  - female
-  - f
-  - F
-  - FEMALE
-  - Female
-  - other
-  - o
-  - O
-  - OTHER
-  - Other
-  - n/a
-size:
-  name: size
-  description: |
-    Surface area of the electrode, units MUST be in `mm^2`.
-  type: number
-  unit: mm2
-software_filters:
-  name: software_filters
-  description: |
-    List of temporal and/or spatial software filters applied
-    (for example, `SSS`, `SpatialCompensation`).
-    Note that parameters should be defined in the general MEG sidecar .json file.
-    Indicate `n/a` in the absence of software filters applied.
-  anyOf:
-  - type: string
-  - type: string
-    enum:
-    - n/a
-species:
-  name: species
-  description: |
-    The `species` column SHOULD be a binomial species name from the
-    [NCBI Taxonomy](https://www.ncbi.nlm.nih.gov/Taxonomy/Browser/wwwtax.cgi)
-    (for example, `homo sapiens`, `mus musculus`, `rattus norvegicus`).
-    For backwards compatibility, if `species` is absent, the participant is assumed to be
-    `homo sapiens`.
-  type: string
-status:
-  name: status
-  description: |
-    Data quality observed on the channel.
-    A channel is considered `bad` if its data quality is compromised by excessive noise.
-    If quality is unknown, then a value of `n/a` may be used.
-    Description of noise type SHOULD be provided in `[status_description]`.
-  type: string
-  enum:
-  - good
-  - bad
-  - n/a
-status_description:
-  name: status_description
-  description: |
-    Freeform text description of noise or artifact affecting data quality on the channel.
-    It is meant to explain why the channel was declared bad in `[status]`.
-  type: string
-stim_file:
-  name: stim_file
-  description: |
-    Represents the location of the stimulus file (such as an image, video, or
-    audio file) presented at the given onset time.
-    There are no restrictions on the file formats of the stimuli files,
-    but they should be stored in the `/stimuli` folder
-    (under the root folder of the dataset; with optional subfolders).
-    The values under the `stim_file` column correspond to a path relative to
-    `/stimuli`.
-    For example `images/cat03.jpg` will be translated to `/stimuli/images/cat03.jpg`.
-  type: string
-  format: stimuli_relative
-strain:
-  name: strain
-  description: |
-    For species different from `homo sapiens`, string value indicating
-    the strain of the species, for example: `C57BL/6J`.
-  type: string
-strain_rrid:
-  name: strain_rrid
-  description: |
-    For species different from `homo sapiens`, research resource identifier
-    ([RRID](https://scicrunch.org/resources/Organisms/search))
-    of the strain of the species, for example: `RRID:IMSR_JAX:000664`.
-  type: string
-  format: rrid
-time:
-  name: time
-  description: |
-    Time, in seconds, relative to `TimeZero` defined by the `*_pet.json`.
-    For example, 5.
-  type: number
-  unit: s
-trial_type:
-  name: trial_type
-  description: |
-    Primary categorisation of each trial to identify them as instances of the
-    experimental conditions.
-    For example: for a response inhibition task, it could take on values `go` and
-    `no-go` to refer to response initiation and response inhibition experimental
-    conditions.
-  type: string
-trigger:
-  name: trigger
-  description: |
-    continuous measurement of the scanner trigger signal
-  type: number
-# type column in channels.tsv files
-type__channels:
-  name: type
-  description: |
-    Type of channel; MUST use the channel types listed below.
-    Note that the type MUST be in upper-case.
-  type: string
-  enum:
-  - MEGMAG
-  - MEGGRADAXIAL
-  - MEGGRADPLANAR
-  - MEGREFMAG
-  - MEGREFGRADAXIAL
-  - MEGREFGRADPLANAR
-  - MEGOTHER
-  - EEG
-  - ECOG
-  - SEEG
-  - DBS
-  - VEOG
-  - HEOG
-  - EOG
-  - ECG
-  - EMG
-  - TRIG
-  - AUDIO
-  - PD
-  - EYEGAZE
-  - PUPIL
-  - MISC
-  - SYSCLOCK
-  - ADC
-  - DAC
-  - HLU
-  - FITERR
-  - OTHER
-# type column for electrodes.tsv files
-type__electrodes:
-  name: type
-  description: |
-    Type of the electrode (for example, cup, ring, clip-on, wire, needle).
-  type: string
-units:
-  name: units
-  description: |
-    Physical unit of the value represented in this channel,
-    for example, `V` for Volt, or `fT/cm` for femto Tesla per centimeter
-    (see [Units](/02-common-principles.html#units)).
-  type: string
-  format: unit
-value:
-  name: value
-  description: |
-    Marker value associated with the event (for example, the value of a TTL
-    trigger that was recorded at the onset of the event).
-  anyOf:
-  - type: number
-  - type: string
-volume_type:
-  name: volume_type
-  description: |
-    The `*_aslcontext.tsv` table consists of a single column of labels identifying
-    the `volume_type` of each volume in the corresponding `*_asl.nii[.gz]` file.
-  type: string
-  enum:
-  - control
-  - label
-  - m0scan
-  - deltam
-  - cbf
-whole_blood_radioactivity:
-  name: whole_blood_radioactivity
-  description: |
-    Radioactivity in whole blood samples,
-    in unit of radioactivity measurements in whole blood samples (for example, `kBq/mL`).
-  type: number
-x:
-  name: x
-  description: |
-    Recorded position along the x-axis.
-  type: number
-y:
-  name: y
-  description: |
-    Recorded position along the y-axis.
-  type: number
-z:
-  name: z
-  description: |
-    Recorded position along the z-axis.
-  anyOf:
-  - type: number
-  - type: string
-    enum:
-    - n/a
diff --git a/dandi/support/bids/schemadata/1.7.0+012+dandi001/objects/datatypes.yaml b/dandi/support/bids/schemadata/1.7.0+012+dandi001/objects/datatypes.yaml
deleted file mode 100644
index 06c059eed..000000000
--- a/dandi/support/bids/schemadata/1.7.0+012+dandi001/objects/datatypes.yaml
+++ /dev/null
@@ -1,44 +0,0 @@
----
-# This file defines valid BIDS datatypes, along with their full names and descriptions.
-# For rules regarding how suffixes relate to datatypes, see files in `rules/datatypes/`.
-anat:
-  name: Anatomical Magnetic Resonance Imaging
-  description: |
-    Magnetic resonance imaging sequences designed to characterize static, anatomical features.
-beh:
-  name: Behavioral Data
-  description: |
-    Behavioral data.
-dwi:
-  name: Diffusion-Weighted Imaging
-  description: |
-    Diffusion-weighted imaging (DWI).
-eeg:
-  name: Electroencephalography
-  description: Electroencephalography
-fmap:
-  name: Field maps
-  description: |
-    MRI scans for estimating B0 inhomogeneity-induced distortions.
-func:
-  name: Task-Based Magnetic Resonance Imaging
-  description: |
-    Task (including resting state) imaging data
-ieeg:
-  name: Intracranial electroencephalography
-  description: |
-    Intracranial electroencephalography (iEEG) or electrocorticography (ECoG) data
-meg:
-  name: Magnetoencephalography
-  description: Magnetoencephalography
-micr:
-  name: Microscopy
-  description: Microscopy
-perf:
-  name: Perfusion imaging
-  description: |
-    Blood perfusion imaging data, including arterial spin labeling (ASL)
-pet:
-  name: Positron Emission Tomography
-  description: |
-    Positron emission tomography data
diff --git a/dandi/support/bids/schemadata/1.7.0+012+dandi001/objects/entities.yaml b/dandi/support/bids/schemadata/1.7.0+012+dandi001/objects/entities.yaml
deleted file mode 100644
index 657b835ee..000000000
--- a/dandi/support/bids/schemadata/1.7.0+012+dandi001/objects/entities.yaml
+++ /dev/null
@@ -1,366 +0,0 @@
----
-# This file describes entities present in BIDS filenames.
-# WARNING: The entities are presented here in alphabetical order!
-# The appropriate order of entities in filenames is defined in `rules/entities.yaml`,
-# rather than this file (`objects/entities.yaml`).
-acquisition:
-  name: Acquisition
-  entity: acq
-  description: |
-    The `acq-<label>` key/value pair corresponds to a custom label the
-    user MAY use to distinguish a different set of parameters used for
-    acquiring the same modality.
-    For example this should be used when a study includes two T1w images - one
-    full brain low resolution and one restricted field of view but high
-    resolution.
-    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.
-  type: string
-  format: label
-atlas:
-  name: Atlas
-  entity: atlas
-  description: |
-    The `atlas-<label>` key/value pair corresponds to a custom label the user
-    MAY use to distinguish a different atlas used for similar type of data.
-
-    This entity is only applicable to derivative data.
-  type: string
-  format: label
-ceagent:
-  name: Contrast Enhancing Agent
-  entity: ce
-  description: |
-    The `ce-<label>` key/value can be used to distinguish
-    sequences using different contrast enhanced images.
-    The label is the name of the contrast agent.
-    The key `"ContrastBolusIngredient"` MAY also be added in the JSON file,
-    with the same label.
-  type: string
-  format: label
-chunk:
-  name: Chunk
-  entity: chunk
-  description: |
-    The `chunk-<index>` key/value pair is used to distinguish between different
-    regions, 2D images or 3D volumes files, of the same physical sample with
-    different fields of view acquired in the same imaging experiment.
-  type: string
-  format: index
-density:
-  name: Density
-  entity: den
-  description: |
-    Density of non-parametric surfaces.
-    MUST have a corresponding `Density` metadata field to provide
-    interpretation.
-
-    This entity is only applicable to derivative data.
-  type: string
-  format: label
-description:
-  name: Description
-  entity: desc
-  description: |
-    When necessary to distinguish two files that do not otherwise have a
-    distinguishing entity, the `_desc-<label>` keyword-value SHOULD be used.
-
-    This entity is only applicable to derivative data.
-  type: string
-  format: label
-direction:
-  name: Phase-Encoding Direction
-  entity: dir
-  description: |
-    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.
-  type: string
-  format: label
-echo:
-  name: Echo
-  entity: echo
-  description: |
-    If files belonging to an entity-linked file collection are acquired at different
-    echo times, the `_echo-<index>` key/value pair MUST be used to distinguish
-    individual files.
-    This entity represents the `"EchoTime"` metadata field. Please note that the `<index>`
-    denotes the number/index (in the form of a nonnegative integer), not the
-    `"EchoTime"` value which needs to be stored in the field `"EchoTime"` of the separate
-    JSON file.
-  type: string
-  format: index
-flip:
-  name: Flip Angle
-  entity: flip
-  description: |
-    If files belonging to an entity-linked file collection are acquired at different
-    flip angles, the `_flip-<index>` key/value pair MUST be used to distinguish
-    individual files.
-    This entity represents the `"FlipAngle"` metadata field. 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.
-  type: string
-  format: index
-hemisphere:
-  name: Hemisphere
-  entity: hemi
-  description: |
-    The `hemi-<label>` entity indicates which hemibrain is described by the file.
-    Allowed label values for this entity are `L` and `R`, for the left and right
-    hemibrains, respectively.
-  type: string
-  format: label
-  enum:
-  - "L"
-  - "R"
-inversion:
-  name: Inversion Time
-  entity: inv
-  description: |
-    If files belonging to an entity-linked file collection are acquired at different
-    inversion times, the `_inv-<index>` key/value pair MUST be used to distinguish
-    individual files.
-    This entity represents the `"InversionTime` metadata field. Please note that the `<index>`
-    denotes the number/index (in the form of a nonnegative integer), not the `"InversionTime"`
-    value which needs to be stored in the field `"InversionTime"` of the separate JSON file.
-  type: string
-  format: index
-label:
-  name: Label
-  entity: label
-  description: |
-    Tissue-type label, following a prescribed vocabulary.
-    Applies to binary masks and probabilistic/partial volume segmentations
-    that describe a single tissue type.
-
-    This entity is only applicable to derivative data.
-  type: string
-  format: label
-modality:
-  name: Corresponding Modality
-  entity: mod
-  description: |
-    The `mod-<label>` key/value pair corresponds to modality label for defacing
-    masks, for example, T1w, inplaneT1, referenced by a defacemask image.
-    For example, `sub-01_mod-T1w_defacemask.nii.gz`.
-  type: string
-  format: label
-mtransfer:
-  name: Magnetization Transfer
-  entity: mt
-  description: |
-    If files belonging to an entity-linked file collection are acquired at different
-    magnetization transfer (MT) states, the `_mt-<label>` key/value pair MUST be used to
-    distinguish individual files.
-    This entity represents the `"MTState"` metadata field. Allowed label values for this
-    entity are `on` and `off`, for images acquired in presence and absence of an MT pulse,
-    respectively.
-  type: string
-  enum:
-  - "on"
-  - "off"
-part:
-  name: Part
-  entity: part
-  description: |
-    This entity is used to indicate which component of the complex
-    representation of the MRI signal is represented in voxel data.
-    The `part-<label>` key/value pair is associated with the DICOM Tag
-    `0008, 9208`.
-    Allowed label values for this entity are `phase`, `mag`, `real` and `imag`,
-    which are typically used in `part-mag`/`part-phase` or
-    `part-real`/`part-imag` pairs of files.
-
-    Phase images MAY be in radians or in arbitrary units.
-    The sidecar JSON file MUST include the units of the `phase` image.
-    The possible options are `"rad"` or `"arbitrary"`.
-
-    When there is only a magnitude image of a given type, the `part` key MAY be
-    omitted.
-  type: string
-  enum:
-  - mag
-  - phase
-  - real
-  - imag
-processing:
-  name: Processed (on device)
-  entity: proc
-  description: |
-    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.
-  type: string
-  format: label
-reconstruction:
-  name: Reconstruction
-  entity: rec
-  description: |
-    The `rec-<label>` key/value can be used to distinguish
-    different reconstruction algorithms (for example `MoCo` for the ones using motion
-    correction).
-  type: string
-  format: label
-recording:
-  name: Recording
-  entity: recording
-  description: |
-    More than one continuous recording file can be included (with different
-    sampling frequencies).
-    In such case use different labels.
-    For example: `_recording-contrast`, `_recording-saturation`.
-  type: string
-  format: label
-resolution:
-  name: Resolution
-  entity: res
-  description: |
-    Resolution of regularly sampled N-dimensional data.
-    MUST have a corresponding `"Resolution"` metadata field to provide
-    interpretation.
-
-    This entity is only applicable to derivative data.
-  type: string
-  format: label
-run:
-  name: Run
-  entity: run
-  description: |
-    If several scans with the same acquisition parameters are acquired in the same session,
-    they MUST be indexed with the [`run-<index>`](../99-appendices/09-entities.md#run) entity:
-    `_run-1`, `_run-2`, `_run-3`, and so on (only nonnegative integers are allowed as
-    run labels).
-
-    If different entities apply,
-    such as a different session indicated by [`ses-<label>`](../99-appendices/09-entities.md#ses),
-    or different acquisition parameters indicated by
-    [`acq-<label>`](../99-appendices/09-entities.md#acq),
-    then `run` is not needed to distinguish the scans and MAY be omitted.
-  type: string
-  format: index
-sample:
-  name: Sample
-  entity: sample
-  description: |
-    A sample pertaining to a subject such as tissue, primary cell
-    or cell-free sample.
-    The `sample-<label>` key/value pair is used to distinguish between different
-    samples from the same subject.
-    The label MUST be unique per subject and is RECOMMENDED to be unique
-    throughout the dataset.
-  type: string
-  format: label
-session:
-  name: Session
-  entity: ses
-  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
-    (for example, training).
-  type: string
-  format: label
-space:
-  name: Space
-  entity: space
-  description: |
-    The space entity can be used to indicate
-    the way in which electrode positions are interpreted
-    (for EEG/MEG/iEEG data) or
-    the spatial reference to which a file has been aligned (for MRI data).
-    The space `<label>` MUST be taken from one of the modality specific lists in
-    [Appendix VIII](../99-appendices/08-coordinate-systems.md).
-    For example for iEEG data, the restricted keywords listed under
-    [iEEG Specific Coordinate Systems](../99-appendices/08-coordinate-systems.md#ieeg-specific-coordinate-systems)
-    are acceptable for `<label>`.
-
-    For EEG/MEG/iEEG data, this entity can be applied to raw data, but
-    for other data types, it is restricted to derivative data.
-  type: string
-  format: label
-split:
-  name: Split
-  entity: split
-  description: |
-    In the case of long data recordings that exceed a file size of 2Gb, the
-    .fif files are conventionally split into multiple parts.
-    Each of these files has an internal pointer to the next file.
-    This is important when renaming these split recordings to the BIDS
-    convention.
-
-    Instead of a simple renaming, files should be read in and saved under their
-    new names with dedicated tools like [MNE-Python](https://mne.tools/),
-    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.
-    If there are multiple parts of a recording and the optional `scans.tsv` is provided,
-    remember to list all files separately in `scans.tsv` and that the entries for the
-    `acq_time` column in `scans.tsv` MUST all be identical, as described in
-    [Scans file](../03-modality-agnostic-files.md#scans-file).
-  type: string
-  format: index
-stain:
-  name: Stain
-  entity: stain
-  description: |
-    The `stain-<label>` key/pair values can be used to distinguish image files
-    from the same sample using different stains or antibodies for contrast enhancement.
-    Stains SHOULD be indicated in the `"SampleStaining"` key in the sidecar JSON file,
-    although the label may be different.
-    Description of antibodies SHOULD also be indicated in `"SamplePrimaryAntibodies"`
-    and/or `"SampleSecondaryAntobodies"` as appropriate.
-  type: string
-  format: label
-subject:
-  name: Subject
-  entity: sub
-  description: |
-    A person or animal participating in the study.
-  type: string
-  format: label
-task:
-  name: Task
-  entity: task
-  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.
-  type: string
-  format: label
-tracer:
-  name: Tracer
-  entity: trc
-  description: |
-    The `trc-<label>` key/value can be used to distinguish
-    sequences using different tracers.
-    The key `"TracerName"` MUST also be included in the associated JSON file,
-    although the label may be different.
-  type: string
-  format: label
diff --git a/dandi/support/bids/schemadata/1.7.0+012+dandi001/objects/metadata.yaml b/dandi/support/bids/schemadata/1.7.0+012+dandi001/objects/metadata.yaml
deleted file mode 100644
index 8a010bb03..000000000
--- a/dandi/support/bids/schemadata/1.7.0+012+dandi001/objects/metadata.yaml
+++ /dev/null
@@ -1,2994 +0,0 @@
----
-# This file defines valid BIDS metadata fields.
-# These definitions include the field names, their descriptions, and valid values.
-# This file **does not** define how and when metadata fields can be used with a given file.
-Acknowledgements:
-  name: Acknowledgements
-  description: |
-    Text acknowledging contributions of individuals or institutions beyond
-    those listed in Authors or Funding.
-  type: string
-AcquisitionDuration:
-  name: AcquisitionDuration
-  description: |
-    Duration (in seconds) of volume acquisition.
-    Corresponds to DICOM Tag 0018, 9073 `Acquisition Duration`.
-    This field is mutually exclusive with `"RepetitionTime"`.
-  type: number
-  exclusiveMinimum: 0
-  unit: s
-AcquisitionMode:
-  name: AcquisitionMode
-  description: |
-    Type of acquisition of the PET data (for example, `"list mode"`).
-  type: string
-AcquisitionVoxelSize:
-  name: AcquisitionVoxelSize
-  description: |
-    An array of numbers with a length of 3, in millimeters.
-    This parameter denotes the original acquisition voxel size,
-    excluding any inter-slice gaps and before any interpolation or resampling
-    within reconstruction or image processing.
-    Any point spread function effects, for example due to T2-blurring,
-    that would decrease the effective resolution are not considered here.
-  type: array
-  minItems: 3
-  maxItems: 3
-  items:
-    type: number
-    exclusiveMinimum: 0
-    unit: mm
-Anaesthesia:
-  name: Anaesthesia
-  description: |
-    Details of anaesthesia used, if any.
-  type: string
-AnalyticalApproach:
-  name: AnalyticalApproach
-  description: |
-    Methodology or methodologies used to analyse the `"GeneticLevel"`.
-    Values MUST be taken from the
-    [database of Genotypes and Phenotypes
-    (dbGaP)](https://www.ncbi.nlm.nih.gov/gap/advanced)
-    under /Study/Molecular Data Type (for example, SNP Genotypes (Array) or
-    Methylation (CpG).
-  anyOf:
-  - type: string
-  - type: array
-    items:
-      type: string
-AnatomicalLandmarkCoordinateSystem:
-  name: AnatomicalLandmarkCoordinateSystem
-  description: |
-    Defines the coordinate system for the anatomical landmarks.
-    See [Appendix VIII](/99-appendices/08-coordinate-systems.html)
-    for a list of restricted keywords for coordinate systems.
-    If `"Other"`, provide definition of the coordinate system in
-    `"AnatomicalLandmarkCoordinateSystemDescription"`.
-  anyOf:
-  - $ref: _MEGCoordSys
-  - $ref: _EEGCoordSys
-  - $ref: _StandardTemplateCoordSys
-  - $ref: _StandardTemplateDeprecatedCoordSys
-AnatomicalLandmarkCoordinateSystemDescription:
-  name: AnatomicalLandmarkCoordinateSystemDescription
-  description: |
-    Free-form text description of the coordinate system.
-    May also include a link to a documentation page or paper describing the
-    system in greater detail.
-  type: string
-AnatomicalLandmarkCoordinateUnits:
-  name: AnatomicalLandmarkCoordinateUnits
-  description: |
-    Units of the coordinates of `"AnatomicalLandmarkCoordinateSystem"`.
-  type: string
-  enum:
-  - m
-  - mm
-  - cm
-  - n/a
-AnatomicalLandmarkCoordinates:
-  name: AnatomicalLandmarkCoordinates
-  description: |
-    Key:value pairs of the labels and 3-D digitized locations of anatomical landmarks,
-    interpreted following the `"AnatomicalLandmarkCoordinateSystem"`
-    (for example, `{"NAS": [12.7,21.3,13.9], "LPA": [5.2,11.3,9.6],
-    "RPA": [20.2,11.3,9.1]}`.
-    Each array MUST contain three numeric values corresponding to x, y, and z
-    axis of the coordinate system in that exact order.
-  type: object
-  additionalProperties:
-    type: array
-    items:
-      type: number
-    minItems: 3
-    maxItems: 3
-# Redefinition of AnatomicalLandmarkCoordinates for MRI data
-AnatomicalLandmarkCoordinates__mri:
-  name: AnatomicalLandmarkCoordinates
-  description: |
-    Key:value pairs of any number of additional anatomical landmarks and their
-    coordinates in voxel units (where first voxel has index 0,0,0)
-    relative to the associated anatomical MRI
-    (for example, `{"AC": [127,119,149], "PC": [128,93,141],
-    "IH": [131,114,206]}`, or `{"NAS": [127,213,139], "LPA": [52,113,96],
-    "RPA": [202,113,91]}`).
-    Each array MUST contain three numeric values corresponding to x, y, and z
-    axis of the coordinate system in that exact order.
-  type: object
-  additionalProperties:
-    type: array
-    items:
-      type: number
-    minItems: 3
-    maxItems: 3
-ArterialSpinLabelingType:
-  name: ArterialSpinLabelingType
-  description: |
-    The arterial spin labeling type.
-  type: string
-  enum:
-  - CASL
-  - PCASL
-  - PASL
-AssociatedEmptyRoom:
-  name: AssociatedEmptyRoom
-  description: |
-    Relative path in BIDS folder structure to empty-room file associated with
-    the subject's MEG recording.
-    The path needs to use forward slashes instead of backward slashes
-    (for example,
-    "sub-emptyroom/ses-/meg/sub-emptyroom_ses-_task-noise_run-_meg.ds").
-  anyOf:
-  - type: array
-    items:
-      type: string
-      format: dataset_relative
-  - type: string
-    format: dataset_relative
-Atlas:
-  name: Atlas
-  description: |
-    Which atlas (if any) was used to generate the mask.
-  type: string
-AttenuationCorrection:
-  name: AttenuationCorrection
-  description: |
-    Short description of the attenuation correction method used.
-  type: string
-AttenuationCorrectionMethodReference:
-  name: AttenuationCorrectionMethodReference
-  description: |
-    Reference paper for the attenuation correction method used.
-  type: string
-Authors:
-  name: Authors
-  description: |
-    List of individuals who contributed to the creation/curation of the dataset.
-  type: array
-  items:
-    type: string
-B0FieldIdentifier:
-  name: B0FieldIdentifier
-  description: |
-    The presence of this key states that this particular 3D or 4D image MAY be
-    used for fieldmap estimation purposes.
-    Each `"B0FieldIdentifier"` MUST be a unique string within one participant's tree,
-    shared only by the images meant to be used as inputs for the estimation of a
-    particular instance of the *B<sub>0</sub> field* estimation.
-    It is RECOMMENDED to derive this identifier from DICOM Tags, for example,
-    DICOM tag 0018, 1030 `Protocol Name`, or DICOM tag 0018, 0024 `Sequence Name`
-    when the former is not defined (for example, in GE devices.)
-  anyOf:
-  - type: string
-  - type: array
-    items:
-      type: string
-B0FieldSource:
-  name: B0FieldSource
-  description: |
-    At least one existing `"B0FieldIdentifier"` defined by images in the
-    participant's tree.
-    This field states the *B<sub>0</sub> field* estimation designated by the
-    `"B0FieldIdentifier"` that may be used to correct the dataset for distortions
-    caused by B<sub>0</sub> inhomogeneities.
-    `"B0FieldSource"` and `"B0FieldIdentifier"` MAY both be present for images that
-    are used to estimate their own B<sub>0</sub> field, for example, in "pepolar"
-    acquisitions.
-  anyOf:
-  - type: string
-  - type: array
-    items:
-      type: string
-BIDSVersion:
-  name: BIDSVersion
-  description: |
-    The version of the BIDS standard that was used.
-  type: string
-BackgroundSuppression:
-  name: BackgroundSuppression
-  description: |
-    Boolean indicating if background suppression is used.
-  type: boolean
-BackgroundSuppressionNumberPulses:
-  name: BackgroundSuppressionNumberPulses
-  description: |
-    The number of background suppression pulses used.
-    Note that this excludes any effect of background suppression pulses applied
-    before the labeling.
-  type: number
-  minimum: 0
-BackgroundSuppressionPulseTime:
-  name: BackgroundSuppressionPulseTime
-  description: |
-    Array of numbers containing timing, in seconds,
-    of the background suppression pulses with respect to the start of the
-    labeling.
-    In case of multi-PLD with different background suppression pulse times,
-    only the pulse time of the first PLD should be defined.
-  type: array
-  items:
-    type: number
-    minimum: 0
-    unit: s
-BasedOn:
-  name: BasedOn
-  description: |
-    List of files in a file collection to generate the map.
-    Fieldmaps are also listed, if involved in the processing.
-  anyOf:
-  - type: string
-    format: participant_relative
-  - type: array
-    items:
-      type: string
-      format: participant_relative
-BloodDensity:
-  name: BloodDensity
-  description: |
-    Measured blood density. Unit of blood density should be in `"g/mL"`.
-  type: number
-  unit: g/mL
-BodyPart:
-  name: BodyPart
-  description: |
-    Body part of the organ / body region scanned.
-  type: string
-BodyPartDetails:
-  name: BodyPartDetails
-  description: |
-    Additional details about body part or location (for example: `"corpus callosum"`).
-  type: string
-BodyPartDetailsOntology:
-  name: BodyPartDetailsOntology
-  description: |
-    [URI](/02-common-principles.html#uniform-resource-indicator) of ontology used for
-    BodyPartDetails (for example: `"https://www.ebi.ac.uk/ols/ontologies/uberon"`).
-  type: string
-  format: uri
-BolusCutOffDelayTime:
-  name: BolusCutOffDelayTime
-  description: |
-    Duration between the end of the labeling and the start of the bolus cut-off
-    saturation pulse(s), in seconds.
-    This can be a number or array of numbers, of which the values must be
-    non-negative and monotonically increasing, depending on the number of bolus
-    cut-off saturation pulses.
-    For Q2TIPS, only the values for the first and last bolus cut-off saturation
-    pulses are provided.
-    Based on DICOM Tag 0018, 925F `ASL Bolus Cut-off Delay Time`.
-  anyOf:
-  - type: number
-    minimum: 0
-    unit: s
-  - type: array
-    items:
-      type: number
-      unit: s
-      minimum: 0
-BolusCutOffFlag:
-  name: BolusCutOffFlag
-  description: |
-    Boolean indicating if a bolus cut-off technique is used.
-    Corresponds to DICOM Tag 0018, 925C `ASL Bolus Cut-off Flag`.
-  type: boolean
-BolusCutOffTechnique:
-  name: BolusCutOffTechnique
-  description: |
-    Name of the technique used, for example `"Q2TIPS"`, `"QUIPSS"`, `"QUIPSSII"`.
-    Corresponds to DICOM Tag 0018, 925E `ASL Bolus Cut-off Technique`.
-  type: string
-BrainLocation:
-  name: BrainLocation
-  description: |
-    Refers to the location in space of the `"TissueOrigin"`.
-    Values may be an MNI coordinate,
-    a label taken from the
-    [Allen Brain Atlas](https://atlas.brain-map.org/atlas?atlas=265297125&plate=\
-    112360888&structure=4392&x=40348.15104166667&y=46928.75&zoom=-7&resolution=\
-    206.60&z=3),
-    or layer to refer to layer-specific gene expression,
-    which can also tie up with laminar fMRI.
-  type: string
-CASLType:
-  name: CASLType
-  description: |
-    Describes if a separate coil is used for labeling.
-  type: string
-  enum:
-  - single-coil
-  - double-coil
-CapManufacturer:
-  name: CapManufacturer
-  description: |
-    Name of the cap manufacturer (for example, `"EasyCap"`).
-  type: string
-CapManufacturersModelName:
-  name: CapManufacturersModelName
-  description: |
-    Manufacturer's designation of the EEG cap model
-    (for example, `"actiCAP 64 Ch Standard-2"`).
-  type: string
-CellType:
-  name: CellType
-  description: |
-    Describes the type of cell analyzed.
-    Values SHOULD come from the
-    [cell ontology](http://obofoundry.org/ontology/cl.html).
-  type: string
-ChunkTransformationMatrix:
-  name: ChunkTransformationMatrix
-  description: |
-    3x3 or 4x4 affine transformation matrix describing spatial chunk transformation,
-    for 2D and 3D respectively (for examples: `[[2, 0, 0], [0, 3, 0], [0, 0, 1]]`
-    in 2D for 2x and 3x scaling along the first and second axis respectively; or
-    `[[1, 0, 0, 0], [0, 2, 0, 0], [0, 0, 3, 0], [0, 0, 0, 1]]` in 3D for 2x and 3x
-    scaling along the second and third axis respectively).
-    Note that non-spatial dimensions like time and channel are not included in the
-    transformation matrix.
-  anyOf:
-  - type: array
-    minItems: 3
-    maxItems: 3
-    items:
-      type: array
-      minItems: 3
-      maxItems: 3
-      items:
-        type: number
-  - type: array
-    minItems: 4
-    maxItems: 4
-    items:
-      type: array
-      minItems: 4
-      maxItems: 4
-      items:
-        type: number
-ChunkTransformationMatrixAxis:
-  name: ChunkTransformationMatrixAxis
-  description: |
-    Describe the axis of the ChunkTransformationMatrix
-    (for examples: `["X", "Y"]` or `["Z", "Y", "X"]`).
-  type: array
-  items:
-    type: string
-    minItems: 2
-    maxItems: 3
-Code:
-  name: Code
-  description: |
-    [URI](/02-common-principles.html#uniform-resource-indicator)
-    of the code used to present the stimuli.
-    Persistent identifiers such as DOIs are preferred.
-    If multiple versions of code may be hosted at the same location,
-    revision-specific URIs are recommended.
-  type: string
-  format: uri
-CogAtlasID:
-  name: CogAtlasID
-  description: |
-    [URI](/02-common-principles.html#uniform-resource-indicator)
-    of the corresponding [Cognitive Atlas](https://www.cognitiveatlas.org/)
-    Task term.
-  type: string
-  format: uri
-CogPOID:
-  name: CogPOID
-  description: |
-    [URI](/02-common-principles.html#uniform-resource-indicator)
-    of the corresponding [CogPO](http://www.cogpo.org/) term.
-  type: string
-  format: uri
-CoilCombinationMethod:
-  name: CoilCombinationMethod
-  description: |
-    Almost all fMRI studies using phased-array coils use root-sum-of-squares
-    (rSOS) combination, but other methods exist.
-    The image reconstruction is changed by the coil combination method
-    (as for the matrix coil mode above),
-    so anything non-standard should be reported.
-  type: string
-Columns:
-  name: Columns
-  description: |
-    Names of columns in file.
-  type: array
-  items:
-    type: string
-ContinuousHeadLocalization:
-  name: ContinuousHeadLocalization
-  description: |
-    `true` or `false` value indicating whether continuous head localisation
-    was performed.
-  type: boolean
-ContrastBolusIngredient:
-  name: ContrastBolusIngredient
-  description: |
-    Active ingredient of agent.
-    Corresponds to DICOM Tag 0018, 1048 `Contrast/Bolus Ingredient`.
-  type: string
-  enum:
-  - IODINE
-  - GADOLINIUM
-  - CARBON DIOXIDE
-  - BARIUM
-  - XENON
-DCOffsetCorrection:
-  name: DCOffsetCorrection
-  description: |
-    A description of the method (if any) used to correct for a DC offset.
-    If the method used was subtracting the mean value for each channel,
-    use "mean".
-  type: string
-DatasetDOI:
-  name: DatasetDOI
-  description: |
-    The Digital Object Identifier of the dataset (not the corresponding paper).
-    DOIs SHOULD be expressed as a valid
-    [URI](/02-common-principles.html#uniform-resource-indicator);
-    bare DOIs such as `10.0.2.3/dfjj.10` are
-    [DEPRECATED](/02-common-principles.html#definitions).
-  type: string
-  format: uri
-DatasetType:
-  name: DatasetType
-  description: |
-    The interpretation of the dataset.
-    For backwards compatibility, the default value is `"raw"`.
-  type: string
-  enum:
-  - raw
-  - derivative
-DecayCorrectionFactor:
-  name: DecayCorrectionFactor
-  description: |
-    Decay correction factor for each frame.
-  type: array
-  items:
-    type: number
-DelayAfterTrigger:
-  name: DelayAfterTrigger
-  description: |
-    Duration (in seconds) from trigger delivery to scan onset.
-    This delay is commonly caused by adjustments and loading times.
-    This specification is entirely independent of
-    `"NumberOfVolumesDiscardedByScanner"` or `"NumberOfVolumesDiscardedByUser"`,
-    as the delay precedes the acquisition.
-  type: number
-  unit: s
-DelayTime:
-  name: DelayTime
-  description: |
-    User specified time (in seconds) to delay the acquisition of data for the
-    following volume.
-    If the field is not present it is assumed to be set to zero.
-    Corresponds to Siemens CSA header field `lDelayTimeInTR`.
-    This field is REQUIRED for sparse sequences using the `"RepetitionTime"` field
-    that do not have the `"SliceTiming"` field set to allowed for accurate
-    calculation of "acquisition time".
-    This field is mutually exclusive with `"VolumeTiming"`.
-  type: number
-  unit: s
-Density:
-  name: Density
-  description: |
-    Specifies the interpretation of the density keyword.
-    If an object is used, then the keys should be values for the ``den`` entity
-    and values should be descriptions of those ``den`` values.
-  anyOf:
-  - type: string
-  - type: object
-    additionalProperties:
-      type: string
-Derivative:
-  name: Derivative
-  description: |
-    Indicates that values in the corresponding column are transformations of values
-    from other columns (for example a summary score based on a subset of items in a
-    questionnaire).
-  type: boolean
-Description:
-  name: Description
-  description: |
-    Free-form natural language description.
-  type: string
-DeviceSerialNumber:
-  name: DeviceSerialNumber
-  description: |
-    The serial number of the equipment that produced the measurements.
-    A pseudonym can also be used to prevent the equipment from being
-    identifiable, so long as each pseudonym is unique within the dataset.
-  type: string
-DewarPosition:
-  name: DewarPosition
-  description: |
-    Position of the dewar during the MEG scan:
-    `"upright"`, `"supine"` or `"degrees"` of angle from vertical:
-    for example on CTF systems, `"upright=15°, supine=90°"`.
-  type: string
-DigitizedHeadPoints:
-  name: DigitizedHeadPoints
-  description: |
-    `true` or `false` value indicating whether head points outlining the
-    scalp/face surface are contained within this recording.
-  type: boolean
-DigitizedHeadPointsCoordinateSystem:
-  name: DigitizedHeadPointsCoordinateSystem
-  description: |
-    Defines the coordinate system for the digitized head points.
-    See
-    [Appendix VIII](/99-appendices/08-coordinate-systems.html)
-    for a list of restricted keywords for coordinate systems.
-    If `"Other"`, provide definition of the coordinate system in
-    `"DigitizedHeadPointsCoordinateSystemDescription"`.
-  anyOf:
-  - $ref: _MEGCoordSys
-  - $ref: _EEGCoordSys
-  - $ref: _StandardTemplateCoordSys
-  - $ref: _StandardTemplateDeprecatedCoordSys
-DigitizedHeadPointsCoordinateSystemDescription:
-  name: DigitizedHeadPointsCoordinateSystemDescription
-  description: |
-    Free-form text description of the coordinate system.
-    May also include a link to a documentation page or paper describing the
-    system in greater detail.
-  type: string
-DigitizedHeadPointsCoordinateUnits:
-  name: DigitizedHeadPointsCoordinateUnits
-  description: |
-    Units of the coordinates of `"DigitizedHeadPointsCoordinateSystem"`.
-  type: string
-  enum:
-  - m
-  - mm
-  - cm
-  - n/a
-DigitizedLandmarks:
-  name: DigitizedLandmarks
-  description: |
-    `true` or `false` value indicating whether anatomical landmark points
-    (fiducials) are contained within this recording.
-  type: boolean
-DispersionConstant:
-  name: DispersionConstant
-  description: |
-    External dispersion time constant resulting from tubing in default unit
-    seconds.
-  type: number
-  unit: s
-DispersionCorrected:
-  name: DispersionCorrected
-  description: |
-    Boolean flag specifying whether the blood data have been dispersion-corrected.
-    NOTE: not customary for manual samples, and hence should be set to `false`.
-  type: boolean
-DoseCalibrationFactor:
-  name: DoseCalibrationFactor
-  description: |
-    Multiplication factor used to transform raw data (in counts/sec) to meaningful unit (Bq/ml).
-    Corresponds to DICOM Tag 0054, 1322 `Dose Calibration Factor`.
-  type: number
-DwellTime:
-  name: DwellTime
-  description: |
-    Actual dwell time (in seconds) of the receiver per point in the readout
-    direction, including any oversampling.
-    For Siemens, this corresponds to DICOM field 0019, 1018 (in ns).
-    This value is necessary for the optional readout distortion correction of
-    anatomicals in the HCP Pipelines.
-    It also usefully provides a handle on the readout bandwidth,
-    which isn't captured in the other metadata tags.
-    Not to be confused with `"EffectiveEchoSpacing"`, and the frequent mislabeling
-    of echo spacing (which is spacing in the phase encoding direction) as
-    "dwell time" (which is spacing in the readout direction).
-  type: number
-  unit: s
-ECGChannelCount:
-  name: ECGChannelCount
-  description: |
-    Number of ECG channels.
-  type: integer
-  minimum: 0
-ECOGChannelCount:
-  name: ECOGChannelCount
-  description: |
-    Number of ECoG channels.
-  type: integer
-  minimum: 0
-EEGChannelCount:
-  name: EEGChannelCount
-  description: |
-    Number of EEG channels recorded simultaneously (for example, `21`).
-  type: integer
-  minimum: 0
-EEGCoordinateSystem:
-  name: EEGCoordinateSystem
-  description: |
-    Defines the coordinate system for the EEG sensors.
-
-    See
-    [Appendix VIII](/99-appendices/08-coordinate-systems.html)
-    for a list of restricted keywords for coordinate systems.
-    If `"Other"`, provide definition of the coordinate system in
-    `EEGCoordinateSystemDescription`.
-  anyOf:
-  - $ref: _MEGCoordSys
-  - $ref: _EEGCoordSys
-  - $ref: _StandardTemplateCoordSys
-  - $ref: _StandardTemplateDeprecatedCoordSys
-EEGCoordinateSystemDescription:
-  name: EEGCoordinateSystemDescription
-  description: |
-    Free-form text description of the coordinate system.
-    May also include a link to a documentation page or paper describing the
-    system in greater detail.
-  type: string
-EEGCoordinateUnits:
-  name: EEGCoordinateUnits
-  description: |
-    Units of the coordinates of `EEGCoordinateSystem`.
-  type: string
-  enum:
-  - m
-  - mm
-  - cm
-  - n/a
-EEGGround:
-  name: EEGGround
-  description: |
-    Description of the location of the ground electrode
-    (for example, `"placed on right mastoid (M2)"`).
-  type: string
-EEGPlacementScheme:
-  name: EEGPlacementScheme
-  description: |
-    Placement scheme of EEG electrodes.
-    Either the name of a standardized placement system (for example, `"10-20"`)
-    or a list of standardized electrode names (for example, `["Cz", "Pz"]`).
-  type: string
-EEGReference:
-  name: EEGReference
-  description: |
-    General description of the reference scheme used and (when applicable) of
-    location of the reference electrode in the raw recordings
-    (for example, `"left mastoid"`, `"Cz"`, `"CMS"`).
-    If different channels have a different reference,
-    this field should have a general description and the channel specific
-    reference should be defined in the `channels.tsv` file.
-  type: string
-EMGChannelCount:
-  name: EMGChannelCount
-  description: |
-    Number of EMG channels.
-  type: integer
-  minimum: 0
-EOGChannelCount:
-  name: EOGChannelCount
-  description: |
-    Number of EOG channels.
-  type: integer
-  minimum: 0
-EchoTime:
-  name: EchoTime
-  description: |
-    The echo time (TE) for the acquisition, specified in seconds.
-    Corresponds to DICOM Tag 0018, 0081 `Echo Time`
-    (please note that the DICOM term is in milliseconds not seconds).
-    The data type number may apply to files from any MRI modality concerned with
-    a single value for this field, or to the files in a
-    [file collection](/99-appendices/10-file-collections.html)
-    where the value of this field is iterated using the
-    [echo entity](/99-appendices/09-entities.html#echo).
-    The data type array provides a value for each volume in a 4D dataset and
-    should only be used when the volume timing is critical for interpretation
-    of the data, such as in
-    [ASL](/04-modality-specific-files/01-magnetic-resonance-imaging-data.html#\
-    arterial-spin-labeling-perfusion-data)
-    or variable echo time fMRI sequences.
-  anyOf:
-  - type: number
-    unit: s
-    exclusiveMinimum: 0
-  - type: array
-    items:
-      type: number
-      unit: s
-      exclusiveMinimum: 0
-EchoTime1:
-  name: EchoTime1
-  description: |
-    The time (in seconds) when the first (shorter) echo occurs.
-  type: number
-  unit: s
-  exclusiveMinimum: 0
-EchoTime2:
-  name: EchoTime2
-  description: |
-    The time (in seconds) when the second (longer) echo occurs.
-  type: number
-  unit: s
-  exclusiveMinimum: 0
-# Redefinition of EchoTime for fieldmap data
-EchoTime__fmap:
-  name: EchoTime
-  description: |
-    The time (in seconds) when the echo corresponding to this map was acquired.
-  type: number
-  unit: s
-  exclusiveMinimum: 0
-EffectiveEchoSpacing:
-  name: EffectiveEchoSpacing
-  description: |
-    The "effective" sampling interval, specified in seconds,
-    between lines in the phase-encoding direction,
-    defined based on the size of the reconstructed image in the phase direction.
-    It is frequently, but incorrectly, referred to as "dwell time"
-    (see the `"DwellTime"` parameter for actual dwell time).
-    It is required for unwarping distortions using field maps.
-    Note that beyond just in-plane acceleration,
-    a variety of other manipulations to the phase encoding need to be accounted
-    for properly, including partial fourier, phase oversampling,
-    phase resolution, phase field-of-view and interpolation.
-  type: number
-  exclusiveMinimum: 0
-  unit: s
-ElectricalStimulation:
-  name: ElectricalStimulation
-  description: |
-    Boolean field to specify if electrical stimulation was done during the
-    recording (options are `true` or `false`). Parameters for event-like
-    stimulation should be specified in the `events.tsv` file.
-  type: boolean
-ElectricalStimulationParameters:
-  name: ElectricalStimulationParameters
-  description: |
-    Free form description of stimulation parameters, such as frequency or shape.
-    Specific onsets can be specified in the events.tsv file.
-    Specific shapes can be described here in freeform text.
-  type: string
-ElectrodeManufacturer:
-  name: ElectrodeManufacturer
-  description: |
-    Can be used if all electrodes are of the same manufacturer
-    (for example, `"AD-TECH"`, `"DIXI"`).
-    If electrodes of different manufacturers are used,
-    please use the corresponding table in the `_electrodes.tsv` file.
-  type: string
-ElectrodeManufacturersModelName:
-  name: ElectrodeManufacturersModelName
-  description: |
-    If different electrode types are used,
-    please use the corresponding table in the `_electrodes.tsv` file.
-  type: string
-EpochLength:
-  name: EpochLength
-  description: |
-    Duration of individual epochs in seconds (for example, `1`)
-    in case of epoched data.
-    If recording was continuous or discontinuous, leave out the field.
-  type: number
-  minimum: 0
-EstimationAlgorithm:
-  name: EstimationAlgorithm
-  description: |
-    Type of algorithm used to perform fitting
-    (for example, `"linear"`, `"non-linear"`, `"LM"` and such).
-  type: string
-EstimationReference:
-  name: EstimationReference
-  description: |
-    Reference to the study/studies on which the implementation is based.
-  type: string
-EthicsApprovals:
-  name: EthicsApprovals
-  description: |
-    List of ethics committee approvals of the research protocols and/or
-    protocol identifiers.
-  type: array
-  items:
-    type: string
-FiducialsCoordinateSystem:
-  name: FiducialsCoordinateSystem
-  description: |
-    Defines the coordinate system for the fiducials.
-    Preferably the same as the `"EEGCoordinateSystem"`.
-    See
-    [Appendix VIII](/99-appendices/08-coordinate-systems.html)
-    for a list of restricted keywords for coordinate systems.
-    If `"Other"`, provide definition of the coordinate system in
-    `"FiducialsCoordinateSystemDescription"`.
-  anyOf:
-  - $ref: _MEGCoordSys
-  - $ref: _EEGCoordSys
-  - $ref: _StandardTemplateCoordSys
-  - $ref: _StandardTemplateDeprecatedCoordSys
-FiducialsCoordinateSystemDescription:
-  name: FiducialsCoordinateSystemDescription
-  description: |
-    Free-form text description of the coordinate system.
-    May also include a link to a documentation page or paper describing the
-    system in greater detail.
-  type: string
-FiducialsCoordinateUnits:
-  name: FiducialsCoordinateUnits
-  description: |
-    Units in which the coordinates that are  listed in the field
-    `"FiducialsCoordinateSystem"` are represented.
-  type: string
-  enum:
-  - m
-  - mm
-  - cm
-  - n/a
-FiducialsCoordinates:
-  name: FiducialsCoordinates
-  description: |
-    Key:value pairs of the labels and 3-D digitized position of anatomical
-    landmarks, interpreted following the `"FiducialsCoordinateSystem"`
-    (for example, `{"NAS": [12.7,21.3,13.9], "LPA": [5.2,11.3,9.6],
-    "RPA": [20.2,11.3,9.1]}`).
-    Each array MUST contain three numeric values corresponding to x, y, and z
-    axis of the coordinate system in that exact order.
-  type: object
-  additionalProperties:
-    type: array
-    items:
-      type: number
-    minItems: 3
-    maxItems: 3
-FiducialsDescription:
-  name: FiducialsDescription
-  description: |
-    Free-form text description of how the fiducials such as vitamin-E capsules
-    were placed relative to anatomical landmarks,
-    and how the position of the fiducials were measured
-    (for example, `"both with Polhemus and with T1w MRI"`).
-  type: string
-FlipAngle:
-  name: FlipAngle
-  description: |
-    Flip angle (FA) for the acquisition, specified in degrees.
-    Corresponds to: DICOM Tag 0018, 1314 `Flip Angle`.
-    The data type number may apply to files from any MRI modality concerned with
-    a single value for this field, or to the files in a
-    [file collection](/99-appendices/10-file-collections.html)
-    where the value of this field is iterated using the
-    [flip entity](/99-appendices/09-entities.html#flip).
-    The data type array provides a value for each volume in a 4D dataset and
-    should only be used when the volume timing is critical for interpretation of
-    the data, such as in
-    [ASL](/04-modality-specific-files/01-magnetic-resonance-imaging-data.html#\
-    arterial-spin-labeling-perfusion-data)
-    or variable flip angle fMRI sequences.
-  anyOf:
-  - type: number
-    unit: degree
-    exclusiveMinimum: 0
-    maximum: 360
-  - type: array
-    items:
-      type: number
-      unit: degree
-      exclusiveMinimum: 0
-      maximum: 360
-FrameDuration:
-  name: FrameDuration
-  description: |
-    Time duration of each frame in default unit seconds.
-    This corresponds to DICOM Tag 0018, 1242 `Actual Frame Duration` converted
-    to seconds.
-  type: array
-  items:
-    type: number
-  unit: s
-FrameTimesStart:
-  name: FrameTimesStart
-  description: |
-    Start times for all frames relative to `"TimeZero"` in default unit seconds.
-  type: array
-  items:
-    type: number
-  unit: s
-Funding:
-  name: Funding
-  description: |
-    List of sources of funding (grant numbers).
-  type: array
-  items:
-    type: string
-GeneratedBy:
-  name: GeneratedBy
-  description: |
-    Used to specify provenance of the dataset.
-  type: array
-  minItems: 1
-  items:
-    type: object
-    properties:
-      Name:
-        type: string
-      Version:
-        type: string
-      Description:
-        type: string
-      CodeURL:
-        type: string
-        format: uri
-      Container:
-        type: object
-        properties:
-          Type:
-            type: string
-          Tag:
-            type: string
-          URI:
-            type: string
-            format: uri
-GeneticLevel:
-  name: GeneticLevel
-  description: |
-    Describes the level of analysis.
-    Values MUST be one of `"Genetic"`, `"Genomic"`, `"Epigenomic"`,
-    `"Transcriptomic"`, `"Metabolomic"`, or `"Proteomic"`.
-  anyOf:
-  - $ref: _GeneticLevelEnum
-  - type: array
-    items:
-      $ref: _GeneticLevelEnum
-Genetics.Database:
-  name: Genetics.Database
-  description: |
-    [URI](/02-common-principles.html#uniform-resource-indicator)
-    of database where the dataset is hosted.
-  type: string
-  format: uri
-Genetics.Dataset:
-  name: Genetics.Dataset
-  description: |
-    [URI](/02-common-principles.html#uniform-resource-indicator)
-    where data can be retrieved.
-  type: string
-  format: uri
-Genetics.Descriptors:
-  name: Genetics.Descriptors
-  description: |
-    List of relevant descriptors (for example, journal articles) for dataset
-    using a valid
-    [URI](/02-common-principles.html#uniform-resource-indicator)
-    when possible.
-  anyOf:
-  - type: string
-  - type: array
-    items:
-      type: string
-Genetics:
-  name: Genetics
-  description: |
-    An object containing information about the genetics descriptor.
-  type: object
-  properties:
-    Database:
-      $ref: Genetics.Database
-    Dataset:
-      $ref: Genetics.Dataset
-    Descriptors:
-      $ref: Genetics.Descriptors
-GradientSetType:
-  name: GradientSetType
-  description: |
-    It should be possible to infer the gradient coil from the scanner model.
-    If not, for example because of a custom upgrade or use of a gradient
-    insert set, then the specifications of the actual gradient coil should be
-    reported independently.
-  type: string
-HED:
-  name: HED
-  description: |
-    Hierarchical Event Descriptor (HED) information,
-    see: [Appendix III](/99-appendices/03-hed.html) for details.
-  anyOf:
-  - type: string
-  - type: object
-    additionalProperties:
-      type: string
-HEDVersion:
-  name: HEDVersion
-  description: |
-    If HED tags are used:
-    The version of the HED schema used to validate HED tags for study.
-  type: string
-Haematocrit:
-  name: Haematocrit
-  description: |
-    Measured haematocrit, meaning the volume of erythrocytes divided by the
-    volume of whole blood.
-  type: number
-HardcopyDeviceSoftwareVersion:
-  name: HardcopyDeviceSoftwareVersion
-  description: |
-    Manufacturer's designation of the software of the device that created this
-    Hardcopy Image (the printer).
-    Corresponds to DICOM Tag 0018, 101A `Hardcopy Device Software Version`.
-  type: string
-HardwareFilters:
-  name: HardwareFilters
-  description: |
-    Object of temporal hardware filters applied, or `"n/a"` if the data is not
-    available. Each key:value pair in the JSON object is a name of the filter and
-    an object in which its parameters are defined as key:value pairs.
-    For example, `{"Highpass RC filter": {"Half amplitude cutoff (Hz)":
-    0.0159, "Roll-off": "6dB/Octave"}}`.
-  anyOf:
-  - type: object
-    additionalProperties:
-      type: object
-  - type: string
-    enum:
-    - n/a
-HeadCircumference:
-  name: HeadCircumference
-  description: |
-    Circumference of the participant's head, expressed in cm (for example, `58`).
-  type: number
-  exclusiveMinimum: 0
-  unit: cm
-HeadCoilCoordinateSystem:
-  name: HeadCoilCoordinateSystem
-  description: |
-    Defines the coordinate system for the head coils.
-    See
-    [Appendix VIII](/99-appendices/08-coordinate-systems.html)
-    for a list of restricted keywords for coordinate systems.
-    If `"Other"`, provide definition of the coordinate system in
-    `HeadCoilCoordinateSystemDescription`.
-  anyOf:
-  - $ref: _MEGCoordSys
-  - $ref: _EEGCoordSys
-  - $ref: _StandardTemplateCoordSys
-  - $ref: _StandardTemplateDeprecatedCoordSys
-HeadCoilCoordinateSystemDescription:
-  name: HeadCoilCoordinateSystemDescription
-  description: |
-    Free-form text description of the coordinate system.
-    May also include a link to a documentation page or paper describing the system in greater detail.
-  type: string
-HeadCoilCoordinateUnits:
-  name: HeadCoilCoordinateUnits
-  description: |
-    Units of the coordinates of `HeadCoilCoordinateSystem`.
-  type: string
-  enum:
-  - m
-  - mm
-  - cm
-  - n/a
-HeadCoilCoordinates:
-  name: HeadCoilCoordinates
-  description: |
-    Key:value pairs describing head localization coil labels and their
-    coordinates, interpreted following the `HeadCoilCoordinateSystem`
-    (for example, `{"NAS": [12.7,21.3,13.9], "LPA": [5.2,11.3,9.6],
-    "RPA": [20.2,11.3,9.1]}`).
-    Note that coils are not always placed at locations that have a known
-    anatomical name (for example, for Elekta, Yokogawa systems); in that case
-    generic labels can be used
-    (for example, `{"coil1": [12.2,21.3,12.3], "coil2": [6.7,12.3,8.6],
-    "coil3": [21.9,11.0,8.1]}`).
-    Each array MUST contain three numeric values corresponding to x, y, and z
-    axis of the coordinate system in that exact order.
-  type: object
-  additionalProperties:
-    type: array
-    items:
-      type: number
-    minItems: 3
-    maxItems: 3
-HeadCoilFrequency:
-  name: HeadCoilFrequency
-  description: |
-    List of frequencies (in Hz) used by the head localisation coils
-    ('HLC' in CTF systems, 'HPI' in Elekta, 'COH' in BTi/4D)
-    that track the subject's head position in the MEG helmet
-    (for example, `[293, 307, 314, 321]`).
-  anyOf:
-  - type: number
-    unit: Hz
-  - type: array
-    items:
-      type: number
-      unit: Hz
-HowToAcknowledge:
-  name: HowToAcknowledge
-  description: |
-    Text containing instructions on how researchers using this dataset should
-    acknowledge the original authors.
-    This field can also be used to define a publication that should be cited in
-    publications that use the dataset.
-  type: string
-ImageAcquisitionProtocol:
-  name: ImageAcquisitionProtocol
-  description: |
-    Description of the image acquisition protocol or
-    [URI](/02-common-principles.html#uniform-resource-indicator)
-    (for example from [protocols.io](https://www.protocols.io/)).
-  type: string
-ImageDecayCorrected:
-  name: ImageDecayCorrected
-  description: |
-    Boolean flag specifying whether the image data have been decay-corrected.
-  type: boolean
-ImageDecayCorrectionTime:
-  name: ImageDecayCorrectionTime
-  description: |
-    Point in time from which the decay correction was applied with respect to
-    `"TimeZero"` in the default unit seconds.
-  type: number
-  unit: s
-Immersion:
-  name: Immersion
-  description: |
-    Lens immersion medium. If the file format is OME-TIFF, the value MUST be consistent
-    with the `Immersion` OME metadata field.
-  type: string
-InfusionRadioactivity:
-  name: InfusionRadioactivity
-  description: |
-    Amount of radioactivity infused into the patient.
-    This value must be less than or equal to the total injected radioactivity
-    (`"InjectedRadioactivity"`).
-    Units should be the same as `"InjectedRadioactivityUnits"`.
-  type: number
-InfusionSpeed:
-  name: InfusionSpeed
-  description: |
-    If given, infusion speed.
-  type: number
-InfusionSpeedUnits:
-  name: InfusionSpeedUnits
-  description: |
-    Unit of infusion speed (for example, `"mL/s"`).
-  type: string
-  format: unit
-InfusionStart:
-  name: InfusionStart
-  description: |
-    Time of start of infusion with respect to `"TimeZero"` in the default unit
-    seconds.
-  type: number
-  unit: s
-InjectedMass:
-  name: InjectedMass
-  description: |
-    Total mass of radiolabeled compound injected into subject (for example, `10`).
-    This can be derived as the ratio of the `"InjectedRadioactivity"` and
-    `"MolarRadioactivity"`.
-    **For those tracers in which injected mass is not available (for example FDG)
-    can be set to `"n/a"`)**.
-  anyOf:
-  - type: number
-  - type: string
-    enum:
-    - n/a
-InjectedMassPerWeight:
-  name: InjectedMassPerWeight
-  description: |
-    Injected mass per kilogram bodyweight.
-  type: number
-InjectedMassPerWeightUnits:
-  name: InjectedMassPerWeightUnits
-  description: |
-    Unit format of the injected mass per kilogram bodyweight
-    (for example, `"ug/kg"`).
-  type: string
-  format: unit
-InjectedMassUnits:
-  name: InjectedMassUnits
-  description: |
-    Unit format of the mass of compound injected (for example, `"ug"` or
-    `"umol"`).
-    **Note this is not required for an FDG acquisition, since it is not available,
-    and SHOULD be set to `"n/a"`**.
-  anyOf:
-  - type: string
-    format: unit
-  - type: string
-    enum:
-    - n/a
-InjectedRadioactivity:
-  name: InjectedRadioactivity
-  description: |
-    Total amount of radioactivity injected into the patient (for example, `400`).
-    For bolus-infusion experiments, this value should be the sum of all injected
-    radioactivity originating from both bolus and infusion.
-    Corresponds to DICOM Tag 0018, 1074 `Radionuclide Total Dose`.
-  type: number
-InjectedRadioactivityUnits:
-  name: InjectedRadioactivityUnits
-  description: |
-    Unit format of the specified injected radioactivity (for example, `"MBq"`).
-  type: string
-  format: unit
-InjectedVolume:
-  name: InjectedVolume
-  description: |
-    Injected volume of the radiotracer in the unit `"mL"`.
-  type: number
-  unit: mL
-InjectionEnd:
-  name: InjectionEnd
-  description: |
-    Time of end of injection with respect to `"TimeZero"` in the default unit
-    seconds.
-  type: number
-  unit: s
-InjectionStart:
-  name: InjectionStart
-  description: |
-    Time of start of injection with respect to `"TimeZero"` in the default unit
-    seconds.
-    This corresponds to DICOM Tag 0018, 1042 `Contrast/Bolus Start Time`
-    converted to seconds relative to `"TimeZero"`.
-  type: number
-  unit: s
-InstitutionAddress:
-  name: InstitutionAddress
-  description: |
-    The address of the institution in charge of the equipment that produced the
-    measurements.
-  type: string
-InstitutionName:
-  name: InstitutionName
-  description: |
-    The name of the institution in charge of the equipment that produced the
-    measurements.
-  type: string
-InstitutionalDepartmentName:
-  name: InstitutionalDepartmentName
-  description: |
-    The department in the institution in charge of the equipment that produced
-    the measurements.
-  type: string
-Instructions:
-  name: Instructions
-  description: |
-    Text of the instructions given to participants before the recording.
-  type: string
-IntendedFor:
-  name: IntendedFor
-  description: |
-    The paths to files for which the associated file is intended to be used.
-    Contains one or more filenames with paths relative to the participant
-    subfolder.
-    Paths need to use forward slashes instead of backward slashes,
-    regardless of operating system.
-  anyOf:
-  - type: string
-    format: participant_relative
-  - type: array
-    items:
-      type: string
-      format: participant_relative
-InversionTime:
-  name: InversionTime
-  description: |
-    The inversion time (TI) for the acquisition, specified in seconds.
-    Inversion time is the time after the middle of inverting RF pulse to middle
-    of excitation pulse to detect the amount of longitudinal magnetization.
-    Corresponds to DICOM Tag 0018, 0082 `Inversion Time`
-    (please note that the DICOM term is in milliseconds not seconds).
-  type: number
-  unit: s
-  exclusiveMinimum: 0
-LabelingDistance:
-  name: LabelingDistance
-  description: |
-    Distance from the center of the imaging slab to the center of the labeling
-    plane (`(P)CASL`) or the leading edge of the labeling slab (`PASL`),
-    in millimeters.
-    If the labeling is performed inferior to the isocenter,
-    this number should be negative.
-    Based on DICOM macro C.8.13.5.14.
-  type: number
-  unit: mm
-LabelingDuration:
-  name: LabelingDuration
-  description: |
-    Total duration of the labeling pulse train, in seconds,
-    corresponding to the temporal width of the labeling bolus for
-    `"PCASL"` or `"CASL"`.
-    In case all control-label volumes (or deltam or CBF) have the same
-    `LabelingDuration`, a scalar must be specified.
-    In case the control-label volumes (or deltam or cbf) have a different
-    `"LabelingDuration"`, an array of numbers must be specified,
-    for which any `m0scan` in the timeseries has a `"LabelingDuration"` of zero.
-    In case an array of numbers is provided,
-    its length should be equal to the number of volumes specified in
-    `*_aslcontext.tsv`.
-    Corresponds to DICOM Tag 0018, 9258 `ASL Pulse Train Duration`.
-  anyOf:
-  - type: number
-    minimum: 0
-    unit: s
-  - type: array
-    items:
-      type: number
-      unit: s
-      minimum: 0
-LabelingEfficiency:
-  name: LabelingEfficiency
-  description: |
-    Labeling efficiency, specified as a number between zero and one,
-    only if obtained externally (for example phase-contrast based).
-  type: number
-  exclusiveMinimum: 0
-LabelingLocationDescription:
-  name: LabelingLocationDescription
-  description: |
-    Description of the location of the labeling plane (`"CASL"` or `"PCASL"`) or
-    the labeling slab (`"PASL"`) that cannot be captured by fields
-    `LabelingOrientation` or `LabelingDistance`.
-    May include a link to an anonymized screenshot of the planning of the
-    labeling slab/plane with respect to the imaging slab or slices
-    `*_asllabeling.jpg`.
-    Based on DICOM macro C.8.13.5.14.
-  type: string
-LabelingOrientation:
-  name: LabelingOrientation
-  description: |
-    Orientation of the labeling plane (`(P)CASL`) or slab (`PASL`).
-    The direction cosines of a normal vector perpendicular to the ASL labeling
-    slab or plane with respect to the patient.
-    Corresponds to DICOM Tag 0018, 9255 `ASL Slab Orientation`.
-  type: array
-  items:
-    type: number
-LabelingPulseAverageB1:
-  name: LabelingPulseAverageB1
-  description: |
-    The average B1-field strength of the RF labeling pulses, in microteslas.
-    As an alternative, `"LabelingPulseFlipAngle"` can be provided.
-  type: number
-  exclusiveMinimum: 0
-  unit: uT
-LabelingPulseAverageGradient:
-  name: LabelingPulseAverageGradient
-  description: |
-    The average labeling gradient, in milliteslas per meter.
-  type: number
-  exclusiveMinimum: 0
-  unit: mT/m
-LabelingPulseDuration:
-  name: LabelingPulseDuration
-  description: |
-    Duration of the individual labeling pulses, in milliseconds.
-  type: number
-  exclusiveMinimum: 0
-  unit: ms
-LabelingPulseFlipAngle:
-  name: LabelingPulseFlipAngle
-  description: |
-    The flip angle of a single labeling pulse, in degrees,
-    which can be given as an alternative to `"LabelingPulseAverageB1"`.
-  type: number
-  exclusiveMinimum: 0
-  maximum: 360
-  unit: degree
-LabelingPulseInterval:
-  name: LabelingPulseInterval
-  description: |
-    Delay between the peaks of the individual labeling pulses, in milliseconds.
-  type: number
-  exclusiveMinimum: 0
-  unit: ms
-LabelingPulseMaximumGradient:
-  name: LabelingPulseMaximumGradient
-  description: |
-    The maximum amplitude of the gradient switched on during the application of
-    the labeling RF pulse(s), in milliteslas per meter.
-  type: number
-  exclusiveMinimum: 0
-  unit: mT/m
-LabelingSlabThickness:
-  name: LabelingSlabThickness
-  description: |
-    Thickness of the labeling slab in millimeters.
-    For non-selective FAIR a zero is entered.
-    Corresponds to DICOM Tag 0018, 9254 `ASL Slab Thickness`.
-  type: number
-  exclusiveMinimum: 0
-  unit: mm
-Levels:
-  name: Levels
-  description: |
-    For categorical variables: An object of possible values (keys) and their
-    descriptions (values).
-  type: object
-  additionalProperties:
-    type: string
-License:
-  name: License
-  description: |
-    The license for the dataset.
-    The use of license name abbreviations is RECOMMENDED for specifying a license
-    (see [Appendix II](/99-appendices/02-licenses.html)).
-    The corresponding full license text MAY be specified in an additional
-    `LICENSE` file.
-  type: string
-LongName:
-  name: LongName
-  description: |
-    Long (unabbreviated) name of the column.
-  type: string
-LookLocker:
-  name: LookLocker
-  description: |
-    Boolean indicating if a Look-Locker readout is used.
-  type: boolean
-M0Estimate:
-  name: M0Estimate
-  description: |
-    A single numerical whole-brain M0 value (referring to the M0 of blood),
-    only if obtained externally
-    (for example retrieved from CSF in a separate measurement).
-  type: number
-  exclusiveMinimum: 0
-M0Type:
-  name: M0Type
-  description: |
-    Describes the presence of M0 information.
-    `"Separate"` means that a separate `*_m0scan.nii[.gz]` is present.
-    `"Included"` means that an m0scan volume is contained within the current
-    `*_asl.nii[.gz]`.
-    `"Estimate"` means that a single whole-brain M0 value is provided.
-    `"Absent"` means that no specific M0 information is present.
-  type: string
-  enum:
-  - Separate
-  - Included
-  - Estimate
-  - Absent
-MEGChannelCount:
-  name: MEGChannelCount
-  description: |
-    Number of MEG channels (for example, `275`).
-  type: integer
-  minimum: 0
-MEGCoordinateSystem:
-  name: MEGCoordinateSystem
-  description: |
-    Defines the coordinate system for the MEG sensors.
-    See [Appendix VIII](/99-appendices/08-coordinate-systems.html)
-    for a list of restricted keywords for coordinate systems.
-    If `"Other"`, provide definition of the coordinate system in
-    `"MEGCoordinateSystemDescription"`.
-  anyOf:
-  - $ref: _MEGCoordSys
-  - $ref: _EEGCoordSys
-  - $ref: _StandardTemplateCoordSys
-  - $ref: _StandardTemplateDeprecatedCoordSys
-MEGCoordinateSystemDescription:
-  name: MEGCoordinateSystemDescription
-  description: |
-    Free-form text description of the coordinate system.
-    May also include a link to a documentation page or paper describing the
-    system in greater detail.
-  type: string
-MEGCoordinateUnits:
-  name: MEGCoordinateUnits
-  description: |
-    Units of the coordinates of `"MEGCoordinateSystem"`.
-  type: string
-  enum:
-  - m
-  - mm
-  - cm
-  - n/a
-MEGREFChannelCount:
-  name: MEGREFChannelCount
-  description: |
-    Number of MEG reference channels (for example, `23`).
-    For systems without such channels (for example, Neuromag Vectorview),
-    `MEGREFChannelCount` should be set to `0`.
-  type: integer
-  minimum: 0
-MRAcquisitionType:
-  name: MRAcquisitionType
-  description: |
-    Type of sequence readout.
-    Corresponds to DICOM Tag 0018, 0023 `MR Acquisition Type`.
-  type: string
-  enum:
-  - 2D
-  - 3D
-MRTransmitCoilSequence:
-  name: MRTransmitCoilSequence
-  description: |
-    This is a relevant field if a non-standard transmit coil is used.
-    Corresponds to DICOM Tag 0018, 9049 `MR Transmit Coil Sequence`.
-  type: string
-MTNumberOfPulses:
-  name: MTNumberOfPulses
-  description: |
-    The number of magnetization transfer RF pulses applied before the readout.
-  type: number
-MTOffsetFrequency:
-  name: MTOffsetFrequency
-  description: |
-    The frequency offset of the magnetization transfer pulse with respect to the
-    central H1 Larmor frequency in Hertz (Hz).
-  type: number
-  unit: Hz
-MTPulseBandwidth:
-  name: MTPulseBandwidth
-  description: |
-    The excitation bandwidth of the magnetization transfer pulse in Hertz (Hz).
-  type: number
-  unit: Hz
-MTPulseDuration:
-  name: MTPulseDuration
-  description: |
-    Duration of the magnetization transfer RF pulse in seconds.
-  type: number
-  unit: s
-MTPulseShape:
-  name: MTPulseShape
-  description: |
-    Shape of the magnetization transfer RF pulse waveform.
-    The value `"GAUSSHANN"` refers to a Gaussian pulse with a Hanning window.
-    The value `"SINCHANN"` refers to a sinc pulse with a Hanning window.
-    The value `"SINCGAUSS"` refers to a sinc pulse with a Gaussian window.
-  type: string
-  enum:
-  - HARD
-  - GAUSSIAN
-  - GAUSSHANN
-  - SINC
-  - SINCHANN
-  - SINCGAUSS
-  - FERMI
-MTState:
-  name: MTState
-  description: |
-    Boolean stating whether the magnetization transfer pulse is applied.
-    Corresponds to DICOM Tag 0018, 9020 `Magnetization Transfer`.
-  type: boolean
-MagneticFieldStrength:
-  name: MagneticFieldStrength
-  description: |
-    Nominal field strength of MR magnet in Tesla.
-    Corresponds to DICOM Tag 0018, 0087 `Magnetic Field Strength`.
-  type: number
-Magnification:
-  name: Magnification
-  description: |
-    Lens magnification (for example: `40`). If the file format is OME-TIFF,
-    the value MUST be consistent with the `"NominalMagnification"` OME metadata field.
-  type: number
-  exclusiveMinimum: 0
-Manual:
-  name: Manual
-  description: |
-    Indicates if the segmentation was performed manually or via an automated
-    process.
-  type: boolean
-Manufacturer:
-  name: Manufacturer
-  description: |
-    Manufacturer of the equipment that produced the measurements.
-  type: string
-ManufacturersModelName:
-  name: ManufacturersModelName
-  description: |
-    Manufacturer's model name of the equipment that produced the measurements.
-  type: string
-MatrixCoilMode:
-  name: MatrixCoilMode
-  description: |
-    (If used)
-    A method for reducing the number of independent channels by combining in
-    analog the signals from multiple coil elements.
-    There are typically different default modes when using un-accelerated or
-    accelerated (for example, `"GRAPPA"`, `"SENSE"`) imaging.
-  type: string
-MaxMovement:
-  name: MaxMovement
-  description: |
-    Maximum head movement (in mm) detected during the recording,
-    as measured by the head localisation coils (for example, `4.8`).
-  type: number
-  unit: mm
-MeasurementToolMetadata:
-  name: MeasurementToolMetadata
-  description: |
-    A description of the measurement tool as a whole.
-    Contains two fields: `"Description"` and `"TermURL"`.
-    `"Description"` is a free text description of the measurement tool.
-    `"TermURL"` is a URL to an entity in an ontology corresponding to this tool.
-  type: object
-  properties:
-    TermURL:
-      type: string
-      format: uri
-    Description:
-      type: string
-MetaboliteAvail:
-  name: MetaboliteAvail
-  description: |
-    Boolean that specifies if metabolite measurements are available.
-    If `true`, the `metabolite_parent_fraction` column MUST be present in the
-    corresponding `*_blood.tsv` file.
-  type: boolean
-MetaboliteMethod:
-  name: MetaboliteMethod
-  description: |
-    Method used to measure metabolites.
-  type: string
-MetaboliteRecoveryCorrectionApplied:
-  name: MetaboliteRecoveryCorrectionApplied
-  description: |
-    Metabolite recovery correction from the HPLC, for tracers where it changes
-    with time postinjection.
-    If `true`, the `hplc_recovery_fractions` column MUST be present in the
-    corresponding `*_blood.tsv` file.
-  type: boolean
-MiscChannelCount:
-  name: MiscChannelCount
-  description: |
-    Number of miscellaneous analog channels for auxiliary signals.
-  type: integer
-  minimum: 0
-MixingTime:
-  name: MixingTime
-  description: |
-    In the context of a stimulated- and spin-echo 3D EPI sequence for B1+ mapping,
-    corresponds to the interval between spin- and stimulated-echo pulses.
-    In the context of a diffusion-weighted double spin-echo sequence,
-    corresponds to the interval between two successive diffusion sensitizing
-    gradients, specified in seconds.
-  type: number
-  unit: s
-ModeOfAdministration:
-  name: ModeOfAdministration
-  description: |
-    Mode of administration of the injection
-    (for example, `"bolus"`, `"infusion"`, or `"bolus-infusion"`).
-  type: string
-MolarActivity:
-  name: MolarActivity
-  description: |
-    Molar activity of compound injected.
-    Corresponds to DICOM Tag 0018, 1077 `Radiopharmaceutical Specific Activity`.
-  type: number
-MolarActivityMeasTime:
-  name: MolarActivityMeasTime
-  description: |
-    Time to which molar radioactivity measurement above applies in the default
-    unit `"hh:mm:ss"`.
-  type: string
-  pattern: ^(?:2[0-3]|[01][0-9]):[0-5][0-9]:[0-5][0-9]$
-MolarActivityUnits:
-  name: MolarActivityUnits
-  description: |
-    Unit of the specified molar radioactivity (for example, `"GBq/umol"`).
-  type: string
-  format: unit
-MultibandAccelerationFactor:
-  name: MultibandAccelerationFactor
-  description: |
-    The multiband factor, for multiband acquisitions.
-  type: number
-MultipartID:
-  name: MultipartID
-  description: |
-    A unique (per participant) label tagging DWI runs that are part of a
-    multipart scan.
-  type: string
-Name:
-  name: Name
-  description: |
-    Name of the dataset.
-  type: string
-NegativeContrast:
-  name: NegativeContrast
-  description: |
-    `true` or `false` value specifying whether increasing voxel intensity
-    (within sample voxels) denotes a decreased value with respect to the
-    contrast suffix.
-    This is commonly the case when Cerebral Blood Volume is estimated via
-    usage of a contrast agent in conjunction with a T2\* weighted acquisition
-    protocol.
-  type: boolean
-NonlinearGradientCorrection:
-  name: NonlinearGradientCorrection
-  description: |
-    Boolean stating if the image saved has been corrected for gradient
-    nonlinearities by the scanner sequence.
-  type: boolean
-NumberOfVolumesDiscardedByScanner:
-  name: NumberOfVolumesDiscardedByScanner
-  description: |
-    Number of volumes ("dummy scans") discarded by the scanner
-    (as opposed to those discarded by the user post hoc)
-    before saving the imaging file.
-    For example, a sequence that automatically discards the first 4 volumes
-    before saving would have this field as 4.
-    A sequence that does not discard dummy scans would have this set to 0.
-    Please note that the onsets recorded in the `events.tsv` file should always
-    refer to the beginning of the acquisition of the first volume in the
-    corresponding imaging file - independent of the value of
-    `"NumberOfVolumesDiscardedByScanner"` field.
-  type: integer
-  minimum: 0
-NumberOfVolumesDiscardedByUser:
-  name: NumberOfVolumesDiscardedByUser
-  description: |
-    Number of volumes ("dummy scans") discarded by the user before including the
-    file in the dataset.
-    If possible, including all of the volumes is strongly recommended.
-    Please note that the onsets recorded in the `events.tsv` file should always
-    refer to the beginning of the acquisition of the first volume in the
-    corresponding imaging file - independent of the value of
-    `"NumberOfVolumesDiscardedByUser"` field.
-  type: integer
-  minimum: 0
-NumberShots:
-  name: NumberShots
-  description: |
-    The number of RF excitations needed to reconstruct a slice or volume
-    (may be referred to as partition).
-    Please mind that this is not the same as Echo Train Length which denotes the
-    number of k-space lines collected after excitation in a multi-echo readout.
-    The data type array is applicable for specifying this parameter before and
-    after the k-space center is sampled.
-    Please see
-    [`"NumberShots"` metadata field]\
-    (/99-appendices/11-qmri.html#numbershots-metadata-field)
-    in the qMRI appendix for corresponding calculations.
-  anyOf:
-  - type: number
-  - type: array
-    items:
-      type: number
-NumericalAperture:
-  name: NumericalAperture
-  description: |
-    Lens numerical aperture (for example: `1.4`). If the file format is OME-TIFF,
-    the value MUST be consistent with the `LensNA` OME metadata field.
-  type: number
-  exclusiveMinimum: 0
-OperatingSystem:
-  name: OperatingSystem
-  description: |
-    Operating system used to run the stimuli presentation software
-    (for formatting recommendations, see examples below this table).
-  type: string
-OtherAcquisitionParameters:
-  name: OtherAcquisitionParameters
-  description: |
-    Description of other relevant image acquisition parameters.
-  type: string
-PASLType:
-  name: PASLType
-  description: |
-    Type of the labeling pulse of the `PASL` labeling,
-    for example `"FAIR"`, `"EPISTAR"`, or `"PICORE"`.
-  type: string
-PCASLType:
-  name: PCASLType
-  description: |
-    The type of gradient pulses used in the `control` condition.
-  type: string
-  enum:
-  - balanced
-  - unbalanced
-ParallelAcquisitionTechnique:
-  name: ParallelAcquisitionTechnique
-  description: |
-    The type of parallel imaging used (for example `"GRAPPA"`, `"SENSE"`).
-    Corresponds to DICOM Tag 0018, 9078 `Parallel Acquisition Technique`.
-  type: string
-ParallelReductionFactorInPlane:
-  name: ParallelReductionFactorInPlane
-  description: |
-    The parallel imaging (for instance, GRAPPA) factor.
-    Use the denominator of the fraction of k-space encoded for each slice.
-    For example, 2 means half of k-space is encoded.
-    Corresponds to DICOM Tag 0018, 9069 `Parallel Reduction Factor In-plane`.
-  type: number
-PartialFourier:
-  name: PartialFourier
-  description: |
-    The fraction of partial Fourier information collected.
-    Corresponds to DICOM Tag 0018, 9081 `Partial Fourier`.
-  type: number
-PartialFourierDirection:
-  name: PartialFourierDirection
-  description: |
-    The direction where only partial Fourier information was collected.
-    Corresponds to DICOM Tag 0018, 9036 `Partial Fourier Direction`.
-  type: string
-PharmaceuticalDoseAmount:
-  name: PharmaceuticalDoseAmount
-  description: |
-    Dose amount of pharmaceutical coadministered with tracer.
-  anyOf:
-  - type: number
-  - type: array
-    items:
-      type: number
-PharmaceuticalDoseRegimen:
-  name: PharmaceuticalDoseRegimen
-  description: |
-    Details of the pharmaceutical dose regimen.
-    Either adequate description or short-code relating to regimen documented
-    elsewhere (for example, `"single oral bolus"`).
-  type: string
-PharmaceuticalDoseTime:
-  name: PharmaceuticalDoseTime
-  description: |
-    Time of administration of pharmaceutical dose, relative to time zero.
-    For an infusion, this should be a vector with two elements specifying the
-    start and end of the infusion period. For more complex dose regimens,
-    the regimen description should be complete enough to enable unambiguous
-    interpretation of `"PharmaceuticalDoseTime"`.
-    Unit format of the specified pharmaceutical dose time MUST be seconds.
-  anyOf:
-  - type: number
-    unit: s
-  - type: array
-    items:
-      type: number
-      unit: s
-PharmaceuticalDoseUnits:
-  name: PharmaceuticalDoseUnits
-  description: |
-    Unit format relating to pharmaceutical dose
-    (for example, `"mg"` or `"mg/kg"`).
-  type: string
-  format: unit
-PharmaceuticalName:
-  name: PharmaceuticalName
-  description: |
-    Name of pharmaceutical coadministered with tracer.
-  type: string
-PhaseEncodingDirection:
-  name: PhaseEncodingDirection
-  description: |
-    The letters `i`, `j`, `k` correspond to the first, second and third axis of
-    the data in the NIFTI file.
-    The polarity of the phase encoding is assumed to go from zero index to
-    maximum index unless `-` sign is present
-    (then the order is reversed - starting from the highest index instead of
-    zero).
-    `PhaseEncodingDirection` is defined as the direction along which phase is was
-    modulated which may result in visible distortions.
-    Note that this is not the same as the DICOM term
-    `InPlanePhaseEncodingDirection` which can have `ROW` or `COL` values.
-  type: string
-  enum:
-  - i
-  - j
-  - k
-  - i-
-  - j-
-  - k-
-PixelSize:
-  name: PixelSize
-  description: |
-    A 2- or 3-number array of the physical size of a pixel, either `[PixelSizeX, PixelSizeY]`
-    or `[PixelSizeX, PixelSizeY, PixelSizeZ]`, where X is the width, Y the height and Z the
-    depth.
-    If the file format is OME-TIFF, these values need to be consistent with `PhysicalSizeX`,
-    `PhysicalSizeY` and `PhysicalSizeZ` OME metadata fields, after converting in
-    `PixelSizeUnits` according to `PhysicalSizeXunit`, `PhysicalSizeYunit` and
-    `PhysicalSizeZunit` OME fields.
-  type: array
-  minItems: 2
-  maxItems: 3
-  items:
-    type: number
-    minimum: 0
-PixelSizeUnits:
-  name: PixelSizeUnits
-  description: |
-    Unit format of the specified `"PixelSize"`. MUST be one of: `"mm"` (millimeter), `"um"`
-    (micrometer) or `"nm"` (nanometer).
-  type: string
-  enum:
-  - mm
-  - um
-  - nm
-PlasmaAvail:
-  name: PlasmaAvail
-  description: |
-    Boolean that specifies if plasma measurements are available.
-  type: boolean
-PlasmaFreeFraction:
-  name: PlasmaFreeFraction
-  description: |
-    Measured free fraction in plasma, meaning the concentration of free compound
-    in plasma divided by total concentration of compound in plasma
-    (Units: 0-100%).
-  type: number
-  minimum: 0
-  maximum: 100
-PlasmaFreeFractionMethod:
-  name: PlasmaFreeFractionMethod
-  description: |
-    Method used to estimate free fraction.
-  type: string
-PostLabelingDelay:
-  name: PostLabelingDelay
-  description: |
-    This is the postlabeling delay (PLD) time, in seconds, after the end of the
-    labeling (for `"CASL"` or `"PCASL"`) or middle of the labeling pulse
-    (for `"PASL"`) until the middle of the excitation pulse applied to the
-    imaging slab (for 3D acquisition) or first slice (for 2D acquisition).
-    Can be a number (for a single-PLD time series) or an array of numbers
-    (for multi-PLD and Look-Locker).
-    In the latter case, the array of numbers contains the PLD of each volume,
-    namely each `control` and `label`, in the acquisition order.
-    Any image within the time-series without a PLD, for example an `m0scan`,
-    is indicated by a zero.
-    Based on DICOM Tags 0018, 9079 `Inversion Times` and 0018, 0082
-    `InversionTime`.
-  anyOf:
-  - type: number
-    exclusiveMinimum: 0
-    unit: s
-  - type: array
-    items:
-      type: number
-      exclusiveMinimum: 0
-      unit: s
-PowerLineFrequency:
-  name: PowerLineFrequency
-  description: |
-    Frequency (in Hz) of the power grid at the geographical location of the
-    instrument (for example, `50` or `60`).
-  anyOf:
-  - type: number
-    exclusiveMinimum: 0
-    unit: Hz
-  - type: string
-    enum:
-    - n/a
-PromptRate:
-  name: PromptRate
-  description: |
-    Prompt rate for each frame (same units as `Units`, for example, `"Bq/mL"`).
-  type: array
-  items:
-    type: number
-PulseSequenceDetails:
-  name: PulseSequenceDetails
-  description: |
-    Information beyond pulse sequence type that identifies the specific pulse
-    sequence used (for example,
-    `"Standard Siemens Sequence distributed with the VB17 software"`,
-    `"Siemens WIP ### version #.##,"` or
-    `"Sequence written by X using a version compiled on MM/DD/YYYY"`).
-  type: string
-PulseSequenceType:
-  name: PulseSequenceType
-  description: |
-    A general description of the pulse sequence used for the scan
-    (for example, `"MPRAGE"`, `"Gradient Echo EPI"`, `"Spin Echo EPI"`,
-    `"Multiband gradient echo EPI"`).
-  type: string
-Purity:
-  name: Purity
-  description: |
-    Purity of the radiolabeled compound (between 0 and 100%).
-  type: number
-  minimum: 0
-  maximum: 100
-RandomRate:
-  name: RandomRate
-  description: |
-    Random rate for each frame (same units as `"Units"`, for example, `"Bq/mL"`).
-  type: array
-  items:
-    type: number
-RawSources:
-  name: RawSources
-  description: |
-    A list of paths relative to dataset root pointing to the BIDS-Raw file(s)
-    that were used in the creation of this derivative.
-  type: array
-  items:
-    type: string
-    format: dataset_relative
-ReceiveCoilActiveElements:
-  name: ReceiveCoilActiveElements
-  description: |
-    Information describing the active/selected elements of the receiver coil.
-    This does not correspond to a tag in the DICOM ontology.
-    The vendor-defined terminology for active coil elements can go in this field.
-  type: string
-ReceiveCoilName:
-  name: ReceiveCoilName
-  description: |
-    Information describing the receiver coil.
-    Corresponds to DICOM Tag 0018, 1250 `Receive Coil Name`,
-    although not all vendors populate that DICOM Tag,
-    in which case this field can be derived from an appropriate
-    private DICOM field.
-  type: string
-ReconFilterSize:
-  name: ReconFilterSize
-  description: |
-    Kernel size of post-recon filter (FWHM) in default units `"mm"`.
-  anyOf:
-  - type: number
-    unit: mm
-  - type: array
-    items:
-      type: number
-      unit: mm
-ReconFilterType:
-  name: ReconFilterType
-  description: |
-    Type of post-recon smoothing (for example, `["Shepp"]`).
-  anyOf:
-  - type: string
-  - type: array
-    items:
-      type: string
-ReconMethodImplementationVersion:
-  name: ReconMethodImplementationVersion
-  description: |
-    Identification for the software used, such as name and version.
-  type: string
-ReconMethodName:
-  name: ReconMethodName
-  description: |
-    Reconstruction method or algorithm (for example, `"3d-op-osem"`).
-  type: string
-ReconMethodParameterLabels:
-  name: ReconMethodParameterLabels
-  description: |
-    Names of reconstruction parameters (for example, `["subsets", "iterations"]`).
-  type: array
-  items:
-    type: string
-ReconMethodParameterUnits:
-  name: ReconMethodParameterUnits
-  description: |
-    Unit of reconstruction parameters (for example, `["none", "none"]`).
-  type: array
-  items:
-    type: string
-    format: unit
-ReconMethodParameterValues:
-  name: ReconMethodParameterValues
-  description: |
-    Values of reconstruction parameters (for example, `[21, 3]`).
-  type: array
-  items:
-    type: number
-RecordingDuration:
-  name: RecordingDuration
-  description: |
-    Length of the recording in seconds (for example, `3600`).
-  type: number
-  unit: s
-RecordingType:
-  name: RecordingType
-  description: |
-    Defines whether the recording is `"continuous"`, `"discontinuous"`, or
-    `"epoched"`, where `"epoched"` is limited to time windows about events of
-    interest (for example, stimulus presentations or subject responses).
-  type: string
-  enum:
-  - continuous
-  - epoched
-  - discontinuous
-ReferencesAndLinks:
-  name: ReferencesAndLinks
-  description: |
-    List of references to publications that contain information on the dataset.
-    A reference may be textual or a
-    [URI](/02-common-principles.html#uniform-resource-indicator).
-  items:
-    type: string
-  type: array
-RepetitionTime:
-  name: RepetitionTime
-  description: |
-    The time in seconds between the beginning of an acquisition of one volume
-    and the beginning of acquisition of the volume following it (TR).
-    When used in the context of functional acquisitions this parameter best
-    corresponds to
-    [DICOM Tag 0020, 0110](http://dicomlookup.com/lookup.asp?sw=Tnumber&q=(0020,0110)):
-    the "time delta between images in a
-    dynamic of functional set of images" but may also be found in
-    [DICOM Tag 0018, 0080](http://dicomlookup.com/lookup.asp?sw=Tnumber&q=(0018,0080)):
-    "the period of time in msec between the beginning
-    of a pulse sequence and the beginning of the succeeding
-    (essentially identical) pulse sequence".
-    This definition includes time between scans (when no data has been acquired)
-    in case of sparse acquisition schemes.
-    This value MUST be consistent with the 'pixdim[4]' field (after accounting
-    for units stored in 'xyzt_units' field) in the NIfTI header.
-    This field is mutually exclusive with VolumeTiming.
-  type: number
-  exclusiveMinimum: 0
-  unit: s
-RepetitionTimeExcitation:
-  name: RepetitionTimeExcitation
-  description: |
-    The interval, in seconds, between two successive excitations.
-    [DICOM Tag 0018, 0080](http://dicomlookup.com/lookup.asp?sw=Tnumber&q=(0018,0080)
-    best refers to this parameter.
-    This field may be used together with the `"RepetitionTimePreparation"` for
-    certain use cases, such as
-    [MP2RAGE](https://doi.org/10.1016/j.neuroimage.2009.10.002).
-    Use `RepetitionTimeExcitation` (in combination with
-    `"RepetitionTimePreparation"` if needed) for anatomy imaging data rather than
-    `"RepetitionTime"` as it is already defined as the amount of time that it takes
-    to acquire a single volume in the
-    [task imaging data](/04-modality-specific-files/01-magnetic-resonance-\
-    imaging-data.html#task-including-resting-state-imaging-data)
-    section.
-  type: number
-  minimum: 0
-  unit: s
-RepetitionTimePreparation:
-  name: RepetitionTimePreparation
-  description: |
-    The interval, in seconds, that it takes a preparation pulse block to
-    re-appear at the beginning of the succeeding (essentially identical) pulse
-    sequence block.
-    The data type number may apply to files from any MRI modality concerned with
-    a single value for this field.
-    The data type array provides a value for each volume in a 4D dataset and
-    should only be used when the volume timing is critical for interpretation of
-    the data, such as in
-    [ASL](/04-modality-specific-files/01-magnetic-resonance-imaging-data.html\
-    #arterial-spin-labeling-perfusion-data).
-  anyOf:
-  - type: number
-    minimum: 0
-    unit: s
-  - type: array
-    items:
-      type: number
-      minimum: 0
-      unit: s
-Resolution:
-  name: Resolution
-  description: |
-    Specifies the interpretation of the resolution keyword.
-    If an object is used, then the keys should be values for the ``res`` entity
-    and values should be descriptions of those ``res`` values.
-  anyOf:
-  - type: string
-  - type: object
-    additionalProperties:
-      type: string
-SEEGChannelCount:
-  name: SEEGChannelCount
-  description: |
-    Number of SEEG channels.
-  type: integer
-  minimum: 0
-SampleEmbedding:
-  name: SampleEmbedding
-  description: |
-    Description of the tissue sample embedding (for example: `"Epoxy resin"`).
-  type: string
-SampleEnvironment:
-  name: SampleEnvironment
-  description: |
-    Environment in which the sample was imaged. MUST be one of: `"in vivo"`, `"ex vivo"`
-    or `"in vitro"`.
-  type: string
-  enum:
-  - in vivo
-  - ex vivo
-  - in vitro
-SampleExtractionInstitution:
-  name: SampleExtractionInstitution
-  description: |
-    The name of the institution in charge of the extraction of the sample,
-    if different from the institution in charge of the equipment that produced the image.
-  type: string
-SampleExtractionProtocol:
-  name: SampleExtractionProtocol
-  description: |
-    Description of the sample extraction protocol or
-    [URI](/02-common-principles.html#uniform-resource-indicator)
-    (for example from [protocols.io](https://www.protocols.io/)).
-  type: string
-SampleFixation:
-  name: SampleFixation
-  description: |
-    Description of the tissue sample fixation
-    (for example: `"4% paraformaldehyde, 2% glutaraldehyde"`).
-  type: string
-SampleOrigin:
-  name: SampleOrigin
-  description: |
-    Describes from which tissue the genetic information was extracted.
-  type: string
-  enum:
-  - blood
-  - saliva
-  - brain
-  - csf
-  - breast milk
-  - bile
-  - amniotic fluid
-  - other biospecimen
-SamplePrimaryAntibody:
-  name: SamplePrimaryAntibody
-  description: |
-    Description(s) of the primary antibody used for immunostaining.
-    Either an [RRID](https://scicrunch.org/resources) or the name, supplier and catalogue
-    number of a commercial antibody.
-    For non-commercial antibodies either an [RRID](https://scicrunch.org/resources) or the
-    host-animal and immunogen used (for examples: `"RRID:AB_2122563"` or
-    `"Rabbit anti-Human HTR5A Polyclonal Antibody, Invitrogen, Catalog # PA1-2453"`).
-    MAY be an array of strings if different antibodies are used in each channel of the file.
-  anyOf:
-  - type: string
-  - type: array
-    items:
-      type: string
-SampleSecondaryAntibody:
-  name: SampleSecondaryAntibody
-  description: |
-    Description(s) of the secondary antibody used for immunostaining.
-    Either an [RRID](https://scicrunch.org/resources) or the name, supplier and catalogue
-    number of a commercial antibody.
-    For non-commercial antibodies either an [RRID](https://scicrunch.org/resources) or the
-    host-animal and immunogen used (for examples: `"RRID:AB_228322"` or
-    `"Goat anti-Mouse IgM Secondary Antibody, Invitrogen, Catalog # 31172"`).
-    MAY be an array of strings if different antibodies are used in each channel of the file.
-  anyOf:
-  - type: string
-  - type: array
-    items:
-      type: string
-SampleStaining:
-  name: SampleStaining
-  description: |
-    Description(s) of the tissue sample staining (for example: `"Osmium"`).
-    MAY be an array of strings if different stains are used in each channel of the file
-    (for example: `["LFB", "PLP"]`).
-  anyOf:
-  - type: string
-  - type: array
-    items:
-      type: string
-SamplingFrequency:
-  name: SamplingFrequency
-  description: |
-    Sampling frequency (in Hz) of all the data in the recording,
-    regardless of their type (for example, `2400`).
-  type: number
-  unit: Hz
-ScaleFactor:
-  name: ScaleFactor
-  description: |
-    Scale factor for each frame.
-  type: array
-  items:
-    type: number
-ScanDate:
-  name: ScanDate
-  description: |
-    Date of scan in the format `"YYYY-MM-DD[Z]"`.
-    This field is DEPRECATED, and this metadata SHOULD be recorded in the `acq_time` column of the
-    corresponding [Scans file](/03-modality-agnostic-files.html#scans-file).
-  type: string
-  format: date
-ScanOptions:
-  name: ScanOptions
-  description: |
-    Parameters of ScanningSequence.
-    Corresponds to DICOM Tag 0018, 0022 `Scan Options`.
-  anyOf:
-  - type: string
-  - type: array
-    items:
-      type: string
-ScanStart:
-  name: ScanStart
-  description: |
-    Time of start of scan with respect to `TimeZero` in the default unit seconds.
-  type: number
-  unit: s
-ScanningSequence:
-  name: ScanningSequence
-  description: |
-    Description of the type of data acquired.
-    Corresponds to DICOM Tag 0018, 0020 `Scanning Sequence`.
-  anyOf:
-  - type: string
-  - type: array
-    items:
-      type: string
-ScatterFraction:
-  name: ScatterFraction
-  description: |
-    Scatter fraction for each frame (Units: 0-100%).
-  type: array
-  items:
-    type: number
-    minimum: 0
-    maximum: 100
-SequenceName:
-  name: SequenceName
-  description: |
-    Manufacturer's designation of the sequence name.
-    Corresponds to DICOM Tag 0018, 0024 `Sequence Name`.
-  type: string
-SequenceVariant:
-  name: SequenceVariant
-  description: |
-    Variant of the ScanningSequence.
-    Corresponds to DICOM Tag 0018, 0021 `Sequence Variant`.
-  anyOf:
-  - type: string
-  - type: array
-    items:
-      type: string
-SinglesRate:
-  name: SinglesRate
-  description: |
-    Singles rate for each frame (same units as `Units`, for example, `"Bq/mL"`).
-  type: array
-  items:
-    type: number
-SkullStripped:
-  name: SkullStripped
-  description: |
-    Whether the volume was skull stripped (non-brain voxels set to zero) or not.
-  type: boolean
-SliceEncodingDirection:
-  name: SliceEncodingDirection
-  description: |
-    The axis of the NIfTI data along which slices were acquired,
-    and the direction in which `"SliceTiming"` is defined with respect to.
-    `i`, `j`, `k` identifiers correspond to the first, second and third axis of
-    the data in the NIfTI file.
-    A `-` sign indicates that the contents of `"SliceTiming"` are defined in
-    reverse order - that is, the first entry corresponds to the slice with the
-    largest index, and the final entry corresponds to slice index zero.
-    When present, the axis defined by `"SliceEncodingDirection"` needs to be
-    consistent with the `slice_dim` field in the NIfTI header.
-    When absent, the entries in `"SliceTiming"` must be in the order of increasing
-    slice index as defined by the NIfTI header.
-  type: string
-  enum:
-  - i
-  - j
-  - k
-  - i-
-  - j-
-  - k-
-SliceThickness:
-  name: SliceThickness
-  description: |
-    Slice thickness of the tissue sample in the unit micrometers (`"um"`) (for example: `5`).
-  type: number
-  unit: um
-  exclusiveMinimum: 0
-SliceTiming:
-  name: SliceTiming
-  description: |
-    The time at which each slice was acquired within each volume (frame) of the
-    acquisition.
-    Slice timing is not slice order -- rather, it is a list of times containing
-    the time (in seconds) of each slice acquisition in relation to the beginning
-    of volume acquisition.
-    The list goes through the slices along the slice axis in the slice encoding
-    dimension (see below).
-    Note that to ensure the proper interpretation of the `"SliceTiming"` field,
-    it is important to check if the OPTIONAL `SliceEncodingDirection` exists.
-    In particular, if `"SliceEncodingDirection"` is negative,
-    the entries in `"SliceTiming"` are defined in reverse order with respect to the
-    slice axis, such that the final entry in the `"SliceTiming"` list is the time
-    of acquisition of slice 0. Without this parameter slice time correction will
-    not be possible.
-  type: array
-  items:
-    type: number
-    minimum: 0
-    unit: s
-SoftwareFilters:
-  name: SoftwareFilters
-  description: |
-    [Object](https://www.json.org/json-en.html)
-    of temporal software filters applied, or `"n/a"` if the data is
-    not available.
-    Each key:value pair in the JSON object is a name of the filter and an object
-    in which its parameters are defined as key:value pairs
-    (for example, `{"Anti-aliasing filter":
-    {"half-amplitude cutoff (Hz)": 500, "Roll-off": "6dB/Octave"}}`).
-  anyOf:
-  - type: object
-    additionalProperties:
-      type: object
-  - type: string
-    enum:
-    - n/a
-SoftwareName:
-  name: SoftwareName
-  description: |
-    Name of the software that was used to present the stimuli.
-  type: string
-SoftwareRRID:
-  name: SoftwareRRID
-  description: |
-    [Research Resource Identifier](https://scicrunch.org/resources) of the
-    software that was used to present the stimuli.
-    Examples: The RRID for Psychtoolbox is 'SCR_002881',
-    and that of PsychoPy is 'SCR_006571'.
-  type: string
-  pattern: .+_.+
-SoftwareVersion:
-  name: SoftwareVersion
-  description: |
-    Version of the software that was used to present the stimuli.
-  type: string
-SoftwareVersions:
-  name: SoftwareVersions
-  description: |
-    Manufacturer's designation of software version of the equipment that produced
-    the measurements.
-  type: string
-SourceDatasets:
-  name: SourceDatasets
-  description: |
-    Used to specify the locations and relevant attributes of all source datasets.
-    Valid keys in each object include `"URL"`, `"DOI"` (see
-    [URI](/02-common-principles.html#uniform-resource-indicator)), and
-    `"Version"` with
-    [string](https://www.w3schools.com/js/js_json_datatypes.asp)
-    values.
-  type: array
-  items:
-    type: object
-    properties:
-      URL:
-        type: string
-        format: uri
-      DOI:
-        type: string
-      Version:
-        type: string
-Sources:
-  name: Sources
-  description: |
-    A list of files with the paths specified relative to dataset root;
-    these files were directly used in the creation of this derivative data file.
-    For example, if a derivative A is used in the creation of another
-    derivative B, which is in turn used to generate C in a chain of A->B->C,
-    C should only list B in `"Sources"`, and B should only list A in `"Sources"`.
-    However, in case both X and Y are directly used in the creation of Z,
-    then Z should list X and Y in `"Sources"`,
-    regardless of whether X was used to generate Y.
-  type: array
-  items:
-    type: string
-    format: dataset_relative
-SpatialReference:
-  name: SpatialReference
-  description: |
-    For images with a single reference, the value MUST be a single string.
-    For images with multiple references, such as surface and volume references,
-    a JSON object MUST be used.
-  anyOf:
-  - type: string
-    enum:
-    - orig
-  - type: string
-    format: uri
-  - type: string
-    format: dataset_relative
-  - type: object
-    additionalProperties:
-      anyOf:
-      - type: string
-        enum:
-        - orig
-      - type: string
-        format: uri
-      - type: string
-        format: dataset_relative
-SpecificRadioactivity:
-  name: SpecificRadioactivity
-  description: |
-    Specific activity of compound injected.
-    **Note this is not required for an FDG acquisition, since it is not available,
-    and SHOULD be set to `"n/a"`**.
-  anyOf:
-  - type: number
-  - type: string
-    enum:
-    - n/a
-SpecificRadioactivityMeasTime:
-  name: SpecificRadioactivityMeasTime
-  description: |
-    Time to which specific radioactivity measurement above applies in the default
-    unit `"hh:mm:ss"`.
-  type: string
-  pattern: ^(?:2[0-3]|[01][0-9]):[0-5][0-9]:[0-5][0-9]$
-SpecificRadioactivityUnits:
-  name: SpecificRadioactivityUnits
-  description: |
-    Unit format of specified specific radioactivity (for example, `"Bq/g"`).
-    **Note this is not required for an FDG acquisition, since it is not available,
-    and SHOULD be set to `"n/a"`**.
-  anyOf:
-  - type: string
-    format: unit
-  - type: string
-    enum:
-    - n/a
-SpoilingGradientDuration:
-  name: SpoilingGradientDuration
-  description: |
-    The duration of the spoiler gradient lobe in seconds.
-    The duration of a trapezoidal lobe is defined as the summation of ramp-up
-    and plateau times.
-  type: number
-  unit: s
-SpoilingGradientMoment:
-  name: SpoilingGradientMoment
-  description: |
-    Zeroth moment of the spoiler gradient lobe in
-    millitesla times second per meter (mT.s/m).
-  type: number
-  unit: mT.s/m
-SpoilingRFPhaseIncrement:
-  name: SpoilingRFPhaseIncrement
-  description: |
-    The amount of incrementation described in degrees,
-    which is applied to the phase of the excitation pulse at each TR period for
-    achieving RF spoiling.
-  type: number
-  unit: degrees
-SpoilingState:
-  name: SpoilingState
-  description: |
-    Boolean stating whether the pulse sequence uses any type of spoiling
-    strategy to suppress residual transverse magnetization.
-  type: boolean
-SpoilingType:
-  name: SpoilingType
-  description: |
-    Specifies which spoiling method(s) are used by a spoiled sequence.
-  type: string
-  enum:
-  - RF
-  - GRADIENT
-  - COMBINED
-StartTime:
-  name: StartTime
-  description: |
-    Start time in seconds in relation to the start of acquisition of the first
-    data sample in the corresponding neural dataset (negative values are allowed).
-  type: number
-  unit: s
-StationName:
-  name: StationName
-  description: |
-    Institution defined name of the machine that produced the measurements.
-  type: string
-StimulusPresentation:
-  name: StimulusPresentation
-  description: |
-    Object containing key value pairs related to the software used to present
-    the stimuli during the experiment, specifically:
-    `"OperatingSystem"`, `"SoftwareName"`, `"SoftwareRRID"`, `"SoftwareVersion"` and
-    `"Code"`.
-    See table below for more information.
-  type: object
-  properties:
-    OperatingSystem:
-      $ref: OperatingSystem
-    SoftwareName:
-      $ref: SoftwareName
-    SoftwareRRID:
-      $ref: SoftwareRRID
-    SoftwareVersion:
-      $ref: SoftwareVersion
-    Code:
-      $ref: Code
-SubjectArtefactDescription:
-  name: SubjectArtefactDescription
-  description: |
-    Freeform description of the observed subject artefact and its possible cause
-    (for example, `"Vagus Nerve Stimulator"`, `"non-removable implant"`).
-    If this field is set to `"n/a"`, it will be interpreted as absence of major
-    source of artifacts except cardiac and blinks.
-  type: string
-TaskDescription:
-  name: TaskDescription
-  description: |
-    Longer description of the task.
-  type: string
-TaskName:
-  name: TaskName
-  description: |
-    Name of the task.
-    No two tasks should have the same name.
-    The task label included in the file name is derived from this `"TaskName"` field
-    by removing all non-alphanumeric (`[a-zA-Z0-9]`) characters.
-    For example `"TaskName"` `"faces n-back"` will correspond to task label
-    `facesnback`.
-  type: string
-TermURL:
-  name: TermURL
-  description: |
-    URL pointing to a formal definition of this type of data in an ontology
-    available on the web.
-  type: string
-TimeZero:
-  name: TimeZero
-  description: |
-    Time zero to which all scan and/or blood measurements have been adjusted to,
-    in the unit "hh:mm:ss".
-    This should be equal to `"InjectionStart"` or `"ScanStart"`.
-  type: string
-  pattern: ^(?:2[0-3]|[01][0-9]):[0-5][0-9]:[0-5][0-9]$
-TissueDeformationScaling:
-  name: TissueDeformationScaling
-  description: |
-    Estimated deformation of the tissue, given as a percentage of the original
-    tissue size (for examples: for a shrinkage of 3%, the value is `97`;
-    and for an expansion of 100%, the value is `200`).
-  type: number
-  exclusiveMinimum: 0
-TissueOrigin:
-  name: TissueOrigin
-  description: |
-    Describes the type of tissue analyzed for `"SampleOrigin"` `brain`.
-  type: string
-  enum:
-  - gray matter
-  - white matter
-  - csf
-  - meninges
-  - macrovascular
-  - microvascular
-TotalAcquiredPairs:
-  name: TotalAcquiredPairs
-  description: |
-    The total number of acquired `control`-`label` pairs.
-    A single pair consists of a single `control` and a single `label` image.
-  type: number
-  exclusiveMinimum: 0
-TotalReadoutTime:
-  name: TotalReadoutTime
-  description: |
-    This is actually the "effective" total readout time,
-    defined as the readout duration, specified in seconds,
-    that would have generated data with the given level of distortion.
-    It is NOT the actual, physical duration of the readout train.
-    If `"EffectiveEchoSpacing"` has been properly computed,
-    it is just `EffectiveEchoSpacing * (ReconMatrixPE - 1)`.
-  type: number
-  unit: s
-TracerMolecularWeight:
-  name: TracerMolecularWeight
-  description: |
-    Accurate molecular weight of the tracer used.
-  type: number
-TracerMolecularWeightUnits:
-  name: TracerMolecularWeightUnits
-  description: |
-    Unit of the molecular weights measurement (for example, `"g/mol"`).
-  type: string
-  format: unit
-TracerName:
-  name: TracerName
-  description: |
-    Name of the tracer compound used (for example, `"CIMBI-36"`)
-  type: string
-TracerRadLex:
-  name: TracerRadLex
-  description: |
-    ID of the tracer compound from the RadLex Ontology.
-  type: string
-TracerRadionuclide:
-  name: TracerRadionuclide
-  description: |
-    Radioisotope labelling tracer (for example, `"C11"`).
-  type: string
-TracerSNOMED:
-  name: TracerSNOMED
-  description: |
-    ID of the tracer compound from the SNOMED Ontology
-    (subclass of Radioactive isotope).
-  type: string
-TriggerChannelCount:
-  name: TriggerChannelCount
-  description: |
-    Number of channels for digital (TTL bit level) triggers.
-  type: integer
-  minimum: 0
-TubingLength:
-  name: TubingLength
-  description: |
-    The length of the blood tubing, from the subject to the detector in meters.
-  type: number
-  unit: m
-TubingType:
-  name: TubingType
-  description: |
-    Description of the type of tubing used, ideally including the material and
-    (internal) diameter.
-  type: string
-Type:
-  name: Type
-  description: |
-    Short identifier of the mask.
-    The value `"Brain"` refers to a brain mask.
-    The value `"Lesion"` refers to a lesion mask.
-    The value `"Face"` refers to a face mask.
-    The value `"ROI"` refers to a region of interest mask.
-  type: string
-  enum:
-  - Brain
-  - Lesion
-  - Face
-  - ROI
-Units:
-  name: Units
-  description: |
-    Measurement units for the associated file.
-    SI units in CMIXF formatting are RECOMMENDED
-    (see [Units](/02-common-principles.html#units)).
-  type: string
-  format: unit
-VascularCrushing:
-  name: VascularCrushing
-  description: |
-    Boolean indicating if Vascular Crushing is used.
-    Corresponds to DICOM Tag 0018, 9259 `ASL Crusher Flag`.
-  type: boolean
-VascularCrushingVENC:
-  name: VascularCrushingVENC
-  description: |
-    The crusher gradient strength, in centimeters per second.
-    Specify either one number for the total time-series, or provide an array of
-    numbers, for example when using QUASAR, using the value zero to identify
-    volumes for which `VascularCrushing` was turned off.
-    Corresponds to DICOM Tag 0018, 925A `ASL Crusher Flow Limit`.
-  anyOf:
-  - type: number
-    unit: cm/s
-  - type: array
-    items:
-      type: number
-      unit: cm/s
-VolumeTiming:
-  name: VolumeTiming
-  description: |
-    The time at which each volume was acquired during the acquisition.
-    It is described using a list of times referring to the onset of each volume
-    in the BOLD series.
-    The list must have the same length as the BOLD series,
-    and the values must be non-negative and monotonically increasing.
-    This field is mutually exclusive with `"RepetitionTime"` and `"DelayTime"`.
-    If defined, this requires acquisition time (TA) be defined via either
-    `"SliceTiming"` or `"AcquisitionDuration"` be defined.
-  type: array
-  minItems: 1
-  items:
-    type: number
-    unit: s
-WholeBloodAvail:
-  name: WholeBloodAvail
-  description: |
-    Boolean that specifies if whole blood measurements are available.
-    If `true`, the `whole_blood_radioactivity` column MUST be present in the
-    corresponding `*_blood.tsv` file.
-  type: boolean
-WithdrawalRate:
-  name: WithdrawalRate
-  description: |
-    The rate at which the blood was withdrawn from the subject.
-    The unit of the specified withdrawal rate should be in `"mL/s"`.
-  type: number
-  unit: mL/s
-_CoordUnits:
-  type: string
-  enum:
-  - m
-  - mm
-  - cm
-  - n/a
-_EEGCoordSys:
-  type: string
-  enum:
-  - CapTrak
-  - EEGLAB
-  - EEGLAB-HJ
-  - Other
-_GeneticLevelEnum:
-  type: string
-  enum:
-  - Genetic
-  - Genomic
-  - Epigenomic
-  - Transcriptomic
-  - Metabolomic
-  - Proteomic
-_LandmarkCoordinates:
-  type: object
-  additionalProperties:
-    type: array
-    items:
-      type: number
-    minItems: 3
-    maxItems: 3
-_MEGCoordSys:
-  type: string
-  enum:
-  - CTF
-  - ElektaNeuromag
-  - 4DBti
-  - KitYokogawa
-  - ChietiItab
-  - Other
-_StandardTemplateCoordSys:
-  type: string
-  enum:
-  - ICBM452AirSpace
-  - ICBM452Warp5Space
-  - IXI549Space
-  - fsaverage
-  - fsaverageSym
-  - fsLR
-  - MNIColin27
-  - MNI152Lin
-  - MNI152NLin2009aSym
-  - MNI152NLin2009bSym
-  - MNI152NLin2009cSym
-  - MNI152NLin2009aAsym
-  - MNI152NLin2009bAsym
-  - MNI152NLin2009cAsym
-  - MNI152NLin6Sym
-  - MNI152NLin6ASym
-  - MNI305
-  - NIHPD
-  - OASIS30AntsOASISAnts
-  - OASIS30Atropos
-  - Talairach
-  - UNCInfant
-_StandardTemplateDeprecatedCoordSys:
-  type: string
-  enum:
-  - fsaverage3
-  - fsaverage4
-  - fsaverage5
-  - fsaverage6
-  - fsaveragesym
-  - UNCInfant0V21
-  - UNCInfant1V21
-  - UNCInfant2V21
-  - UNCInfant0V22
-  - UNCInfant1V22
-  - UNCInfant2V22
-  - UNCInfant0V23
-  - UNCInfant1V23
-  - UNCInfant2V23
-_iEEGCoordSys:
-  type: string
-  enum:
-  - Pixels
-  - ACPC
-  - Other
-iEEGCoordinateProcessingDescription:
-  name: iEEGCoordinateProcessingDescription
-  description: |
-    Has any post-processing (such as projection) been done on the electrode
-    positions (for example, `"surface_projection"`, `"none"`).
-  type: string
-iEEGCoordinateProcessingReference:
-  name: iEEGCoordinateProcessingReference
-  description: |
-    A reference to a paper that defines in more detail the method used to
-    localize the electrodes and to post-process the electrode positions.
-  type: string
-iEEGCoordinateSystem:
-  name: iEEGCoordinateSystem
-  description: |
-    Defines the coordinate system for the iEEG sensors.
-    See
-    [Appendix VIII](/99-appendices/08-coordinate-systems.html)
-    for a list of restricted keywords for coordinate systems.
-    If `"Other"`, provide definition of the coordinate system in
-    `iEEGCoordinateSystemDescription`.
-    If positions correspond to pixel indices in a 2D image
-    (of either a volume-rendering, surface-rendering, operative photo, or
-    operative drawing), this MUST be `"Pixels"`.
-    For more information, see the section on
-    [2D coordinate systems](/04-modality-specific-files/04-intracranial\
-    -electroencephalography.html#allowed-2d-coordinate-systems).
-  anyOf:
-  - $ref: _iEEGCoordSys
-  - $ref: _StandardTemplateCoordSys
-  - $ref: _StandardTemplateDeprecatedCoordSys
-iEEGCoordinateSystemDescription:
-  name: iEEGCoordinateSystemDescription
-  description: |
-    Free-form text description of the coordinate system.
-    May also include a link to a documentation page or paper describing the
-    system in greater detail.
-  type: string
-iEEGCoordinateUnits:
-  name: iEEGCoordinateUnits
-  description: |
-    Units of the `*_electrodes.tsv`.
-    MUST be `"pixels"` if `iEEGCoordinateSystem` is `Pixels`.
-  type: string
-  enum:
-  - m
-  - mm
-  - cm
-  - pixels
-  - n/a
-iEEGElectrodeGroups:
-  name: iEEGElectrodeGroups
-  description: |
-    Field to describe the way electrodes are grouped into strips, grids or depth
-    probes.
-    For example, `"grid1: 10x8 grid on left temporal pole, strip2: 1x8 electrode
-    strip on xxx"`.
-  type: string
-iEEGGround:
-  name: iEEGGround
-  description: |
-    Description of the location of the ground electrode
-    (`"placed on right mastoid (M2)"`).
-  type: string
-iEEGPlacementScheme:
-  name: iEEGPlacementScheme
-  description: |
-    Freeform description of the placement of the iEEG electrodes.
-    Left/right/bilateral/depth/surface
-    (for example, `"left frontal grid and bilateral hippocampal depth"` or
-    `"surface strip and STN depth"` or
-    `"clinical indication bitemporal, bilateral temporal strips and left grid"`).
-  type: string
-iEEGReference:
-  name: iEEGReference
-  description: |
-    General description of the reference scheme used and (when applicable) of
-    location of the reference electrode in the raw recordings
-    (for example, `"left mastoid"`, `"bipolar"`,
-    `"T01"` for electrode with name T01,
-    `"intracranial electrode on top of a grid, not included with data"`,
-    `"upside down electrode"`).
-    If different channels have a different reference,
-    this field should have a general description and the channel specific
-    reference should be defined in the `channels.tsv` file.
-  type: string
diff --git a/dandi/support/bids/schemadata/1.7.0+012+dandi001/objects/modalities.yaml b/dandi/support/bids/schemadata/1.7.0+012+dandi001/objects/modalities.yaml
deleted file mode 100644
index be32d324a..000000000
--- a/dandi/support/bids/schemadata/1.7.0+012+dandi001/objects/modalities.yaml
+++ /dev/null
@@ -1,30 +0,0 @@
----
-# This file describes modalities supported by BIDS.
-mri:
-  name: Magnetic Resonance Imaging
-  description: |
-    Data acquired with an MRI scanner.
-eeg:
-  name: Electroencephalography
-  description: |
-    Data acquired with EEG.
-ieeg:
-  name: Intracranial Electroencephalography
-  description: |
-    Data acquired with iEEG.
-meg:
-  name: Magnetoencephalography
-  description: |
-    Data acquired with an MEG scanner.
-beh:
-  name: Behavioral experiments
-  description: |
-    Behavioral data acquired without accompanying neuroimaging data.
-pet:
-  name: Positron Emission Tomography
-  description: |
-    Data acquired with PET.
-micr:
-  name: Microscopy
-  description: |
-    Data acquired with a microscope.
diff --git a/dandi/support/bids/schemadata/1.7.0+012+dandi001/objects/suffixes.yaml b/dandi/support/bids/schemadata/1.7.0+012+dandi001/objects/suffixes.yaml
deleted file mode 100644
index 10efeaedb..000000000
--- a/dandi/support/bids/schemadata/1.7.0+012+dandi001/objects/suffixes.yaml
+++ /dev/null
@@ -1,654 +0,0 @@
----
-# This file defines valid BIDS file suffixes.
-# For rules regarding how suffixes relate to datatypes, see files in `rules/datatypes/`.
-2PE:
-  name: 2-photon excitation microscopy
-  description: |
-    2-photon excitation microscopy imaging data
-BF:
-  name: Bright-field microscopy
-  description: |
-    Bright-field microscopy imaging data
-Chimap:
-  name: Quantitative susceptibility map (QSM)
-  description: |
-    In parts per million (ppm).
-    QSM allows for determining the underlying magnetic susceptibility of tissue
-    (Chi)
-    ([Wang & Liu, 2014](https://onlinelibrary.wiley.com/doi/10.1002/mrm.25358)).
-    Chi maps are REQUIRED to use this suffix regardless of the method used to
-    generate them.
-  unit: ppm
-CARS:
-  name: Coherent anti-Stokes Raman spectroscopy
-  description: |
-    Coherent anti-Stokes Raman spectroscopy imaging data
-CONF:
-  name: Confocal microscopy
-  description: |
-    Confocal microscopy imaging data
-DIC:
-  name: Differential interference contrast microscopy
-  description: |
-    Differential interference contrast microscopy imaging data
-DF:
-  name: Dark-field microscopy
-  description: |
-    Dark-field microscopy imaging data
-FLAIR:
-  name: Fluid attenuated inversion recovery image
-  description: |
-    In arbitrary units (arbitrary).
-    Structural images with predominant T2 contribution (also known as T2-FLAIR),
-    in which signal from fluids (for example, CSF) is nulled out by adjusting
-    inversion time, coupled with notably long repetition and echo times.
-  unit: arbitrary
-FLASH:
-  name: Fast-Low-Angle-Shot image
-  description: |
-    FLASH (Fast-Low-Angle-Shot) is a vendor-specific implementation for spoiled
-    gradient echo acquisition.
-    It is commonly used for rapid anatomical imaging and also for many different
-    qMRI applications.
-    When used for a single file, it does not convey any information about the
-    image contrast.
-    When used in a file collection, it may result in conflicts across filenames of
-    different applications.
-    **Change:** Removed from suffixes.
-FLUO:
-  name: Fluorescence microscopy
-  description: |
-    Fluorescence microscopy imaging data
-IRT1:
-  name: Inversion recovery T1 mapping
-  description: |
-    The IRT1 method involves multiple inversion recovery spin-echo images
-    acquired at different inversion times
-    ([Barral et al. 2010](https://doi.org/10.1002/mrm.22497)).
-M0map:
-  name: Equilibrium magnetization (M0) map
-  description: |
-    In arbitrary units (arbitrary).
-    A common quantitative MRI (qMRI) fitting variable that represents the amount
-    of magnetization at thermal equilibrium.
-    M0 maps are RECOMMENDED to use this suffix if generated by qMRI applications
-    (for example, variable flip angle T1 mapping).
-  unit: arbitrary
-MEGRE:
-  name: Multi-echo Gradient Recalled Echo
-  description: |
-    Anatomical gradient echo images acquired at different echo times.
-    Please note that this suffix is not intended for the logical grouping of
-    images acquired using an Echo Planar Imaging (EPI) readout.
-MESE:
-  name: Multi-echo Spin Echo
-  description: |
-    The MESE method involves multiple spin echo images acquired at different echo
-    times and is primarily used for T2 mapping.
-    Please note that this suffix is not intended for the logical grouping of
-    images acquired using an Echo Planar Imaging (EPI) readout.
-MP2RAGE:
-  name: Magnetization Prepared Two Gradient Echoes
-  description: |
-    The MP2RAGE method is a special protocol that collects several images at
-    different flip angles and inversion times to create a parametric T1map by
-    combining the magnitude and phase images
-    ([Marques et al. 2010](https://doi.org/10.1016/j.neuroimage.2009.10.002)).
-MPE:
-  name: Multi-photon excitation microscopy
-  description: |
-    Multi-photon excitation microscopy imaging data
-MPM:
-  name: Multi-parametric Mapping
-  description: |
-    The MPM approaches (a.k.a hMRI) involves the acquisition of highly-similar
-    anatomical images that differ in terms of application of a magnetization
-    transfer RF pulse (MTon or MToff), flip angle and (optionally) echo time and
-    magnitue/phase parts
-    ([Weiskopf et al. 2013](https://doi.org/10.3389/fnins.2013.00095)).
-    See [here](https://owncloud.gwdg.de/index.php/s/iv2TOQwGy4FGDDZ) for
-    suggested MPM acquisition protocols.
-MTR:
-  name: Magnetization Transfer Ratio
-  description: |
-    This method is to calculate a semi-quantitative magnetization transfer ratio
-    map.
-MTRmap:
-  name: Magnetization transfer ratio image
-  description: |
-    In arbitrary units (arbitrary).
-    MTR maps are REQUIRED to use this suffix regardless of the method used to
-    generate them.
-    MTRmap intensity values are RECOMMENDED to be represented in percentage in
-    the range of 0-100%.
-  unit: arbitrary
-  minValue: 0
-  maxValue: 100
-MTS:
-  name: Magnetization transfer saturation
-  description: |
-    This method is to calculate a semi-quantitative magnetization transfer
-    saturation index map.
-    The MTS method involves three sets of anatomical images that differ in terms
-    of application of a magnetization transfer RF pulse (MTon or MToff) and flip
-    angle ([Helms et al. 2008](https://doi.org/10.1002/mrm.21732)).
-MTVmap:
-  name: Macromolecular tissue volume (MTV) image
-  description: |
-    In arbitrary units (arbitrary).
-    MTV maps are REQUIRED to use this suffix regardless of the method used to
-    generate them.
-  unit: arbitrary
-MTsat:
-  name: Magnetization transfer saturation image
-  description: |
-    In arbitrary units (arbitrary).
-    MTsat maps are REQUIRED to use this suffix regardless of the method used to
-    generate them.
-  unit: arbitrary
-MWFmap:
-  name: Myelin water fraction image
-  description: |
-    In arbitrary units (arbitrary).
-    MWF maps are REQUIRED to use this suffix regardless of the method used to
-    generate them.
-    MWF intensity values are RECOMMENDED to be represented in percentage in the
-    range of 0-100%.
-  unit: arbitrary
-  minValue: 0
-  maxValue: 100
-NLO:
-  name: Nonlinear optical microscopy
-  description: |
-    Nonlinear optical microscopy imaging data
-OCT:
-  name: Optical coherence tomography
-  description: |
-    Optical coherence tomography imaging data
-PC:
-  name: Phase-contrast microscopy
-  description: |
-    Phase-contrast microscopy imaging data
-PD:
-  name: Proton density image
-  description: |
-    Ambiguous, may refer to a parametric image or to a conventional image.
-    **Change:** Replaced by `PDw` or `PDmap`.
-  unit: arbitrary
-PDT2:
-  name: PD and T2 weighted image
-  description: |
-    In arbitrary units (arbitrary).
-    PDw and T2w images acquired using a dual echo FSE sequence through view
-    sharing process
-    ([Johnson et al. 1994](https://pubmed.ncbi.nlm.nih.gov/8010268/)).
-  unit: arbitrary
-PDT2map:
-  name: Combined PD/T2 image
-  description: |
-    In arbitrary units (arbitrary).
-    Combined PD/T2 maps are REQUIRED to use this suffix regardless of the method
-    used to generate them.
-  unit: arbitrary
-PDmap:
-  name: Proton density image
-  description: |
-    In arbitrary units (arbitrary).
-    PD maps are REQUIRED to use this suffix regardless of the method used to
-    generate them.
-  unit: arbitrary
-PDw:
-  name: Proton density (PD) weighted image
-  description: |
-    In arbitrary units (arbitrary).
-    The contrast of these images is mainly determined by spatial variations in
-    the spin density (1H) of the imaged specimen.
-    In spin-echo sequences this contrast is achieved at short repetition and long
-    echo times.
-    In a gradient-echo acquisition, PD weighting dominates the contrast at long
-    repetition and short echo times, and at small flip angles.
-  unit: arbitrary
-PLI:
-  name: Polarized-light microscopy
-  description: |
-    Polarized-light microscopy imaging data
-R1map:
-  name: Longitudinal relaxation rate image
-  description: |
-    In seconds<sup>-1</sup> (1/s).
-    R1 maps (R1 = 1/T1) are REQUIRED to use this suffix regardless of the method
-    used to generate them.
-  unit: 1/s
-R2map:
-  name: True transverse relaxation rate image
-  description: |
-    In seconds<sup>-1</sup> (1/s).
-    R2 maps (R2 = 1/T2) are REQUIRED to use this suffix regardless of the method
-    used to generate them.
-  unit: 1/s
-R2starmap:
-  name: Observed transverse relaxation rate image
-  description: |
-    In seconds<sup>-1</sup> (1/s).
-    R2-star maps (R2star = 1/T2star) are REQUIRED to use this suffix regardless
-    of the method used to generate them.
-  unit: 1/s
-RB1COR:
-  name: RB1COR
-  description: |
-    Low resolution images acquired by the body coil
-    (in the gantry of the scanner) and the head coil using identical acquisition
-    parameters to generate a combined sensitivity map as described in
-    [Papp et al. (2016)](https://doi.org/10.1002/mrm.26058).
-RB1map:
-  name: RF receive sensitivity map
-  description: |
-    In arbitrary units (arbitrary).
-    Radio frequency (RF) receive (B1-) sensitivity maps are REQUIRED to use this
-    suffix regardless of the method used to generate them.
-    RB1map intensity values are RECOMMENDED to be represented as percent
-    multiplicative factors such that Amplitude<sub>effective</sub> =
-    B1-<sub>intensity</sub>\*Amplitude<sub>ideal</sub>.
-  unit: arbitrary
-S0map:
-  name: Observed signal amplitude (S0) image
-  description: |
-    In arbitrary units (arbitrary).
-    For a multi-echo (typically fMRI) sequence, S0 maps index the baseline signal
-    before exponential (T2-star) signal decay.
-    In other words: the exponential of the intercept for a linear decay model
-    across log-transformed echos. For more information, please see, for example,
-    [the tedana documentation](https://tedana.readthedocs.io/en/latest/\
-    approach.html#monoexponential-decay-model-fit).
-    S0 maps are RECOMMENDED to use this suffix if derived from an ME-FMRI dataset.
-SEM:
-  name: Scanning electron microscopy
-  description: |
-    Scanning electron microscopy imaging data
-SPIM:
-  name: Selective plane illumination microscopy
-  description: |
-    Selective plane illumination microscopy imaging data
-SR:
-  name: Super-resolution microscopy
-  description: |
-    Super-resolution microscopy imaging data
-T1map:
-  name: Longitudinal relaxation time image
-  description: |
-    In seconds (s).
-    T1 maps are REQUIRED to use this suffix regardless of the method used to
-    generate them.
-    See [this interactive book on T1 mapping](https://qmrlab.org/t1_book/intro)
-    for further reading on T1-mapping.
-  unit: s
-T1rho:
-  name: T1 in rotating frame (T1 rho) image
-  description: |
-    In seconds (s).
-    T1-rho maps are REQUIRED to use this suffix regardless of the method used to
-    generate them.
-  unit: s
-T1w:
-  name: T1-weighted image
-  description: |
-    In arbitrary units (arbitrary).
-    The contrast of these images is mainly determined by spatial variations in
-    the longitudinal relaxation time of the imaged specimen.
-    In spin-echo sequences this contrast is achieved at relatively short
-    repetition and echo times.
-    To achieve this weighting in gradient-echo images, again, short repetition
-    and echo times are selected; however, at relatively large flip angles.
-    Another common approach to increase T1 weighting in gradient-echo images is
-    to add an inversion preparation block to the beginning of the imaging
-    sequence (for example, `TurboFLASH` or `MP-RAGE`).
-  unit: arbitrary
-T2map:
-  name: True transverse relaxation time image
-  description: |
-    In seconds (s).
-    T2 maps are REQUIRED to use this suffix regardless of the method used to
-    generate them.
-  unit: s
-T2star:
-  name: T2\* image
-  description: |
-    Ambiguous, may refer to a parametric image or to a conventional image.
-    **Change:** Replaced by `T2starw` or `T2starmap`.
-  anyOf:
-  - unit: arbitrary
-  - unit: s
-T2starmap:
-  name: Observed transverse relaxation time image
-  description: |
-    In seconds (s).
-    T2-star maps are REQUIRED to use this suffix regardless of the method used to
-    generate them.
-  unit: s
-T2starw:
-  name: T2star weighted image
-  description: |
-    In arbitrary units (arbitrary).
-    The contrast of these images is mainly determined by spatial variations in
-    the (observed) transverse relaxation time of the imaged specimen.
-    In spin-echo sequences, this effect is negated as the excitation is followed
-    by an inversion pulse.
-    The contrast of gradient-echo images natively depends on T2-star effects.
-    However, for T2-star variation to dominate the image contrast,
-    gradient-echo acquisitions are carried out at long repetition and echo times,
-    and at small flip angles.
-  unit: arbitrary
-T2w:
-  name: T2-weighted image
-  description: |
-    In arbitrary units (arbitrary).
-    The contrast of these images is mainly determined by spatial variations in
-    the (true) transverse relaxation time of the imaged specimen.
-    In spin-echo sequences this contrast is achieved at relatively long
-    repetition and echo times.
-    Generally, gradient echo sequences are not the most suitable option for
-    achieving T2 weighting, as their contrast natively depends on T2-star rather
-    than on T2.
-  unit: arbitrary
-TB1AFI:
-  name: TB1AFI
-  description: |
-    This method ([Yarnykh 2007](https://doi.org/10.1002/mrm.21120))
-    calculates a B1<sup>+</sup> map from two images acquired at interleaved (two)
-    TRs with identical RF pulses using a steady-state sequence.
-TB1DAM:
-  name: TB1DAM
-  description: |
-    The double-angle B1<sup>+</sup> method
-    ([Insko and Bolinger 1993](https://doi.org/10.1006/jmra.1993.1133)) is based
-    on the calculation of the actual angles from signal ratios,
-    collected by two acquisitions at different nominal excitation flip angles.
-    Common sequence types for this application include spin echo and echo planar
-    imaging.
-TB1EPI:
-  name: TB1EPI
-  description: |
-    This B1<sup>+</sup> mapping method
-    ([Jiru and Klose 2006](https://doi.org/10.1002/mrm.21083)) is based on two
-    EPI readouts to acquire spin echo (SE) and stimulated echo (STE) images at
-    multiple flip angles in one sequence, used in the calculation of deviations
-    from the nominal flip angle.
-TB1RFM:
-  name: TB1RFM
-  description: |
-    The result of a Siemens `rf_map` product sequence.
-    This sequence produces two images.
-    The first image appears like an anatomical image and the second output is a
-    scaled flip angle map.
-TB1SRGE:
-  name: TB1SRGE
-  description: |
-    Saturation-prepared with 2 rapid gradient echoes (SA2RAGE) uses a ratio of
-    two saturation recovery images with different time delays,
-    and a simulated look-up table to estimate B1+
-    ([Eggenschwiler et al. 2011](https://doi.org/10.1002/mrm.23145)).
-    This sequence can also be used in conjunction with MP2RAGE T1 mapping to
-    iteratively improve B1+ and T1 map estimation
-    ([Marques & Gruetter 2013](https://doi.org/10.1371/journal.pone.0069294)).
-TB1TFL:
-  name: TB1TFL
-  description: |
-    The result of a Siemens `tfl_b1_map` product sequence.
-    This sequence produces two images.
-    The first image appears like an anatomical image and the second output is a
-    scaled flip angle map.
-TB1map:
-  name: RF transmit field image
-  description: |
-    In arbitrary units (arbitrary).
-    Radio frequency (RF) transmit (B1+) field maps are REQUIRED to use this
-    suffix regardless of the method used to generate them.
-    TB1map intensity values are RECOMMENDED to be represented as percent
-    multiplicative factors such that FlipAngle<sub>effective</sub> =
-    B1+<sub>intensity</sub>\*FlipAngle<sub>nominal</sub> .
-  unit: arbitrary
-TEM:
-  name: Transmission electron microscopy
-  description: |
-    Transmission electron microscopy imaging data
-UNIT1:
-  name: Homogeneous (flat) T1-weighted MP2RAGE image
-  description: |
-    In arbitrary units (arbitrary).
-    UNIT1 images are REQUIRED to use this suffix regardless of the method used to
-    generate them.
-    Note that although this image is T1-weighted, regions without MR signal will
-    contain white salt-and-pepper noise that most segmentation algorithms will
-    fail on.
-    Therefore, it is important to dissociate it from `T1w`.
-    Please see [`MP2RAGE` specific notes](/99-appendices/11-qmri.html#unit1-images)
-    in the qMRI appendix for further information.
-VFA:
-  name: Variable flip angle
-  description: |
-    The VFA method involves at least two spoiled gradient echo (SPGR) of
-    steady-state free precession (SSFP) images acquired at different flip angles.
-    Depending on the provided metadata fields and the sequence type,
-    data may be eligible for DESPOT1, DESPOT2 and their variants
-    ([Deoni et al. 2005](https://doi.org/10.1002/mrm.20314)).
-angio:
-  name: Angiogram
-  description: |
-    Magnetic resonance angiography sequences focus on enhancing the contrast of
-    blood vessels (generally arteries, but sometimes veins) against other tissue
-    types.
-asl:
-  name: Arterial Spin Labeling
-  description: |
-    The complete ASL time series stored as a 4D NIfTI file in the original
-    acquisition order, with possible volume types including: control, label,
-    m0scan, deltam, cbf.
-aslcontext:
-  name: Arterial Spin Labeling Context
-  description: |
-    A TSV file defining the image types for volumes in an associated ASL file.
-asllabeling:
-  name: ASL Labeling Screenshot
-  description: |
-    An anonymized screenshot of the planning of the labeling slab/plane with
-    respect to the imaging slab or slices `*_asllabeling.jpg`.
-    Based on DICOM macro C.8.13.5.14.
-beh:
-  name: Behavioral recording
-  description: |
-    Behavioral recordings from tasks.
-    These files are similar to events files, but do not include the `"onset"` and
-    `"duration"` columns that are mandatory for events files.
-blood:
-  name: Blood recording data
-  description: |
-    Blood measurements of radioactivity stored in
-    [tabular files](/02-common-principles.html#tabular-files)
-    and located in the `pet/` directory along with the corresponding PET data.
-bold:
-  name: Blood-Oxygen-Level Dependent image
-  description: |
-    Blood-Oxygen-Level Dependent contrast (specialized T2\* weighting)
-cbv:
-  name: Cerebral blood volume image
-  description: |
-    Cerebral Blood Volume contrast (specialized T2\* weighting or difference between T1 weighted images)
-channels:
-  name: Channels File
-  description: |
-    Channel information.
-coordsystem:
-  name: Coordinate System File
-  description: |
-    A JSON document specifying the coordinate system(s) used for the MEG, EEG,
-    head localization coils, and anatomical landmarks.
-defacemask:
-  name: Defacing Mask
-  description: |
-    A binary mask that was used to remove facial features from an anatomical MRI
-    image.
-dwi:
-  name: Diffusion-weighted image
-  description: |
-    Diffusion-weighted imaging contrast (specialized T2 weighting).
-eeg:
-  name: Electroencephalography
-  description: |
-    Electroencephalography recording data.
-electrodes:
-  name: Electrodes
-  description: |
-    File that gives the location of (i)EEG electrodes.
-epi:
-  name: EPI
-  description: |
-    The phase-encoding polarity (PEpolar) technique combines two or more Spin Echo
-    EPI scans with different phase encoding directions to estimate the underlying
-    inhomogeneity/deformation map.
-events:
-  name: Events
-  description: |
-    Event timing information from a behavioral task.
-fieldmap:
-  name: Fieldmap
-  description: |
-    Some MR schemes such as spiral-echo imaging (SEI) sequences are able to
-    directly provide maps of the *B<sub>0</sub>* field inhomogeneity.
-headshape:
-  name: Headshape File
-  description: |
-    The 3-D locations of points that describe the head shape and/or electrode
-    locations can be digitized and stored in separate files.
-ieeg:
-  name: Intracranial Electroencephalography
-  description: |
-    Intracranial electroencephalography recording data.
-inplaneT1:
-  name: Inplane T1
-  description: |
-    In arbitrary units (arbitrary).
-    T1 weighted structural image matched to a functional (task) image.
-  unit: arbitrary
-inplaneT2:
-  name: Inplane T2
-  description: |
-    In arbitrary units (arbitrary).
-    T2 weighted structural image matched to a functional (task) image.
-  unit: arbitrary
-m0scan:
-  name: M0 image
-  description: |
-    The M0 image is a calibration image, used to estimate the equilibrium
-    magnetization of blood.
-magnitude:
-  name: Magnitude
-  description: |
-    Field-mapping MR schemes such as gradient-recalled echo (GRE) generate a
-    Magnitude image to be used for anatomical reference.
-    Requires the existence of Phase, Phase-difference or Fieldmap maps.
-magnitude1:
-  name: Magnitude
-  description: |
-    Magnitude map generated by GRE or similar schemes, associated with the first
-    echo in the sequence.
-magnitude2:
-  name: Magnitude
-  description: |
-    Magnitude map generated by GRE or similar schemes, associated with the second
-    echo in the sequence.
-markers:
-  name: MEG Sensor Coil Positions
-  description: |
-    Another manufacturer-specific detail pertains to the KIT/Yokogawa/Ricoh
-    system, which saves the MEG sensor coil positions in a separate file with two
-    possible filename extensions  (`.sqd`, `.mrk`).
-    For these files, the `markers` suffix MUST be used.
-    For example: `sub-01_task-nback_markers.sqd`
-meg:
-  name: Magnetoencephalography
-  description: |
-    Unprocessed MEG data stored in the native file format of the MEG instrument
-    with which the data was collected.
-pet:
-  name: Positron Emission Tomography
-  description: |
-    PET imaging data SHOULD be stored in 4D
-    (or 3D, if only one volume was acquired) NIfTI files with the `_pet` suffix.
-    Volumes MUST be stored in chronological order
-    (the order they were acquired in).
-phase:
-  name: Phase image
-  description: |
-    [DEPRECATED](/02-common-principles.html#definitions).
-    Phase information associated with magnitude information stored in BOLD
-    contrast.
-    This suffix should be replaced by the
-    [`part-phase`](/99-appendices/09-entities.html#part)
-    in conjunction with the `bold` suffix.
-  anyOf:
-  - unit: arbitrary
-  - unit: rad
-phase1:
-  name: Phase
-  description: |
-    Phase map generated by GRE or similar schemes, associated with the first
-    echo in the sequence.
-phase2:
-  name: Phase
-  description: |
-    Phase map generated by GRE or similar schemes, associated with the second
-    echo in the sequence.
-phasediff:
-  name: Phase-difference
-  description: |
-    Some scanners subtract the `phase1` from the `phase2` map and generate a
-    unique `phasediff` file.
-    For instance, this is a common output for the built-in fieldmap sequence of
-    Siemens scanners.
-photo:
-  name: Photo File
-  description: |
-    Photos of the anatomical landmarks, head localization coils or tissue sample.
-physio:
-  name: Physiological recording
-  description: |
-    Physiological recordings such as cardiac and respiratory signals.
-sbref:
-  name: Single-band reference image
-  description: |
-    Single-band reference for one or more multi-band `dwi` images.
-scans:
-  name: Scans file
-  description: |
-    The purpose of this file is to describe timing and other properties of each imaging acquisition
-    sequence (each run file) within one session.
-    Each neural recording file SHOULD be described by exactly one row. Some recordings consist of
-    multiple parts, that span several files, for example through echo-, part-, or split- entities.
-    Such recordings MUST be documented with one row per file.
-    Relative paths to files should be used under a compulsory filename header.
-    If acquisition time is included it should be listed under the acq_time header.
-    Acquisition time refers to when the first data point in each run was acquired.
-    Furthermore, if this header is provided, the acquisition times of all files that belong to a
-    recording MUST be identical.
-    Datetime should be expressed as described in Units.
-    Additional fields can include external behavioral measures relevant to the scan.
-    For example vigilance questionnaire score administered after a resting state scan.
-    All such included additional fields SHOULD be documented in an accompanying _scans.json file
-    that describes these fields in detail (see Tabular files).
-sessions:
-  name: Sessions file
-  description: |
-    In case of multiple sessions there is an option of adding additional sessions.tsv files
-    describing variables changing between sessions.
-    In such case one file per participant SHOULD be added.
-    These files MUST include a session_id column and describe each session by one and only one row.
-    Column names in sessions.tsv files MUST be different from group level participant key column
-    names in the participants.tsv file.
-stim:
-  name: Continuous recording
-  description: |
-    Continuous measures, such as parameters of a film or audio stimulus.
-uCT:
-  name: Micro-CT
-  description: |
-    Micro-CT imaging data
diff --git a/dandi/support/bids/schemadata/1.7.0+012+dandi001/objects/top_level_files.yaml b/dandi/support/bids/schemadata/1.7.0+012+dandi001/objects/top_level_files.yaml
deleted file mode 100644
index 79eab838c..000000000
--- a/dandi/support/bids/schemadata/1.7.0+012+dandi001/objects/top_level_files.yaml
+++ /dev/null
@@ -1,110 +0,0 @@
----
-# This file describes files which may appear at the top level of a dataset.
-# This does not include information about whether these files are required or optional.
-# For that information, see `rules/top_level_files.yaml`.
-CHANGES:
-  name: CHANGES
-  description: |
-    Version history of the dataset (describing changes, updates and corrections) MAY be provided in
-    the form of a `CHANGES` text file.
-    This file MUST follow the
-    [CPAN Changelog convention](https://metacpan.org/pod/release/HAARG/CPAN-Changes-0.400002/lib/\
-    CPAN/Changes/Spec.pod).
-    The `CHANGES` file MUST be either in ASCII or UTF-8 encoding.
-LICENSE:
-  name: LICENSE
-  description: |
-    A `LICENSE` file MAY be provided in addition to the short specification of the
-    used license in the `dataset_description.json` `"License"` field.
-    The `"License"` field and `LICENSE` file MUST correspond.
-    The `LICENSE` file MUST be either in ASCII or UTF-8 encoding.
-README:
-  name: README
-  description: |
-    In addition a free form text file (`README`) describing the dataset in more details SHOULD be
-    provided.
-    The `README` file MUST be either in ASCII or UTF-8 encoding.
-dataset_description:
-  name: Dataset Description
-  description: |
-    The file `dataset_description.json` is a JSON file describing the dataset.
-genetic_info:
-  name: Genetic Information
-  description: |
-    The `genetic_info.json` file describes the genetic information available in the
-    `participants.tsv` file and/or the genetic database described in
-    `dataset_description.json`.
-    Datasets containing the `Genetics` field in `dataset_description.json` or the
-    `genetic_id` column in `participants.tsv` MUST include this file.
-participants:
-  name: Participant Information
-  description: |
-    The purpose of this RECOMMENDED file is to describe properties of participants
-    such as age, sex, handedness.
-    If this file exists, it MUST contain the column `participant_id`,
-    which MUST consist of `sub-<label>` values identifying one row for each participant,
-    followed by a list of optional columns describing participants.
-    Each participant MUST be described by one and only one row.
-
-    Commonly used *optional* columns in `participant.tsv` files are `age`, `sex`,
-    and `handedness`. We RECOMMEND to make use of these columns, and
-    in case that you do use them, we RECOMMEND to use the following values
-    for them:
-
-    -   `age`: numeric value in years (float or integer value)
-
-    -   `sex`: string value indicating phenotypical sex, one of "male", "female",
-        "other"
-
-        -   for "male", use one of these values: `male`, `m`, `M`, `MALE`, `Male`
-
-        -   for "female", use one of these values: `female`, `f`, `F`, `FEMALE`,
-            `Female`
-
-        -   for "other", use one of these values: `other`, `o`, `O`, `OTHER`,
-            `Other`
-
-    -   `handedness`: string value indicating one of "left", "right",
-        "ambidextrous"
-
-        -   for "left", use one of these values: `left`, `l`, `L`, `LEFT`, `Left`
-
-        -   for "right", use one of these values: `right`, `r`, `R`, `RIGHT`,
-            `Right`
-
-        -   for "ambidextrous", use one of these values: `ambidextrous`, `a`, `A`,
-            `AMBIDEXTROUS`, `Ambidextrous`
-
-    Throughout BIDS you can indicate missing values with `n/a` (for "not
-    available").
-
-samples:
-  name: Sample Information
-  description: |
-    The purpose of this file is to describe properties of samples, indicated by the `sample` entity.
-    This file is REQUIRED if `sample-<label>` is present in any file name within the dataset.
-    If this file exists, it MUST contain the three following columns:
-
-    -   `sample_id`: MUST consist of `sample-<label>` values identifying one row
-        for each sample
-
-    -   `participant_id`: MUST consist of `sub-<label>`
-
-    -   `sample_type`: MUST consist of sample type values, either `cell line`, `in vitro differentiated cells`,
-        `primary cell`, `cell-free sample`, `cloning host`, `tissue`, `whole organisms`, `organoid` or
-        `technical sample` from [ENCODE Biosample Type](https://www.encodeproject.org/profiles/biosample_type)
-
-    Other optional columns MAY be used to describe the samples.
-    Each sample MUST be described by one and only one row.
-
-    Commonly used *optional* columns in `samples.tsv` files are `pathology` and
-    `derived_from`. We RECOMMEND to make use of these columns, and in case that
-    you do use them, we RECOMMEND to use the following values for them:
-
-    -   `pathology`: string value describing the pathology of the sample or type of control.
-        When different from `healthy`, pathology SHOULD be specified in `samples.tsv`.
-        The pathology MAY instead be specified in
-        [Sessions files](../03-modality-agnostic-files.md#sessions-file) in case it changes over time.
-
-    -   `derived_from`: `sample-<label>` key/value pair from which a sample is derived from,
-        for example a slice of tissue (`sample-02`) derived from a block of tissue (`sample-01`)
diff --git a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/associated_data.yaml b/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/associated_data.yaml
deleted file mode 100644
index 609fcafaa..000000000
--- a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/associated_data.yaml
+++ /dev/null
@@ -1,11 +0,0 @@
----
-# This file describes the requirement levels of folders which may appear
-# within a dataset folder without following BIDS format.
-code:
-  required: false
-derivatives:
-  required: false
-sourcedata:
-  required: false
-stimuli:
-  required: false
diff --git a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/anat.yaml b/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/anat.yaml
deleted file mode 100644
index b1a470c2e..000000000
--- a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/anat.yaml
+++ /dev/null
@@ -1,183 +0,0 @@
----
-# Nonparametric
-- suffixes:
-  - T1w
-  - T2w
-  - PDw
-  - T2starw
-  - FLAIR
-  - inplaneT1
-  - inplaneT2
-  - PDT2
-  - angio
-  - T2star  # deprecated
-  - FLASH  # deprecated
-  - PD  # deprecated
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  entities:
-    subject: required
-    session: optional
-    run: optional
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    part: optional
-
-# Parametric
-- suffixes:
-  - T1map
-  - T2map
-  - T2starmap
-  - R1map
-  - R2map
-  - R2starmap
-  - PDmap
-  - MTRmap
-  - MTsat
-  - UNIT1
-  - T1rho
-  - MWFmap
-  - MTVmap
-  - PDT2map
-  - Chimap
-  - S0map
-  - M0map
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  entities:
-    subject: required
-    session: optional
-    run: optional
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-
-# Defacemask
-- suffixes:
-  - defacemask
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  entities:
-    subject: required
-    session: optional
-    run: optional
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    modality: optional
-
-# Multi-echo
-- suffixes:
-  - MESE
-  - MEGRE
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  entities:
-    subject: required
-    session: optional
-    run: optional
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    echo: required
-    part: optional
-
-# Multi-flip
-- suffixes:
-  - VFA
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  entities:
-    subject: required
-    session: optional
-    run: optional
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    echo: optional
-    flip: required
-    part: optional
-
-# Multi-inv
-- suffixes:
-  - IRT1
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  entities:
-    subject: required
-    session: optional
-    run: optional
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    inversion: required
-    part: optional
-
-# MP2RAGE
-- suffixes:
-  - MP2RAGE
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  entities:
-    subject: required
-    session: optional
-    run: optional
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    echo: optional
-    flip: optional
-    inversion: required
-    part: optional
-
-# VFA+MT
-- suffixes:
-  - MPM
-  - MTS
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  entities:
-    subject: required
-    session: optional
-    run: optional
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    echo: optional
-    flip: required
-    mtransfer: required
-    part: optional
-
-# MTR
-- suffixes:
-  - MTR
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  entities:
-    subject: required
-    session: optional
-    run: optional
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    mtransfer: required
-    part: optional
diff --git a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/beh.yaml b/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/beh.yaml
deleted file mode 100644
index 59358b59b..000000000
--- a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/beh.yaml
+++ /dev/null
@@ -1,29 +0,0 @@
----
-# Continuous data
-- suffixes:
-  - stim
-  - physio
-  extensions:
-  - .tsv.gz
-  - .json
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    run: optional
-    recording: optional
-
-# Non-continuous data
-- suffixes:
-  - events
-  - beh
-  extensions:
-  - .tsv
-  - .json
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    run: optional
diff --git a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/dwi.yaml b/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/dwi.yaml
deleted file mode 100644
index dfb178760..000000000
--- a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/dwi.yaml
+++ /dev/null
@@ -1,48 +0,0 @@
----
-# DWI
-- suffixes:
-  - dwi
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  - .bvec
-  - .bval
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-    direction: optional
-    run: optional
-    part: optional
-
-# Single-band reference images
-- suffixes:
-  - sbref
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-    direction: optional
-    run: optional
-    part: optional
-
-# Timeseries
-- suffixes:
-  - physio
-  - stim
-  extensions:
-  - .tsv.gz
-  - .json
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-    direction: optional
-    run: optional
-    part: optional
-    recording: optional
diff --git a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/eeg.yaml b/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/eeg.yaml
deleted file mode 100644
index 6b112e343..000000000
--- a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/eeg.yaml
+++ /dev/null
@@ -1,87 +0,0 @@
----
-- suffixes:
-  - eeg
-  extensions:
-  - .json
-  - .edf
-  - .vhdr
-  - .vmrk
-  - .eeg
-  - .set
-  - .fdt
-  - .bdf
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    run: optional
-
-- suffixes:
-  - channels
-  extensions:
-  - .json
-  - .tsv
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    run: optional
-
-- suffixes:
-  - coordsystem
-  extensions:
-  - .json
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-    space: optional
-
-- suffixes:
-  - electrodes
-  extensions:
-  - .json
-  - .tsv
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-    space: optional
-
-- suffixes:
-  - events
-  extensions:
-  - .json
-  - .tsv
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    run: optional
-
-- suffixes:
-  - photo
-  extensions:
-  - .jpg
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-
-# Timeseries
-- suffixes:
-  - physio
-  - stim
-  extensions:
-  - .tsv.gz
-  - .json
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    run: optional
-    recording: optional
diff --git a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/fmap.yaml b/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/fmap.yaml
deleted file mode 100644
index 2c445196d..000000000
--- a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/fmap.yaml
+++ /dev/null
@@ -1,129 +0,0 @@
----
-# Fieldmaps
-- suffixes:
-  - phasediff
-  - phase1
-  - phase2
-  - magnitude1
-  - magnitude2
-  - magnitude
-  - fieldmap
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-    run: optional
-
-# PEPolar
-- suffixes:
-  - epi
-  - m0scan
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-    ceagent: optional
-    direction: required
-    run: optional
-
-# TB1DAM
-- suffixes:
-  - TB1DAM
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  entities:
-    subject: required
-    session: optional
-    run: optional
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    flip: required
-    inversion: optional
-    part: optional
-
-# TB1EPI
-- suffixes:
-  - TB1EPI
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  entities:
-    subject: required
-    session: optional
-    run: optional
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    echo: required
-    flip: required
-    inversion: optional
-    part: optional
-
-# RFFieldMaps
-- suffixes:
-  - TB1AFI
-  - TB1TFL
-  - TB1RFM
-  - RB1COR
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  entities:
-    subject: required
-    session: optional
-    run: optional
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    echo: optional
-    flip: optional
-    inversion: optional
-    part: optional
-
-# TB1SRGE
-- suffixes:
-  - TB1SRGE
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  entities:
-    subject: required
-    session: optional
-    run: optional
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    echo: optional
-    flip: required
-    inversion: required
-    part: optional
-
-# Parametric
-- suffixes:
-  - TB1map
-  - RB1map
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  entities:
-    subject: required
-    session: optional
-    run: optional
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
diff --git a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/func.yaml b/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/func.yaml
deleted file mode 100644
index 1fbdca7b5..000000000
--- a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/func.yaml
+++ /dev/null
@@ -1,73 +0,0 @@
----
-# Func
-- suffixes:
-  - bold
-  - cbv
-  - sbref
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    direction: optional
-    run: optional
-    echo: optional
-    part: optional
-
-# Phase (deprecated)
-- suffixes:
-  - phase  # deprecated
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    direction: optional
-    run: optional
-    echo: optional
-
-# Events
-- suffixes:
-  - events
-  extensions:
-  - .tsv
-  - .json
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    direction: optional
-    run: optional
-
-# Timeseries
-- suffixes:
-  - physio
-  - stim
-  extensions:
-  - .tsv.gz
-  - .json
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    direction: optional
-    run: optional
-    recording: optional
diff --git a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/ieeg.yaml b/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/ieeg.yaml
deleted file mode 100644
index 37c02963f..000000000
--- a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/ieeg.yaml
+++ /dev/null
@@ -1,88 +0,0 @@
----
-- suffixes:
-  - ieeg
-  extensions:
-  - .mefd/
-  - .json
-  - .edf
-  - .vhdr
-  - .eeg
-  - .vmrk
-  - .set
-  - .fdt
-  - .nwb
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    run: optional
-
-- suffixes:
-  - channels
-  extensions:
-  - .json
-  - .tsv
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    run: optional
-
-- suffixes:
-  - coordsystem
-  extensions:
-  - .json
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-    space: optional
-
-- suffixes:
-  - electrodes
-  extensions:
-  - .json
-  - .tsv
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-    space: optional
-
-- suffixes:
-  - events
-  extensions:
-  - .json
-  - .tsv
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    run: optional
-
-- suffixes:
-  - photo
-  extensions:
-  - .jpg
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-
-# Timeseries
-- suffixes:
-  - physio
-  - stim
-  extensions:
-  - .tsv.gz
-  - .json
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    run: optional
-    recording: optional
diff --git a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/meg.yaml b/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/meg.yaml
deleted file mode 100644
index 104689b7f..000000000
--- a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/meg.yaml
+++ /dev/null
@@ -1,141 +0,0 @@
----
-# MEG data files
-# First group
-- suffixes:
-  - meg
-  extensions:
-  - /  # corresponds to BTi/4D data
-  - .ds/
-  - .json
-  - .fif
-  - .sqd
-  - .con
-  - .raw
-  - .ave
-  - .mrk
-  - .kdf
-  - .mhd
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    run: optional
-    processing: optional
-    split: optional
-
-# Second group
-# Specifically, it's dat files with "acq-calibration"
-- suffixes:
-  - meg
-  extensions:
-  - .dat
-  entities:
-    subject: required
-    session: optional
-    acquisition:
-      requirement: required
-      type: string
-      enum:
-      - calibration
-
-# Third group
-# fif files with "acq-crosstalk"
-- suffixes:
-  - meg
-  extensions:
-  - .fif
-  entities:
-    subject: required
-    session: optional
-    acquisition:
-      requirement: required
-      type: string
-      enum:
-      - crosstalk
-
-# Headshape files
-- suffixes:
-  - headshape
-  extensions:
-  - "*"
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-
-# Marker files
-- suffixes:
-  - markers
-  extensions:
-  - .sqd
-  - .mrk
-  entities:
-    subject: required
-    session: optional
-    task: optional
-    acquisition: optional
-    space: optional
-
-# Coordinate systems
-- suffixes:
-  - coordsystem
-  extensions:
-  - .json
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-
-# Channel files
-- suffixes:
-  - channels
-  extensions:
-  - .json
-  - .tsv
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    run: optional
-    processing: optional
-
-# Events files
-- suffixes:
-  - events
-  extensions:
-  - .json
-  - .tsv
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    run: optional
-
-# Head photos
-- suffixes:
-  - photo
-  extensions:
-  - .jpg
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-
-# Timeseries
-- suffixes:
-  - physio
-  - stim
-  extensions:
-  - .tsv.gz
-  - .json
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    run: optional
-    processing: optional
-    recording: optional
diff --git a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/micr.yaml b/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/micr.yaml
deleted file mode 100644
index 263326e28..000000000
--- a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/micr.yaml
+++ /dev/null
@@ -1,48 +0,0 @@
----
-# Microscopy
-- suffixes:
-  - TEM
-  - SEM
-  - uCT
-  - BF
-  - DF
-  - PC
-  - DIC
-  - FLUO
-  - CONF
-  - PLI
-  - CARS
-  - 2PE
-  - MPE
-  - SR
-  - NLO
-  - OCT
-  - SPIM
-  extensions:
-  - .ome.tif
-  - .ome.btf
-  - .png
-  - .tif
-  - .json
-  - .h5
-  - .ngff
-  entities:
-    subject: required
-    session: optional
-    sample: required
-    acquisition: optional
-    stain: optional
-    run: optional
-    chunk: optional
-
-- suffixes:
-  - photo
-  extensions:
-  - .jpg
-  - .png
-  - .tif
-  entities:
-    subject: required
-    session: optional
-    sample: required
-    acquisition: optional
diff --git a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/perf.yaml b/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/perf.yaml
deleted file mode 100644
index 14b4ffe40..000000000
--- a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/perf.yaml
+++ /dev/null
@@ -1,58 +0,0 @@
----
-# First group
-- suffixes:
-  - asl
-  - m0scan
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-    reconstruction: optional
-    direction: optional
-    run: optional
-
-# Second group
-- suffixes:
-  - aslcontext
-  extensions:
-  - .tsv
-  - .json
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-    reconstruction: optional
-    direction: optional
-    run: optional
-
-# Third group
-- suffixes:
-  - asllabeling
-  extensions:
-  - .jpg
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-    reconstruction: optional
-    run: optional
-
-# Timeseries
-- suffixes:
-  - physio
-  - stim
-  extensions:
-  - .tsv.gz
-  - .json
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-    reconstruction: optional
-    direction: optional
-    run: optional
-    recording: optional
diff --git a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/pet.yaml b/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/pet.yaml
deleted file mode 100644
index 33f1a9f3e..000000000
--- a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/datatypes/pet.yaml
+++ /dev/null
@@ -1,60 +0,0 @@
----
-# PET recordings
-- suffixes:
-  - pet
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  entities:
-    subject: required
-    session: optional
-    task: optional
-    tracer: optional
-    reconstruction: optional
-    run: optional
-
-# Blood recordings
-- suffixes:
-  - blood
-  extensions:
-  - .tsv
-  - .json
-  entities:
-    subject: required
-    session: optional
-    task: optional
-    tracer: optional
-    reconstruction: optional
-    run: optional
-    recording: required
-
-# Events
-- suffixes:
-  - events
-  extensions:
-  - .tsv
-  - .json
-  entities:
-    subject: required
-    session: optional
-    task: required
-    tracer: optional
-    reconstruction: optional
-    run: optional
-
-# Timeseries
-- suffixes:
-  - physio
-  - stim
-  extensions:
-  - .tsv.gz
-  - .json
-  entities:
-    subject: required
-    session: optional
-    task: optional
-    tracer: optional
-    reconstruction: optional
-    run: optional
-    recording: optional
diff --git a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/entities.yaml b/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/entities.yaml
deleted file mode 100644
index 08209723e..000000000
--- a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/entities.yaml
+++ /dev/null
@@ -1,31 +0,0 @@
----
-# This file simply defines the order in which entities should appear within filenames.
-# Entity definitions appear in the `objects/entities.yaml` file.
-- subject
-- session
-- sample
-- task
-- acquisition
-- ceagent
-- tracer
-- stain
-- reconstruction
-- direction
-- run
-- modality
-- echo
-- flip
-- inversion
-- mtransfer
-- part
-- processing
-- hemisphere
-- space
-- split
-- recording
-- chunk
-- atlas
-- resolution
-- density
-- label
-- description
diff --git a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/modalities.yaml b/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/modalities.yaml
deleted file mode 100644
index 04b24489d..000000000
--- a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/modalities.yaml
+++ /dev/null
@@ -1,27 +0,0 @@
----
-# This file defines which data types fall under each modality.
-mri:
-  datatypes:
-  - anat
-  - dwi
-  - fmap
-  - func
-  - perf
-eeg:
-  datatypes:
-  - eeg
-ieeg:
-  datatypes:
-  - ieeg
-meg:
-  datatypes:
-  - meg
-beh:
-  datatypes:
-  - beh
-pet:
-  datatypes:
-  - pet
-micr:
-  datatypes:
-  - micr
diff --git a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/tabular_metadata.yaml b/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/tabular_metadata.yaml
deleted file mode 100644
index e04d10c1f..000000000
--- a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/tabular_metadata.yaml
+++ /dev/null
@@ -1,20 +0,0 @@
----
-# scans.tsv
-- suffixes:
-  - scans
-  extensions:
-  - .tsv
-  - .json
-  entities:
-    subject: required
-    # session is required if session is present in the dataset.
-    session: optional
-# sessions.tsv
-# This file may only exist if session is present in the dataset.
-- suffixes:
-  - sessions
-  extensions:
-  - .tsv
-  - .json
-  entities:
-    subject: required
diff --git a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/top_level_files.yaml b/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/top_level_files.yaml
deleted file mode 100644
index f24133deb..000000000
--- a/dandi/support/bids/schemadata/1.7.0+012+dandi001/rules/top_level_files.yaml
+++ /dev/null
@@ -1,31 +0,0 @@
----
-README:
-  required: true
-  extensions:
-  - None
-CHANGES:
-  required: true
-  extensions:
-  - None
-LICENSE:
-  required: false
-  extensions:
-  - None
-dataset_description:
-  required: true
-  extensions:
-  - .json
-genetic_info:
-  required: false
-  extensions:
-  - .json
-participants:
-  required: false
-  extensions:
-  - .tsv
-  - .json
-samples:
-  required: false
-  extensions:
-  - .tsv
-  - .json
diff --git a/dandi/support/bids/schemadata/1.7.0+369/README.md b/dandi/support/bids/schemadata/1.7.0+369/README.md
deleted file mode 100644
index 81e3b9d63..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/README.md
+++ /dev/null
@@ -1,519 +0,0 @@
-# BIDS-schema
-
-Portions of the BIDS specification are defined using YAML files in order to
-make the specification machine-readable.
-
-Currently the portions of the specification that rely on this schema are
-the entity tables, entity definitions, filename templates, and metadata tables.
-Any changes to the specification should be mirrored in the schema.
-
-## The format of the schema
-
-The schema is divided into two parts: the object definitions and the rules.
-
-The object definitions (files in `objects/`) describe attributes of individual
-objects or data types in the specification.
-Common information in these files includes full names, descriptions, and
-constraints on valid values.
-These files **do not** describe how objects of different types
-(for example file suffixes and file entities) interact with one another, or
-whether objects are required in a given dataset or file.
-
-The rules (files in `rules/`) describe how objects related to one another,
-as well as their requirement levels.
-
-## Object files
-
-The types of objects currently supported in the schema are:
-
--   modalities,
--   datatypes,
--   entities,
--   suffixes,
--   metadata,
--   top-level files,
--   and non-BIDS associated directories.
-
-Each of these object types has a single file in the `objects/` directory.
-
--   `modalities.yaml`: The modalities, or types of technology, used to acquire data in a BIDS dataset.
-    These modalities are not reflected directly in the specification.
-    For example, while both fMRI and DWI data are acquired with an MRI,
-    in a BIDS dataset they are stored in different directories reflecting the two different `datatypes`.
-
--   `datatypes.yaml`: Data types supported by the specification.
-    The only information provided in the file is:
-
-    1.  a full list of valid BIDS datatypes
-    1.  each datatype's full name
-    1.  a free text description of the datatype.
-
--   `entities.yaml`: Entities (key-value pairs in directory and filenames).
-
--   `metadata.yaml`: All valid metadata fields that are explicitly supported in BIDS sidecar JSON files.
-
--   `columns.yaml`: All valid columns that are explicitly supported in BIDS TSV files.
-
--   `suffixes.yaml`: Valid file suffixes.
-
--   `top_level_files.yaml`: Valid top-level files which may appear in a BIDS dataset.
-
--   `associated_data.yaml`: Directories that may appear within a dataset directory without following BIDS rules.
-
-### On re-used objects with different definitions
-
-If an object may mean something different depending on where it is used within the specification,
-then this must be reflected in the schema.
-Specifically, each version of the object must have its own definition within the relevant file.
-However, since object files are organized as dictionaries, each object must have a unique key.
-Thus, we append a suffix to each re-used object's key in order to make it unique.
-For objects with `CamelCase` names (for example, metadata fields), the suffix will start with a single underscore (`_`).
-For objects with `snake_case` names, two underscores must be used.
-
-There should also be a comment near the object definition in the YAML file describing the nature of the different objects.
-
-For example, the TSV column `"reference"` means different things when used for EEG data, as compared to iEEG data.
-As such, there are two definitions in `columns.yaml` for the `"reference"` column: `"reference__eeg"` and `"reference__ieeg"`.
-
-```yaml
-# reference column for channels.tsv files for EEG data
-reference__eeg:
-  name: reference
-  description: |
-    Name of the reference electrode(s).
-    This column is not needed when it is common to all channels.
-    In that case the reference electrode(s) can be specified in `*_eeg.json` as `EEGReference`).
-  type: string
-# reference column for channels.tsv files for iEEG data
-reference__ieeg:
-  name: reference
-  description: |
-    Specification of the reference (for example, 'mastoid', 'ElectrodeName01', 'intracranial', 'CAR', 'other', 'n/a').
-    If the channel is not an electrode channel (for example, a microphone channel) use `n/a`.
-  anyOf:
-  - type: string
-  - type: string
-    enum:
-    - n/a
-```
-
-When adding new object definitions to the schema,
-every effort should be made to find a shared, common definition for the term, should it already exist.
-If the differences between two versions of the same object are subtle or driven by context,
-then you can generally _append_ additional text to the object definition within the associated rendered table in the specification,
-rather than creating a separate entry in the schema.
-
-### `modalities.yaml`
-
-This file contains a dictionary in which each modality is defined.
-Keys are modality abbreviations (for example, `mri` for magnetic resonance imaging),
-and each associated value is a dictionary with two keys: `name` and `description`.
-
-The `name` field is the full name of the modality.
-The `description` field is a freeform description of the modality.
-
-### `datatypes.yaml`
-
-This file contains a dictionary in which each datatype is defined.
-Keys are the directory names associated with each datatype (for example, `anat` for anatomical MRI),
-and each associated value is a dictionary with two keys: `name` and `description`.
-
-The `name` field is the full name of the datatype.
-The `description` field is a freeform description of the datatype.
-
-### `entities.yaml`
-
-This file contains a dictionary in which each entity (key-value pair in filenames) is defined.
-Keys are long-form versions of the entities, which are distinct from both the entities as
-they appear in filenames _and_ their full names.
-For example, the key for the "Contrast Enhancing Agent" entity, which appears in filenames as `ce-<label>`,
-is `ceagent`.
-These keys are also the recommended variable names for their associated entities in BIDS-compliant code,
-since many entities (such as `ce`) have very short filename elements.
-Each key's associated value is a dictionary with five keys:
-
--   `name`,
--   `entity`,
--   `description`,
--   `type`,
--   and either `format` or `enum`.
-
-The `name` field is the full name of the entity. For example, the `name` for `ceagent` is "Contrast Enhancing Agent".
-
-The `entity` field is the entity as it appears in filenames. For example, the `entity` for `ceagent` is `ce`.
-
-The `description` field is a freeform description of the entity.
-The description should apply to _all_ uses of the entity,
-so if there is some additional information about the entity that applies specifically to a subset of suffixes or datatypes,
-then that information should be provided in the specification, rather than the schema.
-
-The `type` field defines the representation type for the value associated with the entity.
-Given that all entities appear in filenames, they should all be strings and the `type` field should always be `string`.
-This is true of both alphanumeric entities (such as `acq-desc`) and numeric ones (such as `run-1`).
-
-The `format` field defines the specific format the value should take.
-Entities are broadly divided into either `label` or `index` types.
-
-When `format` is `index`, then the entity's associated value should be a non-zero integer, optionally with leading zeros.
-For example, `run` should have an index, so a valid entity would be `run-01`.
-
-When `format` is `label`, then the value should be an alphanumeric string.
-Beyond limitations on which characters are allowed, labels have few restrictions.
-For example, `acq` should have a label, so a valid entity might be `acq-someLabel`.
-
-For a small number of entities, only certain labels are allowed.
-In those cases, instead of a `format` field, there will be an `enum` field, which will provide a list of allowed values.
-
-### `metadata.yaml`
-
-This file contains definitions for all metadata fields (fields which may appear in sidecar JSON files)
-currently supported in BIDS.
-
-Entries in this file contain, at minimum, the following fields: `name`,
-`description`, and a set of fields for describing the field's data type.
-
-The data types include:
-
--   `type`, which MUST have a value of `array`,
--   `string`,
--   `integer`,
--   `number`,
--   `object`,
--   or `boolean`.
-
-There are additional fields which may define rules that apply to a given type.
-
--   `array`: If `type` is `array`, then there MUST be an `items` field at
-    the same level as `type`. `items` describes the data type and rules that
-    apply to the individual items in the array. The same rules that apply to
-    describing data types for the field itself apply to `items`.
-    Additionally, there may be any of the following fields at the same level
-    as `type`: `minItems`, `maxItems`.
-    Here is an example of a field that MUST have three `integer` items:
-    ```yaml
-    ExampleField:
-        name: ExampleField
-        description: |
-            The description of "ExampleField".
-        type: array
-        minItems: 3
-        maxItems: 3
-        items:
-            type: integer
-    ```
-
--   `string`: If `type` is `string`, then there MAY be any of the following
-    fields at the same level as `type`: `pattern`, `format`, and `enum`.
-
-    -   `pattern` defines a regular expression for valid string names.
-
-    -   `format` defines the format for the string at the same level as `type`.
-        Valid values for `format` include:
-
-       -   `uri` (uniform resource identifiers),
-
-       -   `date` (date-times),
-
-       -   `unit` (standard units),
-
-       -   `dataset_relative` (relative paths from dataset root),
-
-       -   `participant_relative` (relative paths from participant directory).
-
-    -   `enum` defines a list of valid values for the field.
-        The minimum string length (`minLength`) defaults to 1.
-        Here is an example of a field with a restricted set of possible values:
-        ```yaml
-        ExampleField:
-            name: ExampleField
-            description: |
-                The description of "ExampleField".
-            type: string
-            enum:
-                - PossibleValue1
-                - PossibleValue2
-        ```
-
--   `integer`: If `type` is `integer`, then there MAY be any of the
-    following fields at the same level as `type`: `unit`,
-    `minimum` (inclusive minimum), `maximum` (inclusive maximum),
-    `exclusiveMinimum`, `exclusiveMaximum`.
-    Here is an example of a field with a minimum value of 0:
-    ```yaml
-    ExampleField:
-        name: ExampleField
-        description: |
-            The description of "ExampleField".
-        type: integer
-        minimum: 0
-    ```
-
--   `number`: If `type` is `number`, then there MAY be any of the following
-    fields at the same level as `type`: `unit`,
-    `minimum` (inclusive minimum), `maximum` (inclusive maximum),
-    `exclusiveMinimum`, `exclusiveMaximum`.
-    Here is an example of a field with a minimum of 0, in units of
-    kilometers per second:
-    ```yaml
-    ExampleField:
-        name: ExampleField
-        description: |
-            The description of "ExampleField".
-        type: number
-        minimum: 0
-        # k stands for "kilo", m stands for "meter", "/" means "per", and
-        # s stands for "seconds"
-        unit: km/s
-    ```
-
--   `object`: If `type` is `object`, then there MAY be any of the following
-    fields at the same level as `type`: `additionalProperties`,
-    `properties`.
-    Objects are defined as sets of key-value pairs.
-    Keys MUST be strings, while values may have specific attributes,
-    which is what `additionalProperties` describes.
-    Here is an example of a field which MUST be an object,
-    with one optional field named "OptionalField" that MUST be a `string`
-    and any number of additional optional fields that MUST be `number`s.
-    ```yaml
-    ExampleField:
-        name: ExampleField
-        description: |
-            The description of "ExampleField".
-        type: object
-        properties:
-            OptionalField:
-                type: string
-        additionalProperties:
-            type: number
-    ```
-
--   `boolean`: If `type` is `boolean`, then the field's value MUST be one
-    of: `true`, `false`. Here is an example:
-    ```yaml
-    ExampleField:
-        name: ExampleField
-        description: |
-            The description of "ExampleField".
-        type: boolean
-    ```
-
-Additionally, if multiple data types are possible for a given field
-(for example, if a field may be a `number` or an `array` of `number`s),
-then an `anyOf` field MUST be used, in which an array of data type
-descriptions MUST be defined.
-Here is an example of one such case:
-```yaml
-ExampleField:
-    name: ExampleField
-    description: |
-        The description of "ExampleField".
-    anyOf:
-        - type: number
-        - type: array
-            items:
-            type: number
-```
-
-Furthermore, if the data type description of a field is reused across fields,
-then it may be defined in a separate field and referenced in each target field with the `$ref` keyword.
-Here is an example of a field definition using `$ref`:
-```yaml
-ExampleField:
-    name: ExampleField
-    description: |
-        The description of "ExampleField".
-    $ref: _ReferenceField
-```
-The target field (`_ReferenceField` in this case) MUST be located in
-the metadata YAML file, and MUST contain all information
-that would be used to describe the field's data type otherwise.
-
-Here is an example of a reference field:
-```yaml
-_ReferenceField:
-    name: _ReferenceField
-    description: |
-        Description of "_ReferenceField".
-    type: string
-    enum:
-        - PossibleValue1
-        - PossibleValue2
-```
-
-The result of including `$ref` makes the `ExampleField` above equivalent to the following format:
-```yaml
-ExampleField:
-    name: ExampleField
-    description: |
-        The description of "ExampleField".
-    type: string
-    enum:
-        - PossibleValue1
-        - PossibleValue2
-```
-
-### `columns.yaml`
-
-This file contains definitions for all TSV columns currently supported in BIDS.
-
-Entries in this file follow the same rules as `metadata.yaml`,
-although column names appear in `snake_case`, rather than `CamelCase`.
-
-### `suffixes.yaml`
-
-This file contains a dictionary in which each suffix is defined.
-Keys are the suffixes (for example, `T1w` for a T1-weighted image),
-and each associated value is a dictionary with three keys: `name`, `description`, and (optionally) `unit`.
-
-The `name` field is the full name of the suffix.
-The `description` field is a freeform description of the type of data stored in files with the suffix.
-
-The `unit` field describes units in which the data may appear.
-When no `unit` field is present, data with that suffix is assumed to be in arbitrary units.
-The `unit` field may use an `anyOf` keyword if multiple valid units are possible.
-
-These entries may also, rarely, include fields defining the range or types of values that are valid for
-files with the suffix.
-For example, `MTRmap` files must have values between 0 and 100, since they represent percentages.
-
-### `top_level_files.yaml`
-
-This file contains a dictionary in which each top-level file is defined.
-Keys are the filenames (without file extensions),
-and each associated value is a dictionary with two keys: `name` and `description`.
-
-The `name` field is the full name of the file.
-The `description` field is a freeform description of the file.
-
-### `associated_data.yaml`
-
-This file contains a dictionary in which each non-BIDS directory is defined.
-Keys are directory names, and each associated value is a dictionary with two keys: `name` and `description`.
-
-The `name` field is the full name of the directory.
-The `description` field is a freeform description of the directory.
-
-## Rule files
-
-The files in the `rules/` directory are less standardized than the files in `objects/`,
-because rules governing how different object types interact in a valid dataset are more variable
-than the object definitions.
-
--   `modalities.yaml`: This file simply groups `datatypes` under their associated modality.
-
--   `datatypes/*.yaml`: Files in the `datatypes` directory contain information about valid filenames within a given datatype.
-    Specifically, each datatype's YAML file contains a list of dictionaries.
-    Each dictionary contains a list of suffixes, entities, and file extensions which may constitute a valid BIDS filename.
-
--   `entities.yaml`: This file simply defines the order in which entities, when present, MUST appear in filenames.
-
--   `top_level_files.yaml`: Requirement levels and valid file extensions of top-level files.
-
--   `associated_data.yaml`: Requirement levels of associated non-BIDS directories.
-
-### `modalities.yaml`
-
-This file contains a dictionary in which each key is a modality abbreviation and the value is a dictionary with one key: `datatypes`.
-The `datatypes` dictionary contains a list of datatypes that fall under that modality.
-
-### `datatypes/*.yaml`
-
-The files in this directory are currently the least standardized of any part of the schema.
-
-Each file corresponds to a single `datatype`.
-Within the file is a list of dictionaries.
-Each dictionary corresponds to a group of suffixes that have the same rules regarding filenames.
-
-The dictionaries have three keys: `suffixes`, `extensions`, and `entities`.
-
-The `suffixes` entry is a list of file suffixes for which all of the extensions in the `extensions` entry
-and all of the entity rules in the `entities` entry apply.
-
-The `extensions` entry is a list of valid file extensions.
-
-The `entities` entry is a dictionary in which the keys are entity names and the values are whether the entity is
-required or optional for that suffix.
-Any entities that are not present in this dictionary are not allowed in files with any of the suffixes in the group.
-In rare occasions, there are restrictions on valid entity values
-(for example, some suffixes may only allow an `acq` value of `calibration`).
-In those cases, the entity's value will be another object, rather than a string indicating the requirement level.
-This object will contain at least two keys: "requirement" and "type".
-
-**NOTE**: The order in which entities appear in these dictionaries does not reflect how they should appear in filenames.
-That information is present in `rules/entities.yaml`.
-
-As an example, let us look at part of `meg.yaml`:
-
-```yaml
-- suffixes:
-  - meg
-  extensions:
-  - .fif
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    run: optional
-    processing: optional
-    split: optional
-
-- suffixes:
-  - meg
-  extensions:
-  - .fif
-  entities:
-    subject: required
-    session: optional
-    acquisition:
-      requirement: required
-      type: string
-      enum:
-      - crosstalk
-```
-
-In this case, the first group has one suffix: `meg`.
-The second group has the same suffix (`meg`), but describes different rules for files with that suffix.
-While the valid extension is the same for both groups (`.fif`), the entities are not.
-
-Specifically, files in the first group may have `task`, `run`, `processing`, and `split` entities,
-while files in the second group may not.
-Also, when files in the second group have the `acq` entity, the associated value MUST be `crosstalk`.
-
-### `entities.yaml`
-
-This file contains a list of entities in the order in which they must appear in filenames.
-
-### `top_level_files.yaml`
-
-This file contains a dictionary in which each key is a top-level file and the value is a dictionary with two keys:
-`required` and `extensions`.
-The `required` entry contains a boolean value (true or false) to indicate if that top-level file is required for BIDS datasets or not.
-The `extensions` entry contains a list of valid file extensions for the file.
-
-In cases where there is a data file and a metadata file, the `.json` extension for metadata file is included.
-
-### `associated_data.yaml`
-
-This file contains a dictionary in which each key is a directory and the value is a dictionary with one key: `required`.
-The `required` entry contains a boolean value to indicate if that directory is required for BIDS datasets or not.
-
-## Version of the schema
-
-File `SCHEMA_VERSION` in the top of the directory contains a semantic
-version (`MAJOR.MINOR.PATCH`) for the schema (how it is organized).
-Note that while in `0.` series, breaking changes are
-permitted without changing the `MAJOR` (leading) component of the version.
-Going forward, the 2nd, `MINOR` indicator should be
-incremented whenever schema organization introduces "breaking changes":
-changes which would cause existing tools reading schema to
-adjust their code to be able to read it again.
-Additions of new components to the schema should increment the last,
-`PATCH`, component of the version so that tools could selectively
-enable/disable loading specific components of the schema.
-With the release of `1.0.0` version of the schema,
-we expect that the `MAJOR` component
-will be incremented whenever schema organization introduces "breaking changes",
-`MINOR` - when adding new components to the schema,
-and `PATCH` - when fixing errors in existing components.
diff --git a/dandi/support/bids/schemadata/1.7.0+369/SCHEMA_VERSION b/dandi/support/bids/schemadata/1.7.0+369/SCHEMA_VERSION
deleted file mode 100644
index 0d91a54c7..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/SCHEMA_VERSION
+++ /dev/null
@@ -1 +0,0 @@
-0.3.0
diff --git a/dandi/support/bids/schemadata/1.7.0+369/meta/context.yaml b/dandi/support/bids/schemadata/1.7.0+369/meta/context.yaml
deleted file mode 100644
index 6a531d9b1..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/meta/context.yaml
+++ /dev/null
@@ -1,262 +0,0 @@
-#
-# The context provides the namespaces available to rules.
-# These namespaces are used by selectors to define the scope of application
-# for a rule, as well as assertions, to determine whether the rule is satisfied.
-#
-# Not all components of the context will be defined; for example a NIfTI header
-# will only be defined when examining a NIfTI file.
-#
-# The dataset namespace is constructed once and is available when visiting all
-# files.
-#
-# The subject namespace is constructed once per subject, and is available when
-# visiting all files within that subject.
-#
-# All other (current) namespaces are defined on individual files.
-# Sidecar metadata and file associations are built according to the inheritance
-# principle.
-#
----
-context:
-    type: object
-    properties:
-        dataset:
-            description: "Properties and contents of the entire dataset"
-            type: object
-            properties:
-                dataset_description:
-                    description: "Contents of /dataset_description.json"
-                    type: object
-                files:
-                    description: "List of all files in dataset"
-                    type: array
-                tree:
-                    description: "Tree view of all files in dataset"
-                    type: object
-                ignored:
-                    description: "Set of ignored files"
-                    type: array
-                modalities:
-                    description: "Modalities present in the dataset"
-                    type: array
-                subjects:
-                    description: "Collections of subjects in dataset"
-                    type: object
-                    properties:
-                        sub_dirs:
-                            description: "Subjects as determined by sub-*/ directories"
-                            type: array
-                            items:
-                                type: string
-                        participant_id:
-                            description: "The participant_id column of participants.tsv"
-                            type: array
-                            items:
-                                type: string
-                        phenotype:
-                            description: "The union of participant_id columns in phenotype files"
-                            type: array
-                            items:
-                                type: string
-        subject:
-            description: "Properties and contents of the current subject"
-            type: object
-            properties:
-                sessions:
-                    description: "Collections of sessions in subject"
-                    type: object
-                    properties:
-                        ses_dirs:
-                            description: "Sessions as determined by ses-*/ directories"
-                            type: array
-                            items:
-                                type: string
-                        session_id:
-                            description: "The session_id column of sessions.tsv"
-                            type: array
-                            items:
-                                type: string
-                        phenotype:
-                            description: "The union of session_id columns in phenotype files"
-                            type: array
-                            items:
-                                type: string
-
-        # Properties of the current file
-        path:
-            description: "Path of the current file"
-            type: string
-        entities:
-            description: "Entities parsed from the current filename"
-            type: object
-        datatype:
-            description: "Datatype of current file, for examples, anat"
-            type: string
-        suffix:
-            description: "Suffix of current file"
-            type: string
-        extension:
-            description: "Extension of current file including initial dot"
-            type: string
-        modality:
-            description: "Modality of current file, for examples, MRI"
-            type: string
-
-        sidecar:
-            description: "Sidecar metadata constructed via the inheritance principle"
-            type: object
-        associations:
-            # Note that this is not intended to be an exhaustive list of associated files
-            # or to expose every attribute of those files. It is specifically those files
-            # and attributes for which a rule needs to be applied from an originating file.
-            description: |
-                Associated files, indexed by suffix, selected according to the inheritance principle
-            type: object
-            properties:
-                events:
-                    description: "Events file"
-                    type: object
-                    properties:
-                        path:
-                            description: "Path to associated events file"
-                            type: string
-                        onset:
-                            description: "Contents of the onset column"
-                            type: array
-                            items:
-                                type: string
-                aslcontext:
-                    description: "ASL context file"
-                    type: object
-                    properties:
-                        path:
-                            description: "Path to associated aslcontext file"
-                            type: string
-                        n_rows:
-                            description: "Number of rows in aslcontext.tsv"
-                            type: integer
-                        volume_type:
-                            description: "Contents of the volume_type column"
-                            type: array
-                            items:
-                                type: string
-                m0scan:
-                    description: "M0 scan file"
-                    type: object
-                    properties:
-                        path:
-                            description: "Path to associated M0 scan file"
-                            type: string
-                magnitude:
-                    description: "Magnitude image file"
-                    type: object
-                    properties:
-                        path:
-                            description: "Path to associated magnitude file"
-                            type: string
-                magnitude1:
-                    description: "Magnitude1 image file"
-                    type: object
-                    properties:
-                        path:
-                            description: "Path to associated magnitude1 file"
-                            type: string
-                bval:
-                    description: "B value file"
-                    type: object
-                    properties:
-                        path:
-                            description: "Path to associated bval file"
-                            type: string
-                        n_cols:
-                            description: "Number of columns in bval file"
-                            type: integer
-                bvec:
-                    description: "B vector file"
-                    type: object
-                    properties:
-                        path:
-                            description: "Path to associated bvec file"
-                            type: string
-                        n_cols:
-                            description: "Number of columns in bvec file"
-                            type: integer
-
-        # The following properties are populated if the current file is of an appropriate type
-        columns:
-            description: "TSV columns, indexed by column header, values are arrays with column contents"
-            type: object
-            additionalProperties:
-                type: array
-        json:
-            description: "Contents of the current JSON file"
-            type: object
-        nifti_header:
-            name: "NIfTI Header"
-            description: "Parsed contents of NIfTI header referenced elsewhere in schema."
-            type: object
-            properties:
-                dim_info:
-                    name: "Dimension Information"
-                    description: "Metadata about dimensions data."
-                    type: object
-                    properties:
-                        freq:
-                            name: "Frequency"
-                            description: "These fields encode which spatial dimension (1, 2, or 3)."
-                            type: integer
-                        phase:
-                            name: "Phase"
-                            description: "Corresponds to which acquisition dimension for MRI data."
-                            type: integer
-                        slice:
-                            name: "Slice"
-                            description: "Slice dimensions."
-                            type: integer
-                dim:
-                    name: "Data Dimensions"
-                    description: "Data seq dimensions."
-                    type: array
-                    minItems: 8
-                    maxItems: 8
-                    items:
-                        type: integer
-                pixdim:
-                    name: "Pixel Dimension"
-                    description: "Grid spacings (unit per dimension)."
-                    type: array
-                    minItems: 8
-                    maxItems: 8
-                    items:
-                        type: number
-                xyzt_units:
-                    name: "XYZT Units"
-                    description: "Units of pixdim[1..4]"
-                    type: object
-                    properties:
-                        xyz:
-                            name: "XYZ Units"
-                            description: "String representing the unit of voxel spacing."
-                            type: string
-                            enum:
-                            - "unknown"
-                            - "meter"
-                            - "mm"
-                            - "um"
-                        t:
-                            name: "Time Unit"
-                            description: "String representing the unit of inter-volume intervals."
-                            type: string
-                            enum:
-                            - "unknown"
-                            - "sec"
-                            - "msec"
-                            - "usec"
-                qform_code:
-                    name: "qform code"
-                    description: "Use of the quaternion fields."
-                    type: integer
-                sform_code:
-                    name: "sform code"
-                    description: "Use of the affine fields."
-                    type: integer
diff --git a/dandi/support/bids/schemadata/1.7.0+369/objects/associated_data.yaml b/dandi/support/bids/schemadata/1.7.0+369/objects/associated_data.yaml
deleted file mode 100644
index 63e78fb0b..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/objects/associated_data.yaml
+++ /dev/null
@@ -1,29 +0,0 @@
----
-# This file describes directories that may appear within a dataset directory
-# without following BIDS rules.
-# Information about whether these directories are required or not is present in
-# `rules/associated_data.yaml`.
-code:
-  display_name: Code
-  description: |
-    A directory in which to store any code used to generate the derivatives from the
-    source data.
-derivatives:
-  display_name: Derivative data
-  description: |
-    Derivative data
-sourcedata:
-  display_name: Source data
-  description: |
-    Data before harmonization, reconstruction, and/or file format conversion
-    (for example, E-Prime event logs or DICOM files).
-stimuli:
-  display_name: Stimulus files
-  description: |
-    The stimulus files can be added in a `/stimuli` directory
-    (under the root directory of the dataset; with optional subdirectories)
-    AND using a stim_file column in *_events.tsv mentioning which stimulus file was
-    used for a given event.
-
-    There are no restrictions on the file formats of the stimuli files, but they should be
-    stored in the `/stimuli` directory.
diff --git a/dandi/support/bids/schemadata/1.7.0+369/objects/columns.yaml b/dandi/support/bids/schemadata/1.7.0+369/objects/columns.yaml
deleted file mode 100644
index b4cf79852..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/objects/columns.yaml
+++ /dev/null
@@ -1,680 +0,0 @@
----
-HED:
-  name: HED
-  display_name: HED Tag
-  description: |
-    Hierarchical Event Descriptor (HED) Tag.
-    See [Appendix III](SPEC_ROOT/99-appendices/03-hed.md) for details.
-  type: string
-abbreviation:
-  name: abbreviation
-  display_name: Abbreviation
-  description: |
-    The unique label abbreviation
-  type: string
-acq_time__scans:
-  name: acq_time
-  display_name: Scan acquisition time
-  description: |
-    Acquisition time refers to when the first data point in each run was acquired.
-    Furthermore, if this header is provided, the acquisition times of all files
-    from the same recording MUST be identical.
-    Datetime format and their anonymization are described in
-    [Units](SPEC_ROOT/02-common-principles.md#units).
-  type: string
-  format: datetime
-acq_time__sessions:
-  name: acq_time
-  display_name: Session acquisition time
-  description: |
-    Acquisition time refers to when the first data point of the first run was acquired.
-    Datetime format and their anonymization are described in
-    [Units](SPEC_ROOT/02-common-principles.md#units).
-  type: string
-  format: datetime
-age:
-  name: age
-  display_name: Subject age
-  description: |
-    Numeric value in years (float or integer value).
-  type: number
-  unit: year
-cardiac:
-  name: cardiac
-  display_name: Cardiac measurement
-  description: |
-    continuous pulse measurement
-  type: number
-color:
-  name: color
-  display_name: Color label
-  description: |
-    Hexadecimal. Label color for visualization.
-  type: string
-  unit: hexadecimal
-derived_from:
-  name: derived_from
-  display_name: Derived from
-  description: |
-    `sample-<label>` entity from which a sample is derived,
-    for example a slice of tissue (`sample-02`) derived from a block of tissue (`sample-01`).
-  type: string
-  pattern: ^sample-[0-9a-zA-Z]+$
-description:
-  name: description
-  display_name: Description
-  description: |
-    Brief free-text description of the channel, or other information of interest.
-  type: string
-dimension:
-  name: dimension
-  display_name: Dimension
-  description: |
-    Size of the group (grid/strip/probe) that this electrode belongs to.
-    Must be of form `[AxB]` with the smallest dimension first (for example, `[1x8]`).
-  type: string
-duration:
-  name: duration
-  display_name: Event duration
-  description: |
-    Duration of the event (measured from onset) in seconds.
-    Must always be either zero or positive (or `n/a` if unavailable).
-    A "duration" value of zero implies that the delta function or event is so
-    short as to be effectively modeled as an impulse.
-  anyOf:
-  - type: number
-    unit: s
-    minimum: 0
-  - type: string
-    enum:
-    - n/a
-filename:
-  name: filename
-  display_name: Filename
-  description: |
-    Relative paths to files.
-  type: string
-  format: participant_relative
-group__channel:
-  name: group
-  display_name: Channel group
-  description: |
-    Which group of channels (grid/strip/seeg/depth) this channel belongs to.
-    This is relevant because one group has one cable-bundle and noise can be shared.
-    This can be a name or number.
-  anyOf:
-  - type: string
-  - type: number
-handedness:
-  name: handedness
-  display_name: Subject handedness
-  description: |
-    String value indicating one of "left", "right", "ambidextrous".
-
-    For "left", use one of these values: `left`, `l`, `L`, `LEFT`, `Left`.
-
-    For "right", use one of these values: `right`, `r`, `R`, `RIGHT`, `Right`.
-
-    For "ambidextrous", use one of these values: `ambidextrous`, `a`, `A`, `AMBIDEXTROUS`,
-    `Ambidextrous`.
-  type: string
-  enum:
-  - left
-  - l
-  - L
-  - LEFT
-  - Left
-  - right
-  - r
-  - R
-  - RIGHT
-  - Right
-  - ambidextrous
-  - a
-  - A
-  - AMBIDEXTROUS
-  - Ambidextrous
-  - n/a
-hemisphere:
-  name: hemisphere
-  display_name: Electrode hemisphere
-  description: |
-    The hemisphere in which the electrode is placed.
-  type: string
-  enum:
-  - L
-  - R
-high_cutoff:
-  name: high_cutoff
-  display_name: High cutoff
-  description: |
-    Frequencies used for the low-pass filter applied to the channel in Hz.
-    If no low-pass filter applied, use `n/a`.
-    Note that hardware anti-aliasing in A/D conversion of all MEG/EEG electronics
-    applies a low-pass filter; specify its frequency here if applicable.
-  anyOf:
-  - type: number
-    unit: Hz
-    minimum: 0
-  - type: string
-    enum:
-    - n/a
-hplc_recovery_fractions:
-  name: hplc_recovery_fractions
-  display_name: HPLC recovery fractions
-  description: |
-    HPLC recovery fractions (the fraction of activity that gets loaded onto the HPLC).
-  type: number
-  unit: arbitrary
-impedance:
-  name: impedance
-  display_name: Electrode impedance
-  description: |
-    Impedance of the electrode, units MUST be in `kOhm`.
-  type: number
-  unit: kOhm
-index:
-  name: index
-  display_name: Label index
-  description: |
-    The label integer index.
-  type: integer
-low_cutoff:
-  name: low_cutoff
-  display_name: Low cutoff
-  description: |
-    Frequencies used for the high-pass filter applied to the channel in Hz.
-    If no high-pass filter applied, use `n/a`.
-  anyOf:
-  - type: number
-    unit: Hz
-  - type: string
-    enum:
-    - n/a
-manufacturer:
-  name: manufacturer
-  display_name: Manufacturer
-  description: |
-    The manufacturer for each electrode.
-    Can be used if electrodes were manufactured by more than one company.
-  type: string
-mapping:
-  name: mapping
-  display_name: Label mapping
-  description: |
-    Corresponding integer label in the standard BIDS label lookup.
-  type: integer
-material:
-  name: material
-  display_name: Electrode material
-  description: |
-    Material of the electrode (for example, `Tin`, `Ag/AgCl`, `Gold`).
-  type: string
-metabolite_parent_fraction:
-  name: metabolite_parent_fraction
-  display_name: Metabolite parent fraction
-  description: |
-    Parent fraction of the radiotracer (0-1).
-  type: number
-  minimum: 0
-  maximum: 1
-metabolite_polar_fraction:
-  name: metabolite_polar_fraction
-  display_name: Metabolite polar fraction
-  description: |
-    Polar metabolite fraction of the radiotracer (0-1).
-  type: number
-  minimum: 0
-  maximum: 1
-# name column for channels.tsv files
-name__channels:
-  name: name
-  display_name: Channel name
-  description: |
-    Label of the channel.
-  type: string
-# name column for electrodes.tsv files
-name__electrodes:
-  name: name
-  display_name: Electrode name
-  description: |
-    Name of the electrode contact point.
-  type: string
-# name column for dseg.tsv files
-name__segmentations:
-  name: name
-  display_name: Label name
-  description: |
-    The unique label name.
-  type: string
-notch:
-  name: notch
-  display_name: Notch frequencies
-  description: |
-    Frequencies used for the notch filter applied to the channel, in Hz.
-    If no notch filter applied, use `n/a`.
-  anyOf:
-  - type: number
-    unit: Hz
-  - type: string
-    enum:
-    - n/a
-onset:
-  name: onset
-  display_name: Event onset
-  description: |
-    Onset (in seconds) of the event, measured from the beginning of the acquisition
-    of the first data point stored in the corresponding task data file.
-    Negative onsets are allowed, to account for events that occur prior to the first
-    stored data point.
-    For example, in case there is an in-scanner training phase that begins before
-    the scanning sequence has started events from this sequence should have
-    negative onset time counting down to the beginning of the acquisition of the
-    first volume.
-
-    If any data points have been discarded before forming the data file
-    (for example, "dummy volumes" in BOLD fMRI),
-    a time of 0 corresponds to the first stored data point and not the first
-    acquired data point.
-  type: number
-  unit: s
-pathology:
-  name: pathology
-  display_name: Pathology
-  description: |
-    String value describing the pathology of the sample or type of control.
-    When different from `healthy`, pathology SHOULD be specified.
-    The pathology may be specified in either `samples.tsv` or
-    `sessions.tsv`, depending on whether the pathology changes over time.
-  type: string
-participant_id:
-  name: participant_id
-  display_name: Participant ID
-  description: |
-    A participant identifier of the form `sub-<label>`,
-    matching a participant entity found in the dataset.
-  type: string
-  pattern: ^sub-[0-9a-zA-Z]+$
-plasma_radioactivity:
-  name: plasma_radioactivity
-  display_name: Plasma radioactivity
-  description: |
-    Radioactivity in plasma, in unit of plasma radioactivity (for example, `kBq/mL`).
-  type: number
-# reference column for channels.tsv files for EEG data
-reference__eeg:
-  name: reference
-  display_name: Electrode reference
-  description: |
-    Name of the reference electrode(s).
-    This column is not needed when it is common to all channels.
-    In that case the reference electrode(s) can be specified in `*_eeg.json` as `EEGReference`).
-  type: string
-# reference column for channels.tsv files for iEEG data
-reference__ieeg:
-  name: reference
-  display_name: Electrode reference
-  description: |
-    Specification of the reference (for example, `mastoid`, `ElectrodeName01`, `intracranial`, `CAR`, `other`, `n/a`).
-    If the channel is not an electrode channel (for example, a microphone channel) use `n/a`.
-  anyOf:
-  - type: string
-  - type: string
-    enum:
-    - n/a
-respiratory:
-  name: respiratory
-  display_name: Respiratory measurement
-  description: |
-    continuous breathing measurement
-  type: number
-response_time:
-  name: response_time
-  display_name: Response time
-  description: |
-    Response time measured in seconds.
-    A negative response time can be used to represent preemptive responses and
-    `n/a` denotes a missed response.
-  anyOf:
-  - type: number
-    unit: s
-  - type: string
-    enum:
-    - n/a
-sample:
-  name: sample
-  display_name: Sample index
-  description: |
-    Onset of the event according to the sampling scheme of the recorded modality
-    (that is, referring to the raw data file that the `events.tsv` file accompanies).
-  type: integer
-sample_id:
-  name: sample_id
-  display_name: Sample ID
-  description: |
-    A sample identifier of the form `sample-<label>`,
-    matching a sample entity found in the dataset.
-  type: string
-  pattern: ^sample-[0-9a-zA-Z]+$
-sample_type:
-  name: sample_type
-  display_name: Sample type
-  description: |
-    Biosample type defined by
-    [ENCODE Biosample Type](https://www.encodeproject.org/profiles/biosample_type).
-  type: string
-  enum:
-  - cell line
-  - in vitro differentiated cells
-  - primary cell
-  - cell-free sample
-  - cloning host
-  - tissue
-  - whole organisms
-  - organoid
-  - technical sample
-sampling_frequency:
-  name: sampling_frequency
-  display_name: Channel sampling frequency
-  description: |
-    Sampling rate of the channel in Hz.
-  type: number
-  unit: Hz
-session_id:
-  name: session_id
-  display_name: Session ID
-  description: |
-    A session identifier of the form `ses-<label>`,
-    matching a session found in the dataset.
-  type: string
-  pattern: ^ses-[0-9a-zA-Z]+$
-sex:
-  name: sex
-  display_name: Sex
-  description: |
-    String value indicating phenotypical sex, one of "male", "female", "other".
-
-    For "male", use one of these values: `male`, `m`, `M`, `MALE`, `Male`.
-
-    For "female", use one of these values: `female`, `f`, `F`, `FEMALE`, `Female`.
-
-    For "other", use one of these values: `other`, `o`, `O`, `OTHER`, `Other`.
-  type: string
-  enum:
-  - male
-  - m
-  - M
-  - MALE
-  - Male
-  - female
-  - f
-  - F
-  - FEMALE
-  - Female
-  - other
-  - o
-  - O
-  - OTHER
-  - Other
-  - n/a
-size:
-  name: size
-  display_name: Electrode size
-  description: |
-    Surface area of the electrode, units MUST be in `mm^2`.
-  type: number
-  unit: 'mm^2'
-software_filters:
-  name: software_filters
-  display_name: Software filters
-  description: |
-    List of temporal and/or spatial software filters applied
-    (for example, `SSS`, `SpatialCompensation`).
-    Note that parameters should be defined in the general MEG sidecar .json file.
-    Indicate `n/a` in the absence of software filters applied.
-  anyOf:
-  - type: string
-  - type: string
-    enum:
-    - n/a
-species:
-  name: species
-  display_name: Species
-  description: |
-    The `species` column SHOULD be a binomial species name from the
-    [NCBI Taxonomy](https://www.ncbi.nlm.nih.gov/Taxonomy/Browser/wwwtax.cgi)
-    (for example, `homo sapiens`, `mus musculus`, `rattus norvegicus`).
-    For backwards compatibility, if `species` is absent, the participant is assumed to be
-    `homo sapiens`.
-  type: string
-status:
-  name: status
-  display_name: Channel status
-  description: |
-    Data quality observed on the channel.
-    A channel is considered `bad` if its data quality is compromised by excessive noise.
-    If quality is unknown, then a value of `n/a` may be used.
-    Description of noise type SHOULD be provided in `[status_description]`.
-  type: string
-  enum:
-  - good
-  - bad
-  - n/a
-status_description:
-  name: status_description
-  display_name: Channel status description
-  description: |
-    Freeform text description of noise or artifact affecting data quality on the channel.
-    It is meant to explain why the channel was declared bad in the `status` column.
-  type: string
-stim_file:
-  name: stim_file
-  display_name: Stimulus file
-  description: |
-    Represents the location of the stimulus file (such as an image, video, or
-    audio file) presented at the given onset time.
-    There are no restrictions on the file formats of the stimuli files,
-    but they should be stored in the `/stimuli` directory
-    (under the root directory of the dataset; with optional subdirectories).
-    The values under the `stim_file` column correspond to a path relative to
-    `/stimuli`.
-    For example `images/cat03.jpg` will be translated to `/stimuli/images/cat03.jpg`.
-  type: string
-  format: stimuli_relative
-strain:
-  name: strain
-  display_name: Strain
-  description: |
-    For species different from `homo sapiens`, string value indicating
-    the strain of the species, for example: `C57BL/6J`.
-  type: string
-strain_rrid:
-  name: strain_rrid
-  display_name: Strain RRID
-  description: |
-    For species different from `homo sapiens`, research resource identifier
-    ([RRID](https://scicrunch.org/resources/Organisms/search))
-    of the strain of the species, for example: `RRID:IMSR_JAX:000664`.
-  type: string
-  format: rrid
-time:
-  name: time
-  display_name: Time
-  description: |
-    Time, in seconds, relative to `TimeZero` defined by the `*_pet.json`.
-    For example, 5.
-  type: number
-  unit: s
-trial_type:
-  name: trial_type
-  display_name: Trial type
-  description: |
-    Primary categorisation of each trial to identify them as instances of the
-    experimental conditions.
-    For example: for a response inhibition task, it could take on values `go` and
-    `no-go` to refer to response initiation and response inhibition experimental
-    conditions.
-  type: string
-trigger:
-  name: trigger
-  display_name: Trigger
-  description: |
-    continuous measurement of the scanner trigger signal
-  type: number
-# type column in channels.tsv files
-type__eeg_channels:
-  name: type
-  display_name: Channel type
-  description: |
-    Type of channel; MUST use the channel types listed below.
-    Note that the type MUST be in upper-case.
-  type: string
-  enum:
-  - AUDIO
-  - EEG
-  - EOG
-  - ECG
-  - EMG
-  - EYEGAZE
-  - GSR
-  - HEOG
-  - MISC
-  - PPG
-  - PUPIL
-  - REF
-  - RESP
-  - SYSCLOCK
-  - TEMP
-  - TRIG
-  - VEOG
-type__meg_channels:
-  name: type
-  display_name: Channel type
-  description: |
-    Type of channel; MUST use the channel types listed below.
-    Note that the type MUST be in upper-case.
-  type: string
-  enum:
-  - MEGMAG
-  - MEGGRADAXIAL
-  - MEGGRADPLANAR
-  - MEGREFMAG
-  - MEGREFGRADAXIAL
-  - MEGREFGRADPLANAR
-  - MEGOTHER
-  - EEG
-  - ECOG
-  - SEEG
-  - DBS
-  - VEOG
-  - HEOG
-  - EOG
-  - ECG
-  - EMG
-  - TRIG
-  - AUDIO
-  - PD
-  - EYEGAZE
-  - PUPIL
-  - MISC
-  - SYSCLOCK
-  - ADC
-  - DAC
-  - HLU
-  - FITERR
-  - OTHER
-type__ieeg_channels:
-  name: type
-  display_name: Channel type
-  description: |
-    Type of channel; MUST use the channel types listed below.
-    Note that the type MUST be in upper-case.
-  type: string
-  enum:
-  - EEG
-  - ECOG
-  - SEEG
-  - DBS
-  - VEOG
-  - HEOG
-  - EOG
-  - ECG
-  - EMG
-  - TRIG
-  - AUDIO
-  - PD
-  - EYEGAZE
-  - PUPIL
-  - MISC
-  - SYSCLOCK
-  - ADC
-  - DAC
-  - REF
-  - OTHER
-# type column for electrodes.tsv files
-type__electrodes:
-  name: type
-  display_name: Electrode type
-  description: |
-    Type of the electrode (for example, cup, ring, clip-on, wire, needle).
-  type: string
-units:
-  name: units
-  display_name: Units
-  description: |
-    Physical unit of the value represented in this channel,
-    for example, `V` for Volt, or `fT/cm` for femto Tesla per centimeter
-    (see [Units](SPEC_ROOT/02-common-principles.md#units)).
-  type: string
-  format: unit
-value:
-  name: value
-  display_name: Marker value
-  description: |
-    Marker value associated with the event (for example, the value of a TTL
-    trigger that was recorded at the onset of the event).
-  anyOf:
-  - type: number
-  - type: string
-volume_type:
-  name: volume_type
-  display_name: ASL volume type
-  description: |
-    The `*_aslcontext.tsv` table consists of a single column of labels identifying
-    the `volume_type` of each volume in the corresponding `*_asl.nii[.gz]` file.
-  type: string
-  enum:
-  - control
-  - label
-  - m0scan
-  - deltam
-  - cbf
-whole_blood_radioactivity:
-  name: whole_blood_radioactivity
-  display_name: Whole blood radioactivity
-  description: |
-    Radioactivity in whole blood samples,
-    in unit of radioactivity measurements in whole blood samples (for example, `kBq/mL`).
-  type: number
-x:
-  name: x
-  display_name: X position
-  description: |
-    Recorded position along the x-axis.
-  type: number
-y:
-  name: y
-  display_name: Y position
-  description: |
-    Recorded position along the y-axis.
-  type: number
-z:
-  name: z
-  display_name: Z position
-  description: |
-    Recorded position along the z-axis.
-  anyOf:
-  - type: number
-  - type: string
-    enum:
-    - n/a
diff --git a/dandi/support/bids/schemadata/1.7.0+369/objects/datatypes.yaml b/dandi/support/bids/schemadata/1.7.0+369/objects/datatypes.yaml
deleted file mode 100644
index 13d5907d7..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/objects/datatypes.yaml
+++ /dev/null
@@ -1,55 +0,0 @@
----
-# This file defines valid BIDS datatypes, along with their full names and descriptions.
-# For rules regarding how suffixes relate to datatypes, see files in `rules/datatypes/`.
-anat:
-  value: anat
-  display_name: Anatomical Magnetic Resonance Imaging
-  description: |
-    Magnetic resonance imaging sequences designed to characterize static, anatomical features.
-beh:
-  value: beh
-  display_name: Behavioral Data
-  description: |
-    Behavioral data.
-dwi:
-  value: dwi
-  display_name: Diffusion-Weighted Imaging
-  description: |
-    Diffusion-weighted imaging (DWI).
-eeg:
-  value: eeg
-  display_name: Electroencephalography
-  description: Electroencephalography
-fmap:
-  value: fmap
-  display_name: Field maps
-  description: |
-    MRI scans for estimating B0 inhomogeneity-induced distortions.
-func:
-  value: func
-  display_name: Task-Based Magnetic Resonance Imaging
-  description: |
-    Task (including resting state) imaging data
-ieeg:
-  value: ieeg
-  display_name: Intracranial electroencephalography
-  description: |
-    Intracranial electroencephalography (iEEG) or electrocorticography (ECoG) data
-meg:
-  value: meg
-  display_name: Magnetoencephalography
-  description: Magnetoencephalography
-micr:
-  value: micr
-  display_name: Microscopy
-  description: Microscopy
-perf:
-  value: perf
-  display_name: Perfusion imaging
-  description: |
-    Blood perfusion imaging data, including arterial spin labeling (ASL)
-pet:
-  value: pet
-  display_name: Positron Emission Tomography
-  description: |
-    Positron emission tomography data
diff --git a/dandi/support/bids/schemadata/1.7.0+369/objects/entities.yaml b/dandi/support/bids/schemadata/1.7.0+369/objects/entities.yaml
deleted file mode 100644
index 4d46ec99a..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/objects/entities.yaml
+++ /dev/null
@@ -1,367 +0,0 @@
----
-# This file describes entities present in BIDS filenames.
-# WARNING: The entities are presented here in alphabetical order!
-# The appropriate order of entities in filenames is defined in `rules/entities.yaml`,
-# rather than this file (`objects/entities.yaml`).
-acquisition:
-  name: acq
-  display_name: Acquisition
-  description: |
-    The `acq-<label>` entity corresponds to a custom label the
-    user MAY use to distinguish a different set of parameters used for
-    acquiring the same modality.
-    For example this should be used when a study includes two T1w images - one
-    full brain low resolution and one restricted field of view but high
-    resolution.
-    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.
-  type: string
-  format: label
-atlas:
-  name: atlas
-  display_name: Atlas
-  description: |
-    The `atlas-<label>` key/value pair corresponds to a custom label the user
-    MAY use to distinguish a different atlas used for similar type of data.
-
-    This entity is only applicable to derivative data.
-  type: string
-  format: label
-ceagent:
-  name: ce
-  display_name: Contrast Enhancing Agent
-  description: |
-    The `ce-<label>` entity can be used to distinguish
-    sequences using different contrast enhanced images.
-    The label is the name of the contrast agent.
-    The key `"ContrastBolusIngredient"` MAY also be added in the JSON file,
-    with the same label.
-  type: string
-  format: label
-chunk:
-  name: chunk
-  display_name: Chunk
-  description: |
-    The `chunk-<index>` key/value pair is used to distinguish between different
-    regions, 2D images or 3D volumes files, of the same physical sample with
-    different fields of view acquired in the same imaging experiment.
-  type: string
-  format: index
-density:
-  name: den
-  display_name: Density
-  description: |
-    Density of non-parametric surfaces.
-    MUST have a corresponding `Density` metadata field to provide
-    interpretation.
-
-    This entity is only applicable to derivative data.
-  type: string
-  format: label
-description:
-  name: desc
-  display_name: Description
-  description: |
-    When necessary to distinguish two files that do not otherwise have a
-    distinguishing entity, the `_desc-<label>` entity SHOULD be used.
-
-    This entity is only applicable to derivative data.
-  type: string
-  format: label
-direction:
-  name: dir
-  display_name: Phase-Encoding Direction
-  description: |
-    The `dir-<label>` entity can be set to an arbitrary alphanumeric label
-    (for example, `dir-LR` or `dir-AP`) to distinguish different phase-encoding
-    directions.
-  type: string
-  format: label
-echo:
-  name: echo
-  display_name: Echo
-  description: |
-    If files belonging to an entity-linked file collection are acquired at different
-    echo times, the `_echo-<index>` entity MUST be used to distinguish
-    individual files.
-    This entity represents the `"EchoTime"` metadata field. Please note that the `<index>`
-    denotes the number/index (in the form of a nonnegative integer), not the
-    `"EchoTime"` value which needs to be stored in the field `"EchoTime"` of the separate
-    JSON file.
-  type: string
-  format: index
-flip:
-  name: flip
-  display_name: Flip Angle
-  description: |
-    If files belonging to an entity-linked file collection are acquired at different
-    flip angles, the `_flip-<index>` entity pair MUST be used to distinguish
-    individual files.
-    This entity represents the `"FlipAngle"` metadata field. 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.
-  type: string
-  format: index
-hemisphere:
-  name: hemi
-  display_name: Hemisphere
-  description: |
-    The `hemi-<label>` entity indicates which hemibrain is described by the file.
-    Allowed label values for this entity are `L` and `R`, for the left and right
-    hemibrains, respectively.
-  type: string
-  format: label
-  enum:
-  - "L"
-  - "R"
-inversion:
-  name: inv
-  display_name: Inversion Time
-  description: |
-    If files belonging to an entity-linked file collection are acquired at different
-    inversion times, the `_inv-<index>` entity MUST be used to distinguish
-    individual files.
-    This entity represents the `"InversionTime` metadata field. Please note that the `<index>`
-    denotes the number/index (in the form of a nonnegative integer), not the `"InversionTime"`
-    value which needs to be stored in the field `"InversionTime"` of the separate JSON file.
-  type: string
-  format: index
-label:
-  name: label
-  display_name: Label
-  description: |
-    Tissue-type label, following a prescribed vocabulary.
-    Applies to binary masks and probabilistic/partial volume segmentations
-    that describe a single tissue type.
-
-    This entity is only applicable to derivative data.
-  type: string
-  format: label
-modality:
-  name: mod
-  display_name: Corresponding Modality
-  description: |
-    The `mod-<label>` entity corresponds to modality label for defacing
-    masks, for example, T1w, inplaneT1, referenced by a defacemask image.
-    For example, `sub-01_mod-T1w_defacemask.nii.gz`.
-  type: string
-  format: label
-mtransfer:
-  name: mt
-  display_name: Magnetization Transfer
-  description: |
-    If files belonging to an entity-linked file collection are acquired at different
-    magnetization transfer (MT) states, the `_mt-<label>` entity MUST be used to
-    distinguish individual files.
-    This entity represents the `"MTState"` metadata field. Allowed label values for this
-    entity are `on` and `off`, for images acquired in presence and absence of an MT pulse,
-    respectively.
-  type: string
-  enum:
-  - "on"
-  - "off"
-part:
-  name: part
-  display_name: Part
-  description: |
-    This entity is used to indicate which component of the complex
-    representation of the MRI signal is represented in voxel data.
-    The `part-<label>` entity is associated with the DICOM Tag
-    `0008, 9208`.
-    Allowed label values for this entity are `phase`, `mag`, `real` and `imag`,
-    which are typically used in `part-mag`/`part-phase` or
-    `part-real`/`part-imag` pairs of files.
-
-    Phase images MAY be in radians or in arbitrary units.
-    The sidecar JSON file MUST include the units of the `phase` image.
-    The possible options are `"rad"` or `"arbitrary"`.
-
-    When there is only a magnitude image of a given type, the `part` entity MAY be
-    omitted.
-  type: string
-  enum:
-  - mag
-  - phase
-  - real
-  - imag
-processing:
-  name: proc
-  display_name: Processed (on device)
-  description: |
-    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.
-  type: string
-  format: label
-reconstruction:
-  name: rec
-  display_name: Reconstruction
-  description: |
-    The `rec-<label>` entity can be used to distinguish
-    different reconstruction algorithms (for example `MoCo` for the ones using motion
-    correction).
-  type: string
-  format: label
-recording:
-  name: recording
-  display_name: Recording
-  description: |
-    More than one continuous recording file can be included (with different
-    sampling frequencies).
-    In such case use different labels.
-    For example: `_recording-contrast`, `_recording-saturation`.
-  type: string
-  format: label
-resolution:
-  name: res
-  display_name: Resolution
-  description: |
-    Resolution of regularly sampled N-dimensional data.
-    MUST have a corresponding `"Resolution"` metadata field to provide
-    interpretation.
-
-    This entity is only applicable to derivative data.
-  type: string
-  format: label
-run:
-  name: run
-  display_name: Run
-  description: |
-    If several data acquisitions (for example, MRI scans or EEG recordings)
-    with the same acquisition parameters are acquired in the same session,
-    they MUST be indexed with the [`run-<index>`](../99-appendices/09-entities.md#run) entity:
-    `_run-1`, `_run-2`, `_run-3`, and so on (only nonnegative integers are allowed as
-    run labels).
-
-    If different entities apply,
-    such as a different session indicated by [`ses-<label>`](../99-appendices/09-entities.md#ses),
-    or different acquisition parameters indicated by
-    [`acq-<label>`](../99-appendices/09-entities.md#acq),
-    then `run` is not needed to distinguish the scans and MAY be omitted.
-  type: string
-  format: index
-sample:
-  name: sample
-  display_name: Sample
-  description: |
-    A sample pertaining to a subject such as tissue, primary cell
-    or cell-free sample.
-    The `sample-<label>` entity is used to distinguish between different
-    samples from the same subject.
-    The label MUST be unique per subject and is RECOMMENDED to be unique
-    throughout the dataset.
-  type: string
-  format: label
-session:
-  name: ses
-  display_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
-    (for example, training).
-  type: string
-  format: label
-space:
-  name: space
-  display_name: Space
-  description: |
-    The space entity can be used to indicate
-    the way in which electrode positions are interpreted
-    (for EEG/MEG/iEEG data) or
-    the spatial reference to which a file has been aligned (for MRI data).
-    The space `<label>` MUST be taken from one of the modality specific lists in
-    [Appendix VIII](../99-appendices/08-coordinate-systems.md).
-    For example for iEEG data, the restricted keywords listed under
-    [iEEG Specific Coordinate Systems](../99-appendices/08-coordinate-systems.md#ieeg-specific-coordinate-systems)
-    are acceptable for `<label>`.
-
-    For EEG/MEG/iEEG data, this entity can be applied to raw data, but
-    for other data types, it is restricted to derivative data.
-  type: string
-  format: label
-split:
-  name: split
-  display_name: Split
-  description: |
-    In the case of long data recordings that exceed a file size of 2Gb, the
-    .fif files are conventionally split into multiple parts.
-    Each of these files has an internal pointer to the next file.
-    This is important when renaming these split recordings to the BIDS
-    convention.
-
-    Instead of a simple renaming, files should be read in and saved under their
-    new names with dedicated tools like [MNE-Python](https://mne.tools/),
-    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.
-    If there are multiple parts of a recording and the optional `scans.tsv` is provided,
-    remember to list all files separately in `scans.tsv` and that the entries for the
-    `acq_time` column in `scans.tsv` MUST all be identical, as described in
-    [Scans file](../03-modality-agnostic-files.md#scans-file).
-  type: string
-  format: index
-stain:
-  name: stain
-  display_name: Stain
-  description: |
-    The `stain-<label>` key/pair values can be used to distinguish image files
-    from the same sample using different stains or antibodies for contrast enhancement.
-    Stains SHOULD be indicated in the `"SampleStaining"` key in the sidecar JSON file,
-    although the label may be different.
-    Description of antibodies SHOULD also be indicated in `"SamplePrimaryAntibodies"`
-    and/or `"SampleSecondaryAntobodies"` as appropriate.
-  type: string
-  format: label
-subject:
-  name: sub
-  display_name: Subject
-  description: |
-    A person or animal participating in the study.
-  type: string
-  format: label
-task:
-  name: task
-  display_name: Task
-  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.
-  type: string
-  format: label
-tracer:
-  name: trc
-  display_name: Tracer
-  description: |
-    The `trc-<label>` entity can be used to distinguish
-    sequences using different tracers.
-    The key `"TracerName"` MUST also be included in the associated JSON file,
-    although the label may be different.
-  type: string
-  format: label
diff --git a/dandi/support/bids/schemadata/1.7.0+369/objects/extensions.yaml b/dandi/support/bids/schemadata/1.7.0+369/objects/extensions.yaml
deleted file mode 100644
index 871f14b8c..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/objects/extensions.yaml
+++ /dev/null
@@ -1,299 +0,0 @@
----
-# This file describes valid file extensions in the specification.
-ave:
-  value: .ave
-  display_name: AVE  # not sure what ave stands for
-  description: |
-    File containing data averaged by segments of interest.
-
-    Used by KIT, Yokogawa, and Ricoh MEG systems.
-bdf:
-  value: .bdf
-  display_name: Biosemi Data Format
-  description: |
-    A [Biosemi](https://www.biosemi.com/) Data Format file.
-
-    Each recording consists of a single `.bdf` file.
-    [`bdf+`](https://www.teuniz.net/edfbrowser/bdfplus%20format%20description.html) files are permitted.
-    The capital `.BDF` extension MUST NOT be used.
-bval:
-  value: .bval
-  display_name: FSL-Format Gradient Amplitudes
-  description: |
-    A space-delimited file containing gradient directions (b-vectors) of diffusion measurement.
-
-    The `bval` file contains the *b*-values (in s/mm<sup>2</sup>) corresponding to the
-    volumes in the relevant NIfTI file, with 0 designating *b*=0 volumes.
-bvec:
-  value: .bvec
-  display_name: FSL-Format Gradient Directions
-  description: |
-    A space-delimited file containing gradient directions (b-vectors) of diffusion measurement.
-
-    This file contains 3 rows with *N* space-delimited floating-point numbers,
-    corresponding to the *N* volumes in the corresponding NIfTI file.
-
-    The first row contains the *x* elements, the second row contains the *y* elements and
-    the third row contains the *z* elements of a unit vector in the direction of the applied
-    diffusion gradient, where the *i*-th elements in each row correspond together to
-    the *i*-th volume, with `[0,0,0]` for *non-diffusion-weighted* (also called *b*=0 or *low-b*)
-    volumes.
-
-    Following the FSL format for the `bvec` specification, the coordinate system of
-    the *b* vectors MUST be defined with respect to the coordinate system defined by
-    the header of the corresponding `_dwi` NIfTI file and not the scanner's device
-    coordinate system (see [Coordinate systems](../99-appendices/08-coordinate-systems.md)).
-    The most relevant limitation imposed by this choice is that the gradient information cannot
-    be directly stored in this format if the scanner generates *b*-vectors in *scanner coordinates*.
-chn:
-  value: .chn
-  display_name: KRISS CHN
-  description: |
-    A file generated by KRISS MEG systems containing the position of the center of the MEG coils.
-
-    Each experimental run on the KRISS system produces a file with extension `.kdf`.
-    Additional files that may be available in the same folder include
-    the digitized positions of the head points (`\_digitizer.txt`),
-    the position of the center of the MEG coils (`.chn`),
-    and the event markers (`.trg`).
-con:
-  value: .con
-  display_name: KIT/Yokogawa/Ricoh Continuous Data
-  description: |
-    Raw continuous data from a KIT/Yokogawa/Ricoh MEG system.
-
-    Successor to the `.sqd` extension for raw continuous data.
-dat:
-  value: .dat
-  display_name: MEG Fine-Calibration Format
-  description: |
-    A fine-calibration file used for Neuromag/Elekta/MEGIN MEG recording hardware.
-CTF:
-  value: .ds/
-  display_name: CTF MEG Dataset Folder
-  description: |
-    A folder for MEG data, typically containing a `.meg4` file for the data and a `.res4` file for the resources.
-edf:
-  value: .edf
-  display_name: European Data Format
-  description: |
-    A [European data format](https://www.edfplus.info/) file.
-
-    Each recording consists of a single `.edf`` file.
-    [`edf+`](https://www.edfplus.info/specs/edfplus.html) files are permitted.
-    The capital `.EDF` extension MUST NOT be used.
-eeg:
-  value: .eeg
-  display_name: BrainVision Binary Data
-  description: |
-    A binary data file in the
-    [BrainVision Core Data Format](https://www.brainproducts.com/productdetails.php?id=21&tab=5).
-    These files come in three-file sets, including a `.vhdr`, a `.vmrk`, and a `.eeg` file.
-fdt:
-  value: .fdt
-  display_name: EEGLAB FDT
-  description: |
-    An [EEGLAB](https://sccn.ucsd.edu/eeglab) file.
-
-    The format used by the MATLAB toolbox [EEGLAB](https://sccn.ucsd.edu/eeglab).
-    Each recording consists of a `.set` file with an optional `.fdt` file.
-fif:
-  value: .fif
-  display_name: Functional Imaging File Format
-  description: |
-    An MEG file format used by Neuromag, Elekta, and MEGIN.
-jpg:
-  value: .jpg
-  display_name: Joint Photographic Experts Group Format
-  description: |
-    A JPEG image file.
-json:
-  value: .json
-  display_name: JavaScript Object Notation
-  description: |
-    A JSON file.
-
-    In the BIDS specification, JSON files are primarily used as "sidecar" files, in which metadata describing "data"
-    files are encoded.
-    These sidecar files follow the inheritance principle.
-
-    There are also a few special cases of JSON files being first-order data files, such as `genetic_info.json`.
-kdf:
-  value: .kdf
-  display_name: KRISS KDF
-  description: |
-    A KRISS (file with extension `.kdf`) file.
-
-    Each experimental run on the KRISS system produces a file with extension `.kdf`.
-    Additional files that may be available in the same folder include
-    the digitized positions of the head points (`\_digitizer.txt`),
-    the position of the center of the MEG coils (`.chn`),
-    and the event markers (`.trg`).
-md:
-  value: .md
-  display_name: Markdown
-  description: |
-    A Markdown file.
-mefd:
-  value: .mefd/
-  display_name: Multiscale Electrophysiology File Format Version 3.0
-  description: |
-    A folder in the [MEF3](https://osf.io/e3sf9/) format.
-
-    Each recording consists of a `.mefd` directory.
-mhd:
-  value: .mhd
-  display_name: ITAB Binary Header
-  description: |
-    Produced by ITAB-ARGOS153 systems. This file a binary header file, and is generated along with a
-    raw data file with the `.raw` extension.
-mrk:
-  value: .mrk
-  display_name: MRK
-  description: |
-    A file containing MEG sensor coil positions.
-
-    Used by KIT, Yokogawa, and Ricoh MEG systems.
-    Successor to the `.sqd` extension for marker files.
-OMEZARR:
-  value: .ome.zarr/
-  display_name: OME Next Generation File Format
-  description: |
-    An OME-NGFF file.
-
-    OME-NGFF is a [Zarr](https://zarr.readthedocs.io)-based format, organizing data arrays in nested directories.
-    This format was developed by the Open Microscopy Environment to provide data stream access to very large data.
-nii:
-  value: .nii
-  display_name: NIfTI
-  description: |
-    A Neuroimaging Informatics Technology Initiative (NIfTI) data file.
-niigz:
-  value: .nii.gz
-  display_name: Compressed NIfTI
-  description: |
-    A compressed Neuroimaging Informatics Technology Initiative (NIfTI) data file.
-nwb:
-  value: .nwb
-  display_name: Neurodata Without Borders Format
-  description: |
-    A [Neurodata Without Borders](https://nwb-schema.readthedocs.io) file.
-
-    Each recording consists of a single `.nwb` file.
-OMEBigTiff:
-  value: .ome.btf
-  display_name: Open Microscopy Environment BigTIFF
-  description: |
-    A [BigTIFF](https://www.awaresystems.be/imaging/tiff/bigtiff.html) image file, for very large images.
-OMETiff:
-  value: .ome.tif
-  display_name: Open Microscopy Environment Tag Image File Format
-  description: |
-    An [OME-TIFF](https://docs.openmicroscopy.org/ome-model/6.1.2/ome-tiff/specification.html#) image file.
-png:
-  value: .png
-  display_name: Portable Network Graphics
-  description: |
-    A [Portable Network Graphics](http://www.libpng.org/pub/png/) file.
-pos:
-  value: .pos
-  display_name: Head Point Position
-  description: |
-    File containing digitized positions of the head points.
-
-    This may be produced by a 4D neuroimaging/BTi MEG system or a CTF MEG system.
-raw:
-  value: .raw
-  display_name: RAW
-  description: |
-    When produced by a KIT / Yokogawa / Ricoh MEG system, this file contains trial-based evoked fields.
-
-    When produced by an ITAB-ARGOS153 system, this file contains raw data and is generated along with
-    an associated binary header file  with the `.mhd` extension.
-rst:
-  value: .rst
-  display_name: reStructuredText
-  description: |
-    A [reStructuredText](https://docutils.sourceforge.io/rst.html) file.
-set:
-  value: .set
-  display_name: EEGLAB SET
-  description: |
-    An [EEGLAB](https://sccn.ucsd.edu/eeglab) file.
-
-    The format used by the MATLAB toolbox [EEGLAB](https://sccn.ucsd.edu/eeglab).
-    Each recording consists of a `.set` file with an optional `.fdt` file.
-sqd:
-  value: .sqd
-  display_name: SQD
-  description: |
-    A file containing either raw MEG data or MEG sensor coil positions.
-    While this extension is still valid, it has been succeeded by `.con` for raw MEG data and `.mrk` for
-    marker information.
-
-    Used by KIT, Yokogawa, and Ricoh MEG systems.
-tif:
-  value: .tif
-  display_name: Tag Image File Format
-  description: |
-    A [Tag Image File Format](https://en.wikipedia.org/wiki/TIFF) file.
-trg:
-  value: .trg
-  display_name: KRISS TRG
-  description: |
-    A file generated by KRISS MEG systems containing the event markers.
-
-    Each experimental run on the KRISS system produces a file with extension `.kdf`.
-    Additional files that may be available in the same folder include
-    the digitized positions of the head points (`\_digitizer.txt`),
-    the position of the center of the MEG coils (`.chn`),
-    and the event markers (`.trg`).
-tsv:
-  value: .tsv
-  display_name: Tab-Delimited
-  description: |
-    A tab-delimited file.
-tsvgz:
-  value: .tsv.gz
-  display_name: Compressed Tab-Delimited
-  description: |
-    A gzipped tab-delimited file.
-    This file extension is only used for very large tabular data, such as physiological recordings.
-    For smaller data, the unzipped `.tsv` extension is preferred.
-txt:
-  value: .txt
-  display_name: Text
-  description: |
-    A free-form text file.
-
-    Tab-delimited files should have the `.tsv` extension rather than a `.txt` extension.
-vhdr:
-  value: .vhdr
-  display_name: BrainVision Text Header
-  description: |
-    A text header file in the
-    [BrainVision Core Data Format](https://www.brainproducts.com/productdetails.php?id=21&tab=5).
-    These files come in three-file sets, including a `.vhdr`, a `.vmrk`, and a `.eeg` file.
-vmrk:
-  value: .vmrk
-  display_name: BrainVision Marker
-  description: |
-    A text marker file in the
-    [BrainVision Core Data Format](https://www.brainproducts.com/productdetails.php?id=21&tab=5).
-    These files come in three-file sets, including a `.vhdr`, a `.vmrk`, and a `.eeg` file.
-Any:
-  value: .*
-  display_name: Any Extension
-  description: |
-    Any extension is allowed.
-None:
-  value: ""
-  display_name: No extension
-  description: |
-    A file with no extension.
-Directory:
-  value: /
-  display_name: Folder
-  description: |
-    A folder with no extension.
-    Corresponds to BTi/4D data.
diff --git a/dandi/support/bids/schemadata/1.7.0+369/objects/formats.yaml b/dandi/support/bids/schemadata/1.7.0+369/objects/formats.yaml
deleted file mode 100644
index c9d58a373..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/objects/formats.yaml
+++ /dev/null
@@ -1,124 +0,0 @@
----
-# This file defines valid patterns for different formats
-# Entity patterns
-index:
-  display_name: Index
-  description: |
-    Non-negative, non-zero integers, optionally prefixed with leading zeros for sortability.
-    An index may not be all zeros.
-  pattern: '[0-9]*[1-9]+[0-9]*'
-label:
-  display_name: Label
-  description: |
-    Freeform labels without special characters.
-  pattern: '[0-9a-zA-Z]+'
-# Metadata types
-boolean:
-  display_name: Boolean
-  description: |
-    A boolean.
-    Must be either "true" or "false".
-  pattern: '(true|false)'
-integer:
-  display_name: Integer
-  description: |
-    An integer which may be positive or negative.
-  pattern: '[+-]?\d+'
-number:
-  display_name: Number
-  description: |
-    A number which may be an integer or float, positive or negative.
-  pattern: '[+-]?([0-9]+([.][0-9]*)?|[.][0-9]+)([eE][+-]?[0-9]+)?'
-string:
-  display_name: String
-  description: |
-    The basic string type (not a specific format).
-    This should allow any free-form string.
-  pattern: '.*'
-# String formats
-bids_uri:
-  display_name: BIDS uniform resource indicator
-  description: |
-    A BIDS uniform resource indicator.
-
-    The validation for this format is minimal.
-    It simply ensures that the value is a string with any characters that may appear in a valid URI,
-    starting with "bids:".
-  pattern: 'bids:[0-9a-zA-Z/#:\?\_\-\.]+'
-dataset_relative:
-  display_name: Path relative to the BIDS dataset directory
-  description: |
-    A path to a file, relative to the dataset directory.
-
-    The validation for this format is minimal.
-    It simply ensures that the value is a string with any characters that may appear in a valid path,
-    without starting with "/" (an absolute path).
-  pattern: '(?!/)[0-9a-zA-Z/\_\-\.]+'
-date:
-  display_name: Date
-  description: |
-    A date in the form `"YYYY-MM-DD[Z]"`,
-    where [Z] is an optional, valid timezone code.
-  pattern: '[0-9]{4}-[0-9]{2}-[0-9]{2}([A-Z]{2,4})?'
-datetime:
-  display_name: Datetime
-  description: |
-    A datetime in the form `"YYYY-MM-DDThh:mm:ss[.000000][Z]"`,
-    where [.000000] is an optional subsecond resolution between 1 and 6 decimal points,
-    and [Z] is an optional, valid timezone code.
-  pattern: '[0-9]{4}-[0-9]{2}-[0-9]{2}T(?:2[0-3]|[01][0-9]):[0-5][0-9]:[0-5][0-9](\.[0-9]{1,6})?([A-Z]{2,4})?'
-file_relative:
-  display_name: Path relative to the parent file
-  description: |
-    A path to a file, relative to the file in which the field is defined.
-
-    The validation for this format is minimal.
-    It simply ensures that the value is a string with any characters that may appear in a valid path,
-    without starting with "/" (an absolute path).
-  pattern: '(?!/)[0-9a-zA-Z/\_\-\.]+'
-participant_relative:
-  display_name: Path relative to the participant directory
-  description: |
-    A path to a file, relative to the participant's directory in the dataset.
-
-    The validation for this format is minimal.
-    It simply ensures that the value is a string with any characters that may appear in a valid path,
-    without starting with "/" (an absolute path) or "sub/"
-    (a relative path starting with the participant directory, rather than relative to that directory).
-  pattern: '(?!/)(?!sub-)[0-9a-zA-Z/\_\-\.]+'
-rrid:
-  display_name: Research resource identifier
-  description: |
-    A [research resource identifier](https://scicrunch.org/resources).
-  pattern: 'RRID:.+_.+'
-stimuli_relative:
-  display_name: Path relative to the stimuli directory
-  description: |
-    A path to a stimulus file, relative to a `/stimuli` directory somewhere.
-
-    The validation for this format is minimal.
-    It simply ensures that the value is a string with any characters that may appear in a valid path,
-    without starting with "/" (an absolute path) or "stimuli/"
-    (a relative path starting with the stimuli directory, rather than relative to that directory).
-  pattern: '(?!/)(?!stimuli/)[0-9a-zA-Z/\_\-\.]+'
-time:
-  display_name: Time
-  description: |
-    A time in the form `"hh:mm:ss"`.
-  pattern: '(?:2[0-3]|[01]?[0-9]):[0-5][0-9]:[0-5][0-9]'
-unit:
-  display_name: A standardized unit
-  description: |
-    A unit.
-    SI units in CMIXF formatting are RECOMMENDED
-    (see [Units](/02-common-principles.html#units)).
-
-    Currently this matches any string.
-
-    TODO: Somehow reference the actual unit options in the Units appendix.
-  pattern: '.*'
-uri:
-  display_name: Uniform resource indicator
-  description: |
-    A uniform resource indicator.
-  pattern: '(([^:/?#]+):)?(//([^/?#]*))?([^?#]*)(\?([^#]*))?(#(.*))?'
diff --git a/dandi/support/bids/schemadata/1.7.0+369/objects/metadata.yaml b/dandi/support/bids/schemadata/1.7.0+369/objects/metadata.yaml
deleted file mode 100644
index fadca711c..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/objects/metadata.yaml
+++ /dev/null
@@ -1,3332 +0,0 @@
----
-# This file defines valid BIDS metadata fields.
-# These definitions include the field names, their descriptions, and valid values.
-# This file **does not** define how and when metadata fields can be used with a given file.
-Acknowledgements:
-  name: Acknowledgements
-  display_name: Acknowledgements
-  description: |
-    Text acknowledging contributions of individuals or institutions beyond
-    those listed in Authors or Funding.
-  type: string
-AcquisitionDuration:
-  name: AcquisitionDuration
-  display_name: Acquisition Duration
-  description: |
-    Duration (in seconds) of volume acquisition.
-    Corresponds to DICOM Tag 0018, 9073 `Acquisition Duration`.
-    This field is mutually exclusive with `"RepetitionTime"`.
-  type: number
-  exclusiveMinimum: 0
-  unit: s
-AcquisitionMode:
-  name: AcquisitionMode
-  display_name: Acquisition Mode
-  description: |
-    Type of acquisition of the PET data (for example, `"list mode"`).
-  type: string
-AcquisitionVoxelSize:
-  name: AcquisitionVoxelSize
-  display_name: Acquisition Voxel Size
-  description: |
-    An array of numbers with a length of 3, in millimeters.
-    This parameter denotes the original acquisition voxel size,
-    excluding any inter-slice gaps and before any interpolation or resampling
-    within reconstruction or image processing.
-    Any point spread function effects, for example due to T2-blurring,
-    that would decrease the effective resolution are not considered here.
-  type: array
-  minItems: 3
-  maxItems: 3
-  items:
-    type: number
-    exclusiveMinimum: 0
-    unit: mm
-Anaesthesia:
-  name: Anaesthesia
-  display_name: Anaesthesia
-  description: |
-    Details of anaesthesia used, if any.
-  type: string
-AnalyticalApproach:
-  name: AnalyticalApproach
-  display_name: Analytical Approach
-  description: |
-    Methodology or methodologies used to analyse the `"GeneticLevel"`.
-    Values MUST be taken from the
-    [database of Genotypes and Phenotypes
-    (dbGaP)](https://www.ncbi.nlm.nih.gov/gap/advanced)
-    under /Study/Molecular Data Type (for example, SNP Genotypes (Array) or
-    Methylation (CpG).
-  anyOf:
-  - type: string
-  - type: array
-    items:
-      type: string
-AnatomicalLandmarkCoordinateSystem:
-  name: AnatomicalLandmarkCoordinateSystem
-  display_name: Anatomical Landmark Coordinate System
-  description: |
-    Defines the coordinate system for the anatomical landmarks.
-    See [Appendix VIII](SPEC_ROOT/99-appendices/08-coordinate-systems.md)
-    for a list of restricted keywords for coordinate systems.
-    If `"Other"`, provide definition of the coordinate system in
-    `"AnatomicalLandmarkCoordinateSystemDescription"`.
-  anyOf:
-  - $ref: _MEGCoordSys
-  - $ref: _EEGCoordSys
-  - $ref: _StandardTemplateCoordSys
-  - $ref: _StandardTemplateDeprecatedCoordSys
-AnatomicalLandmarkCoordinateSystemDescription:
-  name: AnatomicalLandmarkCoordinateSystemDescription
-  display_name: Anatomical Landmark Coordinate System Description
-  description: |
-    Free-form text description of the coordinate system.
-    May also include a link to a documentation page or paper describing the
-    system in greater detail.
-  type: string
-AnatomicalLandmarkCoordinateUnits:
-  name: AnatomicalLandmarkCoordinateUnits
-  display_name: Anatomical Landmark Coordinate Units
-  description: |
-    Units of the coordinates of `"AnatomicalLandmarkCoordinateSystem"`.
-  type: string
-  enum:
-  - m
-  - mm
-  - cm
-  - n/a
-AnatomicalLandmarkCoordinates:
-  name: AnatomicalLandmarkCoordinates
-  display_name: Anatomical Landmark Coordinates
-  description: |
-    Key-value pairs of the labels and 3-D digitized locations of anatomical landmarks,
-    interpreted following the `"AnatomicalLandmarkCoordinateSystem"`
-    (for example, `{"NAS": [12.7,21.3,13.9], "LPA": [5.2,11.3,9.6],
-    "RPA": [20.2,11.3,9.1]}`.
-    Each array MUST contain three numeric values corresponding to x, y, and z
-    axis of the coordinate system in that exact order.
-  type: object
-  additionalProperties:
-    type: array
-    items:
-      type: number
-    minItems: 3
-    maxItems: 3
-# Redefinition of AnatomicalLandmarkCoordinates for MRI data
-AnatomicalLandmarkCoordinates__mri:
-  name: AnatomicalLandmarkCoordinates
-  display_name: Anatomical Landmark Coordinates
-  description: |
-    Key-value pairs of any number of additional anatomical landmarks and their
-    coordinates in voxel units (where first voxel has index 0,0,0)
-    relative to the associated anatomical MRI
-    (for example, `{"AC": [127,119,149], "PC": [128,93,141],
-    "IH": [131,114,206]}`, or `{"NAS": [127,213,139], "LPA": [52,113,96],
-    "RPA": [202,113,91]}`).
-    Each array MUST contain three numeric values corresponding to x, y, and z
-    axis of the coordinate system in that exact order.
-  type: object
-  additionalProperties:
-    type: array
-    items:
-      type: number
-    minItems: 3
-    maxItems: 3
-ArterialSpinLabelingType:
-  name: ArterialSpinLabelingType
-  display_name: Arterial Spin Labeling Type
-  description: |
-    The arterial spin labeling type.
-  type: string
-  enum:
-  - CASL
-  - PCASL
-  - PASL
-AssociatedEmptyRoom:
-  name: AssociatedEmptyRoom
-  display_name: Associated Empty Room
-  description: |
-    A path pointing to an empty-room file associated with
-    the subject's MEG recording.
-    The path is relative to the BIDS dataset root.
-    The path needs to use forward slashes instead of backward slashes
-    (for example,
-    "sub-emptyroom/ses-rest/meg/sub-emptyroom_ses-rest_task-noise_run-01_meg.ds").
-    Supplying a list of several paths to empty-room files is possible.
-  anyOf:
-  - type: array
-    items:
-      type: string
-      format: dataset_relative
-  - type: string
-    format: dataset_relative
-Atlas:
-  name: Atlas
-  display_name: Atlas
-  description: |
-    Which atlas (if any) was used to generate the mask.
-  type: string
-AttenuationCorrection:
-  name: AttenuationCorrection
-  display_name: Attenuation Correction
-  description: |
-    Short description of the attenuation correction method used.
-  type: string
-AttenuationCorrectionMethodReference:
-  name: AttenuationCorrectionMethodReference
-  display_name: Attenuation Correction Method Reference
-  description: |
-    Reference paper for the attenuation correction method used.
-  type: string
-Authors:
-  name: Authors
-  display_name: Authors
-  description: |
-    List of individuals who contributed to the creation/curation of the dataset.
-  type: array
-  items:
-    type: string
-B0FieldIdentifier:
-  name: B0FieldIdentifier
-  display_name: B0 Field Identifier
-  description: |
-    The presence of this key states that this particular 3D or 4D image MAY be
-    used for fieldmap estimation purposes.
-    Each `"B0FieldIdentifier"` MUST be a unique string within one participant's tree,
-    shared only by the images meant to be used as inputs for the estimation of a
-    particular instance of the *B<sub>0</sub> field* estimation.
-    It is RECOMMENDED to derive this identifier from DICOM Tags, for example,
-    DICOM tag 0018, 1030 `Protocol Name`, or DICOM tag 0018, 0024 `Sequence Name`
-    when the former is not defined (for example, in GE devices.)
-  anyOf:
-  - type: string
-  - type: array
-    items:
-      type: string
-B0FieldSource:
-  name: B0FieldSource
-  display_name: B0 Field Source
-  description: |
-    At least one existing `"B0FieldIdentifier"` defined by images in the
-    participant's tree.
-    This field states the *B<sub>0</sub> field* estimation designated by the
-    `"B0FieldIdentifier"` that may be used to correct the dataset for distortions
-    caused by B<sub>0</sub> inhomogeneities.
-    `"B0FieldSource"` and `"B0FieldIdentifier"` MAY both be present for images that
-    are used to estimate their own B<sub>0</sub> field, for example, in "pepolar"
-    acquisitions.
-  anyOf:
-  - type: string
-  - type: array
-    items:
-      type: string
-BIDSVersion:
-  name: BIDSVersion
-  display_name: BIDS Version
-  description: |
-    The version of the BIDS standard that was used.
-  type: string
-BackgroundSuppression:
-  name: BackgroundSuppression
-  display_name: Background Suppression
-  description: |
-    Boolean indicating if background suppression is used.
-  type: boolean
-BackgroundSuppressionNumberPulses:
-  name: BackgroundSuppressionNumberPulses
-  display_name: Background Suppression Number Pulses
-  description: |
-    The number of background suppression pulses used.
-    Note that this excludes any effect of background suppression pulses applied
-    before the labeling.
-  type: number
-  minimum: 0
-BackgroundSuppressionPulseTime:
-  name: BackgroundSuppressionPulseTime
-  display_name: Background Suppression Pulse Time
-  description: |
-    Array of numbers containing timing, in seconds,
-    of the background suppression pulses with respect to the start of the
-    labeling.
-    In case of multi-PLD with different background suppression pulse times,
-    only the pulse time of the first PLD should be defined.
-  type: array
-  items:
-    type: number
-    minimum: 0
-    unit: s
-BasedOn:
-  name: BasedOn
-  display_name: Based On
-  description: |
-    List of files in a file collection to generate the map.
-    Fieldmaps are also listed, if involved in the processing.
-  anyOf:
-  - type: string
-    format: participant_relative
-  - type: array
-    items:
-      type: string
-      format: participant_relative
-BloodDensity:
-  name: BloodDensity
-  display_name: Blood Density
-  description: |
-    Measured blood density. Unit of blood density should be in `"g/mL"`.
-  type: number
-  unit: g/mL
-BodyPart:
-  name: BodyPart
-  display_name: Body Part
-  description: |
-    Body part of the organ / body region scanned.
-  type: string
-BodyPartDetails:
-  name: BodyPartDetails
-  display_name: Body Part Details
-  description: |
-    Additional details about body part or location (for example: `"corpus callosum"`).
-  type: string
-BodyPartDetailsOntology:
-  name: BodyPartDetailsOntology
-  display_name: Body Part Details Ontology
-  description: |
-    [URI](SPEC_ROOT/02-common-principles.md#uniform-resource-indicator) of ontology used for
-    BodyPartDetails (for example: `"https://www.ebi.ac.uk/ols/ontologies/uberon"`).
-  type: string
-  format: uri
-BolusCutOffDelayTime:
-  name: BolusCutOffDelayTime
-  display_name: Bolus Cut Off Delay Time
-  description: |
-    Duration between the end of the labeling and the start of the bolus cut-off
-    saturation pulse(s), in seconds.
-    This can be a number or array of numbers, of which the values must be
-    non-negative and monotonically increasing, depending on the number of bolus
-    cut-off saturation pulses.
-    For Q2TIPS, only the values for the first and last bolus cut-off saturation
-    pulses are provided.
-    Based on DICOM Tag 0018, 925F `ASL Bolus Cut-off Delay Time`.
-  anyOf:
-  - type: number
-    minimum: 0
-    unit: s
-  - type: array
-    items:
-      type: number
-      unit: s
-      minimum: 0
-BolusCutOffFlag:
-  name: BolusCutOffFlag
-  display_name: Bolus Cut Off Flag
-  description: |
-    Boolean indicating if a bolus cut-off technique is used.
-    Corresponds to DICOM Tag 0018, 925C `ASL Bolus Cut-off Flag`.
-  type: boolean
-BolusCutOffTechnique:
-  name: BolusCutOffTechnique
-  display_name: Bolus Cut Off Technique
-  description: |
-    Name of the technique used, for example `"Q2TIPS"`, `"QUIPSS"`, `"QUIPSSII"`.
-    Corresponds to DICOM Tag 0018, 925E `ASL Bolus Cut-off Technique`.
-  type: string
-BrainLocation:
-  name: BrainLocation
-  display_name: Brain Location
-  description: |
-    Refers to the location in space of the `"TissueOrigin"`.
-    Values may be an MNI coordinate,
-    a label taken from the
-    [Allen Brain Atlas](https://atlas.brain-map.org/atlas?atlas=265297125&plate=\
-    112360888&structure=4392&x=40348.15104166667&y=46928.75&zoom=-7&resolution=\
-    206.60&z=3),
-    or layer to refer to layer-specific gene expression,
-    which can also tie up with laminar fMRI.
-  type: string
-CASLType:
-  name: CASLType
-  display_name: CASL Type
-  description: |
-    Describes if a separate coil is used for labeling.
-  type: string
-  enum:
-  - single-coil
-  - double-coil
-CapManufacturer:
-  name: CapManufacturer
-  display_name: Cap Manufacturer
-  description: |
-    Name of the cap manufacturer (for example, `"EasyCap"`).
-  type: string
-CapManufacturersModelName:
-  name: CapManufacturersModelName
-  display_name: Cap Manufacturers Model Name
-  description: |
-    Manufacturer's designation of the EEG cap model
-    (for example, `"actiCAP 64 Ch Standard-2"`).
-  type: string
-CellType:
-  name: CellType
-  display_name: Cell Type
-  description: |
-    Describes the type of cell analyzed.
-    Values SHOULD come from the
-    [cell ontology](http://obofoundry.org/ontology/cl.html).
-  type: string
-ChunkTransformationMatrix:
-  name: ChunkTransformationMatrix
-  display_name: Chunk Transformation Matrix
-  description: |
-    3x3 or 4x4 affine transformation matrix describing spatial chunk transformation,
-    for 2D and 3D respectively (for examples: `[[2, 0, 0], [0, 3, 0], [0, 0, 1]]`
-    in 2D for 2x and 3x scaling along the first and second axis respectively; or
-    `[[1, 0, 0, 0], [0, 2, 0, 0], [0, 0, 3, 0], [0, 0, 0, 1]]` in 3D for 2x and 3x
-    scaling along the second and third axis respectively).
-    Note that non-spatial dimensions like time and channel are not included in the
-    transformation matrix.
-  anyOf:
-  - type: array
-    minItems: 3
-    maxItems: 3
-    items:
-      type: array
-      minItems: 3
-      maxItems: 3
-      items:
-        type: number
-  - type: array
-    minItems: 4
-    maxItems: 4
-    items:
-      type: array
-      minItems: 4
-      maxItems: 4
-      items:
-        type: number
-ChunkTransformationMatrixAxis:
-  name: ChunkTransformationMatrixAxis
-  display_name: Chunk Transformation Matrix Axis
-  description: |
-    Describe the axis of the ChunkTransformationMatrix
-    (for examples: `["X", "Y"]` or `["Z", "Y", "X"]`).
-  type: array
-  items:
-    type: string
-    minItems: 2
-    maxItems: 3
-Code:
-  name: Code
-  display_name: Code
-  description: |
-    [URI](SPEC_ROOT/02-common-principles.md#uniform-resource-indicator)
-    of the code used to present the stimuli.
-    Persistent identifiers such as DOIs are preferred.
-    If multiple versions of code may be hosted at the same location,
-    revision-specific URIs are recommended.
-  type: string
-  format: uri
-CogAtlasID:
-  name: CogAtlasID
-  display_name: Cognitive Atlas ID
-  description: |
-    [URI](SPEC_ROOT/02-common-principles.md#uniform-resource-indicator)
-    of the corresponding [Cognitive Atlas](https://www.cognitiveatlas.org/)
-    Task term.
-  type: string
-  format: uri
-CogPOID:
-  name: CogPOID
-  display_name: Cognitive Paradigm Ontology ID
-  description: |
-    [URI](SPEC_ROOT/02-common-principles.md#uniform-resource-indicator)
-    of the corresponding [CogPO](http://www.cogpo.org/) term.
-  type: string
-  format: uri
-CoilCombinationMethod:
-  name: CoilCombinationMethod
-  display_name: Coil Combination Method
-  description: |
-    Almost all fMRI studies using phased-array coils use root-sum-of-squares
-    (rSOS) combination, but other methods exist.
-    The image reconstruction is changed by the coil combination method
-    (as for the matrix coil mode above),
-    so anything non-standard should be reported.
-  type: string
-Columns:
-  name: Columns
-  display_name: Columns
-  description: |
-    Names of columns in file.
-  type: array
-  items:
-    type: string
-ContinuousHeadLocalization:
-  name: ContinuousHeadLocalization
-  display_name: Continuous Head Localization
-  description: |
-    `true` or `false` value indicating whether continuous head localisation
-    was performed.
-  type: boolean
-ContrastBolusIngredient:
-  name: ContrastBolusIngredient
-  display_name: Contrast Bolus Ingredient
-  description: |
-    Active ingredient of agent.
-    Corresponds to DICOM Tag 0018, 1048 `Contrast/Bolus Ingredient`.
-  type: string
-  enum:
-  - IODINE
-  - GADOLINIUM
-  - CARBON DIOXIDE
-  - BARIUM
-  - XENON
-DCOffsetCorrection:
-  name: DCOffsetCorrection
-  display_name: DC Offset Correction
-  description: |
-    A description of the method (if any) used to correct for a DC offset.
-    If the method used was subtracting the mean value for each channel,
-    use "mean".
-  type: string
-DatasetDOI:
-  name: DatasetDOI
-  display_name: DatasetDOI
-  description: |
-    The Digital Object Identifier of the dataset (not the corresponding paper).
-    DOIs SHOULD be expressed as a valid
-    [URI](SPEC_ROOT/02-common-principles.md#uniform-resource-indicator);
-    bare DOIs such as `10.0.2.3/dfjj.10` are
-    [DEPRECATED](SPEC_ROOT/02-common-principles.md#definitions).
-  type: string
-  format: uri
-DatasetType:
-  name: DatasetType
-  display_name: Dataset Type
-  description: |
-    The interpretation of the dataset.
-    For backwards compatibility, the default value is `"raw"`.
-  type: string
-  enum:
-  - raw
-  - derivative
-DecayCorrectionFactor:
-  name: DecayCorrectionFactor
-  display_name: Decay Correction Factor
-  description: |
-    Decay correction factor for each frame.
-  type: array
-  items:
-    type: number
-DelayAfterTrigger:
-  name: DelayAfterTrigger
-  display_name: Delay After Trigger
-  description: |
-    Duration (in seconds) from trigger delivery to scan onset.
-    This delay is commonly caused by adjustments and loading times.
-    This specification is entirely independent of
-    `"NumberOfVolumesDiscardedByScanner"` or `"NumberOfVolumesDiscardedByUser"`,
-    as the delay precedes the acquisition.
-  type: number
-  unit: s
-DelayTime:
-  name: DelayTime
-  display_name: Delay Time
-  description: |
-    User specified time (in seconds) to delay the acquisition of data for the
-    following volume.
-    If the field is not present it is assumed to be set to zero.
-    Corresponds to Siemens CSA header field `lDelayTimeInTR`.
-    This field is REQUIRED for sparse sequences using the `"RepetitionTime"` field
-    that do not have the `"SliceTiming"` field set to allowed for accurate
-    calculation of "acquisition time".
-    This field is mutually exclusive with `"VolumeTiming"`.
-  type: number
-  unit: s
-Density:
-  name: Density
-  display_name: Density
-  description: |
-    Specifies the interpretation of the density keyword.
-    If an object is used, then the keys should be values for the `den` entity
-    and values should be descriptions of those `den` values.
-  anyOf:
-  - type: string
-  - type: object
-    additionalProperties:
-      type: string
-Derivative:
-  name: Derivative
-  display_name: Derivative
-  description: |
-    Indicates that values in the corresponding column are transformations of values
-    from other columns (for example a summary score based on a subset of items in a
-    questionnaire).
-  type: boolean
-Description:
-  name: Description
-  display_name: Description
-  description: |
-    Free-form natural language description.
-  type: string
-DeviceSerialNumber:
-  name: DeviceSerialNumber
-  display_name: Device Serial Number
-  description: |
-    The serial number of the equipment that produced the measurements.
-    A pseudonym can also be used to prevent the equipment from being
-    identifiable, so long as each pseudonym is unique within the dataset.
-  type: string
-DewarPosition:
-  name: DewarPosition
-  display_name: Dewar Position
-  description: |
-    Position of the dewar during the MEG scan:
-    `"upright"`, `"supine"` or `"degrees"` of angle from vertical:
-    for example on CTF systems, `"upright=15°, supine=90°"`.
-  type: string
-DigitizedHeadPoints:
-  name: DigitizedHeadPoints
-  display_name: Digitized Head Points
-  description: |
-    `true` or `false` value indicating whether head points outlining the
-    scalp/face surface are contained within this recording.
-  type: boolean
-DigitizedHeadPoints__coordsystem:
-  name: DigitizedHeadPoints
-  display_name: Digitized Head Points
-  description: |
-    Relative path to the file containing the locations of digitized head points
-    collected during the session (for example, `"sub-01_headshape.pos"`).
-    RECOMMENDED for all MEG systems, especially for CTF and BTi/4D.
-    For Elekta/Neuromag the head points will be stored in the fif file.
-  type: string
-  format: file_relative
-DigitizedHeadPointsCoordinateSystem:
-  name: DigitizedHeadPointsCoordinateSystem
-  display_name: Digitized Head Points Coordinate System
-  description: |
-    Defines the coordinate system for the digitized head points.
-    See
-    [Appendix VIII](SPEC_ROOT/99-appendices/08-coordinate-systems.md)
-    for a list of restricted keywords for coordinate systems.
-    If `"Other"`, provide definition of the coordinate system in
-    `"DigitizedHeadPointsCoordinateSystemDescription"`.
-  anyOf:
-  - $ref: _MEGCoordSys
-  - $ref: _EEGCoordSys
-  - $ref: _StandardTemplateCoordSys
-  - $ref: _StandardTemplateDeprecatedCoordSys
-DigitizedHeadPointsCoordinateSystemDescription:
-  name: DigitizedHeadPointsCoordinateSystemDescription
-  display_name: Digitized Head Points Coordinate System Description
-  description: |
-    Free-form text description of the coordinate system.
-    May also include a link to a documentation page or paper describing the
-    system in greater detail.
-  type: string
-DigitizedHeadPointsCoordinateUnits:
-  name: DigitizedHeadPointsCoordinateUnits
-  display_name: Digitized Head Points Coordinate Units
-  description: |
-    Units of the coordinates of `"DigitizedHeadPointsCoordinateSystem"`.
-  type: string
-  enum:
-  - m
-  - mm
-  - cm
-  - n/a
-DigitizedLandmarks:
-  name: DigitizedLandmarks
-  display_name: Digitized Landmarks
-  description: |
-    `true` or `false` value indicating whether anatomical landmark points
-    (fiducials) are contained within this recording.
-  type: boolean
-DispersionConstant:
-  name: DispersionConstant
-  display_name: Dispersion Constant
-  description: |
-    External dispersion time constant resulting from tubing in default unit
-    seconds.
-  type: number
-  unit: s
-DispersionCorrected:
-  name: DispersionCorrected
-  display_name: Dispersion Corrected
-  description: |
-    Boolean flag specifying whether the blood data have been dispersion-corrected.
-    NOTE: not customary for manual samples, and hence should be set to `false`.
-  type: boolean
-DoseCalibrationFactor:
-  name: DoseCalibrationFactor
-  display_name: Dose Calibration Factor
-  description: |
-    Multiplication factor used to transform raw data (in counts/sec) to meaningful unit (Bq/ml).
-    Corresponds to DICOM Tag 0054, 1322 `Dose Calibration Factor`.
-  type: number
-DwellTime:
-  name: DwellTime
-  display_name: Dwell Time
-  description: |
-    Actual dwell time (in seconds) of the receiver per point in the readout
-    direction, including any oversampling.
-    For Siemens, this corresponds to DICOM field 0019, 1018 (in ns).
-    This value is necessary for the optional readout distortion correction of
-    anatomicals in the HCP Pipelines.
-    It also usefully provides a handle on the readout bandwidth,
-    which isn't captured in the other metadata tags.
-    Not to be confused with `"EffectiveEchoSpacing"`, and the frequent mislabeling
-    of echo spacing (which is spacing in the phase encoding direction) as
-    "dwell time" (which is spacing in the readout direction).
-  type: number
-  unit: s
-ECGChannelCount:
-  name: ECGChannelCount
-  display_name: ECG Channel Count
-  description: |
-    Number of ECG channels.
-  type: integer
-  minimum: 0
-ECOGChannelCount:
-  name: ECOGChannelCount
-  display_name: ECOG Channel Count
-  description: |
-    Number of ECoG channels.
-  type: integer
-  minimum: 0
-EEGChannelCount:
-  name: EEGChannelCount
-  display_name: EEG Channel Count
-  description: |
-    Number of EEG channels recorded simultaneously (for example, `21`).
-  type: integer
-  minimum: 0
-EEGCoordinateSystem:
-  name: EEGCoordinateSystem
-  display_name: EEG Coordinate System
-  description: |
-    Defines the coordinate system for the EEG sensors.
-
-    See
-    [Appendix VIII](SPEC_ROOT/99-appendices/08-coordinate-systems.md)
-    for a list of restricted keywords for coordinate systems.
-    If `"Other"`, provide definition of the coordinate system in
-    `EEGCoordinateSystemDescription`.
-  anyOf:
-  - $ref: _MEGCoordSys
-  - $ref: _EEGCoordSys
-  - $ref: _StandardTemplateCoordSys
-  - $ref: _StandardTemplateDeprecatedCoordSys
-EEGCoordinateSystemDescription:
-  name: EEGCoordinateSystemDescription
-  display_name: EEG Coordinate System Description
-  description: |
-    Free-form text description of the coordinate system.
-    May also include a link to a documentation page or paper describing the
-    system in greater detail.
-  type: string
-EEGCoordinateUnits:
-  name: EEGCoordinateUnits
-  display_name: EEG Coordinate Units
-  description: |
-    Units of the coordinates of `EEGCoordinateSystem`.
-  type: string
-  enum:
-  - m
-  - mm
-  - cm
-  - n/a
-EEGGround:
-  name: EEGGround
-  display_name: EEG Ground
-  description: |
-    Description of the location of the ground electrode
-    (for example, `"placed on right mastoid (M2)"`).
-  type: string
-EEGPlacementScheme:
-  name: EEGPlacementScheme
-  display_name: EEG Placement Scheme
-  description: |
-    Placement scheme of EEG electrodes.
-    Either the name of a standardized placement system (for example, `"10-20"`)
-    or a list of standardized electrode names (for example, `["Cz", "Pz"]`).
-  type: string
-EEGReference:
-  name: EEGReference
-  display_name: EEG Reference
-  description: |
-    General description of the reference scheme used and (when applicable) of
-    location of the reference electrode in the raw recordings
-    (for example, `"left mastoid"`, `"Cz"`, `"CMS"`).
-    If different channels have a different reference,
-    this field should have a general description and the channel specific
-    reference should be defined in the `channels.tsv` file.
-  type: string
-EMGChannelCount:
-  name: EMGChannelCount
-  display_name: EMG Channel Count
-  description: |
-    Number of EMG channels.
-  type: integer
-  minimum: 0
-EOGChannelCount:
-  name: EOGChannelCount
-  display_name: EOG Channel Count
-  description: |
-    Number of EOG channels.
-  type: integer
-  minimum: 0
-EchoTime:
-  name: EchoTime
-  display_name: Echo Time
-  description: |
-    The echo time (TE) for the acquisition, specified in seconds.
-    Corresponds to DICOM Tag 0018, 0081 `Echo Time`
-    (please note that the DICOM term is in milliseconds not seconds).
-    The data type number may apply to files from any MRI modality concerned with
-    a single value for this field, or to the files in a
-    [file collection](SPEC_ROOT/99-appendices/10-file-collections.md)
-    where the value of this field is iterated using the
-    [`echo` entity](SPEC_ROOT/99-appendices/09-entities.md#echo).
-    The data type array provides a value for each volume in a 4D dataset and
-    should only be used when the volume timing is critical for interpretation
-    of the data, such as in
-    [ASL](SPEC_ROOT/04-modality-specific-files/01-magnetic-resonance-imaging-data.md#\
-    arterial-spin-labeling-perfusion-data)
-    or variable echo time fMRI sequences.
-  anyOf:
-  - type: number
-    unit: s
-    exclusiveMinimum: 0
-  - type: array
-    items:
-      type: number
-      unit: s
-      exclusiveMinimum: 0
-EchoTime1:
-  name: EchoTime1
-  display_name: Echo Time1
-  description: |
-    The time (in seconds) when the first (shorter) echo occurs.
-  type: number
-  unit: s
-  exclusiveMinimum: 0
-EchoTime2:
-  name: EchoTime2
-  display_name: Echo Time2
-  description: |
-    The time (in seconds) when the second (longer) echo occurs.
-  type: number
-  unit: s
-  exclusiveMinimum: 0
-# Redefinition of EchoTime for fieldmap data
-EchoTime__fmap:
-  name: EchoTime
-  display_name: Echo Time
-  description: |
-    The time (in seconds) when the echo corresponding to this map was acquired.
-  type: number
-  unit: s
-  exclusiveMinimum: 0
-EffectiveEchoSpacing:
-  name: EffectiveEchoSpacing
-  display_name: Effective Echo Spacing
-  description: |
-    The "effective" sampling interval, specified in seconds,
-    between lines in the phase-encoding direction,
-    defined based on the size of the reconstructed image in the phase direction.
-    It is frequently, but incorrectly, referred to as "dwell time"
-    (see the `"DwellTime"` parameter for actual dwell time).
-    It is required for unwarping distortions using field maps.
-    Note that beyond just in-plane acceleration,
-    a variety of other manipulations to the phase encoding need to be accounted
-    for properly, including partial fourier, phase oversampling,
-    phase resolution, phase field-of-view and interpolation.
-  type: number
-  exclusiveMinimum: 0
-  unit: s
-ElectricalStimulation:
-  name: ElectricalStimulation
-  display_name: Electrical Stimulation
-  description: |
-    Boolean field to specify if electrical stimulation was done during the
-    recording (options are `true` or `false`). Parameters for event-like
-    stimulation should be specified in the `events.tsv` file.
-  type: boolean
-ElectricalStimulationParameters:
-  name: ElectricalStimulationParameters
-  display_name: Electrical Stimulation Parameters
-  description: |
-    Free form description of stimulation parameters, such as frequency or shape.
-    Specific onsets can be specified in the events.tsv file.
-    Specific shapes can be described here in freeform text.
-  type: string
-ElectrodeManufacturer:
-  name: ElectrodeManufacturer
-  display_name: Electrode Manufacturer
-  description: |
-    Can be used if all electrodes are of the same manufacturer
-    (for example, `"AD-TECH"`, `"DIXI"`).
-    If electrodes of different manufacturers are used,
-    please use the corresponding table in the `_electrodes.tsv` file.
-  type: string
-ElectrodeManufacturersModelName:
-  name: ElectrodeManufacturersModelName
-  display_name: Electrode Manufacturers Model Name
-  description: |
-    If different electrode types are used,
-    please use the corresponding table in the `_electrodes.tsv` file.
-  type: string
-EpochLength:
-  name: EpochLength
-  display_name: Epoch Length
-  description: |
-    Duration of individual epochs in seconds (for example, `1`)
-    in case of epoched data.
-    If recording was continuous or discontinuous, leave out the field.
-  type: number
-  minimum: 0
-EstimationAlgorithm:
-  name: EstimationAlgorithm
-  display_name: Estimation Algorithm
-  description: |
-    Type of algorithm used to perform fitting
-    (for example, `"linear"`, `"non-linear"`, `"LM"` and such).
-  type: string
-EstimationReference:
-  name: EstimationReference
-  display_name: Estimation Reference
-  description: |
-    Reference to the study/studies on which the implementation is based.
-  type: string
-EthicsApprovals:
-  name: EthicsApprovals
-  display_name: Ethics Approvals
-  description: |
-    List of ethics committee approvals of the research protocols and/or
-    protocol identifiers.
-  type: array
-  items:
-    type: string
-FiducialsCoordinateSystem:
-  name: FiducialsCoordinateSystem
-  display_name: Fiducials Coordinate System
-  description: |
-    Defines the coordinate system for the fiducials.
-    Preferably the same as the `"EEGCoordinateSystem"`.
-    See
-    [Appendix VIII](SPEC_ROOT/99-appendices/08-coordinate-systems.md)
-    for a list of restricted keywords for coordinate systems.
-    If `"Other"`, provide definition of the coordinate system in
-    `"FiducialsCoordinateSystemDescription"`.
-  anyOf:
-  - $ref: _MEGCoordSys
-  - $ref: _EEGCoordSys
-  - $ref: _StandardTemplateCoordSys
-  - $ref: _StandardTemplateDeprecatedCoordSys
-FiducialsCoordinateSystemDescription:
-  name: FiducialsCoordinateSystemDescription
-  display_name: Fiducials Coordinate System Description
-  description: |
-    Free-form text description of the coordinate system.
-    May also include a link to a documentation page or paper describing the
-    system in greater detail.
-  type: string
-FiducialsCoordinateUnits:
-  name: FiducialsCoordinateUnits
-  display_name: Fiducials Coordinate Units
-  description: |
-    Units in which the coordinates that are  listed in the field
-    `"FiducialsCoordinateSystem"` are represented.
-  type: string
-  enum:
-  - m
-  - mm
-  - cm
-  - n/a
-FiducialsCoordinates:
-  name: FiducialsCoordinates
-  display_name: Fiducials Coordinates
-  description: |
-    Key-value pairs of the labels and 3-D digitized position of anatomical
-    landmarks, interpreted following the `"FiducialsCoordinateSystem"`
-    (for example, `{"NAS": [12.7,21.3,13.9], "LPA": [5.2,11.3,9.6],
-    "RPA": [20.2,11.3,9.1]}`).
-    Each array MUST contain three numeric values corresponding to x, y, and z
-    axis of the coordinate system in that exact order.
-  type: object
-  additionalProperties:
-    type: array
-    items:
-      type: number
-    minItems: 3
-    maxItems: 3
-FiducialsDescription:
-  name: FiducialsDescription
-  display_name: Fiducials Description
-  description: |
-    Free-form text description of how the fiducials such as vitamin-E capsules
-    were placed relative to anatomical landmarks,
-    and how the position of the fiducials were measured
-    (for example, `"both with Polhemus and with T1w MRI"`).
-  type: string
-FlipAngle:
-  name: FlipAngle
-  display_name: Flip Angle
-  description: |
-    Flip angle (FA) for the acquisition, specified in degrees.
-    Corresponds to: DICOM Tag 0018, 1314 `Flip Angle`.
-    The data type number may apply to files from any MRI modality concerned with
-    a single value for this field, or to the files in a
-    [file collection](SPEC_ROOT/99-appendices/10-file-collections.md)
-    where the value of this field is iterated using the
-    [`flip` entity](SPEC_ROOT/99-appendices/09-entities.md#flip).
-    The data type array provides a value for each volume in a 4D dataset and
-    should only be used when the volume timing is critical for interpretation of
-    the data, such as in
-    [ASL](SPEC_ROOT/04-modality-specific-files/01-magnetic-resonance-imaging-data.md#\
-    arterial-spin-labeling-perfusion-data)
-    or variable flip angle fMRI sequences.
-  anyOf:
-  - type: number
-    unit: degree
-    exclusiveMinimum: 0
-    maximum: 360
-  - type: array
-    items:
-      type: number
-      unit: degree
-      exclusiveMinimum: 0
-      maximum: 360
-FrameDuration:
-  name: FrameDuration
-  display_name: Frame Duration
-  description: |
-    Time duration of each frame in default unit seconds.
-    This corresponds to DICOM Tag 0018, 1242 `Actual Frame Duration` converted
-    to seconds.
-  type: array
-  items:
-    type: number
-  unit: s
-FrameTimesStart:
-  name: FrameTimesStart
-  display_name: Frame Times Start
-  description: |
-    Start times for all frames relative to `"TimeZero"` in default unit seconds.
-  type: array
-  items:
-    type: number
-  unit: s
-Funding:
-  name: Funding
-  display_name: Funding
-  description: |
-    List of sources of funding (grant numbers).
-  type: array
-  items:
-    type: string
-GeneratedBy:
-  name: GeneratedBy
-  display_name: Generated By
-  description: |
-    Used to specify provenance of the dataset.
-  type: array
-  minItems: 1
-  items:
-    type: object
-    properties:
-      Name:
-        type: string
-      Version:
-        type: string
-      Description:
-        type: string
-      CodeURL:
-        type: string
-        format: uri
-      Container:
-        type: object
-        properties:
-          Type:
-            type: string
-          Tag:
-            type: string
-          URI:
-            type: string
-            format: uri
-GeneticLevel:
-  name: GeneticLevel
-  display_name: Genetic Level
-  description: |
-    Describes the level of analysis.
-    Values MUST be one of `"Genetic"`, `"Genomic"`, `"Epigenomic"`,
-    `"Transcriptomic"`, `"Metabolomic"`, or `"Proteomic"`.
-  anyOf:
-  - $ref: _GeneticLevelEnum
-  - type: array
-    items:
-      $ref: _GeneticLevelEnum
-Genetics:
-  name: Genetics
-  display_name: Genetics
-  description: |
-    An object containing information about the genetics descriptor.
-  type: object
-  properties:
-    Database:
-      name: Database
-      description: |
-        [URI](SPEC_ROOT/02-common-principles.md#uniform-resource-indicator)
-        of database where the dataset is hosted.
-      type: string
-      format: uri
-    Dataset:
-      name: Dataset
-      description: |
-        [URI](SPEC_ROOT/02-common-principles.md#uniform-resource-indicator)
-        where data can be retrieved.
-      type: string
-      format: uri
-    Descriptors:
-      name: Descriptors
-      description: |
-        List of relevant descriptors (for example, journal articles) for dataset
-        using a valid
-        [URI](SPEC_ROOT/02-common-principles.md#uniform-resource-indicator)
-        when possible.
-      anyOf:
-      - type: string
-      - type: array
-        items:
-          type: string
-GradientSetType:
-  name: GradientSetType
-  display_name: Gradient Set Type
-  description: |
-    It should be possible to infer the gradient coil from the scanner model.
-    If not, for example because of a custom upgrade or use of a gradient
-    insert set, then the specifications of the actual gradient coil should be
-    reported independently.
-  type: string
-HED:
-  name: HED
-  display_name: HED
-  description: |
-    Hierarchical Event Descriptor (HED) information,
-    see: [Appendix III](SPEC_ROOT/99-appendices/03-hed.md) for details.
-  anyOf:
-  - type: string
-  - type: object
-    additionalProperties:
-      type: string
-HEDVersion:
-  name: HEDVersion
-  display_name: HED Version
-  description: |
-    If HED tags are used:
-    The version of the HED schema used to validate HED tags for study.
-  type: string
-Haematocrit:
-  name: Haematocrit
-  display_name: Haematocrit
-  description: |
-    Measured haematocrit, meaning the volume of erythrocytes divided by the
-    volume of whole blood.
-  type: number
-HardcopyDeviceSoftwareVersion:
-  name: HardcopyDeviceSoftwareVersion
-  display_name: Hardcopy Device Software Version
-  description: |
-    Manufacturer's designation of the software of the device that created this
-    Hardcopy Image (the printer).
-    Corresponds to DICOM Tag 0018, 101A `Hardcopy Device Software Version`.
-  type: string
-HardwareFilters:
-  name: HardwareFilters
-  display_name: Hardware Filters
-  description: |
-    Object of temporal hardware filters applied, or `"n/a"` if the data is not
-    available. Each key-value pair in the JSON object is a name of the filter and
-    an object in which its parameters are defined as key-value pairs.
-    For example, `{"Highpass RC filter": {"Half amplitude cutoff (Hz)":
-    0.0159, "Roll-off": "6dB/Octave"}}`.
-  anyOf:
-  - type: object
-    additionalProperties:
-      type: object
-  - type: string
-    enum:
-    - n/a
-HeadCircumference:
-  name: HeadCircumference
-  display_name: Head Circumference
-  description: |
-    Circumference of the participant's head, expressed in cm (for example, `58`).
-  type: number
-  exclusiveMinimum: 0
-  unit: cm
-HeadCoilCoordinateSystem:
-  name: HeadCoilCoordinateSystem
-  display_name: Head Coil Coordinate System
-  description: |
-    Defines the coordinate system for the head coils.
-    See
-    [Appendix VIII](SPEC_ROOT/99-appendices/08-coordinate-systems.md)
-    for a list of restricted keywords for coordinate systems.
-    If `"Other"`, provide definition of the coordinate system in
-    `HeadCoilCoordinateSystemDescription`.
-  anyOf:
-  - $ref: _MEGCoordSys
-  - $ref: _EEGCoordSys
-  - $ref: _StandardTemplateCoordSys
-  - $ref: _StandardTemplateDeprecatedCoordSys
-HeadCoilCoordinateSystemDescription:
-  name: HeadCoilCoordinateSystemDescription
-  display_name: Head Coil Coordinate System Description
-  description: |
-    Free-form text description of the coordinate system.
-    May also include a link to a documentation page or paper describing the system in greater detail.
-  type: string
-HeadCoilCoordinateUnits:
-  name: HeadCoilCoordinateUnits
-  display_name: Head Coil Coordinate Units
-  description: |
-    Units of the coordinates of `HeadCoilCoordinateSystem`.
-  type: string
-  enum:
-  - m
-  - mm
-  - cm
-  - n/a
-HeadCoilCoordinates:
-  name: HeadCoilCoordinates
-  display_name: Head Coil Coordinates
-  description: |
-    Key-value pairs describing head localization coil labels and their
-    coordinates, interpreted following the `HeadCoilCoordinateSystem`
-    (for example, `{"NAS": [12.7,21.3,13.9], "LPA": [5.2,11.3,9.6],
-    "RPA": [20.2,11.3,9.1]}`).
-    Note that coils are not always placed at locations that have a known
-    anatomical name (for example, for Elekta, Yokogawa systems); in that case
-    generic labels can be used
-    (for example, `{"coil1": [12.2,21.3,12.3], "coil2": [6.7,12.3,8.6],
-    "coil3": [21.9,11.0,8.1]}`).
-    Each array MUST contain three numeric values corresponding to x, y, and z
-    axis of the coordinate system in that exact order.
-  type: object
-  additionalProperties:
-    type: array
-    items:
-      type: number
-    minItems: 3
-    maxItems: 3
-HeadCoilFrequency:
-  name: HeadCoilFrequency
-  display_name: Head Coil Frequency
-  description: |
-    List of frequencies (in Hz) used by the head localisation coils
-    ('HLC' in CTF systems, 'HPI' in Elekta, 'COH' in BTi/4D)
-    that track the subject's head position in the MEG helmet
-    (for example, `[293, 307, 314, 321]`).
-  anyOf:
-  - type: number
-    unit: Hz
-  - type: array
-    items:
-      type: number
-      unit: Hz
-HowToAcknowledge:
-  name: HowToAcknowledge
-  display_name: How To Acknowledge
-  description: |
-    Text containing instructions on how researchers using this dataset should
-    acknowledge the original authors.
-    This field can also be used to define a publication that should be cited in
-    publications that use the dataset.
-  type: string
-ImageAcquisitionProtocol:
-  name: ImageAcquisitionProtocol
-  display_name: Image Acquisition Protocol
-  description: |
-    Description of the image acquisition protocol or
-    [URI](SPEC_ROOT/02-common-principles.md#uniform-resource-indicator)
-    (for example from [protocols.io](https://www.protocols.io/)).
-  type: string
-ImageDecayCorrected:
-  name: ImageDecayCorrected
-  display_name: Image Decay Corrected
-  description: |
-    Boolean flag specifying whether the image data have been decay-corrected.
-  type: boolean
-ImageDecayCorrectionTime:
-  name: ImageDecayCorrectionTime
-  display_name: Image Decay Correction Time
-  description: |
-    Point in time from which the decay correction was applied with respect to
-    `"TimeZero"` in the default unit seconds.
-  type: number
-  unit: s
-Immersion:
-  name: Immersion
-  display_name: Immersion
-  description: |
-    Lens immersion medium. If the file format is OME-TIFF, the value MUST be consistent
-    with the `Immersion` OME metadata field.
-  type: string
-InfusionRadioactivity:
-  name: InfusionRadioactivity
-  display_name: Infusion Radioactivity
-  description: |
-    Amount of radioactivity infused into the patient.
-    This value must be less than or equal to the total injected radioactivity
-    (`"InjectedRadioactivity"`).
-    Units should be the same as `"InjectedRadioactivityUnits"`.
-  type: number
-InfusionSpeed:
-  name: InfusionSpeed
-  display_name: Infusion Speed
-  description: |
-    If given, infusion speed.
-  type: number
-InfusionSpeedUnits:
-  name: InfusionSpeedUnits
-  display_name: Infusion Speed Units
-  description: |
-    Unit of infusion speed (for example, `"mL/s"`).
-  type: string
-  format: unit
-InfusionStart:
-  name: InfusionStart
-  display_name: Infusion Start
-  description: |
-    Time of start of infusion with respect to `"TimeZero"` in the default unit
-    seconds.
-  type: number
-  unit: s
-InjectedMass:
-  name: InjectedMass
-  display_name: Injected Mass
-  description: |
-    Total mass of radiolabeled compound injected into subject (for example, `10`).
-    This can be derived as the ratio of the `"InjectedRadioactivity"` and
-    `"MolarRadioactivity"`.
-    **For those tracers in which injected mass is not available (for example FDG)
-    can be set to `"n/a"`)**.
-  anyOf:
-  - type: number
-  - type: string
-    enum:
-    - n/a
-InjectedMassPerWeight:
-  name: InjectedMassPerWeight
-  display_name: Injected Mass Per Weight
-  description: |
-    Injected mass per kilogram bodyweight.
-  type: number
-InjectedMassPerWeightUnits:
-  name: InjectedMassPerWeightUnits
-  display_name: Injected Mass Per Weight Units
-  description: |
-    Unit format of the injected mass per kilogram bodyweight
-    (for example, `"ug/kg"`).
-  type: string
-  format: unit
-InjectedMassUnits:
-  name: InjectedMassUnits
-  display_name: Injected Mass Units
-  description: |
-    Unit format of the mass of compound injected (for example, `"ug"` or
-    `"umol"`).
-    **Note this is not required for an FDG acquisition, since it is not available,
-    and SHOULD be set to `"n/a"`**.
-  anyOf:
-  - type: string
-    format: unit
-  - type: string
-    enum:
-    - n/a
-InjectedRadioactivity:
-  name: InjectedRadioactivity
-  display_name: Injected Radioactivity
-  description: |
-    Total amount of radioactivity injected into the patient (for example, `400`).
-    For bolus-infusion experiments, this value should be the sum of all injected
-    radioactivity originating from both bolus and infusion.
-    Corresponds to DICOM Tag 0018, 1074 `Radionuclide Total Dose`.
-  type: number
-InjectedRadioactivityUnits:
-  name: InjectedRadioactivityUnits
-  display_name: Injected Radioactivity Units
-  description: |
-    Unit format of the specified injected radioactivity (for example, `"MBq"`).
-  type: string
-  format: unit
-InjectedVolume:
-  name: InjectedVolume
-  display_name: Injected Volume
-  description: |
-    Injected volume of the radiotracer in the unit `"mL"`.
-  type: number
-  unit: mL
-InjectionEnd:
-  name: InjectionEnd
-  display_name: Injection End
-  description: |
-    Time of end of injection with respect to `"TimeZero"` in the default unit
-    seconds.
-  type: number
-  unit: s
-InjectionStart:
-  name: InjectionStart
-  display_name: Injection Start
-  description: |
-    Time of start of injection with respect to `"TimeZero"` in the default unit
-    seconds.
-    This corresponds to DICOM Tag 0018, 1072 `Contrast/Bolus Start Time`
-    converted to seconds relative to `"TimeZero"`.
-  type: number
-  unit: s
-InstitutionAddress:
-  name: InstitutionAddress
-  display_name: Institution Address
-  description: |
-    The address of the institution in charge of the equipment that produced the
-    measurements.
-  type: string
-InstitutionName:
-  name: InstitutionName
-  display_name: Institution Name
-  description: |
-    The name of the institution in charge of the equipment that produced the
-    measurements.
-  type: string
-InstitutionalDepartmentName:
-  name: InstitutionalDepartmentName
-  display_name: Institutional Department Name
-  description: |
-    The department in the institution in charge of the equipment that produced
-    the measurements.
-  type: string
-Instructions:
-  name: Instructions
-  display_name: Instructions
-  description: |
-    Text of the instructions given to participants before the recording.
-  type: string
-IntendedFor:
-  name: IntendedFor
-  display_name: Intended For
-  description: |
-    The paths to files for which the associated file is intended to be used.
-    Contains one or more filenames with paths relative to the participant
-    subdirectory.
-    Paths need to use forward slashes instead of backward slashes,
-    regardless of operating system.
-  anyOf:
-  - type: string
-    format: participant_relative
-  - type: array
-    items:
-      type: string
-      format: participant_relative
-IntendedFor__ds_relative:
-  name: IntendedFor
-  display_name: Intended For
-  description: |
-    The paths to files for which the associated file is intended to be used.
-    Contains one or more filenames with paths relative to the dataset
-    root.
-    Paths need to use forward slashes instead of backward slashes,
-    regardless of operating system.
-  anyOf:
-  - type: string
-    format: dataset_relative
-  - type: array
-    items:
-      type: string
-      format: dataset_relative
-InversionTime:
-  name: InversionTime
-  display_name: Inversion Time
-  description: |
-    The inversion time (TI) for the acquisition, specified in seconds.
-    Inversion time is the time after the middle of inverting RF pulse to middle
-    of excitation pulse to detect the amount of longitudinal magnetization.
-    Corresponds to DICOM Tag 0018, 0082 `Inversion Time`
-    (please note that the DICOM term is in milliseconds not seconds).
-  type: number
-  unit: s
-  exclusiveMinimum: 0
-LabelingDistance:
-  name: LabelingDistance
-  display_name: Labeling Distance
-  description: |
-    Distance from the center of the imaging slab to the center of the labeling
-    plane (`(P)CASL`) or the leading edge of the labeling slab (`PASL`),
-    in millimeters.
-    If the labeling is performed inferior to the isocenter,
-    this number should be negative.
-    Based on DICOM macro C.8.13.5.14.
-  type: number
-  unit: mm
-LabelingDuration:
-  name: LabelingDuration
-  display_name: Labeling Duration
-  description: |
-    Total duration of the labeling pulse train, in seconds,
-    corresponding to the temporal width of the labeling bolus for
-    `"PCASL"` or `"CASL"`.
-    In case all control-label volumes (or deltam or CBF) have the same
-    `LabelingDuration`, a scalar must be specified.
-    In case the control-label volumes (or deltam or cbf) have a different
-    `"LabelingDuration"`, an array of numbers must be specified,
-    for which any `m0scan` in the timeseries has a `"LabelingDuration"` of zero.
-    In case an array of numbers is provided,
-    its length should be equal to the number of volumes specified in
-    `*_aslcontext.tsv`.
-    Corresponds to DICOM Tag 0018, 9258 `ASL Pulse Train Duration`.
-  anyOf:
-  - type: number
-    minimum: 0
-    unit: s
-  - type: array
-    items:
-      type: number
-      unit: s
-      minimum: 0
-LabelingEfficiency:
-  name: LabelingEfficiency
-  display_name: Labeling Efficiency
-  description: |
-    Labeling efficiency, specified as a number between zero and one,
-    only if obtained externally (for example phase-contrast based).
-  type: number
-  exclusiveMinimum: 0
-LabelingLocationDescription:
-  name: LabelingLocationDescription
-  display_name: Labeling Location Description
-  description: |
-    Description of the location of the labeling plane (`"CASL"` or `"PCASL"`) or
-    the labeling slab (`"PASL"`) that cannot be captured by fields
-    `LabelingOrientation` or `LabelingDistance`.
-    May include a link to an anonymized screenshot of the planning of the
-    labeling slab/plane with respect to the imaging slab or slices
-    `*_asllabeling.jpg`.
-    Based on DICOM macro C.8.13.5.14.
-  type: string
-LabelingOrientation:
-  name: LabelingOrientation
-  display_name: Labeling Orientation
-  description: |
-    Orientation of the labeling plane (`(P)CASL`) or slab (`PASL`).
-    The direction cosines of a normal vector perpendicular to the ASL labeling
-    slab or plane with respect to the patient.
-    Corresponds to DICOM Tag 0018, 9255 `ASL Slab Orientation`.
-  type: array
-  items:
-    type: number
-LabelingPulseAverageB1:
-  name: LabelingPulseAverageB1
-  display_name: Labeling Pulse Average B1
-  description: |
-    The average B1-field strength of the RF labeling pulses, in microteslas.
-    As an alternative, `"LabelingPulseFlipAngle"` can be provided.
-  type: number
-  exclusiveMinimum: 0
-  unit: uT
-LabelingPulseAverageGradient:
-  name: LabelingPulseAverageGradient
-  display_name: Labeling Pulse Average Gradient
-  description: |
-    The average labeling gradient, in milliteslas per meter.
-  type: number
-  exclusiveMinimum: 0
-  unit: mT/m
-LabelingPulseDuration:
-  name: LabelingPulseDuration
-  display_name: Labeling Pulse Duration
-  description: |
-    Duration of the individual labeling pulses, in milliseconds.
-  type: number
-  exclusiveMinimum: 0
-  unit: ms
-LabelingPulseFlipAngle:
-  name: LabelingPulseFlipAngle
-  display_name: Labeling Pulse Flip Angle
-  description: |
-    The flip angle of a single labeling pulse, in degrees,
-    which can be given as an alternative to `"LabelingPulseAverageB1"`.
-  type: number
-  exclusiveMinimum: 0
-  maximum: 360
-  unit: degree
-LabelingPulseInterval:
-  name: LabelingPulseInterval
-  display_name: Labeling Pulse Interval
-  description: |
-    Delay between the peaks of the individual labeling pulses, in milliseconds.
-  type: number
-  exclusiveMinimum: 0
-  unit: ms
-LabelingPulseMaximumGradient:
-  name: LabelingPulseMaximumGradient
-  display_name: Labeling Pulse Maximum Gradient
-  description: |
-    The maximum amplitude of the gradient switched on during the application of
-    the labeling RF pulse(s), in milliteslas per meter.
-  type: number
-  exclusiveMinimum: 0
-  unit: mT/m
-LabelingSlabThickness:
-  name: LabelingSlabThickness
-  display_name: Labeling Slab Thickness
-  description: |
-    Thickness of the labeling slab in millimeters.
-    For non-selective FAIR a zero is entered.
-    Corresponds to DICOM Tag 0018, 9254 `ASL Slab Thickness`.
-  type: number
-  exclusiveMinimum: 0
-  unit: mm
-Levels:
-  name: Levels
-  display_name: Levels
-  description: |
-    For categorical variables: An object of possible values (keys) and their
-    descriptions (values).
-  type: object
-  additionalProperties:
-    type: string
-License:
-  name: License
-  display_name: License
-  description: |
-    The license for the dataset.
-    The use of license name abbreviations is RECOMMENDED for specifying a license
-    (see [Appendix II](SPEC_ROOT/99-appendices/02-licenses.md)).
-    The corresponding full license text MAY be specified in an additional
-    `LICENSE` file.
-  type: string
-LongName:
-  name: LongName
-  display_name: Long Name
-  description: |
-    Long (unabbreviated) name of the column.
-  type: string
-LookLocker:
-  name: LookLocker
-  display_name: Look Locker
-  description: |
-    Boolean indicating if a Look-Locker readout is used.
-  type: boolean
-M0Estimate:
-  name: M0Estimate
-  display_name: M0Estimate
-  description: |
-    A single numerical whole-brain M0 value (referring to the M0 of blood),
-    only if obtained externally
-    (for example retrieved from CSF in a separate measurement).
-  type: number
-  exclusiveMinimum: 0
-M0Type:
-  name: M0Type
-  display_name: M0Type
-  description: |
-    Describes the presence of M0 information.
-    `"Separate"` means that a separate `*_m0scan.nii[.gz]` is present.
-    `"Included"` means that an m0scan volume is contained within the current
-    `*_asl.nii[.gz]`.
-    `"Estimate"` means that a single whole-brain M0 value is provided.
-    `"Absent"` means that no specific M0 information is present.
-  type: string
-  enum:
-  - Separate
-  - Included
-  - Estimate
-  - Absent
-MEGChannelCount:
-  name: MEGChannelCount
-  display_name: MEG Channel Count
-  description: |
-    Number of MEG channels (for example, `275`).
-  type: integer
-  minimum: 0
-MEGCoordinateSystem:
-  name: MEGCoordinateSystem
-  display_name: MEG Coordinate System
-  description: |
-    Defines the coordinate system for the MEG sensors.
-    See [Appendix VIII](SPEC_ROOT/99-appendices/08-coordinate-systems.md)
-    for a list of restricted keywords for coordinate systems.
-    If `"Other"`, provide definition of the coordinate system in
-    `"MEGCoordinateSystemDescription"`.
-  anyOf:
-  - $ref: _MEGCoordSys
-  - $ref: _EEGCoordSys
-  - $ref: _StandardTemplateCoordSys
-  - $ref: _StandardTemplateDeprecatedCoordSys
-MEGCoordinateSystemDescription:
-  name: MEGCoordinateSystemDescription
-  display_name: MEG Coordinate System Description
-  description: |
-    Free-form text description of the coordinate system.
-    May also include a link to a documentation page or paper describing the
-    system in greater detail.
-  type: string
-MEGCoordinateUnits:
-  name: MEGCoordinateUnits
-  display_name: MEG Coordinate Units
-  description: |
-    Units of the coordinates of `"MEGCoordinateSystem"`.
-  type: string
-  enum:
-  - m
-  - mm
-  - cm
-  - n/a
-MEGREFChannelCount:
-  name: MEGREFChannelCount
-  display_name: MEGREF Channel Count
-  description: |
-    Number of MEG reference channels (for example, `23`).
-    For systems without such channels (for example, Neuromag Vectorview),
-    `MEGREFChannelCount` should be set to `0`.
-  type: integer
-  minimum: 0
-MRAcquisitionType:
-  name: MRAcquisitionType
-  display_name: MR Acquisition Type
-  description: |
-    Type of sequence readout.
-    Corresponds to DICOM Tag 0018, 0023 `MR Acquisition Type`.
-  type: string
-  enum:
-  - 2D
-  - 3D
-MRTransmitCoilSequence:
-  name: MRTransmitCoilSequence
-  display_name: MR Transmit Coil Sequence
-  description: |
-    This is a relevant field if a non-standard transmit coil is used.
-    Corresponds to DICOM Tag 0018, 9049 `MR Transmit Coil Sequence`.
-  type: string
-MTNumberOfPulses:
-  name: MTNumberOfPulses
-  display_name: MT Number Of Pulses
-  description: |
-    The number of magnetization transfer RF pulses applied before the readout.
-  type: number
-MTOffsetFrequency:
-  name: MTOffsetFrequency
-  display_name: MT Offset Frequency
-  description: |
-    The frequency offset of the magnetization transfer pulse with respect to the
-    central H1 Larmor frequency in Hertz (Hz).
-  type: number
-  unit: Hz
-MTPulseBandwidth:
-  name: MTPulseBandwidth
-  display_name: MT Pulse Bandwidth
-  description: |
-    The excitation bandwidth of the magnetization transfer pulse in Hertz (Hz).
-  type: number
-  unit: Hz
-MTPulseDuration:
-  name: MTPulseDuration
-  display_name: MT Pulse Duration
-  description: |
-    Duration of the magnetization transfer RF pulse in seconds.
-  type: number
-  unit: s
-MTPulseShape:
-  name: MTPulseShape
-  display_name: MT Pulse Shape
-  description: |
-    Shape of the magnetization transfer RF pulse waveform.
-    The value `"GAUSSHANN"` refers to a Gaussian pulse with a Hanning window.
-    The value `"SINCHANN"` refers to a sinc pulse with a Hanning window.
-    The value `"SINCGAUSS"` refers to a sinc pulse with a Gaussian window.
-  type: string
-  enum:
-  - HARD
-  - GAUSSIAN
-  - GAUSSHANN
-  - SINC
-  - SINCHANN
-  - SINCGAUSS
-  - FERMI
-MTState:
-  name: MTState
-  display_name: MT State
-  description: |
-    Boolean stating whether the magnetization transfer pulse is applied.
-    Corresponds to DICOM Tag 0018, 9020 `Magnetization Transfer`.
-  type: boolean
-MagneticFieldStrength:
-  name: MagneticFieldStrength
-  display_name: Magnetic Field Strength
-  description: |
-    Nominal field strength of MR magnet in Tesla.
-    Corresponds to DICOM Tag 0018, 0087 `Magnetic Field Strength`.
-  type: number
-Magnification:
-  name: Magnification
-  display_name: Magnification
-  description: |
-    Lens magnification (for example: `40`). If the file format is OME-TIFF,
-    the value MUST be consistent with the `"NominalMagnification"` OME metadata field.
-  type: number
-  exclusiveMinimum: 0
-Manual:
-  name: Manual
-  display_name: Manual
-  description: |
-    Indicates if the segmentation was performed manually or via an automated
-    process.
-  type: boolean
-Manufacturer:
-  name: Manufacturer
-  display_name: Manufacturer
-  description: |
-    Manufacturer of the equipment that produced the measurements.
-  type: string
-ManufacturersModelName:
-  name: ManufacturersModelName
-  display_name: Manufacturers Model Name
-  description: |
-    Manufacturer's model name of the equipment that produced the measurements.
-  type: string
-MatrixCoilMode:
-  name: MatrixCoilMode
-  display_name: Matrix Coil Mode
-  description: |
-    (If used)
-    A method for reducing the number of independent channels by combining in
-    analog the signals from multiple coil elements.
-    There are typically different default modes when using un-accelerated or
-    accelerated (for example, `"GRAPPA"`, `"SENSE"`) imaging.
-  type: string
-MaxMovement:
-  name: MaxMovement
-  display_name: Max Movement
-  description: |
-    Maximum head movement (in mm) detected during the recording,
-    as measured by the head localisation coils (for example, `4.8`).
-  type: number
-  unit: mm
-MeasurementToolMetadata:
-  name: MeasurementToolMetadata
-  display_name: Measurement Tool Metadata
-  description: |
-    A description of the measurement tool as a whole.
-    Contains two fields: `"Description"` and `"TermURL"`.
-    `"Description"` is a free text description of the measurement tool.
-    `"TermURL"` is a URL to an entity in an ontology corresponding to this tool.
-  type: object
-  properties:
-    TermURL:
-      type: string
-      format: uri
-    Description:
-      type: string
-MetaboliteAvail:
-  name: MetaboliteAvail
-  display_name: Metabolite Available
-  description: |
-    Boolean that specifies if metabolite measurements are available.
-    If `true`, the `metabolite_parent_fraction` column MUST be present in the
-    corresponding `*_blood.tsv` file.
-  type: boolean
-MetaboliteMethod:
-  name: MetaboliteMethod
-  display_name: Metabolite Method
-  description: |
-    Method used to measure metabolites.
-  type: string
-MetaboliteRecoveryCorrectionApplied:
-  name: MetaboliteRecoveryCorrectionApplied
-  display_name: Metabolite Recovery Correction Applied
-  description: |
-    Metabolite recovery correction from the HPLC, for tracers where it changes
-    with time postinjection.
-    If `true`, the `hplc_recovery_fractions` column MUST be present in the
-    corresponding `*_blood.tsv` file.
-  type: boolean
-MiscChannelCount:
-  name: MiscChannelCount
-  display_name: Misc Channel Count
-  description: |
-    Number of miscellaneous analog channels for auxiliary signals.
-  type: integer
-  minimum: 0
-MixingTime:
-  name: MixingTime
-  display_name: Mixing Time
-  description: |
-    In the context of a stimulated- and spin-echo 3D EPI sequence for B1+ mapping,
-    corresponds to the interval between spin- and stimulated-echo pulses.
-    In the context of a diffusion-weighted double spin-echo sequence,
-    corresponds to the interval between two successive diffusion sensitizing
-    gradients, specified in seconds.
-  type: number
-  unit: s
-ModeOfAdministration:
-  name: ModeOfAdministration
-  display_name: Mode Of Administration
-  description: |
-    Mode of administration of the injection
-    (for example, `"bolus"`, `"infusion"`, or `"bolus-infusion"`).
-  type: string
-MolarActivity:
-  name: MolarActivity
-  display_name: Molar Activity
-  description: |
-    Molar activity of compound injected.
-    Corresponds to DICOM Tag 0018, 1077 `Radiopharmaceutical Specific Activity`.
-  type: number
-MolarActivityMeasTime:
-  name: MolarActivityMeasTime
-  display_name: Molar Activity Measurement Time
-  description: |
-    Time to which molar radioactivity measurement above applies in the default
-    unit `"hh:mm:ss"`.
-  type: string
-  format: time
-MolarActivityUnits:
-  name: MolarActivityUnits
-  display_name: Molar Activity Units
-  description: |
-    Unit of the specified molar radioactivity (for example, `"GBq/umol"`).
-  type: string
-  format: unit
-MultibandAccelerationFactor:
-  name: MultibandAccelerationFactor
-  display_name: Multiband Acceleration Factor
-  description: |
-    The multiband factor, for multiband acquisitions.
-  type: number
-MultipartID:
-  name: MultipartID
-  display_name: MultipartID
-  description: |
-    A unique (per participant) label tagging DWI runs that are part of a
-    multipart scan.
-  type: string
-Name:
-  name: Name
-  display_name: Name
-  description: |
-    Name of the dataset.
-  type: string
-NegativeContrast:
-  name: NegativeContrast
-  display_name: Negative Contrast
-  description: |
-    `true` or `false` value specifying whether increasing voxel intensity
-    (within sample voxels) denotes a decreased value with respect to the
-    contrast suffix.
-    This is commonly the case when Cerebral Blood Volume is estimated via
-    usage of a contrast agent in conjunction with a T2\* weighted acquisition
-    protocol.
-  type: boolean
-NonlinearGradientCorrection:
-  name: NonlinearGradientCorrection
-  display_name: Nonlinear Gradient Correction
-  description: |
-    Boolean stating if the image saved has been corrected for gradient
-    nonlinearities by the scanner sequence.
-  type: boolean
-NumberOfVolumesDiscardedByScanner:
-  name: NumberOfVolumesDiscardedByScanner
-  display_name: Number Of Volumes Discarded By Scanner
-  description: |
-    Number of volumes ("dummy scans") discarded by the scanner
-    (as opposed to those discarded by the user post hoc)
-    before saving the imaging file.
-    For example, a sequence that automatically discards the first 4 volumes
-    before saving would have this field as 4.
-    A sequence that does not discard dummy scans would have this set to 0.
-    Please note that the onsets recorded in the `events.tsv` file should always
-    refer to the beginning of the acquisition of the first volume in the
-    corresponding imaging file - independent of the value of
-    `"NumberOfVolumesDiscardedByScanner"` field.
-  type: integer
-  minimum: 0
-NumberOfVolumesDiscardedByUser:
-  name: NumberOfVolumesDiscardedByUser
-  display_name: Number Of Volumes Discarded By User
-  description: |
-    Number of volumes ("dummy scans") discarded by the user before including the
-    file in the dataset.
-    If possible, including all of the volumes is strongly recommended.
-    Please note that the onsets recorded in the `events.tsv` file should always
-    refer to the beginning of the acquisition of the first volume in the
-    corresponding imaging file - independent of the value of
-    `"NumberOfVolumesDiscardedByUser"` field.
-  type: integer
-  minimum: 0
-NumberShots:
-  name: NumberShots
-  display_name: Number Shots
-  description: |
-    The number of RF excitations needed to reconstruct a slice or volume
-    (may be referred to as partition).
-    Please mind that this is not the same as Echo Train Length which denotes the
-    number of k-space lines collected after excitation in a multi-echo readout.
-    The data type array is applicable for specifying this parameter before and
-    after the k-space center is sampled.
-    Please see
-    [`"NumberShots"` metadata field]\
-    (/99-appendices/11-qmri.html#numbershots-metadata-field)
-    in the qMRI appendix for corresponding calculations.
-  anyOf:
-  - type: number
-  - type: array
-    items:
-      type: number
-NumericalAperture:
-  name: NumericalAperture
-  display_name: Numerical Aperture
-  description: |
-    Lens numerical aperture (for example: `1.4`). If the file format is OME-TIFF,
-    the value MUST be consistent with the `LensNA` OME metadata field.
-  type: number
-  exclusiveMinimum: 0
-OperatingSystem:
-  name: OperatingSystem
-  display_name: Operating System
-  description: |
-    Operating system used to run the stimuli presentation software
-    (for formatting recommendations, see examples below this table).
-  type: string
-OtherAcquisitionParameters:
-  name: OtherAcquisitionParameters
-  display_name: Other Acquisition Parameters
-  description: |
-    Description of other relevant image acquisition parameters.
-  type: string
-PASLType:
-  name: PASLType
-  display_name: PASL Type
-  description: |
-    Type of the labeling pulse of the `PASL` labeling,
-    for example `"FAIR"`, `"EPISTAR"`, or `"PICORE"`.
-  type: string
-PCASLType:
-  name: PCASLType
-  display_name: PCASL Type
-  description: |
-    The type of gradient pulses used in the `control` condition.
-  type: string
-  enum:
-  - balanced
-  - unbalanced
-ParallelAcquisitionTechnique:
-  name: ParallelAcquisitionTechnique
-  display_name: Parallel Acquisition Technique
-  description: |
-    The type of parallel imaging used (for example `"GRAPPA"`, `"SENSE"`).
-    Corresponds to DICOM Tag 0018, 9078 `Parallel Acquisition Technique`.
-  type: string
-ParallelReductionFactorInPlane:
-  name: ParallelReductionFactorInPlane
-  display_name: Parallel Reduction Factor In Plane
-  description: |
-    The parallel imaging (for instance, GRAPPA) factor.
-    Use the denominator of the fraction of k-space encoded for each slice.
-    For example, 2 means half of k-space is encoded.
-    Corresponds to DICOM Tag 0018, 9069 `Parallel Reduction Factor In-plane`.
-  type: number
-PartialFourier:
-  name: PartialFourier
-  display_name: Partial Fourier
-  description: |
-    The fraction of partial Fourier information collected.
-    Corresponds to DICOM Tag 0018, 9081 `Partial Fourier`.
-  type: number
-PartialFourierDirection:
-  name: PartialFourierDirection
-  display_name: Partial Fourier Direction
-  description: |
-    The direction where only partial Fourier information was collected.
-    Corresponds to DICOM Tag 0018, 9036 `Partial Fourier Direction`.
-  type: string
-PharmaceuticalDoseAmount:
-  name: PharmaceuticalDoseAmount
-  display_name: Pharmaceutical Dose Amount
-  description: |
-    Dose amount of pharmaceutical coadministered with tracer.
-  anyOf:
-  - type: number
-  - type: array
-    items:
-      type: number
-PharmaceuticalDoseRegimen:
-  name: PharmaceuticalDoseRegimen
-  display_name: Pharmaceutical Dose Regimen
-  description: |
-    Details of the pharmaceutical dose regimen.
-    Either adequate description or short-code relating to regimen documented
-    elsewhere (for example, `"single oral bolus"`).
-  type: string
-PharmaceuticalDoseTime:
-  name: PharmaceuticalDoseTime
-  display_name: Pharmaceutical Dose Time
-  description: |
-    Time of administration of pharmaceutical dose, relative to time zero.
-    For an infusion, this should be a vector with two elements specifying the
-    start and end of the infusion period. For more complex dose regimens,
-    the regimen description should be complete enough to enable unambiguous
-    interpretation of `"PharmaceuticalDoseTime"`.
-    Unit format of the specified pharmaceutical dose time MUST be seconds.
-  anyOf:
-  - type: number
-    unit: s
-  - type: array
-    items:
-      type: number
-      unit: s
-PharmaceuticalDoseUnits:
-  name: PharmaceuticalDoseUnits
-  display_name: Pharmaceutical Dose Units
-  description: |
-    Unit format relating to pharmaceutical dose
-    (for example, `"mg"` or `"mg/kg"`).
-  type: string
-  format: unit
-PharmaceuticalName:
-  name: PharmaceuticalName
-  display_name: Pharmaceutical Name
-  description: |
-    Name of pharmaceutical coadministered with tracer.
-  type: string
-PhaseEncodingDirection:
-  name: PhaseEncodingDirection
-  display_name: Phase Encoding Direction
-  description: |
-    The letters `i`, `j`, `k` correspond to the first, second and third axis of
-    the data in the NIFTI file.
-    The polarity of the phase encoding is assumed to go from zero index to
-    maximum index unless `-` sign is present
-    (then the order is reversed - starting from the highest index instead of
-    zero).
-    `PhaseEncodingDirection` is defined as the direction along which phase is was
-    modulated which may result in visible distortions.
-    Note that this is not the same as the DICOM term
-    `InPlanePhaseEncodingDirection` which can have `ROW` or `COL` values.
-  type: string
-  enum:
-  - i
-  - j
-  - k
-  - i-
-  - j-
-  - k-
-PixelSize:
-  name: PixelSize
-  display_name: Pixel Size
-  description: |
-    A 2- or 3-number array of the physical size of a pixel, either `[PixelSizeX, PixelSizeY]`
-    or `[PixelSizeX, PixelSizeY, PixelSizeZ]`, where X is the width, Y the height and Z the
-    depth.
-    If the file format is OME-TIFF, these values need to be consistent with `PhysicalSizeX`,
-    `PhysicalSizeY` and `PhysicalSizeZ` OME metadata fields, after converting in
-    `PixelSizeUnits` according to `PhysicalSizeXunit`, `PhysicalSizeYunit` and
-    `PhysicalSizeZunit` OME fields.
-  type: array
-  minItems: 2
-  maxItems: 3
-  items:
-    type: number
-    minimum: 0
-PixelSizeUnits:
-  name: PixelSizeUnits
-  display_name: Pixel Size Units
-  description: |
-    Unit format of the specified `"PixelSize"`. MUST be one of: `"mm"` (millimeter), `"um"`
-    (micrometer) or `"nm"` (nanometer).
-  type: string
-  enum:
-  - mm
-  - um
-  - nm
-PlasmaAvail:
-  name: PlasmaAvail
-  display_name: Plasma Avail
-  description: |
-    Boolean that specifies if plasma measurements are available.
-  type: boolean
-PlasmaFreeFraction:
-  name: PlasmaFreeFraction
-  display_name: Plasma Free Fraction
-  description: |
-    Measured free fraction in plasma, meaning the concentration of free compound
-    in plasma divided by total concentration of compound in plasma
-    (Units: 0-100%).
-  type: number
-  minimum: 0
-  maximum: 100
-PlasmaFreeFractionMethod:
-  name: PlasmaFreeFractionMethod
-  display_name: Plasma Free Fraction Method
-  description: |
-    Method used to estimate free fraction.
-  type: string
-PostLabelingDelay:
-  name: PostLabelingDelay
-  display_name: Post Labeling Delay
-  description: |
-    This is the postlabeling delay (PLD) time, in seconds, after the end of the
-    labeling (for `"CASL"` or `"PCASL"`) or middle of the labeling pulse
-    (for `"PASL"`) until the middle of the excitation pulse applied to the
-    imaging slab (for 3D acquisition) or first slice (for 2D acquisition).
-    Can be a number (for a single-PLD time series) or an array of numbers
-    (for multi-PLD and Look-Locker).
-    In the latter case, the array of numbers contains the PLD of each volume,
-    namely each `control` and `label`, in the acquisition order.
-    Any image within the time-series without a PLD, for example an `m0scan`,
-    is indicated by a zero.
-    Based on DICOM Tags 0018, 9079 `Inversion Times` and 0018, 0082
-    `InversionTime`.
-  anyOf:
-  - type: number
-    exclusiveMinimum: 0
-    unit: s
-  - type: array
-    items:
-      type: number
-      exclusiveMinimum: 0
-      unit: s
-PowerLineFrequency:
-  name: PowerLineFrequency
-  display_name: Power Line Frequency
-  description: |
-    Frequency (in Hz) of the power grid at the geographical location of the
-    instrument (for example, `50` or `60`).
-  anyOf:
-  - type: number
-    exclusiveMinimum: 0
-    unit: Hz
-  - type: string
-    enum:
-    - n/a
-PromptRate:
-  name: PromptRate
-  display_name: Prompt Rate
-  description: |
-    Prompt rate for each frame (same units as `Units`, for example, `"Bq/mL"`).
-  type: array
-  items:
-    type: number
-PulseSequenceDetails:
-  name: PulseSequenceDetails
-  display_name: Pulse Sequence Details
-  description: |
-    Information beyond pulse sequence type that identifies the specific pulse
-    sequence used (for example,
-    `"Standard Siemens Sequence distributed with the VB17 software"`,
-    `"Siemens WIP ### version #.##,"` or
-    `"Sequence written by X using a version compiled on MM/DD/YYYY"`).
-  type: string
-PulseSequenceType:
-  name: PulseSequenceType
-  display_name: Pulse Sequence Type
-  description: |
-    A general description of the pulse sequence used for the scan
-    (for example, `"MPRAGE"`, `"Gradient Echo EPI"`, `"Spin Echo EPI"`,
-    `"Multiband gradient echo EPI"`).
-  type: string
-Purity:
-  name: Purity
-  display_name: Purity
-  description: |
-    Purity of the radiolabeled compound (between 0 and 100%).
-  type: number
-  minimum: 0
-  maximum: 100
-RandomRate:
-  name: RandomRate
-  display_name: Random Rate
-  description: |
-    Random rate for each frame (same units as `"Units"`, for example, `"Bq/mL"`).
-  type: array
-  items:
-    type: number
-RawSources:
-  name: RawSources
-  display_name: Raw Sources
-  description: |
-    A list of paths relative to dataset root pointing to the BIDS-Raw file(s)
-    that were used in the creation of this derivative.
-  type: array
-  items:
-    type: string
-    format: dataset_relative
-ReceiveCoilActiveElements:
-  name: ReceiveCoilActiveElements
-  display_name: Receive Coil Active Elements
-  description: |
-    Information describing the active/selected elements of the receiver coil.
-    This does not correspond to a tag in the DICOM ontology.
-    The vendor-defined terminology for active coil elements can go in this field.
-  type: string
-ReceiveCoilName:
-  name: ReceiveCoilName
-  display_name: Receive Coil Name
-  description: |
-    Information describing the receiver coil.
-    Corresponds to DICOM Tag 0018, 1250 `Receive Coil Name`,
-    although not all vendors populate that DICOM Tag,
-    in which case this field can be derived from an appropriate
-    private DICOM field.
-  type: string
-ReconFilterSize:
-  name: ReconFilterSize
-  display_name: Recon Filter Size
-  description: |
-    Kernel size of post-recon filter (FWHM) in default units `"mm"`.
-  anyOf:
-  - type: number
-    unit: mm
-  - type: array
-    items:
-      type: number
-      unit: mm
-ReconFilterType:
-  name: ReconFilterType
-  display_name: Recon Filter Type
-  description: |
-    Type of post-recon smoothing (for example, `["Shepp"]`).
-  anyOf:
-  - type: string
-  - type: array
-    items:
-      type: string
-ReconMethodImplementationVersion:
-  name: ReconMethodImplementationVersion
-  display_name: Recon Method Implementation Version
-  description: |
-    Identification for the software used, such as name and version.
-  type: string
-ReconMethodName:
-  name: ReconMethodName
-  display_name: Recon Method Name
-  description: |
-    Reconstruction method or algorithm (for example, `"3d-op-osem"`).
-  type: string
-ReconMethodParameterLabels:
-  name: ReconMethodParameterLabels
-  display_name: Recon Method Parameter Labels
-  description: |
-    Names of reconstruction parameters (for example, `["subsets", "iterations"]`).
-  type: array
-  items:
-    type: string
-ReconMethodParameterUnits:
-  name: ReconMethodParameterUnits
-  display_name: Recon Method Parameter Units
-  description: |
-    Unit of reconstruction parameters (for example, `["none", "none"]`).
-  type: array
-  items:
-    type: string
-    format: unit
-ReconMethodParameterValues:
-  name: ReconMethodParameterValues
-  display_name: Recon Method Parameter Values
-  description: |
-    Values of reconstruction parameters (for example, `[21, 3]`).
-  type: array
-  items:
-    type: number
-RecordingDuration:
-  name: RecordingDuration
-  display_name: Recording Duration
-  description: |
-    Length of the recording in seconds (for example, `3600`).
-  type: number
-  unit: s
-RecordingType:
-  name: RecordingType
-  display_name: Recording Type
-  description: |
-    Defines whether the recording is `"continuous"`, `"discontinuous"`, or
-    `"epoched"`, where `"epoched"` is limited to time windows about events of
-    interest (for example, stimulus presentations or subject responses).
-  type: string
-  enum:
-  - continuous
-  - epoched
-  - discontinuous
-ReferencesAndLinks:
-  name: ReferencesAndLinks
-  display_name: References And Links
-  description: |
-    List of references to publications that contain information on the dataset.
-    A reference may be textual or a
-    [URI](SPEC_ROOT/02-common-principles.md#uniform-resource-indicator).
-  items:
-    type: string
-  type: array
-RepetitionTime:
-  name: RepetitionTime
-  display_name: Repetition Time
-  description: |
-    The time in seconds between the beginning of an acquisition of one volume
-    and the beginning of acquisition of the volume following it (TR).
-    When used in the context of functional acquisitions this parameter best
-    corresponds to
-    [DICOM Tag 0020, 0110](http://dicomlookup.com/lookup.asp?sw=Tnumber&q=(0020,0110)):
-    the "time delta between images in a
-    dynamic of functional set of images" but may also be found in
-    [DICOM Tag 0018, 0080](http://dicomlookup.com/lookup.asp?sw=Tnumber&q=(0018,0080)):
-    "the period of time in msec between the beginning
-    of a pulse sequence and the beginning of the succeeding
-    (essentially identical) pulse sequence".
-    This definition includes time between scans (when no data has been acquired)
-    in case of sparse acquisition schemes.
-    This value MUST be consistent with the 'pixdim[4]' field (after accounting
-    for units stored in 'xyzt_units' field) in the NIfTI header.
-    This field is mutually exclusive with VolumeTiming.
-  type: number
-  exclusiveMinimum: 0
-  unit: s
-RepetitionTimeExcitation:
-  name: RepetitionTimeExcitation
-  display_name: Repetition Time Excitation
-  description: |
-    The interval, in seconds, between two successive excitations.
-    [DICOM Tag 0018, 0080](http://dicomlookup.com/lookup.asp?sw=Tnumber&q=(0018,0080)
-    best refers to this parameter.
-    This field may be used together with the `"RepetitionTimePreparation"` for
-    certain use cases, such as
-    [MP2RAGE](https://doi.org/10.1016/j.neuroimage.2009.10.002).
-    Use `RepetitionTimeExcitation` (in combination with
-    `"RepetitionTimePreparation"` if needed) for anatomy imaging data rather than
-    `"RepetitionTime"` as it is already defined as the amount of time that it takes
-    to acquire a single volume in the
-    [task imaging data](/04-modality-specific-files/01-magnetic-resonance-\
-    imaging-data.html#task-including-resting-state-imaging-data)
-    section.
-  type: number
-  minimum: 0
-  unit: s
-RepetitionTimePreparation:
-  name: RepetitionTimePreparation
-  display_name: Repetition Time Preparation
-  description: |
-    The interval, in seconds, that it takes a preparation pulse block to
-    re-appear at the beginning of the succeeding (essentially identical) pulse
-    sequence block.
-    The data type number may apply to files from any MRI modality concerned with
-    a single value for this field.
-    The data type array provides a value for each volume in a 4D dataset and
-    should only be used when the volume timing is critical for interpretation of
-    the data, such as in
-    [ASL](SPEC_ROOT/04-modality-specific-files/01-magnetic-resonance-imaging-data.md\
-    #arterial-spin-labeling-perfusion-data).
-  anyOf:
-  - type: number
-    minimum: 0
-    unit: s
-  - type: array
-    items:
-      type: number
-      minimum: 0
-      unit: s
-Resolution:
-  name: Resolution
-  display_name: Resolution
-  description: |
-    Specifies the interpretation of the resolution keyword.
-    If an object is used, then the keys should be values for the `res` entity
-    and values should be descriptions of those `res` values.
-  anyOf:
-  - type: string
-  - type: object
-    additionalProperties:
-      type: string
-SEEGChannelCount:
-  name: SEEGChannelCount
-  display_name: SEEG Channel Count
-  description: |
-    Number of SEEG channels.
-  type: integer
-  minimum: 0
-SampleEmbedding:
-  name: SampleEmbedding
-  display_name: Sample Embedding
-  description: |
-    Description of the tissue sample embedding (for example: `"Epoxy resin"`).
-  type: string
-SampleEnvironment:
-  name: SampleEnvironment
-  display_name: Sample Environment
-  description: |
-    Environment in which the sample was imaged. MUST be one of: `"in vivo"`, `"ex vivo"`
-    or `"in vitro"`.
-  type: string
-  enum:
-  - in vivo
-  - ex vivo
-  - in vitro
-SampleExtractionInstitution:
-  name: SampleExtractionInstitution
-  display_name: Sample Extraction Institution
-  description: |
-    The name of the institution in charge of the extraction of the sample,
-    if different from the institution in charge of the equipment that produced the image.
-  type: string
-SampleExtractionProtocol:
-  name: SampleExtractionProtocol
-  display_name: Sample Extraction Protocol
-  description: |
-    Description of the sample extraction protocol or
-    [URI](SPEC_ROOT/02-common-principles.md#uniform-resource-indicator)
-    (for example from [protocols.io](https://www.protocols.io/)).
-  type: string
-SampleFixation:
-  name: SampleFixation
-  display_name: Sample Fixation
-  description: |
-    Description of the tissue sample fixation
-    (for example: `"4% paraformaldehyde, 2% glutaraldehyde"`).
-  type: string
-SampleOrigin:
-  name: SampleOrigin
-  display_name: Sample Origin
-  description: |
-    Describes from which tissue the genetic information was extracted.
-  type: string
-  enum:
-  - blood
-  - saliva
-  - brain
-  - csf
-  - breast milk
-  - bile
-  - amniotic fluid
-  - other biospecimen
-SamplePrimaryAntibody:
-  name: SamplePrimaryAntibody
-  display_name: Sample Primary Antibody
-  description: |
-    Description(s) of the primary antibody used for immunostaining.
-    Either an [RRID](https://scicrunch.org/resources) or the name, supplier and catalogue
-    number of a commercial antibody.
-    For non-commercial antibodies either an [RRID](https://scicrunch.org/resources) or the
-    host-animal and immunogen used (for examples: `"RRID:AB_2122563"` or
-    `"Rabbit anti-Human HTR5A Polyclonal Antibody, Invitrogen, Catalog # PA1-2453"`).
-    MAY be an array of strings if different antibodies are used in each channel of the file.
-  anyOf:
-  - type: string
-  - type: array
-    items:
-      type: string
-SampleSecondaryAntibody:
-  name: SampleSecondaryAntibody
-  display_name: Sample Secondary Antibody
-  description: |
-    Description(s) of the secondary antibody used for immunostaining.
-    Either an [RRID](https://scicrunch.org/resources) or the name, supplier and catalogue
-    number of a commercial antibody.
-    For non-commercial antibodies either an [RRID](https://scicrunch.org/resources) or the
-    host-animal and immunogen used (for examples: `"RRID:AB_228322"` or
-    `"Goat anti-Mouse IgM Secondary Antibody, Invitrogen, Catalog # 31172"`).
-    MAY be an array of strings if different antibodies are used in each channel of the file.
-  anyOf:
-  - type: string
-  - type: array
-    items:
-      type: string
-SampleStaining:
-  name: SampleStaining
-  display_name: Sample Staining
-  description: |
-    Description(s) of the tissue sample staining (for example: `"Osmium"`).
-    MAY be an array of strings if different stains are used in each channel of the file
-    (for example: `["LFB", "PLP"]`).
-  anyOf:
-  - type: string
-  - type: array
-    items:
-      type: string
-SamplingFrequency:
-  name: SamplingFrequency
-  display_name: Sampling Frequency
-  description: |
-    Sampling frequency (in Hz) of all the data in the recording,
-    regardless of their type (for example, `2400`).
-  type: number
-  unit: Hz
-ScaleFactor:
-  name: ScaleFactor
-  display_name: Scale Factor
-  description: |
-    Scale factor for each frame. This field MUST be defined if the imaging data (`.nii[.gz]`) are scaled.
-    If this field is not defined, then it is assumed that the scaling factor is 1. Defining this field
-    when the scaling factor is 1 is RECOMMENDED, for the sake of clarity.
-  type: array
-  items:
-    type: number
-ScanDate:
-  name: ScanDate
-  display_name: Scan Date
-  description: |
-    Date of scan in the format `"YYYY-MM-DD[Z]"`.
-    This field is DEPRECATED, and this metadata SHOULD be recorded in the `acq_time` column of the
-    corresponding [Scans file](SPEC_ROOT/03-modality-agnostic-files.md#scans-file).
-  type: string
-  format: date
-ScanOptions:
-  name: ScanOptions
-  display_name: Scan Options
-  description: |
-    Parameters of ScanningSequence.
-    Corresponds to DICOM Tag 0018, 0022 `Scan Options`.
-  anyOf:
-  - type: string
-  - type: array
-    items:
-      type: string
-ScanStart:
-  name: ScanStart
-  display_name: Scan Start
-  description: |
-    Time of start of scan with respect to `TimeZero` in the default unit seconds.
-  type: number
-  unit: s
-ScanningSequence:
-  name: ScanningSequence
-  display_name: Scanning Sequence
-  description: |
-    Description of the type of data acquired.
-    Corresponds to DICOM Tag 0018, 0020 `Scanning Sequence`.
-  anyOf:
-  - type: string
-  - type: array
-    items:
-      type: string
-ScatterFraction:
-  name: ScatterFraction
-  display_name: Scatter Fraction
-  description: |
-    Scatter fraction for each frame (Units: 0-100%).
-  type: array
-  items:
-    type: number
-    minimum: 0
-    maximum: 100
-SequenceName:
-  name: SequenceName
-  display_name: Sequence Name
-  description: |
-    Manufacturer's designation of the sequence name.
-    Corresponds to DICOM Tag 0018, 0024 `Sequence Name`.
-  type: string
-SequenceVariant:
-  name: SequenceVariant
-  display_name: Sequence Variant
-  description: |
-    Variant of the ScanningSequence.
-    Corresponds to DICOM Tag 0018, 0021 `Sequence Variant`.
-  anyOf:
-  - type: string
-  - type: array
-    items:
-      type: string
-SinglesRate:
-  name: SinglesRate
-  display_name: Singles Rate
-  description: |
-    Singles rate for each frame (same units as `Units`, for example, `"Bq/mL"`).
-  type: array
-  items:
-    type: number
-SkullStripped:
-  name: SkullStripped
-  display_name: Skull Stripped
-  description: |
-    Whether the volume was skull stripped (non-brain voxels set to zero) or not.
-  type: boolean
-SliceEncodingDirection:
-  name: SliceEncodingDirection
-  display_name: Slice Encoding Direction
-  description: |
-    The axis of the NIfTI data along which slices were acquired,
-    and the direction in which `"SliceTiming"` is defined with respect to.
-    `i`, `j`, `k` identifiers correspond to the first, second and third axis of
-    the data in the NIfTI file.
-    A `-` sign indicates that the contents of `"SliceTiming"` are defined in
-    reverse order - that is, the first entry corresponds to the slice with the
-    largest index, and the final entry corresponds to slice index zero.
-    When present, the axis defined by `"SliceEncodingDirection"` needs to be
-    consistent with the `slice_dim` field in the NIfTI header.
-    When absent, the entries in `"SliceTiming"` must be in the order of increasing
-    slice index as defined by the NIfTI header.
-  type: string
-  enum:
-  - i
-  - j
-  - k
-  - i-
-  - j-
-  - k-
-SliceThickness:
-  name: SliceThickness
-  display_name: Slice Thickness
-  description: |
-    Slice thickness of the tissue sample in the unit micrometers (`"um"`) (for example: `5`).
-  type: number
-  unit: um
-  exclusiveMinimum: 0
-SliceTiming:
-  name: SliceTiming
-  display_name: Slice Timing
-  description: |
-    The time at which each slice was acquired within each volume (frame) of the
-    acquisition.
-    Slice timing is not slice order -- rather, it is a list of times containing
-    the time (in seconds) of each slice acquisition in relation to the beginning
-    of volume acquisition.
-    The list goes through the slices along the slice axis in the slice encoding
-    dimension (see below).
-    Note that to ensure the proper interpretation of the `"SliceTiming"` field,
-    it is important to check if the OPTIONAL `SliceEncodingDirection` exists.
-    In particular, if `"SliceEncodingDirection"` is negative,
-    the entries in `"SliceTiming"` are defined in reverse order with respect to the
-    slice axis, such that the final entry in the `"SliceTiming"` list is the time
-    of acquisition of slice 0. Without this parameter slice time correction will
-    not be possible.
-  type: array
-  items:
-    type: number
-    minimum: 0
-    unit: s
-SoftwareFilters:
-  name: SoftwareFilters
-  display_name: Software Filters
-  description: |
-    [Object](https://www.json.org/json-en.html)
-    of temporal software filters applied, or `"n/a"` if the data is
-    not available.
-    Each key-value pair in the JSON object is a name of the filter and an object
-    in which its parameters are defined as key-value pairs
-    (for example, `{"Anti-aliasing filter":
-    {"half-amplitude cutoff (Hz)": 500, "Roll-off": "6dB/Octave"}}`).
-  anyOf:
-  - type: object
-    additionalProperties:
-      type: object
-  - type: string
-    enum:
-    - n/a
-SoftwareName:
-  name: SoftwareName
-  display_name: Software Name
-  description: |
-    Name of the software that was used to present the stimuli.
-  type: string
-SoftwareRRID:
-  name: SoftwareRRID
-  display_name: SoftwareRRID
-  description: |
-    [Research Resource Identifier](https://scicrunch.org/resources) of the
-    software that was used to present the stimuli.
-    Examples: The RRID for Psychtoolbox is 'SCR_002881',
-    and that of PsychoPy is 'SCR_006571'.
-  type: string
-  format: rrid
-SoftwareVersion:
-  name: SoftwareVersion
-  display_name: Software Version
-  description: |
-    Version of the software that was used to present the stimuli.
-  type: string
-SoftwareVersions:
-  name: SoftwareVersions
-  display_name: Software Versions
-  description: |
-    Manufacturer's designation of software version of the equipment that produced
-    the measurements.
-  type: string
-SourceDatasets:
-  name: SourceDatasets
-  display_name: Source Datasets
-  description: |
-    Used to specify the locations and relevant attributes of all source datasets.
-    Valid keys in each object include `"URL"`, `"DOI"` (see
-    [URI](SPEC_ROOT/02-common-principles.md#uniform-resource-indicator)), and
-    `"Version"` with
-    [string](https://www.w3schools.com/js/js_json_datatypes.asp)
-    values.
-  type: array
-  items:
-    type: object
-    properties:
-      URL:
-        type: string
-        format: uri
-      DOI:
-        type: string
-      Version:
-        type: string
-Sources:
-  name: Sources
-  display_name: Sources
-  description: |
-    A list of files with the paths specified relative to dataset root;
-    these files were directly used in the creation of this derivative data file.
-    For example, if a derivative A is used in the creation of another
-    derivative B, which is in turn used to generate C in a chain of A->B->C,
-    C should only list B in `"Sources"`, and B should only list A in `"Sources"`.
-    However, in case both X and Y are directly used in the creation of Z,
-    then Z should list X and Y in `"Sources"`,
-    regardless of whether X was used to generate Y.
-  type: array
-  items:
-    type: string
-    format: dataset_relative
-SpatialReference:
-  name: SpatialReference
-  display_name: Spatial Reference
-  description: |
-    For images with a single reference, the value MUST be a single string.
-    For images with multiple references, such as surface and volume references,
-    a JSON object MUST be used.
-  anyOf:
-  - type: string
-    enum:
-    - orig
-  - type: string
-    format: uri
-  - type: string
-    format: dataset_relative
-  - type: object
-    additionalProperties:
-      anyOf:
-      - type: string
-        enum:
-        - orig
-      - type: string
-        format: uri
-      - type: string
-        format: dataset_relative
-SpecificRadioactivity:
-  name: SpecificRadioactivity
-  display_name: Specific Radioactivity
-  description: |
-    Specific activity of compound injected.
-    **Note this is not required for an FDG acquisition, since it is not available,
-    and SHOULD be set to `"n/a"`**.
-  anyOf:
-  - type: number
-  - type: string
-    enum:
-    - n/a
-SpecificRadioactivityMeasTime:
-  name: SpecificRadioactivityMeasTime
-  display_name: Specific Radioactivity Measurement Time
-  description: |
-    Time to which specific radioactivity measurement above applies in the default
-    unit `"hh:mm:ss"`.
-  type: string
-  format: time
-SpecificRadioactivityUnits:
-  name: SpecificRadioactivityUnits
-  display_name: Specific Radioactivity Units
-  description: |
-    Unit format of specified specific radioactivity (for example, `"Bq/g"`).
-    **Note this is not required for an FDG acquisition, since it is not available,
-    and SHOULD be set to `"n/a"`**.
-  anyOf:
-  - type: string
-    format: unit
-  - type: string
-    enum:
-    - n/a
-SpoilingGradientDuration:
-  name: SpoilingGradientDuration
-  display_name: Spoiling Gradient Duration
-  description: |
-    The duration of the spoiler gradient lobe in seconds.
-    The duration of a trapezoidal lobe is defined as the summation of ramp-up
-    and plateau times.
-  type: number
-  unit: s
-SpoilingGradientMoment:
-  name: SpoilingGradientMoment
-  display_name: Spoiling Gradient Moment
-  description: |
-    Zeroth moment of the spoiler gradient lobe in
-    millitesla times second per meter (mT.s/m).
-  type: number
-  unit: mT.s/m
-SpoilingRFPhaseIncrement:
-  name: SpoilingRFPhaseIncrement
-  display_name: Spoiling RF Phase Increment
-  description: |
-    The amount of incrementation described in degrees,
-    which is applied to the phase of the excitation pulse at each TR period for
-    achieving RF spoiling.
-  type: number
-  unit: degrees
-SpoilingState:
-  name: SpoilingState
-  display_name: Spoiling State
-  description: |
-    Boolean stating whether the pulse sequence uses any type of spoiling
-    strategy to suppress residual transverse magnetization.
-  type: boolean
-SpoilingType:
-  name: SpoilingType
-  display_name: Spoiling Type
-  description: |
-    Specifies which spoiling method(s) are used by a spoiled sequence.
-  type: string
-  enum:
-  - RF
-  - GRADIENT
-  - COMBINED
-StartTime:
-  name: StartTime
-  display_name: Start Time
-  description: |
-    Start time in seconds in relation to the start of acquisition of the first
-    data sample in the corresponding neural dataset (negative values are allowed).
-  type: number
-  unit: s
-StationName:
-  name: StationName
-  display_name: Station Name
-  description: |
-    Institution defined name of the machine that produced the measurements.
-  type: string
-StimulusPresentation:
-  name: StimulusPresentation
-  display_name: Stimulus Presentation
-  description: |
-    Object containing key-value pairs related to the software used to present
-    the stimuli during the experiment, specifically:
-    `"OperatingSystem"`, `"SoftwareName"`, `"SoftwareRRID"`, `"SoftwareVersion"` and
-    `"Code"`.
-    See table below for more information.
-  type: object
-  properties:
-    OperatingSystem:
-      $ref: OperatingSystem
-    SoftwareName:
-      $ref: SoftwareName
-    SoftwareRRID:
-      $ref: SoftwareRRID
-    SoftwareVersion:
-      $ref: SoftwareVersion
-    Code:
-      $ref: Code
-SubjectArtefactDescription:
-  name: SubjectArtefactDescription
-  display_name: Subject Artefact Description
-  description: |
-    Freeform description of the observed subject artefact and its possible cause
-    (for example, `"Vagus Nerve Stimulator"`, `"non-removable implant"`).
-    If this field is set to `"n/a"`, it will be interpreted as absence of major
-    source of artifacts except cardiac and blinks.
-  type: string
-TaskDescription:
-  name: TaskDescription
-  display_name: Task Description
-  description: |
-    Longer description of the task.
-  type: string
-TaskName:
-  name: TaskName
-  display_name: Task Name
-  description: |
-    Name of the task.
-    No two tasks should have the same name.
-    The task label included in the file name is derived from this `"TaskName"` field
-    by removing all non-alphanumeric (`[a-zA-Z0-9]`) characters.
-    For example `"TaskName"` `"faces n-back"` will correspond to task label
-    `facesnback`.
-  type: string
-TermURL:
-  name: TermURL
-  display_name: TermURL
-  description: |
-    URL pointing to a formal definition of this type of data in an ontology
-    available on the web.
-  type: string
-TimeZero:
-  name: TimeZero
-  display_name: Time Zero
-  description: |
-    Time zero to which all scan and/or blood measurements have been adjusted to,
-    in the unit "hh:mm:ss".
-    This should be equal to `"InjectionStart"` or `"ScanStart"`.
-  type: string
-  format: time
-TissueDeformationScaling:
-  name: TissueDeformationScaling
-  display_name: Tissue Deformation Scaling
-  description: |
-    Estimated deformation of the tissue, given as a percentage of the original
-    tissue size (for examples: for a shrinkage of 3%, the value is `97`;
-    and for an expansion of 100%, the value is `200`).
-  type: number
-  exclusiveMinimum: 0
-TissueOrigin:
-  name: TissueOrigin
-  display_name: Tissue Origin
-  description: |
-    Describes the type of tissue analyzed for `"SampleOrigin"` `brain`.
-  type: string
-  enum:
-  - gray matter
-  - white matter
-  - csf
-  - meninges
-  - macrovascular
-  - microvascular
-TotalAcquiredPairs:
-  name: TotalAcquiredPairs
-  display_name: Total Acquired Pairs
-  description: |
-    The total number of acquired `control`-`label` pairs.
-    A single pair consists of a single `control` and a single `label` image.
-  type: number
-  exclusiveMinimum: 0
-TotalReadoutTime:
-  name: TotalReadoutTime
-  display_name: Total Readout Time
-  description: |
-    This is actually the "effective" total readout time,
-    defined as the readout duration, specified in seconds,
-    that would have generated data with the given level of distortion.
-    It is NOT the actual, physical duration of the readout train.
-    If `"EffectiveEchoSpacing"` has been properly computed,
-    it is just `EffectiveEchoSpacing * (ReconMatrixPE - 1)`.
-  type: number
-  unit: s
-TracerMolecularWeight:
-  name: TracerMolecularWeight
-  display_name: Tracer Molecular Weight
-  description: |
-    Accurate molecular weight of the tracer used.
-  type: number
-TracerMolecularWeightUnits:
-  name: TracerMolecularWeightUnits
-  display_name: Tracer Molecular Weight Units
-  description: |
-    Unit of the molecular weights measurement (for example, `"g/mol"`).
-  type: string
-  format: unit
-TracerName:
-  name: TracerName
-  display_name: Tracer Name
-  description: |
-    Name of the tracer compound used (for example, `"CIMBI-36"`)
-  type: string
-TracerRadLex:
-  name: TracerRadLex
-  display_name: Tracer Rad Lex
-  description: |
-    ID of the tracer compound from the RadLex Ontology.
-  type: string
-TracerRadionuclide:
-  name: TracerRadionuclide
-  display_name: Tracer Radionuclide
-  description: |
-    Radioisotope labelling tracer (for example, `"C11"`).
-  type: string
-TracerSNOMED:
-  name: TracerSNOMED
-  display_name: TracerSNOMED
-  description: |
-    ID of the tracer compound from the SNOMED Ontology
-    (subclass of Radioactive isotope).
-  type: string
-TriggerChannelCount:
-  name: TriggerChannelCount
-  display_name: Trigger Channel Count
-  description: |
-    Number of channels for digital (TTL bit level) triggers.
-  type: integer
-  minimum: 0
-TubingLength:
-  name: TubingLength
-  display_name: Tubing Length
-  description: |
-    The length of the blood tubing, from the subject to the detector in meters.
-  type: number
-  unit: m
-TubingType:
-  name: TubingType
-  display_name: Tubing Type
-  description: |
-    Description of the type of tubing used, ideally including the material and
-    (internal) diameter.
-  type: string
-Type:
-  name: Type
-  display_name: Type
-  description: |
-    Short identifier of the mask.
-    The value `"Brain"` refers to a brain mask.
-    The value `"Lesion"` refers to a lesion mask.
-    The value `"Face"` refers to a face mask.
-    The value `"ROI"` refers to a region of interest mask.
-  type: string
-  enum:
-  - Brain
-  - Lesion
-  - Face
-  - ROI
-Units:
-  name: Units
-  display_name: Units
-  description: |
-    Measurement units for the associated file.
-    SI units in CMIXF formatting are RECOMMENDED
-    (see [Units](SPEC_ROOT/02-common-principles.md#units)).
-  type: string
-  format: unit
-VascularCrushing:
-  name: VascularCrushing
-  display_name: Vascular Crushing
-  description: |
-    Boolean indicating if Vascular Crushing is used.
-    Corresponds to DICOM Tag 0018, 9259 `ASL Crusher Flag`.
-  type: boolean
-VascularCrushingVENC:
-  name: VascularCrushingVENC
-  display_name: Vascular Crushing VENC
-  description: |
-    The crusher gradient strength, in centimeters per second.
-    Specify either one number for the total time-series, or provide an array of
-    numbers, for example when using QUASAR, using the value zero to identify
-    volumes for which `VascularCrushing` was turned off.
-    Corresponds to DICOM Tag 0018, 925A `ASL Crusher Flow Limit`.
-  anyOf:
-  - type: number
-    unit: cm/s
-  - type: array
-    items:
-      type: number
-      unit: cm/s
-VolumeTiming:
-  name: VolumeTiming
-  display_name: Volume Timing
-  description: |
-    The time at which each volume was acquired during the acquisition.
-    It is described using a list of times referring to the onset of each volume
-    in the BOLD series.
-    The list must have the same length as the BOLD series,
-    and the values must be non-negative and monotonically increasing.
-    This field is mutually exclusive with `"RepetitionTime"` and `"DelayTime"`.
-    If defined, this requires acquisition time (TA) be defined via either
-    `"SliceTiming"` or `"AcquisitionDuration"` be defined.
-  type: array
-  minItems: 1
-  items:
-    type: number
-    unit: s
-WholeBloodAvail:
-  name: WholeBloodAvail
-  display_name: Whole Blood Avail
-  description: |
-    Boolean that specifies if whole blood measurements are available.
-    If `true`, the `whole_blood_radioactivity` column MUST be present in the
-    corresponding `*_blood.tsv` file.
-  type: boolean
-WithdrawalRate:
-  name: WithdrawalRate
-  display_name: Withdrawal Rate
-  description: |
-    The rate at which the blood was withdrawn from the subject.
-    The unit of the specified withdrawal rate should be in `"mL/s"`.
-  type: number
-  unit: mL/s
-_CoordUnits:
-  type: string
-  enum:
-  - m
-  - mm
-  - cm
-  - n/a
-_EEGCoordSys:
-  type: string
-  enum:
-  - CapTrak
-  - EEGLAB
-  - EEGLAB-HJ
-  - Other
-_GeneticLevelEnum:
-  type: string
-  enum:
-  - Genetic
-  - Genomic
-  - Epigenomic
-  - Transcriptomic
-  - Metabolomic
-  - Proteomic
-_LandmarkCoordinates:
-  type: object
-  additionalProperties:
-    type: array
-    items:
-      type: number
-    minItems: 3
-    maxItems: 3
-_MEGCoordSys:
-  type: string
-  enum:
-  - CTF
-  - ElektaNeuromag
-  - 4DBti
-  - KitYokogawa
-  - ChietiItab
-  - Other
-_StandardTemplateCoordSys:
-  type: string
-  enum:
-  - ICBM452AirSpace
-  - ICBM452Warp5Space
-  - IXI549Space
-  - fsaverage
-  - fsaverageSym
-  - fsLR
-  - MNIColin27
-  - MNI152Lin
-  - MNI152NLin2009aSym
-  - MNI152NLin2009bSym
-  - MNI152NLin2009cSym
-  - MNI152NLin2009aAsym
-  - MNI152NLin2009bAsym
-  - MNI152NLin2009cAsym
-  - MNI152NLin6Sym
-  - MNI152NLin6ASym
-  - MNI305
-  - NIHPD
-  - OASIS30AntsOASISAnts
-  - OASIS30Atropos
-  - Talairach
-  - UNCInfant
-_StandardTemplateDeprecatedCoordSys:
-  type: string
-  enum:
-  - fsaverage3
-  - fsaverage4
-  - fsaverage5
-  - fsaverage6
-  - fsaveragesym
-  - UNCInfant0V21
-  - UNCInfant1V21
-  - UNCInfant2V21
-  - UNCInfant0V22
-  - UNCInfant1V22
-  - UNCInfant2V22
-  - UNCInfant0V23
-  - UNCInfant1V23
-  - UNCInfant2V23
-_iEEGCoordSys:
-  type: string
-  enum:
-  - Pixels
-  - ACPC
-  - Other
-iEEGCoordinateProcessingDescription:
-  name: iEEGCoordinateProcessingDescription
-  display_name: iEEG Coordinate Processing Description
-  description: |
-    Has any post-processing (such as projection) been done on the electrode
-    positions (for example, `"surface_projection"`, `"none"`).
-  type: string
-iEEGCoordinateProcessingReference:
-  name: iEEGCoordinateProcessingReference
-  display_name: iEEG Coordinate Processing Reference
-  description: |
-    A reference to a paper that defines in more detail the method used to
-    localize the electrodes and to post-process the electrode positions.
-  type: string
-iEEGCoordinateSystem:
-  name: iEEGCoordinateSystem
-  display_name: iEEG Coordinate System
-  description: |
-    Defines the coordinate system for the iEEG sensors.
-    See
-    [Appendix VIII](SPEC_ROOT/99-appendices/08-coordinate-systems.md)
-    for a list of restricted keywords for coordinate systems.
-    If `"Other"`, provide definition of the coordinate system in
-    `iEEGCoordinateSystemDescription`.
-    If positions correspond to pixel indices in a 2D image
-    (of either a volume-rendering, surface-rendering, operative photo, or
-    operative drawing), this MUST be `"Pixels"`.
-    For more information, see the section on
-    [2D coordinate systems](/04-modality-specific-files/04-intracranial\
-    -electroencephalography.html#allowed-2d-coordinate-systems).
-  anyOf:
-  - $ref: _iEEGCoordSys
-  - $ref: _StandardTemplateCoordSys
-  - $ref: _StandardTemplateDeprecatedCoordSys
-iEEGCoordinateSystemDescription:
-  name: iEEGCoordinateSystemDescription
-  display_name: iEEG Coordinate System Description
-  description: |
-    Free-form text description of the coordinate system.
-    May also include a link to a documentation page or paper describing the
-    system in greater detail.
-  type: string
-iEEGCoordinateUnits:
-  name: iEEGCoordinateUnits
-  display_name: iEEG Coordinate Units
-  description: |
-    Units of the `*_electrodes.tsv`.
-    MUST be `"pixels"` if `iEEGCoordinateSystem` is `Pixels`.
-  type: string
-  enum:
-  - m
-  - mm
-  - cm
-  - pixels
-  - n/a
-iEEGElectrodeGroups:
-  name: iEEGElectrodeGroups
-  display_name: iEEG Electrode Groups
-  description: |
-    Field to describe the way electrodes are grouped into strips, grids or depth
-    probes.
-    For example, `"grid1: 10x8 grid on left temporal pole, strip2: 1x8 electrode
-    strip on xxx"`.
-  type: string
-iEEGGround:
-  name: iEEGGround
-  display_name: iEEG Ground
-  description: |
-    Description of the location of the ground electrode
-    (`"placed on right mastoid (M2)"`).
-  type: string
-iEEGPlacementScheme:
-  name: iEEGPlacementScheme
-  display_name: iEEG Placement Scheme
-  description: |
-    Freeform description of the placement of the iEEG electrodes.
-    Left/right/bilateral/depth/surface
-    (for example, `"left frontal grid and bilateral hippocampal depth"` or
-    `"surface strip and STN depth"` or
-    `"clinical indication bitemporal, bilateral temporal strips and left grid"`).
-  type: string
-iEEGReference:
-  name: iEEGReference
-  display_name: iEEG Reference
-  description: |
-    General description of the reference scheme used and (when applicable) of
-    location of the reference electrode in the raw recordings
-    (for example, `"left mastoid"`, `"bipolar"`,
-    `"T01"` for electrode with name T01,
-    `"intracranial electrode on top of a grid, not included with data"`,
-    `"upside down electrode"`).
-    If different channels have a different reference,
-    this field should have a general description and the channel specific
-    reference should be defined in the `channels.tsv` file.
-  type: string
diff --git a/dandi/support/bids/schemadata/1.7.0+369/objects/modalities.yaml b/dandi/support/bids/schemadata/1.7.0+369/objects/modalities.yaml
deleted file mode 100644
index 862577d21..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/objects/modalities.yaml
+++ /dev/null
@@ -1,30 +0,0 @@
----
-# This file describes modalities supported by BIDS.
-mri:
-  display_name: Magnetic Resonance Imaging
-  description: |
-    Data acquired with an MRI scanner.
-eeg:
-  display_name: Electroencephalography
-  description: |
-    Data acquired with EEG.
-ieeg:
-  display_name: Intracranial Electroencephalography
-  description: |
-    Data acquired with iEEG.
-meg:
-  display_name: Magnetoencephalography
-  description: |
-    Data acquired with an MEG scanner.
-beh:
-  display_name: Behavioral experiments
-  description: |
-    Behavioral data acquired without accompanying neuroimaging data.
-pet:
-  display_name: Positron Emission Tomography
-  description: |
-    Data acquired with PET.
-micr:
-  display_name: Microscopy
-  description: |
-    Data acquired with a microscope.
diff --git a/dandi/support/bids/schemadata/1.7.0+369/objects/suffixes.yaml b/dandi/support/bids/schemadata/1.7.0+369/objects/suffixes.yaml
deleted file mode 100644
index 1ea222113..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/objects/suffixes.yaml
+++ /dev/null
@@ -1,752 +0,0 @@
----
-# This file defines valid BIDS file suffixes.
-# For rules regarding how suffixes relate to datatypes, see files in `rules/datatypes/`.
-TwoPE:
-  value: 2PE
-  display_name: 2-photon excitation microscopy
-  description: |
-    2-photon excitation microscopy imaging data
-BF:
-  value: BF
-  display_name: Bright-field microscopy
-  description: |
-    Bright-field microscopy imaging data
-Chimap:
-  value: Chimap
-  display_name: Quantitative susceptibility map (QSM)
-  description: |
-    In parts per million (ppm).
-    QSM allows for determining the underlying magnetic susceptibility of tissue
-    (Chi)
-    ([Wang & Liu, 2014](https://doi.org/10.1002/mrm.25358)).
-    Chi maps are REQUIRED to use this suffix regardless of the method used to
-    generate them.
-  unit: ppm
-CARS:
-  value: CARS
-  display_name: Coherent anti-Stokes Raman spectroscopy
-  description: |
-    Coherent anti-Stokes Raman spectroscopy imaging data
-CONF:
-  value: CONF
-  display_name: Confocal microscopy
-  description: |
-    Confocal microscopy imaging data
-DIC:
-  value: DIC
-  display_name: Differential interference contrast microscopy
-  description: |
-    Differential interference contrast microscopy imaging data
-DF:
-  value: DF
-  display_name: Dark-field microscopy
-  description: |
-    Dark-field microscopy imaging data
-FLAIR:
-  value: FLAIR
-  display_name: Fluid attenuated inversion recovery image
-  description: |
-    In arbitrary units (arbitrary).
-    Structural images with predominant T2 contribution (also known as T2-FLAIR),
-    in which signal from fluids (for example, CSF) is nulled out by adjusting
-    inversion time, coupled with notably long repetition and echo times.
-  unit: arbitrary
-FLASH:
-  value: FLASH
-  display_name: Fast-Low-Angle-Shot image
-  description: |
-    FLASH (Fast-Low-Angle-Shot) is a vendor-specific implementation for spoiled
-    gradient echo acquisition.
-    It is commonly used for rapid anatomical imaging and also for many different
-    qMRI applications.
-    When used for a single file, it does not convey any information about the
-    image contrast.
-    When used in a file collection, it may result in conflicts across filenames of
-    different applications.
-    **Change:** Removed from suffixes.
-FLUO:
-  value: FLUO
-  display_name: Fluorescence microscopy
-  description: |
-    Fluorescence microscopy imaging data
-IRT1:
-  value: IRT1
-  display_name: Inversion recovery T1 mapping
-  description: |
-    The IRT1 method involves multiple inversion recovery spin-echo images
-    acquired at different inversion times
-    ([Barral et al. 2010](https://doi.org/10.1002/mrm.22497)).
-M0map:
-  value: M0map
-  display_name: Equilibrium magnetization (M0) map
-  description: |
-    In arbitrary units (arbitrary).
-    A common quantitative MRI (qMRI) fitting variable that represents the amount
-    of magnetization at thermal equilibrium.
-    M0 maps are RECOMMENDED to use this suffix if generated by qMRI applications
-    (for example, variable flip angle T1 mapping).
-  unit: arbitrary
-MEGRE:
-  value: MEGRE
-  display_name: Multi-echo Gradient Recalled Echo
-  description: |
-    Anatomical gradient echo images acquired at different echo times.
-    Please note that this suffix is not intended for the logical grouping of
-    images acquired using an Echo Planar Imaging (EPI) readout.
-MESE:
-  value: MESE
-  display_name: Multi-echo Spin Echo
-  description: |
-    The MESE method involves multiple spin echo images acquired at different echo
-    times and is primarily used for T2 mapping.
-    Please note that this suffix is not intended for the logical grouping of
-    images acquired using an Echo Planar Imaging (EPI) readout.
-MP2RAGE:
-  value: MP2RAGE
-  display_name: Magnetization Prepared Two Gradient Echoes
-  description: |
-    The MP2RAGE method is a special protocol that collects several images at
-    different flip angles and inversion times to create a parametric T1map by
-    combining the magnitude and phase images
-    ([Marques et al. 2010](https://doi.org/10.1016/j.neuroimage.2009.10.002)).
-MPE:
-  value: MPE
-  display_name: Multi-photon excitation microscopy
-  description: |
-    Multi-photon excitation microscopy imaging data
-MPM:
-  value: MPM
-  display_name: Multi-parametric Mapping
-  description: |
-    The MPM approaches (a.k.a hMRI) involves the acquisition of highly-similar
-    anatomical images that differ in terms of application of a magnetization
-    transfer RF pulse (MTon or MToff), flip angle and (optionally) echo time and
-    magnitue/phase parts
-    ([Weiskopf et al. 2013](https://doi.org/10.3389/fnins.2013.00095)).
-    See [here](https://owncloud.gwdg.de/index.php/s/iv2TOQwGy4FGDDZ) for
-    suggested MPM acquisition protocols.
-MTR:
-  value: MTR
-  display_name: Magnetization Transfer Ratio
-  description: |
-    This method is to calculate a semi-quantitative magnetization transfer ratio
-    map.
-MTRmap:
-  value: MTRmap
-  display_name: Magnetization transfer ratio image
-  description: |
-    In arbitrary units (arbitrary).
-    MTR maps are REQUIRED to use this suffix regardless of the method used to
-    generate them.
-    MTRmap intensity values are RECOMMENDED to be represented in percentage in
-    the range of 0-100%.
-  unit: arbitrary
-  minValue: 0
-  maxValue: 100
-MTS:
-  value: MTS
-  display_name: Magnetization transfer saturation
-  description: |
-    This method is to calculate a semi-quantitative magnetization transfer
-    saturation index map.
-    The MTS method involves three sets of anatomical images that differ in terms
-    of application of a magnetization transfer RF pulse (MTon or MToff) and flip
-    angle ([Helms et al. 2008](https://doi.org/10.1002/mrm.21732)).
-MTVmap:
-  value: MTVmap
-  display_name: Macromolecular tissue volume (MTV) image
-  description: |
-    In arbitrary units (arbitrary).
-    MTV maps are REQUIRED to use this suffix regardless of the method used to
-    generate them.
-  unit: arbitrary
-MTsat:
-  value: MTsat
-  display_name: Magnetization transfer saturation image
-  description: |
-    In arbitrary units (arbitrary).
-    MTsat maps are REQUIRED to use this suffix regardless of the method used to
-    generate them.
-  unit: arbitrary
-MWFmap:
-  value: MWFmap
-  display_name: Myelin water fraction image
-  description: |
-    In arbitrary units (arbitrary).
-    MWF maps are REQUIRED to use this suffix regardless of the method used to
-    generate them.
-    MWF intensity values are RECOMMENDED to be represented in percentage in the
-    range of 0-100%.
-  unit: arbitrary
-  minValue: 0
-  maxValue: 100
-NLO:
-  value: NLO
-  display_name: Nonlinear optical microscopy
-  description: |
-    Nonlinear optical microscopy imaging data
-OCT:
-  value: OCT
-  display_name: Optical coherence tomography
-  description: |
-    Optical coherence tomography imaging data
-PC:
-  value: PC
-  display_name: Phase-contrast microscopy
-  description: |
-    Phase-contrast microscopy imaging data
-PD:
-  value: PD
-  display_name: Proton density image
-  description: |
-    Ambiguous, may refer to a parametric image or to a conventional image.
-    **Change:** Replaced by `PDw` or `PDmap`.
-  unit: arbitrary
-PDT2:
-  value: PDT2
-  display_name: PD and T2 weighted image
-  description: |
-    In arbitrary units (arbitrary).
-    PDw and T2w images acquired using a dual echo FSE sequence through view
-    sharing process
-    ([Johnson et al. 1994](https://pubmed.ncbi.nlm.nih.gov/8010268/)).
-  unit: arbitrary
-PDT2map:
-  value: PDT2map
-  display_name: Combined PD/T2 image
-  description: |
-    In arbitrary units (arbitrary).
-    Combined PD/T2 maps are REQUIRED to use this suffix regardless of the method
-    used to generate them.
-  unit: arbitrary
-PDmap:
-  value: PDmap
-  display_name: Proton density image
-  description: |
-    In arbitrary units (arbitrary).
-    PD maps are REQUIRED to use this suffix regardless of the method used to
-    generate them.
-  unit: arbitrary
-PDw:
-  value: PDw
-  display_name: Proton density (PD) weighted image
-  description: |
-    In arbitrary units (arbitrary).
-    The contrast of these images is mainly determined by spatial variations in
-    the spin density (1H) of the imaged specimen.
-    In spin-echo sequences this contrast is achieved at short repetition and long
-    echo times.
-    In a gradient-echo acquisition, PD weighting dominates the contrast at long
-    repetition and short echo times, and at small flip angles.
-  unit: arbitrary
-PLI:
-  value: PLI
-  display_name: Polarized-light microscopy
-  description: |
-    Polarized-light microscopy imaging data
-R1map:
-  value: R1map
-  display_name: Longitudinal relaxation rate image
-  description: |
-    In seconds<sup>-1</sup> (1/s).
-    R1 maps (R1 = 1/T1) are REQUIRED to use this suffix regardless of the method
-    used to generate them.
-  unit: 1/s
-R2map:
-  value: R2map
-  display_name: True transverse relaxation rate image
-  description: |
-    In seconds<sup>-1</sup> (1/s).
-    R2 maps (R2 = 1/T2) are REQUIRED to use this suffix regardless of the method
-    used to generate them.
-  unit: 1/s
-R2starmap:
-  value: R2starmap
-  display_name: Observed transverse relaxation rate image
-  description: |
-    In seconds<sup>-1</sup> (1/s).
-    R2-star maps (R2star = 1/T2star) are REQUIRED to use this suffix regardless
-    of the method used to generate them.
-  unit: 1/s
-RB1COR:
-  value: RB1COR
-  display_name: RB1COR
-  description: |
-    Low resolution images acquired by the body coil
-    (in the gantry of the scanner) and the head coil using identical acquisition
-    parameters to generate a combined sensitivity map as described in
-    [Papp et al. (2016)](https://doi.org/10.1002/mrm.26058).
-RB1map:
-  value: RB1map
-  display_name: RF receive sensitivity map
-  description: |
-    In arbitrary units (arbitrary).
-    Radio frequency (RF) receive (B1-) sensitivity maps are REQUIRED to use this
-    suffix regardless of the method used to generate them.
-    RB1map intensity values are RECOMMENDED to be represented as percent
-    multiplicative factors such that Amplitude<sub>effective</sub> =
-    B1-<sub>intensity</sub>\*Amplitude<sub>ideal</sub>.
-  unit: arbitrary
-S0map:
-  value: S0map
-  display_name: Observed signal amplitude (S0) image
-  description: |
-    In arbitrary units (arbitrary).
-    For a multi-echo (typically fMRI) sequence, S0 maps index the baseline signal
-    before exponential (T2-star) signal decay.
-    In other words: the exponential of the intercept for a linear decay model
-    across log-transformed echos. For more information, please see, for example,
-    [the tedana documentation](https://tedana.readthedocs.io/en/latest/\
-    approach.html#monoexponential-decay-model-fit).
-    S0 maps are RECOMMENDED to use this suffix if derived from an ME-FMRI dataset.
-SEM:
-  value: SEM
-  display_name: Scanning electron microscopy
-  description: |
-    Scanning electron microscopy imaging data
-SPIM:
-  value: SPIM
-  display_name: Selective plane illumination microscopy
-  description: |
-    Selective plane illumination microscopy imaging data
-SR:
-  value: SR
-  display_name: Super-resolution microscopy
-  description: |
-    Super-resolution microscopy imaging data
-T1map:
-  value: T1map
-  display_name: Longitudinal relaxation time image
-  description: |
-    In seconds (s).
-    T1 maps are REQUIRED to use this suffix regardless of the method used to
-    generate them.
-    See [this interactive book on T1 mapping](https://qmrlab.org/t1_book/intro)
-    for further reading on T1-mapping.
-  unit: s
-T1rho:
-  value: T1rho
-  display_name: T1 in rotating frame (T1 rho) image
-  description: |
-    In seconds (s).
-    T1-rho maps are REQUIRED to use this suffix regardless of the method used to
-    generate them.
-  unit: s
-T1w:
-  value: T1w
-  display_name: T1-weighted image
-  description: |
-    In arbitrary units (arbitrary).
-    The contrast of these images is mainly determined by spatial variations in
-    the longitudinal relaxation time of the imaged specimen.
-    In spin-echo sequences this contrast is achieved at relatively short
-    repetition and echo times.
-    To achieve this weighting in gradient-echo images, again, short repetition
-    and echo times are selected; however, at relatively large flip angles.
-    Another common approach to increase T1 weighting in gradient-echo images is
-    to add an inversion preparation block to the beginning of the imaging
-    sequence (for example, `TurboFLASH` or `MP-RAGE`).
-  unit: arbitrary
-T2map:
-  value: T2map
-  display_name: True transverse relaxation time image
-  description: |
-    In seconds (s).
-    T2 maps are REQUIRED to use this suffix regardless of the method used to
-    generate them.
-  unit: s
-T2star:
-  value: T2star
-  display_name: T2\* image
-  description: |
-    Ambiguous, may refer to a parametric image or to a conventional image.
-    **Change:** Replaced by `T2starw` or `T2starmap`.
-  anyOf:
-  - unit: arbitrary
-  - unit: s
-T2starmap:
-  value: T2starmap
-  display_name: Observed transverse relaxation time image
-  description: |
-    In seconds (s).
-    T2-star maps are REQUIRED to use this suffix regardless of the method used to
-    generate them.
-  unit: s
-T2starw:
-  value: T2starw
-  display_name: T2star weighted image
-  description: |
-    In arbitrary units (arbitrary).
-    The contrast of these images is mainly determined by spatial variations in
-    the (observed) transverse relaxation time of the imaged specimen.
-    In spin-echo sequences, this effect is negated as the excitation is followed
-    by an inversion pulse.
-    The contrast of gradient-echo images natively depends on T2-star effects.
-    However, for T2-star variation to dominate the image contrast,
-    gradient-echo acquisitions are carried out at long repetition and echo times,
-    and at small flip angles.
-  unit: arbitrary
-T2w:
-  value: T2w
-  display_name: T2-weighted image
-  description: |
-    In arbitrary units (arbitrary).
-    The contrast of these images is mainly determined by spatial variations in
-    the (true) transverse relaxation time of the imaged specimen.
-    In spin-echo sequences this contrast is achieved at relatively long
-    repetition and echo times.
-    Generally, gradient echo sequences are not the most suitable option for
-    achieving T2 weighting, as their contrast natively depends on T2-star rather
-    than on T2.
-  unit: arbitrary
-TB1AFI:
-  value: TB1AFI
-  display_name: TB1AFI
-  description: |
-    This method ([Yarnykh 2007](https://doi.org/10.1002/mrm.21120))
-    calculates a B1<sup>+</sup> map from two images acquired at interleaved (two)
-    TRs with identical RF pulses using a steady-state sequence.
-TB1DAM:
-  value: TB1DAM
-  display_name: TB1DAM
-  description: |
-    The double-angle B1<sup>+</sup> method
-    ([Insko and Bolinger 1993](https://doi.org/10.1006/jmra.1993.1133)) is based
-    on the calculation of the actual angles from signal ratios,
-    collected by two acquisitions at different nominal excitation flip angles.
-    Common sequence types for this application include spin echo and echo planar
-    imaging.
-TB1EPI:
-  value: TB1EPI
-  display_name: TB1EPI
-  description: |
-    This B1<sup>+</sup> mapping method
-    ([Jiru and Klose 2006](https://doi.org/10.1002/mrm.21083)) is based on two
-    EPI readouts to acquire spin echo (SE) and stimulated echo (STE) images at
-    multiple flip angles in one sequence, used in the calculation of deviations
-    from the nominal flip angle.
-TB1RFM:
-  value: TB1RFM
-  display_name: TB1RFM
-  description: |
-    The result of a Siemens `rf_map` product sequence.
-    This sequence produces two images.
-    The first image appears like an anatomical image and the second output is a
-    scaled flip angle map.
-TB1SRGE:
-  value: TB1SRGE
-  display_name: TB1SRGE
-  description: |
-    Saturation-prepared with 2 rapid gradient echoes (SA2RAGE) uses a ratio of
-    two saturation recovery images with different time delays,
-    and a simulated look-up table to estimate B1+
-    ([Eggenschwiler et al. 2011](https://doi.org/10.1002/mrm.23145)).
-    This sequence can also be used in conjunction with MP2RAGE T1 mapping to
-    iteratively improve B1+ and T1 map estimation
-    ([Marques & Gruetter 2013](https://doi.org/10.1371/journal.pone.0069294)).
-TB1TFL:
-  value: TB1TFL
-  display_name: TB1TFL
-  description: |
-    The result of a Siemens `tfl_b1_map` product sequence.
-    This sequence produces two images.
-    The first image appears like an anatomical image and the second output is a
-    scaled flip angle map.
-TB1map:
-  value: TB1map
-  display_name: RF transmit field image
-  description: |
-    In arbitrary units (arbitrary).
-    Radio frequency (RF) transmit (B1+) field maps are REQUIRED to use this
-    suffix regardless of the method used to generate them.
-    TB1map intensity values are RECOMMENDED to be represented as percent
-    multiplicative factors such that FlipAngle<sub>effective</sub> =
-    B1+<sub>intensity</sub>\*FlipAngle<sub>nominal</sub> .
-  unit: arbitrary
-TEM:
-  value: TEM
-  display_name: Transmission electron microscopy
-  description: |
-    Transmission electron microscopy imaging data
-UNIT1:
-  value: UNIT1
-  display_name: Homogeneous (flat) T1-weighted MP2RAGE image
-  description: |
-    In arbitrary units (arbitrary).
-    UNIT1 images are REQUIRED to use this suffix regardless of the method used to
-    generate them.
-    Note that although this image is T1-weighted, regions without MR signal will
-    contain white salt-and-pepper noise that most segmentation algorithms will
-    fail on.
-    Therefore, it is important to dissociate it from `T1w`.
-    Please see [`MP2RAGE` specific notes](/99-appendices/11-qmri.html#unit1-images)
-    in the qMRI appendix for further information.
-VFA:
-  value: VFA
-  display_name: Variable flip angle
-  description: |
-    The VFA method involves at least two spoiled gradient echo (SPGR) of
-    steady-state free precession (SSFP) images acquired at different flip angles.
-    Depending on the provided metadata fields and the sequence type,
-    data may be eligible for DESPOT1, DESPOT2 and their variants
-    ([Deoni et al. 2005](https://doi.org/10.1002/mrm.20314)).
-angio:
-  value: angio
-  display_name: Angiogram
-  description: |
-    Magnetic resonance angiography sequences focus on enhancing the contrast of
-    blood vessels (generally arteries, but sometimes veins) against other tissue
-    types.
-asl:
-  value: asl
-  display_name: Arterial Spin Labeling
-  description: |
-    The complete ASL time series stored as a 4D NIfTI file in the original
-    acquisition order, with possible volume types including: control, label,
-    m0scan, deltam, cbf.
-aslcontext:
-  value: aslcontext
-  display_name: Arterial Spin Labeling Context
-  description: |
-    A TSV file defining the image types for volumes in an associated ASL file.
-asllabeling:
-  value: asllabeling
-  display_name: ASL Labeling Screenshot
-  description: |
-    An anonymized screenshot of the planning of the labeling slab/plane with
-    respect to the imaging slab or slices `*_asllabeling.jpg`.
-    Based on DICOM macro C.8.13.5.14.
-beh:
-  value: beh
-  display_name: Behavioral recording
-  description: |
-    Behavioral recordings from tasks.
-    These files are similar to events files, but do not include the `"onset"` and
-    `"duration"` columns that are mandatory for events files.
-blood:
-  value: blood
-  display_name: Blood recording data
-  description: |
-    Blood measurements of radioactivity stored in
-    [tabular files](SPEC_ROOT/02-common-principles.md#tabular-files)
-    and located in the `pet/` directory along with the corresponding PET data.
-bold:
-  value: bold
-  display_name: Blood-Oxygen-Level Dependent image
-  description: |
-    Blood-Oxygen-Level Dependent contrast (specialized T2\* weighting)
-cbv:
-  value: cbv
-  display_name: Cerebral blood volume image
-  description: |
-    Cerebral Blood Volume contrast (specialized T2\* weighting or difference between T1 weighted images)
-channels:
-  value: channels
-  display_name: Channels File
-  description: |
-    Channel information.
-coordsystem:
-  value: coordsystem
-  display_name: Coordinate System File
-  description: |
-    A JSON document specifying the coordinate system(s) used for the MEG, EEG,
-    head localization coils, and anatomical landmarks.
-defacemask:
-  value: defacemask
-  display_name: Defacing Mask
-  description: |
-    A binary mask that was used to remove facial features from an anatomical MRI
-    image.
-dwi:
-  value: dwi
-  display_name: Diffusion-weighted image
-  description: |
-    Diffusion-weighted imaging contrast (specialized T2 weighting).
-eeg:
-  value: eeg
-  display_name: Electroencephalography
-  description: |
-    Electroencephalography recording data.
-electrodes:
-  value: electrodes
-  display_name: Electrodes
-  description: |
-    File that gives the location of (i)EEG electrodes.
-epi:
-  value: epi
-  display_name: EPI
-  description: |
-    The phase-encoding polarity (PEpolar) technique combines two or more Spin Echo
-    EPI scans with different phase encoding directions to estimate the underlying
-    inhomogeneity/deformation map.
-events:
-  value: events
-  display_name: Events
-  description: |
-    Event timing information from a behavioral task.
-fieldmap:
-  value: fieldmap
-  display_name: Fieldmap
-  description: |
-    Some MR schemes such as spiral-echo imaging (SEI) sequences are able to
-    directly provide maps of the *B<sub>0</sub>* field inhomogeneity.
-headshape:
-  value: headshape
-  display_name: Headshape File
-  description: |
-    The 3-D locations of points that describe the head shape and/or electrode
-    locations can be digitized and stored in separate files.
-ieeg:
-  value: ieeg
-  display_name: Intracranial Electroencephalography
-  description: |
-    Intracranial electroencephalography recording data.
-inplaneT1:
-  value: inplaneT1
-  display_name: Inplane T1
-  description: |
-    In arbitrary units (arbitrary).
-    T1 weighted structural image matched to a functional (task) image.
-  unit: arbitrary
-inplaneT2:
-  value: inplaneT2
-  display_name: Inplane T2
-  description: |
-    In arbitrary units (arbitrary).
-    T2 weighted structural image matched to a functional (task) image.
-  unit: arbitrary
-m0scan:
-  value: m0scan
-  display_name: M0 image
-  description: |
-    The M0 image is a calibration image, used to estimate the equilibrium
-    magnetization of blood.
-magnitude:
-  value: magnitude
-  display_name: Magnitude
-  description: |
-    Field-mapping MR schemes such as gradient-recalled echo (GRE) generate a
-    Magnitude image to be used for anatomical reference.
-    Requires the existence of Phase, Phase-difference or Fieldmap maps.
-magnitude1:
-  value: magnitude1
-  display_name: Magnitude
-  description: |
-    Magnitude map generated by GRE or similar schemes, associated with the first
-    echo in the sequence.
-magnitude2:
-  value: magnitude2
-  display_name: Magnitude
-  description: |
-    Magnitude map generated by GRE or similar schemes, associated with the second
-    echo in the sequence.
-markers:
-  value: markers
-  display_name: MEG Sensor Coil Positions
-  description: |
-    Another manufacturer-specific detail pertains to the KIT/Yokogawa/Ricoh
-    system, which saves the MEG sensor coil positions in a separate file with two
-    possible filename extensions  (`.sqd`, `.mrk`).
-    For these files, the `markers` suffix MUST be used.
-    For example: `sub-01_task-nback_markers.sqd`
-meg:
-  value: meg
-  display_name: Magnetoencephalography
-  description: |
-    Unprocessed MEG data stored in the native file format of the MEG instrument
-    with which the data was collected.
-pet:
-  value: pet
-  display_name: Positron Emission Tomography
-  description: |
-    PET imaging data SHOULD be stored in 4D
-    (or 3D, if only one volume was acquired) NIfTI files with the `_pet` suffix.
-    Volumes MUST be stored in chronological order
-    (the order they were acquired in).
-phase:
-  value: phase
-  display_name: Phase image
-  description: |
-    [DEPRECATED](SPEC_ROOT/02-common-principles.md#definitions).
-    Phase information associated with magnitude information stored in BOLD
-    contrast.
-    This suffix should be replaced by the
-    [`part-phase`](SPEC_ROOT/99-appendices/09-entities.md#part)
-    in conjunction with the `bold` suffix.
-  anyOf:
-  - unit: arbitrary
-  - unit: rad
-phase1:
-  value: phase1
-  display_name: Phase
-  description: |
-    Phase map generated by GRE or similar schemes, associated with the first
-    echo in the sequence.
-phase2:
-  value: phase2
-  display_name: Phase
-  description: |
-    Phase map generated by GRE or similar schemes, associated with the second
-    echo in the sequence.
-phasediff:
-  value: phasediff
-  display_name: Phase-difference
-  description: |
-    Some scanners subtract the `phase1` from the `phase2` map and generate a
-    unique `phasediff` file.
-    For instance, this is a common output for the built-in fieldmap sequence of
-    Siemens scanners.
-photo:
-  value: photo
-  display_name: Photo File
-  description: |
-    Photos of the anatomical landmarks, head localization coils or tissue sample.
-physio:
-  value: physio
-  display_name: Physiological recording
-  description: |
-    Physiological recordings such as cardiac and respiratory signals.
-sbref:
-  value: sbref
-  display_name: Single-band reference image
-  description: |
-    Single-band reference for one or more multi-band `dwi` images.
-scans:
-  value: scans
-  display_name: Scans file
-  description: |
-    The purpose of this file is to describe timing and other properties of each imaging acquisition
-    sequence (each run file) within one session.
-    Each neural recording file SHOULD be described by exactly one row. Some recordings consist of
-    multiple parts, that span several files, for example through echo-, part-, or split- entities.
-    Such recordings MUST be documented with one row per file.
-    Relative paths to files should be used under a compulsory filename header.
-    If acquisition time is included it should be listed under the acq_time header.
-    Acquisition time refers to when the first data point in each run was acquired.
-    Furthermore, if this header is provided, the acquisition times of all files that belong to a
-    recording MUST be identical.
-    Datetime should be expressed as described in Units.
-    Additional fields can include external behavioral measures relevant to the scan.
-    For example vigilance questionnaire score administered after a resting state scan.
-    All such included additional fields SHOULD be documented in an accompanying _scans.json file
-    that describes these fields in detail (see Tabular files).
-sessions:
-  value: sessions
-  display_name: Sessions file
-  description: |
-    In case of multiple sessions there is an option of adding additional sessions.tsv files
-    describing variables changing between sessions.
-    In such case one file per participant SHOULD be added.
-    These files MUST include a session_id column and describe each session by one and only one row.
-    Column names in sessions.tsv files MUST be different from group level participant key column
-    names in the participants.tsv file.
-stim:
-  value: stim
-  display_name: Continuous recording
-  description: |
-    Continuous measures, such as parameters of a film or audio stimulus.
-uCT:
-  value: uCT
-  display_name: Micro-CT
-  description: |
-    Micro-CT imaging data
diff --git a/dandi/support/bids/schemadata/1.7.0+369/objects/top_level_files.yaml b/dandi/support/bids/schemadata/1.7.0+369/objects/top_level_files.yaml
deleted file mode 100644
index 5583ddae4..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/objects/top_level_files.yaml
+++ /dev/null
@@ -1,128 +0,0 @@
----
-# This file describes files which may appear at the top level of a dataset.
-# This does not include information about whether these files are required or optional.
-# For that information, see `rules/top_level_files.yaml`.
-CHANGES:
-  name: CHANGES
-  display_name: Change log
-  description: |
-    Version history of the dataset (describing changes, updates and corrections) MAY be provided in
-    the form of a `CHANGES` text file.
-    This file MUST follow the
-    [CPAN Changelog convention](https://metacpan.org/pod/release/HAARG/CPAN-Changes-0.400002/lib/\
-    CPAN/Changes/Spec.pod).
-    The `CHANGES` file MUST be either in ASCII or UTF-8 encoding.
-LICENSE:
-  name: LICENSE
-  display_name: License
-  description: |
-    A `LICENSE` file MAY be provided in addition to the short specification of the
-    used license in the `dataset_description.json` `"License"` field.
-    The `"License"` field and `LICENSE` file MUST correspond.
-    The `LICENSE` file MUST be either in ASCII or UTF-8 encoding.
-README:
-  name: README
-  display_name: Readme
-  description: |
-    A REQUIRED text file, `README`, SHOULD describe the dataset in more detail.
-    The `README` file MUST be either in ASCII or UTF-8 encoding and MAY have one of the extensions:
-    `.md` ([Markdown](https://www.markdownguide.org/)),
-    `.rst` ([reStructuredText](https://docutils.sourceforge.io/rst.html)),
-    or `.txt`.
-    A BIDS dataset MUST NOT contain more than one `README` file (with or without extension)
-    at its root directory.
-    BIDS does not make any recommendations with regards to the
-    [Markdown flavor](https://www.markdownguide.org/extended-syntax/#lightweight-markup-languages)
-    and does not validate the syntax of Markdown and reStructuredText.
-    The `README` file SHOULD be structured such that its contents can be easily understood
-    even if the used format is not rendered.
-    A guideline for creating a good `README` file can be found in the
-    [bids-starter-kit](https://github.com/bids-standard/bids-starter-kit/blob/master/templates/README).
-dataset_description:
-  name: Dataset Description
-  display_name: Dataset Description
-  description: |
-    The file `dataset_description.json` is a JSON file describing the dataset.
-genetic_info:
-  name: Genetic Information
-  display_name: Genetic Information
-  description: |
-    The `genetic_info.json` file describes the genetic information available in the
-    `participants.tsv` file and/or the genetic database described in
-    `dataset_description.json`.
-    Datasets containing the `Genetics` field in `dataset_description.json` or the
-    `genetic_id` column in `participants.tsv` MUST include this file.
-participants:
-  name: Participant Information
-  display_name: Participant Information
-  description: |
-    The purpose of this RECOMMENDED file is to describe properties of participants
-    such as age, sex, handedness.
-    If this file exists, it MUST contain the column `participant_id`,
-    which MUST consist of `sub-<label>` values identifying one row for each participant,
-    followed by a list of optional columns describing participants.
-    Each participant MUST be described by one and only one row.
-
-    Commonly used *optional* columns in `participant.tsv` files are `age`, `sex`,
-    and `handedness`. We RECOMMEND to make use of these columns, and
-    in case that you do use them, we RECOMMEND to use the following values
-    for them:
-
-    -   `age`: numeric value in years (float or integer value)
-
-    -   `sex`: string value indicating phenotypical sex, one of "male", "female",
-        "other"
-
-        -   for "male", use one of these values: `male`, `m`, `M`, `MALE`, `Male`
-
-        -   for "female", use one of these values: `female`, `f`, `F`, `FEMALE`,
-            `Female`
-
-        -   for "other", use one of these values: `other`, `o`, `O`, `OTHER`,
-            `Other`
-
-    -   `handedness`: string value indicating one of "left", "right",
-        "ambidextrous"
-
-        -   for "left", use one of these values: `left`, `l`, `L`, `LEFT`, `Left`
-
-        -   for "right", use one of these values: `right`, `r`, `R`, `RIGHT`,
-            `Right`
-
-        -   for "ambidextrous", use one of these values: `ambidextrous`, `a`, `A`,
-            `AMBIDEXTROUS`, `Ambidextrous`
-
-    Throughout BIDS you can indicate missing values with `n/a` (for "not
-    available").
-
-samples:
-  name: Sample Information
-  display_name: Sample Information
-  description: |
-    The purpose of this file is to describe properties of samples, indicated by the `sample` entity.
-    This file is REQUIRED if `sample-<label>` is present in any file name within the dataset.
-    If this file exists, it MUST contain the three following columns:
-
-    -   `sample_id`: MUST consist of `sample-<label>` values identifying one row
-        for each sample
-
-    -   `participant_id`: MUST consist of `sub-<label>`
-
-    -   `sample_type`: MUST consist of sample type values, either `cell line`, `in vitro differentiated cells`,
-        `primary cell`, `cell-free sample`, `cloning host`, `tissue`, `whole organisms`, `organoid` or
-        `technical sample` from [ENCODE Biosample Type](https://www.encodeproject.org/profiles/biosample_type)
-
-    Other optional columns MAY be used to describe the samples.
-    Each sample MUST be described by one and only one row.
-
-    Commonly used *optional* columns in `samples.tsv` files are `pathology` and
-    `derived_from`. We RECOMMEND to make use of these columns, and in case that
-    you do use them, we RECOMMEND to use the following values for them:
-
-    -   `pathology`: string value describing the pathology of the sample or type of control.
-        When different from `healthy`, pathology SHOULD be specified in `samples.tsv`.
-        The pathology MAY instead be specified in
-        [Sessions files](../03-modality-agnostic-files.md#sessions-file) in case it changes over time.
-
-    -   `derived_from`: `sample-<label>` key/value pair from which a sample is derived from,
-        for example a slice of tissue (`sample-02`) derived from a block of tissue (`sample-01`)
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/associated_data.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/associated_data.yaml
deleted file mode 100644
index b855bf9a2..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/associated_data.yaml
+++ /dev/null
@@ -1,11 +0,0 @@
----
-# This file describes the requirement levels of directories which may appear
-# within a dataset directory without following BIDS format.
-code:
-  required: false
-derivatives:
-  required: false
-sourcedata:
-  required: false
-stimuli:
-  required: false
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/checks/asl.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/checks/asl.yaml
deleted file mode 100644
index 090f1a2a6..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/checks/asl.yaml
+++ /dev/null
@@ -1,279 +0,0 @@
-# Rules for ASL data that are not defined in tables.
----
-
-# 157
-ASLLabelingDurationNiftiLength:
-  issue:
-    code: LABELING_DURATION_LENGTH_NOT_MATCHING_NIFTI
-    message: |
-      The number of values for 'LabelingDuration' for this file does not match the 4th dimension
-      of the NIfTI header.
-      'LabelingDuration' is the total duration of the labeling pulse train, in seconds,
-      corresponding to the temporal width of the labeling bolus for `(P)CASL`.
-      In case all control-label volumes (or deltam or CBF) have the same `LabelingDuration`, a scalar must be
-      specified.
-      In case the control-label volumes (or deltam or cbf) have a different `LabelingDuration`,
-      an array of numbers must be specified, for which any `m0scan` in the timeseries has a `LabelingDuration` of
-      zero.
-      In case an array of numbers is provided, its length should be equal to the number of volumes specified in
-      `*_aslcontext.tsv`. Corresponds to DICOM Tag 0018,9258 `ASL Pulse Train Duration`.
-    level: error
-  selectors:
-  - suffix == "asl"
-  - '"LabelingDuration" in sidecar'
-  - type(sidecar.LabelingDuration) == 'array'
-  checks:
-  - nifti_header.dim[4] == sidecar.LabelingDuration.length
-
-# 165
-ASLContextConsistent:
-  issue:
-    code: ASLCONTEXT_TSV_NOT_CONSISTENT
-    message: |
-      The number of volumes in the '*_aslcontext.tsv' for this file does not match the number of
-      values in the NIfTI header.
-    level: error
-  selectors:
-  - suffix == "asl"
-  - '"aslcontext" in associations'
-  checks:
-  - nifti_header.dim[4] == associations.aslcontext.n_rows
-
-# 168
-ASLFlipAngleNiftiLength:
-  issue:
-    code: FLIP_ANGLE_NOT_MATCHING_NIFTI
-    message: |
-      The number of values for 'FlipAngle' for this file does not match the 4th dimension of the NIfTI header.
-      'FlipAngle' is the flip angle (FA) for the acquisition, specified in degrees.
-      Corresponds to: DICOM Tag 0018, 1314 `Flip Angle`.
-      The data type number may apply to files from any MRI modality concerned with a single value for this field,
-      or to the files in a file collection where the value of this field is iterated using the flip entity.
-      The data type array provides a value for each volume in a 4D dataset and should only be used when the
-      volume timing is critical for interpretation of the data, such as in ASL or variable flip
-      angle fMRI sequences.
-    level: error
-  selectors:
-  - suffix == "asl"
-  - '"FlipAngle" in sidecar'
-  - type(sidecar.FlipAngle) == 'array'
-  checks:
-  - nifti_header.dim[4] == sidecar.FlipAngle.length
-
-# 172
-ASLFlipAngleASLContextLength:
-  issue:
-    code: FLIP_ANGLE_NOT_MATCHING_ASLCONTEXT_TSV
-    message: |
-      The number of values for 'FlipAngle' for this file does not match the number of volumes in the
-      'sub-<label>[_ses-<label>][_acq-<label>][_rec-<label>][_run-<index>]_aslcontext.tsv'.
-      'FlipAngle' is the flip angle (FA) for the acquisition, specified in degrees.
-      Corresponds to: DICOM Tag 0018, 1314 `Flip Angle`.
-      The data type number may apply to files from any MRI modality concerned with a single value for this field,
-      or to the files in a file collection where the value of this field is iterated using the flip entity.
-      The data type array provides a value for each volume in a 4D dataset and should only be used when the volume
-      timing is critical for interpretation of the data, such as in ASL or variable flip angle fMRI sequences.
-    level: error
-  selectors:
-  - suffix == "asl"
-  - '"aslcontext" in associations'
-  - '"FlipAngle" in sidecar'
-  - type(sidecar.FlipAngle) == 'array'
-  checks:
-  - aslcontext.n_rows == sidecar.FlipAngle.length
-
-# 173
-ASLPostLabelingDelayNiftiLength:
-  issue:
-    code: POST_LABELING_DELAY_NOT_MATCHING_NIFTI
-    message: |
-      The number of values for 'PostLabelingDelay' for this file does not match the 4th dimension of the NIfTI
-      header.
-      'PostLabelingDelay' is the time, in seconds, after the end of the labeling (for (P)CASL) or middle of the
-      labeling pulse (for PASL) until the middle of the excitation pulse applied to the imaging slab
-      (for 3D acquisition) or first slice (for 2D acquisition).
-      Can be a number (for a single-PLD time series) or an array of numbers (for multi-PLD and Look-Locker).
-      In the latter case, the array of numbers contains the PLD of each volume
-      (that is, each 'control' and 'label')
-      in the acquisition order. Any image within the time-series without a PLD (for example, an 'm0scan') is
-      indicated by a zero.
-      Based on DICOM Tags 0018,9079 Inversion Times and 0018,0082 InversionTime.
-    level: error
-  selectors:
-  - suffix == "asl"
-  - '"aslcontext" in associations'
-  - type(sidecar.PostLabelingDelay) == 'array'
-  checks:
-  - nifti_header.pixdim[4] == sidecar.PostLabelingDelay.length
-
-# 174
-ASLPostLabelingDelayASLContextLength:
-  issue:
-    code: POST_LABELING_DELAY_NOT_MATCHING_ASLCONTEXT_TSV
-    message: |
-      The number of values for 'PostLabelingDelay' for this file does not match the number of volumes
-      in the 'sub-<label>[_ses-<label>][_acq-<label>][_rec-<label>][_run-<index>]_aslcontext.tsv'.
-      'PostLabelingDelay' is the time, in seconds, after the end of the labeling (for (P)CASL) or
-      middle of the labeling pulse (for PASL) until the middle of the excitation pulse applied to
-      the imaging slab (for 3D acquisition) or first slice (for 2D acquisition).
-      Can be a number (for a single-PLD time series) or an array of numbers (for multi-PLD and Look-Locker).
-      In the latter case, the array of numbers contains the PLD of each volume
-      (that is, each 'control' and 'label')
-      in the acquisition order.
-      Any image within the time-series without a PLD (for example, an 'm0scan') is indicated by a zero.
-      Based on DICOM Tags 0018,9079 Inversion Times and 0018,0082 InversionTime.
-    level: error
-  selectors:
-  - suffix == "asl"
-  - '"aslcontext" in associations'
-  - type(sidecar.PostLabelingDelay) == 'array'
-  checks:
-  - aslcontext.n_rows == sidecar.PostLabelingDelay.length
-
-# 175
-ASLLabelingDurationASLContextLength:
-  issue:
-    code: LABELLING_DURATION_NOT_MATCHING_ASLCONTEXT_TSV
-    message: |
-      The number of values for 'LabelingDuration' for this file does not match the number of volumes
-      in the 'sub-<label>[_ses-<label>][_acq-<label>][_rec-<label>][_run-<index>]_aslcontext.tsv'.
-      'LabelingDuration' is the total duration of the labeling pulse train, in seconds,
-      corresponding to the temporal width of the labeling bolus for `(P)CASL`.
-      In case all control-label volumes (or deltam or CBF) have the same `LabelingDuration`,
-      a scalar must be specified.
-      In case the control-label volumes (or deltam or cbf) have a different `LabelingDuration`,
-      an array of numbers must be specified, for which any `m0scan` in the timeseries has a
-      `LabelingDuration` of zero.
-      In case an array of numbers is provided, its length should be equal to the number of volumes
-      specified in `*_aslcontext.tsv`.
-      Corresponds to DICOM Tag 0018,9258 `ASL Pulse Train Duration`.
-    level: error
-  selectors:
-  - suffix == "asl"
-  - '"aslcontext" in associations'
-  - '"LabelingDuration" in sidecar'
-  - type(sidecar.LabelingDuration) == 'array'
-  checks:
-  - aslcontext.n_rows == sidecar.LabelingDuration.length
-
-# 177
-ASLRepetitionTimePreparationASLContextLength:
-  issue:
-    code: REPETITIONTIMEPREPARATION_NOT_MATCHING_ASLCONTEXT_TSV
-    message: |
-      The number of values of 'RepetitionTimePreparation' for this file does not match the number of
-      volumes in the 'sub-<label>[_ses-<label>][_acq-<label>][_rec-<label>][_run-<index>]_aslcontext.tsv'.
-      'RepetitionTimePreparation' is the interval, in seconds, that it takes a preparation pulse block to
-      re-appear at the beginning of the succeeding (essentially identical) pulse sequence block.
-      The data type number may apply to files from any MRI modality concerned with a single value for this field.
-      The data type array provides a value for each volume in a 4D dataset and should only be used when the
-      volume timing is critical for interpretation of the data, such as in ASL.
-    level: error
-  selectors:
-  - suffix == "asl"
-  - '"aslcontext" in associations'
-  - '"RepetitionTimePreparation" in sidecar'
-  - type(sidecar.RepetitionTimePreparation) == 'array'
-  checks:
-  - aslcontext.n_rows == sidecar.RepetitionTimePreparation.length
-
-# 180
-ASLBackgroundSuppressionNumberPulses:
-  issue:
-    code: BACKGROUND_SUPPRESSION_PULSE_NUMBER_NOT_CONSISTENT
-    message: |
-      The 'BackgroundSuppressionNumberPulses' field is not consistent with the length of
-      'BackgroundSuppressionPulseTime'.
-      'BackgroundSuppressionNumberPulses' is the number of background suppression pulses used.
-      Note that this excludes any effect of background suppression pulses applied before the labeling.
-    level: warning
-  selectors:
-  - suffix == "asl"
-  - '"BackgroundSuppressionNumberPulses" in sidecar'
-  - '"BackgroundSuppressionPulseTime" in sidecar'
-  - type(sidecar.BackgroundSuppressionPulseTime) == 'array'
-  checks:
-  - sidecar.BackgroundSuppressionPulseTime.length == sidecar.BackgroundSuppressionNumberPulses
-
-# 181
-ASLTotalAcquiredVolumesASLContextLength:
-  issue:
-    code: TOTAL_ACQUIRED_VOLUMES_NOT_CONSISTENT
-    message: |
-      The number of values for 'TotalAcquiredVolumes' for this file does not match number of
-      volumes in the 'sub-<label>[_ses-<label>][_acq-<label>][_rec-<label>][_run-<index>]_aslcontext.tsv'.
-      'TotalAcquiredVolumes' is the original number of 3D volumes acquired for each volume defined in the
-      'sub-<label>[_ses-<label>][_acq-<label>][_rec-<label>][_run-<index>]_aslcontext.tsv'.
-    level: warning
-  selectors:
-  - suffix == "asl"
-  - '"aslcontext" in associations'
-  - '"TotalAcquiredVolumes" in sidecar'
-  checks:
-  - aslcontext.n_rows == sidecar.TotalAcquiredVolumes
-
-# 196
-ASLEchoTimeASLContextLength:
-  issue:
-    code: ECHO_TIME_NOT_CONSISTENT
-    message: |
-      The number of values for 'EchoTime' for this file does not match number of volumes in the
-      'sub-<label>[_ses-<label>][_acq-<label>][_rec-<label>][_run-<index>]_aslcontext.tsv'.
-      'EchoTime' is the echo time (TE) for the acquisition, specified in seconds.
-    level: warning
-  selectors:
-  - suffix == "asl"
-  - '"aslcontext" in associations'
-  - '"EchoTime" in sidecar'
-  - type(sidecar.EchoTime) == 'array'
-  checks:
-  - aslcontext.n_rows == sidecar.EchoTime.length
-
-# 198
-ASLM0TypeAbsentScan:
-  issue:
-    code: M0Type_SET_INCORRECTLY_TO_ABSENT
-    message: |
-      You defined M0Type as 'absent' while including a separate '*_m0scan.nii[.gz]' and
-      '*_m0scan.json', or defining the 'M0Estimate' field.
-      This is not allowed, please check that this field are filled correctly.
-    level: error
-  selectors:
-  - suffix == "asl"
-  - '"aslcontext" in associations'
-  - '"m0scan" in associations'
-  - '"M0Type" in sidecar'
-  checks:
-  - sidecar.M0Type != "absent"
-
-# 199
-ASLM0TypeAbsentASLContext:
-  issue:
-    code: M0Type_SET_INCORRECTLY_TO_ABSENT_IN_ASLCONTEXT
-    message: |
-      You defined M0Type as 'absent' while including an m0scan volume within the '*_aslcontext.tsv'.
-      This is not allowed, please check that this field are filled correctly.
-    level: error
-  selectors:
-  - suffix == "asl"
-  - '"aslcontext" in associations'
-  - aslcontext.volume_type.includes('"m0scan")
-  - '"M0Type" in sidecar'
-  checks:
-  - sidecar.M0Type != "absent"
-
-# 202
-ASLM0TypeIncorrect:
-  issue:
-    code: M0Type_SET_INCORRECTLY
-    message: |
-      M0Type was not defined correctly.
-      If 'M0Type' is equal to 'separate', the dataset should include a *_m0scan.nii[.gz] and *_m0scan.json file.
-    level: error
-  selectors:
-  - suffix == "asl"
-  - '"aslcontext" in associations'
-  - '"M0Type" in sidecar'
-  - sidecar.M0Type == "separate"
-  checks:
-  - '"m0scan" in associations'
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/checks/dwi.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/checks/dwi.yaml
deleted file mode 100644
index 6cc157290..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/checks/dwi.yaml
+++ /dev/null
@@ -1,61 +0,0 @@
-# Rules for DWI data that are not defined in tables.
----
-
-# 29
-DWIVolumeCount:
-  code: VOLUME_COUNT_MISMATCH
-  description: |
-    The number of volumes in this scan does not match the number of volumes in the
-    corresponding .bvec and .bval files.
-  level: error
-  selectors:
-  - suffix == "dwi"
-  - '"bval" in associations'
-  - '"bvec" in associations'
-  checks:
-  - associations.bval.n_cols == nifti_header.dim[4]
-  - associations.bvec.n_cols == nifti_header.dim[4]
-
-# 30
-DWIBvalRows:
-  code: BVAL_MULTIPLE_ROWS
-  description: |
-    '.bval' files should contain exactly one row of volumes.
-  level: error
-  selectors:
-  - extension == "bval"
-  checks:
-  - data.n_rows == 1
-
-# 31
-DWIBvecRows:
-  code: BVEC_NUMBER_ROWS
-  description: |
-    '.bvec' files should contain exactly three rows of volumes.
-  level: error
-  selectors:
-  - extension == "bvec"
-  checks:
-  - data.n_rows == 3
-
-# 32
-DWIMissingBvec:
-  code: DWI_MISSING_BVEC
-  description: |
-    DWI scans must have a corresponding .bvec file.
-  level: error
-  selectors:
-  - suffix == "dwi"
-  checks:
-  - '"bvec" in associations'
-
-# 33
-DWIMissingBval:
-  code: DWI_MISSING_BVAL
-  description: |
-    DWI scans must have a corresponding .bval file.
-  level: error
-  selectors:
-  - suffix == "dwi"
-  checks:
-  - '"bval" in associations'
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/checks/events.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/checks/events.yaml
deleted file mode 100644
index f6ffd882d..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/checks/events.yaml
+++ /dev/null
@@ -1,16 +0,0 @@
-# Rules for events data that are not defined in tables.
----
-
-# 25
-EventsMissing:
-  issue:
-    code: EVENTS_TSV_MISSING
-    message: |
-      Task scans should have a corresponding events.tsv file.
-      If this is a resting state scan you can ignore this warning or rename the task to include the word "rest".
-    level: warning  # could be an error with the proper selectors, I think
-  selectors:
-  - '"task" in entities'
-  - '!(entities.task.includes("rest"))'
-  checks:
-  - '"events" in associations'
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/checks/fmap.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/checks/fmap.yaml
deleted file mode 100644
index 048765ac7..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/checks/fmap.yaml
+++ /dev/null
@@ -1,26 +0,0 @@
-# Rules for fieldmap data that are not defined in tables.
----
-
-# 91
-FmapFieldmapWithoutMagnitude:
-  issue:
-    code: _FIELDMAP_WITHOUT_MAGNITUDE_FILE
-    message: |
-      '_fieldmap.nii[.gz]' file does not have accompanying '_magnitude.nii[.gz]' file.
-    level: error
-  selectors:
-  - suffix == "fieldmap"
-  checks:
-  - '"magnitude" in associations'
-
-# 92
-FmapPhasediffWithoutMagnitude:
-  issue:
-    code: MISSING_MAGNITUDE1_FILE
-    message: |
-      Each '_phasediff.nii[.gz]' file should be associations with a '_magnitude1.nii[.gz]' file.
-    level: warning
-  selectors:
-  - suffix == "phasediff"
-  checks:
-  - '"magnitude1" in associations'
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/checks/func.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/checks/func.yaml
deleted file mode 100644
index d46d22ff1..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/checks/func.yaml
+++ /dev/null
@@ -1,16 +0,0 @@
-# Rules for functional data that are not defined in tables.
----
-PhaseSuffixDeprecated:
-  issue:
-    code: PHASE_SUFFIX_DEPRECATED
-    message: |
-      DEPRECATED. Phase information associated with magnitude information stored in BOLD contrast.
-      This suffix should be replaced by the part-phase in conjunction with the bold suffix.
-      For backwards compatibility, _phase is considered equivalent to _part-phase_bold.
-      When the _phase suffix is not used, each file shares the same name with the exception of the
-      part-<mag|phase> or part-<real|imag> key/value.
-    level: warning
-  selectors:
-  - datatype == "func"
-  checks:
-  - '!(suffix == "phase")'
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/common_derivatives_validation.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/common_derivatives_validation.yaml
deleted file mode 100644
index 0c2755e3e..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/common_derivatives_validation.yaml
+++ /dev/null
@@ -1,18 +0,0 @@
----
-ResInSidecar:
-    selectors:
-    - dataset.dataset_description.DatasetType == "derivative"
-    - '["mri", "pet"].includes(modality)'
-    - '["nii", " nii.gz"].includes(extension)'
-    - type(sidecar.Resolution) == "object"
-    checks:
-    - entities.resolution in sidecar.Resolution
-
-DenInSidecar:
-    selectors:
-    - dataset.dataset_description.DatasetType == "derivative"
-    - '["mri", "pet"].includes(modality)'
-    - '[".nii", ".nii.gz"].includes(extension)'
-    - type(sidecar.Density) == "object"
-    checks:
-    - entities.density in sidecar.Density
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/dataset_metadata.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/dataset_metadata.yaml
deleted file mode 100644
index c1b086527..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/dataset_metadata.yaml
+++ /dev/null
@@ -1,67 +0,0 @@
----
-dataset_description:
-  selectors:
-  - path == "/dataset_description.json"
-  fields:
-    Name: REQUIRED
-    BIDSVersion: REQUIRED
-    DatasetType: RECOMMENDED
-    License: RECOMMENDED
-    Authors:
-      level: RECOMMENDED
-      issue:
-        code: NO_AUTHORS
-        message: |
-          The Authors field of dataset_description.json should contain an array of fields -
-          with one author per field. This was triggered because there are no authors, which
-          will make DOI registration from dataset metadata impossible.
-    Acknowledgements: OPTIONAL
-    HowToAcknowledge: OPTIONAL
-    Funding: OPTIONAL
-    EthicsApprovals: OPTIONAL
-    ReferencesAndLinks: OPTIONAL
-    DatasetDOI: OPTIONAL
-    GeneratedBy: RECOMMENDED
-    GeneratedBy[].Name: REQUIRED
-    GeneratedBy[].Version: RECOMMENDED
-    GeneratedBy[].Description: OPTIONAL
-    GeneratedBy[].CodeURL: OPTIONAL
-    GeneratedBy[].Container: OPTIONAL
-    GeneratedBy[].Container{}.Type: RECOMMENDED
-    GeneratedBy[].Container{}.Tag: RECOMMENDED
-    GeneratedBy[].Container{}.URI: RECOMMENDED
-    SourceDatasets: RECOMMENDED
-
-derivative_description:
-  selectors:
-  - path == "/dataset_description.json"
-  - json.DatasetType == "derivative"
-  fields:
-    GeneratedBy: REQUIRED
-
-dataset_description_with_genetics:
-  selectors:
-  - path == "/dataset_description.json"
-  - 'dataset.files.includes("/genetic_info.json")'
-  fields:
-    Genetics: REQUIRED
-    Genetics{}.Dataset:
-      level: REQUIRED
-      issue:
-        code: NO_GENETIC_DATABASE
-        message: |
-          A genetic_info.json file is present but no Database field present in Genetics
-          object in dataset_description.json.
-    Genetics{}.Database: OPTIONAL
-    Genetics{}.Descriptors: OPTIONAL
-
-genetic_info:
-  selectors:
-  - path == "/genetic_info.json"
-  fields:
-    GeneticLevel: REQUIRED
-    SampleOrigin: REQUIRED
-    AnalyticalApproach: OPTIONAL
-    TissueOrigin: OPTIONAL
-    BrainLocation: OPTIONAL
-    CellType: OPTIONAL
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/anat.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/anat.yaml
deleted file mode 100644
index 7e0f04d6c..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/anat.yaml
+++ /dev/null
@@ -1,201 +0,0 @@
----
-nonparametric:
-  suffixes:
-  - T1w
-  - T2w
-  - PDw
-  - T2starw
-  - FLAIR
-  - inplaneT1
-  - inplaneT2
-  - PDT2
-  - angio
-  - T2star  # deprecated
-  - FLASH  # deprecated
-  - PD  # deprecated
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  datatypes:
-  - anat
-  entities:
-    subject: required
-    session: optional
-    run: optional
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    part: optional
-
-parametric:
-  suffixes:
-  - T1map
-  - T2map
-  - T2starmap
-  - R1map
-  - R2map
-  - R2starmap
-  - PDmap
-  - MTRmap
-  - MTsat
-  - UNIT1
-  - T1rho
-  - MWFmap
-  - MTVmap
-  - PDT2map
-  - Chimap
-  - S0map
-  - M0map
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  datatypes:
-  - anat
-  entities:
-    subject: required
-    session: optional
-    run: optional
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-
-defacemask:
-  suffixes:
-  - defacemask
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  datatypes:
-  - anat
-  entities:
-    subject: required
-    session: optional
-    run: optional
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    modality: optional
-
-multiecho:
-  suffixes:
-  - MESE
-  - MEGRE
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  datatypes:
-  - anat
-  entities:
-    subject: required
-    session: optional
-    run: optional
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    echo: required
-    part: optional
-
-multiflip:
-  suffixes:
-  - VFA
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  datatypes:
-  - anat
-  entities:
-    subject: required
-    session: optional
-    run: optional
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    echo: optional
-    flip: required
-    part: optional
-
-multiinversion:
-  suffixes:
-  - IRT1
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  datatypes:
-  - anat
-  entities:
-    subject: required
-    session: optional
-    run: optional
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    inversion: required
-    part: optional
-
-mp2rage:
-  suffixes:
-  - MP2RAGE
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  datatypes:
-  - anat
-  entities:
-    subject: required
-    session: optional
-    run: optional
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    echo: optional
-    flip: optional
-    inversion: required
-    part: optional
-
-vfamt:
-  suffixes:
-  - MPM
-  - MTS
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  datatypes:
-  - anat
-  entities:
-    subject: required
-    session: optional
-    run: optional
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    echo: optional
-    flip: required
-    mtransfer: required
-    part: optional
-
-mtr:
-  suffixes:
-  - MTR
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  datatypes:
-  - anat
-  entities:
-    subject: required
-    session: optional
-    run: optional
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    mtransfer: required
-    part: optional
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/beh.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/beh.yaml
deleted file mode 100644
index 1f3111799..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/beh.yaml
+++ /dev/null
@@ -1,34 +0,0 @@
----
-timeseries:
-  suffixes:
-  - stim
-  - physio
-  extensions:
-  - .tsv.gz
-  - .json
-  datatypes:
-  - beh
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    run: optional
-    recording: optional
-
-# Non-continuous data
-noncontinuous:
-  suffixes:
-  - events
-  - beh
-  extensions:
-  - .tsv
-  - .json
-  datatypes:
-  - beh
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    run: optional
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/derivatives/common_derivatives.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/derivatives/common_derivatives.yaml
deleted file mode 100644
index adddf62f3..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/derivatives/common_derivatives.yaml
+++ /dev/null
@@ -1,413 +0,0 @@
----
-anat_nonparametric_common:
-  $ref: rules.datatypes.anat.nonparametric
-  entities:
-    $ref: rules.datatypes.anat.nonparametric.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-anat_parametric_common:
-  $ref: rules.datatypes.anat.parametric
-  entities:
-    $ref: rules.datatypes.anat.parametric.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-anat_defacemask_common:
-  $ref: rules.datatypes.anat.defacemask
-  entities:
-    $ref: rules.datatypes.anat.defacemask.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-anat_multiecho_common:
-  $ref: rules.datatypes.anat.multiecho
-  entities:
-    $ref: rules.datatypes.anat.multiecho.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-anat_multiflip_common:
-  $ref: rules.datatypes.anat.multiflip
-  entities:
-    $ref: rules.datatypes.anat.multiflip.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-anat_multiinversion_common:
-  $ref: rules.datatypes.anat.multiinversion
-  entities:
-    $ref: rules.datatypes.anat.multiinversion.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-anat_mp2rage_common:
-  $ref: rules.datatypes.anat.mp2rage
-  entities:
-    $ref: rules.datatypes.anat.mp2rage.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-anat_vfamt_common:
-  $ref: rules.datatypes.anat.vfamt
-  entities:
-    $ref: rules.datatypes.anat.vfamt.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-anat_mtr_common:
-  $ref: rules.datatypes.anat.mtr
-  entities:
-    $ref: rules.datatypes.anat.mtr.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-beh_timeseries_common:
-  $ref: rules.datatypes.beh.timeseries
-  entities:
-    $ref: rules.datatypes.beh.timeseries.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-beh_noncontinuous_common:
-  $ref: rules.datatypes.beh.noncontinuous
-  entities:
-    $ref: rules.datatypes.beh.noncontinuous.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-dwi_dwi_common:
-  $ref: rules.datatypes.dwi.dwi
-  entities:
-    $ref: rules.datatypes.dwi.dwi.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-dwi_sbref_common:
-  $ref: rules.datatypes.dwi.sbref
-  entities:
-    $ref: rules.datatypes.dwi.sbref.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-dwi_timeseries_common:
-  $ref: rules.datatypes.dwi.timeseries
-  entities:
-    $ref: rules.datatypes.dwi.timeseries.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-eeg_eeg_common:
-  $ref: rules.datatypes.eeg.eeg
-  entities:
-    $ref: rules.datatypes.eeg.eeg.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-eeg_channels_common:
-  $ref: rules.datatypes.eeg.channels
-  entities:
-    $ref: rules.datatypes.eeg.channels.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-eeg_coordsystem_common:
-  $ref: rules.datatypes.eeg.coordsystem
-  entities:
-    $ref: rules.datatypes.eeg.coordsystem.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-eeg_electrodes_common:
-  $ref: rules.datatypes.eeg.electrodes
-  entities:
-    $ref: rules.datatypes.eeg.electrodes.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-eeg_events_common:
-  $ref: rules.datatypes.eeg.events
-  entities:
-    $ref: rules.datatypes.eeg.events.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-eeg_photo_common:
-  $ref: rules.datatypes.eeg.photo
-  entities:
-    $ref: rules.datatypes.eeg.photo.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-eeg_timeseries_common:
-  $ref: rules.datatypes.eeg.timeseries
-  entities:
-    $ref: rules.datatypes.eeg.timeseries.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-fmap_fieldmaps_common:
-  $ref: rules.datatypes.fmap.fieldmaps
-  entities:
-    $ref: rules.datatypes.fmap.fieldmaps.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-fmap_pepolar_common:
-  $ref: rules.datatypes.fmap.pepolar
-  entities:
-    $ref: rules.datatypes.fmap.pepolar.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-fmap_TB1DAM_common:
-  $ref: rules.datatypes.fmap.TB1DAM
-  entities:
-    $ref: rules.datatypes.fmap.TB1DAM.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-fmap_TB1EPI_common:
-  $ref: rules.datatypes.fmap.TB1EPI
-  entities:
-    $ref: rules.datatypes.fmap.TB1EPI.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-fmap_RFFieldMaps_common:
-  $ref: rules.datatypes.fmap.RFFieldMaps
-  entities:
-    $ref: rules.datatypes.fmap.RFFieldMaps.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-fmap_TB1SRGE_common:
-  $ref: rules.datatypes.fmap.TB1SRGE
-  entities:
-    $ref: rules.datatypes.fmap.TB1SRGE.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-fmap_parametric_common:
-  $ref: rules.datatypes.fmap.parametric
-  entities:
-    $ref: rules.datatypes.fmap.parametric.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-func_func_common:
-  $ref: rules.datatypes.func.func
-  entities:
-    $ref: rules.datatypes.func.func.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-func_phase_common:
-  $ref: rules.datatypes.func.phase
-  entities:
-    $ref: rules.datatypes.func.phase.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-func_events_common:
-  $ref: rules.datatypes.func.events
-  entities:
-    $ref: rules.datatypes.func.events.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-func_timeseries_common:
-  $ref: rules.datatypes.func.timeseries
-  entities:
-    $ref: rules.datatypes.func.timeseries.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-ieeg_ieeg_common:
-  $ref: rules.datatypes.ieeg.ieeg
-  entities:
-    $ref: rules.datatypes.ieeg.ieeg.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-ieeg_channels_common:
-  $ref: rules.datatypes.ieeg.channels
-  entities:
-    $ref: rules.datatypes.ieeg.channels.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-ieeg_coordsystem_common:
-  $ref: rules.datatypes.ieeg.coordsystem
-  entities:
-    $ref: rules.datatypes.ieeg.coordsystem.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-ieeg_electrodes_common:
-  $ref: rules.datatypes.ieeg.electrodes
-  entities:
-    $ref: rules.datatypes.ieeg.electrodes.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-ieeg_events_common:
-  $ref: rules.datatypes.ieeg.events
-  entities:
-    $ref: rules.datatypes.ieeg.events.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-ieeg_photo_common:
-  $ref: rules.datatypes.ieeg.photo
-  entities:
-    $ref: rules.datatypes.ieeg.photo.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-ieeg_timeseries_common:
-  $ref: rules.datatypes.ieeg.timeseries
-  entities:
-    $ref: rules.datatypes.ieeg.timeseries.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-meg_meg_common:
-  $ref: rules.datatypes.meg.meg
-  entities:
-    $ref: rules.datatypes.meg.meg.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-meg_calibration_common:
-  $ref: rules.datatypes.meg.calibration
-  entities:
-    $ref: rules.datatypes.meg.calibration.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-meg_crosstalk_common:
-  $ref: rules.datatypes.meg.crosstalk
-  entities:
-    $ref: rules.datatypes.meg.crosstalk.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-meg_headshape_common:
-  $ref: rules.datatypes.meg.headshape
-  entities:
-    $ref: rules.datatypes.meg.headshape.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-meg_markers_common:
-  $ref: rules.datatypes.meg.markers
-  entities:
-    $ref: rules.datatypes.meg.markers.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-meg_coordsystem_common:
-  $ref: rules.datatypes.meg.coordsystem
-  entities:
-    $ref: rules.datatypes.meg.coordsystem.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-meg_channels_common:
-  $ref: rules.datatypes.meg.channels
-  entities:
-    $ref: rules.datatypes.meg.channels.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-meg_events_common:
-  $ref: rules.datatypes.meg.events
-  entities:
-    $ref: rules.datatypes.meg.events.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-meg_photo_common:
-  $ref: rules.datatypes.meg.photo
-  entities:
-    $ref: rules.datatypes.meg.photo.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-meg_timeseries_common:
-  $ref: rules.datatypes.meg.timeseries
-  entities:
-    $ref: rules.datatypes.meg.timeseries.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-micr_microscopy_common:
-  $ref: rules.datatypes.micr.microscopy
-  entities:
-    $ref: rules.datatypes.micr.microscopy.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-micr_photo_common:
-  $ref: rules.datatypes.micr.photo
-  entities:
-    $ref: rules.datatypes.micr.photo.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-perf_asl_common:
-  $ref: rules.datatypes.perf.asl
-  entities:
-    $ref: rules.datatypes.perf.asl.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-perf_aslcontext_common:
-  $ref: rules.datatypes.perf.aslcontext
-  entities:
-    $ref: rules.datatypes.perf.aslcontext.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-perf_asllabeling_common:
-  $ref: rules.datatypes.perf.asllabeling
-  entities:
-    $ref: rules.datatypes.perf.asllabeling.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-perf_timeseries_common:
-  $ref: rules.datatypes.perf.timeseries
-  entities:
-    $ref: rules.datatypes.perf.timeseries.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-pet_pet_common:
-  $ref: rules.datatypes.pet.pet
-  entities:
-    $ref: rules.datatypes.pet.pet.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-pet_blood_common:
-  $ref: rules.datatypes.pet.blood
-  entities:
-    $ref: rules.datatypes.pet.blood.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-pet_events_common:
-  $ref: rules.datatypes.pet.events
-  entities:
-    $ref: rules.datatypes.pet.events.entities
-    space: OPTIONAL
-    desc: OPTIONAL
-
-pet_timeseries_common:
-  $ref: rules.datatypes.pet.timeseries
-  entities:
-    $ref: rules.datatypes.pet.timeseries.entities
-    space: OPTIONAL
-    desc: OPTIONAL
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/derivatives/common_imaging_derivatives.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/derivatives/common_imaging_derivatives.yaml
deleted file mode 100644
index b41a43808..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/derivatives/common_imaging_derivatives.yaml
+++ /dev/null
@@ -1,220 +0,0 @@
----
-anat_parametric_volumetric:
-  $ref: rules.datatypes.anat.parametric
-  entities:
-    $ref: rules.datatypes.anat.parametric.entities
-    space: OPTIONAL
-    resolution: OPTIONAL
-    density: OPTIONAL
-    desc: OPTIONAL
-
-anat_nonparametric_volumetric:
-  $ref: rules.datatypes.anat.nonparametric
-  entities:
-    $ref: rules.datatypes.anat.nonparametric.entities
-    space: OPTIONAL
-    resolution: OPTIONAL
-    density: OPTIONAL
-    desc: OPTIONAL
-
-dwi_volumetric:
-  $ref: rules.datatypes.dwi.dwi
-  entities:
-    $ref: rules.datatypes.dwi.dwi.entities
-    space: OPTIONAL
-    resolution: OPTIONAL
-    density: OPTIONAL
-    desc: OPTIONAL
-
-func_volumetric:
-  $ref: rules.datatypes.func.func
-  entities:
-    $ref: rules.datatypes.func.func.entities
-    space: OPTIONAL
-    resolution: OPTIONAL
-    density: OPTIONAL
-    desc: OPTIONAL
-
-anat_parametric_mask:
-  $ref: rules.datatypes.anat.parametric
-  suffixes:
-  - mask
-  extensions:
-  - .nii.gz
-  entities:
-    $ref: rules.datatypes.anat.parametric.entities
-    space: OPTIONAL
-    resolution: OPTIONAL
-    density: OPTIONAL
-    label: OPTIONAL
-    desc: OPTIONAL
-
-anat_nonparametric_mask:
-  $ref: rules.datatypes.anat.nonparametric
-  suffixes:
-  - mask
-  extensions:
-  - .nii.gz
-  entities:
-    $ref: rules.datatypes.anat.nonparametric.entities
-    space: OPTIONAL
-    resolution: OPTIONAL
-    density: OPTIONAL
-    label: OPTIONAL
-    desc: OPTIONAL
-
-dwi_mask:
-  $ref: rules.datatypes.dwi.dwi
-  suffixes:
-  - mask
-  extensions:
-  - .nii.gz
-  entities:
-    $ref: rules.datatypes.dwi.dwi.entities
-    space: OPTIONAL
-    resolution: OPTIONAL
-    density: OPTIONAL
-    label: OPTIONAL
-    desc: OPTIONAL
-
-func_mask:
-  $ref: rules.datatypes.func.func
-  suffixes:
-  - mask
-  extensions:
-  - .nii.gz
-  entities:
-    $ref: rules.datatypes.func.func.entities
-    space: OPTIONAL
-    resolution: OPTIONAL
-    density: OPTIONAL
-    label: OPTIONAL
-    desc: OPTIONAL
-
-anat_parametric_discrete_segmentation:
-  $ref: rules.datatypes.anat.parametric
-  suffixes:
-  - dseg
-  extensions:
-  - .nii.gz
-  entities:
-    $ref: rules.datatypes.anat.parametric.entities
-    space: OPTIONAL
-    resolution: OPTIONAL
-    density: OPTIONAL
-
-anat_nonparametric_discrete_segmentation:
-  $ref: rules.datatypes.anat.nonparametric
-  suffixes:
-  - dseg
-  extensions:
-  - .nii.gz
-  entities:
-    $ref: rules.datatypes.anat.nonparametric.entities
-    space: OPTIONAL
-    resolution: OPTIONAL
-    density: OPTIONAL
-
-func_discrete_segmentation:
-  $ref: rules.datatypes.func.func
-  suffixes:
-  - dseg
-  extensions:
-  - .nii.gz
-  entities:
-    $ref: rules.datatypes.func.func.entities
-    space: OPTIONAL
-    resolution: OPTIONAL
-    density: OPTIONAL
-
-dwi_discrete_segmentation:
-  $ref: rules.datatypes.dwi.dwi
-  suffixes:
-  - dseg
-  extensions:
-  - .nii.gz
-  entities:
-    $ref: rules.datatypes.dwi.dwi.entities
-    space: OPTIONAL
-    resolution: OPTIONAL
-    density: OPTIONAL
-
-anat_parametric_probabilistic_segmentation:
-  $ref: rules.datatypes.anat.parametric
-  suffixes:
-  - probseg
-  extensions:
-  - .nii.gz
-  entities:
-    $ref: rules.datatypes.anat.parametric.entities
-    space: OPTIONAL
-    resolution: OPTIONAL
-    density: OPTIONAL
-    label: OPTIONAL
-
-anat_nonparametric_probabilistic_segmentation:
-  $ref: rules.datatypes.anat.nonparametric
-  suffixes:
-  - probseg
-  extensions:
-  - .nii.gz
-  entities:
-    $ref: rules.datatypes.anat.nonparametric.entities
-    space: OPTIONAL
-    resolution: OPTIONAL
-    density: OPTIONAL
-    label: OPTIONAL
-
-func_probabilistic_segmentation:
-  $ref: rules.datatypes.func.func
-  suffixes:
-  - probseg
-  extensions:
-  - .nii.gz
-  entities:
-    $ref: rules.datatypes.func.func.entities
-    space: OPTIONAL
-    resolution: OPTIONAL
-    density: OPTIONAL
-    label: OPTIONAL
-
-dwi_probabilistic_segmentation:
-  $ref: rules.datatypes.dwi.dwi
-  suffixes:
-  - probseg
-  extensions:
-  - .nii.gz
-  entities:
-    $ref: rules.datatypes.dwi.dwi.entities
-    space: OPTIONAL
-    resolution: OPTIONAL
-    density: OPTIONAL
-    label: OPTIONAL
-
-anat_parametic_discrete_surface:
-  $ref: rules.datatypes.anat.parametric
-  suffixes:
-  - dseg
-  extensions:
-  - .label.gii
-  - .dlabel.nii
-  entities:
-    $ref: rules.datatypes.anat.parametric.entities
-    hemisphere:: OPTIONAL
-    space: OPTIONAL
-    resolution: OPTIONAL
-    density: OPTIONAL
-
-anat_nonparametic_discrete_surface:
-  $ref: rules.datatypes.anat.nonparametric
-  suffixes:
-  - dseg
-  extensions:
-  - .label.gii
-  - .dlabel.nii
-  entities:
-    $ref: rules.datatypes.anat.nonparametric.entities
-    hemisphere:: OPTIONAL
-    space: OPTIONAL
-    resolution: OPTIONAL
-    density: OPTIONAL
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/dwi.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/dwi.yaml
deleted file mode 100644
index 48c0caf29..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/dwi.yaml
+++ /dev/null
@@ -1,57 +0,0 @@
----
-dwi:
-  suffixes:
-  - dwi
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  - .bvec
-  - .bval
-  datatypes:
-  - dwi
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-    reconstruction: optional
-    direction: optional
-    run: optional
-    part: optional
-
-sbref:
-  suffixes:
-  - sbref
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  datatypes:
-  - dwi
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-    reconstruction: optional
-    direction: optional
-    run: optional
-    part: optional
-
-timeseries:
-  suffixes:
-  - physio
-  - stim
-  extensions:
-  - .tsv.gz
-  - .json
-  datatypes:
-  - dwi
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-    reconstruction: optional
-    direction: optional
-    run: optional
-    part: optional
-    recording: optional
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/eeg.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/eeg.yaml
deleted file mode 100644
index 96a57783b..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/eeg.yaml
+++ /dev/null
@@ -1,109 +0,0 @@
----
-eeg:
-  suffixes:
-  - eeg
-  extensions:
-  - .json
-  - .edf
-  - .vhdr
-  - .vmrk
-  - .eeg
-  - .set
-  - .fdt
-  - .bdf
-  datatypes:
-  - eeg
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    run: optional
-
-channels:
-  suffixes:
-  - channels
-  extensions:
-  - .json
-  - .tsv
-  datatypes:
-  - eeg
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    run: optional
-
-coordsystem:
-  suffixes:
-  - coordsystem
-  extensions:
-  - .json
-  datatypes:
-  - eeg
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-    space: optional
-
-electrodes:
-  suffixes:
-  - electrodes
-  extensions:
-  - .json
-  - .tsv
-  datatypes:
-  - eeg
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-    space: optional
-
-events:
-  suffixes:
-  - events
-  extensions:
-  - .json
-  - .tsv
-  datatypes:
-  - eeg
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    run: optional
-
-photo:
-  suffixes:
-  - photo
-  extensions:
-  - .jpg
-  - .png
-  - .tif
-  datatypes:
-  - eeg
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-
-timeseries:
-  suffixes:
-  - physio
-  - stim
-  extensions:
-  - .tsv.gz
-  - .json
-  datatypes:
-  - eeg
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    run: optional
-    recording: optional
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/fmap.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/fmap.yaml
deleted file mode 100644
index cda02c410..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/fmap.yaml
+++ /dev/null
@@ -1,143 +0,0 @@
----
-fieldmaps:
-  suffixes:
-  - phasediff
-  - phase1
-  - phase2
-  - magnitude1
-  - magnitude2
-  - magnitude
-  - fieldmap
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  datatypes:
-  - fmap
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-    run: optional
-
-pepolar:
-  suffixes:
-  - epi
-  - m0scan
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  datatypes:
-  - fmap
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-    ceagent: optional
-    direction: required
-    run: optional
-
-TB1DAM:
-  suffixes:
-  - TB1DAM
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  datatypes:
-  - fmap
-  entities:
-    subject: required
-    session: optional
-    run: optional
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    flip: required
-    inversion: optional
-    part: optional
-
-TB1EPI:
-  suffixes:
-  - TB1EPI
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  datatypes:
-  - fmap
-  entities:
-    subject: required
-    session: optional
-    run: optional
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    echo: required
-    flip: required
-    inversion: optional
-    part: optional
-
-RFFieldMaps:
-  suffixes:
-  - TB1AFI
-  - TB1TFL
-  - TB1RFM
-  - RB1COR
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  datatypes:
-  - fmap
-  entities:
-    subject: required
-    session: optional
-    run: optional
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    echo: optional
-    flip: optional
-    inversion: optional
-    part: optional
-
-TB1SRGE:
-  suffixes:
-  - TB1SRGE
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  datatypes:
-  - fmap
-  entities:
-    subject: required
-    session: optional
-    run: optional
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    echo: optional
-    flip: required
-    inversion: required
-    part: optional
-
-parametric:
-  suffixes:
-  - TB1map
-  - RB1map
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  datatypes:
-  - fmap
-  entities:
-    subject: required
-    session: optional
-    run: optional
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/func.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/func.yaml
deleted file mode 100644
index 77c3b3acc..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/func.yaml
+++ /dev/null
@@ -1,81 +0,0 @@
----
-func:
-  suffixes:
-  - bold
-  - cbv
-  - sbref
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  datatypes:
-  - func
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    direction: optional
-    run: optional
-    echo: optional
-    part: optional
-
-phase:
-  suffixes:
-  - phase  # deprecated
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  datatypes:
-  - func
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    direction: optional
-    run: optional
-    echo: optional
-
-events:
-  suffixes:
-  - events
-  extensions:
-  - .tsv
-  - .json
-  datatypes:
-  - func
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    direction: optional
-    run: optional
-
-timeseries:
-  suffixes:
-  - physio
-  - stim
-  extensions:
-  - .tsv.gz
-  - .json
-  datatypes:
-  - func
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    ceagent: optional
-    reconstruction: optional
-    direction: optional
-    run: optional
-    recording: optional
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/ieeg.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/ieeg.yaml
deleted file mode 100644
index 6b14df288..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/ieeg.yaml
+++ /dev/null
@@ -1,108 +0,0 @@
----
-ieeg:
-  suffixes:
-  - ieeg
-  extensions:
-  - .mefd/
-  - .json
-  - .edf
-  - .vhdr
-  - .eeg
-  - .vmrk
-  - .set
-  - .fdt
-  - .nwb
-  datatypes:
-  - ieeg
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    run: optional
-
-channels:
-  suffixes:
-  - channels
-  extensions:
-  - .json
-  - .tsv
-  datatypes:
-  - ieeg
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    run: optional
-
-coordsystem:
-  suffixes:
-  - coordsystem
-  extensions:
-  - .json
-  datatypes:
-  - ieeg
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-    space: optional
-
-electrodes:
-  suffixes:
-  - electrodes
-  extensions:
-  - .json
-  - .tsv
-  datatypes:
-  - ieeg
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-    space: optional
-
-events:
-  suffixes:
-  - events
-  extensions:
-  - .json
-  - .tsv
-  datatypes:
-  - ieeg
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    run: optional
-
-photo:
-  suffixes:
-  - photo
-  extensions:
-  - .jpg
-  - .png
-  - .tif
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-
-timeseries:
-  suffixes:
-  - physio
-  - stim
-  extensions:
-  - .tsv.gz
-  - .json
-  datatypes:
-  - ieeg
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    run: optional
-    recording: optional
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/meg.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/meg.yaml
deleted file mode 100644
index 133f4aa7d..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/meg.yaml
+++ /dev/null
@@ -1,163 +0,0 @@
----
-meg:
-  suffixes:
-  - meg
-  extensions:
-  - /  # corresponds to BTi/4D data
-  - .ds/
-  - .json
-  - .fif
-  - .sqd
-  - .con
-  - .raw
-  - .ave
-  - .mrk
-  - .kdf
-  - .mhd
-  - .trg
-  - .chn
-  datatypes:
-  - meg
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    run: optional
-    processing: optional
-    split: optional
-
-calibration:
-  suffixes:
-  - meg
-  extensions:
-  - .dat
-  datatypes:
-  - meg
-  entities:
-    subject: required
-    session: optional
-    acquisition:
-      requirement: required
-      type: string
-      enum:
-      - calibration
-
-crosstalk:
-  suffixes:
-  - meg
-  extensions:
-  - .fif
-  datatypes:
-  - meg
-  entities:
-    subject: required
-    session: optional
-    acquisition:
-      requirement: required
-      type: string
-      enum:
-      - crosstalk
-
-headshape:
-  suffixes:
-  - headshape
-  extensions:
-  - .*
-  - .pos
-  datatypes:
-  - meg
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-
-markers:
-  suffixes:
-  - markers
-  extensions:
-  - .sqd
-  - .mrk
-  datatypes:
-  - meg
-  entities:
-    subject: required
-    session: optional
-    task: optional
-    acquisition: optional
-    space: optional
-
-coordsystem:
-  suffixes:
-  - coordsystem
-  extensions:
-  - .json
-  datatypes:
-  - meg
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-
-channels:
-  suffixes:
-  - channels
-  extensions:
-  - .json
-  - .tsv
-  datatypes:
-  - meg
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    run: optional
-    processing: optional
-
-events:
-  suffixes:
-  - events
-  extensions:
-  - .json
-  - .tsv
-  datatypes:
-  - meg
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    run: optional
-
-photo:
-  suffixes:
-  - photo
-  extensions:
-  - .jpg
-  - .png
-  - .tif
-  datatypes:
-  - meg
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-
-timeseries:
-  suffixes:
-  - physio
-  - stim
-  extensions:
-  - .tsv.gz
-  - .json
-  datatypes:
-  - meg
-  entities:
-    subject: required
-    session: optional
-    task: required
-    acquisition: optional
-    run: optional
-    processing: optional
-    recording: optional
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/micr.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/micr.yaml
deleted file mode 100644
index c08072a74..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/micr.yaml
+++ /dev/null
@@ -1,52 +0,0 @@
----
-microscopy:
-  suffixes:
-  - TEM
-  - SEM
-  - uCT
-  - BF
-  - DF
-  - PC
-  - DIC
-  - FLUO
-  - CONF
-  - PLI
-  - CARS
-  - 2PE
-  - MPE
-  - SR
-  - NLO
-  - OCT
-  - SPIM
-  extensions:
-  - .ome.tif
-  - .ome.btf
-  - .ome.zarr/
-  - .png
-  - .tif
-  - .json
-  datatypes:
-  - micr
-  entities:
-    subject: required
-    session: optional
-    sample: required
-    acquisition: optional
-    stain: optional
-    run: optional
-    chunk: optional
-
-photo:
-  suffixes:
-  - photo
-  extensions:
-  - .jpg
-  - .png
-  - .tif
-  datatypes:
-  - micr
-  entities:
-    subject: required
-    session: optional
-    sample: required
-    acquisition: optional
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/perf.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/perf.yaml
deleted file mode 100644
index ef97ffb54..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/perf.yaml
+++ /dev/null
@@ -1,66 +0,0 @@
----
-asl:
-  suffixes:
-  - asl
-  - m0scan
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  datatypes:
-  - perf
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-    reconstruction: optional
-    direction: optional
-    run: optional
-
-aslcontext:
-  suffixes:
-  - aslcontext
-  extensions:
-  - .tsv
-  - .json
-  datatypes:
-  - perf
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-    reconstruction: optional
-    direction: optional
-    run: optional
-
-asllabeling:
-  suffixes:
-  - asllabeling
-  extensions:
-  - .jpg
-  datatypes:
-  - perf
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-    reconstruction: optional
-    run: optional
-
-timeseries:
-  suffixes:
-  - physio
-  - stim
-  extensions:
-  - .tsv.gz
-  - .json
-  datatypes:
-  - perf
-  entities:
-    subject: required
-    session: optional
-    acquisition: optional
-    reconstruction: optional
-    direction: optional
-    run: optional
-    recording: optional
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/pet.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/pet.yaml
deleted file mode 100644
index 36d8cd3ce..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/datatypes/pet.yaml
+++ /dev/null
@@ -1,68 +0,0 @@
----
-pet:
-  suffixes:
-  - pet
-  extensions:
-  - .nii.gz
-  - .nii
-  - .json
-  datatypes:
-  - pet
-  entities:
-    subject: required
-    session: optional
-    task: optional
-    tracer: optional
-    reconstruction: optional
-    run: optional
-
-blood:
-  suffixes:
-  - blood
-  extensions:
-  - .tsv
-  - .json
-  datatypes:
-  - pet
-  entities:
-    subject: required
-    session: optional
-    task: optional
-    tracer: optional
-    reconstruction: optional
-    run: optional
-    recording: required
-
-events:
-  suffixes:
-  - events
-  extensions:
-  - .tsv
-  - .json
-  datatypes:
-  - pet
-  entities:
-    subject: required
-    session: optional
-    task: required
-    tracer: optional
-    reconstruction: optional
-    run: optional
-
-timeseries:
-  suffixes:
-  - physio
-  - stim
-  extensions:
-  - .tsv.gz
-  - .json
-  datatypes:
-  - pet
-  entities:
-    subject: required
-    session: optional
-    task: optional
-    tracer: optional
-    reconstruction: optional
-    run: optional
-    recording: optional
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/entities.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/entities.yaml
deleted file mode 100644
index 08209723e..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/entities.yaml
+++ /dev/null
@@ -1,31 +0,0 @@
----
-# This file simply defines the order in which entities should appear within filenames.
-# Entity definitions appear in the `objects/entities.yaml` file.
-- subject
-- session
-- sample
-- task
-- acquisition
-- ceagent
-- tracer
-- stain
-- reconstruction
-- direction
-- run
-- modality
-- echo
-- flip
-- inversion
-- mtransfer
-- part
-- processing
-- hemisphere
-- space
-- split
-- recording
-- chunk
-- atlas
-- resolution
-- density
-- label
-- description
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/modalities.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/modalities.yaml
deleted file mode 100644
index 04b24489d..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/modalities.yaml
+++ /dev/null
@@ -1,27 +0,0 @@
----
-# This file defines which data types fall under each modality.
-mri:
-  datatypes:
-  - anat
-  - dwi
-  - fmap
-  - func
-  - perf
-eeg:
-  datatypes:
-  - eeg
-ieeg:
-  datatypes:
-  - ieeg
-meg:
-  datatypes:
-  - meg
-beh:
-  datatypes:
-  - beh
-pet:
-  datatypes:
-  - pet
-micr:
-  datatypes:
-  - micr
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/anat.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/anat.yaml
deleted file mode 100644
index 4df92f0bb..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/anat.yaml
+++ /dev/null
@@ -1,34 +0,0 @@
-#
-# Groups of related metadata fields
-#
-# Assumptions: never need disjunction of selectors
-# Assumptions: top-to-bottom overrides is sufficient logic
-
-
----
-# Anatomy imaging data
-
-MRIAnatomyCommonMetadataFields:
-    selectors:
-    - modality == "MRI"
-    - datatype == "anat"
-    fields:
-        ContrastBolusIngredient: OPTIONAL
-        RepetitionTimeExcitation: OPTIONAL
-        RepetitionTimePreparation: OPTIONAL
-
-PhaseEntityUnits:
-    selectors:
-    - modality == "MRI"
-    - datatype == "anat"
-    - entities.part == "phase"
-    fields:
-        Unit: REQUIRED
-
-PhaseSuffixUnits:
-    selectors:
-    - modality == "MRI"
-    - datatype == "anat"
-    - suffix == "phase"
-    fields:
-        Unit: REQUIRED
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/asl.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/asl.yaml
deleted file mode 100644
index d711f9fc7..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/asl.yaml
+++ /dev/null
@@ -1,285 +0,0 @@
-#
-# Groups of related metadata fields
-#
-# Assumptions: never need disjunction of selectors
-# Assumptions: top-to-bottom overrides is sufficient logic
-
-
----
-# Fields described in text, but not in tables
-MRIASLTextOnly:
-    selectors:
-    - modality == "MRI"
-    - datatype == "perf"
-    - suffix == "asl"
-    fields:
-        MagneticFieldStrength: required
-        MRAcquisitionType: required
-        EchoTime: required
-        SliceTiming:
-            level: recommended
-            level_addendum: required if `MRAcquisitionType` is defined as `2D`
-        RepetitionTimePreparation: required
-        FlipAngle:
-            level: recommended
-            level_addendum: required if `LookLocker` is `true`
-
-MRIASLTextOnlySliceTiming:
-    selectors:
-    - modality == "MRI"
-    - datatype == "perf"
-    - suffix == "asl"
-    - '"MRAcquisitionType" in sidecar'
-    - sidecar.MRAcquisitionType == "2D"
-    fields:
-        SliceTiming:
-            level: required
-            issue:
-                code: SLICE_TIMING_NOT_DEFINED_2D_ASL
-                message: |
-                    You should define `SliceTiming` for this file, because `SequenceType` is sets
-                    to a 2D sequence. `SliceTiming` is the time at which each slice was
-                    acquired within each volume (frame) of the acquisition. Slice timing
-                    is not slice order -- rather, it is a list of times containing the
-                    time (in seconds) of each slice acquisition in relation to the beginning
-                    of volume acquisition. The list goes through the slices along the slice
-                    axis in the slice encoding dimension (see below). Note that to ensure the
-                    proper interpretation of the `SliceTiming` field, it is important to check
-                    if the optional `SliceEncodingDirection` exists. In particular, if
-                    `SliceEncodingDirection` is negative, the entries in `SliceTiming` are
-                    defined in reverse order with respect to the slice axis, such that the
-                    final entry in the `SliceTiming` list is the time of acquisition of slice 0.
-                    Without this parameter slice time correction will not be possible.
-
-MRIASLTextOnlyFlipAngle:
-    selectors:
-    - modality == "MRI"
-    - datatype == "perf"
-    - suffix == "asl"
-    - '"LookLocker in sidecar'
-    - sidecar.LookLocker == true
-    fields:
-        FlipAngle:
-            level: required
-            issue:
-                code: LOOK_LOCKER_FLIP_ANGLE_MISSING
-                message: |
-                    You should define `FlipAngle` for this file, in case of a
-                    LookLocker acquisition. `FlipAngle` is the flip angle (FA)
-                    for the acquisition, specified in degrees. Corresponds to
-                    DICOM Tag 0018, 1314 `Flip Angle`. The data type number may
-                    apply to files from any MRI modality concerned with a single
-                    value for this field, or to the files in a file collection
-                    where the value of this field is iterated using the flip entity.
-                    The data type array provides a value for each volume in a 4D
-                    dataset and should only be used when the volume timing is critical
-                    for interpretation of the data, such as in ASL or variable flip
-                    angle fMRI sequences.
-
-# Common metadata fields applicable to both (P)CASL and PASL
-MRIASLCommonMetadataFields:
-    selectors:
-    - modality == "MRI"
-    - datatype == "perf"
-    - suffix == "asl"
-    fields:
-        ArterialSpinLabelingType: required
-        PostLabelingDelay: required
-        BackgroundSuppression: required
-        M0Type: required
-        TotalAcquiredPairs: required
-        VascularCrushing: recommended
-        AcquisitionVoxelSize: recommended
-        M0Estimate:
-            level: optional
-            level_addendum: required if `M0Type` is `Estimate`
-        BackgroundSuppressionNumberPulses:
-            level: optional
-            level_addendum: recommended if `BackgroundSuppression` is `true`
-        BackgroundSuppressionPulseTime:
-            level: optional
-            level_addendum: recommended if `BackgroundSuppression` is `true`
-        VascularCrushingVENC:
-            level: optional
-            level_addendum: recommended if `VascularCrushing` is `true`
-        LabelingOrientation: recommended
-        LabelingDistance: recommended
-        LabelingLocationDescription: recommended
-        LookLocker: optional
-        LabelingEfficiency: optional
-
-MRIASLCommonMetadataFieldsM0Type:
-    selectors:
-    - modality == "MRI"
-    - datatype == "perf"
-    - suffix == "asl"
-    - '"M0Type" in sidecar'
-    - sidecar.M0Type == "Estimate"
-    fields:
-        M0Estimate:
-            level: required
-            issue:
-                code: M0ESTIMATE_NOT_DEFINED
-                message: |
-                    You must define `M0Estimate` for this file, because `M0Type` is set to
-                    'Estimate'. `M0Estimate` is a single numerical whole-brain M0 value
-                    (referring to the M0 of blood), only if obtained externally (for example
-                    retrieved from CSF in a separate measurement).
-
-MRIASLCommonMetadataFieldsBackgroundSuppression:
-    selectors:
-    - modality == "MRI"
-    - datatype == "perf"
-    - suffix == "asl"
-    - '"BackgroundSuppression" in sidecar'
-    - sidecar.BackgroundSuppression == true
-    fields:
-        BackgroundSuppressionNumberPulses: recommended
-        BackgroundSuppressionPulseTime: recommended
-
-MRIASLCommonMetadataFieldsVascularCrushing:
-    selectors:
-    - modality == "MRI"
-    - datatype == "perf"
-    - suffix == "asl"
-    - '"VascularCrushing" in sidecar'
-    - sidecar.VascularCrushing == true
-    fields:
-        VascularCrushingVENC: recommended
-
-MRIASLPCASLSpecific:
-    selectors:
-    - modality == "MRI"
-    - datatype == "perf"
-    - suffix == "asl"
-    - '"ArterialSpinLabelingType" in sidecar'
-    - '["CASL", "PCASL"].includes(sidecar.ArterialSpinLabelingType)'
-    fields:
-        LabelingDuration: required
-        LabelingPulseAverageGradient: recommended
-        LabelingPulseMaximumGradient: recommended
-        LabelingPulseAverageB1: recommended
-        LabelingPulseDuration: recommended
-        LabelingPulseFlipAngle: recommended
-        LabelingPulseInterval: recommended
-
-MRIASLPCASLSpecific2:
-    selectors:
-    - modality == "MRI"
-    - datatype == "perf"
-    - suffix == "asl"
-    - '"ArterialSpinLabelingType" in sidecar'
-    - sidecar.ArterialSpinLabelingType == "PCASL"
-    fields:
-        PCASLType: recommended
-
-MRIASLCASLSpecific:
-    selectors:
-    - modality == "MRI"
-    - datatype == "perf"
-    - suffix == "asl"
-    - '"ArterialSpinLabelingType" in sidecar'
-    - sidecar.ArterialSpinLabelingType == "CASL"
-    fields:
-        CASLType: recommended
-
-MRIASLPASLSpecific:
-    selectors:
-    - modality == "MRI"
-    - datatype == "perf"
-    - suffix == "asl"
-    - '"ArterialSpinLabelingType" in sidecar'
-    - sidecar.ArterialSpinLabelingType == "PASL"
-    fields:
-        BolusCutOffFlag: required
-        PASLType: recommended
-        LabelingSlabThickness: recommended
-        BolusCutOffDelayTime:
-            level: optional
-            level_addendum: required if `BolusCutOffFlag` is `true`
-        BolusCutOffTechnique:
-            level: optional
-            level_addendum: required if `BolusCutOffFlag` is `true`
-
-MRIASLPASLSpecificBolusCutOffFlag:
-    selectors:
-    - modality == "MRI"
-    - datatype == "perf"
-    - suffix == "asl"
-    - '"ArterialSpinLabelingType" in sidecar'
-    - sidecar.ArterialSpinLabelingType == "PASL"
-    - '"BolusCutOffFlag" in sidecar'
-    - sidecar.BolusCutOffFlag == true
-    fields:
-        BolusCutOffDelayTime:
-            level: required
-            issue:
-                code: PASL_BOLUS_CUT_OFF_DELAY_TIME
-                message: |
-                    It is required to define 'BolusCutOffDelayTime' for this file,
-                    when 'BolusCutOffFlag' is set to true. 'BolusCutOffDelayTime' is
-                    the duration between the end of the labeling and the start of the
-                    bolus cut-off saturation pulse(s), in seconds. This can be a number
-                    or array of numbers, of which the values must be non-negative and
-                    monotonically increasing, depending on the number of bolus cut-off
-                    saturation pulses. For Q2TIPS, only the values for the first and last
-                    bolus cut-off saturation pulses are provided. Based on DICOM Tag
-                    0018,925F ASL Bolus Cut-off Delay Time.
-        BolusCutOffTechnique:
-            level: required
-            issue:
-                code: PASL_BOLUS_CUT_OFF_TECHINIQUE
-                message: |
-                    It is required to define `BolusCutOffTechnique` for this file,
-                    when `BolusCutOffFlag` is set to `true`. `BolusCutOffTechnique`,
-                    is the name of the technique used
-                    (for example, Q2TIPS, QUIPSS or QUIPSSII).
-                    Corresponds to DICOM Tag 0018,925E `ASL Bolus Cut-off Technique`.
-
-# m0scan metadata fields
-MRIASLM0ScanTextOnly:
-    selectors:
-    - modality == "MRI"
-    - datatype == "perf"
-    - suffix == "m0scan"
-    fields:
-        EchoTime: required
-        RepetitionTimePreparation: required
-        FlipAngle:
-            level: recommended
-            level_addendum: required if `LookLocker` is `true`
-
-MRIASLM0ScanTextOnlyFlipAngle:
-    selectors:
-    - modality == "MRI"
-    - datatype == "perf"
-    - suffix == "m0scan"
-    - '"LookLocker" in sidecar'
-    - sidecar.LookLocker == true
-    fields:
-        FlipAngle:
-            level: required
-            issue:
-                code: LOOK_LOCKER_FLIP_ANGLE_MISSING
-                message: |
-                    You should define `FlipAngle` for this file, in case of a LookLocker
-                    acquisition. `FlipAngle` is the flip angle (FA) for the acquisition,
-                    specified in degrees. Corresponds to DICOM Tag 0018, 1314 `Flip Angle`.
-                    The data type number may apply to files from any MRI modality concerned
-                    with a single value for this field, or to the files in a file collection
-                    where the value of this field is iterated using the flip entity. The
-                    data type array provides a value for each volume in a 4D dataset and
-                    should only be used when the volume timing is critical for interpretation
-                    of the data, such as in ASL or variable flip angle fMRI sequences.
-
-MRIASLM0Scan:
-    selectors:
-    - modality == "MRI"
-    - datatype == "perf"
-    - suffix == "m0scan"
-    fields:
-        IntendedFor:
-            level: required
-            description_addendum: |
-                This is used to refer to the ASL time series for which the `*_m0scan.nii[.gz]` is intended.
-        AcquisitionVoxelSize: recommended
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/beh.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/beh.yaml
deleted file mode 100644
index d0760eda5..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/beh.yaml
+++ /dev/null
@@ -1,21 +0,0 @@
-#
-# Groups of related metadata fields
-#
-# Assumptions: never need disjunction of selectors
-# Assumptions: top-to-bottom overrides is sufficient logic
-
-
----
-# Metadata for either beh or events files
-BEHTabularData:
-    selectors:
-    - '["beh", "events"].includes(suffix)'
-    fields:
-        TaskName: recommended
-        Instructions: recommended
-        TaskDescription: recommended
-        CogAtlasID: recommended
-        CogPOID: recommended
-        InstitutionName: recommended
-        InstitutionAddress: recommended
-        InstitutionalDepartmentName: recommended
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/continuous.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/continuous.yaml
deleted file mode 100644
index 2607ce1df..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/continuous.yaml
+++ /dev/null
@@ -1,26 +0,0 @@
-#
-# Groups of related metadata fields
-#
-# Assumptions: never need disjunction of selectors
-# Assumptions: top-to-bottom overrides is sufficient logic
-
-
----
-# Metadata for either physio or stim files
-Continuous:
-    selectors:
-    - '["physio", "stim"].includes(suffix)'
-    fields:
-        SamplingFrequency: required
-        StartTime: required
-        Columns: required
-
-# Other recommended metadata for physiological data
-Physio:
-    selectors:
-    - suffix == "physio"
-    fields:
-        Manufacturer: recommended
-        ManufacturersModelName: recommended
-        SoftwareVersions: recommended
-        DeviceSerialNumber: recommended
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/derivatives/common_derivatives.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/derivatives/common_derivatives.yaml
deleted file mode 100644
index 5d01d3683..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/derivatives/common_derivatives.yaml
+++ /dev/null
@@ -1,85 +0,0 @@
----
-CommonDerivativeFields:
-  selectors:
-  - dataset.DatasetType == "derivative"
-  fields:
-    Description: RECOMMENDED
-    Sources: OPTIONAL
-    RawSources: OPTIONAL
-
-SpatialReferenceEntity:
-  selectors:
-  - dataset.DatasetType == "derivative"
-  - '"space" in entities'
-  fields:
-    SpatialReference: RECOMMENDED
-
-SpatialReferenceNonStandard:
-  selectors:
-  - dataset.DatasetType == "derivative"
-  - 'schema.objects.metadata._StandardTemplateCoordSys).includes(not(entities.space)'
-  fields:
-    SpatialReference: REQUIRED
-
-SpatialReferenceNoEntity:
-  selectors:
-  - dataset.DatasetType == "derivative"
-  - '!("space" in entities)'
-  fields:
-    SpatialReference: REQUIRED
-
-# this needs to come before density and resolution overrides selected in a
-# different way
-MaskDerivatives:
-  selectors:
-  - dataset.DatasetType == "derivative"
-  - suffix == "mask"
-  fields:
-    RawSources: REQUIRED
-    Type: RECOMMENDED
-    Atlas: OPTIONAL
-    Resolution: OPTIONAL
-    Density: OPTIONAL
-
-MaskDerivativesAtlas:
-  selectors:
-  - dataset.DatasetType == "derivative"
-  - suffix == "mask"
-  - '"label" in entities'
-  fields:
-    atlas: RECOMMENDED
-
-SegmentationCommon:
-  selectors:
-  - dataset.DatasetType == "derivative"
-  - '["dseg", "probseg"].includes(suffix)'
-  fields:
-    Type: RECOMMENDED
-    Atlas: OPTIONAL
-    Resolution: OPTIONAL
-    Density: OPTIONAL
-
-# Derivatives -> Imaging data types
-ImageDerivatives:
-  selectors:
-  - dataset.DatasetType == "derivative"
-  - '["mri", "pet"].includes(modality)'
-  - '[".nii", ".nii.gz"].includes(extension)'
-  fields:
-    SkullStripped: REQUIRED
-
-ImageDerivativeResEntity:
-  selectors:
-  - dataset.DatasetType == "derivative"
-  - '["mri", "pet"].includes(modality)'
-  - '"res" in entities'
-  fields:
-    Resolution: REQUIRED
-
-ImageDerivativeDenEntity:
-  selectors:
-  - dataset.DatasetType == "derivative"
-  - '["mri", "pet"].includes(modality)'
-  - '"den" in entities'
-  fields:
-    Density: REQUIRED
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/dwi.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/dwi.yaml
deleted file mode 100644
index 0f25d3ee1..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/dwi.yaml
+++ /dev/null
@@ -1,25 +0,0 @@
-#
-# Groups of related metadata fields
-#
-# Assumptions: never need disjunction of selectors
-# Assumptions: top-to-bottom overrides is sufficient logic
-
-
----
-# Multipart (split) DWI schemes
-# NOTE: I don't think this can be schemafied, since it depends on owner intent.
-MRIDiffusionMultipart:
-    selectors:
-    - modality == "mri"
-    - datatype == "dwi"
-    fields:
-        MultipartID: required
-
-# Other recommended metadata
-MRIDiffusionOtherMetadata:
-    selectors:
-    - modality == "mri"
-    - datatype == "dwi"
-    fields:
-        PhaseEncodingDirection: recommended
-        TotalReadoutTime: recommended
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/eeg.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/eeg.yaml
deleted file mode 100644
index d82715d85..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/eeg.yaml
+++ /dev/null
@@ -1,166 +0,0 @@
-#
-# Groups of related metadata fields
-#
-# Assumptions: never need disjunction of selectors
-# Assumptions: top-to-bottom overrides is sufficient logic
-
-
----
-
-EEGGeneric:
-    selectors:
-    - modality == "eeg"
-    - datatype == "eeg"
-    - suffix == "eeg"
-    fields:
-        TaskName:
-            level: required
-            description_addendum: |
-                A recommended convention is to name resting state task using labels
-                beginning with `rest`.
-
-EEGRecommended:
-    selectors:
-    - modality == "eeg"
-    - datatype == "eeg"
-    - suffix == "eeg"
-    fields:
-        InstitutionName: recommended
-        InstitutionAddress: recommended
-        InstitutionalDepartmentName: recommended
-        Manufacturer: recommended
-        ManufacturersModelName: recommended
-        SoftwareVersions: recommended
-        TaskDescription: recommended
-        Instructions:
-            level: recommended
-            description_addendum: |
-                This is especially important in context of resting state recordings and
-                distinguishing between eyes open and eyes closed paradigms.
-        CogAtlasID: recommended
-        CogPOID: recommended
-        DeviceSerialNumber: recommended
-
-EEGRequired:
-    selectors:
-    - modality == "eeg"
-    - datatype == "eeg"
-    - suffix == "eeg"
-    fields:
-        EEGReference: required
-        SamplingFrequency:
-            level: required
-            description_addendum: |
-                The sampling frequency of data channels that deviate from the main sampling
-                frequency SHOULD be specified in the `channels.tsv` file.
-        PowerLineFrequency: required
-        SoftwareFilters: required
-
-EEGMoreRecommended:
-    selectors:
-    - modality == "eeg"
-    - datatype == "eeg"
-    - suffix == "eeg"
-    fields:
-        CapManufacturer: recommended
-        CapManufacturersModelName: recommended
-        EEGChannelCount: recommended
-        ECGChannelCount: recommended
-        EMGChannelCount: recommended
-        EOGChannelCount: recommended
-        MiscChannelCount: recommended
-        TriggerChannelCount: recommended
-        RecordingDuration: recommended
-        RecordingType: recommended
-        EpochLength: recommended
-        EEGGround: recommended
-        HeadCircumference: recommended
-        EEGPlacementScheme: recommended
-        HardwareFilters: recommended
-        SubjectArtefactDescription: recommended
-
-# General fields
-EEGCoordsystemGeneral:
-    selectors:
-    - modality == "eeg"
-    - datatype == "eeg"
-    - suffix == "coordsystem"
-    fields:
-        IntendedFor:
-            level: optional
-            description_addendum: |
-                This identifies the MRI or CT scan associated with the electrodes,
-                landmarks, and fiducials.
-
-# Fields relating to the EEG electrode positions
-EEGCoordsystemPositions:
-    selectors:
-    - modality == "eeg"
-    - datatype == "eeg"
-    - suffix == "coordsystem"
-    fields:
-        EEGCoordinateSystem: required
-        EEGCoordinateUnits: required
-        EEGCoordinateSystemDescription:
-            level: recommended
-            level_addendum: required if `EEGCoordinateSystem` is `"Other"`
-
-EEGCoordsystemOther:
-    selectors:
-    - modality == "eeg"
-    - datatype == "eeg"
-    - suffix == "coordsystem"
-    - '"EEGCoordinateSystem" in sidecar'
-    - sidecar.EEGCoordinateSystem == "Other"
-    fields:
-        EEGCoordinateSystemDescription: required
-
-# Fields relating to the position of fiducials measured during an EEG session/run
-EEGCoordsystemFiducials:
-    selectors:
-    - modality == "eeg"
-    - datatype == "eeg"
-    - suffix == "coordsystem"
-    fields:
-        FiducialsDescription: optional
-        FiducialsCoordinates: recommended
-        FiducialsCoordinateSystem: recommended
-        FiducialsCoordinateUnits: recommended
-        FiducialsCoordinateSystemDescription:
-            level: recommended
-            level_addendum: required if `FiducialsCoordinateSystem` is `"Other"`
-
-EEGCoordsystemOtherFiducialCoordinateSystem:
-    selectors:
-    - modality == "eeg"
-    - datatype == "eeg"
-    - suffix == "coordsystem"
-    - FiducialsCoordinateSystem == "Other"
-    fields:
-        FiducialsCoordinateSystemDescription: required
-
-# Fields relating to the position of anatomical landmark measured during an EEG session/run
-EEGCoordsystemLandmark:
-    selectors:
-    - modality == "eeg"
-    - datatype == "eeg"
-    - suffix == "coordsystem"
-    fields:
-        AnatomicalLandmarkCoordinates: recommended
-        AnatomicalLandmarkCoordinateSystem:
-            level: recommended
-            description_addendum: Preferably the same as the `EEGCoordinateSystem`.
-        AnatomicalLandmarkCoordinateUnits: recommended
-        AnatomicalLandmarkCoordinateSystemDescription:
-            level: recommended
-            level_addendum: required if `AnatomicalLandmarkCoordinateSystem` is `"Other"`
-
-EEGCoordsystemAnatomicalLandmarkCoordinateSystemDescription:
-    selectors:
-    - modality == "eeg"
-    - datatype == "eeg"
-    - suffix == "coordsystem"
-    - '"AnatomicalLandmarkCoordinateSystem" in sidecar'
-    - sidecar.AnatomicalLandmarkCoordinateSystem == "Other"
-    fields:
-        AnatomicalLandmarkCoordinateSystemDescription: required
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/entities.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/entities.yaml
deleted file mode 100644
index e6249cfd0..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/entities.yaml
+++ /dev/null
@@ -1,81 +0,0 @@
-#
-# Groups of related metadata fields
-#
-# Assumptions: never need disjunction of selectors
-# Assumptions: top-to-bottom overrides is sufficient logic
-
-
----
-
-# Entities
-
-EntitiesTaskMetadata:
-    selectors:
-    - '"task" in entities'
-    fields:
-        TaskName: recommended
-
-EntitiesCeMetadata:
-    selectors:
-    - '"ce" in entities'
-    fields:
-        ContrastBolusIngredient: optional
-
-EntitiesTrcMetadata:
-    selectors:
-    - '"trc" in entities'
-    fields:
-        TracerName: required
-
-EntitiesStainMetadata:
-    selectors:
-    - '"stain" in entities'
-    fields:
-        SampleStaining: recommended
-        SamplePrimaryAntibodies: recommended
-        SampleSecondaryAntibodies: recommended
-
-EntitiesEchoMetadata:
-    selectors:
-    - '"echo" in entities'
-    fields:
-        EchoTime: required
-
-EntitiesFlipMetadata:
-    selectors:
-    - '"flip" in entities'
-    fields:
-        FlipAngle: required
-
-EntitiesInvMetadata:
-    selectors:
-    - '"inv" in entities'
-    fields:
-        InversionTime: required
-
-EntitiesMTMetadata:
-    selectors:
-    - '"mt" in entities'
-    fields:
-        MTState: required
-
-EntitiesPartMetadata:
-    selectors:
-    - entities.part == "phase"
-    fields:
-        Units:
-            level: required
-            rules:
-            - '["rad", "arbitrary"].includes(value)'
-
-EntitiesResMetadata:
-    selectors:
-    - '"res" in entities'
-    fields:
-        Resolution: required
-
-EntitiesDenMetadata:
-    selectors:
-    - '"den" in entities'
-    fields:
-        Density: required
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/fmap.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/fmap.yaml
deleted file mode 100644
index bd628a5c1..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/fmap.yaml
+++ /dev/null
@@ -1,87 +0,0 @@
-#
-# Groups of related metadata fields
-#
-# Assumptions: never need disjunction of selectors
-# Assumptions: top-to-bottom overrides is sufficient logic
-
-
----
-# Fieldmap data
-MRIFieldmapB0FieldIdentifier:
-    selectors:
-    - modality == "MRI"
-    - datatype == "fmap"
-    fields:
-        B0FieldIdentifier: recommended
-
-MRIFieldmapIntendedFor:
-    selectors:
-    - modality == "MRI"
-    - datatype == "fmap"
-    fields:
-        IntendedFor:
-            level: optional
-            description_addendum: |
-                This field is optional, and in case the fieldmaps do not correspond
-                to any particular scans, it does not have to be filled.
-
-# Case 1: Phase-difference map and at least one magnitude image
-MRIFieldmapPhaseDifferencePhasediff:
-    selectors:
-    - modality == "MRI"
-    - datatype == "fmap"
-    - suffix == "phasediff"
-    fields:
-        EchoTime1: required
-        EchoTime2: required
-
-MRIFieldmapPhaseDifferenceMagnitude1:
-    selectors:
-    - modality == "MRI"
-    - datatype == "fmap"
-    - suffix == "magnitude1"
-    fields:
-        EchoTime1: required
-
-MRIFieldmapPhaseDifferenceMagnitude2:
-    selectors:
-    - modality == "MRI"
-    - datatype == "fmap"
-    - suffix == "magnitude2"
-    fields:
-        EchoTime2: required
-
-# Case 2: Two phase maps and two magnitude images
-# NOTE: Need to check for presence of related files.
-# For example, magnitude1 needs EchoTime__fmap only if phase1 file exists,
-# but EchoTime1 if phasediff exists.
-MRIFieldmapTwoPhase:
-    selectors:
-    - modality == "MRI"
-    - datatype == "fmap"
-    - '["phase1", "phase2", "magnitude1", "magnitude2"].includes(suffix)'
-    fields:
-        EchoTime__fmap: required
-
-# Case 3: Direct field mapping
-MRIFieldmapDirectFieldMapping:
-    selectors:
-    - modality == "MRI"
-    - datatype == "fmap"
-    - '["phase", "fieldmap"].includes(suffix)'
-    fields:
-        Units:
-            level: required
-            description_addendum: |
-                Fieldmaps must be in units of Hertz (`"Hz"`),
-                radians per second (`"rad/s"`), or Tesla (`"T"`).
-
-# Case 4: Multiple phase encoded directions ("pepolar")
-MRIFieldmapPepolar:
-    selectors:
-    - modality == "MRI"
-    - datatype == "fmap"
-    - suffix == "epi"
-    fields:
-        PhaseEncodingDirection: required
-        TotalReadoutTime: required
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/func.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/func.yaml
deleted file mode 100644
index 9d7cdd012..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/func.yaml
+++ /dev/null
@@ -1,110 +0,0 @@
-#
-# Groups of related metadata fields
-#
-# Assumptions: never need disjunction of selectors
-# Assumptions: top-to-bottom overrides is sufficient logic
-
-
----
-# Task imaging data
-
-# Required fields
-MRIFuncRequired:
-    selectors:
-    - modality == "mri"
-    - datatype == "func"
-    fields:
-        RepetitionTime: required
-        VolumeTiming: required
-        TaskName:
-            level: required
-            description_addendum: |
-                A recommended convention is to name resting state task using labels
-                beginning with `rest`.
-
-# Timing Parameters
-MRIFuncTimingParameters:
-    selectors:
-    - modality == "mri"
-    - datatype == "func"
-    fields:
-        NumberOfVolumesDiscardedByScanner: recommended
-        NumberOfVolumesDiscardedByUser: recommended
-        DelayTime: recommended
-        AcquisitionDuration:
-            level: recommended
-            level_addendum: |
-                required for sequences that are described with the `VolumeTiming`
-                field and that do not have the `SliceTiming` field set to allow for
-                accurate calculation of "acquisition time"
-            issue:
-                name: VOLUME_TIMING_MISSING_ACQUISITION_DURATION
-                message: |
-                    The field 'VolumeTiming' requires 'AcquisitionDuration' or 'SliceTiming' to be defined.
-        DelayAfterTrigger: recommended
-
-# The mutual exclusion table, spread across 5 definitions
-# NOTE: This introduces a prohibited level
-MRIFuncTimingParametersMutualExclusion1:
-    selectors:
-    - modality == "mri"
-    - datatype == "func"
-    - '"RepetitionTime" in sidecar'
-    fields:
-        AcquisitionDuration: prohibited
-        VolumeTiming: prohibited
-
-MRIFuncTimingParametersMutualExclusion2:
-    selectors:
-    - modality == "mri"
-    - datatype == "func"
-    - '"SliceTiming" in sidecar'
-    - '"VolumeTiming" in sidecar'
-    fields:
-        RepetitionTime: prohibited
-        DelayTime: prohibited
-
-MRIFuncTimingParametersMutualExclusion3:
-    selectors:
-    - modality == "mri"
-    - datatype == "func"
-    - '"AcquisitionDuration" in sidecar'
-    - '"VolumeTiming" in sidecar'
-    fields:
-        RepetitionTime: prohibited
-        DelayTime: prohibited
-
-MRIFuncTimingParametersMutualExclusion4:
-    selectors:
-    - modality == "mri"
-    - datatype == "func"
-    - '"RepetitionTime" in sidecar'
-    - '"SliceTiming" in sidecar'
-    fields:
-        AcquisitionDuration: prohibited
-        VolumeTiming: prohibited
-
-MRIFuncTimingParametersMutualExclusion5:
-    selectors:
-    - modality == "mri"
-    - datatype == "func"
-    - '"RepetitionTime" in sidecar'
-    - '"DelayTime" in sidecar'
-    fields:
-        AcquisitionDuration: prohibited
-        VolumeTiming: prohibited
-
-# fMRI task information
-MRIFuncTaskInformation:
-    selectors:
-    - modality == "mri"
-    - datatype == "func"
-    fields:
-        Instructions:
-            level: recommended
-            description_addendum: |
-                This is especially important in context of resting state recordings and
-                distinguishing between eyes open and eyes closed paradigms.
-        TaskDescription: recommended
-        CogAtlasID: recommended
-        CogPOID: recommended
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/ieeg.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/ieeg.yaml
deleted file mode 100644
index 39c4fa907..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/ieeg.yaml
+++ /dev/null
@@ -1,144 +0,0 @@
-#
-# Groups of related metadata fields
-#
-# Assumptions: never need disjunction of selectors
-# Assumptions: top-to-bottom overrides is sufficient logic
-
-
----
-
-iEEGGeneric:
-    selectors:
-    - modality == "ieeg"
-    - datatype == "ieeg"
-    - suffix == "ieeg"
-    fields:
-        TaskName:
-            level: required
-            description_addendum: |
-                A recommended convention is to name resting state task using labels
-                beginning with `rest`.
-
-iEEGRecommended:
-    selectors:
-    - modality == "ieeg"
-    - datatype == "ieeg"
-    - suffix == "ieeg"
-    fields:
-        InstitutionName: recommended
-        InstitutionAddress: recommended
-        InstitutionalDepartmentName: recommended
-        Manufacturer:
-            level: recommended
-            description_addendum: For example, `"TDT"`, `"Blackrock"`.
-        ManufacturersModelName: recommended
-        SoftwareVersions: recommended
-        TaskDescription: recommended
-        Instructions:
-            level: recommended
-            description_addendum: |
-                This is especially important in context of resting state recordings and
-                distinguishing between eyes open and eyes closed paradigms.
-        CogAtlasID: recommended
-        CogPOID: recommended
-        DeviceSerialNumber: recommended
-
-# Specific iEEG fields MUST be present
-iEEGRequired:
-    selectors:
-    - modality == "ieeg"
-    - datatype == "ieeg"
-    - suffix == "ieeg"
-    fields:
-        iEEGReference: required
-        SamplingFrequency:
-            level: required
-            description_addendum: |
-                The sampling frequency of data channels that deviate from the main sampling
-                frequency SHOULD be specified in the `channels.tsv` file.
-        PowerLineFrequency: required
-        SoftwareFilters": required
-
-# Specific iEEG fields SHOULD be present
-iEEGMoreRecommended:
-    selectors:
-    - modality == "ieeg"
-    - datatype == "ieeg"
-    - suffix == "ieeg"
-    fields:
-        DCOffsetCorrection: deprecated
-        HardwareFilters: recommended
-        ElectrodeManufacturer: recommended
-        ElectrodeManufacturersModelName: recommended
-        ECOGChannelCount: recommended
-        SEEGChannelCount: recommended
-        EEGChannelCount: recommended
-        EOGChannelCount: recommended
-        ECGChannelCount: recommended
-        EMGChannelCount: recommended
-        MiscChannelCount: recommended
-        TriggerChannelCount: recommended
-        RecordingDuration: recommended
-        RecordingType: recommended
-        EpochLength: recommended
-        iEEGGround: recommended
-        iEEGPlacementScheme: recommended
-        iEEGElectrodeGroups: recommended
-        SubjectArtefactDescription: recommended
-
-# Specific iEEG fields MAY be present
-iEEGOptional:
-    selectors:
-    - modality == "ieeg"
-    - datatype == "ieeg"
-    - suffix == "ieeg"
-    fields:
-        ElectricalStimulation: optional
-        ElectricalStimulationParameters: optional
-
-# General fields
-iEEGCoordsystemGeneral:
-    selectors:
-    - modality == "ieeg"
-    - datatype == "ieeg"
-    - suffix == "coordsystem"
-    fields:
-        IntendedFor:
-            level: optional
-            description_addendum: |
-                If only a surface reconstruction is available, this should point to
-                the surface reconstruction file.
-                Note that this file should have the same coordinate system
-                specified in `iEEGCoordinateSystem`.
-                For example, **T1**: `'sub-<label>/ses-<label>/anat/sub-01_T1w.nii.gz'`
-                **Surface**: `'/derivatives/surfaces/sub-<label>/ses-<label>/anat/
-                sub-01_hemi-R_desc-T1w_pial.surf.gii'`
-                **Operative photo**: `'/sub-<label>/ses-<label>/ieeg/
-                sub-0001_ses-01_acq-photo1_photo.jpg'`
-                **Talairach**: `'/derivatives/surfaces/sub-Talairach/ses-01/anat/
-                sub-Talairach_hemi-R_pial.surf.gii'`
-
-# Fields relating to the iEEG electrode positions
-iEEGCoordsystemPositions:
-    selectors:
-    - modality == "ieeg"
-    - datatype == "ieeg"
-    - suffix == "coordsystem"
-    fields:
-        iEEGCoordinateSystem: required
-        iEEGCoordinateUnits: required
-        iEEGCoordinateSystemDescription:
-            level: recommended
-            level_addendum: required if `iEEGCoordinateSystem` is `"Other"`
-        iEEGCoordinateProcessingDescription: recommended
-        iEEGCoordinateProcessingReference: recommended
-
-iEEGCoordsystemOther:
-    selectors:
-    - modality == "ieeg"
-    - datatype == "ieeg"
-    - suffix == "coordsystem"
-    - '"iEEGCoordinateSystem" in sidecar'
-    - sidecar.iEEGCoordinateSystem == "Other"
-    fields:
-        iEEGCoordinateSystemDescription: required
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/meg.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/meg.yaml
deleted file mode 100644
index 71de0f30a..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/meg.yaml
+++ /dev/null
@@ -1,261 +0,0 @@
-#
-# Groups of related metadata fields
-#
-# Assumptions: never need disjunction of selectors
-# Assumptions: top-to-bottom overrides is sufficient logic
-
-
----
-# Magnetoencephalography
-
-# Sidecar JSON (*_meg.json)
-MEGGeneric:
-    selectors:
-    - modality == "meg"
-    - datatype == "meg"
-    - suffix == "meg"
-    fields:
-        TaskName:
-            level: required
-            description_addendum: |
-                A recommended convention is to name resting state task using labels
-                beginning with `rest`.
-
-MEGRecommended:
-    selectors:
-    - modality == "meg"
-    - datatype == "meg"
-    - suffix == "meg"
-    fields:
-        InstitutionName: recommended
-        InstitutionAddress: recommended
-        InstitutionalDepartmentName: recommended
-        Manufacturer:
-            level: recommended
-            description_addendum: |
-                For MEG scanners, this must be one of:
-                `"CTF"`, `"Elekta/Neuromag"`, `"BTi/4D"`, `"KIT/Yokogawa"`,
-                `"ITAB"`, `"KRISS"`, `"Other"`.
-                See [Appendix VII](/99-appendices/07-meg-systems.html) for
-                preferred names.
-        ManufacturersModelName:
-            level: recommended
-            description_addendum: |
-                See [Appendix VII](/99-appendices/07-meg-systems.html) for
-                preferred names.
-        SoftwareVersions: recommended
-        TaskDescription: recommended
-        Instructions:
-            level: recommended
-            description_addendum: |
-                This is especially important in context of resting state recordings and
-                distinguishing between eyes open and eyes closed paradigms.
-        CogAtlasID: recommended
-        CogPOID: recommended
-        DeviceSerialNumber: recommended
-
-# Specific MEG fields MUST be present
-MEGRequired:
-    selectors:
-    - modality == "meg"
-    - datatype == "meg"
-    - suffix == "meg"
-    fields:
-        SamplingFrequency:
-            level: required
-            description_addendum: |
-                The sampling frequency of data channels that deviate from the main sampling
-                frequency SHOULD be specified in the `channels.tsv` file.
-        PowerLineFrequency: required
-        DewarPosition: required
-        SoftwareFilters: required
-        DigitizedLandmarks: required
-        DigitizedHeadPoints: required
-
-# Specific MEG fields SHOULD be present
-MEGMoreRecommended:
-    selectors:
-    - modality == "meg"
-    - datatype == "meg"
-    - suffix == "meg"
-    fields:
-        MEGChannelCount: recommended
-        MEGREFChannelCount: recommended
-        EEGChannelCount: recommended
-        ECOGChannelCount: recommended
-        SEEGChannelCount: recommended
-        EOGChannelCount: recommended
-        ECGChannelCount: recommended
-        EMGChannelCount: recommended
-        MiscChannelCount: recommended
-        TriggerChannelCount: recommended
-        RecordingDuration: recommended
-        RecordingType: recommended
-        EpochLength: recommended
-        ContinuousHeadLocalization: recommended
-        HeadCoilFrequency: recommended
-        MaxMovement: recommended
-        SubjectArtefactDescription: recommended
-        AssociatedEmptyRoom: recommended
-        HardwareFilters: recommended
-
-# Specific EEG fields
-# NOTE: I'm not sure if "EEG is present" is enough to indicate simultaneous EEG/MEG.
-MEGwithEEG:
-    selectors:
-    - modality == "meg"
-    - datatype == "meg"
-    - suffix == "meg"
-    - dataset.modalities.includes('"EEG")
-    fields:
-        EEGPlacementScheme: optional
-        CapManufacturer: optional
-        CapManufacturersModelName: optional
-        EEGReference: optional
-
-# MEG and EEG sensors
-MEGCoordsystemWithEEG:
-    selectors:
-    - modality == "meg"
-    - datatype == "meg"
-    - suffix == "coordsystem"
-    fields:
-        MEGCoordinateSystem: required
-        MEGCoordinateUnits: required
-        MEGCoordinateSystemDescription:
-            level: optional
-            level_addendum: required if `MEGCoordinateSystem` is `Other`
-        EEGCoordinateSystem:
-            level: optional
-            description_addendum: |
-                See [Recording EEG simultaneously with MEG]
-                (/04-modality-specific-files/02-magnetoencephalography.html#recording-eeg-simultaneously-with-meg).
-                Preferably the same as the `MEGCoordinateSystem`.
-        EEGCoordinateUnits: optional
-        EEGCoordinateSystemDescription:
-            level: optional
-            level_addendum: required if `EEGCoordinateSystem` is `Other`
-            description_addendum: |
-                See [Recording EEG simultaneously with MEG]
-                (/04-modality-specific-files/02-magnetoencephalography.html#recording-eeg-simultaneously-with-meg).
-
-# NOTE: The JSON isn't really a sidecar, so "sidecar.MEGCoordinateSystem" is misleading.
-MEGCoordsystemWithEEGMEGCoordinateSystem:
-    selectors:
-    - modality == "meg"
-    - datatype == "meg"
-    - suffix == "coordsystem"
-    - '"MEGCoordinateSystem" in sidecar'
-    - sidecar.MEGCoordinateSystem == "Other"
-    fields:
-        MEGCoordinateSystemDescription: required
-
-# NOTE: Not sure if this requires simult. EEG
-MEGCoordsystemWithEEGEEGCoordinateSystem:
-    selectors:
-    - modality == "meg"
-    - datatype == "meg"
-    - suffix == "coordsystem"
-    - '"EEGCoordinateSystem" in sidecar'
-    - sidecar.EEGCoordinateSystem == "Other"
-    fields:
-        EEGCoordinateSystemDescription: required
-
-# Head localization coils
-MEGCoordsystemHeadLocalizationCoils:
-    selectors:
-    - modality == "meg"
-    - datatype == "meg"
-    - suffix == "coordsystem"
-    fields:
-        HeadCoilCoordinates: optional
-        HeadCoilCoordinateSystem: optional
-        HeadCoilCoordinateUnits: optional
-        HeadCoilCoordinateSystemDescription:
-            level: optional
-            level_addendum: required if `HeadCoilCoordinateSystem` is `Other`
-
-MEGCoordsystemHeadLocalizationCoilsHeadCoilCoordinateSystem:
-    selectors:
-    - modality == "meg"
-    - datatype == "meg"
-    - suffix == "coordsystem"
-    - '"HeadCoilCoordinateSystem" in sidecar'
-    - sidecar.HeadCoilCoordinateSystem == "Other"
-    fields:
-        HeadCoilCoordinateSystemDescription: required
-
-# Digitized head points
-MEGCoordsystemDigitizedHeadPoints:
-    selectors:
-    - modality == "meg"
-    - datatype == "meg"
-    - suffix == "coordsystem"
-    fields:
-        DigitizedHeadPoints: optional
-        DigitizedHeadPointsCoordinateSystem: optional
-        DigitizedHeadPointsCoordinateUnits: optional
-        DigitizedHeadPointsCoordinateSystemDescription:
-            level: optional
-            level_addendum: required if `DigitizedHeadPointsCoordinateSystem` is `Other`
-
-MEGCoordsystemDigitizedHeadPointsDigitizedHeadPointsCoordinateSystem:
-    selectors:
-    - modality == "meg"
-    - datatype == "meg"
-    - suffix == "coordsystem"
-    - '"DigitizedHeadPointsCoordinateSystem" in sidecar'
-    - sidecar.DigitizedHeadPointsCoordinateSystem == "Other"
-    fields:
-        DigitizedHeadPointsCoordinateSystemDescription: required
-
-# Anatomical MRI
-MEGCoordsystemAnatomicalMRI:
-    selectors:
-    - modality == "meg"
-    - datatype == "meg"
-    - suffix == "coordsystem"
-    - dataset.modalities.includes("anat")
-    fields:
-        IntendedFor:
-            level: optional
-            description_addendum: |
-                This is used to identify the structural MRI(s),
-                possibly of different types if a list is specified,
-                to be used with the MEG recording.
-
-# Anatomical landmarks
-MEGCoordsystemAnatomicalLandmarks:
-    selectors:
-    - modality == "meg"
-    - datatype == "meg"
-    - suffix == "coordsystem"
-    fields:
-        AnatomicalLandmarkCoordinates: optional
-        AnatomicalLandmarkCoordinateSystem:
-            level: optional
-            description_addendum: |
-                Preferably the same as the `MEGCoordinateSystem`.
-        AnatomicalLandmarkCoordinateUnits: optional
-        AnatomicalLandmarkCoordinateSystemDescription:
-            level: optional
-            level_addendum: required if `AnatomicalLandmarkCoordinateSystem` is `Other`
-
-MEGCoordsystemAnatomicalLandmarksAnatomicalLandmarkCoordinateSystem:
-    selectors:
-    - modality == "meg"
-    - datatype == "meg"
-    - suffix == "coordsystem"
-    - '"AnatomicalLandmarkCoordinateSystem" in sidecar'
-    - sidecar.AnatomicalLandmarkCoordinateSystem == "Other"
-    fields:
-        AnatomicalLandmarkCoordinateSystemDescription: required
-
-# Fiducials information
-MEGCoordsystemFiducialsInformation:
-    selectors:
-    - modality == "meg"
-    - datatype == "meg"
-    - suffix == "coordsystem"
-    fields:
-        FiducialsDescription: optional
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/micr.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/micr.yaml
deleted file mode 100644
index 077dbbba6..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/micr.yaml
+++ /dev/null
@@ -1,79 +0,0 @@
-#
-# Groups of related metadata fields
-#
-# Assumptions: never need disjunction of selectors
-# Assumptions: top-to-bottom overrides is sufficient logic
-
-
----
-# Device Hardware
-MicroscopyDeviceHardware:
-    selectors:
-    - modality == "micr"
-    - datatype == "micr"
-    fields:
-        Manufacturer: recommended
-        ManufacturersModelName: recommended
-        DeviceSerialNumber: recommended
-        StationName: recommended
-        SoftwareVersions: recommended
-        InstitutionName: recommended
-        InstitutionAddress: recommended
-        InstitutionalDepartmentName: recommended
-
-# Image Acquisition
-MicroscopyImageAcquisition:
-    selectors:
-    - modality == "micr"
-    - datatype == "micr"
-    fields:
-        PixelSize: required
-        PixelSizeUnits: required
-        Immersion: optional
-        NumericalAperture: optional
-        Magnification: optional
-        ImageAcquisitionProtocol: optional
-        OtherAcquisitionParameters: optional
-
-# Sample
-MicroscopySample:
-    selectors:
-    - modality == "micr"
-    - datatype == "micr"
-    fields:
-        BodyPart:
-            level: recommended
-            description_addendum: |
-                From [DICOM Body Part Examined](http://dicom.nema.org/medical/dicom/current/
-                output/chtml/part16/chapter_L.html#chapter_L)
-                (for example `"BRAIN"`).
-        BodyPartDetails: recommended
-        BodyPartDetailsOntology: optional
-        SampleEnvironment: recommended
-        SampleEmbedding: optional
-        SampleFixation: optional
-        SampleStaining: recommended
-        SamplePrimaryAntibody: recommended
-        SampleSecondaryAntibody: recommended
-        SliceThickness: optional
-        TissueDeformationScaling: optional
-        SampleExtractionProtocol: optional
-        SampleExtractionInstitution: optional
-
-# Chunk Transformations
-MicroscopyChunkTransformations:
-    selectors:
-    - modality == "micr"
-    - datatype == "micr"
-    - '"chunk" in entities'
-    fields:
-        ChunkTransformationMatrix: recommended
-
-MicroscopyChunkTransformationsMatrixAxis:
-    selectors:
-    - modality == "micr"
-    - datatype == "micr"
-    - '"chunk" in entities'
-    - '"ChunkTransformationMatrix" in sidecar'
-    fields:
-        ChunkTransformationMatrixAxis: required
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/mri.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/mri.yaml
deleted file mode 100644
index 058e2dab0..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/mri.yaml
+++ /dev/null
@@ -1,263 +0,0 @@
-#
-# Groups of related metadata fields
-#
-# Assumptions: never need disjunction of selectors
-# Assumptions: top-to-bottom overrides is sufficient logic
-
-
----
-# MRI Common metadata fields
-MRIScannerHardware:
-    selectors:
-    - modality == "mri"
-    fields:
-        Manufacturer:
-            level: recommended
-            description_addendum: Corresponds to DICOM Tag 0008, 0070 `Manufacturer`.
-        ManufacturersModelName:
-            level: recommended
-            description_addendum: Corresponds to DICOM Tag 0008, 1090 `Manufacturers Model Name`.
-        DeviceSerialNumber:
-            level: recommended
-            description_addendum: Corresponds to DICOM Tag 0018, 1000 `DeviceSerialNumber`.
-        StationName:
-            level: recommended
-            description_addendum: Corresponds to DICOM Tag 0008, 1010 `Station Name`.
-        SoftwareVersions:
-            level: recommended
-            description_addendum: Corresponds to DICOM Tag 0018, 1020 `Software Versions`.
-        HardcopyDeviceSoftwareVersion: DEPRECATED
-        MagneticFieldStrength:
-            level: recommended, but required for Arterial Spin Labeling
-        ReceiveCoilName: recommended
-        ReceiveCoilActiveElements: recommended
-        GradientSetType: recommended
-        MRTransmitCoilSequence: recommended
-        MatrixCoilMode: recommended
-        CoilCombinationMethod: recommended
-
-MRISequenceSpecifics:
-    selectors:
-    - modality == "mri"
-    fields:
-        PulseSequenceType: recommended
-        ScanningSequence: recommended
-        SequenceVariant: recommended
-        ScanOptions: recommended
-        SequenceName: recommended
-        PulseSequenceDetails: recommended
-        NonlinearGradientCorrection: |
-            recommended, but required if [PET](./09-positron-emission-tomography.md) data are present
-        MRAcquisitionType: recommended, but required for Arterial Spin Labeling
-        MTState: recommended
-        MTOffsetFrequency: optional
-        MTPulseBandwidth: optional
-        MTNumberOfPulses: optional
-        MTPulseShape: optional
-        MTPulseDuration: optional
-        SpoilingState: recommended
-        SpoilingType: optional
-        SpoilingRFPhaseIncrement: optional
-        SpoilingGradientMoment: optional
-        SpoilingGradientDuration: optional
-
-PETMRISequenceSpecifics:
-    selectors:
-    - modality == "mri"
-    - dataset.modalities.includes("PET")
-    fields:
-        NonLinearGradientCorrection: required
-
-ASLMRISequenceSpecifics:
-    selectors:
-    - modality == "mri"
-    - datatype == "perf"
-    fields:
-        MRAcquisitionType: required
-
-MTParameters:
-    selectors:
-    - '"MTState" in sidecar'
-    - sidecar.MTState == "True"
-    fields:
-        MTOffsetFrequency: recommended
-        MTPulseBandwidth: recommended
-        MTNumberOfPulses: recommended
-        MTPulseShape: recommended
-        MTPulseDuration: recommended
-
-SpoilingType:
-    selectors:
-    - '"SpoilingState" in sidecar'
-    - sidecar.SpoilingState == true
-    fields:
-        SpoilingType: recommended
-
-SpoilingRF:
-    selectors:
-    - '"SpoilingType" in sidecar'
-    - '["RF", "COMBINED"].includes(sidecar.SpoilingType)'
-    fields:
-        SpoilingRFPhaseIncrement: recommended
-
-SpoilingGradient:
-    selectors:
-    - '"SpoilingType" in sidecar'
-    - '["GRADIENT", "COMBINED"].includes(sidecar.SpoilingType)'
-    fields:
-        SpoilingGradientMoment: recommended
-        SpoilingGradientDuration: recommended
-
-MRISpatialEncoding:
-    selectors:
-    - modality == "mri"
-    fields:
-        NumberShots: recommended
-        ParallelReductionFactorInPlane: recommended
-        ParallelAcquisitionTechnique: recommended
-        PartialFourier: recommended
-        PartialFourierDirection: recommended
-        PhaseEncodingDirection:
-            level: recommended
-            level_addendum: |
-                This parameter is required if corresponding fieldmap data is present
-                or when using multiple runs with different phase encoding directions
-                (which can be later used for field inhomogeneity correction).
-            issue:
-                name: PHASE_ENCODING_DIRECTION_MUST_DEFINE
-                issue: |
-                    You have to define 'PhaseEncodingDirection' for this file.
-        EffectiveEchoSpacing:
-            level: recommended
-            level_addendum: |
-                <sup>2</sup> This parameter is required if corresponding fieldmap data
-                is present.
-            issue:
-                name: EFFECTIVE_ECHO_SPACING_NOT_DEFINED
-                message: |
-                    You should define 'EffectiveEchoSpacing' for this file. If you don't
-                    provide this information field map correction will not be possible.
-        TotalReadoutTime:
-            level: recommended
-            level_addendum: |
-                <sup>3</sup> This parameter is required if corresponding 'field/distortion' maps
-                acquired with opposing phase encoding directions are present
-                (see [Case 4: Multiple phase encoded
-                directions](#case-4-multiple-phase-encoded-directions-pepolar)).
-            issue:
-                name: TOTAL_READOUT_TIME_MUST_DEFINE
-                message: |
-                    You have to define 'TotalReadoutTime' for this file.
-        MixingTime: recommended
-
-MRITimingParameters:
-    selectors:
-    - modality == "mri"
-    fields:
-        EchoTime:
-            level: recommended
-            level_addendum: |
-                required if corresponding fieldmap data is present,
-                or the data comes from a multi-echo sequence or Arterial Spin Labeling.
-            issue:
-                name: ECHO_TIME_NOT_DEFINED
-                message: |
-                    You must define 'EchoTime' for this file. 'EchoTime' is the echo time (TE)
-                    for the acquisition, specified in seconds. Corresponds to DICOM Tag
-                    0018, 0081 Echo Time (please note that the DICOM term is in milliseconds
-                    not seconds). The data type number may apply to files from any MRI modality
-                    concerned with a single value for this field, or to the files in a file
-                    collection where the value of this field is iterated using the echo entity.
-                    The data type array provides a value for each volume in a 4D dataset and
-                    should only be used when the volume timing is critical for interpretation
-                    of the data, such as in ASL or variable echo time fMRI sequences.
-        InversionTime: recommended
-        SliceTiming:
-            level: recommended
-            level_addendum: |
-                required for sparse sequences that do not have the `DelayTime` field set,
-                and Arterial Spin Labeling with `MRAcquisitionType` set on `2D`.
-        SliceEncodingDirection: recommended
-        DwellTime: recommended
-
-SliceTimingASL:
-    selectors:
-    - modality == "mri"
-    - datatype == "perf"
-    - '["asl", "m0scan"].includes(suffix)'
-    - '"MRAcquisitionType" in sidecar'
-    - sidecar.MRAcquisitionType == "2D"
-    fields:
-        SliceTiming: required
-
-# This is technically for sparse sequences only, but I don't know how to encode that.
-SliceTimingSparse:
-    selectors:
-    - modality == "mri"
-    - '"DelayTime" in sidecar'
-    fields:
-        SliceTiming: required
-
-MRIRFandContrast:
-    selectors:
-    - modality == "mri"
-    fields:
-        FlipAngle:
-            level: recommended
-            level_addendum: required if LookLocker is set to `true`.
-            issue:
-                name: LOOK_LOCKER_FLIP_ANGLE_MISSING
-                message: |
-                    You should define 'FlipAngle' for this file, in
-                    case of a LookLocker acquisition. 'FlipAngle' is the
-                    flip angle (FA) for the acquisition, specified in degrees.
-                    Corresponds to: DICOM Tag 0018, 1314 `Flip Angle`. The data
-                    type number may apply to files from any MRI modality concerned
-                    with a single value for this field, or to the files in a file
-                    collection where the value of this field is iterated using the
-                    flip entity. The data type array provides a value for each volume
-                    in a 4D dataset and should only be used when the volume timing is
-                    critical for interpretation of the data, such as in ASL or
-                    variable flip angle fMRI sequences.
-        NegativeContrast: optional
-
-MRIFlipAngleLookLocker:
-    selectors:
-    - modality == "mri"
-    - '"LookLocker" in sidecar'
-    - sidecar.LookLocker == True
-    fields:
-        FlipAngle: required
-
-MRISliceAcceleration:
-    selectors:
-    - modality == "mri"
-    fields:
-        MultibandAccelerationFactor: recommended
-
-MRIAnatomicalLandmarks:
-    selectors:
-    - modality == "mri"
-    fields:
-        AnatomicalLandmarkCoordinates__mri: recommended
-
-MRIEchoPlanarImagingAndB0Mapping:
-    selectors:
-    - modality == "mri"
-    fields:
-        B0FieldIdentifier: recommended
-        B0FieldSource: recommended
-
-MRIInstitutionInformation:
-    selectors:
-    - modality == "mri"
-    fields:
-        InstitutionName:
-            level: recommended
-            description_addendum: Corresponds to DICOM Tag 0008, 0080 `InstitutionName`.
-        InstitutionAddress:
-            level: recommended
-            description_addendum: Corresponds to DICOM Tag 0008, 0081 `InstitutionAddress`.
-        InstitutionalDepartmentName:
-            level: recommended
-            description_addendum: Corresponds to DICOM Tag 0008, 1040 `Institutional Department Name`.
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/pet.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/pet.yaml
deleted file mode 100644
index 6399eb5e6..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/sidecars/pet.yaml
+++ /dev/null
@@ -1,183 +0,0 @@
----
-# PET common metadata fields
-PETScannerHardware:
-    selectors:
-    - modality == "pet"
-    fields:
-        Manufacturer:
-            level: required
-            description_addendum: Corresponds to DICOM Tag 0008, 0070 `Manufacturer`.
-        ManufacturersModelName:
-            level: required
-            description_addendum: Corresponds to DICOM Tag 0008, 1090 `Manufacturers Model Name`.
-        Units:
-            level: required
-            description_addendum: |
-                SI unit for radioactivity (Becquerel) should be used (for example, "Bq/mL").
-                Corresponds to DICOM Tag 0054, 1001 `Units`.
-        InstitutionName:
-            level: recommended
-            description_addendum: Corresponds to DICOM Tag 0008, 0080 `InstitutionName`.
-        InstitutionAddress:
-            level: recommended
-            description_addendum: Corresponds to DICOM Tag 0008, 0081 `InstitutionAddress`.
-        InstitutionalDepartmentName:
-            level: recommended
-            description_addendum: Corresponds to DICOM Tag 0008, 1040 `Institutional Department Name`.
-        BodyPart:
-            level: recommended
-            description_addendum: Corresponds to DICOM Tag 0018, 0015 `Body Part Examined`.
-
-PETRadioChemistry:
-    selectors:
-    - modality == "pet"
-    fields:
-        TracerName:
-            level: required
-        TracerRadionuclide:
-            level: required
-        InjectedRadioactivity:
-            level: required
-        InjectedRadioactivityUnits:
-            level: required
-        InjectedMass:
-            level: required
-        InjectedMassUnits:
-            level: required
-        SpecificRadioactivity:
-            level: required
-        SpecificRadioactivityUnits:
-            level: required
-        ModeOfAdministration:
-            level: required
-        TracerRadLex:
-            level: recommended
-        TracerSNOMED:
-            level: recommended
-        TracerMolecularWeight:
-            level: recommended
-        TracerMolecularWeightUnits:
-            level: recommended
-        InjectedMassPerWeight:
-            level: recommended
-        InjectedMassPerWeightUnits:
-            level: recommended
-        SpecificRadioactivityMeasTime:
-            level: recommended
-        MolarActivity:
-            level: recommended
-        MolarActivityUnits:
-            level: recommended
-        MolarActivityMeasTime:
-            level: recommended
-        InfusionRadioactivity:
-            level: recommended
-            level_addendum: required if PETRadioChemistry.fields.ModeOfAdministration == 'bolus-infusion'
-        InfusionStart:
-            level: recommended
-            level_addendum: required if PETRadioChemistry.fields.ModeOfAdministration == 'bolus-infusion'
-        InfusionSpeed:
-            level: recommended
-            level_addendum: required if PETRadioChemistry.fields.ModeOfAdministration == 'bolus-infusion'
-        InfusionSpeedUnits:
-            level: recommended
-            level_addendum: required if PETRadioChemistry.fields.ModeOfAdministration == 'bolus-infusion'
-        InjectedVolume:
-            level: recommended
-            level_addendum: required if PETRadioChemistry.fields.ModeOfAdministration == 'bolus-infusion'
-        Purity:
-            level: recommended
-
-# PET Infusion conditionally required entities
-EntitiesBolusMetadata:
-    selectors:
-    - modality == "pet"
-    - sidecar.ModeOfAdministration == 'bolus-infusion'
-    fields:
-        InfusionRadioactivity:
-            level: required
-        InfusionStart:
-            level: required
-        InfusionSpeed:
-            level: required
-        InfusionSpeedUnits:
-            level: required
-        InjectedVolume:
-            level: required
-
-PETPharmaceuticals:
-    selectors:
-    - modality == "pet"
-    fields:
-        PharmaceuticalName:
-            level: recommended
-        PharmaceuticalDoseAmount:
-            level: recommended
-        PharmaCeuticalDoseUnits:
-            level: recommended
-        PharmaCeuticalDoseRegimen:
-            level: recommended
-        PharmaCeuticalDoseTime:
-            level: recommended
-        Anaesthesia:
-            level: optional
-
-PETTime:
-    selectors:
-    - modality == "pet"
-    fields:
-        TimeZero:
-            level: required
-        ScanStart:
-            level: required
-        InjectionStart:
-            level: required
-        FramesTimesStart:
-            level: required
-        FrameDuration:
-            level: required
-        InjectionEnd:
-            level: recommended
-        ScanDate:
-            level: deprecated
-
-PETReconstruction:
-    selectors:
-    - modality == "pet"
-    fields:
-        AcquisitionMode:
-            level: required
-        ImageDecayCorrected:
-            level: required
-        ImageDecayCorrectionTime:
-            level: required
-        ReconMethodName:
-            level: required
-        ReconMethodParameterLabels:
-            level: required
-        ReconMethodParameterUnits:
-            level: required
-        ReconMethodParameterValues:
-            level: required
-        ReconFilterType:
-            level: required
-        ReconFilterSize:
-            level: required
-        AttenuationCorrection:
-            level: required
-        ReconMethodImplementationVersion:
-            level: recommended
-        AttenuationCorrectionMethodReference:
-            level: recommended
-        ScaleFactor:
-            level: recommended
-        ScatterFraction:
-            level: recommended
-        DecayCorrectionFactor:
-            level: recommended
-        DoseCalibrationFactor:
-            level: recommended
-        PromptRate:
-            level: recommended
-        SinglesRate:
-            level: recommended
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/tabular_data/derivatives/common_derivatives.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/tabular_data/derivatives/common_derivatives.yaml
deleted file mode 100644
index 73df02e2d..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/tabular_data/derivatives/common_derivatives.yaml
+++ /dev/null
@@ -1,11 +0,0 @@
----
-SegmentationLookup:
-  selectors:
-  - dataset.DatasetType == "derivative"
-  - '["dseg", "probseg"].includes(suffix)'
-  columns:
-    index: REQUIRED
-    name: REQUIRED
-    abbreviation: OPTIONAL
-    color: OPTIONAL
-    mapping: OPTIONAL
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/tabular_data/eeg.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/tabular_data/eeg.yaml
deleted file mode 100644
index 742a6856e..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/tabular_data/eeg.yaml
+++ /dev/null
@@ -1,43 +0,0 @@
----
-EEGChannels:
-    selectors:
-    - datatype == "eeg"
-    - suffix == "channels"
-    - extension == ".tsv"
-    initial_columns:
-    - name__channels
-    - type__eeg_channels
-    - units
-    columns:
-        name__channels: required
-        type__eeg_channels: required
-        units: required
-        description: optional
-        sampling_frequency: optional
-        reference: optional
-        low_cutoff: optional
-        high_cutoff: optional
-        notch: optional
-        status: optional
-        status_descriptions: optional
-    additional_columns: allowed_if_defined
-
-EEGElectrodes:
-    selectors:
-    - datatype == "eeg"
-    - suffix == "electrodes"
-    - extension == ".tsv"
-    initial_columns:
-    - name__electrodes
-    - x
-    - y
-    - z
-    columns:
-        name__electrodes: required
-        x: required
-        y: required
-        z: required
-        type__electrodes: recommended
-        material: recommended
-        impedance: recommended
-    additional_columns: allowed_if_defined
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/tabular_data/ieeg.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/tabular_data/ieeg.yaml
deleted file mode 100644
index 36bde71c5..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/tabular_data/ieeg.yaml
+++ /dev/null
@@ -1,49 +0,0 @@
----
-iEEGChannels:
-    selectors:
-    - datatype == "ieeg"
-    - suffix == "channels"
-    - extension == ".tsv"
-    initial_columns:
-    - name__channels
-    - type__ieeg_channels
-    - units
-    columns:
-        name__channels: required
-        type__ieeg_channels: required
-        units: required
-        low_cutoff: required
-        high_cutoff: required
-        reference: optional
-        group: optional
-        sampling_frequency: optional
-        description: optional
-        notch: optional
-        status: optional
-        status_descriptions: optional
-    additional_columns: allowed_if_defined
-
-iEEGElectrodes:
-    selectors:
-    - datatype == "ieeg"
-    - suffix == "electrodes"
-    - extension == ".tsv"
-    initial_columns:
-    - name__electrodes
-    - x
-    - y
-    - z
-    columns:
-        name__electrodes: required
-        x: required
-        y: required
-        z: required
-        size: required
-        material: recommended
-        manufacturer: recommended
-        group: recommended
-        hemisphere: recommended
-        type__electrodes: optional
-        impedance: optional
-        dimension: optional
-    additional_columns: allowed_if_defined
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/tabular_data/meg.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/tabular_data/meg.yaml
deleted file mode 100644
index ed6aeda5c..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/tabular_data/meg.yaml
+++ /dev/null
@@ -1,23 +0,0 @@
----
-MEGChannels:
-    selectors:
-    - datatype == "meg"
-    - suffix == "channels"
-    - extension == ".tsv"
-    initial_columns:
-    - name__channels
-    - type__meg_channels
-    - units
-    columns:
-        name__channels: required
-        type__meg_channels: required
-        units: required
-        description: optional
-        sampling_frequency: optional
-        low_cutoff: optional
-        high_cutoff: optional
-        notch: optional
-        software_filters: optional
-        status: optional
-        status_descriptions: optional
-    additional_columns: allowed_if_defined
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/tabular_data/perf.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/tabular_data/perf.yaml
deleted file mode 100644
index 4ced4b5e7..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/tabular_data/perf.yaml
+++ /dev/null
@@ -1,8 +0,0 @@
----
-ASLContext:
-    selectors:
-    - datatype == "perf"
-    - suffix == "aslcontext"
-    columns:
-        volume_type: REQUIRED
-    additional_columns: not_allowed
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/tabular_data/pet.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/tabular_data/pet.yaml
deleted file mode 100644
index 7dfb2c051..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/tabular_data/pet.yaml
+++ /dev/null
@@ -1,52 +0,0 @@
----
-Blood:
-    selectors:
-    - modality == "pet"
-    - suffix == "blood"
-    - extension == ".tsv"
-    columns:
-        time: required
-        plasma_radioactivity: optional
-        metabolite_parent_fraction: optional
-        metabolite_polar_fraction: optional
-        hplc_recovery_fractions: optional
-        whole_blood_radioactivity: optional
-
-BloodPlasma:
-    selectors:
-    - modality == "pet"
-    - suffix == "blood"
-    - extension == ".tsv"
-    - '"PlasmaAvail" in sidecar'
-    columns:
-        plasma_radioactivity: required
-
-BloodMetabolite:
-    selectors:
-    - modality == "pet"
-    - suffix == "blood"
-    - extension == ".tsv"
-    - '"MetaboliteAvail" in sidecar'
-    columns:
-        metabolite_parent_fraction: required
-        metabolite_polar_fraction: recommended
-
-BloodMetaboliteCorrection:
-    selectors:
-    - modality == "pet"
-    - suffix == "blood"
-    - extension == ".tsv"
-    - '"MetaboliteRecoveryCorrectionApplied" in sidecar'
-    - sidecar.MetaboliteRecoveryCorrectionApplied == true
-    columns:
-        hplc_recovery_fractions: required
-
-BloodWholeBlood:
-    selectors:
-    - modality == "pet"
-    - suffix == "blood"
-    - extension == ".tsv"
-    - '"WholeBloodAvail" in sidecar'
-    - sidecar.WholeBloodAvail == true
-    columns:
-        whole_blood_radioactivity: required
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/tabular_data/physio.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/tabular_data/physio.yaml
deleted file mode 100644
index e8d122f6e..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/tabular_data/physio.yaml
+++ /dev/null
@@ -1,9 +0,0 @@
----
-PhysioColumns:
-    selectors:
-    - suffix == "physio"
-    columns:
-        cardiac: OPTIONAL
-        respiratory: OPTIONAL
-        trigger: OPTIONAL
-    additional_columns: allowed
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/tabular_data/task.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/tabular_data/task.yaml
deleted file mode 100644
index a714e7161..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/tabular_data/task.yaml
+++ /dev/null
@@ -1,15 +0,0 @@
----
-TaskEvents:
-    selectors:
-    - '"task" in entities'
-    - suffix == "events"
-    columns:
-        onset: REQUIRED
-        duration: REQUIRED
-        sample: OPTIONAL
-        trial_type: OPTIONAL
-        response_time: OPTIONAL
-        value: OPTIONAL
-        HED: OPTIONAL
-        stim_file: OPTIONAL
-    additional_columns: allowed
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/tabular_metadata.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/tabular_metadata.yaml
deleted file mode 100644
index 6b1ec9baa..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/tabular_metadata.yaml
+++ /dev/null
@@ -1,18 +0,0 @@
----
-scans:
-  suffixes:
-  - scans
-  extensions:
-  - .tsv
-  - .json
-  entities:
-    subject: required
-    session: optional  # session is required if session is present in the dataset.
-sessions:  # This file may only exist if session is present in the dataset.
-  suffixes:
-  - sessions
-  extensions:
-  - .tsv
-  - .json
-  entities:
-    subject: required
diff --git a/dandi/support/bids/schemadata/1.7.0+369/rules/top_level_files.yaml b/dandi/support/bids/schemadata/1.7.0+369/rules/top_level_files.yaml
deleted file mode 100644
index cc776648c..000000000
--- a/dandi/support/bids/schemadata/1.7.0+369/rules/top_level_files.yaml
+++ /dev/null
@@ -1,34 +0,0 @@
----
-README:
-  required: true
-  extensions:
-  - None
-  - .md
-  - .rst
-  - .txt
-CHANGES:
-  required: true
-  extensions:
-  - None
-LICENSE:
-  required: false
-  extensions:
-  - None
-dataset_description:
-  required: true
-  extensions:
-  - .json
-genetic_info:
-  required: false
-  extensions:
-  - .json
-participants:
-  required: false
-  extensions:
-  - .tsv
-  - .json
-samples:
-  required: false
-  extensions:
-  - .tsv
-  - .json
diff --git a/dandi/support/bids/utils.py b/dandi/support/bids/utils.py
deleted file mode 100644
index 2a7e4c536..000000000
--- a/dandi/support/bids/utils.py
+++ /dev/null
@@ -1,196 +0,0 @@
-"""
-THIS MODULE IS BUNDLED FROM THE bids-specification PACKAGE.
-Utility functions for the bids-specification schema.
-"""
-import logging
-import os.path as op
-from pprint import pprint
-
-import numpy as np
-
-
-def get_schema_path():
-    """Get the path to the schema folder.
-
-    Returns
-    -------
-    str
-        Absolute path to the folder containing schema-related files.
-    """
-    return op.abspath(op.join(op.dirname(__file__), "data", "schema"))
-
-
-def combine_extensions(lst):
-    """Combine extensions with their compressed versions in a list.
-
-    This is a basic solution to combining extensions with their
-    compressed versions in a list. Something more robust could
-    be written in the future.
-
-    Parameters
-    ----------
-    lst : list of str
-    """
-    new_lst = []
-    # First, sort by length
-    lst = sorted(lst, key=len)
-    for item in lst:
-        temp_lst = new_lst[:]
-
-        item_found = False
-        for j, new_item in enumerate(temp_lst):
-            if new_item in item:
-                temp_item = new_item + "[" + item.replace(new_item, "", 1) + "]"
-                new_lst[j] = temp_item
-                item_found = True
-
-        if not item_found:
-            new_lst.append(item)
-
-    return new_lst
-
-
-def get_logger(name=None):
-    """Return a logger to use.
-
-    Parameters
-    ----------
-    name : None or str, optional
-        Name of the logger. Defaults to None.
-
-    Returns
-    -------
-    logging.Logger
-        logger object.
-    """
-    return logging.getLogger("bids-schema" + (".%s" % name if name else ""))
-
-
-def set_logger_level(lgr, level):
-    """Set the logger level.
-
-    Parameters
-    ----------
-    lgr : logging.Logger
-        logger object for which to change the level.
-    level : int or str
-        The desired level for the logger.
-    """
-    if isinstance(level, int):
-        pass
-    elif level.isnumeric():
-        level = int(level)
-    elif level.isalpha():
-        level = getattr(logging, level)
-    else:
-        lgr.warning("Do not know how to treat loglevel %s" % level)
-        return
-    lgr.setLevel(level)
-
-
-def drop_unused_entities(df):
-    """Remove columns from a dataframe where all values in the column are NaNs.
-
-    For entity tables, this limits each table to only entities that are used
-    within the modality.
-
-    Parameters
-    ----------
-    df : pandas.DataFrame
-        DataFrame containing entities and datatypes/suffixes.
-        Rows are datatype/suffix combinations and columns are entities.
-
-    Returns
-    -------
-    df : pandas.DataFrame
-        DataFrame with columns associated with unused entities removed.
-    """
-    df = df.replace("", np.nan).dropna(axis=1, how="all").fillna("")
-    return df
-
-
-def flatten_multiindexed_columns(df):
-    """Remove multi-indexing of multi-indexed column headers.
-
-    The first layer is the "DataType", while the second layer is the "Format".
-    This second layer will become a new row.
-
-    Parameters
-    ----------
-    df : pandas.DataFrame
-        DataFrame with two header levels: "Datatype" and "Format".
-
-    Returns
-    -------
-    df : pandas.DataFrame
-        DataFrame with the second header level ("Format") converted to a
-        normal row.
-    """
-    # Flatten multi-index
-    vals = df.index.tolist()
-    df.loc["Format"] = df.columns.get_level_values(1)
-    df.columns = df.columns.get_level_values(0)
-    df = df.loc[["Format"] + vals]
-    df.index.name = "Entity"
-    df = df.drop(columns=["DataType"])
-    return df
-
-
-def get_link(string):
-    refs = {
-        "array": "https://www.w3schools.com/js/js_json_arrays.asp",
-        "string": "https://www.w3schools.com/js/js_json_datatypes.asp",
-        "number": "https://www.w3schools.com/js/js_json_datatypes.asp",
-        "object": "https://www.json.org/json-en.html",
-        "integer": "https://www.w3schools.com/js/js_json_datatypes.asp",
-        "boolean": "https://www.w3schools.com/js/js_json_datatypes.asp",
-    }
-    # Allow plurals (e.g., strings -> links to string)
-    dtype = string[:-1] if string[-1] == "s" else string
-    url = refs.get(dtype)
-    if url:
-        return f"[{string}]({url})"
-    return string
-
-
-def resolve_metadata_type(definition):
-    """Generate string of metadata type from dictionary.
-
-    Parameters
-    ----------
-    definition : :obj:`dict`
-        A schema object definition for a metadata term.
-
-    Returns
-    -------
-    string : :obj:`str`
-        A string describing the valid value types for the metadata term.
-    """
-    if "type" in definition.keys():
-        string = get_link(definition["type"])
-
-        if definition.get("enum") == ["n/a"]:
-            # Special string case of n/a
-            string = '`"n/a"`'
-
-        elif "type" in definition.get("items", {}):
-            # Items within arrays
-            string += " of " + get_link(definition["items"]["type"] + "s")
-
-        elif "type" in definition.get("additionalProperties", {}):
-            # Values within objects
-            string += " of " + get_link(definition["additionalProperties"]["type"] + "s")
-
-    elif "anyOf" in definition:
-        # Use dictionary to get unique substrings while preserving insertion order
-        substrings = {resolve_metadata_type(subdict): None for subdict in definition["anyOf"]}
-
-        string = " or ".join(substrings)
-
-    else:
-        # A hack to deal with $ref in the current schema
-        print(f"Type could not be inferred for {definition['name']}")
-        pprint(definition)
-        string = "unknown"
-
-    return string
diff --git a/dandi/support/bids/validator.py b/dandi/support/bids/validator.py
deleted file mode 100644
index 8c1768d47..000000000
--- a/dandi/support/bids/validator.py
+++ /dev/null
@@ -1,820 +0,0 @@
-from copy import deepcopy
-import datetime
-from functools import lru_cache
-import json
-import os
-from pathlib import Path
-import re
-
-from . import schema, utils
-
-lgr = utils.get_logger()
-
-# The list of which entities create directories could be dynamically specified by the YAML, but for
-# now, it is not.
-# Ordering is important, as "subject" follows "session" alphabetically, but is hierarchically
-# above it.
-DIR_ENTITIES = ["subject", "session"]
-
-
-def _get_paths(
-    bids_paths,
-    pseudofile_suffixes=[],
-):
-    """
-    Get all paths from a list of directories, excluding hidden subdirectories from distribution.
-
-    Parameters
-    ----------
-    bids_paths : list or str
-        Directories from which to get paths, may also contain file paths, which will remain
-        unchanged.
-    pseudofile_suffixes : list of str
-        Directory suffixes prompting the validation of the directory name and limiting further
-        directory walk.
-
-    Notes
-    -----
-    * Figure out how to return paths from BIDS root.
-    * Deduplicate paths (if input dirs are subsets of other input dirs), might best be done at the
-        very end.
-    * Specifying file paths currently breaks because they are truncated based on the bids_paths
-        input.
-    """
-    exclude_subdirs = [
-        ".dandi",
-        ".datalad",
-        ".git",
-    ]
-    # `.bidsignore` is not, in fact, a BIDS file, as per:
-    # https://github.com/bids-standard/bids-specification/issues/980
-    exclude_files = [
-        ".gitattributes",
-        ".gitignore",
-        ".bidsignore",
-        "dandiset.yaml",
-    ]
-
-    path_list = []
-    for bids_path in bids_paths:
-        bids_path = os.path.abspath(os.path.expanduser(bids_path))
-        if os.path.isfile(bids_path):
-            path_list.append(Path(bids_path).as_posix())
-            continue
-        for root, dirs, file_names in os.walk(bids_path, topdown=True):
-            if root.endswith(tuple(pseudofile_suffixes)):
-                # Add the directory name to the validation paths list.
-                path_list.append(Path(root).as_posix() + "/")
-                # Do not index the contents of the directory.
-                dirs[:] = []
-                file_names[:] = []
-            # will break if BIDS ever puts meaningful data under `/.{dandi,datalad,git}*/`
-            if os.path.basename(root) in exclude_subdirs:
-                continue
-            for file_name in file_names:
-                if file_name in exclude_files:
-                    continue
-                file_path = os.path.join(root, file_name)
-                # This will need to be replaced with bids root finding.
-                path_list.append(Path(file_path).as_posix())
-
-    return path_list
-
-
-def _add_entity(
-    regex_entities, entity, entity_shorthand, variable_field, requirement_level
-):
-    """Add entity pattern to filename template based on requirement level."""
-
-    # We need to do this here, although it would be easier to back-reference in the directory.
-    # This is because regex evaluates sequentially and we can not forward-reference a group.
-    if entity in DIR_ENTITIES:
-        variable_regex = f"(?P={entity})"
-    else:
-        variable_regex = f"(?P<{entity}>{variable_field})"
-
-    if requirement_level == "required":
-        if len(regex_entities.strip()):
-            regex_entities += f"_{entity_shorthand}-{variable_regex}"
-        else:
-            # Only the first entity doesn't need an underscore
-            regex_entities += f"{entity_shorthand}-{variable_regex}"
-    else:
-        if len(regex_entities.strip()):
-            regex_entities += f"(|_{entity_shorthand}-{variable_regex})"
-        else:
-            # Only the first entity doesn't need an underscore
-            regex_entities += f"(|{entity_shorthand}-{variable_regex})"
-
-    return regex_entities
-
-
-def _extension_safety(extension):
-    """
-    Making extensions formatting-safe.
-    Issues covered by this function are listed under “Notes”
-
-    Parameters
-    ----------
-    extension : str
-        Extension string, as present in the BIDS YAML schema.
-
-    Returns
-    -------
-    str
-        Extension string, safe for use in validator Regex formatting.
-
-    Notes
-    -----
-    * Bash-wildcard safety: https://github.com/bids-standard/bids-specification/issues/990
-    * Period safety: https://github.com/bids-standard/bids-specification/issues/1055
-    * Hopefully this function will be deprecated soon, but it will not break safe entries.
-    """
-    if extension == "None":
-        return ""
-    if "." in extension:
-        extension = extension.replace(".", "\\.")
-    if "*" in extension:
-        extension = extension.replace("*", ".*?")
-
-    return extension
-
-
-def _add_extensions(regex_string, variant):
-    """Add extensions to a regex string."""
-    fixed_variant_extensions = []
-    for variant_extension in variant["extensions"]:
-        variant_extension = _extension_safety(variant_extension)
-        fixed_variant_extensions.append(variant_extension)
-    if len(fixed_variant_extensions) > 1:
-        regex_extensions = "({})".format("|".join(fixed_variant_extensions))
-    else:
-        regex_extensions = fixed_variant_extensions[0]
-    regex_string = f"{regex_string}{regex_extensions}"
-
-    return regex_string
-
-
-def _add_subdirs(
-    regex_string,
-    variant,
-    datatype,
-    entity_definitions,
-    formats,
-    modality_datatypes,
-):
-    """Add appropriate subdirectories as required by entities present."""
-
-    regex_dirs = "/"
-    for dir_entity in DIR_ENTITIES:
-        if dir_entity in variant["entities"].keys():
-            format_selection = formats[entity_definitions[dir_entity]["format"]]
-            variable_field = f"({format_selection['pattern']})"
-            shorthand = entity_definitions[dir_entity]["name"]
-            if variant["entities"][dir_entity] == "required":
-                regex_subdir = f"{shorthand}-(?P<{dir_entity}>{variable_field})/"
-            else:
-                regex_subdir = f"(|{shorthand}-(?P<{dir_entity}>{variable_field})/)"
-            regex_dirs = f"{regex_dirs}{regex_subdir}"
-    if datatype in modality_datatypes:
-        regex_dirs = f"{regex_dirs}{datatype}/"
-    regex_string = f"{regex_dirs}{regex_string}"
-
-    return regex_string
-
-
-def _add_suffixes(regex_string, variant):
-    """Add suffixes to a regex string."""
-    if len(variant["suffixes"]) == 1:
-        regex_suffixes = variant["suffixes"][0]
-    else:
-        regex_suffixes = "({})".format("|".join(variant["suffixes"]))
-    regex_string = f"{regex_string}_{regex_suffixes}"
-
-    return regex_string
-
-
-def load_top_level(
-    my_schema,
-):
-    """
-    Create full path regexes for top level files, as documented by a target BIDS YAML schema
-    version.
-
-
-    Parameters
-    ----------
-    my_schema : dict
-        A nested dictionary, as returned by `bidsschematools.schema.load_schema()`.
-
-    Returns
-    -------
-    regex_schema : list of dict
-        A list of dictionaries, with keys including 'regex' and 'mandatory'.
-    """
-
-    top_level_files = my_schema["rules"]["top_level_files"]
-
-    regex_schema = []
-    for top_level_filename in top_level_files.keys():
-        top_level_file = top_level_files[top_level_filename]
-        # None value gets passed as list of strings...
-        extensions = top_level_file["extensions"]
-        if extensions != ["None"]:
-            extensions_regex = "|".join(map(_extension_safety, extensions))
-            regex = f".*?/{top_level_filename}({extensions_regex})$"
-        else:
-            regex = f".*?/{top_level_filename}$"
-        regex_entry = {
-            "regex": regex,
-            "mandatory": top_level_file["required"],
-        }
-        regex_schema.append(regex_entry)
-
-    return regex_schema
-
-
-def load_entities(
-    my_schema,
-):
-    """Create full path regexes for entities, as documented by a target BIDS YAML schema version.
-
-    Parameters
-    ----------
-    my_schema : dict
-        A nested dictionary, as returned by `bidsschematools.schema.load_schema()`.
-
-    Notes
-    -----
-
-    * Suggest to BIDS-specification to remove the periods from the extensions, the leading period
-        is not part of the extension, but a delimiter defining the fact that it's an extension.
-        Code sections marked as `Making it period-safe` should be edited when this fix is in,
-        though they will work in any case.
-        https://github.com/bids-standard/bids-specification/issues/990
-    * More issues in comments.
-    * Using pre 3.8 string formatting for legibility.
-
-    Returns
-    -------
-    regex_schema : list of dict
-        A list of dictionaries, with keys including 'regex' and 'mandatory'.
-    """
-
-    # Parsing tabular_metadata as a datatype, might be done automatically if the YAML is moved
-    # to the same subdirectory
-    my_schema["rules"]["datatypes"]["tabular_metadata"] = my_schema["rules"][
-        "tabular_metadata"
-    ]
-    datatypes = my_schema["rules"]["datatypes"]
-    entity_order = my_schema["rules"]["entities"]
-    entity_definitions = my_schema["objects"]["entities"]
-    formats = my_schema["objects"]["formats"]
-
-    # Descriptions are not needed and very large.
-    for i in entity_definitions.values():
-        i.pop("description", None)
-
-    # Needed for non-modality file separation as per:
-    # https://github.com/bids-standard/bids-specification/pull/985#issuecomment-1019573787
-    modalities = my_schema["rules"]["modalities"]
-    modality_datatypes = []
-    for modality_key in modalities.keys():
-        for modality_datatype in modalities[modality_key]["datatypes"]:
-            modality_datatypes.append(modality_datatype)
-
-    regex_schema = []
-    for datatype in datatypes:
-        for variant in datatypes[datatype].values():
-            regex_entities = ""
-            for entity in entity_order:
-                # Slightly awkward construction to account for new-style file specification.
-                # As in:
-                # https://github.com/bids-standard/bids-specification/pull/987
-                try:
-                    if entity in variant["entities"]:
-                        entity_shorthand = entity_definitions[entity]["name"]
-                        if "enum" in entity_definitions[entity].keys():
-                            # Entity key-value pattern with specific allowed values
-                            # tested, works!
-                            variable_field = "({})".format(
-                                "|".join(entity_definitions[entity]["enum"]),
-                            )
-                        else:
-                            format_selection = formats[
-                                entity_definitions[entity]["format"]
-                            ]
-                            variable_field = f"({format_selection['pattern']})"
-                        regex_entities = _add_entity(
-                            regex_entities,
-                            entity,
-                            entity_shorthand,
-                            variable_field,
-                            variant["entities"][entity],
-                        )
-                except KeyError:
-                    pass
-
-            regex_string = _add_suffixes(regex_entities, variant)
-            regex_string = _add_extensions(regex_string, variant)
-            regex_string = _add_subdirs(
-                regex_string,
-                variant,
-                datatype,
-                entity_definitions,
-                formats,
-                modality_datatypes,
-            )
-
-            regex_string = f".*?{regex_string}$"
-            regex_entry = {
-                "regex": regex_string,
-                "mandatory": False,
-            }
-            regex_schema.append(regex_entry)
-
-    return regex_schema
-
-
-@lru_cache()
-def load_all(
-    schema_dir,
-):
-    """
-    Create full path regexes for all BIDS specification files.
-
-    Parameters
-    ----------
-    schema_dir : str, optional
-        A string pointing to a BIDS directory for which paths should be validated.
-
-    Returns
-    -------
-    all_regex : list of dict
-        A list of dictionaries, with keys including 'regex' and 'mandatory'.
-    my_schema : list of dict
-        Nested dictionaries representing the full schema.
-    """
-
-    my_schema = schema.load_schema(schema_dir)
-    all_regex = load_entities(
-        my_schema=my_schema,
-    )
-    top_level_regex = load_top_level(
-        my_schema=my_schema,
-    )
-    all_regex.extend(top_level_regex)
-
-    return all_regex, my_schema
-
-
-def validate_all(
-    bids_paths,
-    regex_schema,
-    debug=False,
-    pseudofile_suffixes=[],
-):
-    """
-    Validate `bids_paths` based on a `regex_schema` dictionary list, including regexes.
-
-    Parameters
-    ----------
-    bids_paths : list or str
-        A string pointing to a BIDS directory for which paths should be validated.
-    regex_schema : list of dict
-        A list of dictionaries as generated by `load_all()`.
-    debug : tuple, optional
-        Whether to print itemwise notices for checks on the console, and include them in the
-        validation result.
-    pseudofile_suffixes : list of str, optional
-        Any suffixes which identify BIDS-valid directory data.
-        These pseudo-file suffixes will be validated based on the directory name, with the
-        directory contents not being indexed for validation.
-        By default, no pseudo-file suffixes are checked.
-
-    Returns
-    -------
-    results : dict
-        A dictionary reporting the target files for validation, the unmatched files and unmatched
-        regexes, and optionally the itemwise comparison results.
-        Keys include "schema_tracking", "path_tracking", "path_listing", "match_listing", and
-        optionally "itemwise"
-
-    Notes
-    -----
-    * Multi-source validation could be accomplished by distributing the resulting tracking_schema
-        dictionary and further eroding it.
-    * Currently only entities are captured in named groups, edit `load_top_level()` to name other
-        groups as well.
-    """
-
-    tracking_schema = deepcopy(regex_schema)
-    paths_list = _get_paths(bids_paths, pseudofile_suffixes=pseudofile_suffixes)
-    tracking_paths = deepcopy(paths_list)
-    if debug:
-        itemwise_results = []
-    matched = False
-    match_listing = []
-    for target_path in paths_list:
-        if debug:
-            print(f"Checking file `{target_path}`.")
-            print("Trying file types:")
-        for regex_entry in tracking_schema:
-            target_regex = regex_entry["regex"]
-            if debug:
-                print(f"\t* {target_path}, with pattern: {target_regex}")
-            matched = re.match(target_regex, target_path)
-            if debug:
-                itemwise_result = {}
-                itemwise_result["path"] = target_path
-                itemwise_result["regex"] = target_regex
-            if matched:
-                if debug:
-                    print("Match identified.")
-                    itemwise_result["match"] = True
-                    itemwise_results.append(itemwise_result)
-                break
-            if debug:
-                itemwise_result["match"] = False
-                itemwise_results.append(itemwise_result)
-        if matched:
-            tracking_paths.remove(target_path)
-            # Might be fragile since it relies on where the loop broke:
-            if regex_entry["mandatory"]:
-                tracking_schema.remove(regex_entry)
-            match_entry = matched.groupdict()
-            match_entry["path"] = target_path
-            match_listing.append(match_entry)
-        else:
-            if debug:
-                print(
-                    f"The `{target_path}` file could not be matched to any regex schema entry."
-                )
-    results = {}
-    if debug:
-        results["itemwise"] = itemwise_results
-    results["schema_tracking"] = tracking_schema
-    results["schema_listing"] = regex_schema
-    results["path_tracking"] = tracking_paths
-    results["path_listing"] = paths_list
-    results["match_listing"] = match_listing
-
-    return results
-
-
-def write_report(
-    validation_result,
-    report_path="/var/tmp/bids-validator/report_{datetime}-{pid}.log",
-    datetime_format="%Y%m%d%H%M%SZ",
-):
-    """Write a human-readable report based on the validation result.
-
-    Parameters
-    ----------
-    validation_result : dict
-        A dictionary as returned by `validate_all()` with keys including "schema_tracking",
-        "path_tracking", "path_listing", and, optionally "itemwise".
-        The "itemwise" value, if present, should be a list of dictionaries, with keys including
-        "path", "regex", and "match".
-    report_path : str, optional
-        A path under which the report is to be saved, `datetime`, and `pid`
-        are available as variables for string formatting, and will be expanded to the
-        current datetime (as per the `datetime_format` parameter) and process ID, respectively.
-    datetime_format : str, optional
-        A datetime format, optionally used for the report path.
-
-    Notes
-    -----
-    * Not using f-strings in order to prevent arbitrary code execution.
-    """
-
-    report_path = report_path.format(
-        datetime=datetime.datetime.utcnow().strftime(datetime_format),
-        pid=os.getpid(),
-    )
-    report_path = os.path.abspath(os.path.expanduser(report_path))
-    try:
-        os.makedirs(os.path.dirname(report_path))
-    except OSError:
-        pass
-
-    total_file_count = len(validation_result["path_listing"])
-    validated_files_count = total_file_count - len(validation_result["path_tracking"])
-    with open(report_path, "w") as f:
-        try:
-            for comparison in validation_result["itemwise"]:
-                if comparison["match"]:
-                    comparison_result = "A MATCH"
-                else:
-                    comparison_result = "no match"
-                f.write(
-                    f'- Comparing the `{comparison["path"]}` path to the `{comparison["regex"]}` '
-                    f"pattern resulted in {comparison_result}.\n"
-                )
-        except KeyError:
-            pass
-        f.write(
-            f"\nSUMMARY:\n{validated_files_count} out of {total_file_count} files were "
-            "successfully validated, using the following regular expressions:"
-        )
-        for regex_entry in validation_result["schema_listing"]:
-            f.write(f'\n\t- `{regex_entry["regex"]}`')
-        f.write("\n")
-        if len(validation_result["path_tracking"]) > 0:
-            f.write("The following files were not matched by any regex schema entry:")
-            f.write("\n\t* `")
-            f.write("`\n\t* `".join(validation_result["path_tracking"]))
-        else:
-            f.write("All files were matched by a regex schema entry.")
-        if len(validation_result["schema_tracking"]) > 0:
-            f.write(
-                "\nThe following mandatory regex schema entries did not match any files:"
-            )
-            f.write("\n")
-            for entry in validation_result["schema_tracking"]:
-                if entry["mandatory"]:
-                    f.write(f'\t** `{entry["regex"]}`\n')
-        else:
-            f.write("All mandatory BIDS files were found.\n")
-        f.close()
-    lgr.info("BIDS validation log written to %s", report_path)
-
-
-def _find_dataset_description(my_path):
-    candidate = os.path.join(my_path, "dataset_description.json")
-    # Windows support... otherwise we could do `if my_path == "/"`.
-    if my_path == "/" or not any(i in my_path for i in ["/", "\\"]):
-        return None
-    if os.path.isfile(candidate):
-        return candidate
-    else:
-        level_up = os.path.dirname(my_path.rstrip("/\\"))
-        return _find_dataset_description(level_up)
-
-
-def select_schema_dir(
-    bids_paths,
-    schema_reference_root,
-    schema_version,
-    schema_min_version="1.7.0+369",
-):
-    """
-    Select schema directory, according to a fallback logic whereby the schema path is
-    either (1) `schema_version` if the value is a path, (2) a concatenation of
-    `schema_reference_root` and `schema_version`, (3) a concatenation of the detected
-    version specification from a `dataset_description.json` file if one is found in
-    parents of the input path, (4) `schema_min_version` if no other version can be found
-    or if the detected version from `dataset_description.json` is smaller than
-    `schema_min_version`.
-
-    Parameters
-    ----------
-    bids_paths : list of str
-        Paths to be validated.
-        Entries in this list will be used to crawl the directory tree upwards until a
-        dataset_description.json file is found.
-    schema_reference_root : str, optional
-        Path where schema versions are stored, and which contains directories named exactly
-        according to the respective schema version, e.g. "1.7.0".
-        If the path starts with the string "{module_path}" it will be expanded relative to the
-        module path.
-    schema_version : str or None, optional
-        Version of BIDS schema, or path to schema.
-        If a path is given, this will be expanded and used directly, not concatenated with
-        `schema_reference_root`.
-        If the path starts with the string "{module_path}" it will be expanded relative to the
-        module path.
-        If None, the `dataset_description.json` fie will be queried for the dataset schema version.
-    schema_min_version : str, optional
-        Minimal version to use UNLESS the schema version is manually specified.
-        If the version is auto-detected and the version is smaller than schema_min_version,
-        schema_min_version will be selected instead.
-
-    Returns
-    -------
-
-    """
-    # Expand module_path
-    module_path = os.path.abspath(os.path.dirname(__file__))
-    if schema_reference_root.startswith("{module_path}"):
-        schema_reference_root = schema_reference_root.format(module_path=module_path)
-    schema_reference_root = os.path.abspath(os.path.expanduser(schema_reference_root))
-    if schema_version:
-        if "/" in schema_version:
-            schema_dir = schema_version
-            if schema_version.startswith("{module_path}"):
-                schema_dir = schema_version.format(module_path=module_path)
-            schema_dir = os.path.abspath(os.path.expanduser(schema_dir))
-            return schema_dir
-        schema_dir = os.path.join(schema_reference_root, schema_version)
-        return schema_dir
-    dataset_descriptions = []
-    for bids_path in bids_paths:
-        bids_path = os.path.abspath(os.path.expanduser(bids_path))
-        dataset_description = _find_dataset_description(bids_path)
-        if dataset_description:
-            if dataset_description in dataset_descriptions:
-                raise ValueError(
-                    "You have selected files belonging to 2 different datasets. "
-                    "Please run the validator once per dataset."
-                )
-            else:
-                with open(dataset_description) as f:
-                    try:
-                        dataset_info = json.load(f)
-                    except json.decoder.JSONDecodeError:
-                        lgr.error(
-                            "The `%s` file could not be loaded. "
-                            "Please check whether the file is valid JSON. "
-                            "Falling back to the %s BIDS version.",
-                            dataset_description,
-                            schema_min_version,
-                        )
-                        schema_version = schema_min_version
-                    else:
-                        try:
-                            schema_version = dataset_info["BIDSVersion"]
-                        except KeyError:
-                            lgr.warning(
-                                "BIDSVersion is not specified in "
-                                "`dataset_description.json`. "
-                                "Falling back to %s.",
-                                schema_min_version,
-                            )
-                            schema_version = schema_min_version
-        if not schema_version:
-            lgr.warning(
-                "No BIDSVersion could be found for the dataset. Falling back to %s.",
-                schema_min_version,
-            )
-            schema_version = schema_min_version
-        elif schema_min_version:
-            if schema_version < schema_min_version:
-                lgr.warning(
-                    "BIDSVersion %s is less than the minimal working "
-                    "%s. "
-                    "Falling back to %s. "
-                    "To force the usage of earlier versions specify them explicitly "
-                    "when calling the validator.",
-                    schema_version,
-                    schema_min_version,
-                    schema_min_version,
-                )
-                schema_version = schema_min_version
-    schema_dir = os.path.join(schema_reference_root, schema_version)
-    if os.path.isdir(schema_dir):
-        return schema_dir
-    else:
-        raise ValueError(
-            f"The expected schema directory {schema_dir} does not exist on the system. "
-            "Please ensure the file exists or manually specify a schema version for "
-            "which the bidsschematools files are available on your system."
-        )
-
-
-def log_errors(validation_result):
-    """
-    Raise errors for validation result.
-
-    Parameters
-    ----------
-    validation_result : dict
-        A dictionary as returned by `validate_all()` with keys including "schema_tracking",
-        "path_tracking", "path_listing", and, optionally "itemwise".
-        The "itemwise" value, if present, should be a list of dictionaries, with keys including
-        "path", "regex", and "match".
-    """
-    total_file_count = len(validation_result["path_listing"])
-    validated_files_count = total_file_count - len(validation_result["path_tracking"])
-    if validated_files_count == 0:
-        lgr.error("No valid BIDS files were found.")
-    for entry in validation_result["schema_tracking"]:
-        if entry["mandatory"]:
-            lgr.error(
-                "The `%s` regex pattern file required by BIDS was not found.",
-                entry["regex"],
-            )
-    for i in validation_result["path_tracking"]:
-        lgr.warning("The `%s` file was not matched by any regex schema entry.", i)
-
-
-def _get_directory_suffixes(my_schema):
-    """Query schema for suffixes which identify directory entities.
-
-    Parameters
-    ----------
-    my_schema : dict
-        Nested directory as produced by `bidsschematools.schema.load_schema()`.
-
-    Returns
-    -------
-    list of str
-        Directory pseudofile suffixes excluding trailing slashes.
-
-    Notes
-    -----
-    * Yes this seems super-awkward to do explicitly, after all, the trailing slash is
-        already in so it should automagically work, but no:
-        - Subdirectory names need to be dynamically excluded from validation input.
-        - Backslash directory delimiters are still in use, which is regrettable.
-    """
-    pseudofile_suffixes = []
-    for i in my_schema["objects"]["extensions"].values():
-        i_value = i["value"]
-        if i_value.endswith("/") and i_value != "/":
-            pseudofile_suffixes.append(i_value[:-1])
-    return pseudofile_suffixes
-
-
-def validate_bids(
-    bids_paths,
-    schema_reference_root="/usr/share/bids-schema/",
-    schema_version=None,
-    debug=False,
-    report_path=False,
-    suppress_errors=False,
-):
-    """
-    Validate paths according to BIDS schema.
-
-    Parameters
-    ----------
-    paths : str or list of str
-        Paths which to validate, may be individual files or directories.
-    schema_reference_root : str, optional
-        Path where schema versions are stored, and which contains directories named exactly
-        according to the respective schema version, e.g. "1.7.0".
-        If the path starts with the string "{module_path}" it will be expanded relative to the
-        module path.
-    schema_version : str or None, optional
-        Version of BIDS schema, or path to schema.
-        If a path is given, this will be expanded and used directly, not concatenated with
-        `schema_reference_root`.
-        If the path starts with the string "{module_path}" it will be expanded relative to the
-        module path.
-        If None, the `dataset_description.json` fie will be queried for the dataset schema version.
-    report_path : bool or str, optional
-        If `True` a log will be written using the standard output path of `.write_report()`.
-        If string, the string will be used as the output path.
-        If the variable evaluates as False, no log will be written.
-
-    Returns
-    -------
-    results : dict
-        A dictionary reporting the target files for validation, the unmatched files and unmatched
-        regexes, and optionally the itemwise comparison results.
-        Keys include "schema_tracking", "path_tracking", "path_listing", "match_listing", and
-        optionally "itemwise"
-
-    Examples
-    --------
-    >>> from bidsschematools import validator
-    >>> bids_paths = '~/.data2/datalad/000026/rawdata'
-    >>> schema_version='{module_path}/data/schema/'
-    >>> validator.validate_bids(bids_paths, schema_version=schema_version, debug=False)"
-
-    Notes
-    -----
-    * Needs to account for inheritance principle, probably somewhere deeper in the logic, might be
-        as simple as pattern parsing and multiplying patterns to which inheritance applies.
-        https://github.com/bids-standard/bids-specification/pull/969#issuecomment-1132119492
-    """
-
-    if isinstance(bids_paths, str):
-        bids_paths = [bids_paths]
-
-    bids_schema_dir = select_schema_dir(
-        bids_paths, schema_reference_root, schema_version
-    )
-    regex_schema, my_schema = load_all(bids_schema_dir)
-    pseudofile_suffixes = _get_directory_suffixes(my_schema)
-    validation_result = validate_all(
-        bids_paths,
-        regex_schema,
-        debug=debug,
-        pseudofile_suffixes=pseudofile_suffixes,
-    )
-
-    # Record schema version.
-    # Not sure whether to incorporate in validation_result.
-    if bids_schema_dir == os.path.join(
-        os.path.abspath(os.path.dirname(__file__)),
-        "data",
-        "schema",
-    ):
-        # Declare we are using live version,
-        # string will evaluate as larger than numbered versions.
-        schema_version = "99999.0.0"
-    else:
-        _, schema_version = os.path.split(bids_schema_dir)
-    validation_result["bids_schema_version"] = schema_version
-
-    log_errors(validation_result)
-
-    if report_path:
-        if isinstance(report_path, str):
-            write_report(validation_result, report_path=report_path)
-        else:
-            write_report(validation_result)
-
-    return validation_result
diff --git a/dandi/tests/data/expected_bids_validator_xs_write.log b/dandi/tests/data/expected_bids_validator_xs_write.log
deleted file mode 100644
index e8daa5537..000000000
--- a/dandi/tests/data/expected_bids_validator_xs_write.log
+++ /dev/null
@@ -1,7 +0,0 @@
-
-SUMMARY:
-0 out of 1 files were successfully validated, using the following regular expressions:
-	- `.*?/sub-(?P<subject>([a-zA-Z0-9]*?))/(|ses-(?P<session>([a-zA-Z0-9]*?))/)anat/sub-(?P=subject)(|_ses-(?P=session))(|_acq-(?P<acquisition>([a-zA-Z0-9]*?)))(|_ce-(?P<ceagent>([a-zA-Z0-9]*?)))(|_rec-(?P<reconstruction>([a-zA-Z0-9]*?)))(|_run-(?P<run>([a-zA-Z0-9]*?)))(|_part-(?P<part>(mag|phase|real|imag)))_(T1w|T2w|PDw|T2starw|FLAIR|inplaneT1|inplaneT2|PDT2|angio|T2star)\.(nii.gz|nii|json)$`
-The following files were not matched by any regex schema entry:
-	* `/home/chymera/.data2/datalad/000026/rawdata/sub-EXC022/anat/sub-EXC022_ses-MRI_flip-1_VFA.nii.gz
-The following mandatory regex schema entries did not match any files:
diff --git a/dandi/tests/test_bids_validator_xs.py b/dandi/tests/test_bids_validator_xs.py
deleted file mode 100644
index 19b19fba3..000000000
--- a/dandi/tests/test_bids_validator_xs.py
+++ /dev/null
@@ -1,371 +0,0 @@
-import os
-
-BIDS_EXAMPLES_WHITELIST = [
-    "asl003",
-    "eeg_cbm",
-    "hcp_example_bids",
-    "micr_SEM",
-    "micr_SEMzarr",
-    "micr_SPIM",
-    "pet001",
-    "pet003",
-    "qmri_tb1tfl",
-    "qmri_vfa/derivatives/qMRLab",
-]
-BIDS_EXAMPLES_BLACKLIST = [
-    "invalid_pet001",
-]
-
-TEST_SCHEMA_PATH = "{module_path}/schemadata/1.7.0+369"
-
-
-def test__add_entity():
-    from ..support.bids.validator import _add_entity
-
-    # Test empty input and directory creation and required entity
-    regex_entities = ""
-    entity = "subject"
-    entity_shorthand = "sub"
-    variable_field = "([a-zA-Z0-9]*?)"
-    requirement_level = "required"
-
-    _regex_entities = _add_entity(
-        regex_entities,
-        entity,
-        entity_shorthand,
-        variable_field,
-        requirement_level,
-    )
-
-    assert _regex_entities == "sub-(?P=subject)"
-
-    # Test append input and optional entity
-    regex_entities = (
-        "sub-(?P=subject)(|_ses-(?P=session))"
-        "(|_task-(?P<task>([a-zA-Z0-9]*?)))(|_trc-(?P<tracer>([a-zA-Z0-9]*?)))"
-        "(|_rec-(?P<reconstruction>([a-zA-Z0-9]*?)))"
-        "(|_run-(?P<run>([a-zA-Z0-9]*?)))"
-    )
-    entity = "recording"
-    entity_shorthand = "recording"
-    variable_field = "([a-zA-Z0-9]*?)"
-    requirement_level = "optional"
-
-    _regex_entities = _add_entity(
-        regex_entities,
-        entity,
-        entity_shorthand,
-        variable_field,
-        requirement_level,
-    )
-
-    assert (
-        _regex_entities == "sub-(?P=subject)(|_ses-(?P=session))"
-        "(|_task-(?P<task>([a-zA-Z0-9]*?)))(|_trc-(?P<tracer>([a-zA-Z0-9]*?)))"
-        "(|_rec-(?P<reconstruction>([a-zA-Z0-9]*?)))"
-        "(|_run-(?P<run>([a-zA-Z0-9]*?)))"
-        "(|_recording-(?P<recording>([a-zA-Z0-9]*?)))"
-    )
-
-
-def test__add_extensions():
-    from ..support.bids.validator import _add_extensions
-
-    # Test single extension
-    regex_string = (
-        "sub-(?P=subject)(|_ses-(?P=session))"
-        "_sample-(?P<sample>([a-zA-Z0-9]*?))"
-        "(|_acq-(?P<acquisition>([a-zA-Z0-9]*?)))_photo"
-    )
-    variant = {
-        "suffixes": ["photo"],
-        "extensions": [".jpg"],
-        "entities": {
-            "subject": "required",
-            "session": "optional",
-            "sample": "required",
-            "acquisition": "optional",
-        },
-    }
-    _regex_string = _add_extensions(regex_string, variant)
-
-    assert (
-        _regex_string == "sub-(?P=subject)(|_ses-(?P=session))"
-        "_sample-(?P<sample>([a-zA-Z0-9]*?))"
-        "(|_acq-(?P<acquisition>([a-zA-Z0-9]*?)))_photo\\.jpg"
-    )
-
-    # Test multiple extensions
-    regex_string = (
-        "sub-(?P=subject)(|_ses-(?P=session))"
-        "_sample-(?P<sample>([a-zA-Z0-9]*?))"
-        "(|_acq-(?P<acquisition>([a-zA-Z0-9]*?)))_photo"
-    )
-    variant = {
-        "suffixes": ["photo"],
-        "extensions": [".jpg", ".png", ".tif"],
-        "entities": {
-            "subject": "required",
-            "session": "optional",
-            "sample": "required",
-            "acquisition": "optional",
-        },
-    }
-    _regex_string = _add_extensions(regex_string, variant)
-
-    assert (
-        _regex_string == "sub-(?P=subject)(|_ses-(?P=session))"
-        "_sample-(?P<sample>([a-zA-Z0-9]*?))"
-        "(|_acq-(?P<acquisition>([a-zA-Z0-9]*?)))"
-        "_photo(\\.jpg|\\.png|\\.tif)"
-    )
-
-
-def test__add_subdirs():
-    from ..support.bids.validator import _add_subdirs
-
-    regex_string = "sub-(?P=subject)_sessions\\.(tsv|json)"
-    variant = {
-        "suffixes": ["sessions"],
-        "extensions": [".tsv", ".json"],
-        "entities": {"subject": "required"},
-    }
-    datatype = "tabular_metadata"
-    entity_definitions = {
-        "acquisition": {
-            "display_name": "Acquisition",
-            "name": "acq",
-            "type": "string",
-            "format": "label",
-        },
-        "session": {
-            "display_name": "Session",
-            "name": "ses",
-            "type": "string",
-            "format": "label",
-        },
-        "subject": {
-            "display_name": "Subject",
-            "name": "sub",
-            "type": "string",
-            "format": "label",
-        },
-    }
-    formats = {
-        "label": {
-            "pattern": "[0-9a-zA-Z]+",
-        }
-    }
-    modality_datatypes = [
-        "anat",
-        "dwi",
-        "fmap",
-        "func",
-        "perf",
-        "eeg",
-        "ieeg",
-        "meg",
-        "beh",
-        "pet",
-        "micr",
-    ]
-    _regex_string = _add_subdirs(
-        regex_string, variant, datatype, entity_definitions, formats, modality_datatypes
-    )
-
-    assert (
-        _regex_string == "/sub-(?P<subject>([0-9a-zA-Z]+))/sub-(?P=subject)"
-        "_sessions\\.(tsv|json)"
-    )
-
-
-def test__add_suffixes():
-    from ..support.bids.validator import _add_suffixes
-
-    # Test single expansion
-    regex_entities = "sub-(?P=subject)"
-    variant = {
-        "suffixes": ["sessions"],
-        "extensions": [
-            ".tsv",
-            ".json",
-        ],
-        "entities": {"subject": "required"},
-    }
-    regex_string = "sub-(?P=subject)_sessions"
-
-    _regex_string = _add_suffixes(regex_entities, variant)
-
-    assert _regex_string == regex_string
-
-    # Test multiple expansions
-    regex_entities = (
-        "sub-(?P=subject)(|_ses-(?P=session))"
-        "(|_acq-(?P<acquisition>([a-zA-Z0-9]*?)))"
-        "(|_rec-(?P<reconstruction>([a-zA-Z0-9]*?)))"
-        "(|_dir-(?P<direction>([a-zA-Z0-9]*?)))(|_run-(?P<run>([a-zA-Z0-9]*?)))"
-        "(|_recording-(?P<recording>([a-zA-Z0-9]*?)))"
-    )
-    variant = {
-        "suffixes": [
-            "physio",
-            "stim",
-        ],
-        "extensions": [
-            ".tsv.gz",
-            ".json",
-        ],
-        "entities": {
-            "subject": "required",
-            "session": "optional",
-            "acquisition": "optional",
-            "reconstruction": "optional",
-            "direction": "optional",
-            "run": "optional",
-            "recording": "optional",
-        },
-    }
-    regex_string = (
-        "sub-(?P=subject)(|_ses-(?P=session))"
-        "(|_acq-(?P<acquisition>([a-zA-Z0-9]*?)))"
-        "(|_rec-(?P<reconstruction>([a-zA-Z0-9]*?)))"
-        "(|_dir-(?P<direction>([a-zA-Z0-9]*?)))(|_run-(?P<run>([a-zA-Z0-9]*?)))"
-        "(|_recording-(?P<recording>([a-zA-Z0-9]*?)))"
-        "_(physio|stim)"
-    )
-
-    _regex_string = _add_suffixes(regex_entities, variant)
-
-    assert _regex_string == regex_string
-
-
-def test_load_all():
-    from ..support.bids.validator import load_all
-
-    schema_path = os.path.join(
-        os.path.abspath(os.path.dirname(__file__)),
-        "../support/bids/schemadata/1.7.0+369",
-    )
-
-    schema_all, _ = load_all(schema_path)
-
-    # Check if expected keys are present in all entries
-    for entry in schema_all:
-        assert "regex" in list(entry.keys())
-        assert "mandatory" in list(entry.keys())
-
-
-def test_write_report(tmp_path):
-    from ..support.bids.validator import write_report
-
-    validation_result = {}
-
-    validation_result["schema_tracking"] = [
-        {
-            "regex": ".*?/sub-(?P<subject>([a-zA-Z0-9]*?))/"
-            "(|ses-(?P<session>([a-zA-Z0-9]*?))/)anat/sub-(?P=subject)"
-            "(|_ses-(?P=session))(|_acq-(?P<acquisition>([a-zA-Z0-9]*?)))"
-            "(|_ce-(?P<ceagent>([a-zA-Z0-9]*?)))"
-            "(|_rec-(?P<reconstruction>([a-zA-Z0-9]*?)))"
-            "(|_run-(?P<run>([a-zA-Z0-9]*?)))"
-            "(|_part-(?P<part>(mag|phase|real|imag)))"
-            "_(T1w|T2w|PDw|T2starw|FLAIR|inplaneT1|inplaneT2|PDT2|angio|T2star)"
-            "\\.(nii.gz|nii|json)$",
-            "mandatory": False,
-        }
-    ]
-    validation_result["schema_listing"] = [
-        {
-            "regex": ".*?/sub-(?P<subject>([a-zA-Z0-9]*?))/"
-            "(|ses-(?P<session>([a-zA-Z0-9]*?))/)anat/sub-(?P=subject)"
-            "(|_ses-(?P=session))(|_acq-(?P<acquisition>([a-zA-Z0-9]*?)))"
-            "(|_ce-(?P<ceagent>([a-zA-Z0-9]*?)))"
-            "(|_rec-(?P<reconstruction>([a-zA-Z0-9]*?)))"
-            "(|_run-(?P<run>([a-zA-Z0-9]*?)))"
-            "(|_part-(?P<part>(mag|phase|real|imag)))"
-            "_(T1w|T2w|PDw|T2starw|FLAIR|inplaneT1|inplaneT2|PDT2|angio|T2star)"
-            "\\.(nii.gz|nii|json)$",
-            "mandatory": False,
-        }
-    ]
-    validation_result["path_tracking"] = [
-        "/home/chymera/.data2/datalad/000026/"
-        "rawdata/sub-EXC022/anat/sub-EXC022_ses-MRI_flip-1_VFA.nii.gz"
-    ]
-    validation_result["path_listing"] = [
-        "/home/chymera/.data2/datalad/000026/"
-        "rawdata/sub-EXC022/anat/sub-EXC022_ses-MRI_flip-1_VFA.nii.gz"
-    ]
-
-    report_path = os.path.join(
-        tmp_path,
-        "output_bids_validator_xs_write.log",
-    )
-    expected_report_path = os.path.join(
-        os.path.abspath(os.path.dirname(__file__)),
-        "data/expected_bids_validator_xs_write.log",
-    )
-    write_report(validation_result, report_path=report_path)
-    with open(report_path, "r") as f:
-        report_text = f.read()
-    with open(expected_report_path, "r") as f:
-        expected_report_text = f.read()
-    assert report_text == expected_report_text
-
-
-def test_bids_datasets(bids_examples, tmp_path):
-    from ..support.bids.validator import validate_bids
-
-    # Validate per dataset with explicit schema specification:
-    for i in os.listdir(bids_examples):
-        if i in BIDS_EXAMPLES_WHITELIST:
-            result = validate_bids(
-                os.path.join(bids_examples, i),
-                schema_version=TEST_SCHEMA_PATH,
-                report_path=True,
-                debug=True,
-            )
-            # Have all files been validated?
-            assert len(result["path_tracking"]) == 0
-
-    # Create input for file list based validation
-    selected_dir = os.path.join(bids_examples, BIDS_EXAMPLES_WHITELIST[0])
-    selected_paths = []
-    for root, dirs, files in os.walk(selected_dir, topdown=False):
-        for f in files:
-            selected_path = os.path.join(root, f)
-            selected_paths.append(selected_path)
-    # Does terminal debug output and schema auto-fallback work?
-    result = validate_bids(
-        selected_paths,
-        schema_reference_root="{module_path}/schemadata",
-        debug=True,
-    )
-    # Does default log path specification work?
-    result = validate_bids(
-        selected_paths, schema_version=TEST_SCHEMA_PATH, report_path=True
-    )
-
-    # Does custom log path specification work?
-    result = validate_bids(
-        selected_paths,
-        schema_version=TEST_SCHEMA_PATH,
-        debug=True,
-        report_path=os.path.join(tmp_path, "test_bids.log"),
-    )
-    # Have all files been validated?
-    assert len(result["path_tracking"]) == 0
-
-
-def test_error_datasets(bids_examples):
-    from ..support.bids.validator import validate_bids
-
-    # Validate per dataset, with automatic schema selection:
-    for i in os.listdir(bids_examples):
-        if i in BIDS_EXAMPLES_BLACKLIST:
-            result = validate_bids(
-                os.path.join(bids_examples, i),
-                schema_reference_root="{module_path}/schemadata",
-            )
-            # Are there non-validated files?
-            assert len(result["path_tracking"]) != 0
diff --git a/dandi/validate.py b/dandi/validate.py
index 3c3636eee..57d8dd285 100644
--- a/dandi/validate.py
+++ b/dandi/validate.py
@@ -11,7 +11,6 @@
 def validate_bids(
     *paths: Union[str, Path],
     schema_version: Optional[str] = None,
-    devel_debug: bool = False,
     report: bool = False,
     report_path: str = "",
 ) -> dict:
@@ -37,7 +36,7 @@ def validate_bids(
         patterns.
     """
 
-    from .support.bids.validator import validate_bids as validate_bids_
+    from bidsschematools.validator import validate_bids as validate_bids_
 
     if report and not report_path:
         log_dir = appdirs.user_log_dir("dandi-cli", "dandi")
@@ -48,8 +47,6 @@ def validate_bids(
     validation_result = validate_bids_(
         paths,
         schema_version=schema_version,
-        schema_reference_root="{module_path}/schemadata",
-        debug=devel_debug,
         report_path=report_path,
     )
     return dict(validation_result)
diff --git a/setup.cfg b/setup.cfg
index 052721432..12e6f6206 100644
--- a/setup.cfg
+++ b/setup.cfg
@@ -30,6 +30,7 @@ project_urls =
 python_requires = >=3.7
 install_requires =
     appdirs
+    bidsschematools
     click
     click-didyoumean
     dandischema ~= 0.7.0