Edition and custody fields
Document editions, release events, page locators, digital custody and archival reviews.
Editions & custody · object
Edition and custody structure
Start with a top-level field, then follow its values and alternatives. The index stays available as you explore.
Required fields must be present. Lists may be empty unless a minimum is specified.
Extra fields: Not allowed at this document root.
Choose an entity type
10 alternativesEach entry in entities uses one type. Include only the types your material needs.
- Document editionOne copy's metadata, markings, page count and file identity.
- Document eventCreation, release or declassification of a specific edition.
- Digital artifactAn exact file, its capture metadata, hashes and derivation.
- Custody actionA file handoff or other action, including an explicit earlier gap.
- External identifierA catalog reference scoped to an edition or observation.
- Identifier checkWho checked a particular identifier, when and with what result.
- WitnessShared person declarations, qualifications and relevant time.
- AccountShared account declarations, speakers and source wording.
- ProcedureShared procedure declarations and reported results.
- Witness groupShared group declarations, rosters and reported counts.
Document identity
5 fieldskindstringIdentifies the document kind.RequiredschemaVersionstringThe explicit document contract version.RequiredidstringA scoped document identity.RequiredrecordedAtstringWhen these declarations were assembled, separate from release, creation and review dates.Required4 nestedrecordedBystringWho assembled the declarations.Required
Snapshots and declarations
3 fieldsobservationRefobjectExact observation snapshot described by these declarations.Required3 nestedcontextRefslist of objectExact contextual snapshots used by this document.Required4 nestedentitieslist of choiceTyped declarations for particular editions, artifacts, custody actions and identifiers, alongside witness and account detail.Required11054 nested
How to read this reference npm 2.0.0-beta.4
Required is local. A field marked required must exist in its containing object or selected alternative. A required list can be empty unless minItems says otherwise. Choose the alternative that describes your data; do not combine every alternative.
Structure and meaning are checked separately. These entries come from the published package. Explanations and grouping are editorial. Follow the validation guide for semantic checks such as unresolved references.
- Schema identifier
urn:disclosureos:experimental:research-entities:0.2.0- Package export
@disclosureos/records/experimental/v2/entities/schema/0.2.0
Repeated keys in different branches are separate schema entries. Their exact paths and field links preserve that context. The schema version is independent of the npm package version.