Why Classifying Metadata Types Matters
Not all metadata serves the same purpose. A date stamp on a document tells a records manager when to archive it — but it tells a search engine very little about what the document contains. Understanding the distinct roles that different metadata types play helps organizations design smarter metadata schemas, avoid redundancy, and ensure every important function is covered.
The most widely used classification framework divides metadata into three primary categories: descriptive, structural, and administrative. Each has a different job, a different audience, and different implications for how it should be created and maintained.
Descriptive Metadata: Making Content Findable
Descriptive metadata characterizes the intellectual content of a resource. Its primary purpose is discovery — helping people and systems locate a resource based on what it is about.
Common Descriptive Metadata Fields
- Title: The name of the resource
- Author/Creator: Who made it
- Description/Abstract: A summary of the content
- Subject/Keywords: Topics covered
- Language: The language(s) used
- Date created/published: When it was made available
Who Uses Descriptive Metadata?
End users rely on descriptive metadata every time they run a search. Search engines index it to determine relevance. Librarians use it to build catalogues. Content management systems use it to power filtering, faceted navigation, and recommendations. It is the metadata closest to human reading.
Structural Metadata: Defining Relationships and Order
Structural metadata describes how the components of a complex object relate to one another. Where descriptive metadata answers "what is this?", structural metadata answers "how is this put together?"
Examples of Structural Metadata in Practice
- A digitized book's structural metadata records page order, chapter boundaries, and the relationship between images and their captions.
- A video's structural metadata defines chapters, scene boundaries, and subtitle track associations.
- A database schema describes how tables relate to each other through foreign keys and join conditions.
- An XML document's schema defines which elements are required, which are optional, and how they nest.
Structural Metadata and Interoperability
Structural metadata is critical for systems that need to reassemble or render complex objects correctly. A digital archive might store a manuscript as thousands of individual image files; without structural metadata specifying the correct sequence and groupings, those images cannot be meaningfully presented as a coherent document.
Administrative Metadata: Managing Resources Over Time
Administrative metadata supports the management, maintenance, and governance of resources throughout their lifecycle. It is primarily used by systems and administrators rather than end users — and it encompasses several sub-categories.
Technical Metadata
Technical metadata documents the properties needed to decode, render, or use a file:
- File format and version (e.g., PDF/A-2b)
- Resolution, color space, and compression for images
- Encoding, bit rate, and codec for audio/video
- Software required for access
Rights Metadata
Rights metadata records the intellectual property status of a resource and governs its reuse:
- Copyright holder and expiration date
- Licensing terms (e.g., Creative Commons license type)
- Access restrictions and embargo periods
Preservation Metadata
For archives and long-term repositories, preservation metadata tracks the provenance and integrity of files over time:
- Checksums to verify file integrity
- Migration history (format conversions)
- Custody and chain of ownership
Comparing the Three Types
| Type | Primary Question | Primary Audience | Example Field |
|---|---|---|---|
| Descriptive | What is this about? | End users, search engines | Keywords, description |
| Structural | How is this organized? | Systems, renderers | Page sequence, schema |
| Administrative | How do we manage this? | Administrators, systems | File format, rights, checksum |
Designing a Balanced Metadata Schema
When building a metadata schema for any digital repository, content management system, or data platform, all three types should be deliberately addressed. Teams often focus heavily on descriptive metadata — the most visible and user-facing type — while neglecting structural and administrative elements that are just as critical for long-term manageability.
A practical exercise: for each resource type your system handles, map out one or two fields from each category. If you struggle to name an administrative metadata field, that is a signal your governance and lifecycle management processes may be underdeveloped. If you cannot name a structural field, consider whether your system handles compound objects and whether those relationships are currently tracked anywhere at all.