Provenance and Original Order: Explain Context with Evidence
Treat provenance and original order as frameworks for describing how records were created and used, not universal handling commands. Compare paper and collaborative records, and separate preservation evidence from authenticity claims.
Publication & corrections: infostoa · Editorial standards
Individual author and specialist reviewer information is not provided for this article.
Use provenance and original order to describe context
Provenance helps describe how records relate to their creator and the activities that produced them. Original order is a framework for describing and retaining an arrangement when evidence shows that the creator established it and that it carries meaning. Neither principle should be reduced to a universal command never to combine or move records. Consult prior inventories, business processes, transfer records, user needs, and institutional policy; distinguish supported relationships from uncertainty.
Two departments may address the same policy but work under different authority and procedures. Describe those contexts separately and link them with subject access. In a collaborative system, several teams may create and revise a document; a folder name alone may not identify its provenance. Review contributors, functions, dates, versions, system history, and relationships, then capture the relevant context in description.
| Case | Evidence to inspect | Practical choice |
|---|---|---|
| Numbered department files with a surviving sequence | Register, workflow, attachment and reference links | Retain the supported arrangement and creator data; add subject discovery in a separate index |
| Donated papers with mixed order | Donor notes, earlier lists/labels, physical clues | Reconstruct only supported relationships and document inference and processing history |
| Project records co-edited by teams | Change history, roles, permissions, version links | Avoid assuming one creator; describe collaborators/functions and link related records |
These are examples, not legal or repository-specific procedures. Access restrictions, privacy, transfer terms, and jurisdictional law require separate review.
What checksums and metadata can establish
Comparing a checksum with a baseline can detect whether bytes changed after that baseline was recorded. If the baseline’s provenance is unclear or there is no check history, that comparison alone does not establish original authenticity, completeness, or trustworthy creation context. Linking preservation events to the object—tool, date, outcome, error handling, and transformation history—makes the available evidence easier to assess.
OAIS (ISO 14721:2025) is a reference model for an archive system responsible for long-term preservation and access for a Designated Community. It describes functions such as ingest, archival storage, data management, access, and dissemination; it is not a product specification that guarantees authenticity through checksums or encryption. PREMIS is a data dictionary that links preservation metadata to Objects, Events, Rights, and Agents. Neither replaces operational policy, organizational accountability, or actual checking.
A review sequence for arrangement and preservation
- Identify creators and activities; do not collapse co-creation, delegation, or succession into one actor.
- Record inventories and system history that support an existing arrangement, including gaps.
- Describe any new arrangement separately from original order.
- Link each digital object’s baseline checksum to check events, tool, date, result, and error response.
- Assess format identification/validation, readability, structural completeness, access, and transformations as distinct questions.
This is a review framework for a repository’s own policy, not a report on an inspected collection.
Sources: ISO 14721:2025 OAIS, Library of Congress PREMIS 3.0.