Bentley Library EAD 2002 Tag Set

This list represents the set of EAD element tags that might be used in a BHL finding aid, some are required elements, others are optional. Some may rarely be used. The layout of this documents attempts to illustrate the nesting of elements within EAD. The correspondence is not perfect, but generally helps convey the structure of a Bentley EAD finding aid. References to "the system" are to the DLPS (University of Michigan, Digital Library Production Services) search, conversion and display scripts and procedures. In many cases, rather than hard encoding <head> elements into the .xml file, the system will generate headers and punctuation based on attribute values or the context of an element. (modified 12/08/03)

<ead> (the root element, wrapper for entire finding aid)
- <eadheader> (contains descriptive and declarative information making up the "electronic titlepage" standard attribute values will be set to
  - langencoding=iso639-2b
  - audience="internal'
  - repositoryencoding="iso155511"
  - dateencoding="iso8601" (standard to which "normal" date attributes comply)
  - relatedencoding="Dublin Core" (for eadheader only, MARC21 will be used in <archdesc> to describe the collection.)
- - <eadid>umich-bhl-call no. </eadid> (a unique identifier for the EAD instance, call number is numeric part of BHL call number, the element which uniquely identifies a finding aid in the DLPS database) Standard attributes will be:
    - countrycode="us"
    - mainagencycode="miu-h"
    - publicid="//us:miu-h//TXT// us::miu-h::filename//EN" (where filename is the name of the EAD file, this is for compliance with RLG guidelines)
    - encodinganalog="Identifier"
  - <filedesc> (contains a full bibliographic description of the encoded finding aid)
  - - <titlestatement> (container element that groups information about the title of an encoded finding aid and those responsible for its intellectual content)
    - - <titleproper encodinganalog="Title"> (title of the finding aid that has been encoded in EAD, in form "Finding Aid for xxxx papers|records)
      - <date> </date> (inclusive dates of collection/record group may be tagged)
      - </titleproper>
      - <author encodinganalog="Creator"> </author> (names the person or persons responsible for preparing the encoded and/or previous versions of the finding aid, in the form "Finding aid prepared by Joe Smith, 1995")
      - </author>
    - </titlestatement>
    - <publicationstmt>
    - - <publisher encodiinganalog="Publisher">Bentley Historical Library, University of Michigan</publisher> (name of the publisher)
      - <date encodinganalog="Date"> </date> (date of electronic publication)
    - </publicationstmt>
  - </filedesc>
  - < profiledesc> (container element, provides detailed information about non-bibliographic aspects of the text of an encoded finding aid; language and/or place , date and agent of creation of the encoded finding aid)
  - - <creation> </creation> (name of creator of encoding finding aid, can use phrase like "Encoded finding aid prepared by Joe Smith, 1997")
    - - <date> </date> (date encoded finding aid prepared may be tagged separately)
    - <langusage><language encodinganalog="Language" langcode="eng">English</language></langusage> (indicates the language in which the finding aid is written)
    - <descrules>Finding aid prepared using Describing Archives: A Content Standard (DACS)</descrules> (indicates the rules , standards or protocols followed increting the finding aid)
  - </profiledesc>
  - <revisiondesc> summarizes changes that have been made to the encoded finding aid, most recent change first
  - - <change>
    - - <date> date of revision</date> (use normalized date format YYYYMMDD)
      - <item> description of change</> (for first item use something like "Original encoding from Word 2000 file", any subsequent significant changes/updating should be recorded)
    - </change
  - </revsiondesc>
- </eadheader>
- <frontmatter> (container element for information that appears on the "title page")
- - <titlepage>
  - - <publisher> </publisher> (MHC/UARP, BHL, UM use <lb/> to force line breaks between)
    - <titleproper> <titleproper> (title of the finding aid "Finding Aid for the<lb/> Will E. Hampton papers,.)
    - - <date>1839-1959</date> (inclusive dates of the collections)
    - <author> <author> (author of the finding aid, in the form "Finding Aid prepared by Joe Smith, 1994" use <lb/> to separate multiple authors)
    - <sponsor> </sponsor> (for text crediting sponsor/funders of projects)
  - </titlepage>
- </frontmatter>
- <archdesc> standard attributes:
  - level="collection|record group" (required)
  - type=inventory"
  - relatedencoding="MARC21"
  - audience="external"
  (wrapper element around segment of encoded finding aid that describes the content, context, and extent of the historical materials being described in the encoded finding aid. Level attribute describing the highest tier of material being described (usually collection or record group) is required. Attribute value assigned will determine value of some headings generated by html display system, e.g. Biography or History. Reletedencoding attribute specifies that all subsequent encodinanalog attributes refer to MARC unless otherwise stated.
- - <did> (A container element that bundles eight elements identifying fundamental descriptive information needed to identify the unit being described, here the full collection/record group)
  - - <origination><persname encodinganalog="100" source="lcnaf"> </persname> </origination> (use for the creator/collector of the records/papers in AACR2 format with <persname>, <corpname> or <famname> tag and encodinganalog and source of authority attributes set inside the "name" element, equivalent of MARC 100/110/111 field) (heading "Creator: " supplied by system)
    - <unittitle encodinganalog="245"> </unittitle> (title of the unit being described, here the collection or record group, e.g., "Ferry family papers." in AACR2 format with dates encoded as <unitdate> inside </unititle> (heading "Title: supplied by system) If the <unittitle> contains a formal title of a publication the title can be placed in a <title> tag.
    - - <unitdate type="inclusive" encodinganalog="245$f" normal="yyymmdd/yyyymmdd"> </unitdate> (dates of the material being described, here the collection or record group, RLG recommends setting normal attrubte for all unitdates, BHL may set normal at least for this top-level unitdate)
        (heading "Inclusive Dates: " supplied by system)
      - <unitdate type="bulk" encodinganalog="245$g"> </unitdate> (option to repeat unitdate tag to indicate bulk date span of the collection) (heading "Bulk Dates: " will be supplied by system)
    - <physdesc> (A statement of the physical characteristics or object type(s) of the materials being described. Can include information on the extent, dimensions, genre form and other physical facets of the materials.) (in this occurrence of <physdesc> system should not supply opening and closing parens) use label attribute to determine what heading will be displayed, default in template will be "Quantity"> use a separate <physdesc> for each subelement used.
    - - <extent encodinganalog="300" > </extent> (size of the collection, normally expressed in linear ft., might also indicate number of volumes or outsize material) (heading "Quantity: " will be supplied by system)
      - <genreform> <genreform> (used to distinguish type of material by intellectual content or physical characteristics. BHL may have occasion to use, (e.g. Photographs, Sound Recordings, Diaries or outsize volumes) (heading will be supplied based on value of label in <physdesc >)
    - <unitid repository code="MiU-H" countrycode="us" type="call number" encodinganalog="099"> </unitid> (BHL call number) (heading "Call No.: " will be supplied by system)
    - <abstract> </abstract> a very brief, one or two sentences description of creator and collection. to permit user to make very quick appraisal of a collections relevance. (heading "Abstract: " will be supplied by system)
    - <langmaterial>The materials in the the collections are in <language langcode="eng" encodinganalog="041">English</language></langmaterial>
    - (heading "Language:" will be supplied by system)
    - <physloc> </physloc> will be used to indicate that material is stored off site or otherwise not immediately physically accessible. (heading will be supplied by system)
    - <originalsloc encodiganalog="535"><p> </p></originalsloc> (new element to specify location/repository of original material if copies are being described in the finding aid)
    - <repository> <corpname encodinganalog="852"><subarea>Bentley Historical Library</subarea> University of Michigan<corpname> (name of the institution or agency providing intellectual access to the materials being described, may enter name directly or use <name> and <address> elements.) (heading "Repository: " will be supplied by system) (an extptr with href attribute will point to file through DLPS resolver to supply BHL address, phone fax, e-mail)
    - - <extptr> </extptr href="bhlads"></repository> (empty element, attributes will point to an external file with BHL address, contact information)
    - </did>
    - <descgrp type="admininfo"> ( generic container element that bundles information about the source, provenance, availability, restrictions, processing, preferred citation, and other matters relating to the management of the materials being described, type attribute is used to distinguish it from other possible uses)
      heading "Access and Use" will be supplied by system.
    - - <acqinfo encodinganalog="541"> (Information about the source of the materials being described and the circumstances of acquisition) heading "Acquisition Information : " will be supplied by system
      - <p> (text can only be entered in a paragraph )
        
        <num type="accession"> </num> (enclose the actual accession/donor number in a number tag) e.g <p> The collection (Donor No. <num type="accession">1234 </num> ...</p> if there are multiple donor numbers tag them individually.
      - </acqinfo>
      - <accruals encodinganalog="585"> (Information about expected receipt of addtional material) heading "Accruals : " will be supplied by system
        
        <p> (text can only be entered in a paragraph )
        
        <num type="accession"> </num> (enclose the actual accession/donor number in a number tag) e.g <p> The collection (Donor No. <num type="accession">1234 </num> ...</p> if there are multiple donor numbers tag them individually.
        
        </acqinfo>
        
        <accessrestrict encodinganalog="506"> (contains information about gaining access to the materials being described by the encoded finding aid that may have been imposed by the repository, donor, legal statute, or other agency) heading "Access Restrictions: " will be supplied by system.
        
        <p> </p> (text will normally be in a paragraph, blockquote or list could be used) BHL will use <extptr> to standard restriction statement on university records
        
        <extptr href="uarpacc" actuate="onload" show="embed"> (for UARP record groups an additional block of standard text text on UM/BHL access policy will automatically display
        
        </accessrestrict>
        
        <userestrict encodinganalog="540"> (contains information on restrictions of use of the material after access has been granted, such as restrictions on reproduction, publication, citation, BHL would use for copyright statement. (heading "Copyright: " will be supplied by system.)
        
        <p> </p> (text will normally be in a paragraph, blockquote or list.)
        
        <blockquote> </blockquote> (could be used to quote text from a donor agreement.)
        
        </userestrict>
        
        <phystech><p> </p></phystech> May be used to note physical characteristics of the material or technical or system requirements to use material, e.g. hardware/software)
        
        <custodhist encodinganalog="561"> (Information about the chain of ownership or physical and intellectual custody of the materials being described.) (heading "Provenance: " will be supplied by system.)
        
        <p> </p> (text will be in a paragraph)
        
        </custodhist>
        
        <appraisal encodinganalog="583"> (provides information on the appraisal of the material) (heading "Appraisal Information will be supplied by system)
        
        <p> </p> (text will be in a paragraph)
        
        </appraisal>
        
        <processinfo encodinganalog="583"> (could be used to explain processing decisions, e.g., if collection has been significantly reprocessed.) (heading "Processing Information: " will be supplied by system)
        
        <p> </p> (text will be in a paragraph)
        
        </processinfo>
        
        <altformavail encodinganalog="530"> (used to indicate if the material is available in an alternate format, e.g., microfilm) (heading "Alternate Format: " will be supplied by system )
        
        <p> </p> (text will be in a paragraph) can repeat if necessary
        
        <prefercite="524"> (provides an example of the preferred from of citation) (heading "Preferred Citation: " will be supplied by system)
        
        <p> </p> (text will be in a paragraph)
        
        </prefercite
      - </descgrp>
    - - <controlaccess> (A container element that bundles subordinate <controlaccess> elements for subject, form and genre, and contributor terms, the authoritative forms for key access points, each has attribute values to indicate MARC field equivalent and authority source, e.g., lcsh, lcnaf, lctgm) (heading "Subject Terms" supplied by system for outermost <controlaccess>, use nested <controlaccess> elements with <head>s to distinguish general subject terms, subjects for visual and sound material, form and genre terms and contribtuors)
      - <controlaccess > (values of authority attributes are examples, they may vary)
        
        <head>Subjects:</head> (heading supplied by tagger)
        
        <persname authority="lcnaf" encodinganalog="600"> </persname>
        
        <corpname authority="lcnaf encodinganalog="610"> </corpname>
        
        <famname authority="lcnaf" encodinganalog="100"> </famname>
        
        <subject authority="lcsh" encodinganalog="650"<subject>
        
        <occupation authority="lcsh|aat|etc encodinganalog="656" </occupation>
        
        <geogname authority="lcsh" encodinganalog="655"> </geogname>
        
        </controlaccess>
        
        <head> Subject - Visual Materials:</head> (heading supplied by tagger)
        
        <persname authority="lcnaf" encodinganalog="600"> </persname>
        
        <corpname authority="lcnaf" encodinganalog="610"> </corpname>
        
        <famname authority="lcnaf" encodinganalog"600"> </famname>
        
        <subject authority="lcsh" encodinganalog="650"> <subject>
        
        <occupation authority="lcsh|aat|etc encodinganalog="656"> </occupation>
        
        <geogname authority="aacr2" encodinganalog="651"> </geogname>
        
        </controlacess>
        
        <controlaccess>
        
        <head>Form and Genre Terms</head>(Use to indicate collection has Diaries, Blueprints, Photographs, etc.) (supplied by tagger)
        
        <genreform authority="|aat|etc" encodinganalog="655">
        
        </controlaccess>
        
        <controlaccess >
        
        <head>Contributors: </head> (use for lists of correspondents) (supplied by tagger)
        
        <persname authority="lcnaf" =encodinganalog="700"> </persname>
        
        <corpname authority="lcnaf" encodinganalog="710"> </corpname>
        
        </controlaccess>
      - </controlaccess>
    - - <bioghist> (an essay or chronology providing biographical information about the individual(s) or family, or historical information about the corporate body responsible for creating or assembling the materials being described. The first paragraph should be a summary statement of this for the MARC 545 field)) (heading Biography or History will be supplied by system depending on value of Level attribute in <archdesc> either "collection" or "record group")
      - <bioghist><p> </p></bioghist>(the rest of the text will normally be entered in paragraphs. Lists, blockquotes, notes etc. can be used along with or within a paragraph. Multiple <bioghist>s with <head> could be used if a record group had several distinct creators, e.g., University President could have separate nested <bioghist> with <head> for each president.)
        
        <chronlist> (two column list with date and event or eventgroup) (might be used for such things as a list of deans or department chairs.)
        
        <head> </head> (optional heading for the list, supplied by tagger)
        
        <listhead> "date" </listhead> <listhead>"event" </listhead> (optional heading for columns, supplied by tagger)
        
        <chronitem><date> </date><event> </event> </chronitem>
        
        <chronitem><date> </date><eventgrp><event> </event><event> </event></eventgrp><chronitem>
        
        <chronlist>
        
        <bioghist>
      - </bioghist>
      - <arrangement> (Provides information on the organization and arrangement of the materials being described in the encoded finding aid such as the logical and physical hierarchical groupings into which the materials have been organized. This is the equivalent of the summary contents list BHL often uses. Should normally include short narrative introduction and then a nested list of series and subseries titles, as appropriate to the compelxity of the records, with inclusive box ranges indicated.) (heading "Arrangement of the Papers" or "Arrangement of the Records" based on value of the level attribute in <archdesc> will be supplied by system. Replaces deprecated <organization> element)
      - <p> </p> (text will normally be entered in paragraphs, lists, blockquotes, etc. can be used along with or within a paragraph.)
        
        <list type="simple">
        
        <item>
        
        <list type="simple">
        
        <item> </item>
        
        </list>
        
        </item>
        
        <item> </item>
        
        <list>
      - </arrangement>
    - - <scopecontent encodinganalog="520"> (A prose statement summarizing the information on the scope and content of the materials being described, including form and arrangement of the materials as well as the names of organizations, individuals, events, places, and topics documented in the materials This scope and content note will be used to describe the entirety of the collection. More detailed series descriptions will be incorporated into the series entries in the contents list. (heading "Collection Scope and Content Note" will be supplied by system.)
      - <scopecontent><p> </p></scopecontent>
        
        <p> </p> (text will normally be entered in paragraphs, lists, blockquotes, etc. can be used within a paragraph.)
        
        <scopecontent>
      - <odd> </odd> (Other Descriptive Data, a catch all element to accommodate finding aid features that don't fit into other EAD structures, can be used directly in <archdesc> or in any of the <c0X>s, can contain paragraphs, lists, tables, etc.)
    - - <dsc type=combined> (Information describing logical and/or physical hierarchical groupings of the materials being described at a detailed level. In BHL usage this is the box list.) Required type attribute supplies a more specific designation than the one given in the element name, legal values are analyticover |combined |indepth |othertype. BHL usage will normally be combined.
      - NOTE: Container information will be attached to each file|item that is the lowest level (highest component number) in any given hierarchy, attributes for containertype and label will be set. Only the number or other value will be included in the container element, the system will supply a heading based on the label attribute value.
      - <c01 level="subgrp|series|subgroup|file|item> (system will insert the "heading" "Series: " or "Subgroup: " based on the value of the level attribute, only for subgroup and series, e.g., Series: Topical File, 1995-1997 (1.5 ft.) (if unit of description is an accession set attribute as level="othertype" othertype="accession", in practice we will try to avoid using accessions as a unit of description)
        
        <did>
        
        <unititle>series title<unitdate type="inclusive|bulk> date(s) </unitdate> </unittitle> (system will supply comma and space between title and date if needed, if "title" is a "date" use unitdate inside unittitle)
        
        <physdesc><extent>X linear ft.|2 folders </extent></physdesc> (system will supply opening and closing parens for <physdesc>
        
        <physdesc><physfacet>1 7/8 ips, 7 inch reel</physfacet></physdesc>
        
        </did>
        
        <note><p> </p></note> (use for explanatory or parenthetical notes that should not be considered part of "unittitle proper". can use multiple notes, tagger must supply appropriate parens or brackets, system will supply space between <physdesc> and <notes>) (notes can be placed within the <did> element if it is "fundamental descriptive information", as a rule BHL style will put parenthetical notes outside the <did>)
        
        <accessrestrict><p> [Restricted unitl <date normal=20250101>Jan. 1, 2025 </date>]</accessrestrict> (will be used primarily in university record groups to indicate closure status and expiration dates. e.g. Dean Search Committee Files [CLOSED until 2010], by convention we will set restriction statements off with square brackets)
        
        <scopenote><p> </p></scopenote> (heading "Scope and Content Note: " will be inserted by the system)
        
        <c02 level="series|subseries|file|item"> (all elements used in c01 can be used in lower elements, <scopenote> would rarely be used below c04)
        
        <unittitle> <unitdate>text</unitdate></unittitle><physdesc><extent> </extent></physdesc> </did><scopenote><p> </p></scopenote>
        
        <c03 level=file|item>did><container type="box label="Box"> # </container>< unittitle>title text <unitdate> date</unitdate> </unittitle> <physdesc><extent> </extent></physdesc> </did> </c03> (level="file|item" is the default for c0X elements, )
        
        <c03 level=unspecified><did><container type=container label="box">container=folder> X</container> <unittitle> title text <unitdate> date</unitdate></unittitle></did></c03 level="file|item">
        
        <c04> </c04></c03> etc., potentially down to <c012> see below for possible structures)
        
        </c02> (could repeat for a new subseries or file,)
        
        </c01>
        
        <c01> (repeat when a new series begins)
        
        <c02> etc.</c02>
        
        </c01>
        
        </dsc>
      - <descgrp type="add"> (used in place of deprecated Adjunct Descriptive Data element, a generic container element for bundling information that is useful for interpreting, managing or augmenting the materials being described. The type attribute is set to "add" to distinguish it from other uses. A <dscgrp type="add"> element can contain such items as indices, lists of related or separated material, fileplans and bibliographies. <dscgrp> can be used directly in <archddesc> or in any of the <c0X> elements. In BHL practice would most likely be used for lists of correspondents, related collections or possibly bibliographies.) (heading "Additional Descriptive Information" will be supplied by the system if the <dscgrp type="add"> element is used)
        
        <relatedmaterial>
        
        <header> </header> (tagger supplies heading typically it will be "Related Material")
        
        <p> or <list> (text can appear in a paragraph, list or possibly other elements such as blockquote or title)
        
        <separated material> (use for statement about material removed from collection, either placed in another collection or discarded)
        
        <header> </header> (tagger supplies heading typically it will be "Separated Material"
        
        <p> or <list> (text can appear in a paragraph, list or possibly other elements such as blockquote)
        
        <bibliography>
        
        <head> </head> (tagger supplies heading typically it will be "Bibliography")
        
        <p> or <list> (bibref> <bibseries> and <title> elements could be used
        
        <index> (used to tag indexes or other supplementary information, e.g., index to correspondents)
        
        <head> </head> (heading will be supplied by tagger)
        
        <indexentry> (wrapper element containing the index term, usually a name of subject, and the reference)
        
        <persname> <persname>
        
        <ref> </ref> (<ref> data will typically be the date of a letter or letters, data can be entered directly into <ref> , but BHL will typically use a <list> to format the data)
        
        <table> </table> (see below for details on table element)
        
        </indexentry>
        
        <index>
        
        <fileplan> (used to describe classification plan or scheme for physical arrangement, storage and retrieval of files used by the individual or organization creating or compiling the records)
        
        <head> </head> (tagger supplies the heading)
        
        <p> </p> <p> or <list> (text can appear in a paragraph, list or possibly other elements such as blockquote or title)
        
        </fileplan>
        
        <descgrp> </dscgrp> (A nested element to bundle that does not fit into one of the above elements. Will usually contain a <head> and some combination of <p> <list> or other formatting element.)
        
        </descgrp>
      - </archdesc>
    - </ead>
    - The access terms sub-elements can be outside of the <controlaccess> section, in both the narrative and container list portions of finding aids. They will display as inline text. Names and subject terms would appear in natural language order. The normal attribute can be used to supply the controlled version of the name or term. To date BHL has not done extensive subject markup outside of <controlaccess> except for selected (usually older) finding aids which have indexes to correspondents.
    - - <persname> (use without authority attribute for name in natural order)
      - <family name>
      - <corpname>
      - <geogname>
      - <occupation>
      - <subject>
      - <genreform> In the contents list, certain forms of material should be identified with a <genreform> tag to permit easier retrieval of specific forms such as photographs or sound recordings. If a collection has a series/subseries/file of photographs, e.g., the unittitle of the highest level <c0X> directly containing the photographs should include a genreform tag in unittitle with the normal attribute set to a value from a standard list of genre terms. This will identify the entire region defined by the <c0X> containing the <genreform> element as photographs.
      - Table Element
      - An EAD table can occur almost anywhere in a finding aid. Tables are rare in Bentley practice but would most likely occur in the <descgrp type="add"> section, in a nested <dscgrp> (an exception is the specialized table <chronlist> which is sometimes used in the <bioghist> section.)
      - <dscgrp>
      - <head> <head> (heading supplied by tagger)
        
        <table>
        
        <tablegroup cols=X> (required cols attribute specifies number of columns in table
        
        <tablebody>
        
        <row>
        
        <thead> </thead> (table head use to provide headings for columns, repeat for each colum)
        
        </row>
        
        <row> <entry> </entry><entry> </entry> </row> (align and valign attributes may be used
        
        </tablebody>
        
        <tablegroup>
        
        <table>
      - </dscgrp>
    Possible EAD <c0x> structures for Bentley finding aids
    
    (all within <ead><archdesc><dsc>, unitdate, physdesc, note tags are not shown, <c0x> can continue down through <c12>) at the file or item level)
- 1) f.a. with subgroup, series, subseries, sub-subseries, file|item
  - <c01 level="subgrp"><did><unittitle>title</unittitle<did>
  - - <c02 level="series><did><unittitle>series title</unittitle></did>
    - - <c03 level="subseries"><did><unittitle>subseriestitle</unittitle></did>
        
        <c04 level="sub-subseries"><unittitle>sub-subseriestitle</unittitle></did>
        
        <c05 level="file"><did><container label="Box" type="box> # </container><unittitle>file title</unittitle></did>
        
        <c05 level="file"><did><container label="Box" type="box> # </container><unittitle>file|item title</unittitle></did>
- 2) f.a. with subgroup, series, subseries, file|item
- - <c01 level="subgrp"><did><unittitle>title</unittitle<did>
    - <c02 level="series><did><unittitle>series title</unittitle></did>
    - - <c03 level="subseries"><unittitle>subseriestitle</unittitle></did>
      - <c04 level="file"><did> <container type="box label="Box"> # </container><unittitle>file|itemtitle</unittitle></did>
        
        <c04 level="file"><did> <container type="box label="Box"> # </container><unittitle>file|item title</unittitle></did>
- 3.) f.a. with subgroup, series, file|item
- - <c01 level="subgrp"><did><unittitle>title</unittitle<did>
  - - <c02 level="series><did><unittitle>series title</unittitle></did>
    - - <c03 level="file"><did><container label="Box" type="box> # </container><unittitle>file|item title</unittitle></did>
      - <c03 level="file"><did><container label="Box" type="box> # </container><unittitle>file|item title</unittitle></did>
- 4.) f.a. with series, subseries, sub-subseries file|item
- - <c01 level="series"><did><unittitle> series title</unittitle<did>
  - - <c02 level="subseries"><unittitle>subseriestitle</unittitle></did>
    - - <c03 level="sub-subseries"><unittitle>sub-subseriestitle</unittitle></did>
      - <c04 level="file"><did><container label="Box" type="box> # </container><unittitle>file|itemtitle</unittitle></did>
        
        <c04 level="file"><did><container label="Box" type="box> # </container><unittitle>file|itemtitle</unittitle></did>
- 5.) f.a. with series, subseries, file|item
- - <c01 level="series"><did><unittitle> series title</unittitle<did>
  - - <c02 level="subseries"><unittitle>subseriestitle</unittitle></did>
    - - <c03 level="file"><did><container label="Box" type="box> # </container><unittitle>file title</unittitle></did>
      - <c03 level="file"><did><container label="Box" type="box> # </container><unittitle>file title</unittitle></did>
- 6.) f.a. with series, file|item
- - <c01 level="series"><did><unittitle> series title</unittitle<did>
  - - <c02 level="file"><did><container label="Box" type="box> # </container><unittitle>file|item title</unittitle></did>
    - <c02 level="file"><did><container label="Box" type="box> # </container><unittitle>file|item title</unittitle></did>
- 7.) f.a. with file/item only, no series
- - <c01 level="file|item"> <did><container label="Box" type="box> # </container><unittitle>file|item title</unittitle></did></c01>

Bentley Library EAD 2002 Tag Set

Possible EAD <c0x> structures for Bentley finding aids