MOBILE-ID · TRUSTED LTANS

DMS / ECM / Records Management

Retain exact record revisions and attachment relationships across DMS migrations, format changes and lifecycle decisions.

Problem and records to preserve

Revision links may be lost during repository migration; metadata alone does not prove original bytes.

SYNTHETIC CASE

Synthetic DMS record set

DMS-SYN-001

Element	Illustrative scope
Decision makers / users	Records managers, archivists and DMS/ECM product owners
Source system	DMS / ECM
Revision	Rename/storage changes retain sourceId; format conversion creates linked derivatives.
Record relationship	A new revision retains its parent and matching attachments.

Sector-specific record journey

Close revision

Freeze the DMS revision with document ID and attachments; later edits create a new revision.

Inventory

List relative paths, MIME, sizes and member digests; report omissions before submission.

Bind source ID

Map source ID/revision to archiveId; filenames are not unique identifiers.

Evidence

Track jobs and evidence revisions; distinguish receipts from EVIDENCE_READY.

Sync DMS

Sync results to DMS through deduplicated events or reconciliation queries; do not overwrite source bytes.

Delivered artifacts

Recipient	Artifact
Source system	Intake receipts, source/revision-to-`archiveId`/`jobId` mappings and per-item errors.
Package recipient	Document/revision-to-`archiveId` mapping with corresponding evidence inventory.
Record owner / operations	Completed/outstanding inventory, applied decisions and report references; no automatic legal conclusion.

Rights, retention and deployment

DMS and LTANS read/export permissions are checked separately.

Choose BYOS if the DMS retains originals; agree reread checks and key lifecycle.

Retention authority and exit

The owner must approve the retention authority and trigger for this record class: DMS finalizes a record revision and annex inventory.

Archival Period & Retention Legal Hold Deployment Model Comparison

Sample dossier and tests

Synthetic text files exercise inventory and hashing; they are not signed contracts, real records or ERS/XMLERS.

Download synthetic dossier

Test	Expected outcome
Intact	File inventory, size and SHA-256 match the manifest.
Missing / changed bytes	The verifier rejects the package without claiming inventory success.
Sector business case	Changing a frozen attachment must fail digest reconciliation.

Sample package and independent checks Integration test plan

Scope a PoC for this dossier

Submit two versions of one record; verify distinct digests, source traceability and reconcilable exports.

Prepare a sector-specific request

Evidence Record Model Archival Period & Retention

Finalization point and specific acceptance

Control point	Requirement
Source event	DMS finalizes a record revision and annex inventory.
Revision / decision	Rename/storage changes retain sourceId; format conversion creates linked derivatives.
Test and expected result	Missing annexes or wrong revision mappings fail inventory checks.

Sample inventory/hashing checks bytes only. Authorization, decision and state cases must run in the provisioned test environment before business acceptance.

End-to-end reference dossier Integration test plan Design a Trusted LTANS PoC

Source-system handoff record

Information	Value / decision
Record	DMS-SYN-001
Source system	DMS / ECM
Revision relationship	A new revision retains its parent and matching attachments.
Recipient and output	Document/revision-to-archiveId mapping with corresponding evidence inventory.
Rights and authority	DMS and LTANS read/export permissions are checked separately.
Required rejection test	Changing a frozen attachment must fail digest reconciliation.

Sector information is source business metadata, not automatically new REST fields. Agree field mapping and ownership before a PoC.