Category: Metadata Standards

Records Metadata

Also known as: Metadata for records, Recordkeeping metadata

Simply put

Records metadata is descriptive information about a record, such as who created it, when it was created, its file type, and how it may be accessed or circulated. It is often described as data about data, and it helps organizations find, retrieve, and understand both physical and electronic records. Depending on organizational practice, this information can also cover matters such as copyright status or security classification.

Formal definition

Records metadata is structured information that describes the context, content, and management of a record throughout its lifecycle, supporting the identification, retrieval, access control, and administration of records as evidence of activity. It typically includes attributes such as creator or author, creation date, and format, alongside use metadata describing how records may be accessed or circulated and information such as copyright status or security classification. Its design and application in specific technological environments are commonly informed by the ISO 23081 family of standards, which addresses metadata for records; the precise metadata elements captured and their obligation levels generally depend on organizational policy, system capability, and applicable jurisdictional and sector requirements. Records metadata is distinct from the record content itself, though when integrated with established records management practices it can improve the search, retrieval, and ongoing management of records across their lifecycle.

Why it matters

Records metadata is often what makes a record findable, intelligible, and usable over time. Without structured information describing who created a record, when it was created, its format, and how it may be accessed or circulated, an organization may hold documents it cannot reliably locate, interpret, or trust. Metadata is frequently what allows both physical and electronic records to be searched, retrieved, and understood, and when combined with established records management practices it can substantially improve how records are managed across their lifecycle.

Beyond retrieval, records metadata supports the properties that distinguish a record from mere information, including its context and evidential value. Attributes such as creator, creation date, security classification, and copyright status help establish and preserve the meaning of a record as evidence of an activity. Use metadata, which describes how records may be accessed or circulated, can also support access control and appropriate handling. The specific elements captured and whether they are mandatory or optional typically depend on organizational policy, system capability, and applicable jurisdictional and sector requirements.

Because metadata is distinct from the record content itself, gaps or inconsistencies in metadata can undermine the discoverability and defensibility of otherwise complete records. Where metadata is incomplete, poorly structured, or lost during system migrations, organizations may find that records become harder to retrieve or that their context is diminished. For this reason, deliberate design and consistent application of records metadata is generally treated as foundational to sound recordkeeping rather than an optional refinement.

Who it's relevant to

Records managers

Records managers rely on metadata to identify, classify, retrieve, and administer records across their lifecycle. Consistent and well-designed metadata is often central to ensuring that both physical and electronic records remain findable and manageable, and to integrating metadata with established records management practices.

Information governance officers

Those responsible for information governance may use records metadata as one input to broader accountability concerns spanning policy, access, and risk. Metadata describing security classification and how records may be accessed or circulated can support decisions about handling and control, though the specific requirements typically depend on organizational policy and applicable jurisdictional and sector obligations.

Systems and records system designers

Those designing or configuring records and information systems commonly draw on the ISO 23081 family of standards when developing technical specifications for metadata to be applied in specific technological environments. Their choices about which elements to capture and whether they are mandatory generally depend on system capability alongside organizational and jurisdictional requirements.

Archivists and preservation staff

Metadata describing the context, content, and management of a record supports its continued intelligibility and evidential value over time. Attributes such as creator, creation date, and format help those responsible for long-term management understand and preserve records as evidence of activity.

Compliance and access professionals

Staff managing access, copyright, or security concerns may depend on use metadata that describes how records can be accessed or circulated, as well as metadata identifying copyright status or security classification. What is required in any given context typically varies by jurisdiction and sector.

Inside Records Metadata

Identity metadata

Elements that uniquely identify a record and distinguish it from copies, drafts, and related items, such as a persistent identifier, title, and creator or author. These support the ability to locate and cite the authoritative record over time.

Contextual metadata

Information describing the business, administrative, or transactional context in which a record was created and used, including the originating activity, the agents involved, and relationships to other records. This context is typically what helps establish a record as evidence of activity rather than mere information.

Content and structural metadata

Elements describing the form, format, and internal structure of the record, along with dependencies on particular software, encoding, or rendering environments. Such metadata often supports the usability of a record over time, though its sufficiency depends on the format and preservation approach.

Management and lifecycle metadata

Data documenting how a record is controlled across its lifecycle, including classification, retention and disposition instructions, access and security markings, and the record's current disposition status. This may distinguish records subject to retention, transfer, or destruction.

Event history and provenance metadata

A record of actions taken on or affecting the record over time, such as capture, migration, access, and disposition events. This history often contributes to demonstrating authenticity, integrity, and a chain of custody, though what is captured depends on system capabilities and organizational policy.

Use and access metadata

Elements governing and documenting who may access a record and under what conditions, which can intersect with privacy, security, and freedom of information obligations. The applicable requirements vary by jurisdiction and sector.

Common questions

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

Is records metadata the same as the descriptive tags used in general document management?

Not quite. While both involve data about content, records metadata serves a more specific evidential purpose. In recordkeeping, metadata is intended to help establish and preserve the authenticity, reliability, integrity, and usability of a record over time, and to document the context and management of that record throughout its lifecycle. Descriptive tags in general document management often focus on findability and organization rather than on sustaining a record's evidential value. The two overlap where descriptive elements support retrieval, but records metadata typically extends further into contextual, structural, and management information that supports the record as evidence of activity.

Once a record is captured, is its metadata fixed and unchanging?

Not generally. Some metadata, particularly information that fixes the point of capture and supports authenticity and integrity, is typically intended to remain stable and protected against unauthorized alteration. However, records metadata often continues to accumulate over the lifecycle as management actions occur, such as classification, access decisions, retention assignment, and disposition. In this sense metadata can be understood as having both stable elements that anchor the record's identity and context, and additive elements that record subsequent events and actions. What matters is that changes are themselves controlled and, where appropriate, documented, rather than the whole metadata set being frozen.

What categories of metadata should we consider capturing for records?

Approaches vary by organization, sector, and the systems in use, so this depends on organizational policy and any applicable standards. In broad terms, records metadata is often discussed in terms of information that identifies the record, describes its content, captures its context (such as the activity, agent, and business process it relates to), documents its structure, and records management actions taken over its lifecycle, including access, retention, and disposition events. Rather than adopting a fixed list, many organizations align their metadata categories with recognized recordkeeping standards and with their own retrieval, accountability, and compliance requirements.

How much metadata is enough, and what are the risks of capturing too much or too little?

There is no universal answer, as the appropriate level typically depends on the record's value, associated risk, and relevant regulatory or business requirements. Capturing too little metadata may undermine the ability to establish authenticity, locate records, apply retention correctly, or demonstrate accountability. Capturing excessive metadata can increase cost, complexity, and maintenance burden, and may raise privacy or security considerations depending on what the metadata itself contains. Many organizations aim for a proportionate approach, capturing the metadata needed to support the record's evidential value and management obligations without accumulating information that is not used or defensible.

How can metadata support the disposition of records?

Metadata can play a supporting role in disposition by documenting information relevant to retention and to the actions taken at the end of a retention period. This may include information that helps associate records with a retention rule, that records when a disposition decision or action occurred, and that captures the outcome. It is worth emphasizing that disposition may involve transfer or permanent preservation as well as destruction, so metadata can also support the documentation of transfers and of continued preservation. The specific metadata used for these purposes typically depends on organizational policy and the recordkeeping system involved.

What happens to records metadata when records are migrated or transferred between systems?

Preserving metadata across migration or transfer is generally an important consideration, because the record's context and its ability to support authenticity, integrity, and usability can depend on that metadata remaining associated with the record. Challenges can arise where systems structure or interpret metadata differently, which may require mapping between schemas and verifying that information is not lost or corrupted in the process. Documenting migration and transfer actions is itself often treated as part of the record's management history. The precise handling depends on the systems, any applicable standards, and organizational policy, and it is prudent to confirm that evidential value is maintained rather than assuming metadata carries over intact.

Common misconceptions

Records metadata is essentially the same as the descriptive tags used in document management systems.

While there is overlap, records metadata is oriented toward supporting the evidential qualities of records, such as authenticity, reliability, integrity, and usability, and toward managing retention and disposition. It typically includes contextual, event history, and management elements that go beyond the descriptive metadata often emphasized for general document retrieval. The distinction depends in part on system design and organizational practice.

Once metadata is created it can be edited freely to correct or update the record.

Some metadata, particularly event history and provenance information, is generally intended to remain fixed so that it can support a record's integrity and authenticity. In many recordkeeping approaches such metadata is added to rather than overwritten, and permissible changes depend on organizational policy and the controls of the system.

Metadata is separate from the record and therefore less important to preserve.

In recordkeeping, metadata is often considered part of what makes something a record and evidence of activity, and losing it can undermine the record's usability and evidential value. The extent to which metadata must be retained alongside content typically depends on the record's context, format, and applicable requirements.

Best practices

Define which metadata elements are required to establish and maintain the evidential qualities of records, distinguishing identity, contextual, structural, management, and event history metadata rather than treating metadata as a single undifferentiated set.

Capture metadata as close to the point of record creation or capture as practical, since context is often most readily and reliably documented at that time.

Protect event history and provenance metadata from unauthorized alteration, favoring approaches that add to the record of actions rather than overwrite it, in line with organizational policy and system controls.

Ensure retention, disposition, access, and security metadata is present and kept current so that records can be managed through their lifecycle, including transfer or permanent preservation as well as destruction where appropriate.

Preserve metadata alongside record content through migrations and format changes, verifying that structural and contextual metadata needed for usability is carried forward.

Align access and use metadata with applicable privacy, security, and freedom of information obligations, recognizing that specific requirements vary by jurisdiction and sector.