-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Annotate genes in HGNC with SO terms #118
Comments
References #118 This is thanks to the solutions to The-Sequence-Ontology/SO-Ontologies#301, The-Sequence-Ontology/SO-Ontologies#552, and The-Sequence-Ontology/SO-Ontologies#550. Thanks again to @egchr for helping
CC @sartweedie |
Just to clarify the situation with ‘complex locus constituent’ - this isn’t for genes that encode proteins that are part of complexes but rather complex in the sense of complicated. These are unusual cases where the research community have requested names for parts of complicated loci encoding many alternate isoforms. We think the closest SO term is gene_fragment (SO:0000997). |
Readthroughs are another oddity - they really represent transcripts derived from more than one adjacent gene. However, they are often discussed and treated as separate ‘gene’s distinct from the component genes that contribute to the ‘readthrough’ so some have been named separately. SO:0000697 doesn’t work for these. We suggest making a new SO term for these under transcript. I can put in a ticket for this. |
SO:0001500 is fine for phenotype I think even though it isn't under gene. All of the HGNC phenotype records have all been withdrawn (though they still appear in our records as withdrawn). |
Either find or create terms for all HGNC gene locus types that can be used to annotate all genes in HGNC:
So far, the mappings I've made are in here: https://github.com/pyobo/pyobo/blob/dc7b4736f2bbf943084e8f8a95e1293c2717c566/src/pyobo/sources/hgnc.py#L110-L145
Related discussion
With HGNC on twitter:
On the OBO Foundry Slack workspace:
https://obo-communitygroup.slack.com/archives/C01BDKWDS91/p1631787773022200
The text was updated successfully, but these errors were encountered: