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
Add missing field and docs gaf-eco-mapping-derived.txt #249
Comments
Hi Chris |
@cmungall should the GO_REF just be included on the ECO IDs that currently have the GO_REFs in the non-derived mapping file, or should it be propagated to descendants? |
Can you also add a link to this in the wiki page? |
https://github.com/evidenceontology/evidenceontology/blob/master/gaf-eco-mapping-derived.txt resolves to HTML, it needs to resolve to the raw github URL
|
Hi @cmungall - I'm a bit confused by your last comment because that GitHub URL will always resolve to the HTML. The URL we use in the header of the file is http://purl.obolibrary.org/obo/eco/gaf-eco-mapping-derived.txt and resolves to the raw text file. We are reviewing the Wiki and will update with this link shortly! Thanks! |
@nsuvarnaiari |
All the issues have been resolved. |
A while ago I worked with Marcus on this https://github.com/evidenceontology/evidenceontology/blob/master/gaf-eco-mapping.txt
This provides a mapping from a GAF code + GO_REF to an ECO class
There is a PURL for this, so that people can use a PURL rather than a github URL http://purl.obolibrary.org/obo/eco/gaf-eco-mapping.txt
all good
at some point some groups started needing a derived version of this so they didn't have to walk to the ECO graph
Here:
https://github.com/evidenceontology/evidenceontology/blob/master/gaf-eco-mapping-derived.txt
This essentially has materialized inferences
However, it lacks a GO_REF. It also lacks documentation at the start of the file
Can these be added? The docs should state exactly what the file is an how it's derived
I also recommend the PURL is advertised in the header:
http://purl.obolibrary.org/obo/eco/gaf-eco-mapping-derived.txt
cc @kltm
The text was updated successfully, but these errors were encountered: