You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, entries in db-xrefs.yaml and presented in the amigo /xrefs page as if they were "top-level" entries, which can cause confusion for some users (re: discussion w/ @pgaudet ). We would like to fix this.
For example, maybe instead of
[LocusID](https://amigo.geneontology.org/xrefs#LocusID)
NCBI Gene
Site
http://www.ncbi.nlm.nih.gov/
Object
gene
Example ID
NCBI_Gene:4771
URL syntax
https://www.ncbi.nlm.nih.gov/gene/[example_id]
URL example
https://www.ncbi.nlm.nih.gov/gene/4771
We could have:
NCBIGene (with synonym [LocusID](https://amigo.geneontology.org/xrefs#LocusID))
NCBI Gene
Site
http://www.ncbi.nlm.nih.gov/
Object
gene
Example ID
NCBI_Gene:4771
URL syntax
https://www.ncbi.nlm.nih.gov/gene/[example_id]
URL example
https://www.ncbi.nlm.nih.gov/gene/4771
The text was updated successfully, but these errors were encountered:
Noting that I think this might be due to AmiGO still using xref_abbs somehow? The "best" thing would likely be to unsure that we are using the YAML, then iterate for the template and nest (and link) the synonyms there.
Currently, entries in db-xrefs.yaml and presented in the amigo /xrefs page as if they were "top-level" entries, which can cause confusion for some users (re: discussion w/ @pgaudet ). We would like to fix this.
For example, maybe instead of
We could have:
The text was updated successfully, but these errors were encountered: