## <defitem>

<defitem> (Definition List Item) A formatting element in a special type of list that keeps an entry in a list (called a <label>) paired with its definition, description, or explanation (called an <item>). The <defitem> can be thought of as an entry with two cells: <label> followed by <item>. Lists with <defitem>s are often displayed in two columns.

<table><tr><td>Module</td><td>EAD</td></tr><tr><td>Attributes</td><td>att.EADGlobal (@id, @altrender, @audience, @encodinganalog)</td></tr><tr><td>Contained by</td><td>EAD: list</td></tr><tr><td>May contain</td><td>EAD: item label</td></tr><tr><td>Note</td><td>See also related element &lt;list&gt;.</td></tr><tr><td>Example</td><td>&lt;list xmlns="urn:ibn:1-931666-22-9" type="deflist"&gt;<br/>&lt;listhead&gt;<br/>&lt;head01&gt;Abbreviation&lt;/head01&gt;<br/>&lt;head02&gt;Expansion&lt;/head02&gt;<br/>&lt;/listhead&gt;<br/>&lt;defitem&gt;<br/>&lt;label&gt;ALS&lt;/label&gt;<br/>&lt;item&gt;Autograph Letter Signed&lt;/item&gt;<br/>&lt;/defitem&gt;<br/>&lt;defitem&gt;<br/>&lt;label&gt;TLS&lt;/label&gt;<br/>&lt;item&gt;Typewritten Letter Signed&lt;/item&gt;<br/>&lt;/defitem&gt;<br/>&lt;/list&gt;</td></tr><tr><td>Content model</td><td>&lt;content&gt;<br/>&lt;/content&gt;</td></tr></table>

<table><tr><td>Schema Declaration</td><td>element defitem { att.EADGlobal_attributes, label, item }</td></tr></table>

## <descgrp>

<descgrp> (Description Group) An element that can be used to bring together any group of elements that are children of the Archival Description <archdesc> element except for the <did> and <dsc> elements. Description Group might be used, for example, to cluster elements into groups that correspond to the areas specified by the General International Standard Archival Description (ISAD(G)).

<table><tr><td>Module</td><td>EAD</td></tr><tr><td>Attributes</td><td>att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.typed (@type)</td></tr><tr><td>Member of</td><td>model desc base</td></tr><tr><td>Contained by</td><td>EAD: archdesc archdescgrp c c01 c02 c03 c04 c05 c06 c07 c08 c09 c10 c11 c12 descgrp</td></tr><tr><td>May contain</td><td>EAD: accessrestrict accruals acqinfo address altformavail appraisal arrangement bibliography bioghist blockquote chronlist controlaccess custodhist descgrp fileplan head list note odd originalsloc otherfindaid p phystech prefercite processinfo relatedmaterial scopecontent separatedmaterial table userestrict</td></tr><tr><td>Note</td><td>Description Group can be used in place of wrapper elements from EAD Version 1.0 such as Administrative Information &lt;admininfo&gt; and Adjunct Descriptive Data &lt;add&gt;. Use the TYPE attribute to characterize the nature of the groupings.</td></tr></table>
## Example

```xml
<descgrp xmlns="urn:isl:1-931666-22-9">
  <head>Related and Associated Materials</head>
  <separatedmaterial>
    <p>Photographs and sound recordings have been transferred to the appropriate custodial divisions of the Library where they are identified as part of these papers. Among the sound recordings are the following broadcasts:</p>
  </separatedmaterial>
</descgrp>
```

```xml
<list>[...]</list>
</separatedmaterial>
```

```xml
<separatedmaterial>
  <p>Other papers of Earl Warren, which relate chiefly to his early years and public service in California, are held by the California State Archives in Sacramento.</p>
</separatedmaterial>
```

```xml
<relatedmaterial>
  <p>Records relating to the Warren Commission are held in the National Archives and Records Administration.</p>
</relatedmaterial>
```

```xml
</descgrp>
```

## Example

```xml
<descgrp xmlns="urn:isl:1-931666-22-9">
  <head>Important Information for Users of the Collection</head>
</descgrp>
```

```xml
<accessrestrict>
  <head>Access</head>
</accessrestrict>
```

```xml
<p>Collection is open for research. Scrapbooks are extremely fragile and require close supervision by Special Collections staff during use.</p>
</accessrestrict>
```

```xml
<userrestrict>
  <head>Publication Rights</head>
</userrestrict>
```

```xml
<p>Property rights reside with the University of California. Literary rights are retained by the creators of the records and their heirs. For permissions to reproduce or to publish, please contact the Head of Special Collections and Archives.</p>
</userrestrict>
```

```xml
<prefercite>
  <head>Preferred Citation</head>
  <p>Eugene Loring Papers. MS-P02. Special Collections and Archives, The UCI Libraries, Irvine, California.</p>
</prefercite>
```

```xml
<acqinfo>
  <head>Acquisition Information</head>
  <p>Gift of Eugene Loring, 1975 and 1980.</p>
</acqinfo>
```

```xml
<processinfo>
  <head>Processing History</head>
  <p>Preliminary processing by Roger Berry in 1975 and 1980. Processing completed by Emma Kheradyar in 1996-1997. Guide edited by Laura Clark Brown in 1998 and completed by William Landis in 2000.</p>
</processinfo>
```

```xml
</processinfo>
```

```xml
<acqinfo>
  <head>Acquisition Information</head>
  <p>Gift of Eugene Loring, 1975 and 1980.</p>
</acqinfo>
```

```xml
</acqinfo>
```

```xml
<processinfo>
  <head>Processing History</head>
  <p>Preliminary processing by Roger Berry in 1975 and 1980. Processing completed by Emma Kheradyar in 1996-1997. Guide edited by Laura Clark Brown in 1998 and completed by William Landis in 2000.</p>
</processinfo>
```

```xml
</processinfo>
```

```xml
<p>Preliminary processing by Roger Berry in 1975 and 1980. Processing completed by Emma Kheradyar in 1996-1997. Guide edited by Laura Clark Brown in 1998 and completed by William Landis in 2000.</p>
</processinfo>
```

```xml
</processinfo>
```

```xml
</descgrp>
```
## Content model

`<content>`

`</content>`

## Schema

### Declaration

element descgrp
{
  att.EADGlobal_attributes,
  att.typed_attributes,
  head?,
  (model_blocks | model desc base)+
}

## <descrules>

`<descrules>` (Descriptive Rules) A subelement of Profile Description `<profiledesc>` for the enumeration of the rules, standards, conventions, and protocols used in preparing the description.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

**Contained by** EAD: profiledesc

**May contain** EAD: abbr archref bibref emph expan extptr extref lb linkgrp ptr ref subtitle title

**Note**

Do not confuse this element with the RULES attribute in the `<controlaccess>` subelements, e.g., `<persname>`, `<geogname>`, and `<title>`, which are used to specify the descriptive rules, such as AACR2R, used in formulating individual access points. The `<descrules>` element is comparable to ISAD(G) data element 3.7.2.

**Example**

`<descrules xmlns="urn:isbn:1-931666-22-9">Finding aid prepared using <title render="italic">Rules for Archival Description</title></descrules>`

## Content model

`<content>`

`</content>`

## Schema

### Declaration

element descrules { att.EADGlobal_attributes, ( text | model.phrase.basicConfig )* }

## <did>

`<did>` (Descriptive Identification) A required wrapper element that bundles other elements identifying core information about the described materials in either Archival Description `<archdesc>` or a Component `<c>`. The various `<did>` subelements are intended for brief, clearly designated statements of information and, except for `<note>`, do not require Paragraphs `<p>` to enter text.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

**Contained by** EAD: archdesc archdescgrp c c01 c02 c03 c04 c05 c06 c07 c08 c09 c10 c11 c12

**May contain** EAD: abstract container dao daogrp head langmaterial materialspec note origination physdesc physloc repository unitdate unitid unittitle

**Note**

The `<did>` groups elements that constitute a good basic description of an archival unit. This grouping ensures that the same data elements and structure are available at every level of description within the EAD hierarchy. It facilitates
the retrieval or other output of a cohesive body of elements for resource discovery and recognition. The <did> in <archdesc> is sometimes called the high level <did>, because it describes the collection as a whole. Consider using the following elements for this high level <did>: <head>, <origination>, <unittitle>, <physdesc>, <repository>, and <abstract>. The <unitid> and <physloc> elements are suggested if applicable to a repository's practice. A <did> within a Component <c> can be less complete, and might have only a <container> or <unitid> and a <unittitle>.

**Example**
```xml
<archdesc xmlns="urn:isl:1-931666-22-9" type="inventory" level="subgrp">
  <did>
    <head>Overview of the Records</head>
    <repository label="Repository:">
      <corpname>Minnesota Historical Society</corpname>
    </repository>
    <origination label="Creator:">Minnesota. Game and Fish Department</origination>
  </did>
  <unittitle label="Title:">Game laws violation records</unittitle>
  <unitdate label="Dates:">1908-1928</unitdate>
  <abstract label="Abstract:">Records of prosecutions for and seizures of property resulting from violation of the state's hunting and fishing laws.</abstract>
  <physdesc label="Quantity:">2.25 cu. ft. (7 v. and 1 folder in 3 boxes)</physdesc>
  <physloc label="Location:">See Detailed Description section for box location</physloc>
</archdesc>
```

**Example**
```xml
<archdesc xmlns="urn:isl:1-931666-22-9" level="collection">
  <did>
    <unittitle>Early Durham Cartularies</unittitle>
    <unitid>GB-0033-DCD</unitid>
    <unitdate label="Date range:"
      normal="1220/1230">compiled
      between 1220 and 1230, with later additions</unitdate>
    <physdesc label="Extent:">1 cartulary (175ff. and inserts), 1 fragment and 1 [photostat of] fragment.</physdesc>
    <repository label="Repository:">Durham University Library, Archives and Special Collections</repository>
    <origination label="Origination:">early cartularies produced by the Durham monastic administration.</origination>
  </did>
</archdesc>
```

**Example**
```xml
<dsc xmlns="urn:isl:1-931666-22-9" type="combined">
  <c01 level="series">
    <did>
      <unittitle>Series 1: Correspondence,</unittitle>
      <unitdate type="inclusive">1943-1978</unitdate>
      <physdesc>
        <extent>2.5 linear ft.</extent>(5 document boxes)</physdesc>
      </did>
      <scopecontent>[...]</scopecontent>
    </unittitle>
  </c01>
</dsc>
```
<did>

<unittitle>Subseries 1.1: Outgoing Correspondence, </unittitle>

<unitdate type="inclusive">1943-1969</unitdate>

<physdesc>

<extent>0.75 linear
ft.</extent>

</physdesc>

</did>

<c03 level="file"

<did>

<physloc audience="internal">B:14:D</physloc>

<container type="box">1</container>

<container type="folder">1</container>

<unittitle>Abbinger-Aldrich</unittitle>

<physdesc>

<extent>14 letters</extent>

<physdesc>

<did>

<c03>

<c02>

<c01>

<dsc>

Schematron <did> elements MUST contain <unitid>

<s:rule context="ead:did"> <s:assert role="MUST" test="ead:unitid">a did MUST
have a unitid, according 17.3 and WP19</s:assert> </s:rule>

Schematron <did> elements MUST contain <unitittle>

<s:rule context="ead:did"> <s:assert role="MUST" test="ead:unittitle">a did
MUST have a unittitle, according 17.3</s:assert> </s:rule>

Schematron a <did> MUST have at least one non-empty <unitittle>

<s:rule context="ead:did"> <s:assert role="MUST"
test="count(ead:unittitle[text()]) > 0">a did MUST have at least one non-empty
unittitle</s:assert> </s:rule>

Content model

<content/>

Schema

Declaration element did { att.EADGlobal_attributes, ( head?, model.did+ ) }

<dimensions>

<dimensions> (Dimensions) A subelement of <physdesc> for information about the size of the materials being described; usually includes numerical data. Measurements may be expressed in any convenient unit. Attributes may be used when the unit of measurement or type of dimension is not clear in the finding aid text. The UNIT attribute specifies the kind of measurement, for example, "inches" or "meters." The TYPE attribute specifies the kind of dimensions being measured, for example, "height" or "circumference." Multiple dimensions, for example, height-by-width, can be tagged in a single <dimensions> element or in separate <dimensions> with distinctive attribute values.

Module EAD

Attributes att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.labeled (@label) att.typed (@type)

unit

Status

Optional
## Datatype

**Contained by** EAD: dimensions physdesc

**May contain** EAD: abbr archref bibref dimensions emph expan extptr extref lb linkgrp ptr ref subtitle title

**Note** Do not confuse with the `<extent>` element, which is used to tag the quantity of described materials.

**Example**
```xml
<dsc xmlns="urn:isb:1-931666-22-9" type="in-depth">
  <head>Handlist</head>
  <c01>
    <did>
      <unititle>Cartuarium vetus</unititle>
      <physdesc>3 paper leaves; 1 parchment on paper leaf; 175 leaves, 4 inserts, 2 schedules, parchment; 4 paper leaves <dimensions> approximately 230 mm x 163 mm.</dimensions>
    </physdesc>
    </did>
  </c01> . . . </dsc>
```

## Content model

```xml
<content>
</content>
```

## Schema Declaration

element dimensions
{
  att.EADGlobal_attributes,
  att.labeled_attributes,
  att.typed_attributes,
  attribute unit { text }?,
  ( text, model.phrase.basicConfig, dimensions )*
}
```

## <div>

### <div> (Text Division)
A generic element that designates a major section of text within <frontmatter>. Examples of these text divisions include a title page, preface, acknowledgments, or instructions for using a finding aid. Use the <head> element to identify the <div>'s purpose.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

**Contained by** EAD: div frontmatter

**May contain** EAD: address blockquote chronlist div head list note p table

**Example**
```xml
<frontmatter xmlns="urn:isb:1-931666-22-9">
  <titlepage>[...]</titlepage>
  <div>
    <head>Acknowledgements</head>
    <p>The University of California, Irvine Libraries wishes to acknowledge the generosity of the family of Edgar Holden for an endowment in support of the processing and maintenance of this collection and the University of California Office of the President for grant funding in support of the encoding of this and other finding aids using the Encoded Archival Description standard.</p>
  </div>
```
## Example

```html
</div> ... </frontmatter>
<frontmatter xmlns="urn:isl:1-931666-22-9">
  <titlepage>
    <titleproper>Inventory of the Rietta Hines Herbert Papers, 1940-1969</titleproper>
    <author>Processed by: Debra Carter</author>
    <publisher>Schomburg Center for Research in Black Culture</publisher>The New York Public Library</publisher>
    <date>August, 1977</date>
  </titlepage>
  <!--&amp;schtp;-->
  <p>© <date>1999</date> The New York Public Library, Astor, Lenox and Tilden Foundations. All rights reserved.</p>
</titlepage>
<div>
  <head>Preface</head>
  <p>This inventory is one of several prepared as a part of the archival preservation program at the Schomburg Center for Research in Black Culture, a research division of The New York Public Library.</p>
  <p>The Schomburg archival preservation program involves the organization and preservation of primary source material held by the Center and of significance to the study of the Black Experience. It furthermore includes the preparation of detailed inventories of these records, making the information contained therein accessible as well as available to scholars.</p>
  <p>The necessary staff and supplies for this program were made available through a combination of Library, National Endowment for the Humanities grant, and State of New York grant funds.</p>
</div>
</frontmatter>
```

## Content model

```xml
<content>
</content>
```

## Schema Declaration

```xml
element div { att.EADGlobal_attributes, head?, model_blocks*, div* }
```

## <dsc>

<dsc> (Description of Subordinate Components) A wrapper element that bundles information about the hierarchical groupings of the materials being described. The subordinate components can be presented in several different forms or levels of descriptive detail, which are identified by the element's required TYPE attribute. For example, "analyticover" identifies an overview description of series and subseries, which might be followed by a second <dsc> with the TYPE attribute set to "in-depth" that provides a more detailed listing of the content of the materials, including information about the container numbers associated with those materials. The TYPE attribute value "combined" is used when the description of a series is followed immediately by a listing of the contents of that series. The TYPE attribute "othertype" is for models that do not follow any of the above-mentioned formats, in which case the OTHERTYPE attribute can then be used to
specify a particular presentation model.

<table><tr><td>Module</td><td>EAD</td></tr><tr><td>Attributes</td><td>att.EADGlobal (@id, @altrender, @audience, @encodinganalog)<br/>att.dsectab.tpattern (@tpattern)<br/>type</td></tr><tr><td>Member of</td><td>model desc full</td></tr><tr><td>Contained by</td><td>EAD: archdesc archdescgrp c c01 c02 c03 c04 c05 c06 c07 c08 c09 c10 c11 c12 dsc</td></tr><tr><td>May contain</td><td>EAD: address blockquote c c01 chronlist dsc head list note p table thead</td></tr><tr><td>Note</td><td>See also related elements &lt;c&gt; and &lt;c01&gt; through &lt;c12&gt;.</td></tr><tr><td>Example</td><td>&lt;dsc xmlns="urn:isl:1-931666-22-9" type="combined"&gt;<br/>&lt;c01 level="series"&gt;<br/>&lt;did&gt;<br/>&lt;unittitle&gt;Activities, &lt;/unittitle&gt;<br/>&lt;unitdate type="inclusive"&gt;1965-1971&lt;/unitdate&gt;<br/>&lt;physdesc&gt;<br/>&lt;extent&gt;0.3 linear ft.&lt;/extent&gt;<br/>&lt;/physdesc&gt;<br/>&lt;/did&gt;<br/>&lt;scopecontent&gt;<br/>&lt;p&gt;The Activities series gives examples of the types of activities offered at the camp. The folders contain<br/>&lt;genreform&gt;reports,&lt;/genreform&gt;<br/>&lt;genreform&gt;schedules,&lt;/genreform&gt; and<br/>&lt;genreform&gt;inventories &lt;/genreform&gt; from each activity area of the camp. These records are predominantly from the late 1960s and early 1970s and replicate some of the information found in the staff manuals.&lt;/p&gt;<br/>&lt;/scopecontent&gt;<br/>&lt;c02 level="file"&gt;<br/>&lt;did&gt;<br/>&lt;container label="Box" type="box"&gt;1&lt;/container&gt;<br/>&lt;unittitle&gt;General, &lt;/unittitle&gt;<br/>&lt;unitdate type="inclusive"&gt;1970-1971&lt;/unitdate&gt;<br/>&lt;/did&gt;<br/>&lt;/c02&gt;<br/>&lt;c02 level="file"&gt;<br/>&lt;did&gt;<br/>&lt;container type="box"&gt;1&lt;/container&gt;<br/>&lt;unittitle&gt;Camp Crafts, &lt;/unittitle&gt;<br/>&lt;unitdate&gt;1967&lt;/unitdate&gt;<br/>&lt;/did&gt;<br/>&lt;/c02&gt;<br/>&lt;c02 level="file"&gt;<br/>&lt;did&gt;<br/>&lt;container type="box"&gt;1&lt;/container&gt;</td></tr></table>
Example

<unittitle>Education Program, </unittitle>
<unitdate>1967</unitdate>
</did>
</c02>
<c02 level="file">
<did>
<container type="box">1</container>
<unittitle>Expressive Arts, </unittitle>
<unitdate>1970</unitdate>
</did>
</c02> ... </c01> ... </dsc>
<dsc xmlns="urn:isl:1-931666-22-9" type="analyticover">
<c01 level="series">
<did>
<unitid>1-429-1</unitid>
<unittitle>Forest Stand Maps by Township and Basemap </unittitle>
<unitdate type="inclusive">1958-1979</unitdate>
<physdesc>
<extent>36 ft. (approx. 1700 sheets)</extent>
of <genreform>cartographic records.</genreform>
</physdesc>
<materialspec>Scale: predominantly 4 inches to 1 mile
(1:15,840)</materialspec>
</did>
<scopecontent>
<p>Series consists of forest stand maps. A map
sheet was created for each township of the surveyed
section of the province and for each basemap area in
unsurveyed areas.</p> ... </scopecontent>
</c01>
<c01 level="series">
<did>
<unitid>RG 1-429-2</unitid>
<unittitle>Forest Stand Map Composites</unittitle>
<unitdate type="inclusive">1958-1971</unitdate>
<physdesc>
<extent>ca.70</extent>
<genreform>maps</genreform>
</genreform>
</physdesc>
<materialspec>Scale: 1 inch to 1 mile</materialspec>
</did>
<scopecontent>
<p>Series consists of composite maps of the
forest resource inventory data from all the
townships within a Forestry Management Unit. The
composites offer a broader view of an area than the
township/basemaps, however the forest stand
statistics are quite small and difficult to
read.</p> ... </scopecontent>
</c01> ... </dsc>
</dsc> urn:isl:1-931666-22-9 type="in-depth">

Example

D.11.4: Report on Standards
<c01 level="series">
  <did>
    <unittitle>Series 1: Administrative Records, </unittitle>
    <unitdate type="inclusive">1912-1956.</unitdate>
  </did>
  <c02>
    <did>
      <container id="mss92-894c-bx1"
                type="box">Box
                  1</container>
      <container parent="mss92-894c-bx1"
                  label="Folder" type="folder">7-8 </container>
      <unittitle>Annual reports, </unittitle>
      <unitdate type="inclusive">1912-16, 1922</unitdate>
    </did>
  </c02>
  <c02>
    <did>
      <container parent="mss92-894c-bx1"
                  label="Folder" type="folder">9 </container>
      <unittitle>Board of Directors—Minutes and
                  correspondence, </unittitle>
      <unitdate type="inclusive">1947-1949</unitdate>
    </did>
  </c02>
  <c02>
    <did>
      <container parent="mss92-894c-bx1"
                  label="Folder" type="folder">10 </container>
      <unittitle>Contracts and specifications for
                  construction of nurses' quarters, </unittitle>
      <unitdate>ca. 1947</unitdate>
    </did>
  </c02>
  <c02>
    <did>
      <container parent="mss92-894c-bx1"
                  label="Folder" type="folder">11 </container>
      <unittitle>Marin County Reports, </unittitle>
      <unitdate type="inclusive">1955-1956</unitdate>
    </did>
  </c02>
  <c01>
    <c01 level="series">
      <did>
        <unittitle>Series 3: Philip King Brown, </unittitle>
        <unitdate type="inclusive">1910-1931, n.d.</unitdate>
      </did>
      <c02>
        <did>
          <container parent="mss92-894c-bx1"
                      label="Folder" type="folder">21 </container>
        </did>
      </c02>
    </c01>
  </c01>
</c01>
<unittitle>Correspondence, </unittitle>

<unitdate type="inclusive">1910-1931</unitdate>

</did>

</c02>

<c02>

<did>

<container parent="mss92-894c-bx1"

label="Folder" type="folder">22 </container>

<unittitle>Writings, </unittitle>

<unitdate>n.d.</unitdate>

</did>

</c02> . . . </c01>

</dsc>

Schematron <dsc> MUST have a type attribute

<s:rule context="ead:dsc"> <s:assert role="MUST" test="@type">dsc MUST have a type attribute</s:assert> </s:rule>

Schematron if <dsc>'s type attribute has "othertype" for value, <dsc> MUST have a not empty othertype attribute

<s:rule context="ead:dsc"> <s:assert role="MUST" test="not(@type
='othertype') or (@othertype and not(@othertype=""))">if dsc's type attribute has
"othertype" for value, dsc MUST have a not empty othertype attribute</s:assert>
</s:rule>

Schematron the <dsc> components SHOULD numbered, from <c01> to <c06>

<s:rule role="SHOULD" context="ead:dsc | ead:c01 | ead:c02 | ead:c03 | ead:c04 | ead:c05 "> <s:assert test="not(ead:c)">the dsc components SHOULD numbered, from c01 to c06</s:assert> </s:rule>

Content model

<content/>

Schema

Declaration

element dsc

{ att.EADGlobal_attributes, att.dsctab.tpattern_attributes, attribute type { data.enumerated }?, ( head?, model_blocks* ), ( ( thread?, ( ( c, thread? )+ | ( c01, thread? )+ ) ) | dsc* ) }

<dscgroup>

<dscgroup> (Description of Subordinate Components Group) A wrapper element used only within the <archdescgrp> subelement of <eadgrp> in the EAD Group Document Type Definition. The <dscgrp> contains two or more <ead> encoded finding aids, one after the other.

Module EAD

Attributes att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

Contained by —

May contain EAD: address blockquote chronlist ead head list note p table

Note See also the <eadgrp> element.

Content model

<content>

</content>
## Schema

**Declaration** element dscgroup { att.EADGlobal_attributes, head?, ead, model_blocks* }

## <ead>

<ead> (Encode Archival Description) The outermost wrapper element for an information access tool known generically as a finding aid. A finding aid establishes physical and intellectual control over many types of archival materials and helps researchers understand and access the materials being described. The <ead> element defines a particular instance of a document encoded with the EAD Document Type Definition.

**Module** EAD

**Attributes**
att.EADGlobal (@id, @altrender, @audience, @encodinganalog)
att-relatedencoding (@relatedencoding)

**Contained by** EAD: dscgroup

**May contain** EAD: archdesc eadheader frontmatter

**Note**
The AUDIENCE attribute value may be set to "external" to display data in all subelements, unless the value is changed for a specific element. A separate Document Type Definition called EAD Group can be used to bundle <ead> finding aids that describe different parts of a collection that have been dispersed among various institutions or custodial units. See the <eadgrp> element description for additional information.

**Example**
The following elements constitute the minimum set of elements for an EAD instance (i.e., those required by the DTD). Although the Description of Subordinate Components <dsc> is not itself required, if it is used its type attribute must be set.

<ead xmlns="urn:isl:1-931666-22-9">
  <eadheader>
    <eadid>[...]</eadid>
    <filedesc>
      <titlestmt>
        <titleproper>[...]</titleproper>
      </titlestmt>
    </filedesc>
  </eadheader>
  <archdesc level="fonds">
    <did>[...]</did>
    <dsc type="combined">[...]</dsc>
  </archdesc>
</ead>

## Content model

<content>
</content>

## Schema

**Declaration**

 element ead
 {
  att.EADGlobal_attributes,
  att-relatedencoding_attributes,
  (eadheader, frontmatter?, archdesc)
 }
<eadheader>

<eadheader> (EAD Header) A wrapper element for bibliographic and descriptive information about the finding aid document rather than the archival materials being described. The <eadheader> is modeled on the Text Encoding Initiative (TEI) header element to encourage uniformity in the provision of metadata across document types.

**Module** EAD

**Attributes**
* att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att encodings (@countryencoding, @langencoding, @scriptencoding, @repositoryencoding, @dateencoding)
* att. relatedencoding (@relatedencoding)
* findaidstatus

The extent to which the encoded finding aid is a finished document.

**Status** Optional
**Datatype**

**Contained by** EAD: ead

**May contain** EAD: eadid filedesc profiledesc revisiondesc

**Note**
The <eadheader> is required, because information that was often unrecorded for a local paper finding aid is essential in a machine-readable environment. Four subelements are available, which must occur in the following order: <eadid> (required), <filedesc> (required), <profiledesc> (optional), and <revisiondesc> (optional). These elements and their subelements provide: a unique identification code for the finding aid; bibliographic information, such as the author and title of the finding aid; information about the encoding of the finding aid; and statements about significant revisions. The FINDAIDSTATUS attribute can be used to indicate how complete or polished the information in the finding aid is. The COUNTRYENCODING, DATEENCODING, LANGENCODING, REPOSITORYENCODING, and SCRIPTENCODING attributes are used to specify the ISO standards from which code values for other attributes, such as COUNTRYCODE in <eadid> and <unitid>, are taken. Some or all of the <eadheader> subelements can be used to display title page information. Alternatively, the <eadheader> can be blocked from display by setting the AUDIENCE attribute to "internal" and using the <frontmatter> <titlepage> elements to create a title page.

**Example**
Following are the required <eadheader> elements.
<eadheader xmlns="urn:isl:1-931666-22-9">
<eadid>[...]</eadid>
<filedesc>
<titlestmt>
<titleproper>[...]</titleproper>
</titlestmt>
</filedesc>
</eadheader>

**Schematron**
If the language of the description is not English, a parallel form of the title in English SHOULD be added. For instance, using another <unittitle> element with a type attribute
<s:rule context="ead:eadheader"> <s:assert role="SHOULD" test="ead:profiledesc/ead:langusage/@langcode = 'eng'">If the language of the description is not English, a parallel form of the title in English SHOULD be added. For instance, using another unittitle element with a type attribute</s:assert> </s:rule>

**Schematron**
<eadheader> MUST contain a <profiledesc> element
<s:rule context="ead:eadheader">
<s:assert role="MUST" test="ead:profiledesc">eadheader MUST contain a profiledesc element</s:assert> </s:rule>

**Schematron**
A date of creation for the finding aid is welcome. The relevant element in <date>, child of <creation>

<s:rule context="ead:eadheader"> <s:assert role="COULD" test="ead:creation/ead:date and normalize-space(ead:creation/ead:date)">eadheader COULD have a non-empty creation-date</s:assert> </s:rule>

**Content model**

<content/>

**Schema Declaration**

element eadheader
{
    att.EADGlobal_attributes,
    att encodings attributes,
    att.relatedencoding_attributes,
    attribute findaidstatus { text }?,
    (eadid, filedesc, profiledesc?, revisiondesc?)
}

<eadid>

<eadid> (EAD Identifier) A required subelement of <eadheader> that designates a unique code for a particular EAD finding aid document.

**Module** EAD

**Attributes**
att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.coded (@countrycode)

mainagencycode
A code compliant with ISO/DIS 15511 Information and Documentation International Standard Identifier for Libraries and Related Organizations (ISIL).

**Status** Optional

**Datatype**

**Note**
Values should be supplied without the country code, which should be placed instead in the COUNTRYCODE attribute.

url
An absolute (http://www.loc.gov/ead/ms99999.xml) or relative (ms99999.xml) Uniform Resource Locator.

**Status** Optional

**Datatype**

A Uniform Resource Name intended to serve as a persistent, location-independent, resource identifier.

urn

**Status** Optional

**Datatype**

A formal public identifier (FPI) that includes the owner name and an object name.

publicid

**Status** Optional

**Datatype**

**Note**
Defined in ISO/IEC 9070:1991, the FPI is intended to be universally unique, with each owner name being unique, and each object name unique within the name
identifier domain controlled by the owner.
A machine-readable unique identifier.

**Status** Optional

**Datatype**

**Contained by** EAD: eadheader

**May contain** Character data only

**Note**
Two of the attributes, COUNTRYCODE and MAINAGENCYCODE, are required to make the <eadid> compliant with ISAD(G) element 3.1.1. MAINAGENCYCODE provides the ISO 15511 code for the institution that maintains the finding aid (which may not be the same as the institution that is the custodian of the materials described). COUNTRYCODE supplies the ISO 3166-1 code for the country of the maintenance agency. In addition to these two attributes, it is recommended that repositories also use at least one of the following attributes: URL, PUBLICID, or IDENTIFIER to make the <eadid> globally unique. PUBLICID should be a Formal Public Identifier, URL an absolute or relative address, and IDENTIFIER a machine-readable unique identifier for the finding aid file. (The proper syntax for PUBLICID is defined in ISO/IEC 9070:1991 Information technology -- SGML support facilities -- Registration procedures for public text owner identifiers.)

**Example**
```xml
<eadid xmlns="urn:isb:1-931666-22-9" countrycode="us"
mainagencycode="txu-hu"
publicid="-//us::txu-hu//TEXT us::txu-hu::hrc.00001//EN"
url="www.lib.utexas.edu/taro/hrc/00001.xml">hrc.00001</eadid>
```

**Schematron**
the <eadid> element MUST contain text. Most of the time, it is automatically generated by the archival tool.

`<s:rule context="ead:eadid"> <s:assert role="MUST" test="normalize-space(.)">eadid MUST contain text</s:assert> </s:rule>`

**Schematron**
`<eadid> SHOULD contain a mainagencycode attribute, which provides (if applicable) the ISO 15511 code for the institution that maintains the finding aid.`
`<s:rule context="ead:eadid"> <s:assert role="SHOULD" test="@mainagencycode">eadid SHOULD contain a mainagencycode attribute</s:assert> </s:rule>`

**Content model**
`<content/>`

**Schema Declaration**

```json
{
  att.EADGlobal_attributes,
  att.coded_attributes,
  attribute mainagencycode { text }?,
  attribute url { text }?,
  attribute urn { text }?,
  attribute publicid { text }?,
  attribute identifier { text }?,
  text
}
```

## <edition>

`<edition>` (Edition) A version of the finding aid or other bibliographic entity. When used in the `<editionstmt>` subelement of the `<eadheader>` or in the `<titlepage>` subelement of `<frontmatter>`,
the `<edition>` refers to the version of the finding aid. A new edition of a finding aid represents substantial additions or changes and should supersede previous online versions. When used in a Bibliographic Reference `<bibref>`, the `<edition>` element specifies the version of a published work.

**Module** EAD

**Attributes** att.EADGlobal (`@id`, `@altrender`, `@audience`, `@encodinganalog`)

**Contained by** EAD: bibref editionstmt titlepage unittitle

**May contain** EAD: emph extptr lb ptr

**Example**
```xml
<eadheader xmlns="urn:islbn:1-931666-22-9" audience="internal"
langencoding="iso639-2b">
<eadid>[...]</eadid>
<filedesc>
<titlestmt>[...]</titlestmt>
<editionstmt>
<edition>2nd ed.</edition>
<p>This edition reflects substantial additions to the
collection in 1994.</p>
</editionstmt>
</filedesc> . . . </eadheader>
```

**Content model**

`<content>`

`</content>`

**Schema Declaration**

`element edition { att.EADGlobal_attributes, (text | model.phrase.bare) }*}`

**<editionstmt>**

`<editionstmt>` (Edition Statement) An optional subelement within the `<filedesc>` portion of the `<eadheader>` element that groups information about a finding aid edition by providing an `<edition>` element as well as a Paragraph `<p>` element for narrative statements.

**Module** EAD

**Attributes** att.EADGlobal (`@id`, `@altrender`, `@audience`, `@encodinganalog`)

**Contained by** EAD: filedesc

**May contain** EAD: edition p

**Example**
```xml
<eadheader xmlns="urn:islbn:1-931666-22-9" audience="internal"
langencoding="iso639-2b">
<eadid>[...]</eadid>
<filedesc>
<titlestmt>[...]</titlestmt>
<editionstmt>
<edition>2nd ed.</edition>
<p>This edition reflects substantial additions to the
collection in 1994.</p>
</editionstmt>
</filedesc> . . . </eadheader>
```

**Example**
```xml
<filedesc xmlns="urn:islbn:1-931666-22-9">
<titlestmt>
<titleproper>Etat sommaire des fonds d'archives privées du
Centre historique des Archives nationales</titleproper>
<subtitle>Séries AP et AB XIX</subtitle>
<author>Instrument de recherche rédigé par Claire Sibille,
avec la collaboration de George-Andrée Banguio et de</author>
</filedesc>
```
Violaine Le Nénaon, sous la direction de Christine
Nougaret</author>

</titlestmt>

<editionstmt>

<edition> Première édition</edition>

</editionstmt>

<publicationstmt>

<publisher>Centre historique des Archives nationales de
France (CHAN)</ publisher>

<address>

<addressline>60 rue des Francs-Bourgeois</addressline>

<addressline>F-75141 PARIS CEDEX 03</addressline>

<address>

<date>mai 2001</date>

<publicationstmt>

<filedesc>

Content model

<content>

</content>

Schema

Declaration element editionstmt { att.EADGlobal_attributes, ( edition | p )+ }

<emph>

<emph> (Emphasis) A formatting element for marking words or phrases that are stressed or emphasized for linguistic effect. Use the RENDER attribute to specify the kind of emphasis, e.g., bold or italics.

Module EAD

Attributes att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att rendered (@render)

Member of model District render

Contained by EAD: abstract addressline archref author bibref bibseries container corpname
creation date descrules dimensions edition emph entry event extrefloc famname
function genreform geogname head head01 head02 imprint item label
langmaterial language language legalstatus materialspec name num occupation
origination p persname physdesc physfacet physloc publisher ref refloc repository
resource runner sponsor subarea subject subtitle title titleproper unitdate unitid
unittitle

May contain EAD: abbr archref bibref emph expan extptr extref lb linkgrp ptr ref subtitle title

Note

When the content of an entire element should always be rendered in italics or
some other display feature, use the style sheet functions instead of the <emph>
element.

Example

<abstract xmlns="urn:isl:1-931666-22-9" label="Abstract"> Papers document Donald C. Stone's work with Ornstein and Swencionis on the <emph> render="italic"> est</emph> Outcome Project, and the development of his doctoral research, including his various publications on the human potential movement, up to the completion of his doctoral dissertation. </abstract>

Content model

<content>

</content>
## Schema

### Declaration

element emph
{
  att.EADGlobal_attributes,
  attrendered_attributes,
  (text | model.phrase.basicConfig)*
}

## <entry>

<entry> (Table Entry) A formatting element that designates the contents of a cell in a table. A cell is the intersection of a row and a column. The <entry> attributes control cell spanning, alignment of the contents, and the rules on the cell edges. The attributes can be specified for <entry> or inherited from the nearest of the following table elements: <table>, <tgroup>, <colspec/>, <tbody>, or <row>.

### Module

EAD

### Attributes

att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

align

Status

Optional

Datatype

Legal values are: left

right

center

justify

char

char

Status

Optional

Datatype

charoff

Status

Optional

Datatype

colname

Status

Optional

Datatype

colsep

Status

Optional

Datatype

Legal values are: 1

O

morerows

Status

Optional

Datatype

nameend

Status

Optional

Datatype

namest

Status

Optional

Datatype

rowsep

Status

Optional

Datatype

Legal values are: 1
O

<table><tr><td>valign</td><td>Status</td><td>Optional</td></tr><tr><td></td><td>Datatype</td><td></td></tr><tr><td></td><td>Legal values are:</td><td>top</td></tr></table>

middle

bottom

<table><tr><td>Contained by</td><td>EAD: row</td></tr><tr><td>May contain</td><td>EAD: abbr address archref bibref corpname date emph expan extptr extref famname function genreform geogname lb linkgrp list name note num occupation origination persname ptr ref repository subject subtitle title unitdate unittitle</td></tr><tr><td>Note</td><td>Three attributes are used together to force horizontal alignment on a specific character, such as a decimal point. The ALIGN attribute must be set to "char" (align="char"). The CHAR attribute should be set to the specific character on which the text will align (for example the decimal point, char="."). The CHAROFF attribute controls the position of the alignment by naming the percentage of the current column width that is to the left of the alignment character (for example, charoff="30"). The extent of a horizontal span is determined by naming the first column (NAMEST) and the last column (NAMEEND) in the span. By convention, the specified rule is printed or displayed to the right of the column. External rules are specified using the FRAME attribute of the &lt;table&gt; element, horizontal rules are specified using ROWSEP.</td></tr></table>

<table><tr><td>Example</td><td><table xmlns="urn:isl:1-931666-22-9" frame="none"><thead><tr><th>colspec</th><th>colname</th></tr></thead><tbody><tr><td>align="left" colwidth="50pt"/></td><td>Major Family Members</td></tr><tr><td>align="left" colwidth="50pt"/></td><td>Spouses</td></tr><tr><td>align="left" colwidth="50pt"/></td><td>Children</td></tr></tbody></table></td></tr></table>

Content model
<chronitem>
  <date>1917-1919</date>
  <event>Served in <corpname>United States Army</corpname>
</event>
</chronitem>
</chronlist>
</bioghist>

## Content model

<content>
</content>

## Schema

**Declaration** element event { att.EADGlobal_attributes, ( text | model.para.content )* }

## <eventgrp>

<eventgrp> (Event Group) An element within a Chronology List Item <chronitem> that bundles multiple <event>s associated with the same <date>.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

**Contained by** EAD: chronitem

**May contain** EAD: event

**Note** See related element Chronology List <chronlist>.

**Example**

<bioghist xmlns="urn:isl:1-931666-22-9">
  <head>Biographical Note</head>
  <chronlist>
    <chronitem>
      <date normal="19010718">1901 July 18</date>
      <event>Born, Holsterhausen, Westphalia, Germany</event>
    </chronitem>
    <chronitem>
      <date normal="1918">1918</date>
      <event>Member and active participant of Sokoly, Polish insurrection against the Germans</event>
    </chronitem>
    <chronitem>
      <date normal="1920">1920</date>
      <eventgrp>
        <event>Private, Polish Army, Polish-Russo War</event>
        <event>Graduated from Agricultural High School, People's University</event>
      </eventgrp>
    </chronitem>
    ...
  </chronlist>
</bioghist>

## Content model

<content>
</content>

## Schema

**Declaration** element eventgrp { att.EADGlobal_attributes, event+ }
<expan>

<expan> (Expansion) A generic element to designate the full form of a word that often appears as an abbreviation or acronym. Use the ABBR attribute to supply the abbreviated form for indexing or searching purposes.

**Module** EAD

**Attributes**

att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

abbr An abbreviation for a word or phrase that is expressed in an expanded form in the text; used for searching and indexing purposes. Available only in the <expan> element.

**Status** Optional

**Datatype**

**Member of** model.phrase.basicConfig

**Contained by** EAD: abstract archref bibref creation descrules dimensions emph entry event extrefloc item label langmaterial langusage materialspec origination p physdesc physfacet physloc ref refloc repository subtitle titleproper unitdate unitid untitle

**May contain** Character data only

**Note** See also related element Abbreviation <abbr>.

**Example** <note xmlns="urn:isl:1-931666-22-9">

**Content model**

**Schema**

**Declaration** element expan { att.EADGlobal_attributes, attribute abbr { text }?, text }

<extent>

<extent> (Extent) A <physdesc> subelement for information about the quantity of the materials being described or an expression of the physical space they occupy. Includes such traditional archival measurements as cubic and linear feet and meters; also includes counts of microfilm reels, photographs, or other special formats, the number of logical records in a database, or the volume of a data file in bytes.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.typed (@type) att.labeled (@label)

unit **Status** Optional

**Datatype**

**Contained by** EAD: physdesc

**May contain** Character data only

**Note** Repeat the element when more than one type or unit of extent is provided, such as, when both linear feet and quantity of containers are given. Use the UNIT attribute to indicate the measurement unit, e.g., "bytes" or "cubic meter." Use the <dimension> element when it is necessary to specify the size of the archival materials being described, for example, height and width.

**Example** <archdesc xmlns="urn:isl:1-931666-22-9" level="collection">
<persname encodinganalog="100"
label="Creator:" source="Icnaf"> Franklin, George A. (George
Albert).</persname>
</origination>
<unititle>The George Franklin Papers, </unititle>
<unitdate type="inclusive">1928-1972</unitdate>
<physdesc>
<extent>100 boxes; </extent>
<extent>50 linear feet</extent>
</physdesc>
</did>
</archdesc>

Example

<c xmlns="urn:isl:1-931666-22-9" level="file">
<did>
<physloc audience="internal">B:14:D</physloc>
<container type="box">1</container>
<container type="folder">1</container>
<unititle>Abbinger-Aldrich</unititle>
<physdesc>
<extent>14 letters</extent>
</physdesc>
</did>
</c>

Content model

<content>
</content>

Schema

Declaration

element extent
{
  att.EADGlobal_attributes,
  att.typed_attributes,
  att.labeled_attributes,
  attribute unit { text }?,
  ( text | m.phrase.basicConfig )*
}

<extptr/>

<extptr/> (Extended Pointer) An empty linking element that uses attributes to connect the EAD document to an external electronic object, which is not part of the materials being described. Examples include graphic representations of a repository's seal or logo, and pointers to an institution's web page.

Module EAD

Attributes
att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.xlink (@label, @href, @type, @title, @from, @to, @role, @actuate, @show, @arcrole, @xpointer, @entityref, @target, @parent)

Member of model.phrase.bare

Contained by EAD: abstract addressline archref author bibref bibseries container corpname creation date descrules dimensions edition emph entry event extrefloc famname function genreform geogname head head01 head02 imprint item label langmaterial language langusage legalstatus materialspec name num occupation
## Content model

`<content>`

`</content>`

## Schema Declaration

element extptrloc { att.EADGlobal_attributes, att.xlink_attributes, empty }

## <extref>

`<extref>` (Extended Reference) A linking element that can include text and subelements as part of its reference to an electronic object that is external to the EAD document.

**Module** EAD

**Attributes**
att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.xlink (@label, @href, @type, @title, @from, @to, @role, @actuate, @show, @arcrole, @xpointer, @entityref, @target, @parent)

**Member of** modelpag

**Contained by**
EAD: abstract archref bibliography bibref creation descrules dimensions emphasis entry event item label langmaterial language materialspec origination otherfindaid p physdesc physfacet physloc ref relatedmaterial repository separatedmaterial unitdate unitid unittitle

**May contain** EAD: archref bibref ref title

**Note**

Use the ENTITYREF or HREF attribute to identify the external object. Use the `<ref>` element to point to another location within the EAD document. While XML Linking Language (XLink) Version 1.0, which is the basis for EAD linking elements, is a stable document, examples of EAD usage are hypothetical and have not been tested in real XLink-based applications. Those wishing to use XLink are encouraged to consult the specification available online at http://www.w3.org/TR/xlink.

## Example

```xml
<bioghist xmlns="urn:isl:1-931666-22-9">
  <head>Chronology</head>
  <chronlist> . . . </chronitem>
  <date normal="199510">October 1995</date>
  <event>
    <extref linktype="simple" entityref="nobelsite" title="Nobel Prize eMuseum" actuate="onrequest" show="new">Awarded Nobel Prize in Physics by the Royal Swedish Academy of Sciences.</extref>
  </event>
  <</chronitem> . . . </chronlist>
</bioghist>
```

## Content model

`<content>`

`</content>`

## Schema Declaration

element extref

```json
{
  att.EADGlobal_attributes,
  att.xlink_attributes,
  (text | m.para.content.norefs | bibref | title | archref | ref)*
}
```
<extrefloc>

<extrefloc> (Extended Reference Location) The location of an Extended Reference <extref> that is a resource in an extended link.

**Module** EAD

**Attributes**
att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.xlink (@label, @href, @type, @title, @from, @to, @role, @actuate, @show, @arcrole, @xpointer, @entityref, @target, @parent)

**Member of** model.extended.els

**Contained by** EAD: daogrp linkgrp

**May contain**
EAD: abbr address blockquote chronlist corpname date emph expan extptr famname function genreform geogname lb list name note num occupation origination persname ptr repository subject table unitdate unittitle

**Note**
While XML Linking Language (XLink) Version 1.0, which is the basis for EAD linking elements, is a stable document, examples of EAD usage are hypothetical and have not been tested in real XLink-based applications. Those wishing to use XLink are encouraged to consult the specification available online at http://www.w3.org/TR/xlink.

**Example**
<relatedmaterial xmlns="urn:isl:1-931666-22-9">
<p>The Society also has records of other conservation organizations in Minnesota.</p>

<p>
<linkgrp linktype="extended">
<extrefloc href="http://www.someserver.edu/findaids/3270.xml">
<archref>Issak Walton League of Minnesota</archref>
</extrefloc>
</linkgrp>

<extrefloc href="http://www.someserver.edu/findaids/9248.xml">
<archref>Minnesota Audubon Council</archref>
</extrefloc>

<extrefloc entityref="FBWW">
<archref>Friends of the Boundary Waters
Wilderness</archref>
</extrefloc>

<extrefloc href="http://www.someserver.edu/findaids/23145.sgm">
<archref>Minnesota Emergency Conservation
Committee</archref>
</extrefloc>

Content model

Schema

**Declaration**

```xml
<extrefloc>
    <element extrefloc>
        <att.EADGlobal_attributes>
        <att.xlink_attributes>
            ( text | model.para.content.norefs )*
        </att.xlink_attributes>
    </element>
</extrefloc>
```
`<famname>`

`<famname>` (Family Name) The proper noun designation for a group of persons closely related by blood or persons who form a household. Includes single families and family groups, e.g., Patience Parker Family and Parker Family.

**Module** EAD

**Attributes**
att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.access (@source, @rules, @authfilenumber, @normal) att.roled (@role)

**Member of** model.access

**Contained by**
EAD: bibref controlaccess entry event extrefloc indexentry item label namegrp origination p physdesc physfacet ref refloc unittitle

**May contain** EAD: emph extptr lb ptr

**Note**
All names in a finding aid do not have to be tagged. One option is to tag those names for which access other than basic, undifferentiated keyword retrieval is desired. Use of authorized forms is recommended to facilitate access to the names within and across finding aid systems. The `<famname>` element may be used in text elements such as `<p>`. To indicate a family name with major representation in the materials being described, nest `<famname>` within the `<controlaccess>` element. The `ROLE` attribute can be used to specify the relationship(s) of the name to the materials being described, for example, "compiler," "creator," "collector," or "subject." The `NORMAL` attribute can be used to provide the authority form of a name that has been encoded with `<famname>` in narrative text, e.g., within a paragraph. The `AUTHFILENUMBER` attribute can be used to identify a link to an authority file record that has more information about the name or cross references for alternative forms of the name and related names. Use the `SOURCE` attribute to specify the vocabulary from which the name has been taken and/or the `RULES` attribute to specify the descriptive rules followed when forming the name.

See also the related elements `<controlaccess>`, `<corpname>`, `<persname>`, and `<name>`.

The `<famname>` element is comparable to MARC fields 100, 600, 700.

**Example**
<indexentry xmlns="urn:isl:1-931666-22-9">
  <famname>Hely-Hutchinson family</famname>
  <indexentry>
    <genreform> Pedigree, 20th cent.</genreform>
    <ref linktype="simple" role="internal"
          target="EngC5769-f74" show="replace" actuate="onrequest">MS. Eng. c. 5769,
          fol. 74</ref>
  </indexentry>
</indexentry>

**Example**
<archdesc xmlns="urn:isl:1-931666-22-9" level="collection">
  <did>[...]</did> . . . <controlaccess>
    <head>Controlled Vocabulary Indexing Terms:</head>
    <controlaccess>
      <head>Subjects:</head>
      <famname encodinganalog="600"
                source="lcnaf">Ferry
                  family.</famname>
      <geogname encodinganalog="651"
                  source="lcsh">Ferry Field
                    (University of Michigan)</geogname>
    </controlaccess>
  </archdesc>
```xml
</controlaccess>
</archdesc>
```

## Content model

```xml
<content>
</content>
```

## Schema

### Declaration

element famname
{
  att.EADGlobal_attributes,
  att.access_attributes,
  att.roled_attributes,
  (text | model.phrase.bare)*
}

## <filedesc>

### <filedesc>
(File Description) A required subelement of the <eadheader> that bundles much of the bibliographic information about the finding aid, including its author, title, subtitle, and sponsor (all in the <titlestmt>), as well as the edition, publisher, publishing series, and related notes (encoded separately).

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

**Contained by** EAD: eadheader

**May contain** EAD: editionstmt notestmt publicationstmt seriesstmt titlestmt

### Note

This element has been modeled on a Text Encoding Initiative (TEI) DTD element and includes the following subelements, in this order: a required <titlestmt>, an optional <editionstmt>, an optional <publicationstmt>, an optional <seriesstmt>, and an optional <notestmt>. The <filedesc> provides information that is helpful for citing a finding aid in a bibliography or footnote. Institutions that catalog finding aids separately from the archival materials being described might use the <filedesc> elements to build a basic bibliographic record for the finding aid. Do not confuse with the <profiledesc> element, which describes the encoding of the finding aid. Do not confuse with <archdesc> elements, which refer to the materials being described rather than the finding aid itself.

### Example

```xml
<eadheader xmlns="urn:isl:1-931666-22-9">
  <eadid>[...]</eadid>
  <filedesc>
    <titlestmt>
      <titleproper>Guide to the Bank of Willows Records,</      <date>1880-1905</date>
      <titleproper>
      </titlestmt>
      <publicationstmt>
        <!--&amp;hdr-cst-spcoll;-->
        <date>© 1999</date>
        <p>The Board of Trustees of Stanford University. All      rights reserved.</p>
      </publicationstmt>
    </filedesc>
    <profiledesc>[...]</profiledesc>
  </filedesc>
</eadheader>
```
```xml
</eadheader>
```

### Example

```xml
<filedesc xmlns="urn:ibn:1-931666-22-9">
```

```xml
<titlestmt>
```

```xml
<titleproper>Inventory of the Otis Turner Papers,
1978-1990</titleproper>
```

```xml
<author>Processed by Hanna Bailey</author>
```

```xml
</titlestmt>
```

```xml
<publicationstmt>
```

```xml
<!--&amp;hdrscm;-->
```

```xml
<p>© <date>2000</date> The New York Public Library. Astor,
Lenox and Tilden Foundations. All rights reserved.</p>
```

```xml
</publicationstmt>
```

```xml
</filedesc>
```

### Content model

```xml
<content>
```

```xml
</content>
```

### Schema Declaration

#### Declaration

element filedesc

<figure><img src="image_9.png" /></figure>

att.EADGlobal_attributes,

( titlestmt, editionstmt?, publicationstmt?, seriesstmt?, notestmt? )

<figure><img src="image_10.png" /></figure>

## <fileplan>

### <fileplan>
(File Plan) Information about any classification scheme used for arranging, storing, and retrieving the described materials by the parties originally responsible for creating or compiling them. A filing plan is usually identified by the type of system used, e.g., alphabetical, numerical, alpha-numerical, decimal, color-coded, etc. It is often hierarchical and may include the filing guidelines of the originating organization. Additional types include a drawing of a room layout or a scientific scheme.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

**Member of** model desc. base

**Contained by** EAD: archdesc archdescgrp c c01 c02 c03 c04 c05 c06 c07 c08 c09 c10 c11 c12 descgrp fileplan

**May contain** EAD: fileplan head

**Note**

Do not confuse with Other Finding Aid <otherfindaid> which contains references to additional descriptions of the material rather than descriptions of classification schemes by which the materials might still be arranged. In EAD Version 1.0 fileplan was a subelement of Adjunct Descriptive Data <add>, which has been deprecated in EAD 2002 (see Appendix B). The new Description Group <descgrp> element, which can group any of the <did>-level elements (except the Description of Subordinate Components <dsc>), may be used to wrap elements where a group heading is desirable. The <descgrp> element can be used to replace <add> when converting finding aids encoded in EAD V1.0 to EAD 2002.

### Example

```xml
<fileplan xmlns="urn:ibn:1-931666-22-9">
```

```xml
<head>File List</head>
```

```xml
<note>
```

```xml
<p>The list below outlines the classification system used
```
for the central files of Vice President Mondale's
office. This structure assigned alpha-numeric codes to
primary subjects and to secondary and tertiary
subdivisions thereunder.</p>

</note>

<fileplan>

<head>AGRICULTURE (AG)</head>

<list type="ordered">

<defitem>

<label>1</label>

<item>Home Economics</item>

</defitem>

<defitem>

<label>2</label>

<item>Horticulture</item>

</defitem>

<defitem>

<label>3</label>

<item>Marketing</item>

</defitem>

<defitem>

<label>4</label>

<item>Price Support</item>

</defitem>

</list>

<fileplan>

<fileplan>

<head>ARTS (AR)</head>

<list type="ordered">

<defitem>

<label>1</label>

<item>Languages</item>

</defitem>

<defitem>

<label>2</label>

<item>Museums</item>

</defitem>

<defitem>

<label>3</label>

<item>Music</item>

</defitem>

<defitem>

<label>4</label>

<item>Painting/Drawing</item>

</defitem>

</list>

<fileplan>

<fileplan>

Content model

<content>

</content>
Schema

Declaration element fileplan { att.EADGlobal_attributes, head?, ( m_blocks | fileplan )+ }

<frontmatter>

<frontmatter> (Front Matter) A wrapper element that bundles prefatory text found before the start of the Archival Description <archdesc>. It focuses on the creation, publication, or use of the finding aid rather than information about the materials being described. Examples include a title page, preface, dedication, and instructions for using a finding aid. The optional <titlepage> element within <frontmatter> can be used to repeat selected information from the <eadheader> to generate a title page that follows local preferences for sequencing information. The other <frontmatter> structures, such as a dedication, are encoded as Text Divisions <div>s, with a <head> element containing word(s) that identify the nature of the text.

Module EAD

Attributes att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

Contained by EAD: ead

May contain EAD: div titlepage

Example
<frontmatter xmlns="urn:isl:1-931666-22-9">
  <titlepage>
    <titleproper>Register of the Gibbons (Stuart C.) Papers,</date>
  </titleproper>
  <num>Collection number: Ms28</num>
  <publisher>San Joaquin County Historical Society and Museum</lb/>
  <extptr actuate="onload" show="embed"
    entityref="sjmlogo"/>
  <lb/> Lodi, California</publisher>
  <!--&amp;tp-cstoh;-->
  <list type="deflist">
    <defitem>
      <label>Processed by: </label>
      <item>Don Walker</item>
    </defitem>
    <defitem>
      <label>Date Completed: </label>
      <item>1997</item>
    </defitem>
    <defitem>
      <label>Encoded by: </label>
      <item>Don Walker</item>
    </defitem>
    <list>
      <p>© 2000 San Joaquin County Historical Society &amp;</p>
      <p>Museum. All rights reserved.</p>
    </list>
  </titlepage>
</frontmatter>

Content model

<content>

</content>

Schema
**Declaration** element frontmatter { att.EADGlobal_attributes, titlepage?, div* }

<function>

<function> (Function) Terms for the spheres of activities and processes that generated the described materials. Such terms often provide useful access points to the materials, especially for corporate, government, or institutional records. Examples include: collecting taxes and entertaining.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.access (@source, @rules, @authfilenumber, @normal)

**Member of** model.access

**Contained by** EAD: controlaccess entry event extrefloc indexentry item label namegrp p physdesc physfacet ref refloc untitle

**May contain** EAD: emph extptr lb ptr

**Note**

All functions mentioned in a finding aid do not have to be tagged. One option is to tag those functions for which access other than basic, undifferentiated keyword retrieval is desired. Use of controlled vocabulary forms is recommended to facilitate access to the functions within and across finding aid systems. The <function> element may be used in text elements such as <p>. To indicate a function with major representation in the materials being described, nest <function> within the <controlaccess> element. Use the SOURCE attribute to specify the vocabulary from which the term has been taken. The AUTHFILENUMBER attribute can be used to identify a link to an authority file record that has more information about the function or cross references for alternative forms of a function term.

Do not confuse with <occupation>, which designates a type of work or business and is often associated with personal papers.

See also the related access elements under <controlaccess>.

The <function> element is comparable to MARC field 657.

**Example**

<controlaccess xmlns="urn:ibn:1-931666-22-9">

<head>Index Terms</head>

<p>These records are indexed under the following headings in the catalog of the Minnesota Historical Society. Researchers wishing to find related materials should search the catalog under these index terms.</p>

<controlaccess>

<head>Government Functions:</head>

<function encodinganalog="657"

source="aat">Law

enforcing.</function>

<function encodinganalog="657"

source="aat">Convicting.</function>

</controlaccess>

<controlaccess>

**Content model**

<content>

</content>

**Schema**

**Declaration** element function

{
att.EADGlobal_attributes,
att.access_attributes,
(text | model.phrase.bare)*
}

<genreform>

<genreform> (Genre/Physical Characteristic) A term that identifies the types of material being described, by naming the style or technique of their intellectual content (genre); order of information or object function (form); and physical characteristics. Examples include: account books, architectural drawings, portraits, short stories, sound recordings, and videotapes.

**Module** EAD

**Attributes**
att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.typed (@type)
att.access (@source, @rules, @authfilenumber, @normal)

**Member of** model.access

**Contained by**
EAD: controlaccess entry event extrefloc indexentry item label namegrp p
physdesc physfacet ref refloc unittitle

**May contain** EAD: emph extptr lb ptr

**Note**
All genres and forms of material mentioned in a finding aid do not have to be tagged. One option is to tag those <genreform> terms for which access other than basic, undifferentiated keyword retrieval is desired. Use of controlled vocabulary terms is recommended to facilitate access to the information within and across finding aid systems. The <genreform> element may be used in text elements such as <p>. To indicate a function with major representation in the materials being described, nest <genreform> within the <controlaccess> element. To associate a <genreform> term with more detailed physical characteristics, use <genreform>> within the <physdesc> or <physfacet> elements. Use the SOURCE attribute to specify the vocabulary from which the term has been taken. The NORMAL attribute can be used to provide the authority form of a term that has been encoded with <genreform> in narrative text, e.g., within a paragraph. The AUTHFILENUMBER attribute can be used to identify a link to an authority file record that has more information about the term or cross references for alternative forms of a genre term.

See also the related access elements under <controlaccess>.

The <genreform> element is comparable to ISAD(G) data element 3.1.5 and MARC field 655, and, when used in conjunction with <extent>, to MARC field 300.

**Example** <controlaccess xmlns="urn:isl:1-931666-22-9">

<head>Index Terms</head>

<controlaccess>

<head>Physical Characteristics of Materials in the
Collection:</head>

<genreform encodinganalog="655$a"

source="gmGPC">Architectural drawings</genreform>

<genreform encodinganalog="655$a"

source="gmGPC">Photographs</genreform>

</controlaccess>

</controlaccess>

**Example** <scopecontent xmlns="urn:isl:1-931666-22-9">

<head>Scope and Content of the Collection</head>

<p>Although the bulk of the collection is composed of

<genreform>letters</genreform>, <genreform>portrait

photographs</genreform> appear in several series.</p>
```xml
</scopecontent>
```

### Example

```xml
<c01 xmlns="urn:isbn:1-931666-22-9" level="series">
  <did>[...]</did>
  <c02 level="file">
    <did>
      <unittitle>Diaries, </unittitle>
      <unitdate type="inclusive">1820-1864</unitdate>
      <physdesc>
        <extent>14
        </extent>
        <genreform>diaries</genreform> bound in
        <physfacet type="cover material">red
          leather</physfacet>
      </physdesc>
    </did>
  </c02>
</c01>
```

### Content model

```xml
<content>
</content>
```

### Schema Declaration

```json
element genreform
{
  att.EADGlobal_attributes,
  att.typed_attributes,
  att.access_attributes,
  (text | model.phrase.bare)*
}
```

## <geogname>

### <geogname> (Geographic Name)
The proper noun designation for a place, natural feature, or political jurisdiction. Examples include: Appalachian Mountains; Baltimore, Md.; Chinatown, San Francisco; and Kew Gardens, England.

**Module** EAD

**Attributes**
att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.access (@source, @rules, @authfilenumber, @normal) att.roled (@role)

**Member of** model.access

**Contained by**
EAD: controlaccess entry event extrefloc imprint indexentry item label namegrp p physdesc physfacet ref refloc unittitle

**May contain** EAD: emph extptr lb ptr

**Note**

All names in a finding aid do not have to be tagged. One option is to tag those names for which access other than basic, undifferentiated keyword retrieval is desired. Use of controlled vocabulary names is recommended to facilitate access to the names within and across finding aid systems. The <geogname> element may be used in text elements such as <p>. To indicate a place name with major representation in the materials being described, nest <geogname> within the <controlaccess> element. The ROLE attribute can be used to specify the relationship(s) of the name to the materials being described, for example, "subject." The NORMAL attribute can be used to provide the authority form of a term that has been encoded with <geogname> in narrative text, e.g., within a
paragraph. Use the SOURCE attribute to specify the vocabulary from which the name has been taken and/or the RULES attribute to specify the descriptive rules followed when forming the name. The AUTHFILENUMBER attribute can be used to identify a link to an authority file record that has more information about the name or cross references for alternative forms of the name and related names.
See also the related access elements under <controlaccess>.
The <geogname> element is comparable to MARC fields 651 and 752.

**Example**
```xml
<controlaccess xmlns="urn:isl:1-931666-22-9">
  <head>Controlled Vocabulary Indexing Terms:</head>
  <controlaccess>
    <head>Subjects:</head>
    <famname encodinganalog="600">
      <source="lcnaf">Ferry</source>
      <family>.</family>
    </famname>
    <geogname encodinganalog="651">
      <source="lcsh">Ferry Field</source>
      <univ>(University of Michigan)</univ></geogname>
    </controlaccess>
  </controlaccess>
</controlaccess>
```

**Content model**

```xml
<content>
</content>
```

**Schema Declaration**

element geogname
```json
{
  att.EADGlobal_attributes,
  att.access_attributes,
  att.roled_attributes,
  (text | model.phrase.bare)*
}
```

**<head>**

**<head>** (Heading) A generic element that designates the title or caption for a section of text, including a list. When a <head> is used, it should be the first subelement, followed by one or more other elements.

**Module** EAD

**Attributes**
att.EADGlobal (@id, @altrender, @audience, @encodinganalog)
althead
An alternative short form of the heading element <head> that might be used, for example, to create a running header.

**Status** Optional

**Datatype**

**Contained by**
EAD: accessrestrict accruals acqinfo altformavail appraisal arrangement
bibliography bioghist c c01 c02 c03 c04 c05 c06 c07 c08 c09 c10 c11 c12 chronlist
controlaccess custodhist daodesc descgrp did div dsc dscgroup fileplan index list
odd originalsloc otherfindaid phystech prefercite processinfo relatedmaterial
scopecontent separatedmaterial table userestrict

**May contain** EAD: emph extptr lb ptr

**Note**
Do not confuse with the <listhead> subelements <head01> and <head02>, which designate headings for columns in a list. A <head> element is used for column
heads in a table.

**Example**
```xml
<chronlist xmlns="urn:isl:1-931666-22-9">
  <head>Publications List</head>
  <listhead>
    <head01>Publication Year</head01>
    <head02>Book Title</head02>
  </listhead>
  <chronitem>[...]</chronitem>
</chronlist>
```

**Example**
```xml
<bioghist xmlns="urn:isl:1-931666-22-9" id="PRO123">
  <head>Administrative History</head>
  <p>In October 1964, the incoming Labour government created new office of Secretary of State for Economic Affairs (combined with First Secretary of State) and set up the Department of Economic Affairs under the Ministers of the Crown Act 1964 to carry primary responsibility for long term economic planning.</p>
</bioghist>
```

## Content model

```xml
<content>
</content>
```

## Schema

**Declaration**
```xml
element head
{
  att.EADGlobal_attributes,
  attribute althead { text }?,
  ( text | model.phrase.bare )*
}
```

### <head01>

### <head01> (First Heading)
A formatting element within <listhead> that designates the heading over the first column in a multicolumn list.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

**Contained by** EAD: listhead

**May contain** EAD: emph extptr lb ptr

**Note**
Do not confuse with the generic <head> element, which designates a heading for an entire list or other section of text. Do not confuse with the <thead> element, which is used for column heads in a table.

**Example**
```xml
<chronlist xmlns="urn:isl:1-931666-22-9">
  <head>Publications List</head>
  <listhead>
    <head01>Publication Year</head01>
    <head02>Book Title</head02>
  </listhead>
  <chronitem>
    <date type="publication">1928</date>
    <event>
      <title render="italic">The Happy Little Lamb</title>
    </event>
  </chronitem>
</chronlist>
```
```xml
</event>
</chronitem> ... </chronlist>
```

### Content model

```xml
<content>
</content>
```

### Schema

```xml
Declaration element head01 { att.EADGlobal_attributes, ( text | model.phrase.bare )* }
```

### <head02>

### <head02> (Second Heading)
A formatting element within <listhead> that designates the heading over the second column in a multicolumn list.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

**Contained by** EAD: listhead

**May contain** EAD: emph extptr lb ptr

**Note** Do not confuse with the generic <head> element, which designates a heading for an entire list or other section of text. Do not confuse with the <thead> element, which is used for column heads in a table.

**Example**
```xml
<chronlist xmlns="urn:isl:1-931666-22-9">
  <head>Publications List</head>
  <listhead>
    <head01>Publication Year</head01>
    <head02>Book Title</head02>
  </listhead>
  <chronitem>
    <date type="publication">1928</date>
    <event>
      <title render="italic">The Happy Little Lamb</title>
    </event>
  </chronitem>
</chronlist>
```

### Content model

```xml
<content>
</content>
```

### Schema

```xml
Declaration element head02 { att.EADGlobal_attributes, ( text | model.phrase.bare )* }
```

### <imprint>

### <imprint> (Imprint)
Information relating to the publication or distribution of a work cited in a Bibliographic Reference <bibref> or <unittitle>. In both elements the place of publication, name of the publisher, and date of publication can be encoded as either plain text or wrapped in the <imprint> subelements <geogname>, <publisher>, and <date>. It is seldom, if ever, appropriate to use <imprint> in a citation for an unpublished work cited in a <bibref>.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

**Contained by** EAD: bibref unittitle

**May contain** EAD: date emph extptr geogname lb ptr publisher

**Example** <bibref xmlns="urn:isl:1-931666-22-9">
<title render="italic">Action For Outdoor Recreation For America.</title>, <imprint> <geogname>Washington, D.C.</geogname>: <publisher>Citizen's Committee For The Outdoor Recreation Resources Review Commission Report</publisher>, <date type="publication" normal="1964">1964 </date>. </imprint> </bibref>

Content model

<content>
</content>

Schema

Declaration element imprint

{ att.EADGlobal_attributes, ( text | model.phrase.bare | publisher | geogname | date )* }

<index>

<index> (Index) A list of key terms and reference pointers that have been assembled to enhance access to the materials being described. The <index> can also serve as a helpful alphabetical overview of subjects, correspondents, photographers, or other entities represented in the collection. This back-of-the volume <index> may provide hypertext links, or it may note the container numbers useful for locating the position in the finding aid where the indexed material appears.

Module EAD

Attributes att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

Contained by EAD: index

May contain EAD: address blockquote chronlist head index indexentry list listhead note p table

Note

The <index> is assumed to be text that has to be tagged, not text generated automatically from the encoded finding aid. In some cases, the <index> repeats terms and names found elsewhere in the finding aid. In other cases, such as in some literary manuscript collections, the <index> may be the only place where a name is listed, and the references point to one or more files, which include letters from that person or corporate body, but which are described only in general terms, e.g., "Correspondents T-Z."The <index> should contain <indexentry> elements, which consist of an access element, such as <name> or <subject>, followed by a Pointer <ptr/>, Pointer Group <ptrgrp>, or Reference <ref> element. Plain text cannot be used in an <indexentry>. If the <indexentry> elements are expected to provide access points other than basic keyword retrieval, use authority file terms to facilitate access to the information within and across finding aid systems. In EAD Version 1.0 <index> was a subelement of Adjunct Descriptive Data <add>, which has been deprecated in EAD 2002 (see Appendix B). The new Description Group <descgrp> element, which can group any of the <did>-level elements (except the Description of Subordinate Components <dsc>), may be used to wrap elements where a group heading is desirable. The <descgrp> element can be used to replace <add> when converting finding aids encoded in EAD V1.0 to EAD 2002.

Example

<index xmlns="urn:isl:1-931666-22-9">
  <head>Photographer Index</head>
  <p>Names of photographers and studios--and the cities and states</p>
</index>
in which they operated--are usually noted as they appear on the photographs (usually stamped or written on the verso). Corporate names appear in direct order; personal names in inverted order (i.e., filed by surname). Rectos and versos of photographs were microfilmed to capture information exactly as it appears on the photographs. To locate a specific photographer/studio, a user should consider all possible forms of entry (corporate and personal), browse the index under these forms, identify which LOT(s) contain photographs by that photographer/studio, then browse the relevant LOT on the microfilm to locate specific photographs that bear the markings of the specific photographer/studio.</p>
<indexentry>
  <name>12th Air Force Photo:</name>
  <ref target="LOT13105" actuate="onrequest" show="replace">LOT 13105</ref>
</indexentry>
<indexentry>
  <name>15th Air Force Command:</name>
  <ref target="LOT13105" actuate="onrequest" show="replace">LOT 13105</ref>
</indexentry>
<indexentry>
  <name>324th Service Corp.:</name>
  <ref target="LOT13105" actuate="onrequest" show="replace">LOT 13105</ref>
</indexentry>
<indexentry>
  <name>A.L. Adams Photo Studio--Atlanta, Ga.:</name>
  <ref target="LOT13076" actuate="onrequest" show="replace">LOT 13076</ref>
</indexentry>
<indexentry>
  <name>AAA Agricultural Adjustment Agency by Cooper:</name>
  <ref target="LOT13121" actuate="onrequest" show="replace">LOT 13121</ref>
</indexentry>
</index>

## Content model

<content>
</content>

## Schema Declaration

element index

{ att.EADGlobal_attributes, head?, model blocks*, (( listhead?, indexentry+ ) | index+ ) }
## <indexentry>

**<indexentry>** (Index Entry) A formatting element that pairs an index term with one or more linking elements. Each <indexentry> contains an access element, such as <namegrp> or <subject>; an optional <note> that can divide the entry into subcategories, e.g., "during office" and "family life"; followed by optional Pointer <ptr/>, Pointer Group <ptrgrp>, or Reference <ref> elements. Plain text cannot be used in an <indexentry>. If the <indexentry> subelements are expected to provide access points other than basic keyword retrieval, use controlled vocabulary terms to facilitate access to information within and across finding aid systems, with the SOURCE attribute to indicate which vocabulary provided the term.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

**Contained by** EAD: index entry

**May contain** EAD: corpname famname function genreform geogname indexentry name namegrp occupation persname ptr ptrgrp ref subject subtitle title

**Note** Use the Name Group <namegrp> element to bundle access element entries, e.g., several <famname> and <persname> elements, that share the same <ref>, <ptr/>, or <ptrgrp> element. Use the Pointer Group <ptrgrp> element to bundle several <ref> or <ptr/> links to a single access term. Use the <ptr/> element when no text is needed with the link. Use the <ref> element when text as well as a link are needed.

**Example** <index xmlns="urn:ibn:1-931666-22-9">

## Content model

## Schema Declaration

## <item>

**<item>** (Item) A formatting element used in one of three contexts: as an entry in a simple, random, or ordered <list>; as part of a <defitem> inside a definition list; or as an entry within the <change> element. In the first instance, the <item> can be a number, word, or phrase. In a definition list, which is usually displayed as two columns, a <defitem> pairs a <label> with a corresponding
`<item>` containing text that defines, describes, or explains the terms or other text tagged as the `<label>`. In the `<adheader> <revisiondesc> <change>` element, the `<item>` designates information about a revision to the finding aid and is often paired with a `<date>`.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

**Contained by** EAD: change defitem list

**May contain** EAD: abbr address archref bibref blockquote chronlist corpname date emph expan extptr extref famname function genreform geogname lb linkgrp list name note num occupation origination persname ptr ref repository subject subtitle table title unitdate untitle

**Note** Do not confuse with `<chronitem>`, which designates entries in a Chronology List `<chronlist>`. See also related elements `<list>`, `<defitem>`, and `<change>`.

**Example**
```xml
<adheader xmlns="urn:isbn:1-931666-22-9" langencoding="iso639-2b">
    <eadid>[...]</eadid> ... <revisiondesc>
    <change>
        <date normal="19970505">May 5, 1997</date>
        <item>This electronic finding aid was updated to current markup standards by Sarah Taylor using a perl script. Updates included: adheader, eadid, arrangement of did elements and their labels.</item>
    </change>
    <revisiondesc>
    </eadheader>
```

**Example**
```xml
<list xmlns="urn:isbn:1-931666-22-9" type="deflist">
    <defitem>
        <label>ALS</label>
        <item>Autograph Letter Signed</item>
    </defitem>
    <defitem>
        <label>TLS</label>
        <item>Typewritten Letter Signed</item>
    </defitem>
</list>
```

**Content model**

`<content>`
`</content>`

**Schema Declaration**

element item { att.EADGlobal_attributes, ( text | model.para.content )* }

**<label>**

`<label>` (Label) A formatting element that identifies the term or concept being described, defined, or explained in a Definition List Item `<defitem>`. The `<defitem>` can be thought of as an entry in a `<list>` that is usually displayed in two columns: `<label>` followed by `<item>`. Each list item `<defitem>` contains a term or concept (called a `<label>`) and a definition, description, or explanation of that `<label>` (called an `<item>`).

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

**Contained by** EAD: defitem

**May contain** EAD: abbr archref bibref corpname date emph expan extptr extref famname function genreform geogname lb linkgrp name num occupation origination
yrname ptr ref repository subject subtitle title unitdate unittitle

**Note** Do not confuse with the attribute called LABEL, which identifies the kind of information in an element for public display in the did subelements. See also related elements <list> and <defitem>.

**Example**
```xml
<list xmlns="urn:isl:1-931666-22-9" type="deflist">
  <defitem>
    <label>ALS</label>
    <item>Autograph Letter Signed</item>
  </defitem>
  <defitem>
    <label>TLS</label>
    <item>Typewritten Letter Signed</item>
  </defitem>
</list>
```

**Content model**

```xml
<content>
</content>
```

**Schema Declaration**

element label { att.EADGlobal_attributes, ( text | model.phrase.plus )* }

**<langmaterial>**

<langmaterial> (Language of the Material) A prose statement enumerating the language(s) of the archival materials found in the unit being described.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.labeled (@label)

**Member of** model.did

**Contained by** EAD: archref did

**May contain** EAD: abbr archref bibref emph expan extptr extref language lb linkgrp ptr ref subtitle title

**Note** Language of the material may also be recorded in coded form in the LANGCODE attribute in the <language> subelement using the ISO 639-2b three-letter language codes. Do not confuse with the Language Usage <langusage> element which specifies the language(s) in which the finding aid is written. See also the description for the <language> element.
The <langmaterial> element is comparable to the ISAD(G) data element 3.4.3 and MARC field 546.

**Example**
```xml
<c01 xmlns="urn:isl:1-931666-22-9" level="series">
  <did>
    <unittitle>Correspondence, </unittitle>
    <unitdate type="inclusive">1854-1902. </unitdate>
    <physdesc>4 boxes</physdesc>
    <langmaterial>Correspondence in <language>French, </language>
      <language>German, </language>and
      <language>English.</language>
    </langmaterial>
  </did>
</c01>
```

**Example**
```xml
<eadheader xmlns="urn:isl:1-931666-22-9" langencoding="iso639-2b">[...]</eadheader>
```
```xml
<archdesc xmlns="urn:islbn:1-931666-22-9" level="fonds">
  <did>...</did>
  <langmaterial>Texte <language langcode="ara">arabe</language> et t raduction <language langcode="fre">française</language> par Lacroix fils</langmaterial>
  <did>...</did>
</archdesc>
```

### Example

```xml
<did xmlns="urn:islbn:1-931666-22-9">
  <unitid label="Reference Code">DL 42</unitid>
  <unittitle label="Title">Duchy of Lancaster: Cartularies, Enrolments, Surveys and other Miscellaneous Books</unittitle>
  <unitdate label="Creation Dates" type="inclusive">13th Century -1894</unitdate>
  <langmaterial label="Language(s)"><language langcode="eng">English</language>, <language langcode="fre">French</language> and <language langcode="lat">Latin</language></langmaterial>
  <did>
```

### Schematron

```xml
<langmaterial> COULD contain a <language> element.
  <s:rule context="ead:langmaterial">
    <s:assert role="COULD" test="ead:language">langmaterial COULD have a language sub element</s:assert>
  </s:rule>
```

### Content model

```xml
<content/>
```

### Schema

#### Declaration

```json
{
  att.EADGlobal_attributes,
  att.labeled_attributes,
  (text | model.phrase.basicConfig | language)*
}
```

#### <language>

### <language> (Language)
A subelement of <language> within the <profiledesc> portion of the <eadheader> that specifies the language or communication system in which the finding aid is written. For bilingual or multilingual finding aids, either identify each language in a separate <language> element, or mention only the predominant language. The LANGCODE attribute can be used to provide the three-letter ISO 639-2b code for the language.

**Module** EAD

**Attributes**
* att.EADGlobal (@id, @altrender, @audience, @encodinganalog)
* att.langcode (@langcode)
* att.scriptcode (@scriptcode)

**Contained by** EAD: langmaterial language

**May contain** EAD: emph extptr lb ptr

**Note**
Also a subelement of <langmaterial> within <did>, where it specifies the language of the materials being described. In this instance, the LANGCODE attribute may be used to provide the three-letter ISO 639-2b code which is the equivalent of the MARC 041 field. The SCRIPTCODE attribute may be used to specify the ISO 15924 code for the script in which the language is written.

### Example

```xml
<eadheader xmlns="urn:islbn:1-931666-22-9" langencoding="iso639-2b">
  <eadid>[...]</eadid>
```
```xml
<filedesc>[...]</filedesc>
<profiledesc>
<creation>[...]</creation>
<langusage>Bilingual finding aid written in <language langcode="fre">French</language> and <language langcode="eng">English.</language>
</langusage>
</profiledesc>
</eadheader>
```

### Example

```xml
<c01 xmlns="urn:isbn:1-931666-22-9" level="series">
<did>
<unittitle>Correspondence, </unittitle>
<unitdate type="inclusive">1854-1902.</unitdate>
<physdesc>4 boxes</physdesc>
<langmaterial>Correspondence in <language>French, </language>and <language>German, </language>and <language>English.</language>
</langmaterial>
</did>
</c01>
```

### Schematron

```xml
<language> MUST have a langcode attribute. See also the rule on langcode and ISO 639: ISO639rule
<s:rule context="ead:language">
<s:assert role="MUST" test="@langcode">language MUST have a langcode attribute</s:assert> </s:rule>
```

### Schematron

```xml
<language> MUST have a scriptcode attribute. See also the rule on scriptcode and ISO 15924: ISO15924rule
<s:rule context="ead:language">
<s:assert role="SHOULD" test="@scriptcode">language SHOULD have a scriptcode attribute</s:assert> </s:rule>
```

### Content model

```xml
<content/>
```

### Schema Declaration

#### element language

```json
{
    att.EADGlobal_attributes,
    att.langcode_attributes,
    att.scriptcode_attributes,
    (text | model.phrase.bare)*
}
```

### <langusage>

### <langusage>
Language Usage)
An optional subelement within the <profiledesc> portion of the <eadheader> that provides a statement about languages, sublanguages, and dialects represented in an encoded finding aid. The language(s) in which the finding aid is written can be further specified using the <language> subelement within <langusage>. For bilingual or multilingual finding aids, either identify each language in a separate <language> element, or mention only the predominant language.

#### Module EAD

#### Attributes att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

#### Contained by EAD: profiledesc
**May contain** EAD: abbr archref bibref emph expan extptr extref language lb linkgrp ptr ref subtitle title

**Note** The <langusage> element is modeled on a Text Encoding Initiative (TEI) DTD element.

**Example**
```xml
<eadheader xmlns="urn:isl:1-931666-22-9" langencoding="iso639-2b">
  <eadid>[...]</eadid>
  <filedesc>[...]</filedesc>
  <profiledesc>
    <creation>[...]</creation>
    <langusage>Bilingual finding aid written in <language langcode="fre">French</language> and <language langcode="eng">English.</language>
  </langusage>
  <profiledesc>
  </profiledesc>
</eadheader>
```

**Content model**

```xml
<content>
</content>
```

**Schema Declaration**

element language
```json
{
  att.EADGlobal_attributes,
  (text | model.phrase.basicConfig | language )*
}
```

**<lb/>**

**<lb/>** (Line Break) An empty formatting element that forces text to start on a new line at a point chosen by the author rather than a linewrap algorithm or style sheet. Use only when a line break is needed within an element, for example, within a <titlepage>. Use a style sheet to specify line breaks between elements.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

**Member of** model.render

**Contained by** EAD: abstract addressline archref author bibref bibseries container corpname creation date descrules dimensions edition emph entry event extrefloc famname function genreform geogname head head01 head02 imprint item label langmaterial language langusage legalstatus materialspec name num occupation origination p persname physdesc physfacet physloc publisher ref refloc repository resource runner sponsor subarea subject subtitle title titleproper unitdate unitid unittitle

**May contain** Empty element

**Example**
```xml
<publisher xmlns="urn:isl:1-931666-22-9"> San Joaquin County
  Historical Society and Museum <lb/>
  <extptr actuate="onload" show="embed"
    entityref="sjmlogo"/>
  <lb/> Lodi, California </publisher>
```

**Content model**

```xml
<content>
</content>
```

**Schema**
**Declaration** element lb { att.EADGlobal_attributes, empty }

<legalstatus>

<legalstatus> (Legal Status) The statutorily-defined status of the materials being described in the encoded finding aid, as, for example, defined by the Public Records Act of 1958 in the United Kingdom.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.typed (@type)

**Contained by** EAD: accessrestrict

**May contain** EAD: date emph extptr lb ptr

**Note** The <legalstatus> element is comparable to the ISAD(G) data element 3.4.1 and MARC field 506.

**Example**
```xml
<did xmlns="urn:islbn:1-931666-22-9">
  <unitid label="Reference Code">PREM 8</unitid>
  <unittitle label="Title">Prime Minister's Office: Correspondence and Papers</unittitle>
  <unitdate label="Creation Dates" type="inclusive">1935-1951</unitdate>
</did>
<accessrestrict xmlns="urn:islbn:1-931666-22-9">
  <legalstatus>Public Record(s)</legalstatus>
</accessrestrict>
```

Content model

<content>
</content>

Schema

**Declaration** element legalstatus
```xml
{
  att.EADGlobal_attributes,
  att.typed_attributes,
  (text | model.phrase.bare | date)*
}
```

<linkgrp>

<linkgrp> (Linking Group) A wrapper element that contains two or more linking elements which form an extended link group so as to enable a set of multidirectional, out-of-line links.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.xlink (@label, @href, @type, @title, @from, @to, @role, @actuate, @show, @arcrole, @xpointer, @entityref, @target, @parent)

**Member of** model refs

**Contained by** EAD: abstract bibliography creation descrules dimensions emph entry event item label langmaterial langusage materialspec origination otherfindaid p physdesc physfacet physloc relatedmaterial repository separatedmaterial unitdate unitid unittitle

**May contain** EAD: arc extptrloc extrefloc ptrloc refloc resource

**Example** <relatedmaterial xmlns="urn:islbn:1-931666-22-9">
<p>The Society also has records of other conservation</p>
organizations in Minnesota.</p>
<p>
  <linkgrp linktype="extended">
  <extrefloc href="http://www.someserver.edu/findaids/3270.xml">
    <archref>Issak Walton League of Minnesota</archref>
  </extrefloc>
  <extrefloc href="http://www.someserver.edu/findaids/9248.xml">
    <archref>Minnesota Audubon Council</archref>
  </extrefloc>
  <extrefloc entityref="FBWW">
    <archref>Friends of the Boundary Waters
      <br/>
      Wilderness</archref>
  </extrefloc>
  <extrefloc href="http://www.someserver.edu/findaids/23145.sgm">
    <archref>Minnesota Emergency Conservation
      <br/>
      Committee</archref>
  </extrefloc>
</linkgrp>
</p>
</relatedmaterial>

## Content model

<content>
</content>

## Schema

### Declaration

element linkgrp
{
  att.EADGlobal_attributes,
  att.xlink_attributes,
  model.extended.els+
}

## <list>

<list> (List) A formatting element that contains a series of words or numerals (called <item>s) separated from one another and arranged in a linear, often vertical sequence.

**Module** EAD

**Attributes**
att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

type characterizes the element in some sense, using any convenient classification scheme or typology.

**Derived from** att.typed

**Status** Optional

**Datatype**

**Member of** model.inter.noquote

**Contained by**
EAD: accessrestrict accruals acqinfo altformavail appraisal arrangement bibliography bioghist blockquote controlaccess custodhist daodesc descgrp div dsc dscgroup entry event extrefloc index item note odd originalsloc otherfindaid p phystech prefercite processinfo ref refloc relatedmaterial revisiondesc scopecontent separatedmaterial userestrict

**May contain** EAD: defitem head item listhead

**Note**
The TYPE attribute is used to identify and format the list. The choices are: "simple," "deflist," "marked," and "ordered." In a "simple" list, <item>s are not
numbered or bulleted. In a "deflist" or definition list, each <defitem> pairs a <label> with a corresponding <item> containing the text that defines, describes, or explains the term or other text tagged as the <label>. In a "marked" list, the sequence of the list items is not critical, and a bullet, box, dash, or other character is displayed at the beginning of each <item>. In an "ordered" list, the sequence of the list <item>s is important, and each list <item> is lettered or numbered. See also the related elements <defitem> and <item>.

**Example**

```xml
<bibliography xmlns="urn:isbn:1-931666-22-9">
  <head>Major Works of Archibald MacLeish</head>
  <list type="ordered" numeration="arabic">
    <item>
      <bibref>
        <imprint>
          <date>1924</date>
        </imprint>
        <title render="italic">The Happy Marriage, and Other Poems</title>
        (Boston and New York: Houghton Mifflin. 79 pp.)
      </bibref>
    </item>
    <item>
      <bibref>
        <imprint>
          <date>1925</date>
        </imprint>
        <title render="italic">The Pot of Earth</title>
        (Boston and New York: Houghton Mifflin. 44 pp.)
      </bibref>
    </item>
    ...
  </list>
</bibliography>
```

**Content model**

```xml
<content>
</content>
```

**Schema Declaration**

element list
```json
{
  att.EADGlobal_attributes,
  attribute type { data.enumerated }?,
  head?,
  ( item+ | ( listhead?, defitem+ ) )
}
```

**<listhead>**

**<listhead>** (List Heading) A formatting element that groups headings for columns in a definition, marked, or ordered list, Chronology List <chronlist>, or <index>. The headings are called <head01> and <head02>.

<table><tr><td>Module</td><td>EAD</td></tr><tr><td>Attributes</td><td>att.EADGlobal (@id, @altrender, @audience, @encodinganalog)</td></tr><tr><td>Contained by</td><td>EAD: chronlist index list</td></tr><tr><td>May contain</td><td>EAD: head01 head02</td></tr><tr><td>Example</td><td>&lt;chronlist xmlns="urn:isbn:1-931666-22-9"&gt;</td></tr></table>
```
<head>Publications List</head>
```

```
<listhead>
```

```
<head01>Publication Year</head01>
```

```
<head02>Book Title</head02>
```

```
</listhead>
```

```
<chronitem>[...]</chronitem>
```

```
</chronlist>
```

## Content model

```
<content>
```

```
</content>
```

## Schema

```
Declaration element listhead { att.EADGlobal_attributes, head01?, head02? }
```

## <materialspec>

<materialspec> (Material Specific Details) Data which are unique to a particular class or form of material and which are not assigned to any other element of description. Examples of material specific details include mathematical data, such as scale for cartographic and architectural records, jurisdictional and denominational data for philatelic records, and physical presentation data for music records.

Module EAD

Attributes att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.typed (@type) att.labeled (@label)

Member of model.did

Contained by EAD: archref did materialspec

May contain EAD: abbr archref bibref emph expan extptr extref lb linkgrp materialspec num ptr ref subtitle title

Note The <matspec> element is comparable to MARC fields 254, 255, and 256.

Example
```xml
<c03 xmlns="urn:isbn:1-931666-22-9" level="file">
  <did> . . . <materialspec label="Mathematical Data">
    <materialspec label="Scale:">1:10000</materialspec>
    <materialspec label="Projection:">Universal transverse Mercator projection</materialspec>
  </materialspec>
</did> . . . </c03>
```

## Content model

```
<content>
```

```
</content>
```

## Schema

Declaration element materialspec
```json
{
  att.EADGlobal_attributes,
  att.typed_attributes,
  att.labeled_attributes,
  ( text | model.phrase.basicConfig | num | materialspec )*
}
```

## <name>

<name> (Name) The proper noun or noun phrase designation for an entity that is difficult to tag
more specifically as a `<corpname>`, `<famname>`, `<geogname>`, `<persname>`, or `<title>`. The `<name>` element may be used in place of the more specific access elements when it is not known what kind of name is being described or when a high degree of precision is unnecessary. For example, the `<name>` element might be used in an `<indexentry>` when it is not clear if the name "Bachrach" refers to a person or a photographic corporation.

**Module** EAD

**Attributes**
* att.EADGlobal (`@id`, `@altrender`, `@audience`, `@encodinganalog`) att.access (`@source`, `@rules`, `@authfilenumber`, `@normal`) att.roled (`@role`)

**Member of** model.access

**Contained by**
* EAD: bibref controlaccess entry event extrefloc indexentry item label namegrp origination p physdesc physfacet ref refloc repository unittitle

**May contain** EAD: emph extptr lb ptr

**Note**
All names in a finding aid do not have to be tagged. One option is to tag those names for which access other than basic, undifferentiated keyword retrieval is desired. Use of controlled vocabulary names is recommended to facilitate access to the names within and across finding aid systems. The `<name>` element may be used in text elements such as `<p>`. To indicate a name with major representation in the materials being described, nest `<name>` within the `<controlaccess>` element. The ROLE attribute can be used to specify the relationship(s) of the name to the materials being described, for example, "subject" or "photographer." The SOURCE attribute can be used to specify the vocabulary from which the name has been taken. The RULES attribute can be used to specify the descriptive rules followed when forming the name, such as AACR2R.
See also the related access elements under `<controlaccess>`.
The `<name>` element is comparable to MARC field 720, when it is not from a controlled vocabulary.

**Example**
```xml
<c02 xmlns="urn:isbn:1-931666-22-9" level="file">
  <did>
    <unittitle>
      <name>Bartleby</name>barn purchase files, </unittitle>
      <unitdate>1799.</unitdate>
      <physdesc>
        <extent>3 items, </extent>heavily
        <physfacet>foxed.</physfacet>
      </physdesc>
      <note>
        <p>Items relate to the purchase by Mr. Wigglethorpe from <persname normal="Brookes, Josiah">Jos. Brookes</p>
        <p></p>
      </note>
    </did>
  </did>
</c02>
```

**Content model**
```xml
<content>
</content>
```

**Schema Declaration**
```json
{
  element name
  att.EADGlobal_attributes,
  att.access_attributes,
}
```
att.roled_attributes,
(text | model.phrase.bare)*
}

<namegrp>

<namegrp> (Name Group) A formatting element used in an <indexentry> to group access element entries that share the same <ref>, <ptr>, or <ptrgrp> element. A <note> is available to divide a name or term into subcategories, for example, "during office" and "family life."

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

**Contained by** EAD: indexentry

**May contain** EAD: corpname famname function genre reform geogname name note occupation pseudonym subject subtitle title

**Example**
```xml
<index xmlns="urn:isl:1-931666-22-9">
  <head>Index to Correspondents and Recipients</head>
  <indexentry>
    <corpname>Bach &amp; Bros.</corpname>
    <ref linktype="simple" target="NonC:21-2" show="replace" actuate="onrequest"> (In non correspondence)</ref>
  </indexentry>
  <indexentry>
    <namegrp>
      <corpname>Bacon and Lewis, Ltd.</corpname>
      <persname>Levering, Alexander M.</persname>
      <persname>Windom, Lucious</persname>
    </namegrp>
    <ref linktype="simple" target="Cres:18610408" show="replace" actuate="onrequest"> (1861 Apr. 8, AL S, to W.W., re: inquiry into what to do with unsold flour)</ref>
  </indexentry>
  ...
</index>
```

**Content model**

```xml
<content>
</content>
```

**Schema Declaration**

element namegrp { att.EADGlobal_attributes, ( model.access.title | note )+ }

<note>

<note> (Note) A generic element that provides a short statement explaining the text, indicating the basis for an assertion, or citing the source of a quotation or other information. Used both for general comments and as an annotation for the text in a finding aid. Not used when more specific content designation elements are appropriate, e.g., <abstract>, <altformavail>, <archref>, or <scopecontent>. Do not confuse with Other Descriptive Data <odd> element, which is used within <archdesc> and <c> to designate information that is more than a short comment in a <note>.

**Module** EAD

**Attributes**
att.EADGlobal (@id, @altrender, @audience, @encodinganalog)
att.typed (@type)
att.labeled (@label)

show

Status

Datatype

Optional
Legal values are: embed

new

actuate

Status Optional

Datatype

Legal values are: onload

onrequest

**Member of** model desc full model did model inter no quote
**Contained by** EAD: access restrict accruals acq info alt form avail appraisal arch desc arch desc grp
arch ref arrangement bibliography bioghist blockquote c c01 c02 c03 c04 c05 c06
c07 c08 c09 c10 c11 c12 control access custod hist daodesc desc grp did div dsc
dsc group entry event ext ref loc index item name grp note note test mt odd original s loc
other find aid p phystech prefercite process info ref ref loc related material
scope content separated material user restrict

**May contain** EAD: address blockquote chronlist list note p table

**Note** The placement of a <note> is dependent on the design of the document and the purpose of the <note>. A <note> may appear at the end of the text as endnotes, at the foot of a section as footnotes or embedded within the text. One or more <note> elements may be grouped in a <note test> element in the <file desc> portion of the <ead header>. The ACTUATE and SHOW attributes can be used to mask a <note> from display until it is requested by a finding aid user. The <note> element is comparable to ISAD(G) data element 3.6.1 and MARC field 500.

**Example**
```xml
<archdesc xmlns="urn:isbn:1-931666-22-9" level="collection">
  <did>...</did>
  <repository label="repository">
    <encoding analog="852">
      <corpname>Library of Congress, <subarea>Prints and</corpname>
      <subarea>Photographs Division, </subarea>
    </corpname>
    <location>Washington, D.C. 20540</location>
  </repository>
  <note>
    <p>For information about Prints and Photographs Division collections and services, see the Prints and Photographs Division's Reading Room Home Page:</p>
    <extptr actuate="onrequest">
      <href="http://www.loc.gov/rr/print.htm" show="new"/>
    </extptr>
  </note>
</archdesc>
```

**Content model**

`<content>`

`</content>`

**Schema Declaration**

element note
{
  att.EADGlobal_attributes,
  att.typed_attributes,
  att.labeled_attributes,
  attribute show { "embed" | "new" }?,
attribute actuate { "onload" | "onrequest" }?,
model_blocks+
}

<notestmt>

<notestmt> (Note Statement) An optional subelement within the <filedesc> portion of the <eadheader> that groups <note> elements, each of which contains a single piece of descriptive information about the finding aid. These <note>s are similar to the "general notes" in traditional bibliographic descriptions.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

**Contained by** EAD: filedesc

**May contain** EAD: note

**Note** The <notestmt> element is modeled on a header element found in the Text Encoding Initiative (TEI).

**Example** In the California Digital Library, access points are put in the <eadheader> for system use in the resource directory. These same access points are also provided in <controlaccess> for public use.

<notestmt xmlns="urn:isl:1-931666-22-9">

<note>

<p>

<subject source="cdl">Arts and Humanities--Performing Arts--Dance</subject>

<subject source="cdl">Arts and Humanities--Performing Arts--Theater</subject>

</p>

</note>

</notestmt>

**Content model**

<content>

</content>

**Schema Declaration**

element notestmt { att.EADGlobal_attributes, note+ }

<num>

<num> (Number) A generic element for numeric information in any form. The <num> element is used only when it is necessary to display a number in a special way, or to identify it with a TYPE attribute. For example, an accession number in the <acqinfo> element might be designated as <num type="accession">. A publication number might be designated as <publicationstmt> ... <num>no. 42</num> ...

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.typed (@type)

**Member of** model.data

**Contained by** EAD: bibref bibseries entry event extrefloc item label materialspec p publicationstmt ref refloc seriesstmt subtitle title titlepage titleproper unittitle

**May contain** EAD: emph extptr lb ptr

**Note** Do not confuse with <container>, <unitid>, or <eadid>, which may also consist of numeric information.
**Example**
```xml
<filedesc xmlns="urn:isl:1-931666-22-9">
    <titlestmt>[...]</titlestmt>
    <seriesstmt>
        <titleproper encodinganalog="440$a">Archival Inventories and Guides of the World; </titleproper>
        <num encodinganalog="440$v">no. 148</num>
    </seriesstmt>
</filedesc>

Example
<acqinfo xmlns="urn:isl:1-931666-22-9">
    <p>The collection (Donor No. <num type="donor">8338</num>) was donated by <persname role="donor">Vonda Thomas</p>
    <p>and <persname role="donor">Francine Farrow</p>
    <p>in March 1995.</p>
</acqinfo>
```

## Content model

```xml
<content>
</content>
```

## Schema Declaration

element num
{
    att.EADGlobal_attributes,
    att.typed_attributes,
    (text | model.phrase.bare)*
}

## <occupation>

<occupation> (Occupation) A term identifying a type of work, profession, trade, business, or avocation significantly reflected in the materials being described.

Module EAD

Attributes att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.access (@source, @rules, @authfilenumber, @normal)

Member of model.access

Contained by EAD: controlaccess entry event extrefloc indexentry item label namegrp p physdesc physfacet ref refloc unittitle

May contain EAD: emph extptr lb ptr

Note

All occupations in a finding aid do not have to be tagged. One option is to tag those occupations for which access other than basic, undifferentiated keyword retrieval is desired. Use of controlled vocabulary forms is recommended to facilitate access to occupations within and across finding aid systems. The <occupation> element may be used in text elements such as <p>. To indicate an occupation with major representation in the described materials, nest <occupation> within the <controlaccess> element. Use the SOURCE attribute to specify the vocabulary from which the term has been taken. The NORMAL attribute can be used to provide the authority form of a term that has been encoded with <occupation> in narrative text, e.g., within a paragraph. The AUTHFILENUMBER attribute can be used to identify a link to an authority file record that has more information about the occupation.

Do not confuse with <function>, which designates the spheres of activities and processes that generated the described materials, e.g., collecting taxes or entertaining.
Do not confuse with the ROLE attribute available on the various name elements, e.g., <corpname>, <persname>, <famname>, etc., which may be used to specify the relationship of a name to the described materials, e.g., "compiler," "creator," "collector," or "subject."

See also the related access terms under <controlaccess>.

The <occupation> element is comparable to MARC field 656.

### Example

<controlaccess xmlns="urn:isl:1-931666-22-9">

<head>Selected Search Terms</head>

<controlaccess>

<head>Occupations:</head>

<occupation encodinganalog="656">Dramatists</occupation>

<occupation encodinganalog="656">Librarians of
Congress</occupation>

<occupation encodinganalog="656">Poets</occupation>

<occupation encodinganalog="656">Public
officers</occupation>

</controlaccess>

</controlaccess>

### Content model

<content>

</content>

### Schema Declaration

element occupation

{
  att.EADGlobal_attributes,
  att.access_attributes,
  (text | model.phrase.bare)*
}

## <odd>

### <odd> (Other Descriptive Data)
An element for information about the described materials that is not easily incorporated into one of the other named elements within <archdesc> and <c>.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.typed (@type)

**Member of** model desc base

**Contained by** EAD: archdesc archdescgrp c c01 c02 c03 c04 c05 c06 c07 c08 c09 c10 c11 c12 descgrp odd

**May contain** EAD: address blockquote chronlist dao daogrp head list note odd p table

**Note** When converting finding aids to an ideal EAD markup, some shifting of text or addition of data may be necessary to conform to the DTD's sequencing of elements and the consignment of certain elements to specific settings. The <odd> element helps to minimize conversion difficulties by designating, as "other," information that does not fit easily into one of EAD's more distinct categories. Some situations in which <odd> may be used are when the information does not correspond to another element's definition; when the information is of such mixed content as to make a single classification difficult; and when shifting the information to permit more specific content designation would be too costly or burdensome for the finding aid encoder. The first situation may occur especially when additional narrative description is required beyond
what is included in the <bioghist> and <scopecontent> elements, such as when
the finding aid is describing a computer file. Applying the *type* and
*encoding analog* attributes may help provide additional content specification in
situations where the unspecified `<odd>` is used.

Despite its wide availability under <archdesc> and <c>, the <odd> element should
be used with restraint and only after carefully considering the consequences that
unspecified content designation poses for searching, retrieving, and displaying
information in a networked environment.

The <odd> element is comparable to ISAD(G) data element 3.6.1 and MARC field 500.

## Example

Note: The Public Record Office of the United Kingdom uses a 7 level system of intellectual units devised specifically for that repository. In that system "division" is the equivalent of "subfonds" and "class" is the equivalent of "series."

<c01 xmlns="urn:isl:1-931666-22-9" level="otherlevel"
otherlevel="division">

<did>

<unittitle>Records of the Industrial Division</unittitle>

<origination>

<corpname>Department of Economic Affairs, Industrial
Group; </corpname>

<corpname>Department of Economic Affairs, Industrial
Division; </corpname>

<corpname>Department of Economic Affairs, Industrial
Policy; Division </corpname>

<corpname>Department of Economic Affairs, Industrial
Prices and Incomes Department; </corpname>

</origination>

<unitdate>1949-1969</unitdate>

<physdesc>

<extent>2</extent>

<genreform>classes</genreform>

<physdesc>

<did>

<scopecontent>[...]</scopecontent>

<bioghist>[...]</bioghist>

<controlaccess>[...]</controlaccess>

<odd>

<list type="simple">

<item>Department of Economic Affairs: Industrial Policy

Group: Registered Files (1-IG and 2-IG Series) <ref actuate="onrequest" target="ew26" et="ew26" show="new">EW 26</ref>

</item>

<item>Department of Economic Affairs: Industrial
Division and Industrial Policy Division: Registered
Files (IA Series) <ref actuate="onrequest" target="ew27" show="new">EW 27</ref>

</item>

</list>

</odd>

</c01>
## Content model

`<content>`

`</content>`

## Schema Declaration

element odd

{
  att.EADGlobal_attributes,
  att.typed_attributes,
  head?,
  ( model_blocks | dao | daogrp | odd )+
}

## <originalsloc>

`<originalsloc>` (Location of Originals) Information about the existence, location, availability, and/or the destruction of originals where the unit described consists of copies.

**Module** EAD

**Attributes**
att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.typed (@type)

**Member of** model desc base

**Contained by**
EAD: archdesc archdescgrp c c01 c02 c03 c04 c05 c06 c07 c08 c09 c10 c11 c12 daogrp originalsloc

**May contain**
EAD: address blockquote chronlist head list note originalsloc p table

**Note**
Do not confuse `<originalsloc>` with Alternative Form Available `<altformavail>`, which is used to encode information about copies of the material being described. The `<originalsloc>` element is comparable to ISAD(G) data element 3.5.1 and MARC field 535.

**Example**
`<c01 xmlns="urn:isl:1-931666-22-9" level="file">`

`<did>`
`<unittitle>Dream diary, </unittitle>`
`<unitdate normal="1947/1948">1947-48</unitdate>`
`</did>`

`<originalsloc>`
`<p>File contains photocopies of original still held by the donor.</p>`
`</originalsloc>`

`</c01>`

**Example**
`<c01 xmlns="urn:isl:1-931666-22-9" level="series">`

`<did>[...]</did>`
`<originalsloc>`
`<p>Originals destroyed after microfilming, 1981.</p>`
`</originalsloc>`

`</c01>`

**Example**
`<c03 xmlns="urn:isl:1-931666-22-9" level="file">`

`<did>[...]</did>`
`<originalsloc>`
`<p>Original glass plate negatives are held by the Bailly family, Lunenburg, Nova Scotia.</p>`
`</originalsloc>`

`</c03>`

**Schematron**
If the element `<originalsloc>` is not empty, you COULD try to identify if copies are
present in the EHRI portal and make a link between the two descriptions.

`<s:rule context="ead:originalsloc/ead:p"> <s:assert role="COULD" test="not(normalize-space(.))">If the element originalsloc is not empty, you COULD try to identify if copies are present in the EHRI portal and make a link between the two descriptions.</s:assert> </s:rule>`

## Content model

`<content/>`

## Schema

### Declaration

element originalsloc

{ att.EADGlobal_attributes, att.typed_attributes, head?, (model blocks | originalsloc) + }

## <origination>

`<origination>` (Origination) Information about the individual or organization responsible for the creation, accumulation, or assembly of the described materials before their incorporation into an archival repository. The `<origination>` element may be used to indicate such agents as correspondents, records creators, collectors, and dealers. Using the `LABEL` attribute may help identify for a finding aid reader the role of the originator, e.g., "creator," "collector," or "photographer." It is also possible to set the `ROLE` attribute on the name elements that are available within `<origination>`, i.e., `<corpname>`, `<famname>`, `<name>`, and `<persname>`.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.labeled (@label)

**Member of** model.data model did

**Contained by** EAD: archref did entry event extrefloc item label p ref refloc

**May contain** EAD: abbr archref bibref corpname emph expan extptr extref famname lb linkgrp name **persname** ptr ref **title**

**Note** The `<origination>` element is comparable to `ISAD(G)` data element `3.2.1` and `MARC` fields `100`, `110`, `700`, and `710`.

**Example**
```xml
<archdesc xmlns="urn:isl:1-931666-22-9" level="collection">
  <did>
    <origination label="Creator:">
      <persname encodinganalog="100"
                  normal="Frisell, Toni" role="photographer">Toni
                    Frisell</persname>
    </origination>
  </did>
</archdesc>
```

**Example**
```xml
<archdesc xmlns="urn:isl:1-931666-22-9" type="inventory" level="subgrp">
  <did>
    <head>Overview of the Records</head>
    <repository label="Repository:">
      <corpname>Minnesota
        Historical Society</corpname>
    </repository>
    <origination label="Creator:">
```
<corpname>Minnesota. Game and
Fish Department</corpname>
</origination>
<unittitle label="Title:">Game laws violation records, </unittitle>
<unitdate label="Dates:">1908-1928</unitdate>
<abstract label="Abstract:">Records of prosecutions for and
seizures of property resulting from violation of the
state's hunting and fishing laws. </abstract>
<physdesc label="Quantity:"> 2.25 cu. ft. (7 v. and 1 folder
in 3 boxes) </physdesc>
<physloc label="Location:"> See Detailed Description section
for box location </physloc>
</did>
</archdesc>

## Content model

<content>
</content>

## Schema

**Declaration** element origination
{
  att.EADGlobal_attributes,
  att.labeled_attributes,
  (text | model.phrase.basicConfig | corpname | famname | name | persname)*
}

## <otherfindaid>

**<otherfindaid>** (Other Finding Aid) Information about additional or alternative guides to the described material, such as card files, dealers' inventories, or lists generated by the creator or compiler of the materials. It is used to indicate the existence of additional finding aids; it is not designed to encode the content of those guides.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

**Member of** model desc base

**Contained by** EAD: archdesc archdescgrp c c01 c02 c03 c04 c05 c06 c07 c08 c09 c10 c11 c12 descgrp otherfindaid

**May contain** EAD: address archref bibref blockquote chronlist extref head linkgrp list note otherfindaid p ref subtitle table title

**Note**
Do not confuse with <fileplan>, which designates information about a particular type of access tool, known as a file plan, which explains the classification scheme used by the parties originally responsible for creating or compiling the described materials. The <archref> element may be used to give a formal citation to the other finding aid or to link to an online version of it.
In EAD Version 1.0 <otherfindaid> was a subelement of Adjunct Descriptive Data <add>, which has been deprecated in EAD 2002 (see Appendix B). The new Description Group <descgrp> element, which can group any of the <did>-level elements (except the Description of Subordinate Components <dsc>), may be used to wrap elements where a group heading is desirable. The <descgrp> element can be used to replace <add> when converting finding aids encoded in EAD V1.0 to EAD 2002.

The <otherfindaid> element is comparable to ISAD(G) data element 3.4.5.
### Example

```xml
<otherfindaid xmlns="urn:isl:1-931666-22-9">
  <bibref>The Society has published an expanded guide to this
    collection: <title>Guide to the Records of the American
      Crystal Sugar Company.</title>
      <p>Compiled by <persname role="author">David Carmichael;</p>
      <p>assisted by <persname role="author">Lydia A. Lucas</p>
      <p>and <persname role="author">Marion E. Matters.</p>
      <p>St. Paul. Division of Archives and Manuscripts.</p>
      <p>Minnesota Historical Society. 1985.</p>
      <p></bibref>
    </collection>
  </otherfindaid>
</otherfindaid>
```

### Content model

```xml
<content>
</content>
```

### Schema

#### Declaration

```xml
element otherfindaid
{
  att.EADGlobal_attributes,
  head?,
  (model_blocks | model Refs | otherfindaid) +
}
```

### <p>

#### <p> (Paragraph)
One or more sentences that form a logical prose passage. A paragraph may be a subdivision of a larger composition, or it may exist alone. It is usually typographically distinct: A line space is often left blank before it; the text begins on a new line; and the first letter of the first word is often indented, enlarged, or both. The <p> element is an important textual feature, which may be used inside of more than thirty other elements. The content model of a <p> provides access to thirty-three other elements, including reference and linking elements, formatting elements, controlled access elements, and some of the Descriptive Identification <did> subelements.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

**Member of** model_blocks

**Contained by** EAD: accessrestrict accruals acqinfo altformavail appraisal arrangement bibliography bioghist blockquote controlaccess custodhist daodesc descgrp div dsc dscgroup editionstmt index note odd originalsloc otherfindaid phystech prefercite processinfo publicationstmt relatedmaterial scopecontent separatedmaterial seriesstmt userestrict

**May contain** EAD: abbr address archref bibref blockquote chronlist corpname date emph expan extptr extref famname function genreform geogname lb linkgrp list name note num occupation origination persname ptr ref repository subject subtitle table title unitdate unittitle

### Example

```xml
<bioghist xmlns="urn:isl:1-931666-22-9">
  <head>Biographical Sketch</head>
  <p>John Ferguson Godfrey was born in Toronto on December 19,
     1942. He received a B.A. (Hons.) from Trinity College,
     University of Toronto, in 1965, a M.Phil. degree from
     Balliol College, Oxford University, England, in 1967, and a
     D.Phil. degree from St. Anthony's College, Oxford
     University, in 1975. He holds the title of Doctor of Sacred
     letters (honoris causa), Trinity College (1987).</p>
```
<p>Mr. Godfrey taught in the Department of History of Dalhousie University, Halifax, first as Assistant Professor (1970-1975), and then as Associate Professor (1980-1987). At

<corpname>King's College University, Halifax</corpname>
he held the position of Assistant Professor (1975-1976),
before becoming President and Vice-Chancellor
(1977-1987).</p>

## Content model

## Schema

Declaration element p { att.EADGlobal_attributes, ( text | model.para.content )* }

## <persname>

<persname> (Personal Name) The proper noun designation for an individual, including any or all of that individual's forenames, surnames, honorific titles, and added names.

Module EAD

Attributes
att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.access (@source, @rules, @authfilenumber, @normal) att.roled (@role)

Member of model.access

Contained by
EAD: bibref controlaccess entry event extrefloc indexentry item label namegrp origination p physdesc physfacet ref refloc unittitle

May contain EAD: emph extptr lb ptr

Note

All names in a finding aid do not have to be tagged. One option is to tag those names for which access other than basic, undifferentiated keyword retrieval is desired. Use of controlled vocabulary forms is recommended to facilitate access to names within and across finding aid systems. The <persname> element may be used in text elements such as <p>. To indicate a personal name with major representation in the materials being described, nest <persname> within the <controlaccess> element. The ROLE attribute can be used to specify the relationship(s) of the name to the materials being described, for example, "compiler," "creator," "collector," or "subject." The NORMAL attribute can be used to provide the authority form of a name that has been encoded with <persname> in narrative text, e.g., within a paragraph. Use the SOURCE attribute to specify the vocabulary from which the name has been taken. The AUTHFILENUMBER attribute can be used to identify a link to an authority file record that has more information about the name or cross references for alternative forms of the name and related names. The RULES attribute can be used to specify the descriptive rules followed when forming the name, such as AACR2R.

See also related elements <controlaccess>, <corpname>, <fname>, and <name>.

The <persname> element is comparable to MARC fields 100, 600, and 700.

Example
include none of his personal papers. The collection
documents Perlman's career as an economist and author at
<corpname normal="Cornell University">Cornell,</corpname>
<corpname normal="Johns Hopkins University">Johns
Hopkins,</corpname> and the <corpname>University of
Pittsburgh</corpname> and reflects his interest in work
arbitration, trade unions, and the economics of public
health. Among correspondents are many noted economists,
including <persname normal="Abramovitz, Moses">Moses Abramovitz,</persname
ame>
<persname normal="Shubik, Martin">Martin Shubik,</p>
<persname normal="Bronfenbrenner, Martin">Martin
Bronfenbrenner.</p>
<persname normal="Shubik, Martin">Martin Shubik,</p>
<persname normal="Bronfenbrenner, Martin">Martin
Bronfenbrenner.</p>
While many of the letters
are personal in nature, others contain considerable
information about Perlman's work, particularly in the years
around the publication of his works <title render="italic">Judges in Industry: A St
udy of Labor Arbitration in
Australia</title>
<date type="publication">(1954)</date> and <title render="italic">Spatial, Regio
nal, and Population
Economics: Essays in Honor of Edgar M. Hoover</title>
<date type="publication">(1972).</date> Additional
correspondence relates to the publication of the <title render="italic">Journal of E
conomic
Literature.</title>
</p>
</scopecontent>

Example

<controlaccess xmlns="urn:isbn:1-931666-22-9">
  <head>Subjects:</head>
  <persname encodinganalog="600$a"
    source="Icnaf">Reimann, Lewis
    Charles, 1909-1978.</persname>
  <persname encodinganalog="600$a"
    source="Icnaf">Evans,
    Thomas.</persname>
  <persname encodinganalog="600$a"
    source="Icnaf">Trippe, Matthew
    J., 1915-1967.</persname>
  <persname encodinganalog="600$a"
    source="Icnaf">Elliot,
    Raymond.</persname>
</controlaccess>

Schematron

In the access points, Person names SHOULD be structured like this : Family
name, given name
<s:rule context="ead:controlaccess/ead:persname"> <s:assert role="SHOULD"
test="[0-9a-zA-Z]+([0-9a-zA-Z]+)*">In the access points, Person names
SHOULD be structured like this : Family name, given name</s:assert> </s:rule>

Content model

<content/>

Schema

Declaration

element <persname>
```json
{
    att.EADGlobal_attributes,
    att.access_attributes,
    att.roled_attributes,
    (text | model.phrase.bare)*
}
```

## <physdesc>

### <physdesc>
(Physical Description) A wrapper element for bundling information about the appearance or construction of the described materials, such as their dimensions, a count of their quantity or statement about the space they occupy, and terms describing their genre, form, or function, as well as any other aspects of their appearance, such as color, substance, style, and technique or method of creation. The information may be presented as plain text, or it may be divided into the <dimension>, <extent>, <genreform>, and <physfacet> subelements.

**Module** EAD

**Attributes**
att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.labeled (@label) att.access (authfilenumber, normal, @source, @rules)

**Member of** model did

**Contained by** EAD: archref did

**May contain**
EAD: abbr archref bibref corpname date dimensions emph expan extent extptr extref famname function genreform geogname lb linkgrp name occupation pseudom name ptr ref subject subtitle title

**Note**
The <physdesc> element is comparable to ISAD(G) data element 3.1.5 and MARC field 300.

**Example**
```xml
<c01 xmlns="urn:isbn:1-931666-22-9" level="series">
    <did>
        <unittitle>Seizure Records, </unittitle>
        <unitdate>December 1908-January 1928.</unitdate>
        <physdesc>4 volumes and 1 folder.</physdesc>
    </did>
    <c01>
```

**Example**
```xml
<c xmlns="urn:isbn:1-931666-22-9" level="subseries">
    <did>
        <unittitle>Documentary Movies, </unittitle>
        <unitdate type="inclusive">1952-1964</unitdate>
        <physdesc>
            <extent>2.5 linear ft.</extent>
        </physdesc>
    </did>
    <c>
```

**Schematron**
In the <did> element, <physdesc> SHOULD come with a non-empty <extent> <s:rule context="ead:physdesc"> <s:assert role="SHOULD" test="normalize-space(ead:extent[1])">a did SHOULD have a non-empty physdesc-extent, according to 17.3</s:assert> </s:rule>

### Content model

`<content/>`

### Schema

**Declaration**
element physdesc
```json
{
    att.EADGlobal_attributes,
```
att.labeled_attributes,
att.access_attribute.sourceforge,
att.access_attribute_rules,
(
  text
  | model.phrase.basicConfig
  | dimensions
  | physfacet
  | extent
  | date
  | model.access
)*
)

<physfacet>

<physfacet> (Physical Facet) A <physdesc> subelement for information about an aspect of the appearance of the described materials, such as their color, style, marks, substances, materials, or techniques and methods of creation.

<table><tr><td><strong>Module</strong></td><td>EAD</td></tr><tr><td><strong>Attributes</strong></td><td>att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.labeled (@label) att.typed (@type) att.access (authfilenumber, normal, @source, @rules) unit</td></tr><tr><td></td><td><strong>Status</strong> Optional</td></tr><tr><td></td><td><strong>Datatype</strong></td></tr></table>

**Contained by** EAD: physdesc

**May contain** EAD: abbr archref bibref corpname date emph expan extptr extref famname function genreform geogname lb linkgrp name occupation persname ptr ref subject subtitle title

**Note** It is used especially to note aspects of appearance that affect or limit use of the materials. It generally should not be used for aspects of physical description that are covered more directly by the <extent>, <dimensions>, and <genreform> elements, although use of <genreform> may be appropriate for further specification within some <physfacet> instances. The TYPE attribute may be used to specify which aspect of the physical appearance is being designated, e.g., <physfacet type="color">red</physfacet>

**Example**
```xml
<physdesc xmlns="urn:isl:1-931666-22-9">
  <extent>3</extent>
  <genreform>daguerreotypes, </genreform>
  <physfacet>hand colored</physfacet>
</physdesc>
```

**Example**
```xml
<physdesc xmlns="urn:isl:1-931666-22-9">
  <physfacet type="material">Paper</physfacet>
  <physfacet type="ruling">Ruled in red ink</physfacet>
  <physfacet type="watermarks">Briquet 1234</physfacet>
  <physfacet type="binding">Bound in 19th century red leather</physfacet>
</physdesc>
```

**Content model**

```xml
<content>
</content>
```

**Schema**
**Declaration**

```json
{
    element physfacet
    {
        att.EADGlobal_attributes,
        att.labeled_attributes,
        att.typed_attributes,
        att.access_attribute.sourceforge,
        att.access_attribute_rules,
        attribute unit { text }?,
        ( text | model.phrase.basicConfig | model.access | date )*
    }
}
```

## <physloc>

<physloc> (Physical Location) Information identifying the place where the described materials are stored, such as the name or number of the building, room, stack, shelf, or other tangible area.

**Module** EAD
**Attributes**
att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.labeled (@label) att.typed (@type)
parent

**Status** Optional
**Datatype**

**Member of** model did
**Contained by** EAD: archref did
**May contain** EAD: abbr archref bibref emph expan extptr extref lb linkgrp ptr ref subtitle title
**Note** Do not confuse with <container>, which is used to identify the cartons, boxes, reels, folders, and other storage devices used to hold the described materials.
Also do not confuse with <repository>, which is used to identify the institution or agency responsible for providing intellectual access to the described materials. Like all Descriptive Identification <did> subelements, the <physloc> element has a LABEL attribute which may be used to provide a readily understandable heading for the element's content. The TYPE attribute may also be used to identify the nature of the storage location. For security reasons, the AUDIENCE attribute value may be set to "internal" to shield public access to storage location information.

The <physloc> element is comparable to MARC field 852.

**Example**
```xml
<archdesc xmlns="urn:isl:1-931666-22-9" type="inventory" level="subgrp">
    <did>
        <head>Overview of the Records</head>
        <repository label="Repository:">
            <corpname>Minnesota
                Historical Society</corpname>
        </repository>
        <origination label="Creator:">Minnesota. Game and Fish
                Department</origination>
        <unittitle label="Title:">Game laws violation records</unittitle>
        <unitdate label="Dates:">1908-1928</unitdate>
        <abstract label="Abstract:">Records of prosecutions for and
                seizures of property resulting from violation of the
                state's hunting and fishing laws.</abstract>
        <physdesc label="Quantity:"> 2.25 cu. ft. (7 v. and 1 folder
                in 3 boxes)</physdesc>
        <physloc label="Location:"> See Detailed Description section
                for box location</physloc>
    </did>
</archdesc>
```
```xml
</did>
</archdesc>
```

### Example

```xml
<c02 xmlns="urn:isl:1-931666-22-9" level="file">
  <did>
    <physloc>112.1.8.1B-2</physloc>
    <container type="box">2</container>
    <unititle>
      <unitdate type="inclusive">December 1908-July 1917</unitdate>
    </unittitle>
  </did>
</c02>
```

### Content model

```xml
<content>
</content>
```

### Schema

#### Declaration

```xml
element physloc {
    att.EADGlobal_attributes,
    att.labeled_attributes,
    att.typed_attributes,
    attribute parent { xsd:IDREFS }?,
    ( text | model.phrase.basicConfig )*
}
```

### <phystech>

### <phystech>
(Physical Characteristics and Technical Requirements) A description of important physical conditions or characteristics that affect the storage, preservation, or use of the materials described. This includes details of their physical composition or the need for particular hardware or software to preserve or access the materials.

**Module** EAD

**Attributes**
att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.typed (@type)

**Member of** model desc base

**Contained by**
EAD: archdesc archdescgrp c c01 c02 c03 c04 c05 c06 c07 c08 c09 c10 c11 c12 descgrp phystech

**May contain**
EAD: address blockquote chronlist head list note p phystech table

**Note**
The <phystech> element is comparable to ISAD(G) data element 3.4.4 and MARC fields 340 and 538.

**Example**
```xml
<c04 xmlns="urn:isl:1-931666-22-9" level="item">
  <did>[...]</did>
  <phystech>
    <p>Some oxydization of the aluminum layer.</p>
  </phystech>
</c04>
```

**Example**
```xml
<c02 xmlns="urn:isl:1-931666-22-9" level="subseries">
  <did>[...]</did>
  <phystech>
    <head>System Requirements</head>
    <p>48K RAM; Apple Disk II with controller; colour</p>
  </phystech>
</c02>
```
```
  monitor</p>
</phystech>
</c02>
```

## Content model

```
<content>
</content>
```

## Schema Declaration

```
element phystech
{
  att.EADGlobal_attributes,
  att.typed_attributes,
  head?,
  ( model_blocks | phystech )+
}
```

## <prefercite>

**<prefercite>** (Preferred Citation) Information about how users should identify the described materials when referring to them in published credits. Generally the repository or agent responsible for providing intellectual access to the materials will supply users with a recommended wording or prescribed format for structuring references to the described materials in bibliographies, footnotes, screen credits, etc.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

**Member of** model desc base

**Contained by** EAD: archdesc archdescgrp c c01 c02 c03 c04 c05 c06 c07 c08 c09 c10 c11 c12 descgrp prefercite

**May contain** EAD: address blockquote chronlist head list note p prefercite table

**Note** Do not confuse with <archref> or <bibref> which are used to cite and/or link to materials other than those described in the finding aid. In EAD Version 1.0 <prefercite> was a subelement of Administrative Information <admininfo>, which has been deprecated in EAD 2002 (see Appendix B). The new Description Group <descgrp> element, which can group any of the <did>-level elements (except the Description of Subordinate Components <dsc>), may be used to wrap elements where a group heading is desirable. The <descgrp> element can be used to replace <admininfo> where it has been used as a wrapper when converting finding aids encoded in EAD V1.0 to EAD 2002.

The <prefercite> element is comparable to MARC field 524.

**Example**
```xml
<prefercite xmlns="urn:isl:1-931666-22-9">
  <head>Preferred Citation</head>
  <p>[Identification of item], Arequipa Sanatorium Records, BANC MSS 92/894c, The Bancroft Library, University of California, Berkeley.</p>
</prefercite>
```

**Example**
```xml
<prefercite xmlns="urn:isl:1-931666-22-9">
  <p>item, folder title, box number, Charles Thomas, Jr. Papers, Bentley Historical Library, University of Michigan.</p>
</prefercite>
```

## Content model

```
  <content>
</content>
```
## Schema

**Declaration** element prefercite
{
  att.EADGlobal_attributes,
  head?,
  (model_blocks | prefercite) +
}

## <processinfo>

<processinfo> (Processing Information) Information about accessioning, arranging, describing, preserving, storing, or otherwise preparing the described materials for research use. Specific aspects of each of these activities may be encoded separately within other elements, such as <acqinfo>, <arrangement>, <physloc>, etc.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.typed (@type)

**Member of** model desc base

**Contained by** EAD: archdesc archdescgrp c c01 c02 c03 c04 c05 c06 c07 c08 c09 c10 c11 c12 descgrp processinfo

**May contain** EAD: address blockquote chronlist head list note p processinfo table

**Note** In EAD Version 1.0 <processinfo> was a subelement of Administrative Information <admininfo>, which has been deprecated in EAD 2002 (see Appendix B). The new Description Group <descgrp> element, which can group any of the <did>-level elements (except the Description of Subordinate Components <dsc>), may be used to wrap elements where a group heading is desirable. The <descgrp> element can be used to replace <admininfo> where it has been used as a wrapper when converting finding aids encoded in EAD V1.0 to EAD 2002. The <processinfo> element is comparable to ISAD(G) data element 3.7.1 and MARC field 583. A <date> within a <processinfo><p> element is comparable to ISAD(G) data element 3.7.3.

**Example**
<processinfo xmlns="urn:isbn:1-931666-22-9">
  <head>Processing Information:</head>
  <p>These records were organized and cataloged in <date>1977</date> by Lydia Lucas.</p>
</processinfo>

### Content model

<content>
</content>

## Schema

**Declaration** element processinfo
{
  att.EADGlobal_attributes,
  att.typed_attributes,
  head?,
  (model_blocks | processinfo) +
}
`<profiledesc>`

`<profiledesc>` (Profile Description) An optional subelement of the `<adheader>` that bundles information about the creation of the encoded version of the finding aid, including the name of the agent, place, and date of encoding. The `<profiledesc>` element also designates the predominant and minor languages used in the finding aid.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

**Contained by** EAD: adheader

**May contain** EAD: creation descrules language

**Note**
Do not confuse with `<filedesc>`, which bundles such bibliographic information as the title, author, publisher, edition, and publishing series of the finding aid. For newer finding aids, the author and encoder may be the same person or institution, but for most older finding aids, someone other than the author will be converting and encoding the document. The encoder should be listed in the `<creation>` subelement of `<profiledesc>`, while the author should be identified in the `<titlestmt>` subelement of `<filedesc>`.

Within `<profiledesc>` the Descriptive Rules `<descrules>` element can be used to specify the descriptive code or guidelines followed in creating the finding aid.

**Example**

```xml
<adheader xmlns="urn:isl:1-931666-22-9" audience="internal"
langencoding="iso639-2b">
<eadid>[...]</eadid>
<filedesc>[...]</filedesc>
<profiledesc>
<creation>Machine-readable finding aid and skeletal markup
derived via a macro from WordPerfect file; markup
checked and completed by Sarah Taylor. <date normal="19950423">April 23, 1995.</date>
</creation>
<langusage> Finding aid written in <language langcode="eng">English.</lang usage>
</langusage>
<descrules>Finding aid prepared using <title render="italic">Rules for Archival Description</title>
</descrules>
</profiledesc>
</adheader>
```

**Schematron**
<adheader> MUST contain information on the language used in the EAD document: <langusage> <language> element

```xml
<s:rule context="ead:profiledesc"> <s:assert role="MUST"
test="ead:langusage/ead:language">adheader MUST contain a
language/language element</s:assert> </s:rule>
```

**Schematron**
<adheader> SHOULD contain a <creation> element

```xml
<s:rule context="ead:profiledesc">
<s:assert role="SHOULD" test="ead:creation">adheader SHOULD contain a
creation element</s:assert> </s:rule>
```

**Schematron**
<descrules> has a default value added automatically by EHRI. Therefore, the content of <descrules> will be overwritten

```xml
<s:rule context="ead:profiledesc" role="SHOULD">
<s:assert test="not(normalize-space(ead:descrules))">descrules has a default
value added automatically by EHRI. Therefore, the content of descrules will be
overwritten</s:assert> </s:rule>
```
## Content model

`<content/>`

## Schema

### Declaration

element profiledesc

<figure><img src="image_11.png" /></figure>

att.EADGlobal_attributes,

( creation?, langusage?, descrules? )

## <ptr/>

`<ptr/>` (Pointer) An empty internal linking element that uses attributes to provide for movement from one place in a finding aid to another place in the same finding aid. Unlike the `<ref>` element, the `<ptr/>` element cannot contain text and subelements to describe the referenced object.

### Module

### Attributes

EAD

att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.xlink (@label, @href, @type, @title, @from, @to, @role, @actuate, @show, @arcrole, @xpointer, @entityref, @target, @parent)

### Member of

model.phrase.bare

### Contained by

EAD: abstract addressline archref author bibref bibseries container corpname creation date descrules dimensions edition emph entry event extrefloc famname function genreform geogname head head01 head02 imprint indexentry item label langmaterial language langusage legalstatus materialspec name num occupation origination p persname physdesc physfacet physloc ptrgrp publisher ref refloc repository runner sponsor subarea subject subtitle title titleproper unitdate unitid unittitle

### May contain

Empty element

### Note

Do not confuse with `<extptr/>` which is used to connect the EAD document to an external electronic object, which is not part of the described materials. See related linking elements `<extptr/>`, `<extptrloc/>`, `<extref>`, `<extrefloc>`, `<linkgrp>`, `<ptrgrp>`, `<ptrloc/>`, `<ref>`, and `<refloc>`.

While XML Linking Language (XLink) Version 1.0, which is the basis for EAD linking elements, is a stable document, examples of EAD usage are hypothetical and have not been tested in real XLink-based applications. Those wishing to use XLink are encouraged to consult the specification available online at http://www.w3.org/TR/xlink.

### Example

`<appraisal xmlns="urn:isl:1-931666-22-9">`

`<p> This collection was re-appraised by repository staff in 1992 in order to facilitate use by weeding the collection of materials no longed deemed as having evidential or informational value. A list of materials removed from the collection after the re-appraisal is provided at the end of this guide. <ptr linktype="simple" actuate="onrequest" show="replace" target="mss1982-062_add2"/> </p>`

`</appraisal>`

## Content model

`<content>`

`</content>`

## Schema
**Declaration** element ptr { att.EADGlobal_attributes, att.xlink_attributes, empty }

<ptrgrp>

<ptrgrp> (Pointer Group) A wrapper element for two or more Pointer <ptr/> or Reference <ref> elements used in an <indexentry>. Pointers and references are internal links that provide for movement from one place in the finding aid to another place in the same finding aid. When encoding an index in EAD, a name or entry is generally listed only once, followed by a <ptrgrp> containing the series of pointers and references that link the name or entry to the places in the finding aid where it appears. The <ptrgrp> prevents the name or entry from having to appear multiple times in the index.

<table><tr><td>Module</td><td>EAD</td></tr><tr><td>Attributes</td><td>att.EADGlobal (@id, @altrender, @audience, @encodinganalog)</td></tr><tr><td>Contained by</td><td>EAD: indexentry</td></tr><tr><td>May contain</td><td>EAD: ptr ref</td></tr><tr><td>Example</td><td><index xmlns="urn:isl:1-931666-22-9"><head>Correspondent Index</head><indexentry>< Exchange Name>Adeltraud, Jerome</Exchange Name><ptrgrp><ref linktype="simple" target="corresp19730824" actuate="onrequest" show="replace"><date normal="19730824">1973 August 24</date></ref><ref linktype="simple" target="corresp19740228" actuate="onrequest" show="replace"><date normal="19740228">1974 February 28</date></ref><ref linktype="simple" target="corresp19750315" actuate="onrequest" show="replace"><date normal="19750315">1975 March 15</date></ref></ptrgrp></indexentry> ... </index></table>

Schema

**Declaration** element ptrgrp { att.EADGlobal_attributes, ( ptr | ref )+ }

<ptrloc/>

<ptrloc/> (Pointer Location) The location of a pointer <ptr/> that is a resource in an extended link.

<table><tr><td>Module</td><td>EAD</td></tr><tr><td>Attributes</td><td>att.EADGlobal (@id, @altrender, @audience, @encodinganalog)</td></tr><tr><td>Member of</td><td>model.extended.els</td></tr><tr><td>Contained by</td><td>EAD: daogrp linkgrp</td></tr><tr><td>May contain</td><td>Empty element</td></tr><tr><td>Note</td><td>While XML Linking Language (XLink) Version 1.0, which is the basis for EAD linking elements, is a stable document, examples of EAD usage are hypothetical and have not been tested in real XLink-based applications. Those wishing to use</td></tr></table>
XLink are encouraged to consult the specification available online at
http://www.w3.org/TR/xlink.

## Content model

```xml
<content>
</content>
```

## Schema Declaration

element ptrloc { att.EADGlobal_attributes, empty }

## <publicationstmt>

<publicationstmt> (Publication Statement) A wrapper element within the <filedesc> portion of <eadheader> for information concerning the publication or distribution of the encoded finding aid, including the publisher's name and address, the date of publication, and other relevant details.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

**Contained by** EAD: <filedesc>

**May contain** EAD: address date num p publisher

**Note** The <publicationstmt> may contain just text, laid out in Paragraphs <p>, or it may include the <publisher>, <address>, <date>, and <num> elements, which allow for more specific tagging of a publisher's name and address, the date of publication, and the number, if any, assigned to the published finding aid.

## Example

```xml
<filedesc xmlns="urn:isl:1-931666-22-9">
    <titlestmt>[...]</titlestmt>
    <publicationstmt>
        <date>1995</date>
        <publisher>Prints &amp; Photographs Division<lb/>Library of Congress</publisher>
        <address>
            <addressline>Washington, D.C. 20540</addressline>
        </address>
    </publicationstmt>
</filedesc>
```

## Schematron

<eadheader> SHOULD specify a <publisher>
<s:rule context="ead:publicationstmt">
<s:assert role="SHOULD" test="ead:publisher">eadheader SHOULD specify a
publisher</s:assert> </s:rule>

## Content model

<content/>

## Schema Declaration

element publicationstmt
{
    att.EADGlobal_attributes,
    ( publisher | date | address | num | p )+
}

## <publisher>

<publisher> (Publisher) When used in the <publicationstmt> portion of <eadheader> and in the <titlepage> element in <frontmatter>, the <publisher> is the name of the party responsible for issuing or distributing the encoded finding aid. Often this party is the same corporate body
identified in the `<repository>` element in the finding aid. When used in the `<imprint>` section of a Bibliographic Reference `<bibref>`, the `<publisher>` is the name of the party issuing a monograph or other bibliographic work cited in the finding aid.

**Module** EAD

**Attributes** `att.EADGlobal` (`@id`, `@altrender`, `@audience`, `@encodinganalog`)

**Contained by** EAD: imprint publicationstmt titlepage

**May contain** EAD: emph extptr lb ptr

**Example**
```xml
<filedesc xmlns="urn:isl:1-931666-22-9">
    <titlestmt>[...]</titlestmt>
    <publicationstmt>
        <date>1995</date>
        <publisher>Prints &amp; Photographs Division<lb/>Library of Congress</publisher>
        <address>
            <addressline>Washington, D.C.
                20540</addressline>
        </address>
    </publicationstmt>
    <filedesc>
```

**Example**
```xml
<bibliography xmlns="urn:isl:1-931666-22-9">
    <bibref>
        <persname role="author">Kinder, Dolores.</persname>
        <title>Once Upon a Lullaby.</title>
        <imprint>
            <geogname>New York: </geogname>
            <publisher>Wells &amp; Sons, </publisher>
            <date type="publication">1931</date>
        </imprint>
    </bibref>
</bibliography>
```

**Content model**

```xml
<content>
</content>
```

**Schema Declaration**

element publisher { att.EADGlobal_attributes, ( text | model.phrase.bare )* }

**<ref>**

**<ref>** (Reference) An internal linking element that provides for movement from one place in a finding aid to another place in the same finding aid. Unlike the internal Pointer `<ptr/>` element, the `<ref>` element may contain text and subelements that identify or describe the referenced object. The `<ref>` element may be used in a variety of ways in an encoded finding aid. For example, a `<ref>` may provide a dynamic link from one Component `<c>` to another related Component `<c>` in the same way that See and See also references direct readers of paper-based finding aids. Or, a `<ref>` might be used to direct the reader from text in a scope and content note to a description of a Component `<c>` in a contents list.

**Module** EAD

**Attributes** `att.EADGlobal` (`@id`, `@altrender`, `@audience`, `@encodinganalog`) `att.xlink` (`@label`, `@href`, `@type`, `@title`, `@from`, `@to`, `@role`, `@actuate`, `@show`, `@arcrole`, `@xpointer`, `@entityref`, `@target`, `@parent`)

**Member of** `model refs`
**Contained by** EAD: abstract archref bibliography bibref creation descrules dimensions emph entry event extref indexentry item label langmaterial langusage materialspec origination otherfindaid p physdesc physfacet physloc ptrgrp relatedmaterial repository separatedmaterial unitdate unitid unittitle

**May contain** EAD: abbr address archref bibref blockquote chronlist corpname date emph expan extptr extref famname function genreform geogname lb list name note num occupation origination persname ptr repository subject table title unitdate unittitle

**Note** While XML Linking Language (XLink) Version 1.0, which is the basis for EAD linking elements, is a stable document, examples of EAD usage are hypothetical and have not been tested in real XLink-based applications. Those wishing to use XLink are encouraged to consult the specification available online at http://www.w3.org/TR/xlink.

**Example**
```xml
<index xmlns="urn:isl:1-931666-22-9">
  <head>Index to Correspondents and Recipients</head>
  <indexentry>
    <corpname>Bach &amp; Bros.</corpname>
    <ref linktype="simple" target="NonC:21-2" show="replace" actuate="onrequest"> (In non correspondence)</ref>
  </indexentry>
  <indexentry>
    <namegrp>
      <corpname>Bacon and Lewis, Ltd.</corpname>
      <persname>Levering, Alexander M.</persname>
      <persname>Windom, Lucious</persname>
    </namegrp>
    <ref linktype="simple" target="Cres:18610408" show="replace" actuate="onrequest"> (1861 Apr. 8, AL S, to W.W., re: inquiry into what to do with unsold flour)</ref>
  </indexentry>
  ...
</index>
```

**Content model**

```xml
<content>
</content>
```

**Schema Declaration**

element ref
```xml
{
  att.EADGlobal_attributes,
  att.xlink_attributes,
  (text | model.para.content.norefs | bibref | title | extref | archref )*
}
```

**<refloc>**

**<refloc>** (Reference Location) A linking element that provides the location of a reference <ref> that is a resource in an extended link.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.roled (@role)

**Member of** model.extended.els

**Contained by** EAD: daogrp linkgrp

**May contain** EAD: abbr address blockquote chronlist corpname date emph expan extptr famname function genreform geogname lb list name note num occupation
**Note**

originationättiernameptrrepository subject table unitdate unittitle
While XML Linking Language (XLink) Version 1.0, which is the basis for EAD
linking elements, is a stable document, examples of EAD usage are hypothetical
and have not been tested in real XLink-based applications. Those wishing to use
XLink are encouraged to consult the specification available online at
http://www.w3.org/TR/xlink/.

**Example**
```xml
<archdesc xmlns="urn:isl:1-931666-22-9" level="collection">
  <did>[...]</did>
  <arrangement>
    <p>This collection is organized into two major sections. The
    Original Gift portion reflects the materials originally
    donated to the Society by Mr. Provenance, while the
    Additions portion contains records transferred following
    his death. As these two groups of documents have not
    been physically interfiled, materials on any given topic
    may appear in either or both sections, each of which is
    divided into four parallel series. <linkgrp>
      <refloc target="a9"/>
      <refloc target="s1"/>
      <refloc target="s7"/>
    </linkgrp>
    </p>
    <p id="a9">Personal Correspondence</p>
    <p id="a10">Financial Records</p>
    <p id="a11">Diaries</p>
    <p id="a12">Literary Manuscripts</p>
  </arrangement>
  <dsc type="combined">
    <head>Original Gift</head>
    <c01 id="s1">
      <did>
        <unittitle>Personal correspondence, </unittitle>
        <unitdate>1917-1965.</unitdate>
      </did>
    </c01> . . . </dsc>
    <dsc type="combined">
      <head>Additions</head>
      <c01 id="s7">
        <did>
          <unittitle>Personal correspondence, </unittitle>
          <unitdate>1922-1945.</unitdate>
        </did>
      </c01> . . . </dsc>
    </unittitle>
  </dsc>
</archdesc>
```

**Content model**

<content>
</content>

**Schema**

**Declaration**

```
element refloc
{
  att.EADGlobal_attributes,
```
att.roled_attributes,
(text | model.para.content.norefs)*
}

<relatedmaterial>

<relatedmaterial> (Related Material) Information about materials that are not physically or logically included in the material described in the finding aid but that may be of use to a reader because of an association to the described materials. Materials designated by this element are not related to the described material by provenance, accumulation, or use.

<table><tr><td>Module</td><td>EAD</td></tr><tr><td>Attributes</td><td>att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.typed (@type)</td></tr><tr><td>Member of</td><td>model desc base</td></tr><tr><td>Contained by</td><td>EAD: archdesc archdescgrp c c01 c02 c03 c04 c05 c06 c07 c08 c09 c10 c11 c12 descgrp relatedmaterial</td></tr><tr><td>May contain</td><td>EAD: address archref bibref blockquote chronlist extref head linkgrp list note p ref relatedmaterial subtitle table title</td></tr><tr><td>Note</td><td>Do not confuse <relatedmaterial> with the element <separatedmaterial>, which provides information about materials that have been separated or physically removed from the described materials but that are related to them by provenance. Also do not confuse with <altformavail>, which encodes information about copies of the described materials, such as microforms, photocopies, and reproductions in digital formats. Do not confuse with <originalsloc>, which encodes information regarding the existence and location of the originals when the unit being described consists of copies. In EAD Version 1.0 <relatedmaterial> was a subelement of Adjunct Descriptive data <add>, which has been deprecated in EAD 2002 (see Appendix B). The new Description Group <descgrp> element, which can group any of the <did>-level elements (except the Description of Subordinate Components <dsc>), may be used to wrap elements where a group heading is desirable. The <descgrp> element can be used to replace <add> when converting finding aids encoded in EAD V1.0 to EAD 2002. The <relatedmaterial> element is comparable to ISAD(G) data element 3.5.3 and MARC field 544 with indicator 1.</td></tr><tr><td>Example</td><td><relatedmaterial xmlns="urn:isl:1-931666-22-9"><head>Related Correspondence</head><p>Researchers should note that a significant amount of the correspondence between Franklin Wigglethorpe and Nellie Forbush is extant. In addition to the incoming letters in this collection from Mr. Wigglethorpe to Miss Forbush, the letters written to Mr. Wigglethorpe by Miss Forbush are available to researchers at the Mainline University Special Collections Library.</p><archref><origination><persname>Wigglethorpe, Franklin.</persname></origination><unittitle>Franklin Wigglethorpe Papers, <unitdate type="inclusive">1782-1809.</unitdate></unittitle><unitid>MSS 00143</unitid></relatedmaterial></td></tr></table>
```xml
</archref>
```

```p
<p>An online guide to the Wigglethorpe Papers is available.
```

```extptr
actuate="onrequest"
entityref="mu-scl-00143" show="new"/>
```

```p
</p>
```

```</relatedmaterial>
```

### Example

```p
<separatedmaterial xmlns="urn:isl:1-931666-22-9">
```

```p
<p>Photographs and sound recordings have been transferred to the
appropriate custodial divisions of the Library where they
are identified as part of these papers. Among the sound
recordings are the following broadcasts:</p>
```

```list
[...]</list>
```

```</separatedmaterial>
```

```p
<separatedmaterial xmlns="urn:isl:1-931666-22-9">
```

```p
<p>Other papers of Earl Warren, which relate chiefly to his
early years and public service in California, are held by
the California State Archives in Sacramento.</p>
```

```</separatedmaterial>
```

```p
<relatedmaterial xmlns="urn:isl:1-931666-22-9">
```

```p
<p>Records relating to the Warren Commission are held in the
National Archives and Records Administration.</p>
```

```</relatedmaterial>
```

### Content model

```p
<content>
```

```</content>
```

### Schema

#### Declaration

element relatedmaterial

{

att.EADGlobal_attributes,

att.typed_attributes,

head?

( model_blocks | model_refs | relatedmaterial )+

### <repository>

```xml
<repository> (Repository) The institution or agency responsible for providing intellectual access to the materials being described. The <corpname> element may be used within <repository> to encode the institution's proper name.
```

#### Module EAD

#### Attributes
att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.labeled (@label)

#### Member of model.data model.did

#### Contained by
EAD: archref did entry event extrefloc item label p ref refloc

#### May contain
EAD: abbr address archref bibref corpname emph expan extptr extref lb linkgrp name ptr ref subarea subtitle title

#### Note

Although the repository providing intellectual access usually also has physical custody over the materials, this is not always the case. For example, an archives may assume responsibility for long-term intellectual access to electronic records, but the actual electronic data files or systems may continue to reside in the office where they were created and maintained, or they may be held for long-term
storage by a unit such as a data library that is able to provide the appropriate
technical facilities for storage and remounting. When it is clear that the physical
custodian does not provide intellectual access, use <physloc> to identify the
custodian and <repository> to designate the intellectual caretaker. When a
distinction cannot be made, assume that the custodian of the physical objects
also provides intellectual access to them and should be recognized as the
<repository>. The <repository> element is comparable to MARC field 852.

**Example**
```xml
<archdesc xmlns="urn:isl:1-931666-22-9" type="inventory" level="subgrp">
  <did>
    <head>Overview of the Records</head>
    <repository label="Repository:">
      <corpname>Minnesota Historical Society</corpname>
    </repository>
    <origination label="Creator:">Minnesota. Game and Fish Department</origination>
    <unittitle label="Title:">Game laws violation records, </unittitle>
    <unitdate label="Dates:">1908-1928</unitdate>
    <abstract label="Abstract:">Records of prosecutions for and seizures of property resulting from violation of the state's hunting and fishing laws. </abstract>
    <physdesc label="Quantity:">2.25 cu. ft. (7 v. and 1 folder in 3 boxes) </physdesc>
    <physloc label="Location:">See Detailed Description section for box location</physloc>
  </did>
</archdesc>
```

**Example**
Note: The Public Record Office of the United Kingdom uses a 7 level system of intellectual units devised specifically for that repository. In that system "lettercode" is the equivalent of "fonds" and "class" is the equivalent of "series."
```xml
<archdesc xmlns="urn:isl:1-931666-22-9" level="otherlevel"
otherlevel="Lettercode">
  <did>
    <unitid>EW</unitid>
    <unittitle>Records of the Department of Economic Affairs</unittitle>
    <origination>
      <corpname>Department of Economic Affairs</corpname>
    </origination>
    <unitdate>1945-1979</unitdate>
    <physdesc>
      <extent>28</extent>
      <genreform>classes</genreform>
    </physdesc>
    <repository>Public Record Office, Kew</repository>
  </did>
</archdesc>
```

## Content model

```xml
<content>
</content>
```

## Schema
**Declaration**

 element repository
 {
  att.EADGlobal_attributes,
  att.labeled_attributes,
  (text | model.phrase.basicConfig | address | corpname | name | subarea)*
 }

<resource>

<resource> (Resource) A linking element that specifies the local resource that participates in an
extended link.

**Module** EAD
**Attributes**
att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.xlink (@label, @href, @type, @title, @from, @to, @role, @actuate, @show, @arcrole, @xpointer, @entityref, @target, @parent)

**Member of** model.extended.els

**Contained by** EAD: daogrp linkgrp

**May contain** EAD: emph lb

**Note**
While XML Linking Language (XLink) Version 1.0, which is the basis for EAD linking elements, is a stable document, examples of EAD usage are hypothetical and have not been tested in real XLink-based applications. Those wishing to use XLink are encouraged to consult the specification available online at http://www.w3.org/TR/xlink.

**Example**

```xml
<c02 xmlns="urn:isl:1-931666-22-9" level="file">
  <did>
    <unititle>Photographs of John Smith and family members</unititle>
    <unitdate type="inclusive" normal="1895/1928">1895-1928</unitdate>
    <daogrp linktype="extended">
      <daodesc>
        <p>Sample digitized image from this file: John Smith graduation portrait, <date normal="18950528">28 May 1895</date>.</p>
      </daodesc>
      <resource linktype="resource" label="start"/>
      <daoloc entityref="f0042_1tmb" linktype="locator" label="thumb"/>
      <daoloc entityref="f0042_1ref" linktype="locator" label="reference"/>
      <arc linktype="arc" show="embed" actuate="onload" from="start" to="thumb"/>
      <arc linktype="arc" show="new" actuate="onrequest" from="thumb" to="reference"/>
    </daogrp>
  </did>
</c02>
```

**Content model**

```xml
<content>
</content>
```
## Schema

**Declaration** element resource
{
  att.EADGlobal_attributes,
  att.xlink_attributes,
  (text | model.render )*
}

## <revisiondesc>

<revisiondesc> (Revision Description) An optional subelement of the <eadheader> for information about changes or alterations that have been made to the encoded finding aid. The revisions may be recorded as part of a <list> or as a series of <change> elements. Like much of the <eadheader>, the <revisiondesc> element is modeled on an element found in the Text Encoding Initiative (TEI) DTD. The TEI recommends that revisions be numbered and appear in reverse chronological order, with the most recent <change> first.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

**Contained by** EAD: eadheader

**May contain** EAD: change list

**Example**
<eadheader xmlns="urn:isbn:1-931666-22-9" audience="internal"
langencoding="iso639-2b">
<eadid>[...]</eadid>
<filedesc>[...]</filedesc>
<profiledesc>[...]</profiledesc>
<revisiondesc>
<change>
<date normal="19970505">May 5, 1997</date>
<item>This electronic finding aid was updated to current
markup standards by Sarah Taylor using a perl
script. Updates included: eadheader, eadid,
arrangement of did elements and their labels.</item>
</change>
</revisiondesc>
</eadheader>

## Content model

<content>

</content>

## Schema

**Declaration** element revisiondesc { att.EADGlobal_attributes, ( list | change+ ) }

## <row>

<row> (Table Row) A formatting element that contains one or more <entry> elements (horizontal cells) in a table.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog)
rowsep **Status** Optional

**Datatype**

**Legal values are:** 1
0

<table><tr><td>valign</td><td>Status</td><td>Optional</td></tr><tr><td></td><td>Datatype</td><td></td></tr><tr><td></td><td>Legal values are:</td><td>top<br>middle<br>bottom</td></tr></table>

**Contained by** EAD: tbody thead

**May contain** EAD: entry

**Note**

By convention, a rule specified by the ROWSEP attribute prints or displays below the row. Vertical rules are specified by the COLSEP attribute in <table> or one of its column-related subelements; external rules are specified by the FRAME attribute available on the <table> element. See also related elements <table>, <tbody>, <tfoot>, and <thead>.

**Example**

<table xmlns="urn:isbn:1-931666-22-9" frame="none">
  <tbody>
    <tr>
      <td>colspec</td>
      <td>colnum="1" colname="1" align="left" colwidth="50pt"/>
      <td>colname="1" colname="1" align="left" colwidth="50pt"/>
      <td>colnum="2" colname="2" align="left" colwidth="50pt"/>
      <td>colname="2" colname="2" align="left" colwidth="50pt"/>
      <td>colnum="3" colname="3" align="left" colwidth="50pt"/>
      <td>colname="3" colname="3" align="left" colwidth="50pt"/>
      <td>thead>
        <tr>
          <td>row</td>
          <td>entry</td>
        </tr>
      </tbody>
    </table>

**Content model**

<content>
</content>

**Schema Declaration**

element row
{
  att.EADGlobal_attributes,
  attribute rowsep { "1" | "0" }?,
attribute align { "top" | "middle" | "bottom" }?,
entry+
}

<runner>

<runner> (Runner) An optional formatting element that provides for a header, footer, or watermark to appear on every page of a printed finding aid or throughout an electronic version. If a transparent image is desired as background, use <extptr/> instead. The <runner> is available within <archdesc> and <archdescgrp> and must appear before the <did>. The PLACEMENT attribute specifies whether the <runner> should appear as a header, footer, or watermark.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.roled (@role) placement

**Contained by** EAD: archdesc archdescgrp

**May contain** EAD: emph extptr lb ptr

**Example** <runner xmlns="urn:isl:1-931666-22-9" placement=" footer "> Special Collections, University of Virginia Library, #5866-b </runner>

Content model

<content>

</content>

Schema

**Declaration** element runner

{ att.EADGlobal_attributes, att.roled_attributes, attribute placement { "header" | " footer " | "watermark" }?, ( text | model.phrase.bare )* }

<scopecontent>

<scopecontent> (Scope and Content) A prose statement summarizing the range and topical coverage of the described materials, often mentioning the form and arrangement of the materials and naming significant organizations, individuals, events, places, and subjects represented. The purpose of the <scopecontent> element is to assist readers in evaluating the potential relevance of the materials to their research. It may highlight particular strengths of, or gaps in, the described materials and may summarize in narrative form some of the descriptive information entered in other parts of the finding aid.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

**Member of** model desc. base

**Contained by** EAD: archdesc archdescgrp c c01 c02 c03 c04 c05 c06 c07 c08 c09 c10 c11 c12 descgrp scopecontent

**May contain** EAD: address arrangement blockquote chronlist dao daogrp head list note p scopecontent table

**Note** Additional <scopecontent> elements may be nested inside one another when a complex collection of materials is being described and separate headings are desired. For example, when a collection is received and processed in installments, individual scope and content notes may be created for each installment. EAD permits these separate narrative descriptions to be encoded as
discrete <scopecontent> elements, but it also enables the encoder to gather the independent <scopecontent> notes within a single larger <scopecontent> reflective of the materials as a whole. Nested <scopecontent> elements might also occur when an institution encodes the first paragraph of a long scope and content note as a separate summary <scopecontent> with an *encoding analog* attribute set to MARC field 520$a. The *scopecontent* element is comparable to ISAD(G) data element 3.3.1 and MARC field 520.

<table><tr><td>Example</td><td><archdesc xmlns="urn:isl:1-931666-22-9" level="fonds"><did>[...]</did><scopecontent encodinganalog="520"><head>Scope and Content</head><p>Fonds includes records relating to the Department of Plant Ecology's administration, teaching and research; extension work relating to the Saskatchewan Weed Survey; and correspondence with a variety of institutions and individuals. A series of minutes and correspondence relating to the Saskatchewan Committee on the Ecology and Preservation of Grasslands (established in 1935) documents the efforts to establish permanent reserves of significant grasslands in Saskatchewan.</p></scopecontent></archdesc></td></tr><tr><td>Example</td><td><dsc xmlns="urn:isl:1-931666-22-9" type="combined"><head>Detailed Description of the Collection</head><c01 level="series"><did><unittitle>Record of Prosecutions, </unittitle><unitdate>1916-1927. </unitdate><physdesc>3 volumes.</physdesc></did><scopecontent><p>Information provided in each entry: date of report, name and address of person arrested, location where offense was committed, date of arrest, nature of offense, name of judge or justice, result of trial, amounts of fine and court costs, number of days served if jailed, name of warden, and occasional added remarks. Types of offenses included hunting or fishing out of season or in unauthorized places, exceeding catch or bag limits, taking undersized fish, illegal fishing practices such as gill-netting or dynamiting, illegal hunting practices such as night-lighting, killing non-game birds, fishing or hunting without a license, and hunting-related offenses against persons such as fraud and assault.</p></scopecontent></c01></dsc></td></tr><tr><td>Example</td><td><scopecontent xmlns="urn:isl:1-931666-22-9"><p>Papers of the Lewis family, 19th-20th cent., mainly letters to: Elizabeth, Lady Lewis (1844-1931), with a few to her</p></scopecontent></td></tr></table>
husband Sir George Lewis, 1st Bart. (1833-1911); to one of their daughters, Katherine Elizabeth Lewis (d. 1961), with a few to their son Sir George Lewis, 2nd Bart. (1868-1927); and to their grand-daughter Elizabeth Lewis, later Wansbrough (d. 1995). Many of the letters are undated; some can be dated from the postmark on the envelope, but several letters were kept in the wrong envelopes; most of Paderewski's and Whistler's letters had become separated from their envelopes.</p>

## Content model

<content>

</content>

## Schema

### Declaration

element scopecontent

{ att.EADGlobal_attributes, head?,

((model blocks) | arrangement | scopecontent | dao | daogrp)+}

## <separatedmaterial>

<separatedmaterial> (Separated Material) Information about materials that are associated by provenance to the described materials but that have been physically separated or removed.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.typed (@type)

**Member of** model desc base

**Contained by** EAD: archdesc archdescgrp c c01 c02 c03 c04 c05 c06 c07 c08 c09 c10 c11 c12 descgrp separatedmaterial

**May contain** EAD: address archref bibref blockquote chronlist extref head linkgrp list note p ref separatedmaterial subtitle table title

**Note** Items may be separated for various reasons, including the dispersal of special formats to more appropriate custodial units; the outright destruction of duplicate or nonessential material; and the deliberate or unintentional scattering of fonds among different repositories. Do not confuse with <relatedmaterial>, which is used to encode descriptions of or references to materials that are not physically or logically included in the material described in the finding aid but that may be of use to a reader because of an association to the described materials. Items encoded as <relatedmaterial> are not related to the described material by provenance, accumulation, or use. In EAD Version 1.0 <separatedmaterial> was a subelement of Adjunct Descriptive Data <add>, which has been deprecated in EAD 2002 (see Appendix B). The new Description Group <descgrp> element, which can group any of the <did>-level elements (except the Description of Subordinate Components <dsc>), may be used to wrap elements where a group heading is desirable. The <descgrp> element can be used to replace <add> when converting finding aids encoded in EAD V1.0 to EAD 2002. The <separatedmaterial> element is comparable to ISAD(G) data element 3.5.3 and MARC field 544 with indicator 0.

**Example** <separatedmaterial xmlns="urn:isl:1-931666-22-9">
<publicationstmt>

<!--&amp;hdr-huntm;-->

<date>© 1998</date>

<p>The Huntington Library. All rights reserved.</p>

<publicationstmt>

<seriesstmt>

<p>Observatories of the Carnegie Institution of Washington
Collection</p>

</seriesstmt>

<filedesc>

## Content model

<content>

</content>

## Schema

Declaration element seriesstmt { att.EADGlobal_attributes, ( titleproper | num | p )+ }

## <sponsor>

<sponsor> (Sponsor) Name(s) of institution(s) or individual(s) who endorsed, financed, or arranged the acquisition, appraisal, and processing of the described materials or the preparation and distribution of the finding aid. Because acknowledgment of such contributors often appears on title pages of finding aids, the <sponsor> element is available in both the optional <titlepage> element in <frontmatter> and in the required <titlestmt> portion of the <eadheader>. Do not confuse with <author>, which is used to denote the persons or institutions responsible for the intellectual content of the finding aid, or with <repository>, which is used to identify the institution or corporate body providing intellectual access to the described materials.

Module EAD

Attributes att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

Contained by EAD: titlepage titlestmt

May contain EAD: emph extptr lb ptr

Note The <sponsor> element is comparable to MARC field 536.

Example <filedesc xmlns="urn:isl:1-931666-22-9">

<titlestmt>

<titleproper>Inventory of The Bruno Walter Papers, <date>ca.
1887-1966</date>

</titleproper>

<author>Processed by Richard Koprowski, Fran Barulich, and
Robert Kosovsky; machine-readable finding aid created by
Robert Kosovsky</author>

<sponsor>Encoding funded by the generous support of the
Gladys Krieble Delmas Foundation.</sponsor>

<titlestmt> . . . </filedesc>

## Content model

<content>

</content>

## Schema

Declaration element sponsor { att.EADGlobal_attributes, ( text | model.phrase.bare )* }
## <subarea>

**<subarea>** (Subordinate Area) A name or phrase that indicates a secondary or subsidiary administrative level within a repository or other corporate body; a specialized area of subject or other collecting emphasis within a larger unit; or an ancillary collecting area based on the physical form of the materials.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

**Contained by** EAD: corpname repository

**May contain** EAD: emph extptr lb ptr

**Note** This information may be included as plain text within the <repository> and <corpname> elements, or it may be encoded within <repository> and <corpname> as separately tagged <subarea> elements. The latter approach facilitates the filtering of finding aids by administrative division, department, or specialty. For <corpname>s other than <repository>, the <subarea> might help refine searches of large corporate entities, such as government agencies, which share common words, e.g., United States.

**Example** <did xmlns="urn:isl:1-931666-22-9">

**Example** <controlaccess xmlns="urn:isl:1-931666-22-9">

### Content model

### Schema Declaration

element subarea { att.EADGlobal_attributes, ( text | model.phrase.bare )* }

## <subject>

**<subject>** (Subject) A term that identifies a topic associated with or covered by the described materials. Personal, corporate, and geographic names behaving as subjects are tagged as <persname>, <corpname>, and <geogname>, respectively. The ROLE attribute can be set to "subject" when it is necessary to specify the relationship of the name to the materials being described.

**Module** EAD

**Attributes** att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.access (@source, @rules, @authfilenumber, @normal)

**Member of** model.access

**Contained by** EAD: controlaccess entry event extrefloc indexentry item label namegrp p physdesc physfacet ref refloc unittitle

**May contain** EAD: emph extptr lb ptr

**Note** All subjects mentioned in a finding aid do not have to be tagged. One option is to
tag those subjects for which access other than basic, undifferentiated keyword
retrieval is desired. Use of controlled vocabulary forms is recommended to
facilitate access to the subjects within and across finding aid systems. The
<subject> element may be used in text elements such as <p>. To indicate a
subject with major representation in the materials being described, nest <subject>
within the <controlaccess> element. Use the SOURCE attribute to specify the
vocabulary from which the term has been taken. The NORMAL attribute can be
used to provide the authority form of a term that has been encoded with <subject>
in narrative text, e.g., within a paragraph. The RULES attribute can be used to
specify the descriptive rules followed when formulating the term. The
AUTHFILENUMBER attribute can be used to identify a link to an authority file
record that has more information about the subject or cross references for
alternative forms of a subject term.

The <subject> element is comparable to MARC fields 650 and 69x.

Example

<controlaccess xmlns="urn:isb:1-931666-22-9">

<head>Selected Search Terms</head>

<controlaccess>

<head>Subjects:</head>

<subject encodinganalog="650">Alien and Sedition laws,
1798</subject>

<subject encodinganalog="650">American Confederate voluntary
exiles</subject>

<subject encodinganalog="650">Kentucky and Virginia
resolutions of 1798</subject>

</controlaccess>

<controlaccess>

Content model

<content>

<content>

Schema

Declaration

element subject

{
  att.EADGlobal_attributes,
  att.access_attributes,
  (text | model.phrase.bare)*
}

<subtitle>

<subtitle> (Subtitle) A secondary or subsidiary name of an encoded finding aid that is subordinate to the main name encoded in <titleproper>. The <subtitle> element is available only within <titlepage> and <titlestmt> to capture bibliographic aspects of the finding aid. Subtitles of monographs, serials, paintings, and other such works mentioned in the finding aid are not separately encoded, but they may be listed as part of the <title> element.

Module EAD

Attributes att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

Member of model.access.title modelpagc refs

Contained by EAD: abstract bibliography controlaccess creation descrules dimensions emph entry event indexentry item label langmaterial langusage materialspec namegrp origination otherfindaid p physdesc physfacet physloc relatedmaterial repository separatedmaterial titlepage titlestmt unitdate unitid unittitle
## May contain Example

EAD: abbr date emph expan extptr lb num ptr
<filedesc xmlns="urn:isl:1-931666-22-9">
  <titlestmt>
    <titleproper>Tom Stoppard</titleproper>
    <subtitle>An Inventory of His Papers at the Harry Ransom Humanities Research Center</subtitle>
    <author>Finding aid written by Katherine Mosley</author>
  </titlestmt>
  <publicationstmt>
    <publisher>The University of Texas at Austin, Harry Ransom Humanities Research Center</publisher>
    <date>2000</date>
  </publicationstmt>
</filedesc>

## Content model

<content>
</content>

## Schema Declaration

element subtitle
{
  att.EADGlobal_attributes,
  ( text | model.phrase.bare | abbr | date | expan | num )*
}

## <table>

<table> (Table) A wrapper element for formatting information in a row and column display.

<table>
  <tbody>
    <tr>
      <td rowspan="11">Module<br>Attributes</td>
      <td>EAD</td>
      <td></td>
    </tr>
    <tr>
      <td>att.EADGlobal (@id, @altrender, @audience, @encodinganalog)</td>
      <td></td>
    </tr>
    <tr>
      <td>frame</td>
      <td>
        <table>
          <tbody>
            <tr>
              <td><strong>Status</strong></td>
              <td>Optional</td>
            </tr>
            <tr>
              <td><strong>Datatype</strong></td>
              <td></td>
            </tr>
            <tr>
              <td><strong>Legal values are:</strong></td>
              <td>
                <table>
                  <tbody>
                    <tr>
                      <td>top</td>
                    </tr>
                    <tr>
                      <td>bottom</td>
                    </tr>
                    <tr>
                      <td>topbot</td>
                    </tr>
                    <tr>
                      <td>all</td>
                    </tr>
                    <tr>
                      <td>sides</td>
                    </tr>
                    <tr>
                      <td>none</td>
                    </tr>
                  </tbody>
                </table>
              </td>
            </tr>
          </tbody>
        </table>
      </td>
    </tr>
    <tr>
      <td>colsep</td>
      <td>
        <table>
          <tbody>
            <tr>
              <td><strong>Status</strong></td>
              <td>Optional</td>
            </tr>
            <tr>
              <td><strong>Datatype</strong></td>
              <td></td>
            </tr>
            <tr>
              <td><strong>Legal values are:</strong></td>
              <td>
                <table>
                  <tbody>
                    <tr>
                      <td>1</td>
                    </tr>
                    <tr>
                      <td>0</td>
                    </tr>
                  </tbody>
                </table>
              </td>
            </tr>
          </tbody>
        </table>
      </td>
    </tr>
    <tr>
      <td>rowsep</td>
      <td>
        <table>
          <tbody>
            <tr>
              <td><strong>Status</strong></td>
              <td>Optional</td>
            </tr>
            <tr>
              <td><strong>Datatype</strong></td>
              <td></td>
            </tr>
          </tbody>
        </table>
      </td>
    </tr>
  </tbody>
</table>
Legal values are: 1

0

pgwide

Status

Optional

Datatype

Legal values are: 1

0

**Member of**
**Contained by**

model.inter.noquote

EAD: accessrestrict accruals acqinfo altformavail appraisal arrangement bibliography bioghist blockquote controlaccess custodhist daodesc descgrp div dsc dscgroup event extrefloc index item note odd originalsloc otherfindaid p phystech prefercite processinfo ref refloc relatedmaterial scopecontent separatedmaterial userestrict

**May contain**
**Note**

EAD: head tgroup

The application of the <table> element is based on the XML Exchange Table Model, an XML expression of the Exchange subset of the full CALS table model DTD. This model is promulgated by the Organization for the Advancement of Structured Information Standards (OASIS) to promote interoperability among vendor products.

**Example**

<table xmlns="urn:ISBN:1-931666-22-9" frame="none">
  <tbody>
    <tr>
      <td>
        <table>
          <tr>
            <td>
              <td colspan="2">tgroup cols="3">...</td>
            </tr>
            <tr>
              <td>
                <td colspan="2">&lt;colspec colnum="1" colname="1" align="left" colwidth="50pt"/&gt;</td>
              </tr>
              <tr>
                <td>
                  <td colspan="2">&lt;colspec colnum="2" colname="2" align="left" colwidth="50pt"/&gt;</td>
                </tr>
                <tr>
                  <td>
                    <td colspan="2">&lt;colspec colnum="3" colname="3" align="left" colwidth="50pt"/&gt;</td>
                  </tr>
                </table>
              </td>
            </tr>
          </table>
        </tbody>
      </td>
    </tr>
  </tbody>
</table>

**Content model**

<content>
</content>
## Schema

**Declaration**

```xml
<Schema Declaration>
    <element table>
        {
            att.EADGlobal_attributes,
            attribute frame { "top" | "bottom" | "topbot" | "all" | "sides" | "none" }?,
            attribute colsep { "1" | "0" }?,
            attribute rowsep { "1" | "0" }?,
            attribute pgwide { "1" | "0" }?,
            head?,
            tgroup+
        }
    </element table>
</Schema>
```

## <tbody>

<tbody> (Table Body) A formatting element that contains one or more <row> elements, which in turn contain <entry> elements in a <table>. The <tbody> element identifies the body of the information in a <table>, as distinct from the column headings (Table Head <thead>).

**Module** EAD

**Attributes**

att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

valign Status Optional

**Datatype**

Legal values are: top

middle

bottom

**Contained by** EAD: tgroup

**May contain** EAD: row

**Note** See also related elements <entry>, <row>, <table>, <tgroup>, and <thead>.

**Example**

```xml
<table xmlns="urn:isbn:1-931666-22-9" frame="none">
    <thead>
        <tr>
            <th>colnum</th>
            <th>colname</th>
        </tr>
    </thead>
    <tbody>
        <tr>
            <td>1</td>
            <td>Major Family Members</td>
        </tr>
        <tr>
            <td>2</td>
            <td>Spouses</td>
        </tr>
        <tr>
            <td>3</td>
            <td>Children</td>
        </tr>
    </tbody>
</table>
```
(1787-1848)</td>
</tr>
</tbody>
</table>

## Content model

<content>
</content>

## Schema

**Declaration**

 element tbody
 {
  att.EADGlobal_attributes,
  attribute valign { "top" | "middle" | "bottom" }?,
  row+
 }

## <tgroup>

<tgroup> (Table Group) A formatting element that bundles <table> subelements: <colspec/>, <thead>, and <tbody>. Tables are comprised of one or more <tgroup>s, depending on the number of times the column specifications change. The <tgroup> element provides a subgrouping of rows within a table that all use the same column specifications.

**Module** EAD

**Attributes**

 att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

cols **Status** Optional

colsep **Datatype**

colsep **Status** Optional

colsep **Datatype**

colsep **Legal values are:** 1

colsep **Legal values are:** 0

rowsep **Status** Optional

rowsep **Datatype**

rowsep **Legal values are:** 1

rowsep **Legal values are:** 0

align **Status** Optional

align **Datatype**

align **Legal values are:** left

align **Legal values are:** right

align **Legal values are:** center

align **Legal values are:** justify

align **Legal values are:** char

**Contained by** EAD: table

**May contain** EAD: colspec tbody thread
Note

Three attributes are used together to force horizontal alignment on a specific
character, such as a decimal point. The `ALIGN` attribute must be set to `"char"`
(`align="char"`). The `CHAR` attribute should be set to the specific character on
which the text will align (for example the decimal point, `char="."`). The `CHAROFF`
attribute controls the position of the alignment by naming the percentage of the
current column width that is to the left of the alignment character (for example,
`charoff="30"`). The required `COLS` attribute specifies the number of columns in the
table. By convention, any rule specified in `COLSEP` is printed or displayed to the
right of the column. External rules are specified with the `FRAME` attribute of
`<table>`; horizontal rules are specified with the `<table>` or `<group>` `ROWSEP`
attribute.

By convention, any rule specified in `rowsep` prints or displays below the row.

Vertical rules are specified by a `COLSEP` attribute; external rules are specified by
the `FRAME` attribute of the `<table>` element.

See also related elements `<colspec>`, `<table>`, `<tbody>`, `<thead>`.

Example

<table>
  <thead>
    <tr>
      <th>Column</th>
      <th>Attribute</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>colname</td>
      <td>Major Family Members</td>
    </tr>
    <tr>
      <td>colname</td>
      <td>Spouses</td>
    </tr>
    <tr>
      <td>colname</td>
      <td>Children</td>
    </tr>
  </tbody>
</table>
</row>

<row>

<entry colname="3">Joseph Fairfax Albemarle
(1792-1856)</entry>

</row>

<row>

<entry colname="1">John Delaney Albemarle
(1787-1848)</entry>

<entry colname="2">Martha Mary Adams
(1795-1862)</entry>

<entry colname="3">John Adams Albemarle
(1814-1867)</entry>

</row>

<row>

<entry colname="3">Mary Delaney Albemarle
(1818-1880)</entry>

</row> . . . </tbody>

## Content model

## Schema Declaration

## <thead>

<thead> (Table Head) A formatting element that contains the heading information in a <table>, usually column heads, that appears at the top of the table and may appear again at the top of any physical break in rows in the body. The <thead> element is used inside an ordinary structural <table> and to provide column headings for Components <c> or the Description of Subordinate Components <dsc>.

Module EAD

Attributes
align
valign
Status
Optional
Datatype
Legal values are: top
middle
bottom

**Contained by** EAD: c c01 c02 c03 c04 c05 c06 c07 c08 c09 c10 c11 dsc tgroup

**May contain** EAD: row

**Note** See related elements <table> and <tgroup> for general table information.

**Example**
<table xmlns="urn:isl:1-931666-22-9" frame="none">
  <tgroup cols="3">
    <colspec colnum="1" colname="1" align="left" colwidth="50pt"/>
    <colspec colnum="2" colname="2" align="left" colwidth="50pt"/>
    <colspec colnum="3" colname="3" align="left" colwidth="50pt"/>
    <thead>
      <tr>
        <th>Major Family Members</th>
      </tr>
    </thead>
    <tbody>
      <tr>
        <td>Spouses</td>
      </tr>
      <tr>
        <td>Children</td>
      </tr>
    </tbody>
  </tgroup>
</table>

Content model

<content>
</content>

Schema

**Declaration**

```json
{
  "elementType": "thead",
  "attributes": {
    "attributeAlignment": "top" | "middle" | "bottom",
    "row"
  }
}
```

<title>

<title> (Title) The formal name of a work, such as a monograph, serial, or painting, listed in a finding aid. Subtitles of such works are not separately encoded but may instead be listed as part of the <title> element.

**Module** EAD

**Attributes**

att.EADGlobal (@id, @altrender, @audience, @encodinganalog) att.typed (@type) att.access (@source, @rules, @authfilenumber, @normal) att.xlink (@label, @href, @type, @title, @from, @to, @role, @actuate, @show, @arcrole, @xpointer, @entityref, @target, @parent) attrendered (@render)

**Member of** model.access.title modelpagc

**Contained by** EAD: abstract archref bibliography bibref bibseries controlaccess creation descrules dimensions emph entry event extref indexentry item label langmaterial langusage materialspec namegrp origination otherfindaid p physdesc physfacet physloc ref relatedmaterial repository separatedmaterial unitdate unitid unittitle

**May contain** EAD: date emph extptr lb num ptr

**Note** Do not confuse with <titleproper>, which is used for the title of the encoded finding
aid. Also do not confuse with <unittitle>, which is used to encode the name of the described materials, such as the title of a collection, record group, fonds, series, file, or item. Do not confuse with the TITLE attribute which is found in several linking elements. The <title> element may be used inside of <unittitle>, and it is possible that a <unittitle> may contain no text other than that which is further specified by the <title> element. (See example below.) The RULES attribute can be used to specify the descriptive rules followed when forming the title, such as AACR2R. The ENTITYREF or HREF attributes may be used to name either the entity or pointer when linking to a machine-readable version of the cited <title>. The RENDER attribute permits specification of how the content of a particular <title> element should be displayed or printed, e.g., bold, italics, quoted, etc. The <title> element is comparable to MARC fields 130, 240, 245, 630, 730, and 740.

While XML Linking Language (XLink) Version 1.0, which is the basis for EAD linking elements, is a stable document, examples of EAD usage are hypothetical and have not been tested in real XLink-based applications. Those wishing to use XLink are encouraged to consult the specification available online at http://www.w3.org/TR/xlink.

### Example

```xml
<c01 xmlns="urn:isl:1-931666-22-9">
  <did>
    <unittitle>Short stories, </unittitle>
    <unitdate>1946-1954</unitdate>
  </did>
  <c02>
    <did>
      <unittitle>
        <title render="italic">The Lottery</title>
      </unittitle>
    </did>
  </c02>
</c01>
```

### Example

```xml
<bibref xmlns="urn:isl:1-931666-22-9">
  <title render="italic">Library of Congress Acquisitions: Manuscript Division, <date>1982,</date></title>
  <p> p. 29.</p>
</bibref>
```

### Content model

```xml
<content>
</content>
```

### Schema Declaration

#### element title

```json
{
  att.EADGlobal_attributes,
  att.typed_attributes,
  att.access_attributes,
  att.xlink_attributes,
  attrendered_attributes,
  (text | model.phrase.bare | date | num)*
}
```
# <titlepage>

<titlepage> (Title Page) A wrapper element within <frontmatter> that groups bibliographic information about an encoded finding aid, including its name, author, and other aspects of its creation and publication. It contains much of the same information found in the <filedesc> portion of the <headheader>, such as the <titleproper>, < subtitle >, <author>, <sponsor>, <publisher>, and <date> of the finding aid. Although it is possible to generate an electronic or printed title page directly from the <headheader>, use of the <titlepage> may be more accommodating of local preferences, including displays of photographic illustrations, institutional logos, or other graphic images.

Module EAD

Attributes att.EADGlobal (@id, @altrender, @audience, @encodinganalog)

Contained by EAD: frontmatter

May contain EAD: author bibseries date edition num publisher sponsor subtitle titleproper

Example

<frontmatter xmlns="urn:isl:1-931666-22-9">

<titlepage>

<titleproper>Inventory of The Arequipa Sanatorium Records,

<date>1911-1958</date>

</titleproper>

<num type="Collection number:">BANC MSS 92/894 c</num>

<publisher>The Bancroft Library<lb/>University of

California, Berkeley<lb/>Berkeley, California</ publisher>

<list type="deflist">

<defitem>

<label>Processed by:</label>

<item>Lynn Downey</item>

</defitem>

<defitem>

<label>Completed by:</label>

<item>Mary Morganti and Katherine Bryant</item>

</defitem>

<defitem>

<label>Date Completed:</label>

<item>

<date>May 1994</date>

</item>

</defitem>

<defitem>

<label>Encoded by:</label>

<item>Gabriela A. Montoya</item>

</defitem>

<list>

<p>© 1996 The Regents of the University of California. All rights reserved.</p>

<titlepage>

</frontmatter>

Content model

<content>

</content>

Schema

Declaration element titlepage