When working with datasets in the RDR repository, it is important to understand how versions are managed and how to view the history of changes. This page explains:

  • How dataset versions are generated
  • What types of changes trigger a new version
  • How to view and compare previous versions
Version changes
When a dataset is published for the first time, it automatically acquires version 1.0.











If it is edited later, a new draft is generated that must go through the review and publication process. Depending on the type of change, the draft will be published as version 1.1 (minor change) or 2.0 (major change).

Types of changes:

The following is how the version change is determined:

  • Minor change → version 1.1
    These are small modifications to the metadata that do not affect the citation of the dataset. For example, spelling corrections or adding non-essential complementary information.
  • Major change → version 2.0
    Includes changes to the files (deletion, replacement or addition of new files) or significant modifications to the metadata that alter the citation of the dataset.

















For more information, you can consult the “Dataset versions” section of the Dataverse user guide: https://guides.dataverse.org/en/5.11.1/user/dataset-management.html#dataset-versions




Version history or change control

In the “Versions” tab of a dataset record, you can consult the complete history of modifications.

Available information:

  • Modification date
  • Change author
  • Change details, accessible by clicking on “View Details










Additional features:

  • Version comparison

You can select two versions (even if they are not consecutive) and click “View differences” to see the changes.











  • Querying a specific version

By clicking on the version number in the “Dataset” column, you can access the complete record of that version, including files, metadata, and terms of use.



  • No labels