Operational metadata layer

DIO/ODI Corpus Metadata Registry

The Corpus Metadata Registry is the operational metadata source of truth for the DIO/ODI publication corpus and the DIO/ODI Reference Model. It records publication identities, versions, relations between works, bibliographic references, external representations, and ordered keyword profiles.

Registry status: Operational metadata registry

Scope: DIO/ODI corpus and DIO/ODI Reference Model publication metadata

Authority: The registry governs publication metadata and inter-work relations. It is separate from the canonical Reference Vocabulary: registry updates do not change vocabulary concepts, hierarchy, definitions, or provenance.

Registry components

Works

Canonical identities and publication metadata for DIO/ODI works and Reference Model releases, including identifiers, versions, dates, and inclusion history.

JSON

Relations

Directed inter-work relation graph. Relations retain their direction and semantics; only records explicitly marked approved_for_zenodo: true are eligible for automatic projection into Zenodo metadata.

JSON

References

Canonical bibliographic strings and identifiers for internal DIO/ODI works and external references.

JSON

Distribution representations

External distribution copies, variants, and supplementary representations, with relation types and verification status preserved rather than collapsed into generic equivalence.

JSON

Keyword profiles

Canonical ordered keyword grammar, work-specific profiles, chunk structure, and non-export aliases. The sequence is governed by explicit ordering and completeness rules.

JSON

How the registry is used

  1. Maintain work identities, DOI and version information, relations, distribution representations, keyword profiles, and citations in the registry.
  2. Before a new Reference Model release, project only the approved metadata subset into the root .zenodo.json file.
  3. After Zenodo assigns a version-specific DOI, synchronize the live registry and citation surfaces without rewriting immutable archived snapshots.

Documentation and source

For the complete operational workflow, field-level conventions, relation discipline, version-scoped distribution rules, and keyword governance, consult the technical registry documentation (Markdown). The machine-readable JSON files linked above are the structured registry records.

Maintained by Daniel Beránek · ORCID 0009-0004-0050-0264 · CC BY 4.0