You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
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.
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
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)
The text was updated successfully, but these errors were encountered: