Encoded Archival Description (EAD)
What is EAD ? <ul><li>EAD stands for Encoded Archival Description, and is a non-proprietary  de facto  standard for the en...
<ul><li>Data  structure  : a body of containers or wrappers of data </li></ul><ul><li>Data  value  : controlled vocabulari...
Structure is not content !! <ul><li>EAD is a data structure and not a data content standard. It does not prescribe how one...
EAD is hierarchical  <ul><li>Following traditional archival theory, EAD flows from the general to the granular </li></ul><...
EAD is DTD <ul><li>EAD is a Document Type Definition : a set of markup declarations that define a document type.  </li></u...
EAD Elements   <ul><li>EAD elements are structured metadata that allow for easy identification and universal acceptance ac...
EAD Elements <ul><li>Tag library is available on the EAD website.  </li></ul>
EAD Tag Library
<ul><li>Tag Name:  Short, mnemonic form of the element name that is used in the machine-readable encoded document. </li></...
<ul><li>May contain:  Identifies what may occur within the element being defined. Elements are listed in alphabetical orde...
<ul><li>May occur within:  Identifies all of the parent elements within which the described element may appear, listed in ...
The Three <ul><li>Three  major  ( required ) components of an EAD document:  </li></ul><ul><li>EAD:  <ead> </li></ul><ul><...
EAD: Group Exercise One <ul><li>For each of the three required or major EAD elements outlined,  <ead>,   <eadheader> , <ar...
Encoded Archival Description:   <ead> <ul><li><ead>  is the outermost wrapper  element defines a particular instance of a ...
EAD Header :   <eadheader> <ul><li>A wrapper element for bibliographic and descriptive information about the finding aid d...
Archival Description :   <archdesc> <ul><li>A wrapper element for the bulk of an EAD document instance, which describes th...
Description of Subordinate Components :   <dsc> <ul><li>A wrapper element that bundles information about the hierarchical ...
Attributes <ul><li>EAG tags are robust due to attributes.  Attributes reflect named properties of an element and may take ...
Attributes <ul><li><persname   encodinganalog=   &quot;100&quot;   label=   &quot;Creator:&quot;   source=   “ulan&quot;  ...
Attributes <ul><li>Most attributes are optional and of the type called  #IMPLIED  (i.e. the attribute is not required. If ...
Attributes <ul><li>The value of attributes may be constrained by the DTD using specific attribute type values. For example...
Attributes <ul><li>CDATA: --   Character data . No markup is recognized within a CDATA value except for character referenc...
The 9 elements <ul><li><ead>  </li></ul><ul><li><eadheader>  </li></ul><ul><li><eadid>[...]</eadid>  </li></ul><ul><ul><li...
EAD: Group Exercise Two <ul><li>Given that only 9 of 146 elements are required to be a valid EAD document, many local inst...
Research Library Groups (RLG)   Best Practices guidelines for Encoded Archival Description <ul><li>Required  and   Mandato...
Research Library Groups (RLG)   Best Practices guidelines for Encoded Archival Description <ul><ul><li><profiledesc> </li>...
Research Library Groups (RLG)   Best Practices guidelines for Encoded Archival Description <ul><ul><ul><li><repository> </...
Research Library Groups (RLG)   Best Practices guidelines for Encoded Archival Description <ul><ul><ul><li><accessrestrict...
Research Library Groups (RLG)   Best Practices guidelines for Encoded Archival Description <ul><ul><ul><li><dsc>  Single <...
Research Library Groups (RLG)   Best Practices guidelines for Encoded Archival Description <ul><ul><ul><li><c>/<c0x>  Numb...
<ul><li>Created in 2002, the RLG EAD BPG is considered the core resource for establishing BPG’s at institutions  </li></ul...
EAD: Individual Exercise <ul><li>Open up the XML editor oXygen </li></ul><ul><li>Open the following file in the XML editor...
EAD: Individual Exercise <ul><li>Utilizing what you’ve learned with the EAD tag library, hand code the attached sheet   </...
EAD: Individual Exercise <ul><li>Now open the following file in the XML editor oXygen :   Links_Hall_EAD_Finding Aid_Compl...
EAD: Individual Exercise <ul><li>This is what the handout looks like on ouput:   </li></ul>
Wrappers and wrappers
Wrappers and wrappers <ul><li>Metadata curation is key </li></ul><ul><li>Local usage and local schemas drive which tags to...
Wrappers and wrappers <ul><li><genreform></genreform> </li></ul><ul><li>A term that identifies the types of material being...
Local Usage <ul><li><c   level=   &quot;item&quot;   > </li></ul><ul><li><did> </li></ul><ul><li><unitid   countrycode=   ...
Unit id:  001-1121  Box:  1  Title:   Drapery – Study Date:  circa 1920s  Dimensions:  11 x 8 ½ inches  Medium:  Graphite ...
EAD: Seduction of the Complex <ul><li>Do not be seduced by complexity: EAD is, at its core, a simple structure </li></ul><...
EAD: Seduction of the Complex <ul><li>Complexity of description depends on the needs of the collection.  </li></ul><ul><li...
Upcoming SlideShare
Loading in...5
×

Encoded Archival Description (EAD)

4,348

Published on

A presentation of an EAD workshop I led at Pratt Institute's School of Information & Library Science

Published in: Technology, Education
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
4,348
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Encoded Archival Description (EAD)

  1. 1. Encoded Archival Description (EAD)
  2. 2. What is EAD ? <ul><li>EAD stands for Encoded Archival Description, and is a non-proprietary de facto standard for the encoding of finding aids for use in a networked (online) environment. </li></ul><ul><li>Finding aids are inventories, indexes, or guides that are created by archival and manuscript repositories to provide information about specific collections. While the finding aids may vary somewhat in style, their common purpose is to provide detailed description of the content and intellectual organization of collections of archival materials. </li></ul><ul><li>EAD allows the standardization of collection information in finding aids within and across repositories. </li></ul>
  3. 3. <ul><li>Data structure : a body of containers or wrappers of data </li></ul><ul><li>Data value : controlled vocabularies to populate data structures </li></ul><ul><li>Data content : guidelines for for syntax of data values </li></ul>What is EAD ? <ul><li>(EAD, CDWA) </li></ul><ul><li>(DACS, CCO) </li></ul>(LCSH, AAT)
  4. 4. Structure is not content !! <ul><li>EAD is a data structure and not a data content standard. It does not prescribe how one formulates the data that appears in any given data element. </li></ul><ul><li>EAD focuses on the structural content of archival description, not on its presentation. </li></ul>
  5. 5. EAD is hierarchical <ul><li>Following traditional archival theory, EAD flows from the general to the granular </li></ul><ul><li>Utilizes Extensible Markup Language (XML) </li></ul><ul><li>XML is a set of “elements” that conform to to a set of rules known as a Document Type Definition (DTD) </li></ul>
  6. 6. EAD is DTD <ul><li>EAD is a Document Type Definition : a set of markup declarations that define a document type. </li></ul><ul><li>An EAD document must be validated against a DTD. In other words, you CANNOT CREATE wrappers, you must conform to tag elements within EAD DTD. </li></ul>?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot; standalone=&quot;no&quot;?> <!DOCTYPE ead PUBLIC &quot;+//ISBN 1-931666-00-8//DTD ead.dtd Encoded Archival Description (EAD) Version 2002//EN&quot; &quot;ead.dtd&quot;> <ead>
  7. 7. EAD Elements <ul><li>EAD elements are structured metadata that allow for easy identification and universal acceptance across institutions (such as ) </li></ul><ul><li>and union catalogs ( ) . </li></ul>
  8. 8. EAD Elements <ul><li>Tag library is available on the EAD website. </li></ul>
  9. 9. EAD Tag Library
  10. 10. <ul><li>Tag Name: Short, mnemonic form of the element name that is used in the machine-readable encoded document. </li></ul><ul><li>Element Name: Expanded version of the tag name which more fully describes the element's meaning. </li></ul><ul><li>Description: The first paragraph of the description defines the element by drawing from terminology in archival glossaries, basic dictionaries, and data dictionaries such as ISAD(G), MARC21, the  Categories for the Description of Works of Art , and the Text Encoding Initiative DTD </li></ul>
  11. 11. <ul><li>May contain: Identifies what may occur within the element being defined. Elements are listed in alphabetical order by tag name. Elements may be empty (e.g., containing only an attribute); or they may contain text (called #PCDATA); other elements; or a mixture of text and other elements. </li></ul><ul><ul><li>The abbreviation #PCDATA (parsed character data) means that text content is allowed directly inside of an element, but the text cannot include characters that would be interpreted by a parser as action codes. For example, a left angle bracket has to be represented as the character entity reference &lang; so that it is not misinterpreted as the start of an element name. </li></ul></ul><ul><ul><li>The list of nested elements usually includes more elements than are generally needed, because similar elements sharing the same content model travel together as a group. This is a device to ease the authoring of a DTD and to aid machine processing of encoded documents. For example, once one reference element such as <ref> is listed under May contain, all the reference elements appear, including <archref>, <bibref>, <extptr>, <extref>, and <ptr>, even though the simple internal <ref> element is the most likely choice in a particular context. </li></ul></ul>
  12. 12. <ul><li>May occur within: Identifies all of the parent elements within which the described element may appear, listed in alphabetical order by tag name. This information conveys the sense of where and how often an element is available throughout the DTD. Definitions for parent elements may provide additional information about an element's usage. </li></ul><ul><li>Attributes: Identifies all attributes that can be associated with an element. Attributes are represented in lowercase letters in XML coding, but the Online EAD Tag Library uses the convention of capital letters to distinguish attributes from elements within the tag library context. See the EAD Attributes section of the tag library for definitions and additional information </li></ul>
  13. 13. The Three <ul><li>Three major ( required ) components of an EAD document: </li></ul><ul><li>EAD: <ead> </li></ul><ul><li>EAD Header : <eadheader> </li></ul><ul><li>Archival Description : <archdesc> </li></ul><ul><li>**Description of Subordinate Components : <dsc> </li></ul><ul><li>[Not required, but major: occurs within <archdesc>] </li></ul>
  14. 14. EAD: Group Exercise One <ul><li>For each of the three required or major EAD elements outlined, <ead>, <eadheader> , <archdesc> , <dsc> consult the EAD tag library and list what elements may be contained in each and what may occur within. </li></ul>
  15. 15. Encoded Archival Description: <ead> <ul><li><ead> is the outermost wrapper element defines a particular instance of a document encoded with the EAD Document Type Definition. </li></ul><ul><li>It contains a required <eadheader>, optional <frontmatter>, and a required <archdesc> element, in that order. </li></ul>
  16. 16. EAD Header : <eadheader> <ul><li>A wrapper element for bibliographic and descriptive information about the finding aid document rather than the archival materials being described. </li></ul><ul><li>The <eadheader> is required, because information that was often unrecorded for a local paper finding aid is essential in a machine-readable environment. </li></ul><ul><li>Four subelements are available, which must occur in the following order: < eadid> (required), <filedesc> (required), <profiledesc> (optional), and <revisiondesc> (optional). </li></ul><ul><li>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. </li></ul>
  17. 17. Archival Description : <archdesc> <ul><li>A wrapper element for the bulk of an EAD document instance, which describes the content, context, and extent of a body of archival materials, including administrative and supplemental information that facilitates use of the materials. </li></ul><ul><li>Information is organized in unfolding, hierarchical levels that allow for a descriptive overview of the whole to be followed by more detailed views of the parts, designated by the element Description of Subordinate Components <dsc> . </li></ul><ul><li>The Descriptive Identification <did> element is required to appear in <archdesc> before presenting more detailed descriptions in <bioghist>, <scopecontent> , and <dsc> , in order to provide first a basic description of the archival materials. </li></ul><ul><li>Data elements available at the <archdesc> level are repeated at the various component levels within <dsc> , and information is inherited from one hierarchical level to the next. </li></ul>
  18. 18. Description of Subordinate Components : <dsc> <ul><li>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. </li></ul>
  19. 19. Attributes <ul><li>EAG tags are robust due to attributes.  Attributes reflect named properties of an element and may take on different values, depending on the context in which they occur.  </li></ul><ul><li><[tag] [attribute] = “[value]” > </li></ul>
  20. 20. Attributes <ul><li><persname encodinganalog= &quot;100&quot; label= &quot;Creator:&quot; source= “ulan&quot; > Schapiro, Meyer </persname> </li></ul>
  21. 21. Attributes <ul><li>Most attributes are optional and of the type called #IMPLIED (i.e. the attribute is not required. If no attribute value is specified, a processing program may infer a value) </li></ul><ul><li>Two attributes are flagged as #REQUIRED , that is, the LEVEL attribute on <archdesc> and <archdescgrp>, and the COLS attribute on <tgroup> </li></ul><ul><li>Two attribute are #FIXED the LINKTYPE attribute on <arc> and <archref> </li></ul>
  22. 22. Attributes <ul><li>The value of attributes may be constrained by the DTD using specific attribute type values. For example, &quot;id&quot; attribute is of type ID, which constrains its value to a string beginning with an alphabetic character. An &quot;id&quot; value must be unique within the EAD instance within which it occurs, that is, no other tag in the entire document can have the same &quot;id&quot; value. Most EAD attributes are of type CDATA, which means that any text characters may be used. </li></ul>
  23. 23. Attributes <ul><li>CDATA: -- Character data . No markup is recognized within a CDATA value except for character references. If the characters < (less than), > (greater than), & (ampersand), ' (apostrophe), or &quot; (quotation) are used, they must be escaped using a character reference. </li></ul><ul><li>ID: -- Unique identifier. For example, most elements have an ID attribute, so that a unique code can be established for and used to refer to that specific element. The content of the ID attribute is of the type called &quot;id.&quot; Parsers verify that the value of attributes of type &quot;id&quot; are unique. ID attribute values must begin with an alpha, not numeric, character, either upper or lowercase, and may contain a . (period), : (colon), - (hyphen), or _ (underscore), but not a blank space. See also attributes of type &quot;idref.&quot; </li></ul><ul><li>NMTOKEN: -- A name token, which can consist of any alpha or numeric character, as well as a . (period), : (colon), - (hyphen), or _ (underscore), but not a blank space. A number of attributes in EAD where a character string from a code list is to be used are NMTOKEN. </li></ul>
  24. 24. The 9 elements <ul><li><ead> </li></ul><ul><li><eadheader> </li></ul><ul><li><eadid>[...]</eadid> </li></ul><ul><ul><li><filedesc> </li></ul></ul><ul><li><titlestmt> </li></ul><ul><li><titleproper>[...]</titleproper> </li></ul><ul><li></titlestmt> </li></ul><ul><li></filedesc> </li></ul><ul><li></eadheader> </li></ul><ul><li><archdesc level= “collection” > </li></ul><ul><li><did>[...]</did> </li></ul><ul><li><dsc type= &quot;combined” >[...]</dsc> </li></ul><ul><li></archdesc> </li></ul><ul><li></ead> </li></ul>
  25. 25. EAD: Group Exercise Two <ul><li>Given that only 9 of 146 elements are required to be a valid EAD document, many local institutions create Better Practice Guidelines (BPG) </li></ul><ul><li>In groups of two, consult the Research Library Group (RLG) Best Practices guidelines for Encoded Archival Description and list the Required (R) and Mandatory (M) elements for each institution </li></ul>
  26. 26. Research Library Groups (RLG) Best Practices guidelines for Encoded Archival Description <ul><li>Required and Mandatory </li></ul><ul><ul><li><ead> </li></ul></ul><ul><ul><li><eadheader> </li></ul></ul><ul><ul><ul><li>langencoding= Set to &quot;iso639-2b.” </li></ul></ul></ul><ul><ul><ul><li>relatedencoding= MARC or DublinCore </li></ul></ul></ul><ul><ul><ul><li>repositoryencoding= Set to &quot;iso15511.” </li></ul></ul></ul><ul><ul><ul><li>countryencoding= Set to &quot;iso3166-1.” </li></ul></ul></ul><ul><ul><ul><li>dateencoding= Set to &quot;iso8601.” </li></ul></ul></ul><ul><ul><li><eadid> </li></ul></ul><ul><ul><ul><li>countrycode= Use ISO 3166-1. </li></ul></ul></ul><ul><ul><ul><li>mainagencycode= MARC Code List for Organizations </li></ul></ul></ul><ul><ul><li><filedesc> </li></ul></ul><ul><ul><ul><li><titlestmt> </li></ul></ul></ul><ul><ul><ul><ul><li><titleproper> </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>encodinganalog= </li></ul></ul></ul></ul></ul><ul><ul><ul><li><publicationstmt> </li></ul></ul></ul><ul><ul><ul><ul><li><publisher> </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>encodinganalog= </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><li><date> </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>encodinganalog= </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>normal= Use ISO 8601. </li></ul></ul></ul></ul></ul>
  27. 27. Research Library Groups (RLG) Best Practices guidelines for Encoded Archival Description <ul><ul><li><profiledesc> </li></ul></ul><ul><ul><ul><li><creation> </li></ul></ul></ul><ul><ul><ul><ul><li>encodinganalog= </li></ul></ul></ul></ul><ul><ul><ul><li><langusage> </li></ul></ul></ul><ul><ul><ul><ul><li><language> </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>encodinganalog= </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>langcode= Use ISO 639-2b. </li></ul></ul></ul></ul></ul><ul><ul><li><archdesc> </li></ul></ul><ul><ul><ul><ul><li>level= Most commonly set as fonds (use collection or recordgrp as applicable). This element is considered an essential element for data exchange by ISAD(G)v2. </li></ul></ul></ul></ul><ul><ul><ul><ul><li>relatedencoding= </li></ul></ul></ul></ul><ul><ul><ul><li><did> </li></ul></ul></ul><ul><ul><ul><ul><li><origination> </li></ul></ul></ul></ul><ul><ul><ul><ul><li><unittitle> </li></ul></ul></ul></ul><ul><ul><ul><ul><li><unitdate> </li></ul></ul></ul></ul><ul><ul><ul><ul><li>type= </li></ul></ul></ul></ul><ul><ul><ul><ul><li>normal= Use ISO 8601 </li></ul></ul></ul></ul><ul><ul><ul><li>< physdesc> </li></ul></ul></ul><ul><ul><ul><ul><li><extent> </li></ul></ul></ul></ul>
  28. 28. Research Library Groups (RLG) Best Practices guidelines for Encoded Archival Description <ul><ul><ul><li><repository> </li></ul></ul></ul><ul><ul><ul><li><unitid> </li></ul></ul></ul><ul><ul><ul><ul><li>countrycode= Use ISO 3166-1. </li></ul></ul></ul></ul><ul><ul><ul><ul><li>repositorycode= Use ISO 1551. </li></ul></ul></ul></ul><ul><ul><ul><li><langmaterial> </li></ul></ul></ul><ul><ul><ul><ul><li><language> </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>langcode= Use ISO 639-2b. </li></ul></ul></ul></ul></ul><ul><ul><ul><li><bioghist> </li></ul></ul></ul><ul><ul><ul><li><scopecontent> If organization/arrangement cannot readily be separated from the scope note, give as part of <scopecontent>. If separable, use <arrangement> and do not nest within <scopecontent>. </li></ul></ul></ul>
  29. 29. Research Library Groups (RLG) Best Practices guidelines for Encoded Archival Description <ul><ul><ul><li><accessrestrict> Use for conditions governing access. </li></ul></ul></ul><ul><ul><ul><li><userestrict> Use for conditions governing access </li></ul></ul></ul>
  30. 30. Research Library Groups (RLG) Best Practices guidelines for Encoded Archival Description <ul><ul><ul><li><dsc> Single <dsc> model should be used with nested components in which descriptions for subfonds, series, subseries, file, and item are placed at teha ppropriate level in the component hierarchy </li></ul></ul></ul><ul><ul><ul><li><c>/<c0x> Numbered and unnumbered components are functionally equivalent. Use of the numbered components may providea more readily intelligible view of the nested structure to the human eye and may make machine manipulation easier. Only one of the options can be used in a given <dsc> Institutions are urged to adopt one model or the other as standard practice. Nested <c>/<c0x>s should be used as needed to reflect the intellectual structure of the archival materials. The full suite of subelements and attributes described are available at each component level. </li></ul></ul></ul><ul><ul><ul><ul><li>level=&quot;subfonds/series/file” The levels of the components should be subordinate to the level set for in <archdesc> (see &quot;Archival Levels,&quot; page 6). This element is considered an essential element for data exchange by ISAD(G)v2. </li></ul></ul></ul></ul><ul><ul><ul><li><did> </li></ul></ul></ul><ul><ul><ul><li><unittitle> Considered the minimum for description at component levels because some description is needed for users to decide if documents are worthy of further investigation. </li></ul></ul></ul>
  31. 31. Research Library Groups (RLG) Best Practices guidelines for Encoded Archival Description <ul><ul><ul><li><c>/<c0x> Numbered and unnumbered components are functionally equivalent. Use of the numbered components may providea more readily intelligible view of the nested structure to the human eye and may make machine manipulation easier. Only one of the options can be used in a given <dsc> Institutions are urged to adopt one model or the other as standard practice. Nested <c>/<c0x>s should be used as needed to reflect the intellectual structure of the archival materials. The full suite of subelements and attributes described are available at each component level. </li></ul></ul></ul><ul><ul><ul><ul><li>level=“item” All of the general guidelines for components apply to item-level <c>s and if the component links to a digital object, the following guidelines also apply. </li></ul></ul></ul></ul><ul><ul><ul><li><did> </li></ul></ul></ul><ul><ul><ul><ul><li><daogrp> Required for linking to digital archival objects </li></ul></ul></ul></ul><ul><ul><ul><ul><li><daoloc> Required for linking to digital archival objects </li></ul></ul></ul></ul>
  32. 32. <ul><li>Created in 2002, the RLG EAD BPG is considered the core resource for establishing BPG’s at institutions </li></ul><ul><li>Library of Congress and Online Archive of California are two of the largest institutions to follow and expand on RLG guidelines </li></ul>Research Library Groups (RLG) Best Practices guidelines for Encoded Archival Description
  33. 33. EAD: Individual Exercise <ul><li>Open up the XML editor oXygen </li></ul><ul><li>Open the following file in the XML editor oXygen : Links_Hall_EAD_Finding Aid_Skeleton.xml </li></ul>
  34. 34. EAD: Individual Exercise <ul><li>Utilizing what you’ve learned with the EAD tag library, hand code the attached sheet </li></ul><ul><li>Double check your work between your hand coding and the tags on the screen </li></ul>
  35. 35. EAD: Individual Exercise <ul><li>Now open the following file in the XML editor oXygen : Links_Hall_EAD_Finding Aid_Complete.xml </li></ul>
  36. 36. EAD: Individual Exercise <ul><li>This is what the handout looks like on ouput: </li></ul>
  37. 37. Wrappers and wrappers
  38. 38. Wrappers and wrappers <ul><li>Metadata curation is key </li></ul><ul><li>Local usage and local schemas drive which tags to use, for example: </li></ul><ul><li><genreform></genreform> </li></ul><ul><li>Vs. </li></ul><ul><li><physfacet></physfacet> </li></ul>
  39. 39. Wrappers and wrappers <ul><li><genreform></genreform> </li></ul><ul><li>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. </li></ul><ul><li><physfacet></physfacet> </li></ul><ul><li>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. 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. </li></ul>
  40. 40. Local Usage <ul><li><c level= &quot;item&quot; > </li></ul><ul><li><did> </li></ul><ul><li><unitid countrycode= &quot;us&quot; repositorycode= &quot;nnc-rb &quot; > 001-1121 </unitid> </li></ul><ul><li><container type= &quot;Box&quot; label= &quot;Box&quot; >1 </container> </li></ul><ul><li><unittitle> </li></ul><ul><li><title render= &quot;italic&quot; >Drapery - Study </title> </li></ul><ul><li></unittitle> </li></ul><ul><li><unitdate> 1920s </unitdate> </li></ul><ul><li><physdesc> </li></ul><ul><li><dimensions unit= &quot;inches&quot; >11 x 8 1/2 </dimensions> </li></ul><ul><li><genreform> Graphite on detached diary page </genreform> </li></ul><ul><li></physdesc> </li></ul><ul><li></did> </li></ul><ul><li><scopecontent> </li></ul><ul><li><p> Inscribed on verso, marked &quot;3&quot;. </p> </li></ul><ul><li></scopecontent> </li></ul><ul><li></c> </li></ul>
  41. 41. Unit id: 001-1121 Box: 1 Title: Drapery – Study Date: circa 1920s Dimensions: 11 x 8 ½ inches Medium: Graphite on detached diary page Note: Inscribed on verso, marked &quot;3”
  42. 42. EAD: Seduction of the Complex <ul><li>Do not be seduced by complexity: EAD is, at its core, a simple structure </li></ul><ul><li>To be a valid (i.e. compliant) EAD document, a finding aid only needs 9 elements </li></ul>
  43. 43. EAD: Seduction of the Complex <ul><li>Complexity of description depends on the needs of the collection. </li></ul><ul><li>Consult More Product, Less Process (MPLP) for minimal processing guidelines. </li></ul>

×