A basic presentation prepared for Queens College (CUNY) Graduate School of Library and Information Science, May 2011. Describes what EAD is, how it is created, and how it is implemented.
40. Download via Slideshare: http://www.slideshare.net/archivistkevin/a-brief-introduction-to-encoded-archival-description Twitter @archivistkevin Thank you!
Notas do Editor
Recent grad, now a processing archivist. New archivists point of view. Thank colleague and fellow alum Ryan Mendenhall, with whom I developed this presentation. EAD is not scary!
http://www.flickr.com/photos/carowallis1/2314716161/sizes/m/in/photostream/ Will be available on slideshare – many links on images and in text in the later portion of the presentation
Familiar with html? Similar (tags aka mark-up), but data structure, not display
Common that programs will display tags in different color, to help differentiate markup from content
http://www.flickr.com/photos/johnkay/3539126525/sizes/m/in/photostream/ Note that it is hierarchical – nested. Parent elements apply to child elements.
Encoding standards are rules for defining buckets; content standards are rules for the information inside http://www.flickr.com/photos/linneberg/4481309196/sizes/m/in/photostream/
DTD and schema define the buckets; the list of tags in the tag library (we’ll see later) is defined here. Move to schema is coming; more flexible; not something you need to know right away http://www.flickr.com/photos/linneberg/4481309196/sizes/m/in/photostream/
Encoding standards are rules for making the buckets; content standards are rules for the information inside
An EAD-encoded finding aid is split into info about institution/FA (metametadata) and info about materials (the finding aid)
http://findingaids.cjh.org/?pID=1165371 {here we will go through the first 200 lines or so Abelmann FA in the firefox or IE “view source” panel} How do we get HTML? Via XSLT – a transformation. In a bit more detail later.
Extremely unlikely you will be asked to type it all out by hand. Temples, programs, guidance.
Software is free (like kittens, not like beer) Designed by archivists: interface is intuitive Manages most common archival processes Designed for metadata standards Output – html, ead Built on a database (MySQL)
Web-based, but still need MySQL backend EAD import/export SAA archon webinar Sandbox on archon website: <http://www.archon.org/sandbox.php> Going to be combined with AT
Basic, powerful XML editor. You can safely ignore about 95% of the buttons and drop-downs, but will do things like suggest valid tags and attributes, close tags, and validate as you go. This is what we use.
Notetab Pro Text editor In conjunction with free downloads from EAD Cookbook Free, once installed reasonably friendly
https://code.google.com/p/eaditor/ More complex but powerful tool – works on native XML, not database (like AT/archon). For the pro implementor.
A simple text editor – OK for simple tinkering; hard to actually use.
http://www.loc.gov/ead/tglib/element_index.html
XSLT (Extensible Stylesheet Language Transformations) is a declarative, XML-based language used for the transformation of XML documents. Here, the EAD tag processinfo is converted into HTML.
XSLT (Extensible Stylesheet Language Transformations) is a declarative, XML-based language used for the transformation of XML documents. Here, the EAD tag processinfo is converted into HTML.
http://www.aaa.si.edu/collections/online Hard to predict, but the data are structured so you can be flexible.