Map objects
Map document/revision/attachment to ArchiveRequest; identify business fields outside the schema.
MOBILE-ID · TRUSTED LTANS
Integration for software providers
Add preservation to DMS/ECM/eContract using LTANS record IDs and reconcilable event journeys.
Problem and records to preserve
Building long-term evidence internally requires sustained algorithm, TSA and transfer management.
SYNTHETIC CASE
Synthetic DMS integration transaction
APP-SYN-001| Element | Illustrative scope |
|---|---|
| Decision makers / users | Product owners, architects and ISV integration teams |
| Source system | DMS / ECM / eContract / ERP |
| Revision | Retain source transaction/revision mapping and idempotency key across timeouts. |
| Record relationship | Applications retain source/revision-to-archiveId/jobId mappings. |
Sector-specific record journey
Choose custody
Choose PROVIDER_MANAGED, CUSTOMER_MANAGED or HASH_ONLY and exercise durable reread rights.
Submit async
Persist idempotency key with request content; reconcile the original transaction after disconnect.
Receive events
Verify webhook signatures and persist inbox entries; late events require current-state reconciliation.
Retain LTANS IDs
Retain archiveId/jobId/resultReference in source mappings; separate UI labels from enums.
Source lookup
Authorize lookup/export across source and LTANS; test cross-tenant denial during PoC.
Delivered artifacts
| Recipient | Artifact |
|---|---|
| Source system | Intake receipts, source/revision-to-archiveId/jobId mappings and per-item errors. |
| Package recipient | Receipts, job results and reports for the source application. |
| Record owner / operations | Completed/outstanding inventory, applied decisions and report references; no automatic legal conclusion. |
Rights, retention and deployment
Machine scopes differ from user permissions; no frontend secrets.
Agree contracting party, first-line support, branding rights and metering units before commercialization.
Retention authority and exit
The owner must approve the retention authority and trigger for this record class: A source application completes a preservation-relevant transaction.
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 | Detect key reuse with changed body; duplicate webhooks have no repeated effects. |
Scope a PoC for this dossier
Complete an end-to-end journey, test duplicates and reordered events; retain versioned reconciliation results.
Prepare a sector-specific requestFinalization point and specific acceptance
| Control point | Requirement |
|---|---|
| Source event | A source application completes a preservation-relevant transaction. |
| Revision / decision | Retain source transaction/revision mapping and idempotency key across timeouts. |
| Test and expected result | Same key/different payload is rejected; duplicate callbacks do not create another source record. |
Sample inventory/hashing checks bytes only. Authorization, decision and state cases must run in the provisioned test environment before business acceptance.
Source-system handoff record
| Information | Value / decision |
|---|---|
| Record | APP-SYN-001 |
| Source system | DMS / ECM / eContract / ERP |
| Revision relationship | Applications retain source/revision-to-archiveId/jobId mappings. |
| Recipient and output | Receipts, job results and reports for the source application. |
| Rights and authority | Machine scopes differ from user permissions; no frontend secrets. |
| Required rejection test | Detect key reuse with changed body; duplicate webhooks have no repeated effects. |
Sector information is source business metadata, not automatically new REST fields. Agree field mapping and ownership before a PoC.