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

Feature request: DOI versioning #7867

Closed
Danny-dK opened this issue May 11, 2021 · 2 comments
Closed

Feature request: DOI versioning #7867

Danny-dK opened this issue May 11, 2021 · 2 comments

Comments

@Danny-dK
Copy link

I had a question on DOI and versions within Dataverse. Data in Dataverse gets 1 DOI, even when there are multiple versions present of the data package. Considering that this might hamper machine readability to refer to a specific version of a data package, would a Zenodo implementation be something to consider? That would allow getting people immediately to the correct version of a data package through a specific resolvable DOI (and avoids possible confusion on which version to use).

https://help.zenodo.org/#versioning%22

image

I understand that you can refer to a version by for example:

https://dataverse.nl/dataset.xhtml?persistentId=doi:10.34894/2WZ0S9&version=2.0
https://dataverse.nl/dataset.xhtml?persistentId=doi:10.34894/2WZ0S9&version=1.0

But that is not really the same as one resolvable DOI (https://doi.org/10.34894/2WZ0S9)

@pdurbin
Copy link
Member

pdurbin commented May 11, 2021

Please see also:

@djbrooke
Copy link
Contributor

Hi @Danny-dK - thanks! It's certainly something we're interested in. I'm going to move this content over to #4499 since there's some additional conversation in that issue, and I'll close this issue as a duplicate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants