Category: Metadata Standards

Encoded Archival Description

Also known as:

Simply put

Encoded Archival Description (EAD) is a non-proprietary standard for encoding archival finding aids so they can be shared and used in online, networked environments. A finding aid describes the contents and structure of an archival collection, and EAD provides a consistent, machine-readable way to represent that description. It is based on XML, a common format for structuring documents so that computers can process and exchange them.

Formal definition

Encoded Archival Description (EAD) is an XML-based, non-proprietary standard for encoding descriptive information contained in archival finding aids, intended for use in networked (online) environments. It provides a structured markup vocabulary for representing the content, hierarchy, and context of archival descriptions, supporting exchange and interoperability across repositories and aggregation platforms such as archival portals. According to the evidence, EAD originated from work initiated at the Society of American Archivists in 1993, is maintained by the Technical Subcommittee on Encoded Archival Standards, and the standard is hosted by the Library of Congress. EAD addresses the encoding of archival description and finding aids specifically; it should be distinguished from records management lifecycle controls and from broader information governance frameworks, and from related but separate archival encoding standards, the details of which are outside the scope of this evidence.

Why it matters

Archival finding aids are the primary means by which researchers and staff discover what a collection contains and how it is arranged. Historically these finding aids were produced in inconsistent, repository-specific formats, which limited the ability to search across institutions or aggregate descriptions in shared platforms. As a non-proprietary, XML-based standard, EAD provides a consistent and machine-readable way to encode this descriptive information, which supports exchange and interoperability across repositories and aggregation platforms such as archival portals.

Because EAD is XML-based and non-proprietary, descriptions encoded to the standard are not locked into a single vendor's software and can be processed, transformed, and republished across systems over time. This matters for long-term access, since finding aids often need to remain usable well beyond the lifespan of any particular tool used to create them. Aggregation initiatives, such as the Archives Portal Europe referenced in the evidence, rely on shared standards of this kind to bring descriptions from many contributors together in a single discovery environment.

It is worth being clear about scope. EAD addresses the encoding of archival description and finding aids; it is not a records management lifecycle control and does not, on its own, govern retention, disposition, privacy, or the broader accountability concerns of an information governance framework. Professionals should treat it as a descriptive and interoperability standard rather than a substitute for those distinct disciplines, and should note that related but separate archival encoding standards exist whose details fall outside this evidence.

Who it's relevant to

Archivists and archival description staff

Those who create and maintain finding aids are the primary audience for EAD, since the standard provides a consistent way to encode the contents, structure, and context of archival collections. Using EAD helps ensure their descriptions can be shared and reused beyond a single local system.

Repositories and cultural heritage institutions

Libraries, archives, and other repositories that contribute descriptions to shared discovery services benefit from EAD's role in supporting exchange and interoperability. As a non-proprietary standard, it reduces dependence on any single vendor's format for the finding aids they hold.

Operators of aggregation and archival portals

Platforms that bring together descriptions from many contributors, such as the Archives Portal Europe noted in the evidence, rely on shared encoding standards like EAD to ingest and present finding aids from multiple repositories in a common discovery environment.

Records and information professionals who interface with archival programs

Records managers and information governance staff whose work connects with archival transfer and preservation may encounter EAD as the descriptive standard applied to material held in an archive. They should recognize that EAD concerns archival description rather than lifecycle controls or governance frameworks, and treat it accordingly when scoping responsibilities across the two disciplines.

Inside EAD

XML-based structure

EAD is an XML standard, meaning its finding aids are expressed through structured, machine-readable markup rather than free-form text. This structure supports consistent encoding and, in principle, easier exchange and reuse of descriptive information across systems, though the degree of interoperability achieved depends on how consistently the schema is applied.

Finding aid orientation

EAD is designed to encode archival finding aids, which are descriptive tools that help users locate and understand records held in an archival collection. It typically supports description at multiple levels, from the collection as a whole down to component parts such as series, files, or items, reflecting the hierarchical arrangement common in archival practice.

Descriptive and contextual elements

The standard provides elements for capturing information about a collection's content, arrangement, provenance, and administrative or biographical context. This contextual description helps establish the meaning and evidential value of the records being described, distinguishing archival description from a simple inventory or catalog listing.

Hierarchical component nesting

EAD accommodates the nested, multilevel structure characteristic of archival collections, allowing description to move from general to specific. This mirrors the principle of describing aggregations of records in context rather than treating each item in isolation.

Common questions

Answers to the questions practitioners most commonly ask about EAD.

Is Encoded Archival Description a cataloguing standard for individual records like those used in library systems?

Not in the same way. EAD is a standard for encoding archival finding aids, which describe collections or fonds hierarchically and in their context, rather than cataloguing discrete items independently. While item-level description can appear within an EAD instance, the standard is oriented toward representing aggregations of archival materials and their arrangement, so it differs in purpose and structure from item-focused library cataloguing formats. The two serve overlapping discovery goals but reflect different descriptive traditions.

Does adopting EAD dictate how an archive must arrange or appraise its holdings?

No. EAD is an encoding standard for expressing finding aids in a structured, machine-processable form; it is not itself a set of arrangement, appraisal, or description rules. Decisions about how materials are arranged and described typically follow separate archival descriptive standards and institutional practice. EAD provides a way to represent the resulting description, so it should be understood as a carrier for finding aid content rather than as guidance on how that content is determined.

How does EAD relate to the descriptive standards an archive already follows?

EAD is generally used to encode finding aids whose content is shaped by separate archival descriptive standards. In practice, institutions often map the elements of their descriptive framework onto EAD's structure so that established descriptive practice can be expressed in a shareable, structured format. The specific mapping depends on the descriptive standard and institutional policy, and it is worth confirming how local practice aligns with the encoding elements before implementation.

What is typically involved in converting existing finding aids into EAD?

Conversion often involves analyzing the structure of existing finding aids, identifying the hierarchical and contextual elements they contain, and mapping those elements to the corresponding EAD encoding. Depending on the source material, this can require varying degrees of manual review, cleanup, and quality control, particularly where legacy finding aids were created inconsistently. The effort involved depends heavily on the condition and consistency of the original descriptions and on organizational resources and priorities.

How can EAD support the sharing and aggregation of archival descriptions across institutions?

Because EAD provides a common structured encoding for finding aids, it can facilitate exchange and aggregation of descriptions among repositories and within union catalogues or portals that accept the format. The degree of interoperability achieved in practice often depends on consistent application of the encoding and on agreed conventions among participating institutions, so successful aggregation typically relies on shared guidelines as well as the standard itself.

What practical considerations affect long-term maintenance of EAD finding aids?

Maintaining EAD finding aids over time generally involves keeping the encoded instances valid against the standard, managing updates as descriptions are revised, and considering how the encoding is stored, versioned, and rendered for users. Institutions often need to plan for changes in tools, systems, and versions of the standard. The specific approach depends on organizational infrastructure, staffing, and policy, and should be considered alongside broader digital preservation and access planning.

Common misconceptions

EAD is a records management or retention standard that governs how records are kept or disposed of.

EAD is a descriptive standard for encoding archival finding aids, not a framework for retention, disposition, or lifecycle control. It concerns how existing archival holdings are described and made discoverable, and it should not be confused with records management standards that address the control of records as evidence across their lifecycle.

EAD is the same thing as a catalog record or a general metadata schema for individual documents.

EAD is oriented toward archival finding aids that typically describe collections and their components in a hierarchical, context-rich way, rather than cataloging discrete items in isolation. Its emphasis on provenance and arrangement distinguishes it from item-level bibliographic or document description approaches.

Adopting EAD automatically guarantees interoperability and seamless data exchange between institutions.

While EAD's XML structure is intended to support exchange and reuse, the practical level of interoperability achieved depends heavily on consistent application of the schema, shared encoding conventions, and local implementation choices. Divergent practices can limit how readily finding aids are exchanged in practice.

Best practices

Apply the EAD schema consistently across finding aids so that structural and descriptive elements are encoded in a predictable way, which supports discoverability and, where relevant, exchange between systems.

Use EAD's multilevel structure to describe collections in context, moving from the collection level down to component parts, rather than treating archival materials as isolated items.

Capture provenance and contextual information alongside content description, since this context is central to establishing the meaning and evidential value of archival holdings.

Keep EAD's descriptive purpose distinct from records management functions such as retention and disposition, and coordinate with related recordkeeping systems where lifecycle control is handled elsewhere.

Document and follow local encoding conventions so that consistency is maintained over time and across contributors, recognizing that interoperability depends on shared practice as much as on the standard itself.

Review encoded finding aids for accuracy and completeness of hierarchical relationships and contextual elements, since errors in structure can undermine both usability and reliable discovery.