What Is Encoded Archival Description (EAD)?

Encoded Archival Description (EAD) is an XML-based metadata standard designed specifically to structure, deliver, and exchange archival finding aids in a standardized, machine-readable format. This article explains the fundamentals of EAD, its hierarchical architecture, why archivists use it to describe physical and digital collections, and the key benefits it provides for digital preservation and online research discovery.

Understanding Encoded Archival Description

EAD is an open standard maintained by the Technical Subcommittee for Encoded Archival Standards (TS-EAS) of the Society of American Archivists (SAA) in partnership with the Library of Congress. It provides a standardized data structure for archival finding aids—detailed inventories and contextual guides that describe the contents, provenance, and structure of archival collections.

Unlike standard library cataloging standards such as MARC, which are optimized for single items like books, EAD is designed to represent complex, multilevel archival hierarchies.

The Hierarchical Structure of EAD

Archival collections are organized hierarchically, moving from broad context down to individual items. EAD captures this structure through designated XML tags, typically divided into two main components:

1. The Header (<control> in EAD3 / <eadheader> in EAD 2002)

This section contains administrative metadata about the finding aid itself. It includes information such as: * The title and unique identifier of the finding aid * The repository responsible for its creation * Creation, revision, and publication dates * Language and encoding rules used

2. The Archival Description (<archdesc>)

This is the core of the finding aid, containing the actual descriptive metadata for the collection. It operates from the top level down: * Collection-Level Information: High-level details such as the collection creator, biographical/historical notes, scope and content notes, access restrictions, and administrative history. * Description of Subordinate Components (<dsc>): The inventory section that maps the collection’s internal organization. It allows archivists to nest descriptions into series, sub-series, boxes, folders, and individual items (often designated as c01, c02, etc., or general <c> levels).

Why Archivists Use EAD

• Standardization: EAD aligns closely with international descriptive guidelines, such as the General International Standard Archival Description (ISAD(G)) and Describing Archives: A Content Standard (DACS).
• Interoperability and Data Exchange: Because EAD files are formatted in XML, repositories can easily share, syndicate, and aggregate collection descriptions across regional, national, and international union catalogs (such as ArchiveGrid).
• Deep Searchability: EAD enables full-text and field-specific searching within complex inventories, allowing researchers to pinpoint specific folders or documents within massive archival collections.
• Platform Independence: XML is human-readable, machine-readable, and software-independent. This ensures long-term preservation of descriptive data without reliance on proprietary database formats.
• Flexible Presentation: Since the underlying XML separates data from presentation, repositories can use XSLT stylesheets or web frameworks to render the same EAD document into HTML web pages, downloadable PDFs, or interactive online tools.

Evolution: From EAD 2002 to EAD3

The standard was originally developed at the University of California, Berkeley, in the 1990s. While EAD 2002 was the widely adopted baseline for over a decade, EAD3 was released in 2015 to modernize the standard. EAD3 introduced improved support for linked open data, standardized relations between creators and resources, and tightened semantic rules to enhance consistency across digital repositories.