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
Document our policy/workflow of adding new chemical terms into OBA:
1. identifiers must be provided to either PRO, CHEBI, SWISSLIPIDS, LIPIDMAPS, UNIPROT
2. we (the OBA team) map all identifiers to CHEBI, PRO, SWISSLIPID, LIPID MAPS terms (in this order of precedence). If the submitted id is, for example, a LIPID MAPS ID, then we still try to map it to CHEBI first.
3. We always map to the species-independent PRO IDs
Create a ROBOT template that furthermore imports the following information
1. Human-specific PR code (use oboInOwl:hasDbXref), and add axiom annotation "human specific"
2. Original UniProt ID (use oboInOwl:hasDbXref)
We should discuss about adding the PRO sssom file into the pro slim in a meeting, but lets do the above first.
The text was updated successfully, but these errors were encountered:
Add to docs: how to "inform" submitters about new ids - (they should get at least the old ID, the old label, if any, the OBA id and the OBA label back so they can easily re-curate).
1. identifiers must be provided to either PRO, CHEBI, SWISSLIPIDS, LIPIDMAPS, UNIPROT
2. we (the OBA team) map all identifiers to CHEBI, PRO, SWISSLIPID, LIPID MAPS terms (in this order of precedence). If the submitted id is, for example, a LIPID MAPS ID, then we still try to map it to CHEBI first.
3. We always map to the species-independent PRO IDs
1. Human-specific PR code (use oboInOwl:hasDbXref), and add axiom annotation "human specific"
2. Original UniProt ID (use oboInOwl:hasDbXref)
We should discuss about adding the PRO sssom file into the pro slim in a meeting, but lets do the above first.
The text was updated successfully, but these errors were encountered: