...
| Note |
|---|
| title | Duplicate Version Labels |
|---|
|
| If a second version is created with the same label as a previous version, that label is quietly reassigned to the most recent version tagged resource has a version with a given label, you may not create another version with that label. If you later delete a labeled version, you may then create a new version with that label. |
| Tip |
|---|
Version creation is a relatively costly operation. With the ability to create versions whenever you wish, you can develop workflows that maximize the utility of this feature. Possible strategies include: - For batch operations, only create version checkpoints once nodes have been ingested, verified and tested.
- For small (but high-level) data such as the descriptive metadata created by subject experts, set a versioning policy to store every modification, thereby capturing the entirety of the curatorial endeavor.
- Create snapshot versions that correspond to released versions of content (i.e., version X of a shared dataset, controlled vocabulary or collection)
|
...
| Info |
|---|
When restoring an old version, two operations occur: - Immediately before restoring the old version, a version snapshot is made to reflect the current state of the object. This version will not have a version label.
- The current state of the resource will be updated to match the version being restored – but a new version will not be created. You can create a version explicitly if you want to create a version that records the revert.
|
Deleting a previous version
If you wish to remove historic version snapshots you may do so either using the REST API or the HTML view of the historic version. You may not, however, delete the most recent version snapshot