Metadata and classification
Metadata contracts retain schema/version, file plans and source identifiers.
Fields and mappings
Examples include schemaVersion, title, recordClass and sourceRef. Proposed OpenAPI defines required/optional fields; projects add dictionaries, types, sensitivity, language and validation.
Controlled changes
PATCH records/{recordId}/metadata requests correction with expectedVersion and reason. Version conflicts return 409; declared records do not use silent last-write-wins. Metadata permission does not imply content modification.
AI and schemas
AI results retain confidence/model/version and image sources. Only rule-reviewed values become official metadata, with before/after lineage. Match classifications to the effective file plan.
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