Add CElegansSubject and species-specific Subject neurodata types #575
Labels
category: extension
proposed extensions
category: proposal
proposed enhancements or new features
priority: medium
non-critical problem and/or affecting only a small set of NWB users
Milestone
cc @dysprague @CodyCBakerPhD @bendichter
Some species have different requirements than others. For example, C Elegans sex is either XO or XX. @dysprague created the ndx-multichannel-volume extension that includes a
CElegansSubject
neurodata type with three fields:growth_stage_time
,growth_stage
, andcultivation_temp
.growth_stage
is required. This type is necessary because in the currentSubject
schema, if we were to addgrowth_stage
it would have to be optional; we do not have a way to say formally that if species = "Caenorhabditis elegans", thengrowth_stage
is required. It also helps tools like nwbinspector to do different best practices validation ofsex
andage
based on species.It feels strange to use the ndx-multichannel-volume extension just to use the
CElegansSubject
neurodata type, but that is workable. It would be better to have this type split off in its own extension or part of the core NWB schema.Related:
NeurodataWithoutBorders/nwbinspector#353
dandi/dandi-schema#171
#492
see especially @satra's comments on dandi/dandi-schema#171 (comment)
For the C elegans subject, we could...
CElegansSubject
into its own extension and later consider integration into coreCElegansSubject
into core as a NWB Enhancement ProposalCElegansSubject
into core without a NEPI lean toward option 2. Thoughts? We can also consult the TAB.
Separately but relatedly, I can imagine humans, rodents, flies, and other animals having species-specific metadata as well.
strain
andgenotype
are not applicable to humans.age
anddate_of_birth
are not really meaningful in flies and worms (I think). We saw someone wanting to storewean_time
in rodents. Perhaps we should create species-specific Subject neurodata types.The text was updated successfully, but these errors were encountered: