Successfully reported this slideshow.

EAD Workshop, Queens College, 4-22-2013

632 views

Published on

Published in: Education
  • Be the first to comment

  • Be the first to like this

EAD Workshop, Queens College, 4-22-2013

  1. 1. Queens College GSLIS 1
  2. 2. OutlineI. The BasicsII. Finding Aid Quiz and BreakIII. Implementation 2
  3. 3. Relax! 3
  4. 4. I. The Basics 4
  5. 5. I. Basics What is EAD? XML standard for encoding finding aids 5
  6. 6. I. Basics - What is EAD? XML standard for encoding finding aids XML (eXtensible Markup Language): a set of rules for structuring data via markup 6
  7. 7. I. Basics - What is EAD? XML standard for encoding finding aids Tag: <unitdate era=“ce”>2013</unitdate> Attribute: <unitdate era=“ce”>2013</unitdate> Element: <unitdate era=“ce”>2013</unitdate> 7
  8. 8. I. Basics - What is EAD? XML standard for encoding finding aids Elements and attributes defined by a Document Type Definition (DTD) or a Schema <bioghist> <bionote> 8
  9. 9. I. Basics - What is EAD? XML standard for encoding finding aids <ead> <eadheader> <titleproper>Guide to the Papers of Joseph Roth </titleproper> </eadheader> </ead> 9
  10. 10. I. Basics - What is EAD? XML standard for encoding finding aids Defined set of containers for descriptive data EAD : DACS = MARC : AACR2/RDA 10
  11. 11. I. Basics - What is EAD? XML standard for encoding finding aids A description of records that gives the repository physical and intellectual control over the materials and that assists users to gain access to and understand the materials (SAA) Describing Archives: A Content Standard (DACS) 11
  12. 12. I. Basics What is EAD? XML standard for encoding finding aids 12
  13. 13. I. Basics What is EAD? EAD encoding is not a substitute for sound archival description! 13
  14. 14. I. Basics A Brief Aside: DACSDescribing Archives: A Content Standard “rules to ensure the creation of consistent, appropriate, and self- explanatory descriptions of archival material.” 14
  15. 15. I. Basics - A Brief Aside: DACS“DACS defines twenty-five elements that are useful in creating systems for describing archival materials.” 15
  16. 16. I. Basics - A Brief Aside: DACS Seven Element Types• Identity• Content and Structure• Conditions of Access and Use• Acquisition and Appraisal• Related Materials• Notes• Description Control 16
  17. 17. I. Basics - A Brief Aside: DACS “Not all of the DACS elements are required in every archival description.” 17
  18. 18. I. Basics - A Brief Aside: DACS Statement of PrinciplesPrinciple 7: Archival descriptions may bepresented at varying levels of detail toproduce a variety of outputs. 18
  19. 19. I. Basics - A Brief Aside: DACS Principle 7• 7.1: Levels of description correspond to levels of arrangement.• 7.2: Relationships between levels of description must be clearly indicated.• 7.3: Information provided at each level of description must be appropriate to that level. 19
  20. 20. I. Basics - A Brief Aside: DACS DACS revision underway 20
  21. 21. I. Basics 21
  22. 22. II. Finding Aid 22
  23. 23. II. Finding Aid EAD Finding Aid Structure <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE ead SYSTEM "ead.dtd"> or <ead xsi:schemaLocation="urn:isbn:1-931666-22-9 http://www.loc.gov/ead/ead.xsd"> 23
  24. 24. II. Finding Aid EAD Finding Aid Structure<ead> <eadheader>Information about repository and finding aid</eadheader> <archdesc>Description of archival materials</archdesc></ead> 24
  25. 25. II. Finding Aid Common Tags <eadheader>• EAD Identifier<eadid mainagencycode="NyNyCJH" countrycode="us" encodinganalog="856$u" publicid="-//us::nnlbi//TEXT us::nnlbi::JustinMueller.xml//EN">JustinMueller.xml</eadid> 25
  26. 26. II. Finding Aid Common Tags <eadheader>• Finding aid author<titlestmt> <author>Processed by Stanislav Pejša.</author></titlestmt> 26
  27. 27. II. Finding Aid Common Tags <archdesc>• Minimum required description – “high-level did”<did> <origination>Mueller, Justin J.</origination> <unittitle>Justin J. Mueller Collection</unittitle> <unitdate>undated, 1890-2005</unitdate> <abstract>[short descriptive text]</abstract> […] 27
  28. 28. II. Finding Aid Common Tags <archdesc>• Minimum required description – “high-level did”<did> […] <langmaterial>In German and English</langmaterial> <physdesc>1 linear foot</physdesc> <unitid>AR 10254</unitid> <repository>Leo Baeck Institute</repository> <physloc>V 11/2</physloc></did> 28
  29. 29. II. Finding Aid Common Tags <archdesc>• Biographical information<bioghist><p>Joseph Roth was one of the most prominent Austrian writers of the first half of the 20th century.</p></bioghist>• Controlled vocabulary<geogname encodinganalog="651$a" source="lcsh" authfilenumber="n79040121">Austria</geogname> 29
  30. 30. II. Finding Aid Common Tags <archdesc>• Description of Subordinate Components<dsc><c01 level="series"> <c02>Folder 1 <c03>Item 1</c03> <c03>Item 2</c03> </c02> <c02>Folder 2</c02></c01> 30
  31. 31. II. Finding Aid Common Tags <archdesc>• Description of Subordinate ComponentsA Component <c> provides information about the content, context, and extent of a subordinate body of materials.Each <c> element identifies an intellectually logical section of the described materials. The physical filing separations between components do not always coincide with the intellectual separations.From EAD Tag library <http://www.loc.gov/ead/tglib/elements/c.html> 31
  32. 32. II. Finding Aid Common Tags <archdesc>• Description of Subordinate Components<dsc><c01 level="series"> <did> <unittitle id="serII">Series II: Publications</unittitle> <unitdate normal="1985/1996">1985-1996</unitdate> </did> <c02>Subordinate intellectual parts, e.g. folders</c02></c01> 32
  33. 33. II. Finding Aid Common Tags <archdesc>• Description of Subordinate Components<c02> <did> <container type="box">2</container> <container type="folder">1</container> <unittitle>Articles</unittitle> <unitdate>1985-1994</unitdate> </did></c02> 33
  34. 34. II. Finding Aid Common Tags <archdesc>• Description of Subordinate Components<c02> <did> <container type="box">OS 145</container> <container type="folder">1</container> <unittitle>Newspaper foldout</unittitle> <unitdate>1996</unitdate> </did></c02> 34
  35. 35. II. Finding Aid Common Tags – Human Readable? <dimensions> 35
  36. 36. II. Finding Aid Common Tags – Human Readable? <dimensions>A subelement of <physdesc> for information about the size of the materials being described; usually includes numerical data. 36
  37. 37. II. Finding Aid Common Tags – Human Readable? <famname> 37
  38. 38. II. Finding Aid Common Tags – Human Readable? <famname>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. 38
  39. 39. II. Finding Aid Common Tags – Human Readable? <revisiondesc> 39
  40. 40. II. Finding Aid Common Tags – Human Readable? <revisiondesc>An optional subelement of the <eadheader> for information about changes or alterations that have been made to the encoded finding aid. 40
  41. 41. II. Finding Aid EAD Finding Aid 41
  42. 42. II. Finding Aid Quiz 42
  43. 43. III. Implementation 43
  44. 44. III. Implementation: Creating EAD 44
  45. 45. III. Implementation: Creating EAD Archivists’ Toolkit Archon ArchivesSpace 45
  46. 46. III. Implementation: Creating EAD ICA-AtoM 46
  47. 47. III. Implementation: Creating EAD oXygen 47
  48. 48. III. Implementation: Creating EAD NoteTab Dreamweaver EADitor Note Pad 48
  49. 49. III. Implementation: Creating EAD PASCL spreadsheet “the spreadsheet from heaven” 49
  50. 50. III. Implementation: Creating EAD My Workflow 50
  51. 51. III. Implementation: Using EAD 51
  52. 52. III. Implementation: Using EAD Now What? 52
  53. 53. III. Implementation: Using EAD XSLT 53
  54. 54. III. Implementation: Using EAD XSLT 54
  55. 55. III. Implementation: Using EAD EAD to HTML 55
  56. 56. III. Implementation: Using EAD EAD to HTML with DC 56
  57. 57. III. Implementation: Using EAD EAD to PDF 57
  58. 58. III. Implementation: Using EAD EAD to MARC 58
  59. 59. III. Implementation: Using EAD Other Uses• Integration with other standards (e.g. EAC-CPF)• Open Archives Initiative – Protocol for Metadata Harvesting (OAI-PMH)• EAD consortia• Metadata for digitized collections 59
  60. 60. III. Implementation: Using EAD Other Uses• Flexible search and display 60
  61. 61. III. Implementation: Using EAD Resources 61
  62. 62. III. Implementation: Using EAD EAD Tag Library 62
  63. 63. III. Implementation: Using EAD SAA Standards Portal 63
  64. 64. III. Implementation: Using EAD SAA EAD Roundtable 64
  65. 65. III. Implementation: Using EAD EAD Tools 65
  66. 66. III. Implementation: Using EAD Tinker!• Learn more about XML and XSLT• Download the free trial of oXygen XML editor, the schema, an EAD finding aid, and a stylesheet.• Try some basic actions: add a folder, change a controlled vocabulary term, remove a series. 66
  67. 67. III. Implementation: Using EAD The Future of EADAlpha release of EAD revision, February 2013• Reduce semantic overload• Simplify and standardize links• Reduce mixed content• Add, deprecate, and delete elements 67
  68. 68. III. Implementation: Using EAD The Future of EAD• Revision is schema-based – goodbye, DTD• LC stylesheet: dtd2schema.xsl• “Attribute validation errors indicate that the attribute value does not conform to the ruling ISO standard” 68
  69. 69. III. Implementation: Using EAD The Future of EAD• Beta release of schema, documentation, and migration tools, July 1, 2013• New version of EAD released with tag library and migration tools, Winter 2014 slideshare.net/mikerush/ead-revision-progress-report-20120808 4/01/2013 email from Mike Rush to EAD listserv 69
  70. 70. III. Implementation: Using EAD The Future of EAD“In an ideal world, EAD and EAC-CPF would beopaque to all but a few expert users, created whenneeded as secondary outputs from efficient andadaptable software tools with archivist-optimizedinterfaces.” Thirty Years On: SAA and Descriptive Standards 70
  71. 71. III. Implementation: Using EAD The Future of EAD“This next wave [of archival standards] is going topush beyond online versions of print-baseddocument genres and embrace the Web as thenative format for description—dynamic, diverse,and discoverable description.” Thirty Years On: SAA and Descriptive Standards 71
  72. 72. III. Implementation: Using EAD Relax! http://www.slideshare.net/archivistkevin 72

×