Skip to content

Archival Succession and Migration Plan

Document — instantiates Collective Memory Curation

Preserves custody, formats, context, rights, restrictions, governance decisions, relationships, and responsibility across steward or platform change.

An Archival Succession and Migration Plan is the forward-looking document that governs a memory collection's handoff from one steward, format, or platform to the next — and its defining conviction is that the thing most likely to be lost in that handoff is not the files but the governance attached to them. A bit-perfect copy that arrives without its consent terms, its provenance links, its embargo dates, and its record of who decided what and why is no longer collective memory; it is a bag of undifferentiated data. The plan therefore treats custody, rights, restrictions, context, and prior curation decisions as the payload, and the files as merely one part of it. It is the one mechanism whose subject is the boundary between stewards rather than the collection itself.

Example

A regional labor union is dissolving its independent archive and transferring seventy years of strike photographs, grievance files, and oral-history cassettes to a university library's special collections. A naive transfer would ship the boxes and the disk image and call it done. The succession plan does more. It builds a crosswalk mapping the union's home-grown catalog fields to the library's descriptive schema, so that "photographer unknown — taken during the 1974 lockout" survives as context rather than collapsing into a blank creator field. It carries forward a rights register noting which oral-history narrators consented only to research use and which cassettes carry a twenty-year embargo that has eight years left to run. It names the specific archivist who will hold decision authority after transfer, the budget line that funds cassette digitization before the tape degrades, and the date the new steward must review whether the embargoes still hold. Two years later, when a filmmaker requests a restricted interview, the library can answer from the migrated consent record instead of guessing — the memory's governance crossed the boundary intact.

How it works

The plan is assembled as a small set of linked registers rather than prose. A format and fidelity crosswalk lists each material type, its target format, and the significant properties that must survive conversion. A rights and restriction register carries embargoes, consent scopes, and cultural-access rules forward with their expiry and review dates attached. A decision log transfers the reasoning behind past appraisal and restriction choices so the new steward can revisit rather than reinvent them. A responsibility matrix names who holds authority, resources, and review duties after the handoff. Finally, an acceptance test verifies — before the old steward stands down — that a sample of objects arrives with context, rights, and access controls functioning, with a dark-archive fallback held until the test passes.

Tuning parameters

  • Migration cadence — a one-time transfer versus a standing schedule of periodic format refreshes. Continuous migration fights format obsolescence but consumes steward capacity indefinitely.
  • Fidelity target — how many significant properties must survive conversion. Higher fidelity resists silent loss but multiplies storage and tooling cost.
  • Custody model — central single-steward transfer versus federated or community-held copies with shared minimum metadata. Distribution buys resilience and legitimacy at the price of coordination overhead.
  • Verification depth — spot-check versus full acceptance test of the arriving collection. Deeper testing catches broken context and rights early but delays the handoff.
  • Restriction carry-forward — whether embargoes reset, expire, or transfer untouched at the boundary. Untouched transfer honors consent but can freeze restrictions no one re-examines.

When it helps, and when it misleads

Its strength is that it directly attacks custodian dependency — the failure where rights, formats, relationships, and decisions all live with one person or platform and vanish when they do. It converts a fragile "it's all on Marcia's laptop" into transferable governance[1], and it forces the digital-dark-age problem into view while the originals are still readable.

Its failure mode is the "lift and shift": a technically successful migration that moves every byte while quietly dropping the consent envelope, the positionality notes, and the decision history — leaving intact files that no longer carry the conditions under which people contributed. The classic misuse is to let a platform vendor's export tool define what counts as "the collection," so that whatever the tool cannot serialize is deemed not to exist. The guarding discipline is the acceptance test against context and rights, not merely file count: a migration that loses consent or description is a memory failure even when every bit survives.

How it implements the components

  • stewardship_retention_and_review_cycle — the plan is the succession and continuity leg of the steward cycle: it names the next steward, the funding, and the post-transfer review date.
  • provenance_context_and_positionality_record — it carries these records across the boundary via the field crosswalk, so origin, custody, and positionality survive the schema change.
  • access_consent_and_sensitivity_envelope — it migrates embargoes, consent scopes, and cultural-access rules with their expiry and review dates attached.
  • legal_hold_and_evidentiary_original_guard — before any conversion that would destroy an original, it checks for active holds and evidentiary-original duties and preserves the source.

It does not catalog the collection's own absences — plural_contribution_and_representation_map — that is Memory Gap and Silence Register; a succession plan moves what exists across a handoff, while the register names what is missing from the collection. Nor does it run appraisal (transparent_appraisal_and_selection_rule) or surface memory at decisions (memory_activation_and_retrieval_design).

Editorial Notes

Form Classification

Form family: Representation, Specification & Plan

Rationale: Preserves custody, formats, context, rights, restrictions, governance decisions, relationships, and responsibility across steward or platform change, making its operative form a non-executable information artifact that externalizes static or prospective structure.

Independent corroboration: The frozen evidence defines Archival Succession and Migration Plan as 'Preserves custody, formats, context, rights, restrictions, governance decisions, relationships, and responsibility across steward or platform change', so its operative form is Representation, Specification & Plan.

Review outcome: Independent reviewer agreement; high confidence.

Origin Attribution

Primary origin: Library & Information Science

Origin pattern: Cross-disciplinary synthesis

Present-day reach: Multi-domain

Rationale: Digital-preservation and archival-succession practice treats representation information, provenance, rights, restrictions, and stewardship as part of the preserved package.

Related originating lineages:

Review outcome: Independent reviewer agreement; high confidence.

References

[1] Consultative Committee for Space Data Systems. Reference Model for an Open Archival Information System (OAIS). CCSDS 650.0-M-2 / ISO 14721:2012 (2012). Requires institutional preservation responsibilities, a formal succession plan, and independent understandability beyond individual custodians. registry