Archival Provenance Metadata Template¶
A metadata template — instantiates Carrier-Independent Work Identity Governance
A structured template for capturing an instance's origin, custody, and transformation history, so that a claim to be the same work rests on documented evidence rather than assertion.
A register can declare that this file is still the same work; only evidence can back the declaration. Archival Provenance Metadata Template is the fill-in schema that captures that evidence, per instance: where it came from, whose hands it passed through, what was done to it, and how each step can be verified. Its defining idea is that identity continuity is an evidentiary claim — a modified instance is the same work because there is an unbroken, checkable record of how it got from origin to here, not because someone says so. It is not the identity statement and not a lineage picture; it is the structured custody-and-transformation record attached to the object itself.
Example¶
A climate research dataset moves from an instrument's raw output, through a lab's cleaning scripts, into a national repository, and out to a dozen re-users. Each hop is a chance for the "same dataset" claim to quietly break — a silent unit conversion, a dropped station, a re-encoding. The Archival Provenance Metadata Template travels with the object and records, at every boundary: the source it derived from, the agent and institution that held it, the transformation applied, the date, and a fixity value (a checksum) that lets any later user confirm the bytes have not changed since. Filling it against an established schema — real examples include PREMIS and W3C PROV — means a re-user five years on can trace the published dataset back to the instrument and satisfy themselves it is the same work, degraded by nothing they were not told about.
How it works¶
What distinguishes this from a narrative or a graph is that it is a per-object, boundary-triggered record: it is filled in at each custody handoff or transformation, not reconstructed afterward. Each entry captures the source, the agent, the event, the time, and a fixity/verification value; the entries accumulate into the object's origin-to-present trace. It captures raw evidence — it does not judge whether that evidence adds up to sameness, and it does not render the accumulated history as a navigable structure. Those are downstream jobs.
Tuning parameters¶
- Event granularity — every operation versus milestone transformations only. Fine grain catches silent corruption; coarse grain is affordable but hides small losses.
- Fixity method — plain checksum versus cryptographic signature. Stronger methods make the record tamper-evident rather than merely descriptive.
- Custody detail — named individuals versus institutions only. Named custody is more accountable; institutional custody is more durable and less privacy-fraught.
- Schema conformance — adopt a standard (PREMIS, PROV) versus a bespoke template. Standards buy interoperability; bespoke buys fit.
- Retention — how long provenance is kept and where. Provenance that outlives the object is what makes late continuity claims checkable.
When it helps, and when it misleads¶
Its strength is that it converts "trust me, it's the same" into "here is the trail" — the one thing that lets an identity claim survive a change of custodian, format, or decade.
Its failure modes are the ones that afflict any chain of custody: a gap anywhere breaks the whole claim, and provenance can be incomplete, mistaken, or forged.[n1] A neatly completed template lends an object false confidence — the form being full is not the same as the trail being true. The classic misuse is to back-fill provenance after the fact, reconstructing a tidy custody story to justify a continuity that was never actually maintained. The discipline that guards against this is to capture at the boundary in real time and to use tamper-evident fixity, so the record is contemporaneous evidence rather than a later rationalization.
How it implements the components¶
Archival Provenance Metadata Template realizes the evidentiary side of the archetype — the components that record what happened and where it came from, not what it is or whether it still counts:
provenance_lineage_trace— it captures the origin, custody chain, and derivation of the instance.modification_event_log— it records each transformation event: what changed, when, by whom, and from what source.
It does not assemble these entries into a navigable lineage structure (Version Lineage Graph), state the work's identity or authority (Abstract Work Register), or judge whether the recorded changes preserve the work (Identity Preservation Checklist and Semantic Diff Review).
Related¶
- Instantiates: Carrier-Independent Work Identity Governance — it supplies the documented history other mechanisms lean on when a continuity claim is challenged.
- Sibling mechanisms: Version Lineage Graph · Migration Context Preservation Plan · Abstract Work Register · Edition and Manifestation Catalog · Fork Decision Record · Governed Translation or Adaptation Review · Identity Boundary-Case Table · Identity Preservation Checklist · Persistent-Identifier Resolution Policy · Semantic Diff Review · Work–Expression–Manifestation Matrix
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: The template is filled at every custody handoff or transformation and accumulates source, agent, event, time, and fixity evidence into an object's origin-to-present trace, so its operative form is a provenance record.
Nearest alternative: Representation, Specification & Plan — The empty schema is a template, but deployed instances gain value from accumulating actual custody and transformation history.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Library & Information Science
Origin pattern: Convergent development
Present-day reach: Multi-domain
Rationale: Archival metadata standards such as PREMIS and provenance schemas capture origin, custody, transformation, time, and fixity per object.
Related originating lineages:
- Computer Science & Software Engineering — Digital-preservation schemas, persistent identifiers, checksums, and machine-readable event records implement the template.
- Criminology & Forensic Studies — Chain-of-custody practice supplies the contemporaneous, unbroken handling trace and the consequence of a gap.
- Material Culture & Museum Studies — Accession and object-history practice records custody, condition, and transformations across manifestations.
Review resolution: Library and archival science is the agreed primary. Digital provenance standards, forensic chain of custody, and museum accession practice are independently formative; general history and law are adjacent uses or governance contexts rather than necessary additional origins.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] The chain of custody is the documented, unbroken record of who created, held, and handled an item and when — used in law, forensics, and archives to vouch for authenticity and integrity. A single gap in the chain undermines the claim no matter how convincing the item looks, which is why the record must be contemporaneous rather than reconstructed. ↩