XML instances are indexed by OpenText/LiveLink, along with a variety of non-EAD HTML files, to create a combined index. For Beinecke library, Divinity Library, and Manuscripts and Archives, XML files are processed against XSL style sheets to create hard-coded HTML versions, using a homegrown program built around MicroSoft's MSXML3 parser, or XSLTProc (Manuscripts and Archives). Each XML instance generates two HTML files: a content file and a navigator, generated by two different style sheets. When the style sheets create these content and navigator files, they insert javascript coding that allows hyperlinking between the two. These files sit in a directory parallel to the XML file and are pointed to from the OpenText results pages. The Music Library supplies an XML file for indexing and a suite of frames-linked HTML files for display (A decision was made to use these "canned" versions of converted files to: 1. allow access from both Netscape and IE & 2. to speed up file delivery). All files, then, can be viewed using any standard web browser. Instances are in EAD 1.0.
For Beinecke Library and the Divinity Library: Source files (ASCII for Beinecke; Wordperfect for Divinity) are run through a series of macros, developed in-house, which add markup. Some manual editing is required in all files, to add links, etc. . Instances are checked against IE. After corrections are made, instances are saved in UNIX format. Two-part HTML equivalents are made to accompany the XML instance (explained above). After this, they are ready to be indexed.
For Manuscripts and Archives: OpenOffice [ http://www.openoffice.org ] based template, which is then processed using XSLT and Perl to create EAD v1.0. For additional information contact stephen.yearl@yale.edu
The Yale Music Library has contracted with ArchProteus to convert WordPerfect or typewritten finding aids into EAD. ArchProteus supplies the Music Library with an XML instance (used for indexing in the Yale finding aid database) and an HTML version for end users.