Encoded Archival Description

Encoded Archival Description (EAD) is an XML standard for encoding archival finding aids, maintained by the Technical Subcommittee for Encoded Archival Description of the Society of American Archivists, in partnership with the Library of Congress.[1]

History

EAD originated at the 1993 Society of American Archivists annual meeting in New Orleans and was headed by Daniel Pitti at the University of California, Berkeley.[2] The project's goal was to create a data standard for describing archives, similar to the MARC standards for describing bibliographic materials. The initial EAD Version 1.0 was released in the fall of 1998.[3] Such a standard enables archives, museums, libraries, and manuscript repositories to list and describe their holdings in a manner that would be machine-readable and therefore easy to search, maintain and exchange.[4] Since its inception, many archives and special collections have adopted it.

In addition to the development and maintenance work done by the Society of American Archivists and the Library of Congress, the Research Libraries Group (RLG) has developed and published a set of "Best Practice" implementation guidelines[5] for EAD, which lays out mandatory, recommended, and optional elements and attributes. RLG has also provided a kind of clearinghouse for finding aids in EAD format, known as ArchiveGrid. Member libraries provide RLG the URL for their finding aids; RLG automatically harvests data from the finding aids, indexes it, and provides a search interface for the index, thus giving researchers the ability to search across several hundred institutions' collections with a single query. RLG also has developed the "RLG Report Card,"[6] an automated quality-checking program that will analyze an EAD instance and report any areas where it diverges from the best practices guidelines.

SAA's Technical Subcommittee for Encoded Archival Description, which include international representation, embarked on a revision of the EAD standard in 2010.[7] The latest version, EAD3, was released in August 2015.[8]

Adoption

A number of repositories in the United States, Canada, the United Kingdom, France, Australia and elsewhere have adopted and implemented EAD with varying levels of technical sophistication. One of the most ambitious efforts is the Online Archive of California, a union catalog of over 5000 EAD finding aids covering manuscripts and images from institutions across the state. The French National Library Francois Mitterrand publishes more than 90000 EAD finding aids covering archives and manuscripts.

EAD Element Set

The EAD standard's XML schema specifies the elements to be used to describe a manuscript collection as well as the arrangement of those elements (for example, which elements are required, or which are permitted inside which other elements). The EAD tag set has 146 elements and is used both to describe a collection as a whole, and also to encode a detailed multi-level inventory of the collection. Many EAD elements have been, or can be, mapped to content standards (such as DACS and ISAD(G)) and other structural standards (such as MARC or Dublin Core), increasing the flexibility and interoperability of the data.[9]

EAD 1.0 was an SGML document type definition (DTD). EAD 2002, the second incarnation of EAD, was finalized in December 2002 and made available as an XML DTD. The latest version of EAD, EAD3, is available as both an XML schema and a DTD.[10]

Parts of an EAD finding aid

Note: Examples in this section are EAD2, and may not be valid against the EAD3 schema.

eadheader

Note: In the current release of EAD3 1.0, the eadheader element has been replaced with the control element.[11]

The first section of an EAD-encoded finding aid is the eadheader. This section contains the title and optional subtitle of the collection and detailed information about the finding aid itself: who created it, when it was created, its revision history, the language the finding aid is written in, and so on. The eadheader itself has a number of required attributes that map to various ISO standards such as ISO 3166-1 for country codes and ISO 8601 for date formats.

The eadheader and its child elements can be mapped to other standards for easy interchange of information. They are often mapped to Dublin Core elements such as Creator, Author, Language. For example, in the excerpt below the relatedencoding="DC" attribute of the eadheader element specifies that child elements will be mapped to Dublin Core; the child element <author encodinganalog="Creator"> indicates that the EAD element <author> maps to the Dublin Core element <creator>.

Example of an eadheader:

<eadheader audience="internal" countryencoding="iso3166-1" 
dateencoding="iso8601" langencoding="iso639-2b" 
relatedencoding="DC" repositoryencoding="iso15511" 
scriptencoding="iso15924">
   <eadid countrycode="us" identifier="bachrach_lf" mainagencycode="NSyU">bachrach_lf</eadid>
   <filedesc>
      <titlestmt>
         <titleproper encodinganalog="Title">Louis Fabian Bachrach Papers</titleproper>
         <subtitle>An inventory of his papers at Blank University</subtitle>
         <author encodinganalog="Creator">Mary Smith</author>
      </titlestmt>
      <publicationstmt>
         <publisher encodinganalog="Publisher">Blank University</publisher>
         <date encodinganalog="Date" normal="1981">1981</date>
      </publicationstmt>
   </filedesc>
   <profiledesc>
      <creation>John Jones
         <date normal="2006-09-13">13 Sep 2006</date>
      </creation>
      <langusage>
         <language encodinganalog="Language" langcode="eng">English</language>
      </langusage>
   </profiledesc>
</eadheader>

archdesc

The archdesc section contains the description of the collection material itself. First, the Descriptive Identification or did element contains a description of the collection as a whole, including the creator (which may be an individual or an organization), size (usually given in linear feet), inclusive dates, language(s), and an abstract or brief description. As with the eadheader above, elements may be mapped to corresponding standards; elements in this section are usually mapped to MARC elements. For example, in the excerpt below the relatedencoding="MARC21" attribute of the archdesc element specifies that child elements will be mapped to MARC21; the child element <unittitle encodinganalog="245$a" label="Title: "> indicates that the unittitle element maps to MARC field 245, subfield a.

Example:

<archdesc level="collection" type="inventory" relatedencoding="MARC21">
   <did>
      <head>Overview of the Collection</head>
      <repository encodinganalog="852$a" label="Repository: ">Blank University</repository>
      <origination label="Creator: ">
         <persname encodinganalog="100">Brightman, Samuel C. (Samuel Charles), 1911-1992</persname>
      </origination>
      <unittitle encodinganalog="245$a" label="Title: ">Samuel C. Brightman Papers</unittitle>
      <unitdate encodinganalog="245$f" normal="1932/1992" type="inclusive" label="Inclusive Dates: ">1932-1992</unitdate>
      <physdesc encodinganalog="300$a" label="Quantity: ">
         <extent>6 linear ft.</extent>
      </physdesc>
      <abstract encodinganalog="520$a" label="Abstract: ">
          Papers of the American journalist including some war correspondence, 
          political and political humor writings, and adult education material
      </abstract>
      <unitid encodinganalog="099" label="Identification: " countrycode="us" repositorycode="NSyU">2458163</unitid>
      <langmaterial label="Language: " encodinganalog="546">
         <language langcode="eng">English</language>
      </langmaterial>
   </did>
</archdesc>

Several additional descriptive elements may follow the did including:

  • bioghist - biographic description of the person or organization
  • scopecontent - a detailed narrative description of the collection material
  • relatedmaterial - description of items which the repository acquired separately but which are related to this collection, and which a researcher might want to be aware of
  • separatedmaterial - items which the repository acquired as part of this collection but which have been separated from it, perhaps for special treatment, storage needs, or cataloging
  • controlaccess - a list of subject headings or keywords for the collection, usually drawn from an authoritative source such as Library of Congress Subject Headings or the Art and Architecture Thesaurus
  • accessrestrict and userestrict - statement concerning any restrictions on the material in the collection
  • arrangement - the way in which the materials in the collection are arranged

The second, and usually largest, section of the archdesc is the dsc, which contains a full inventory of the collection broken down into progressively smaller intellectual chunks. EAD offers two options: the c element which can be nested within itself to an unlimited level, and a set of numbered container elements c01 through c12 which can only be nested numerically (i.e. a c01 can contain only a c02; a c02 can contain only a c03, and so on). Note that the c and c0# elements refer to intellectual subdivisions of the material; the actual physical container is specified using the container element. The inventory may go down to as detailed a level as desired. The example below shows an inventory to the folder level.

Example of an inventory:

<dsc type="combined"><head>Inventory</head>
   <c01>
      <did>
        <unittitle>Correspondence</unittitle>
      </did>
      <c02>
         <did>
            <unittitle>Adams, Martha</unittitle>
            <unitdate normal="1962/1967">1962-1967</unitdate>
            <container type="box">1</container>
            <container type="folder">1</container>
         </did>
      </c02>
      <c02>
         <did>
            <unittitle>Barnett, Richard</unittitle>
            <unitdate normal="1965">1965</unitdate>
            <container type="box">1</container>
            <container type="folder">2</container>
         </did>
      </c02>
      ...etc
   </c01>
   <c01>
      <did>
        <unittitle>Writings</unittitle>
      </did>
      <c02>
         <did>
            <unittitle>Short stories</unittitle>
            <unitdate normal="1959/1979">1959-1979</unitdate>
            <container type="box">5</container>
            <container type="folder">1-9</container>
         </did>
      </c02>
   </c01>
</dsc>

Citing EAD

There have been some studies about how to cite EAD files with variable granularity. In particular, Buneman and Silvello[12] proposed a rule-based system to automatically create citation snippets to be used as references when citing XML data; a case study is based on EAD. Furthermore, Silvello[13] proposed a framework, which learning from examples, automatically creates references at different level of coarseness for XML files. This framework has been tested on the Library of Congress collection of EAD files.

Criticism

A user study[14] analyzing the user interaction patterns with finding aids highlighted that "[they] focus on rules for description rather than on facilitating access to and use of the materials they list and describe", and that many archive users have serious issues using finding aids. Common and frequent user interaction patterns with finding aids are navigational and thus they require to browse the archival hierarchy to make sense of the archival data.[15]

Some critics claim that EAD constrains researcher interaction because several operations are either impossible or inefficient.[16] For example, it is problematic to:

  • let the user access a specific item on-the-fly, since it requires defining fixed access points to the archival hierarchy;[17]
  • let the user reconstruct the context of an item without browsing the whole archival hierarchy;[18]
  • present the user with only selected items from an archive, since the finding aid presents a given collection as a whole.[19][20]

Furthermore, EAD allows for several degrees of freedom in tagging practice, which may turn out to be problematic in the automatic processing of EAD files, since it is difficult to know in advance how an institution will use the hierarchical elements. It has been underlined that only EAD files meeting stringent best practice guidelines are shareable and searchable.[21]

See also

References

  1. ↑ Stockting, B (2004). "Time to Settle Down? EAD Encoding Principles in the Access to Archives Programme (A2A) and the Research Libraries Group's Best Practice Guidelines". Journal of Archival Organization. 2 (3): 7–24. doi:10.1300/j201v02n03_02.
  2. ↑ Dooley, Jackie M., ed. (1998). Encoded Archival Description: Context, Theory, and Case Studies. Chicago: The Society of American Archivists. ISBN 0931828430.
  3. ↑ Pitti, Daniel V.; Duff, Wendy M., eds. (2001). Encoded Archival Description on the Internet. Binghamton, N.Y.: The Hawthorn Information Press. ISBN 0789013975.
  4. ↑ "Development of the Encoded Archival Description DTD".
  5. ↑ , RLG Best Practice Guidelines for Encoded Archival Description, 2002.
  6. ↑ , RLG EAD Report Card.
  7. ↑ "EAD Revision Under Way," Library of Congress, https://www.loc.gov/ead/eadrevision.html
  8. ↑ "EAD3 1.0 is available! | Society of American Archivists". www2.archivists.org. Retrieved 2015-10-19.
  9. ↑ Stockting, B (2004). "Time to Settle Down? EAD Encoding Principles in the Access to Archives Programme (A2A) and the Research Libraries Group's Best Practice Guidelines". Journal of Archival Organization. 2 (3): 7–24. doi:10.1300/j201v02n03_02.
  10. ↑ EAD schema and other files for download via GitHub
  11. ↑ "EAD: Encoded Archival Description (EAD Official Site, Library of Congress)". www.loc.gov. Retrieved 2016-01-06.
  12. ↑ Buneman, P. and Silvello, G. (2010). ‘A Rule-Based Citation System for Structured and Evolving Datasets’. IEEE Bulletin of the Technical Committee on Data Engineering, Vol. 3, No. 3. IEEE Computer Society, pp. 33-41, September 2010. Available online: http://sites.computer.org/debull/A10sept/buneman.pdf
  13. ↑ Silvello, G. (2016). ‘Learning to Cite Framework: How to Automatically Construct Citations for Hierarchical Data’. Journal of the Association for Information Science and Technology (JASIST), to appear, 2016. Pre-print available online: http://www.dei.unipd.it/~silvello/papers/2016-DataCitation-JASIST-Silvello.pdf
  14. ↑ Freund, L.; Toms, E. G. (2016). "Interacting with Archival Finding Aids". Journal of the Association for Information Science and Technology. 67 (4): 994–1008. doi:10.1002/asi.23436.
  15. ↑ N. Ferro and G. Silvello (2016). `From Users to Systems: Identifying and Overcoming Barriers to Efficiently Access Archival Data`. ACHS@JCDL 2016. http://ceur-ws.org/Vol-1611/paper2.pdf
  16. ↑ Ferro, N.; Silvello, G. (2013). "NESTOR: A Formal Model for Digital Archives". Information Processing & Management. 49 (6): 1206–1240. doi:10.1016/j.ipm.2013.05.001.
  17. ↑ N. Ferro and G. Silvello. A Methodology for Sharing Archival Descriptive Metadata in a Distributed Environment. In Proc. 12th European Conference on Research and Advanced Technology for Digital Libraries, pages 268–279. LNCS 5173, Springer, Germany, 2008.
  18. ↑ Daines, J. G.; Nimer, C. L. (2011). "Re-Imagining Archival Display: Creating User-Friendly Finding Aids". Journal of Archival Organization. 9 (1): 4–31. doi:10.1080/15332748.2011.574019.
  19. ↑ M. Y. Eidson. "Describing Anything That Walks: The Problem Behind the Problem of EAD", Journal of Archival Organization 1(4) 5–28, 2002.
  20. ↑ Roth, J. (2011). "Serving Up EAD: An Exploratory Study on the Deployment and Utilization of Encoded Archival Description Finding Aids". The American Archivists. 64 (2): 214–237.
  21. ↑ Prom, C.J., Rishel, C.A., Schwartz, S.W., Fox, K.J. (2007). "A Unified Platform for Archival Description and Access". In: Proc. 7th ACM/IEEE Joint Conference on Digital Libraries (JCDL 2007), pp. 157–166. ACM Press, New York (2007)
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.