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

Get non-mouse PRO ids into Noctua for use in annotation #105

Open
hdrabkin opened this issue May 12, 2017 · 11 comments
Open

Get non-mouse PRO ids into Noctua for use in annotation #105

hdrabkin opened this issue May 12, 2017 · 11 comments

Comments

@hdrabkin
Copy link

All of PRO IDS should be available in Noctua (ids for human, pombe, etc); can these be loaded from PRO directly (could (PRO to supply a GPI file).

@cmungall cmungall self-assigned this May 12, 2017
@kltm kltm changed the title Getting non-mouse PRO ids into Noctua for use in annotation Get non-mouse PRO ids into Noctua for use in annotation May 12, 2017
@kltm
Copy link
Member

kltm commented May 12, 2017

So the action here would be to get a GPI file that covered PRO (one way or another) and include it in NEO, yes?

@hdrabkin
Copy link
Author

Essentially. Right now, MGI handles the mouse specific, but PRO has lots of human, Pombe, etc. that aren't being submitted, so there is no way to use them in Noctua.

@cmungall
Copy link
Member

The translation is simple.

However there are things here that require discussion with the larger group

  • size issues and hardware. All of PRO is large (300k classes), we need to determine if we will need to up memory for minerva or solr. Also we don't have any guaranteed estimated upper bounds like with most ontologies. In theory PRO could grow orders of magnitude over the years.
  • size issues for usability. Has the potential to flood autocomplete results making it harder to find what is needed.
  • orthogonality issues. We will have 'duplicate' entries for GCRPs, which can potentially confuse curators and bring up a host of SOP issues. One option is to exclude GCRPs from PRO and only use PRO for subclasses of GCRPs, but this is awkward

@kltm
Copy link
Member

kltm commented May 23, 2017

As these issues still seem to be open, is this still on the table for Corvallis?

@hdrabkin
Copy link
Author

Yes;

@kltm
Copy link
Member

kltm commented May 24, 2017

To clarify: is the intention here to have all of this fixed and being used before Corvallis?

@cmungall
Copy link
Member

cmungall commented May 24, 2017 via email

@hdrabkin
Copy link
Author

Since I assume PRO might be the one to supply a PRO specific GPI, I very much doubt this could be done by then! Darren Natale at PRO (who will be at the meeting) would need guidance at the least.

@cmungall
Copy link
Member

No, that part is trivial / not necessary. We actually convert GPI to obo/owl. PRO is already in obo/owl, and could be slotted in naturally. However, we can't do that until the issues I mention above are discussed.

@cmungall
Copy link
Member

cmungall commented Aug 9, 2017

Removing from current milestones. Will be discussed when I attend PRO meeting

@vanaukenk vanaukenk transferred this issue from geneontology/noctua Jun 3, 2022
@suzialeksander
Copy link

Noting there is still interest in this: geneontology/helpdesk#439

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants