-
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
Map APO entities to OBA / GO (or whatever else) #928
Comments
Related issue: Map APO modifiers to PATO -- issue #927 |
Hi @matentzn @rays22 we have completed a first pass of splitting the APO terms into trait and process. we have done a first pass to assign process terms from GO. please take a look and let us know what you think.
|
This separation between traits and processes is very useful for GO too @pgaudet. This distinction between organization and morphology crops up a lot. There are other terms described as traits which sit badly in GO (i.e related to telomere length and mitochondrial ditribution. Some minor suggestions. APO:0000046 silencing -> GO:0031507heterochromatin formation APO:0000096 nutrient utilization GO:0031667 response to nutrient levels
APO:0000253 cell cycle progression GO:0007049 cell cycle (in the current GO organisation this is broad because it includes cell cycle events in addition to "control of progression", (although I would like this to change eventually). For these, note that they should probably be related, because these terms describe 'phases' not processes (they should really be in a different ontology), and they don't describe progression. We have used these in FYPO logical defs but the qualifiers are always related to progression (i.e delay, duration etc) |
I have created this spreadsheet for APO because I need to progress fast: https://docs.google.com/spreadsheets/d/1pQ4VBAtfFOHLEdr1V5-4PtrtQsK50mLMQKhJ8GRpDjY/edit#gid=0 @rays22 I have not curated anything yet in there, just FYI that you dont create a new source of truth when you get to it.
|
Related issues:
The text was updated successfully, but these errors were encountered: