device/dev- entity + devices.{tsv,json}

[yarikoptic]

Your idea

Relates to

• BEP for audio/video capture of behaving subjects #1771

by @bendichter , and overall to cover necessary disambiguation between acquisition across different devices of the same kind. In our case it would immediately be multiple video cameras, so we could have _dev-camera1, _dev-camera2 with devices.tsv providing at least the device_id and description columns and then any other additional metadata fields.

It would reflect the addition of _camera- entity in neuroblueprint (ref: https://neuroblueprint.neuroinformatics.dev/latest/specification.html#example-project-folder ; attn @niksirbi) .

We should also see on extensive metadata schema already in AIND (bids-standard/bids-2-devel#60) listed in https://github.com/AllenNeuralDynamics/aind-data-schema to potentially generalize a few other generic device description metadata fields, and/or provide more specialization for some common device types (audiovideo recording etc)

[niksirbi]

so we could have _dev-camera1, _dev-camera2 with devices.tsv providing at least the device_id and description columns and then any other additional metadata fields

That seems to me a sensible and BIDS-y way of approaching this.

It would reflect the addition of _camera- entity in neuroblueprint

Note that camera is not a formal entity in NeuroBlueprint, it's just shown among some example filenames to encourage adherence to the key1-value1_key2-value2 schema for naming things.

Having a dev entity is much more flexible, I like it.