Mobile-ID · Long-term digital evidence preservation
Customers and partnersWorkflow demoContact
Trusted LTANS
Evaluate
MOBILE-ID · TRUSTED LTANS

Education and digital credentials

Preserve credentials and transcripts with issue decisions and linked corrections without exposing full student records.

Problem and records to preserve

Credentials are checked years later, across software generations and administrative teams.

SYNTHETIC CASE

Synthetic award decision and credential set

EDU-SYN-001
ElementIllustrative scope
Decision makers / usersAcademic affairs, examination, credential and IT teams
Source systemAcademic/credential management
RevisionA correction has its own ID, original link and approval basis; verify the exact credential/revision.
Record relationshipA correction has a new ID linked to the original credential.

Sector-specific record journey

01

Finalize issue

The SIS retains issue-decision ID, credential ID and inventory.

02

Preserve signed revision

Receive exact bytes and validation material from the selected signing workflow.

03

Authorize lookup

A public code does not grant full transcript access.

04

Correct

Issue a new revision linked to the old with a reason.

Delivered artifacts

RecipientArtifact
Source systemIntake receipts, source/revision-to-archiveId/jobId mappings and per-item errors.
Package recipientCredential inventory, correction history and authorized verification report.
Record owner / operationsCompleted/outstanding inventory, applied decisions and report references; no automatic legal conclusion.

Rights, retention and deployment

Academic services owns records; verifiers receive only authorized information.

VNeID/RSHUB and Trusted SIC can support source-system signing under integration scope; LTANS preserves outputs and relevant validation material.

Retention authority and exit

The owner must approve the retention authority and trigger for this record class: An award decision finalized by academic administration.

Sample dossier and tests

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

Download synthetic dossier
TestExpected outcome
IntactFile inventory, size and SHA-256 match the manifest.
Missing / changed bytesThe verifier rejects the package without claiming inventory success.
Sector business caseCorrections preserve originals; verification does not expose complete student records.

Scope a PoC for this dossier

Test original and corrected credentials; verification must identify the version without exposing full transcripts.

Prepare a sector-specific request

Finalization point and specific acceptance

Control pointRequirement
Source eventAn award decision finalized by academic administration.
Revision / decisionA correction has its own ID, original link and approval basis; verify the exact credential/revision.
Test and expected resultPublic lookup cannot download transcripts; correction cannot overwrite the original.

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

InformationValue / decision
RecordEDU-SYN-001
Source systemAcademic/credential management
Revision relationshipA correction has a new ID linked to the original credential.
Recipient and outputCredential inventory, correction history and authorized verification report.
Rights and authorityAcademic services owns records; verifiers receive only authorized information.
Required rejection testCorrections preserve originals; verification does not expose complete student records.

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

Next steps

Search LTANS documentation

Expanded illustration