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

Add documentation on github for GO curators #105

Closed
cmungall opened this issue Sep 16, 2015 · 4 comments
Closed

Add documentation on github for GO curators #105

cmungall opened this issue Sep 16, 2015 · 4 comments

Comments

@cmungall
Copy link
Member

Migrated from http://wiki.geneontology.org/index.php/Manager_Call_2015-09-16

Github: 1) Documentation on how to use github for curators, 2) how to add curator initials when a new > curator wants to make ontology changes (Paola has volunteered to bring this up in Ontology call). > UPDATE ON 2): discussed here: http://jira.geneontology.org/browse/GO-952. Last question remaining: > Chris, can editors stop editing the GO.curator_dbxref file then?

@kltm
Copy link
Member

kltm commented Sep 16, 2015

I assume the idea would be to make GO.curator_dbxref a read-only downstream artifact like GO.db_xrefs?
Might want to Will need to coordinate with @hdietze on this. The last merge of all resources was a little bit ago, so we'd have to do that again, and then flip it over (copying the dbxrefs.yaml).

@kltm
Copy link
Member

kltm commented Sep 16, 2015

@cmungall There is also GO.curator_dbxrefs.json. Do you know how this was generated (at least since FOAF/WebID was the rage)? It does not seem to update as part of any pipeline, but I haven't been able to find the update script anywhere (and it would be somewhat nicer to work with than parsing the other file, again).

@kltm
Copy link
Member

kltm commented Sep 16, 2015

Discussed with @cmungall, will treat org field of GO.curators_dbxrefs as string for the time being. @hdietze has provided the sources for his current instance, so will do a three-way merge with the current data.

kltm added a commit that referenced this issue Sep 16, 2015
…r all of the various use cases; this affects: geneontology/noctua#191 geneontology/noctua#184 and #105; TODO: three-way merge of various data, with this being the base
kltm added a commit that referenced this issue Sep 17, 2015
@kltm
Copy link
Member

kltm commented Sep 17, 2015

Not sure if gists tag you, but here:
https://gist.github.com/kltm/198879e787c3a42470de
@cmungall @hdietze

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

2 participants