Ensure all maintainers can publish PyGMT to Zenodo and make a DOI

[weiji14]

Need to make sure that every core maintainer can reserve a new Zenodo version DOI for PyGMT. Continuing discussion from #599 (comment)_. I.e. everyone should be able to click on the green "New version" button (see sceenshot).

Which will take you to a page where there should be a 'Reserve DOI' button somewhere. Click on that, and copy the DOI link to the changelog/release notes for the new PyGMT version (e.g. at #599).

As to why we can't just automate this, see #599 (comment)_ (quoted below):

Just to clarify, there's 2 options that I know of to make a Zenodo DOI, each with pros/cons (see also FAQs at https://help.zenodo.org/):

1. Use the automated Github integration:

• Pro: It's automated, publishing a release creates the DOI automatiically
• Con: We don't know the DOI number beforehand, so can't put it into the release notes. Also, I couldn't manage to link it to our current permanent/concept DOI at https://doi.org/10.5281/zenodo.3781524.

2. Manually reserve a DOI (what was done for PyGMT v0.1.x):

• Pro: We know the DOI beforehand, so can put it into our release notes. Also more control with the metadata information.
• Con: It's not automated, I had to manually download the pygmt-v0.1.x.zip file, and upload it to Zenodo. Also as we found out, maybe it's linked only to my account?!!

Either way, would be good to discuss what we want to do 😐

[leouieda]

Copying from #599:

I was just checking on some of my own uploads and it seems like only the original creator can upload a new version. This really sucks since we can't use the DOI versioning and have multiple release managers at the same time. I have sent them an email asking is there is a workaround and if not, making that a feature request.

At the moment, it seems like we only have 2 options:

1. Wei Ji creates new Zenodo uploads forever 😉
2. We go back to making a new upload for every release instead of creating a new version. This would allow anyone to do the upload. Con is that we have to copy authors and descriptions every time.

I don't think the GitHub automation is an option since it doesn't allow reserving the DOI. In the end, I found it more trouble than it's worth. One thing we could do is build our own automation using the Zenodo API. It lets us reserve DOIs and make uploads. But that could be a lot of work.

[weiji14]

After some more searching, I found that the multi-user feature is on their current roadmap (see https://about.zenodo.org/roadmap/), and due for (Northern Hemisphere) autumn 2020 according to zenodo/zenodo#35 and zenodo/zenodo#151. So maybe I won't need to do this forever after all 😆

[leouieda]

And here I thought that I had you hooked for good...

[weiji14]

Just an update, things appear to have been pushed out to (Northern Hemisphere) autumn 2021 (see zenodo/zenodo#810 (comment)). The multi-curator feature will likely come to InvenioRDM in May 2021 (see https://inveniosoftware.org/products/rdm/roadmap and https://github.com/inveniosoftware/invenio-communities), and once Zenodo migrates their system to InvenioRDM (v4?) in the near term (hopefully sometime this year in 2021), we'll be able to add other PyGMT maintainers into the list.