Category: Metadata Standards

Metadata Schema

Also known as: Metadata Scheme, Metadata Standard

Simply put

A metadata schema is a predefined structure that sets out what information should be recorded about a resource and how that information should be organized. It typically defines the fields to be used, such as dates, names, and titles, along with rules for how each field should be filled in. This shared structure helps ensure that metadata is consistent so resources can be reliably identified, described, and retrieved.

Formal definition

A metadata schema is a predefined set of elements used to structure metadata, specifying element names, their meanings, and content rules governing the values each element may hold. It establishes the overall framework for how metadata is set up, commonly addressing standardized treatment of shared components such as dates, names, and titles. In practice, a schema functions to support accurate and consistent identification, description, and retrieval of resources, and specific schemas vary in scope and complexity depending on the community, domain, and system in which they are applied. Note that in recordkeeping contexts, a metadata schema defines the structure and rules for descriptive, administrative, and technical metadata, but the choice and application of a particular schema depends on organizational policy, jurisdiction, and sector requirements, which fall outside the scope of this general definition.

Why it matters

A metadata schema provides the shared structure that allows metadata to be consistent across records, systems, and over time. Without an agreed schema, the same information may be recorded in different ways or in different places, making it difficult to reliably identify, describe, and retrieve resources. In recordkeeping contexts, this consistency underpins the ability to locate records when needed and to understand what they are, who created them, and when, which supports the broader goals of accurate description and dependable retrieval.

Consistent metadata structured according to a schema also contributes to the qualities that distinguish a record from mere information, such as usability over time. When descriptive, administrative, and technical metadata are captured against defined elements with clear content rules, records can be more readily understood and managed throughout their lifecycle. This is particularly important where resources must remain identifiable and retrievable long after their creation, and where different individuals or systems must interpret the same metadata in the same way.

The practical value of a schema depends heavily on context. Schemas vary in scope and complexity according to the community, domain, and system in which they are applied, and the choice of a particular schema in a recordkeeping setting typically depends on organizational policy, jurisdiction, and sector requirements. As a result, the benefits of a metadata schema are realized only when the schema is well matched to the resources it describes and consistently applied.

Who it's relevant to

Records managers

Records managers rely on metadata schemas to ensure that records are described consistently so they can be reliably identified and retrieved across their lifecycle. The choice of a particular schema in a recordkeeping context typically depends on organizational policy and applicable sector requirements.

Archivists and description specialists

Those responsible for describing resources use metadata schemas to structure descriptive, administrative, and technical metadata against defined elements and content rules, supporting accurate description and long-term usability of holdings.

Information governance officers

Information governance officers are concerned with how schemas are selected and applied as part of broader policy, ensuring that metadata practices align with organizational, jurisdictional, and sector requirements. This governance dimension sits alongside, and is broader than, the records management task of consistent description itself.

System and data managers

Those implementing schemas within systems apply element definitions and content rules so that metadata is captured consistently. Because schemas vary in scope and complexity depending on the domain and system, matching the schema to the resources it describes is an important part of their work.

Inside Metadata Schema

Metadata Elements

The individual data fields defined by the schema, such as title, creator, date of creation, and classification, each capturing a specific attribute about a record or information object.

Element Definitions and Semantics

Statements that specify the meaning, intended use, and scope of each element, so that values are recorded consistently and interpreted the same way across systems and over time.

Encoding and Value Constraints

Rules governing how values are expressed, which may include controlled vocabularies, permitted formats, or syntax requirements to support consistency and interoperability. The specific constraints depend on organizational policy and the systems involved.

Obligation and Cardinality Rules

Indications of whether an element is mandatory, optional, or conditional, and how many times it may occur, which help determine the minimum metadata needed for a record to be adequately described and managed.

Structural Relationships

The organization of elements into groups, hierarchies, or entities, and the relationships between them, which allow metadata to reflect the context and dependencies among records and their aggregations.

Application and Governance Guidance

Accompanying rules on how the schema is to be applied, maintained, and extended, typically reflecting an organization's recordkeeping policy and, where relevant, applicable standards.

Common questions

Answers to the questions practitioners most commonly ask about Metadata Schema.

Is a metadata schema the same thing as the record itself, or a substitute for it?

No. A metadata schema is a structured specification of the descriptive, contextual, and management information about a record; it is not the record and does not replace it. Metadata typically supports the identification, retrieval, understanding, and management of records, but the authoritative record remains a distinct object. Confusing the schema (or the metadata it governs) with the record can undermine the properties, such as authenticity, reliability, integrity, and usability, that give a record its evidential value.

Is adopting a metadata schema simply a technical or software configuration task?

Not in most cases. While a schema is often implemented within a system, it is fundamentally a recordkeeping and governance instrument rather than a purely technical artifact. Its design typically reflects policy decisions about classification, retention, access, and accountability, and it usually requires input from records, compliance, privacy, and business stakeholders. Treating it only as system configuration risks omitting the contextual and management metadata needed to sustain records as evidence over time.

How should an organization decide which metadata elements to include in its schema?

Element selection typically follows from the purposes the metadata must serve, identification, retrieval, contextual understanding, and lifecycle management, and from applicable policy and, in many jurisdictions, regulatory obligations. Organizations often distinguish mandatory elements needed to establish and manage records as evidence from optional elements that add descriptive value. The appropriate set depends on organizational policy, sector, and jurisdiction, and is generally shaped in consultation with records, compliance, and business stakeholders rather than derived from a single fixed list.

Can an existing or standardized metadata schema be adopted, or must one be built from scratch?

Many organizations adapt existing or standards-based schemas rather than building entirely new ones. Recordkeeping standards and national archives guidance often provide reference models or element sets intended to be tailored to context. Adopting an established schema can promote consistency and interoperability, but it typically still requires mapping to organizational classification, retention, and access requirements. The suitability of any given schema depends on the organization's needs, systems, and jurisdictional obligations.

How is metadata captured and applied consistently across records?

Consistency is often supported through a combination of automated capture at the point of record creation or capture, controlled vocabularies or value lists, and defined rules for mandatory elements. Some metadata may be inherited from classification schemes or business systems, while other elements may require manual entry governed by policy. Depending on organizational policy and system capabilities, validation controls and periodic quality checks are commonly used to reduce inconsistency, since unreliable metadata can weaken retrieval and lifecycle management.

How should a metadata schema be maintained and updated over time?

A metadata schema is typically treated as a governed artifact subject to change control, so that revisions are documented and their effect on existing records is understood. Changes often arise from evolving business needs, policy, system migrations, or, in many jurisdictions, changing regulatory requirements. Maintaining backward compatibility and preserving previously captured metadata is generally important to sustain the ongoing authenticity, integrity, and usability of records. The specific governance approach depends on organizational policy and the systems involved.

Common misconceptions

A metadata schema is the same as the metadata itself.

A metadata schema is the defined structure and set of rules that specify what metadata should be captured and how, whereas the metadata is the actual descriptive values recorded for a given record. The schema is the template; the metadata is the content that populates it.

Adopting a metadata schema is purely a technical or systems configuration task.

While schemas are often implemented within systems, defining and governing a schema is also a recordkeeping and policy matter. It typically requires decisions about which elements are needed to establish authenticity, reliability, integrity, and usability, and about how the schema is maintained over time.

A single universal metadata schema will meet every organization's needs.

Requirements often vary by organization, sector, and jurisdiction. Schemas are frequently tailored or extended to reflect local recordkeeping policy and applicable obligations, so what is adequate in one context may be insufficient or excessive in another.

Best practices

Define each element's meaning, intended use, and obligation status explicitly, so that values are captured and interpreted consistently across systems and over time.

Align the schema with your organization's recordkeeping policy and, where relevant, with recognized standards, tailoring or extending elements to suit your specific context rather than assuming a single schema fits all needs.

Prioritize the elements needed to support the qualities that make something a record, such as authenticity, reliability, integrity, and usability, rather than capturing metadata for its own sake.

Use controlled vocabularies or value constraints where consistency and interoperability matter, and document these constraints as part of the schema.

Establish governance for maintaining and versioning the schema, so that changes are controlled and existing metadata remains interpretable as the schema evolves.

Test the schema against representative records before wider adoption to confirm that mandatory elements are practical to complete and that the structure captures the necessary context.