thearchivist.fun
Glossary · Evergreen reference

Version history

Version history explains how an object or dataset changed over time. It can record corrections, additions, merged identifiers, format conversions, and software behavior changes. A date-stamped file is a starting point, but the reason for the change matters as much as the timestamp. For each meaningful revision, preserve an edition identifier, date, short explanation, and the affected records or files. Keep source evidence for a corrected claim and distinguish editorial changes from alterations inherited from a source. Do not recycle an old identifier for unrelated content. When publishing a new edition, explain compatibility with earlier exports or citations. Good version history lets a reader understand why their older copy differs from yours and allows a maintainer to reverse a mistaken transformation without reconstructing the project from memory.

Context and provenance

A record of changes that keeps editions and their relationships understandable.

Sources and evidence

  1. DataONE: Document integration of multiple datasets
  2. W3C: PROV model primer

Editorial review: 2026-09-23. New evidence may change this account.

Report a problem with this record