Storage and data preservation
Agree storage location, retention, recovery and exit; avoid tying record ownership to a format or provider.
Responsibility matrix to agree
| Item | Decision | Acceptance evidence |
|---|---|---|
| Data location | Customer/provider agree environment/region | Store/operator inventory |
| Fixity | Preservation team checks approved cadence | Copy/version-level reports |
| Recovery | Agree configuration-specific RTO/RPO | Exercise and reconciliation records |
| Holds and retention | Owner/authorized approver decides | Versioned policies and hold decisions |
| Export/exit | Agree recipient, format and retained data | Manifest, hashes and receipt |
Storage and preservation
Storage keeps data available; preservation adds fixity, metadata, versions and long-term usability. Backups aid recovery but do not replace preservation policy or legal holds.
Project-specific commitments
Agree data location, operator, copies, inspection cadence, retention, RTO/RPO and support timing in the contract/profile. The baseline contains no approved values; this page makes no default numeric commitments.
Service exit
Deliver content with metadata, manifests, necessary histories and integrity evidence to authorized recipients. Reconcile received copies, required retained copies and deletable data; handle backups under an approved schedule.
Content 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
Two 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 detailsIntegrity, provenance and evidence
Each evidence type answers a different question; hashes, timestamps and approvals are not interchangeable.
Read detailsStart with a verifiable scope.
Agree record classes, quality criteria, permissions and evidence before scaling.
Plan assessment