Open CodyCBakerPhD opened 2 years ago
I think @h-mayorquin expressed interest in leading this
I believe we decided to use attributes of the dataset.
age
field.age
, e.g. "6-8 weeks".age.lower_bound
and age.upper_bound
, which if used are required to be ISO 8610 duration format.age.reference = "fertilization"
.Commenting here for the to-do list.
DANDI landed on using a slash for age range. We have already added this to the docs here and to the code here:
Age reference is now a field within NWB.
The only final point is one of "growth stage", which I have only ever seen come up for C. elegens, so maybe we should make a species-specific exception there
The only final point is one of "growth stage", which I have only ever seen come up for C. elegens, so maybe we should make a species-specific exception there
Didn't fly life stages (or maybe it was also fly larvae) also follow a similar type of customized pattern?
What would you like to see added to the NWBInspector?
From discussion the other day, need to formalize a Best Practice for using the
age
ofSubject
as a free-form text field to account for some additional properties.We already recommend ISO 8601 when exact age is known. If only a range is available, this uncertainty should be indicated.
I think what we landed on was using interval notation, e.g.,
age="(P4W, P6W)"
to indicate subject age could have been as low as 4 weeks and as high as 6 weeks old, but exact age unknown.There was also the reference time of 'birth' or 'stage' of development, which can be added on using a separation character such as '-', for the form
age="P4D - <reference point>"
, .e.g.age="P4D - Conception"
for in utero mouse studies, orage="P1D - Adulthood"
for Drosophila melanogaster studies, with global default<reference point>
being"birth"
.Pseudocode or other logic of the check
No response
Do you have any interest in helping implement the check function?
Yes.
Code of Conduct