-
Notifications
You must be signed in to change notification settings - Fork 2
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
Schema update priority ticket - gender/Visium 2022-07-05 #844
Comments
Enrique to check the PRs for the comments |
Gender field PR is waiting on the ontology release |
@ESapenaVentura to check if review has gone through today. |
Gender_identity is ready, waiting on ontology ticket |
EOD friday as hannes is on holidays |
The Visium update will be merged, as approved by Hannes. |
This will be included in the next ontology release |
Ontology release to staging has been done - I am pushing the PR to staging |
enrique is investigating the linter faliure in the schema repo |
@ESapenaVentura chatted with Zoe about the issue - Created ticket in HCAO repo |
Stalled until we hear back about gender_identity ontology term. |
Still not solved with this month's release... |
Had a discussion with Zoe, they couldn't get to fix the issue and will work on it for the next release! |
The gender_identity ontology term needs a meeting setup with OLS. @ESapenaVentura to action this. |
I have sent an email to Henriette, copying in CC Zoe and the wrangler team |
What are the next schema updates?
Schema Update 1: Gender field
PR here
Schema Update 2: Visium permeabilisation time field
PR here
What schemas will they affect?
These changes will affect the following schemas:
Why are these changes needed?
We currently lack the metadata field to store gender. There are datasets with trans donors (TestisCellAtlas) where gathering and storing this metadata is vital. The dataset is blocked by this. This schema change adds an optional ontologised gender field to donor_organism.
Data contributors want to be able to store the permeabilisation time field in our metadata schema as it is a key field that they want to search and filter through.
Type of change and time frame
Update number 1 constitutes a minor change.
Update number 2 constitutes a minor change.
We are expecting to push both updates before 20/07/2022 (Wednesday, 20th July)
The text was updated successfully, but these errors were encountered: