geneontology / go-site

A collection of metadata, tools, and files associated with the Gene Ontology public web presence.
http://geneontology.org
BSD 3-Clause "New" or "Revised" License
45 stars 89 forks source link

Consider invenio as alternative to gorefs #749

Open cmungall opened 6 years ago

cmungall commented 6 years ago

https://invenio-software.org/

may be overkill for our needs, but just wanted to record the possibility for future services

I am recommending this for AGR who have need of a system for greypubs

kltm commented 6 years ago

Could you outline a bit more how you would envision this working? (and parameters for closing this ticket?)

cmungall commented 6 years ago

Could you outline a bit more how you would envision this working?

  1. configure and deploy
  2. one time transfer of gorefs (unknown: easy to have each one get a DOI? If so, keep mapping)
  3. curators add new refs as needed
  4. we change redirects in db-xrefs yaml to here OR we simply use DOIs directly
  5. Beyond what we do now: API hooks in so that AmiGO etc can show something informative about the ref

unknowns: hard to deploy? Looks like a simple docker-compose setup. But would likely involve hooking in some authorization mechanism.

could we piggy back off an AGR instance?

(and parameters for closing this ticket?)

a 👎 from you

kltm commented 6 years ago

C'mon, man, I can't say 👎 to you.

I'd be eager to find a way of storing/archiving our refs into a system like this--they have become quite burdensome over time as we migrate from system to system. As well, these are Good Folks doing Good Work. That said, it looks like you'd be thinking of running our own instance instead of a public one? I'd worry that's more of the same churn, but with more abstraction. If we could use Zenodo (in the Gene Ontology group) or OSF.io or somebody else to take over that bit of infrastructure, with our people logging in and add/updating as needed (generating new or versioned DOIs), that might be nice.