How do the following ideas strike you all as a summary of "ead lite"
tagging? Debate and suggestions are invited.
I had offered to start this conversation last April because our approach
to tagging the existing, fairly detailed (60 page) NAACP Visual Materials
finding aid aimed for a minimalist approach. Then the phrase "ead lite"
(like 'tei lite'?) surfaced, and Anne Mitchell helped me fish out what
seemed to be the NAACP tagging patterns.
Although interested in feedback, I'll leave to the application
guidelines, SAA CAIE EAD group, and others to sort out an actual "ead
Helena Zinkham phone: (202) 707-2922
Prints & Photographs Div. fax: (202) 707-6647
Library of Congress email: [log in to unmask]
Washington, DC 20540-4840
EAD - LITE
+ Reduce costs by saving time spent on content analysis and tagging
+ Speed tagging of more finding aids by tagging at a basic level
+ Simplify understanding of EAD core structures
+ Enable non-archivists to provide basic tagging (?)
+ Be clear about what you might lose in current and future
display, retrieval, or printing of a finding aid text by not
tagging it as specifically as the EAD tags make possible.
1. Focus on tags that identify large structural blocks
Designate <admininfo>, then rely on paragraphs <p> rather than mark
individual sentences as <altformavail> or <userestrict>.
Use <head> tag in elements to provide clear table of contents
navigation in an SGML browser.
2. Focus on tags that simple SGML viewers can display
Use the <c> <did> approach for container lists, rather than
the <drow> <dentry> approach.
3. Focus on tags that capture core content of collection, to aid
retrieval of information among many finding aids in a pool. Tag
high-level elements specifically; skip lower-level tags and
attributes. Invest in tagging that contributes most to
structured retrieval and display; rely on keyword retrieval for
words in areas such as <chronlist> and <dsc>.
a) Tag each element in the <archdesc> <did>.
b) Tag the key names that surface in <scopecontent>; don't tag each
<persname> or set attributes on elements in a container list; don't tag
parts of sentences as separate elements, e.g., don't use <organization>
element for a few words in midst of a <scopecontent> element; don't tag
the <date> element in a container list <unittitle>; tag the <title> in a
<bibref> but not all the other possible subelements.
c) Tag elements that provide high-level information filters for a
retrieval system, e.g., Broad topic, Geographic, Chronologic, Language
4. Establish a template approach to <eadheader> elements and to
<archdesc> <did> elements.
5. Add <ref> tags to aid user navigation within a finding aid,
e.g., from description of series to container list.
COULD ALSO MEAN:
6. Tag as specifically as the data makes easy. Assign many tags,
because automation skills or available software, plus
consistently formatted data make it possible to set up strings of
very specific elements and attributes that are easily assigned.
NAACP TAGGING THAT ILLUSTRATES EAD-LITE IDEAS
(Note: Most but not all attributes and elements used in LC,
Prints & Photos finding aid for NAACP are listed below.)
(Note: Declared entities for digital object or external pointers
in the EAD document, since less than 10 entities. For a
digitized collection, would set up a separate declaration
<ead> includes encodinganalog attribute
<eadheader> includes findingaidstatus attribute
<filedesc> ... (template approach with boilerplate data content for
<titlestatement> <titleproper> <subtitle>; <author>; <date>)
<profiledesc> ... (boilerplate)
<frontmatter> ... (if have a "how to use the finding aid" section)
<did> (with encodinganalog and label att. for each subelement)
<daodesc> image sampler
<controlaccess> <subject> <formgenre>
(with encodinganalog attributes)
<ref> to areas of <add> that have full <userestrict> or
<chronlist> <chronitem> <event | eventgroup> <date>
<ref> to areas of first <dsc>
<dsc> with attribute for .....
<c> <did> <unitid> (with <ref> to container list);
<unittitle> </did> <scopecontent> </c>
(No <unitdate> or <persname> ...)
<dsc> with attribute for container list
<c> <did> <unitid> <unittitle>
<c> <did> <unittitle> (recursively)
<c> <did> <unittitle> <unitid> (bottom level)
<indexentry> <name> <ref>
<div> (Microfilm concordance)
<defitem> <label> <item>
<div> (Sections on repro restrictions, ordering copies)
Use?: Langmaterial attribute?