Skip to content
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

Need SOP for adding new imported terms #13433

Closed
hdrabkin opened this issue Apr 27, 2017 · 6 comments
Closed

Need SOP for adding new imported terms #13433

hdrabkin opened this issue Apr 27, 2017 · 6 comments

Comments

@hdrabkin
Copy link
Contributor

hdrabkin commented Apr 27, 2017

The file
http://www.geneontology.org/quality_control/annotation_checks/taxon_checks/taxon_union_terms.obo

We need a new union that isn't in the above file;
Bacteria or Archaea
We also note that several of items in the above file are not imported into protege.

@ukemi
Copy link
Contributor

ukemi commented Apr 27, 2017

NCBITAXON_Union:0000004?

@hdrabkin
Copy link
Contributor Author

That one will do. But we still need SOP for the ones that aren't available.

@ukemi
Copy link
Contributor

ukemi commented Apr 28, 2017

Yes. this is a more general issue of how to request new imports.

@ukemi ukemi changed the title Need SOP for adding new taxon unions Need SOP for adding new imported terms Apr 28, 2017
@cmungall
Copy link
Member

I gave a quick demo of how to do this on the last call when you were away, the goal would be to get others able to do this.

But there are extra steps with the NCBITaxon union. We run a DL-reasoner (UnionOf is outside EL) to materialize a subClassOf hierarchy (so for example, HumanOrYeast SubClassOf Opisthokonte).

@ukemi
Copy link
Contributor

ukemi commented Apr 28, 2017

OK. We need to get this into the ontology developers' SOP documentation.

@ukemi
Copy link
Contributor

ukemi commented May 2, 2017

I have added a section to the ontology editors' documentation about adding import requests to the respective .txt files.

@ukemi ukemi closed this as completed May 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants