Document DOI assignment for releases

[peterdesmet]

DOIs are already automatically assigned, but it might be good to:

• Add those DOIs to the releases on GitHub
• Add more metadata (e.g. authors) to the packages on Zenodo.
• 2021-08-24: https://doi.org/10.5281/zenodo.5251698 part of DOI version chain 1
• 2020-08-20: https://doi.org/10.5281/zenodo.5136636 part of DOI version chain 1
• 2014-11-08: https://doi.org/10.5281/zenodo.12694 part of DOI version chain 1
• 2013-10-23: https://doi.org/10.5281/zenodo.12693 part of DOI version chain 2
• 2011-10-26: https://doi.org/10.5281/zenodo.12691 part of DOI version chain 1
• 2009-12-07: https://doi.org/10.5281/zenodo.5593192 part of DOI version chain 3
• 2009-10-08: https://doi.org/10.5281/zenodo.5593189 part of DOI version chain 3
• Remove pre-releases from Zenodo
• Correct authors for https://doi.org/10.5281/zenodo.12691

[peterdesmet]

Also add to instructions on how to do this to build/README.md.

[peterdesmet]

It will require some more work to remove pre-releases from Zenodo, but at least they are not public:

https://zenodo.org/record/12684
https://zenodo.org/record/12690
https://zenodo.org/record/15508/
https://zenodo.org/record/15491/
https://zenodo.org/record/15489/
https://zenodo.org/record/15487/
https://zenodo.org/record/15485/
https://zenodo.org/record/15481/
https://zenodo.org/record/14816/

[peterdesmet]

The latest 3 of the 5 versions are on Zenodo and have a DOI: https://zenodo.org/search?page=1&size=20&q=darwin%20core. I don't see the need to go further back (than 2011-10-26), unless @tucotuco you want me to deposit the two 2009 releases on Zenodo as well.

GitHub integration with Zenodo is fairly well described elsewhere (e.g. https://guides.github.com/activities/citable-code/) + you can look at previous releases to see what metadata was added, so don't see the need to describe this in readme at this time.

[tucotuco]

For the sake of completeness, I would add both. For the sake of history, I would definitely add the first version of the standard 2009-10-08.

[peterdesmet]

Bit of a rocky history with the Zenodo integration. I contacted their support as I currently cannot create packages for those two releases.

[peterdesmet]

Not a blocking issue for releasing website though, so I'm taking it out of the milestone.

[peterdesmet]

Answer from Zenodo:

At the moment there's no easy way to create Zenodo releases for already existing packages. The whole workflow is inherently connected with the GitHub's webhook, which is activated at the time of the release.
What you can do now is to create a regular Zenodo upload with the ZIP of your releases and upload them to Zenodo as "Software"-type record. This will not, however, be recognized as a GitHub "Release" since there will be no additional payload information from GitHub.

Do you want me to do that?

[tucotuco]

Not needed for current release. Removing from current milestone.

[peterdesmet]

Update on this issue: the 5 latest of the 7 total official Darwin Core releases are deposited on Zenodo.

Do you want me to deposit 2 earlier (2009-12-07 and 2009-10-08) releases on Zenodo, knowing that they will be separate deposits, not versions of the already existing one. Or are we fine not having those deposited on Zenodo?

[tucotuco]

If there is no real cost and not too much effort, I would opt for completeness and deposit them.

…

On Fri, Oct 22, 2021 at 7:41 AM Peter Desmet ***@***.***> wrote: Update on this issue: the 5 latest of the 7 total official Darwin Core releases are deposited on Zenodo. Do you want me to deposit 2 earlier (2009-12-07 and 2009-10-08) releases on Zenodo, knowing that they will be separate deposits, not versions of the already existing one. Or are we fine not having those deposited on Zenodo? — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#48 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADQ72YBYR52TL245T3JCPDUIE5XLANCNFSM4AX2YT6A> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[peterdesmet]

Added. This issue can now be closed (after 7 years 😅 ).

[tucotuco]

Huzzah!

…

On Fri, Oct 22, 2021 at 1:39 PM Peter Desmet ***@***.***> wrote: Added. This issue can now be closed (after 7 years 😅 ). — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#48 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADQ7222TPHEDFADNZPPLJDUIGHT7ANCNFSM4AX2YT6A> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.