-
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
uPheno integration issues #965
Comments
A question. What does "nucleus phenotype" actually mean? If it means any phenotype that is observed in the nucleus, it would be tricky. So does this term really mean "nucleus organization phenotype"? or "nucleus morphology phenotype (size and shape)" |
@ValWood nucleus phenotype is meant to be the grouping class that collects all morphological and physiological abnormalities in the nucleus. The removal of the word abnormal from the uPheno labels without replacing it with another word with a similar if less negative connotations is I think contributing to the confusion. Both organization and morphology terms should fall under this term. If this isn't a useful grouping class than we should also discuss that. We can add that to the potential workshop topics. |
got it! In FYPO, due to a historic design decision, we keep abnormal morphology and abnormal process phenotypes distinct. Despite being (probably) ontologically correct I think that searches would benefit from such a grouping term (because often the genes annotated to such terms obviously often overlap). In fact, in some cases, it is difficult to distinguish, and really only depends on the method of observation (for example, we were recently unable to justify abnormal cytoskeleton organization from abnormal cytoskeleton morphology). I'm still considering what to do here. |
We've done a similar thing in the MP and have a similar issue, are they talking about the process or the outcome of the process is frequently tricky to decide. |
While searching for cellular phenotypes in uPheno I have come across a number of integration issues, including:
The text was updated successfully, but these errors were encountered: