As an admin of another repository system migrating dataset versions to Dataverse, I would like to include existing dataset version numbers so that my version numbers are persistent across repositories

[jggautier]

Dataset version numbers are generated by Dataverse and cannot be edited or imported. This is a problem for admins of other repositories who are migrating different versions of datasets into Dataverse and want to maintain the version number that's already in their metadata. The only way for researchers to identify a particular version of a dataset is from the version number, so when the version number changes during a migration, the researcher will have a harder time finding a particular version.

Janet brought this up in a Google Groups post, and it's an unresolved comment in the Dataverse 4.0+ Metadata Crosswalk.

[cmbz]

To focus on the most important features and bugs, we are closing issues created before 2020 (version 5.0) that are not new feature requests with the label 'Type: Feature'.

If you created this issue and you feel the team should revisit this decision, please reopen the issue and leave a comment.