Category: Metadata Standards

Structural Metadata

Simply put

Structural metadata is information that describes how the parts of a resource or dataset fit together, such as how chapters relate to a book or how tables relate within a database. Rather than telling you what a resource is about, it tells you how it is organized and how its components connect. This helps systems and people navigate, assemble, and make sense of complex digital materials.

Formal definition

Structural metadata is a category of metadata that describes the organization, types, versions, relationships, and formatting of the components that make up a digital resource or dataset. It typically documents how discrete parts relate to one another, for example, the sequence of pages or chapters within a document, or the relationships among tables and fields within a database, and is often used to support machine processing, navigation, discovery, and integration across systems. It is distinct from descriptive metadata, which characterizes the subject or content of a resource, and from administrative metadata; the boundaries between these categories can vary depending on the metadata schema and organizational practice in use.

Why it matters

Structural metadata is what allows complex digital resources to remain usable and coherent over time, rather than dissolving into disconnected fragments. A digitized report, a multi-part case file, or a relational database has meaning that depends not only on its individual components but on how those components relate, the sequence of pages, the version relationships among drafts, or the links among tables and fields. Without structural metadata, a system may retain all the underlying content yet lose the ability to reassemble it into a navigable, intelligible whole. For records professionals, this bears directly on the usability of records, one of the properties that distinguishes an authoritative record from mere retained information.

The practical stakes are most visible in preservation and migration contexts. When digital materials are moved between systems or carried forward across format changes, structural metadata is often what enables the relationships among parts to survive the transition. If it is not captured or is lost, otherwise complete content can become difficult to render, order, or interpret, which can undermine the integrity and long-term usability of records held for evidential or business purposes. This risk tends to grow with the complexity of the resource and the number of system boundaries the material crosses.

Structural metadata also supports discovery, machine processing, and integration across systems, which matters as organizations increasingly rely on automated handling of large or heterogeneous collections. That said, its value depends heavily on the metadata schema in use and on consistent organizational practice; the way structural metadata is defined and where its boundaries sit relative to descriptive and administrative metadata can vary, so its benefits are realized only when capture and maintenance are treated deliberately rather than assumed.

Who it's relevant to

Digital preservation specialists and archivists

Those responsible for long-term preservation rely on structural metadata to keep the relationships among the parts of a resource intact across format migrations and system transfers. Because usability is one of the properties that distinguishes an authoritative record, capturing structural metadata is often essential to ensuring that complex materials remain navigable and interpretable rather than reduced to disconnected content.

Records managers

Records managers concerned with the integrity and usability of records benefit from understanding how structural metadata supports the ability to reassemble and interpret multi-part records over time. Its practical value depends on the schema in use and on consistent organizational practice, so it is typically a matter to address through policy rather than to assume by default.

Data management and integration practitioners

For those working with databases and cross-system data flows, structural metadata describes how data is organized, interconnected, and formatted, such as the relationships among tables and fields in a relational database. This supports discovery, integration, and the machine processing on which automated handling of data typically depends.

Metadata and information architecture practitioners

Those designing metadata schemas need to be deliberate about where structural metadata sits relative to descriptive and administrative categories, since the boundaries between them can vary by schema and practice. Clear definitions help ensure that relationships among components are captured consistently and can be relied upon across systems.

Inside Structural Metadata

Component Relationships

Information describing how the constituent parts of a record or information object relate to one another, such as the association between individual pages, files, or sections that together form a coherent whole.

Sequence and Ordering

Data that establishes the intended order of components, for example the pagination of a multi-page document or the arrangement of items within a compound object, so the record can be reassembled and rendered as originally constituted.

Aggregation and Hierarchy

Representation of how lower-level items combine into higher-level aggregates, such as documents grouped into files and files into series, reflecting the hierarchical arrangement often used in recordkeeping systems.

Internal Linkages and Dependencies

References that bind together elements which depend on one another for meaning or rendering, for instance a text file and its associated images or a container file and its embedded components.

Rendering and Presentation Structure

Information that supports the correct display or reconstruction of a record, helping preserve its usability by indicating how parts should be assembled and presented to a user.

Common questions

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

Is structural metadata the same as descriptive metadata?

No. Descriptive metadata supports discovery and identification of a record, such as its title, author, or subject, whereas structural metadata describes how the components of a record or set of records relate to one another and how they fit together, for example the sequence of pages in a document or the relationship between a message and its attachments. The two categories serve different purposes and are typically managed as distinct metadata types, though both may be captured for the same record.

Does structural metadata simply mean file format information?

Not exactly. File format is a technical attribute often recorded within technical metadata, while structural metadata concerns the internal organization and interrelationships of a record's parts and the connections between related objects. Format details may be relevant to rendering or reconstructing a record, but structural metadata is broader in that it captures the arrangement and dependencies needed to keep a compound or complex record whole and usable over time.

How should structural metadata be captured for compound records such as emails with attachments?

Structural metadata for compound records typically documents the relationships between the constituent parts, so that an email and its attachments remain linked and can be reconstructed as a single coherent record. Capturing this often depends on the capabilities of the recordkeeping system and organizational policy; where feasible it is generally advisable to record these relationships at the point of capture rather than reconstructing them later.

What role does structural metadata play in maintaining record integrity and usability over time?

Structural metadata can support the integrity and usability of records by preserving the arrangement and dependencies among their parts, which helps ensure a record can be rendered, understood, and used as originally intended. Its effectiveness depends on consistent capture and on migration or preservation processes that carry the relationships forward; the specific requirements often vary with the record type and the systems involved.

How is structural metadata affected when records are migrated or transferred between systems?

During migration or transfer, structural metadata should be carried across so that the relationships between record components are not lost. Because different systems may represent structure differently, mapping and validation are often needed to confirm that compound and complex records remain intact. The approach typically depends on the source and target systems and on organizational preservation policy.

Who is typically responsible for defining structural metadata requirements in an organization?

Responsibility for defining structural metadata requirements is often shared, commonly involving records management, information governance, and technical or systems staff working together. Records and governance functions may set the requirements for what relationships must be preserved, while technical staff implement how they are captured and maintained. The precise allocation of roles depends on organizational structure and policy.

Common misconceptions

Structural metadata is the same as descriptive metadata.

The two serve different purposes. Descriptive metadata typically supports discovery and identification by describing what a record is about, whereas structural metadata describes how the parts of a record fit together. Both may coexist for a single record, but conflating them can lead to gaps in either discoverability or the ability to reconstruct the object.

Structural metadata only matters for complex digital objects and is irrelevant for simple records.

While structural metadata is often most visible in compound or multi-part digital objects, even relatively simple records may carry structural information, such as page order. Its significance depends on the nature of the record and organizational requirements rather than complexity alone.

Capturing content is sufficient to preserve a record, so structural metadata can be discarded.

Retaining content without the structural metadata that binds its components can undermine the usability and, in some cases, the integrity of a record, since the parts may no longer be reassembled as originally constituted. Structural metadata is often part of what makes a record usable over time.

Best practices

Capture structural metadata at or near the point of record creation or capture, so that relationships between components are documented while they are still known and verifiable.

Keep structural metadata distinct from, but linked to, descriptive and other metadata types, ensuring each supports its intended function without conflation.

Ensure structural metadata is retained and migrated alongside the record throughout its lifecycle, so that usability is preserved through storage, transfer, and any format migration.

Document the ordering, aggregation, and internal dependencies of compound or multi-part records so they can be reliably reassembled and rendered in future.

Align structural metadata practices with applicable recordkeeping standards and organizational policy, recognizing that specific requirements may vary by jurisdiction, sector, and system.

Validate that structural metadata remains accurate and functional after system changes or migrations, since broken linkages can compromise the integrity and usability of the record.