-
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
Clarify and implement rules on inclusion of RNA gene products / RNA central #99
Comments
Before we close, could this other issue be related to the problem of RNAs not passing the ShEx, and be traceable to NEO in some way? |
One other minor issue, I don't know much much it bugs curators: RNAC GPIs lack symbols. This means that they show up with IDs on the display: If we look at the source, e.g https://rnacentral.org/rna/URS00005EB5B7/9606 We see that RNAC provide names "Homo sapiens let-7a-1 stem-loop (hsa-let-7a-1)" but not symbols This is reflected in the GPI: ➜ neo git:(master) ✗ gzip -dc mirror/goa_human_rna.gpi.gz | grep URS00005EB5B7_9606 | cut -f3 ➜ neo git:(master) ✗ gzip -dc mirror/goa_human_rna.gpi.gz | grep URS00005EB5B7_9606 | cut -f4 @alexsign -- is there a way to get something approaching a symbol into the GPI file (the thing in parens looks like a symbol) If not, I propose that we add something to the neo perl scripts that uses the name for the rdfs:label if symbol is not present. Then the name will show up in the Noctua models, e.g. the ones here: geneontology/noctua#760 |
I dont knwow if this is true for all RNAC entities, but the label would be what's in the parenthesis - for e.g. hsa-let-7a-1 @RLovering is this correct? |
There are various tickets in this repo that are very old and related to RNAcentral. Let's close these.
We should clarify the situation. I think it is as follows
Autocomplete works fine with the human RNAs as expected (though it's confusing as they don't have actual symbols)
If this is correct then this ticket can be closed with the addition of documentation and closing of the old tickets
The text was updated successfully, but these errors were encountered: