A fixity check fails; quarantine the affected representation, verify a recovery copy and record preservation decisions.
Trusted Records · Platform
Long-term digital preservation
Maintain readability, integrity verification and record context over time; backup is only part of recovery.
Inputs and starting conditions
SIP, content/metadata, formats, representation information, preservation policy and designated-user requirements.
Workflow and control gates
- 01Validate SIP
- 02Create / manage AIP
- 03Check fixity / replicas
- 04Assess format risk
- 05Preservation action
AIPs retain content and preservation information; DIPs support dissemination. Fixity compares bytes with recorded values, not provenance by itself. Monitor readability and representation/version lineage as well as copies.
Exceptions and recovery
Fixity mismatch: isolate the suspect copy, compare replicas and investigate before repair. Format risk needs an approved plan/action; evidence renewal requires verified services/configuration.
Roles, outputs and states
| Responsibilities | Evidence and states |
|---|---|
| Preservation officers plan; owners approve changes; repository operators execute; auditors inspect before/after evidence. | SIP validation, AIP/version, fixity reports, replica history, format risks, approvals and repository health. States: validating → preserved → at risk / action → verified. |
Scenario and acceptance criteria
Complete only when
Reports retain algorithm, value, time and recovery outcome.
Interfaces for this workflow
Integration handoff
End-to-end integration workflows
Connect technical states to business decisions instead of merely listing endpoints.
Read detailsOpenAPI and Swagger Reference
The proposed contract is rendered from one local specification; no network Try-It or real credentials.
Read detailsErrors and next actions
A consistent error envelope guides recovery without disclosing sensitive data.
Read detailsContent, usability and evidence
Govern
Record/version, authority, retention and holds
Store content
Source bytes, replicas, locations and operator permissions
Preserve usability
Formats, representation information, migration/lineage
Preserve evidence
Contract-specific validation, profiles, receipts, renewal and verification
Backup / DR
Restore operations without replacing preservation layers
LTANS — long-term evidence preservation
Connect records lineage to Mobile-ID’s published LTANS capability; agree the Records configuration in a contract and profile.
Read detailsPreservation Profile Center
Choose preservation configurations by record class, designated community and required evidence. Illustrative profiles are not approved service offerings.
Read detailsPreservation standards and evidence
Standards → controls → workflows → contracts → evidence. Reference design mappings rather than Trusted Records certification.
Read detailsService Playground — task-based experience
Exercise a records workflow with forms, requests/responses and a timeline. Use synthetic data in offline simulation or a local HTTP mock.
Read detailsContent and evidence preservation
Choose a profile before admission. Separate content storage, readability, LTANS evidence and backup/DR. Mobile-ID connectivity is based on published capability; storage models, APIs, receipts and deployment authority require agreement. Hash/fixity checks do not replace signature or provenance validation.
Continue the workflow
Conversion and migration
Change formats or repositories while preserving source–target reconciliation, version lineage and exceptions.
Read detailsTwo journeys, one records lifecycle
Connect paper and born-digital records through persistent identifiers, policies and evidence.
Read detailsIntegration quickstart
Exercise ingest → job tracking → registration → verification with synthetic data.
Read detailsStart with a verifiable scope.
Agree record classes, quality criteria, permissions and evidence before scaling.
Plan assessment