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

Document DOI assignment for releases #48

Closed
11 tasks done
peterdesmet opened this issue Nov 20, 2014 · 12 comments
Closed
11 tasks done

Document DOI assignment for releases #48

peterdesmet opened this issue Nov 20, 2014 · 12 comments
Assignees
Labels

Comments

@peterdesmet
Copy link
Member

peterdesmet commented Nov 20, 2014

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

@peterdesmet
Copy link
Member Author

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

@peterdesmet peterdesmet changed the title Add DOIs to releases Document DOI assignment for releases Mar 13, 2015
@peterdesmet
Copy link
Member Author

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
Copy link
Member

tucotuco commented Nov 8, 2016

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.

@tucotuco tucotuco reopened this Nov 8, 2016
@peterdesmet
Copy link
Member Author

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

@peterdesmet
Copy link
Member Author

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

@peterdesmet peterdesmet removed this from the Migration of DwC to GitHub milestone Nov 8, 2016
@peterdesmet
Copy link
Member Author

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?

@peterdesmet peterdesmet added this to the DwC simplification milestone Oct 7, 2017
@tucotuco
Copy link
Member

tucotuco commented Aug 8, 2021

Not needed for current release. Removing from current milestone.

@peterdesmet
Copy link
Member Author

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
Copy link
Member

tucotuco commented Oct 22, 2021 via email

@peterdesmet
Copy link
Member Author

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

@tucotuco
Copy link
Member

tucotuco commented Oct 22, 2021 via email

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

2 participants