EAD (Encoded Archival Description ; Version 2002 Official Site)

Encoded Archival Description Tag Library, Version 2002

EAD Elements

<unitdate> Date of the Unit

Description:

The creation year, month, or day of the described materials. The <unitdate> may be in the form of text or numbers, and may consist of a single date or range of dates. As an important subelement of the Descriptive Identification <did>, the <unitdate> is used to tag only the creation and other relevant dates of the materials described in the encoded finding aid. Do not confuse it with the <date> element, which is used to tag all other dates.

A standard numeric form of the date (YYYYMMDD, etc.) can be specified with the NORMAL attribute to facilitate machine comparison of dates for search purposes. The TYPE attribute may be used to indicate whether the <unitdate> represents inclusive dates or bulk (predominant) dates. The CERTAINTY attribute may be applied to indicate if the date has been supplied or estimated by the archivist. The DATECHAR attribute can be used to supply a term characterizing the nature of the dates, such as creation or accumulation. The CALENDAR attribute, which has a default value of "gregorian," specifies the calendar from which the date stems. The value "ce" (common or Christian era) is the default for the ERA attribute.

The <unitdate> may be nested within the <unittitle> or used independently of that element.

This element is comparable to ISAD(G) element 3.1.3, and MARC fields 245 subfield f for inclusive dates, 245 subfield g for bulk dates, or 260 subfield c.

May contain:

#PCDATA, abbr, archref, bibref, emph, expan, extptr, extref, lb, linkgrp, ptr, ref, title

May occur within:

archref, did, entry, event, extref, extrefloc, item, label, p, ref, refloc, unittitle

Attributes:

ALTRENDER #IMPLIED, CDATA
AUDIENCE #IMPLIED, external, internal
CALENDAR gregorian, NMTOKEN
CERTAINTY #IMPLIED, CDATA
DATECHAR #IMPLIED, CDATA
ENCODINGANALOG #IMPLIED, CDATA
ERA ce, NMTOKEN
ID #IMPLIED, ID
LABEL #IMPLIED, CDATA
NORMAL #IMPLIED, CDATA
TYPE #IMPLIED, bulk, inclusive

Examples:

    1.
        <archdesc level="collection">
            <did>
                <head>Collection Summary</head>
                <origination label="Creator"><corpname encodinganalog="110">National Association
                for the Advancement of Colored People</corpname>
                </origination>
                <unittitle label="Title" encodinganalog="245">Visual Materials from the National
                Association for the Advancement of Colored People Records (Library of Congress)</unittitle>
                <unitdate label="Dates" type="inclusive" encodinganalog="260">
                	ca. 1838-1969, </unitdate>
                <unitdate type="bulk">bulk 1944-1955</unitdate>
            </did>
        </archdesc>

    2.
        <dsc type="analyticover">
            <c level="subseries">
                <did>
                    <unittitle>Documentary Movies, </unittitle>
                    <unitdate type="inclusive" normal="1952/1964">1952-1964</unitdate>
                    <physdesc><extent>2.5 linear ft.</extent></physdesc>
                    <abstract>Includes scores, arranged alphabetically by movie title,
                    and some correspondence, arranged chronologically.</abstract>
                </did>
            </c> . . .
        </dsc>