Versions

Overview

All data uploaded to a dataset is versioned. A version is a locked copy of the table that can't be edited or deleted. This means that you can confidently use a dataset in your projects, knowing that it will never change while you're working on it.

If the dataset's owner has an update, finds a mistake to correct, or would otherwise like to modify the existing data they can create and release a new version that will exist alongside the previous version of that dataset.

Every version contains a table of data along with the edits applied to modify it from the previous version, and any release notes written by the editor.

Inspecting versions

You can inspect the version history of a dataset by clicking on the version number on the dataset page or on a dataset node.

View a dataset's version from the dataset page
View and change the version of any dataset within a project

Within the version history, you can click on different versions on the left to view them. Below each version there is a summary of the differences from the previous version (or from an empty table in the case of v1.0.

View the content of each version by selecting

Within each version you can view the Edits, Table and Release tabs, if you have the appropriate access level.

  • The Edits tab describes all the changes made since the previous version.

  • The Table tab is the data itself and what you will be downloading or using in the project.

  • The Release tab contains the release notes and information about the version's sample and temporal range.

As versions age, their corresponding tables may become archived. You won't be able to view the cells on archived tables, but you can still query them on the query tab or work with them in a project.

Semantic version tags

To help researchers better understand if they should upgrade to a new version, Redivis uses semantic versioning, of the form v[major].[minor] The first version of every dataset is v1.0. For subsequent versions, the tag will augment automatically depending on the changes being released.

  • Major update: Your existing code may not run.

    • Triggered when any edits rename, delete, or retype variables

  • Minor update: Your existing code will generally run.

    • Edits include adding / removing records, recoding variables, adding variables