Encoded Archival Description is a standard for encoding archival finding aids or guides to primary source materials.
EAD is based on the multi-level description of finding aids and collections used by archival repositories. This may include a general description of all materials, a description of series or groups, and a description of files or items. Encoding is based on, and seeks to reflect, the content and structure of the original document.
Below is an example of a finding aid for the Frank Cather Postcard Collection. Click Here to view this finding aid and more.

Basic tags of EAD
Key Encoding Concepts
1. EAD makes use of a tag structure that identifies the components of a document. The tag structure is based on a combination of elements and attributes.
2. ELEMENTS are contained within start and end tags generic to a piece of information
3. ATTRIBUTES modify or clarify information within elements and provide more specific information
4. EAD Required Tags: EAD was developed to allow a great deal of flexibility in the encoding of a document. There are only a few required tags:
- <EAD>
- <EADHEADER>
- <EADID>
- <FILEDESC>
- <TITLESTMT>
- <TITLEPROPER>
- <ARCHDESC> LEVEL attribute
- <DID>
- <DSC> TYPE attribute
What EAD does
EAD tags describe the characteristics of archival materials.
EAD makes use of a tag structure that identifies the components of a document. Each component or part is identified, and noted through the encoding. Because EAD is an application of XML, EAD utilizes the concepts of tags, elements, and attributes for encoding text.
How EAD works
EAD is based on the multi-level description of finding aids and collections used by archival repositories. Finding aids may include a general description of all materials, a description of series or groups, and a description of files or items. EAD encoding is based on, and seeks to reflect, the content and structures of archival finding aids.
Encoding using EAD
Basic Steps:
Mark Up or Encoding
First, mark up or encode a document using the tag structure outlined within the EAD Document Type Definition. A Tag Library and Application Guidelines are available for assistance with the mark up of documents. Software that allows encoding in XML can be used to create the encoded document. Such software includes Xmetal, Epic Editor and NoteTab Light. NoteTab light is available in a free version that works very well with EAD projects. Since it is free, NoteTab Light is the application used most often by the UNL Libraries.
Validate the Document and EAD markup
The markup must be valid for the information to display, and it must be "checked" against the set of rules outlined in the Document Definition Type (DTD). This process is called "parsing" or "validating".
Presentation
The presentation, or final display, of an encoded document requires the use of a style sheet or program that converts an EAD document into HTML, or into a text file, or a word-processing file, and so on. In this way, a single encoded document that can be displayed in many different ways, for different audiences.Special characters
Special characters may be represented by using a character entity file, which is a feature of text encoding that permits encoders to display special characters and symbols.Example:
À is represented with character entity À
^ is represented with character entity ^





