-
Notifications
You must be signed in to change notification settings - Fork 17
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
Ensure that all TOP level HPO and MP terms have corresponding uPheno classes #948
Comments
If it helps this is a mapping of the high level HPO terms to high level MP terms |
Very helpful, thanks @sbello |
It would be great to review the top level structure of upheno, which seems very heterogeneous, and it is often hard to find corresponding terms in the source ontologies where one would expect them. It would be great to schedule a workshop to review and discuss this! |
Agree with @pnrobinson |
It would be good if @ar-ibrahim and @rays22 you could meet with Sue and perhaps draft a concrete proposal for a workshop - Would be nice to run another one! |
Let me know if this is what you had in mind Nico >> upheno-HPO-MP_mapping spreadsheet |
Also @sbello and I have agreed to meet in mid-July to draft a workshop for Biocuration 2025. |
Very good, thank you! In the meantime, I will draft something based on the combination of the MP and HPO upper categories. Thanks for your help!! |
@sbello will share another experience with re-designing the upper level of VT |
When we created the top level organization of VT we modified this from MP to expand the systems to cover all vertebrates. It could be helpful to look at the differences. A few key things:
It would also be helpful for the Alliance to consider the next level of organization under cellular phenotype as we need to be able to have a good slim set there as well. |
Please review MP and HPO and figure out if they have corresponding uPheno classes.
HP top level classes:
MP top level classes:
Ideally create a table in Google sheets.
Ask @rays22 for advice if needed!
The text was updated successfully, but these errors were encountered: