Category: Metadata Standards

Metadata Element Set

Also known as: Metadata Schema, Metadata Element Set (generic)

Simply put

A metadata element set is a defined collection of standard properties used to describe resources such as records, documents, or web content, so that they can be identified, found, and understood consistently. Each element captures a particular attribute of a resource, for example its title, creator, or date. The best-known example is the Dublin Core Metadata Element Set, a widely used set of fifteen core elements for resource description.

Formal definition

A metadata element set is a formally specified group of named elements (properties), each intended to represent a defined attribute of a described resource, that together provide a structured vocabulary for resource description. The Dublin Core Metadata Element Set (DCMES) is a prominent example, comprising fifteen core elements developed for describing resources in a cross-disciplinary information environment and applied to electronic records, documents, and web resources; it is often characterized as a foundational descriptive standard on which many information services base their schemas. In recordkeeping contexts, a metadata element set typically supports description and discovery, and it should be understood as distinct from records metadata schemes designed specifically to capture and maintain evidential attributes such as authenticity, integrity, provenance, and management history across the record lifecycle. The specific elements, their semantics, and any mandatory or optional status depend on the particular standard adopted and on organizational implementation choices; where a set is described here as descriptive, that scope does not necessarily extend to structural, administrative, or preservation metadata unless the implementing standard provides for them.

Why it matters

A metadata element set provides the shared vocabulary that makes consistent description possible across an organization or a wider information community. Without an agreed set of elements, the same attribute of a record might be captured in incompatible ways, or omitted entirely, which undermines the ability to identify, locate, and understand resources later. By standardizing which properties are recorded and what each one means, a metadata element set supports discovery and interoperability, allowing records and other resources to be exchanged, aggregated, and interpreted consistently between systems and, in many cases, between institutions.

For recordkeeping professionals, however, the significance of a metadata element set depends heavily on its intended scope. A descriptive set such as the Dublin Core Metadata Element Set is well suited to identification and discovery of resources, but it should not be assumed to capture the evidential attributes that records management requires. Attributes such as authenticity, integrity, provenance, and management history across the record lifecycle are typically the concern of records metadata schemes designed for that purpose. Treating a general descriptive element set as if it were a complete recordkeeping metadata solution risks leaving gaps in the evidence needed to demonstrate that a record is what it claims to be and has been reliably maintained.

Understanding these boundaries matters because the specific elements, their meanings, and whether they are mandatory or optional vary by standard and by organizational implementation. Adopting an element set is therefore a scoping decision as much as a technical one: professionals need to be clear about what description the set provides, what it does not cover, and how it fits alongside other metadata that supports management, structure, and long-term preservation.

Who it's relevant to

Records managers

Records managers use metadata element sets to support consistent description and discovery of records, but they need to distinguish a general descriptive set from a records metadata scheme built to capture evidential attributes such as authenticity, integrity, provenance, and management history. Where a descriptive set is adopted, they should assess what it does not cover and how additional metadata will support the record across its lifecycle.

Metadata and cataloguing specialists

Those responsible for designing and maintaining descriptive schemas often base their work on foundational standards such as the Dublin Core Metadata Element Set. They make decisions about which elements to apply, their semantics, and whether they are mandatory or optional, tailoring the set to local needs while preserving interoperability with wider information services.

Information governance and interoperability leads

Professionals concerned with how information is exchanged and understood across systems and organizations rely on standardized element sets to enable consistent interpretation and aggregation of resources. They need clarity on the scope of any set adopted, so that descriptive metadata is not mistaken for the structural, administrative, or preservation metadata required for other governance purposes.

Archivists and digital preservation staff

Archivists working with electronic records, documents, and web resources may encounter descriptive element sets used for identification and discovery. Because such sets do not necessarily extend to preservation metadata unless the standard provides for it, preservation staff must consider what additional metadata is needed to maintain resources reliably over the long term.

Inside Metadata Element Set

Identity metadata

Elements that identify a record uniquely, such as a title, identifier, or reference code, enabling it to be distinguished from other records and reliably retrieved within a system.

Descriptive metadata

Elements describing the content, subject, and context of a record, supporting search, discovery, and understanding of what the record documents.

Provenance and agent metadata

Elements capturing who created, received, or acted upon a record, and the organizational or business context of its creation, which supports authenticity and accountability.

Business context metadata

Elements linking a record to the activity, function, or process it evidences, typically expressed through classification schemes and supporting the record's role as evidence of activity.

Management and use metadata

Elements governing control over the record across its lifecycle, which may include classification, access and security controls, retention and disposition information, and rights.

Event history metadata

Elements documenting actions taken on a record over time, such as capture, access, migration, or disposition events, which help demonstrate integrity and maintain an auditable trail.

Relationship metadata

Elements expressing links between a record and other records, agents, activities, or systems, supporting context and the ability to interpret a record within the aggregation to which it belongs.

Structural and technical metadata

Elements describing format, encoding, and technical dependencies that affect a record's usability and renderability, which can be important for long-term accessibility depending on organizational policy.

Common questions

Answers to the questions practitioners most commonly ask about Metadata Element Set.

Is a metadata element set the same thing as a database schema or a technical field list?

Not quite. While a metadata element set may be implemented through database fields or a technical schema, the two are not identical. A metadata element set is a defined collection of metadata elements chosen to describe records and support their management, retrieval, and evidential value over time. It is a conceptual and often standards-informed specification of what should be captured about a record, whereas a schema is one possible technical realization of that specification. The same element set may be implemented across different systems using different schemas, so conflating the two can obscure the recordkeeping purpose the element set is meant to serve.

Does adopting a metadata element set mean capturing every possible element for every record?

No. A metadata element set typically distinguishes between elements that are mandatory, conditional, or optional, and the appropriate level of capture usually depends on the record type, business context, and organizational policy. Applying an element set is a matter of selecting and configuring the elements that are proportionate to the risk, value, and management needs of the records in question. Attempting to populate every element for every record is often neither necessary nor sustainable, and may divert effort from the elements that genuinely support authenticity, retrievability, and disposition.

How should an organization decide which metadata elements to make mandatory?

The choice typically depends on what each element is intended to support, such as identifying the record, establishing its context, controlling access, or governing retention and disposition. Many organizations start from a recognized standard or reference element set and then map elements to their own business, legal, and regulatory requirements, which vary by jurisdiction and sector. Elements that underpin the evidential qualities of records, such as those supporting authenticity, integrity, and usability, are often treated as candidates for mandatory capture, while others may remain conditional or optional depending on record type and organizational policy.

Where in the record lifecycle should metadata elements be captured?

Capture is often distributed across the lifecycle rather than concentrated at a single point. Some elements are typically captured at creation or capture, such as those identifying the record and its originating context, while others accumulate as the record is classified, used, transferred, or moves toward disposition. Designing an element set usually involves considering not only what to capture but when it can reliably be captured, since some contextual information is difficult to reconstruct later. The aim is generally to ensure that the metadata needed to manage and interpret a record persists with it throughout its existence.

How can a metadata element set be maintained consistently across multiple systems?

Consistency across systems often relies on documenting the element set clearly, defining each element's meaning and permitted values, and mapping how it is implemented in each system. Where records move between systems or are transferred to another custodian, crosswalks or mappings between different element sets can help preserve meaning. Governance arrangements, controlled vocabularies, and change-control processes may support ongoing consistency, though the degree of alignment achievable in practice depends on the systems involved and organizational resources. Interoperability is generally easier where systems reference common or standards-informed element sets.

How does a metadata element set relate to retention and disposition?

Certain metadata elements typically support retention and disposition decisions, for example by recording classification, applicable retention rules, disposition status, and any holds that may suspend disposition. Capturing these elements reliably can help ensure that disposition actions, which may include transfer, permanent preservation, or destruction, are carried out in accordance with policy and applicable requirements. It is worth noting that disposition metadata may itself need to be retained as evidence that an action occurred, so an element set often accounts for documenting the disposition process, not only triggering it. Specific retention obligations depend on jurisdiction, sector, and organizational policy.

Common misconceptions

A metadata element set is simply a fixed list of fields that any organization can adopt unchanged.

A metadata element set is typically a framework of defined elements that organizations tailor to their functions, systems, and jurisdictional requirements. Which elements are mandatory, optional, or repeatable often depends on organizational policy and the applicable regulatory environment, rather than being universally fixed.

Recordkeeping metadata and general descriptive or library-style metadata are the same thing.

While there is overlap, recordkeeping metadata places particular emphasis on capturing context, agents, business activity, and event history so that a record can function as authentic and reliable evidence over time. This evidential and lifecycle focus distinguishes it from metadata used primarily for resource discovery or content description alone.

Metadata is captured once at creation and then remains static.

Metadata associated with a record often accumulates across its lifecycle. Event history, management, and relationship metadata may be added or updated as actions such as classification, access, transfer, or disposition occur, supporting ongoing integrity and usability rather than describing only a single point in time.

Best practices

Define which metadata elements are mandatory, optional, and repeatable for your organization, and align these choices with your business functions, systems, and applicable jurisdictional and sector requirements rather than adopting a generic set unchanged.

Capture context, agent, and business activity metadata at or near the point of record creation or capture, so that the properties supporting authenticity and reliability are established early rather than reconstructed later.

Maintain event history metadata to record actions taken on records over time, such as capture, access, migration, and disposition, to support demonstrable integrity and an auditable trail.

Include management metadata covering classification, access and security controls, and retention and disposition information, so that lifecycle controls are consistently applied and distinguishable from the record's content.

Document relationships between records, agents, and activities so that individual records remain interpretable within their wider aggregation and business context.

Review and govern the metadata element set periodically, updating it as functions, systems, and regulatory obligations change, and document the rationale for any element that is added, retired, or made conditional.