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

gorefs place to link to for descriptions #1762

Closed
ValWood opened this issue Jan 11, 2022 · 7 comments
Closed

gorefs place to link to for descriptions #1762

ValWood opened this issue Jan 11, 2022 · 7 comments
Labels

Comments

@ValWood
Copy link
Contributor

ValWood commented Jan 11, 2022

HI,

We would like somewhere stable to a) link to and b) extract the text for the GO db-xrefs.

Googling I can only find ;
https://github.com/geneontology/go-site/blob/master/metadata/gorefs/goref-0000116.md

Is there anywhere on the GO site proper?

We could use this:
https://raw.githubusercontent.com/geneontology/go-site/master/metadata/gorefs/goref-0000116.md

but it done not look very constrained (embedded URLs and PMIDs etc)

We want to add this information to these pages:
https://www.pombase.org/reference/GO_REF:0000116

@kimrutherford

@kltm kltm added the question label Jan 11, 2022
@kltm
Copy link
Member

kltm commented Jan 11, 2022

@ValWood Just to clarify, it looks like you're GO refs, not the rules or the db xrefs, correct?

The GO_REF:0000015 CURIE expands to the URI http://purl.obolibrary.org/obo/go/references/0000015, which is then mapped to https://github.com/geneontology/go-site/blob/master/metadata/gorefs/goref-0000015.md. So, officially, the URI is what one would want.

Depending on what you're doing though, it might be easier just to either work with the data in GitHub (as it's easily handled using a yamldown lib) or take the entire thing from the aggregated README:
https://github.com/geneontology/go-site/blob/master/metadata/gorefs/README.md

That said, depending on your use, it may be the less derived from the URI source the better.

@ValWood
Copy link
Contributor Author

ValWood commented Jan 11, 2022

It seems this should be on the main GO site somewhere really. I wonder how other link to this info??

@ValWood
Copy link
Contributor Author

ValWood commented Jan 11, 2022

Doesn't it seem a bit weird to link to a GitHub page?
I see that is what AmiGO does....

@kimrutherford
Copy link
Contributor

Ideally, we'd like a single easy to parse file containing all the GO ref details. We were hoping there would be a file a bit like this one that we use for our internal references: https://curation.pombase.org/dumps/latest_build/pombe-embl/supporting_files/PB_references.txt

But for now will parse the individual .md files. Thanks for the hint about yamldown.

@ValWood
Copy link
Contributor Author

ValWood commented Jan 13, 2022

I'm sure others could use such a file too!

kimrutherford added a commit to pombase/pombase-legacy that referenced this issue Jan 14, 2022
kimrutherford added a commit to pombase/pombase-chado that referenced this issue Jan 14, 2022
Authors are now stored in the "authors" pubprop rather than
"pubmed_authors", abstract now in "abstract" rather than "pubmed_abstract".
We do this so that the authors and abstract sources are clear in Chado.

Parsing is now slightly more strict and the ID can be "pb_ref_id" or
"ref_id".

Refs geneontology/go-site#1762
@kimrutherford
Copy link
Contributor

Ideally, we'd like a single easy to parse file containing all the GO ref details.

I'm sure others could use such a file too!

We now process the .md files into a single file for loading.

Here's what we loaded last night: https://curation.pombase.org/dumps/latest_build/pombe-embl/supporting_files/go_references.txt

@kltm
Copy link
Member

kltm commented Jan 19, 2022

With feedback from @cmungall, closing in favor of future work item: #1764

@kltm kltm closed this as completed Jan 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants