<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE entry
  PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<entry>
    <url>http://www.mnhs.org/collections/manuscripts/manuscripts.htm</url>
    <institution>Minnesota Historical Society</institution>
    <updated>2007-02-19</updated>
    <delivery>
      <p> XML versions of finding aids are converted to HTML that may be accessed in three ways:
        through a link from the MARC record for the collection via our OPAC via a Web search engine
        such as Yahoo or Alta Vista. HTML &lt;meta&gt; tags are generated automatically from
        the markup in the encoded finding aid during their transformation into HTML to facilitate
        indexing by these services through a link from pages on our Web site that list significant
        collections by subject matter</p>
      <p>The transformation from EAD in XML syntax into HTML is done through the use of an
        XSL stylesheet and James Clark's XT program, a free XSL processor application. This
        operation is done in batch mode. The original source XML and HTML versions then are mounted
        in a single directory on our Web site. The same process, employing a second stylesheet, is
        used to generate a print copy of the finding aid for our reading room. Finding aids are also
        accessible via RLG's Archival Resources service which is available to researchers in our
        reading room.</p>
    </delivery>
    <encoding>
      <p>The Minnesota Historical is currently revising its authoring process. For newly
        processed collections, separate techniques are used to create the collection level portion
        of the finding aid and the description of the components section. The collection-level data
        is harvested from the MARC record which is typically prepared before the rest of the finding
        aid. The MARC record is downloaded from the OPAC. Logos Research's marcxml.exe program then
        converts that file from the MARC transmission format into the MARC DTD format. The resulting
        XML file is then converted into an EAD instance using an XSL stylesheet and James Clark's
        xt.exe program. A single batch process executes all these steps. The resulting XML file is
        then loaded into the XMetaL application wherein the cataloger simply completes the
        &lt;eadheader&gt; data and/or augments the description with expanded scope and
        content, biographical, or organization information depending on the complexity of the
        materials. The description of the components section is created in either of two ways. For
        small collections with short contents listings, the cataloger adds the &lt;dsc&gt;
        portion directly to the file in XMetaL using a series of keyboard macros. For longer
        contents listings, we find it more flexible to create the text in Microsoft Word, convert
        that document into XML using the Microsoft SGML Author for Word software described below,
        and append it to the XML file. Using SGML Author for Word to encode the text involves the
        following tools:</p>
      <p>Microsoft Word for Windows 95 Generic, off-the-shelf version. Microsoft SGML Author for
        Word A Microsoft application that is a generic tool for transforming Word documents into
        SGML instances (and visa versa). The converter works by associating a Word "style" in the
        source document with a corresponding SGML element. For example, the MHS inventory template
        includes a style called "BiogPara." During conversion, the text defined by that style is
        wrapped with the EAD string
        &lt;bioghist&gt;&lt;p&gt;...&lt;/p&gt;&lt;/bioghist&gt;.
        Microsoft Templates, Styles, and Macros Locally developed applications of standard Word
        features. Styles produce a consistent presentation by applying to document text standard,
        predefined font types, sizes, and weights, tabbing, indention, and line spacing. They are
        embedded within templates which carry standardized "boilerplate" text and which serve as the
        basis for the conversion to SGML process. Macros are used to facilitate the application of
        styles and reduce the number of keystrokes required. The creation and use of these functions
        are described in any comprehensive Word manual. SX A freeware SGML parser that also converts
        SGML files to XML syntax. Using SGML Author for Word to encode the text involves the
        following steps: Open a Word template and draft the contents listing. This is done by the
        processing archivist. Once the editorial review process is complete, the text is forwarded
        to the departmental conversion coordinator who completes the remaining steps. Create the EAD
        instance: run the SGML Author converter by selecting the Save As SGML option on the Word
        File menu. Run the sx.exe application to parse the resulting SGML document and convert it
        into XML syntax. Append the file to the end of the document create in XMetaL as described
        above. </p>
    </encoding>
    <contact>Dennis Meissner, Head of Collections Management <a href="mailto:dennis.meissner@mnhs.org">dennis.meissner@mnhs.org</a>
    </contact>
    <rlg> Yes</rlg>
  </entry>
