Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ENH] Additional age related columns for participants.tsv file to cover animal data #1839

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

ree-gupta
Copy link
Member

@ree-gupta ree-gupta commented May 27, 2024

The PR adds columns for age_category, age_type, birthdate as discussed and suggested by @yarikoptic in #1826

This is open for discussion.

Related issues:

@bids-standard/bep032

@ree-gupta ree-gupta marked this pull request as ready for review July 17, 2024 14:13
@bendichter
Copy link
Contributor

What would be the best way to indicate that these fields are recommended for non-humans, but not recommended for humans?

@yarikoptic
Copy link
Collaborator

What would be the best way to indicate that these fields are recommended for non-humans, but not recommended for humans?

Besides birthday I think we can entirely avoid species-specificity here, but I liked phrasing to refer to units section on anonymization. I was looking at the stages and if someone annotates that it is late adult stage - it might help finding subjects of such interest. It is more of a question to me of duplicity of metadata, thus possibly leading to incongruities.

Copy link
Collaborator

@yarikoptic yarikoptic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

slight tune ups

src/schema/objects/columns.yaml Outdated Show resolved Hide resolved
src/schema/objects/enums.yaml Outdated Show resolved Hide resolved
name: age_type
display_name: Age type
description: |
Type of age measurement (e.g. `postnatal`, `fetal`, `gestational`). If not specified, `postnatal` is assumed.
Copy link
Collaborator

@yarikoptic yarikoptic Jul 17, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is there some ontology or controlled vocab to reference here as well by any chance?

@lzehl says "No!"

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if age_reference, some time points to consider:

  • fertilization
  • birth
  • gestation
  • ...

it seems we are boiling down to establishing a list of Enums with clear definitions and possibly adding TermURLs for some of them where there is a clear association.

TODO also to formalize such "TermURL" like linking at the level of schema which seems to lack it ATM.

ree-gupta and others added 2 commits September 18, 2024 14:20
Co-authored-by: Yaroslav Halchenko <debian@onerussian.com>
Co-authored-by: Yaroslav Halchenko <debian@onerussian.com>
@lzehl
Copy link

lzehl commented Oct 16, 2024

@bendichter @yarikoptic I agree that only birth_date causes issues with humans due to GDPR.
For the age_category we use in openMINDS:
https://openminds-documentation.readthedocs.io/en/latest/instance_libraries/terminologies/ageCategory.html

This list is derived from the UBERON ontology where possible with small additions were needed. Note that openMINDS did not yet integrate all UBERON life cycle stages:
https://www.ebi.ac.uk/ols4/ontologies/uberon/classes/http%253A%252F%252Fpurl.obolibrary.org%252Fobo%252FUBERON_0000104?lang=en

age_type in addition to define the reference point of the age value is a good idea. I'm not sure if the ontology https://bioportal.bioontology.org/ontologies/FMA/?p=classes&conceptid=http://purl.org/sig/ont/fma/fma312872 suggested by @satra in #1634 is species independent defined (definitions are also very sparse in this ontology).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants