The short answer
Inventory archive files and formats, preserve checksums and source metadata, identify software, keys, fonts, schemas, code lists, and relationships needed to interpret them, then open and sample-render the package in a controlled environment. Record native, normalized, partially readable, dependency-bound, corrupt, and unknown outcomes without discarding originals.
Operational checklist
Mark your progress, then save a working copy. Selections reset when you leave this page. A checked box is not an approval or evidence of completion.
☐
Archive inventory complete
☐
Checksums retained
☐
Formats and versions identified
☐
Dependencies documented
☐
Representative samples opened
☐
Meaning and relationships tested
☐
Originals preserved
☐
Retest scheduled
0 of 8 marked
Key takeaways
- Possession of bytes is not proof of future usability.
- Preserve originals and document normalized copies.
- Interpretation dependencies belong in the archive package.
Inventory formats and dependencies
Record file ID, path, size, checksum, media type, format/version where supportable, source module, export time, property/time scope, encoding, compression, encryption, key custody, schema/data dictionary, code lists, relationships, rendering software, and access owner.
Library of Congress guidance identifies disclosure, adoption, transparency, self-documentation, external dependencies, patents, and technical protection as format sustainability factors. It does not select a PMS archive format for the organization.
Test bytes, rendering, and meaning separately
| Outcome | Byte/open test | Interpretation test | Disposition |
|---|---|---|---|
| Native readable | Original opens and checksum matches | Fields/relationships understood | Retain tested method |
| Normalized copy | Derivative opens | Transform and losses documented | Preserve original plus derivative |
| Dependency-bound | Requires old software/key/font/schema | Dependency available and tested | Package dependency or remediate |
| Partial/corrupt | Some content fails | Affected scope known | Re-export or document loss |
| Unknown | Format or meaning unresolved | No supported interpretation | Hold decommission dependency |
Make readability repeatable
Store the test environment or instructions, sample IDs, expected results, observed results, tool versions, access steps, and next retest date. Test representative large, old, non-English, attachment-rich, and relational records.
A normalized PDF may preserve appearance while losing searchable fields or relationships; record that tradeoff explicitly.
Close with checksums, interpretation dependencies, samples, and retest ownership
Name the reviewed population, cutoff, evidence version, decision owner, unresolved exceptions, next checkpoint, and downstream records updated. Preserve the superseded state; a clean current screen is not a substitute for the correction or exception history.
Reopen the record if the population, authority, source version, external outcome, or dependent report changes after sign-off.
Edge cases
- Encrypted export lacks tested key recovery: treat as unreadable dependency.
- CSV opens but code meanings are missing: bytes pass, interpretation fails.
- Normalized copy changes layout or fields: document losses and keep native original.
Sources and references
Follow each source to check the underlying claim. Access checks and professional review are different steps.
1. Primary source · Library of Congress
Sustainability of Digital FormatsDisclosure, adoption, transparency, self-documentation, dependencies, patents, and technical protection affect long-term format usability.
Source checked 2026-09-18
Automated source-access check: 2026-09-18.
Continue the workflow
Migration audit-log preservation and retrieval samplingSource-system decommission acceptance after PMS migrationVerify documents and attachments after a PMS migrationRevision history
2026-09-18
Initial Phase 5 operational article with distinct intent, original artifact, source limits, and AI-assisted technical review.