60 likes | 186 Views
OAI and EAD. Chris Prom University of Illinois Archives. EAD/OAI Issues. Should we map whole finding aid? Context for “hits”-- representing hierarchical inheritance What level of materials are being described? EAD’s flexibility as a data structure standard. EAD/OAI Study.
E N D
OAI and EAD Chris Prom University of Illinois Archives
EAD/OAI Issues • Should we map whole finding aid? • Context for “hits”-- representing hierarchical inheritance • What level of materials are being described? • EAD’s flexibility as a data structure standard
EAD/OAI Study • Study of encoding patterns • Basic metadata elements exist in many finding aids • Lack of standardization • Unique encoding practices • Empty or near empty records; • Some lack key metadata elements • Little use of content standards like APPM, LCSH, LCNAF • Archivists’ workflow difficulties • Preprint: http://web.library.uiuc.edu/ahx/workpap/ • OAI may help harmonize differences in markup protocols and provide better access
Mapping EAD to OAI • Use one master record • represent hierarchy using mini records • Xpointer • //dsc[1]/c01[2]/c02[3]/c03[10] • When EADs are split into their subordinate components, XPointers identify the individual parts and link them together • Server-side scripts use the XPointers for rendering and linking • unbundles EAD while preserving context on output
Index and Search Issues • Size of EAD finding aids: 1 EAD can result on 1000’s of DC records • Frequently occurring search term can overwhelm results list • http://oai.grainger.uiuc.edu/oai/search/ • working on revised mapping
Work to Do • Upcoming article--Reengineering Archival Access Through the OAI Protocols • Does it scale? • Will archival community embrace OAI? • Build OAI support into Archivist Workbench tools? • Issue White Paper with technical and mapping details • Follow on (production level) grant/project?