Components may be subdivided into smaller and smaller components and may eventually reach the level of a single item. For example, the components of a collection may be series, components of series may be subseries, components of subseries may be files, and components of files may be items. A component may be either an unnumbered <c> or a numbered <c01>, <c02>, etc. The numbered components <c01> to <c12> assist a finding aid encoder in nesting up to twelve component levels accurately, although five or fewer levels often suffice.
Use the LEVEL attribute to identify the descriptive character of the component, for example, "series," "subseries," "subgrp," "file," or "item." Assigning a LEVEL attribute for the highest <c> is recommended; thereafter the attribute may be used when the repository deems it useful, but usually not beyond the "subseries" level.
The LANGMATERIAL attribute can be used to indicate the language of the archival materials being described if it is different from the principal language setting identified in the <archdesc> LANGMATERIAL attribute. This attribute is comparable to ISAD(G) data element 3.4.4 and MARC field 546.
ALTRENDER | #IMPLIED, CDATA |
AUDIENCE | #IMPLIED, external, internal |
ENCODINGANALOG | #IMPLIED, CDATA |
ID | #IMPLIED, ID |
LANGMATERIAL | #IMPLIED, CDATA |
LEGALSTATUS | #IMPLIED, public, private, otherlegalstatus |
LEVEL | #IMPLIED, series, collection, file, fonds, item, otherlevel, recordgrp, subgrp, subseries |
OTHERLEGALSTATUS | #IMPLIED, CDATA |
OTHERLEVEL | #IMPLIED, CDATA |
<dsc type="in-depth"> <c level="series"> <did><unittitle>Series 1: Correspondence</unittitle>[...]</did> [other possible elements and text... ] <c level="subseries"> <did><unittitle>Subseries 1.1: Outgoing Correspondence</unittitle> [...]</did> [other possible elements and text... ] <c level="file"> <did><unittitle>Abbinger-Aldrich</unittitle>[...]</did> </c> [other possible elements and text... ] </c> <c level="subseries"> <did><unittitle>Subseries 1.2: Incoming Correspondence</unittitle> [...]</did> [other possible elements and text... ] <c level="file"> <did><unittitle>Adams-Ayers</unittitle>[...]</did> </c> [other possible elements and text... ] </c> [other possible elements and text... ] </c> [other possible elements and text... ] </dsc>
<dsc type="combined"> [other possible elements and text... ] <c level="series"> <did><unittitle>Topical Files</unittitle> [...]</did> <scopecontent>[...]</scopecontent> <c><did><unittitle>California Dining Club.</unittitle></did> <c><did><unittitle>Annual financial statements, <unitdate type="inclusive">1923-1929</unitdate></unittitle></did></c> <c><did><unittitle>Membership rosters, <unitdate type="inclusive">1918-1932</unitdate></unittitle></did></c> <c><did><unittitle>Minutes, <unitdate type="inclusive">1925-1930</unitdate></unittitle></did></c> <c><did><unittitle>Newsletters, <unitdate type="inclusive">1919-1932</unitdate></unittitle></did></c> </c> [other possible elements and text... ] </c> [other possible elements and text... ] </dsc>
Table of Contents | ||||||||
Home Page |
Acknowledgments | Introduction | EAD Design Principles |
Overview of EAD Structure |
Tag Library Conventions |
EAD Attributes | EAD Elements by Tag Name |
Index of EAD Element Names |
Go to:
The Library of Congress