Add file for 1.6 branch.

[working/Evergreen.git] / 2.0 / development / customize_opac.xml

<?xml version="1.0" encoding="utf-8"?>\r
<chapter xml:id="Customizing_OPAC" xmlns="http://docbook.org/ns/docbook" version="5.0" xml:lang="EN"\r
    xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xlink="http://www.w3.org/1999/xlink">\r
        <info>\r
                <title>Customizing the OPAC</title>\r
        </info>\r
        <para>While Evergreen is ready to go out of the box, libraries will want to customize Evergreen with their own color scheme, logos and layout. This chapter will explain how to \r
        customize Evergreen to meet the needs of your users. For these task some knowledge of <systemitem>html</systemitem> and <systemitem>css</systemitem> is required. Many of these \r
        instructions assume an installation of Evergreen using the default file locations.</para>\r
        <note>\r
                <para>Be sure to save a backup copy of all files you edit in a location other than <filename class="directory">/openils/var/web/opac/</filename> as files here could be \r
                overwritten when you upgrade your copy of Evergreen.</para>\r
        </note> \r
        <section xml:id="ColorScheme">\r
                <title>Change the Color Scheme</title>\r
                <indexterm><primary>OPAC</primary><secondary>customizing</secondary><tertiary>changing the color scheme</tertiary></indexterm>\r
                <para>To change the color scheme of the default Evergreen skin, edit <filename>/openils/var/web/opac/theme/default/css/colors.css</filename>. From this one file you can \r
                change the 4 base color scheme as well as colors of specific elements.     \r
                </para>                                                  \r
                <para>You can also create alternate themes for your users.</para>     \r
                <procedure>\r
                        <step>\r
                                <para>Copy the css folder and its contents from the example alternate theme <filename>/openils/var/web/opac/theme/reddish/</filename> \r
                                to a new folder <filename>/openils/var/web/opac/theme/<emphasis>[your new theme]</emphasis>/</filename>.</para>\r
                        </step> \r
                        <step>\r
                                <para>Edit <filename>/openils/var/web/opac/theme/<emphasis role="bold">[your new theme]</emphasis>/css/colors.css</filename> to use the colors you want.</para>\r
                        </step>\r
                        <step>\r
                                <para>Link to your new style sheet by adding the following to <filename>/openils/var/web/opac/skin/default/xml/common/css_common.xml</filename>.</para>\r
<programlisting language="xml">\r
&lt;link type='text/css'\r
rel="alternate stylesheet"  \r
title='&amp;opac.style.yourtheme;'  \r
href="&lt;!--#echo var='OILS_THEME_BASE'--&gt;/yourtheme/css/colors.css" \r
name='Default' csstype='color'/&gt;\r
</programlisting> \r
                        </step> \r
                        <step>\r
                                <para> Give your new theme a name users can select by adding the following to <filename>/openils/var/web/opac/locale/<emphasis role="bold">\r
                                [your locale]</emphasis>/opac.dtd</filename>.</para>\r
                                <screen>&lt;!ENTITY opac.style.yourtheme "YourTheme"&gt;</screen>       \r
                        </step> \r
                </procedure>    \r
        </section>\r
        <section xml:id="customizing_opac_text">\r
                <title>customizing Opac Text and Labels</title>\r
                <indexterm><primary>OPAC</primary><secondary>customizing</secondary><tertiary>text and labels</tertiary></indexterm>\r
                <para>To change text and links used throughout the OPAC, edit the following files:</para>\r
                <itemizedlist>\r
                        <listitem><filename>/openils/var/web/opac/locale/<emphasis role="bold">[your locale]</emphasis>/lang.dtd</filename></listitem>\r
                        <listitem><filename>/openils/var/web/opac/locale/<emphasis role="bold">[your locale]</emphasis>/opac.dtd</filename></listitem>\r
                </itemizedlist>\r
                <tip>\r
                        <para>A better way to customize OPAC text is to create custom dtd files for your lang and opac customizations and then add a include \r
                        statement above the default dtd files.</para>\r
                <programlisting>\r
                &lt;!DOCTYPE html PUBLIC \r
                "-//W3C//DTD XHTML 1.0 Transitional//EN"\r
                "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd" [\r
                &lt;!--#include virtual="/opac/locale/${locale}/custom_opac.dtd"--&gt;\r
                &lt;!--#include virtual="/opac/locale/${locale}/opac.dtd"--&gt;\r
                ]&gt;\r
                </programlisting>\r
                        <para>position is important here. The first/top included dtd files will take precedence over the subsequent dtd includes.</para> \r
                </tip>\r
                <para>While it is possible to add text to the xml files itself, it is a good practice to use the DTD file to control the text and refer to the DTD elements in the xml/html code.</para>   \r
                <para>For example, the <filename>footer.xml</filename> file has this code to generate a copyright statement:</para>\r
<programlisting>\r
&lt;div id='copyright_text'&gt;\r
&lt;span&gt;&amp;footer.copyright;&lt;/span&gt;\r
</programlisting>\r
                <para>The included <filename>opac.dtd</filename> file in the en-US locale directory has this setting for &amp;footer.copyright text:</para>  \r
                <programlisting>&lt;!ENTITY footer.copyright "Copyright &#xA9; 2006-2010 Georgia Public Library Service, and others"&gt;</programlisting>\r
        </section>\r
        <section xml:id="Logo_Images">\r
                <title>Logo Images</title>\r
                <para>To change the logos used by default to your own logos, replace the following files with images of your own, appropriately sized. </para>\r
                <itemizedlist>\r
                        <listitem>Large main logo:<filename>/openils/var/web/opac/images/main_logo.jpg</filename></listitem>\r
                        <listitem>Small logo:<filename>/openils/var/web/opac/images/small_logo.jpg</filename></listitem>\r
                </itemizedlist>                          \r
        </section>\r
        <section xml:id="AddedContent">\r
                <title>Added Content</title>\r
                <indexterm><primary>OPAC</primary><secondary>added content</secondary></indexterm>\r
                <para>By default Evergreen includes customizable <quote>Added Content</quote> features to enhance the OPAC experience for your user. These features include Amazon book covers \r
                and Google books searching. These features can be turned off or customized.</para>\r
                <simplesect xml:id="bookcovers">\r
                        <title>Book Covers</title>\r
                        <para>The default install of Evergreen includes Amazon book covers. The settings for this are controlled by the &lt;added_content&gt; section of \r
                        <filename>/openils/conf/opensrf.xml</filename>. Here are the key elements of this configuration:</para> \r
                        <programlisting>&lt;module&gt;OpenILS::WWW::AddedContent::Amazon&lt;/module&gt;</programlisting>\r
                        <para>This calls the Amazon perl module. If you wish to link to a different book cover service other than Amazon, you must create a new perl module and refer to it here. \r
                        You will also need to change other settings accordingly. There are some available book cover perl modules available in  \r
                        <ulink url="http://svn.open-ils.org/trac/ILS/browser/trunk/Open-ILS/src/perlmods/OpenILS/WWW/AddedContent">trunk</ulink></para>\r
                        <programlisting>&lt;base_url&gt;http://images.amazon.com/images/P/&lt;/base_url&gt;</programlisting>\r
                        <para>Base URL for Amazon added content fetching.  This URL may need to be shortened when new (read: non-image) content fetching \r
                        capabilities are added.</para>   \r
                        <programlisting>&lt;timeout&gt;1&lt;/timeout&gt;</programlisting>\r
                        <para>Max number of seconds to wait for an added content request to return data.  Data not returned within the timeout is considered a failure.</para>   \r
                        <programlisting>&lt;retry_timeout&gt;600&lt;/retry_timeout&gt;</programlisting>\r
                        <para>After added content lookups have been disabled due to too many lookup failures, this is the amount of time to wait before we try again.</para>\r
                        <programlisting>&lt;max_errors&gt;15&lt;/max_errors&gt;</programlisting>\r
                        <para>Maximum number of consecutive lookup errors a given process can live before added content lookups are disabled for everyone.</para>       \r
                        <programlisting>&lt;userid&gt;MY_USER_ID&lt;/userid&gt;</programlisting>\r
                        <para>If a userid is required to access the added content.</para>\r
                </simplesect>\r
                <simplesect xml:id="googlebookslink">\r
                        <title>Google Books Link</title>\r
                        <indexterm><primary>OPAC</primary><secondary>added content</secondary><tertiary>Google Books</tertiary></indexterm>\r
                        <para>The results page will display a <emphasis role="bold">Browse in Google Books Search</emphasis> link for items in the results page which have corresponding entries\r
                         in <systemitem class="resource">Google Books</systemitem>. \r
                        This will link to Google Books content including table of contents and complete versions of the work if it exists in Google Books. Items not in Google Books will not \r
                        display a link. This feature can be turned off by changing the googleBooksLink variable setting to <emphasis>false</emphasis> in the file \r
                        <filename>/openils/var/web/opac/skin/default/js/result_common.js</filename>. By default, this feature is activated. </para> \r
                </simplesect>\r
                <simplesect xml:id="addedcontent-syndetics">\r
                        <title>Syndetics</title><indexterm><primary>added content</primary><secondary>Syndetics</secondary></indexterm>\r
                        <para>Sydantics is another option for added content, Here is an example of using Sydantics as your added content provider:</para>\r
                        \r
<programlisting>\r
<![CDATA[\r
            <!-- We're using Syndetics -->\r
            <module>OpenILS::WWW::AddedContent::Syndetic</module>\r
            <base_url>http://syndetics.com/index.aspx</base_url>\r
\r
            <!-- A userid is required to access the added content from Syndetic. -->\r
            <userid>uneedsomethinghere</userid>\r
\r
            <!--\r
            Max number of seconds to wait for an added content request to\r
            return data.  Data not returned within the timeout is considered\r
            a failure\r
            -->\r
            <timeout>1</timeout>\r
\r
            <!--\r
            After added content lookups have been disabled due to too many\r
            lookup failures, this is the amount of time to wait before\r
            we try again\r
            -->\r
            <retry_timeout>600</retry_timeout>\r
\r
            <!--\r
            maximum number of consecutive lookup errors a given process can\r
            have before added content lookups are disabled for everyone\r
            -->\r
            <max_errors>15</max_errors>\r
\r
        </added_content>\r
]]>\r
</programlisting>\r
                        <note><para>Sydantics is a fee based service. For details, visit: <ulink url="http://www.bowker.com/syndetics/">http://www.bowker.com/syndetics/</ulink></para></note>  \r
                </simplesect>             \r
        </section>\r
        <section xml:id="resultspage">\r
                <title>Customizing the Results Page</title>\r
                <para>The results page is extremely customizable and allows some built in features to be activated with some simple edits or more advanced customizations can be done by more \r
                experienced web developers.</para>\r
                <para>There are several critical files to edit if you wish to  customize the results page:</para>\r
                <itemizedlist>\r
                        <listitem><filename>/openils/var/web/opac/skin/default/js/result_common.js</filename> - This file controls the JavaScript for the top level elements on the results \r
                        page and should only be edited by experienced web developers except for the <link linkend='googlebookslink'>Google books link setting</link> mentioned previously.</listitem>\r
                        <listitem><filename>/openils/var/web/opac/skin/default/js/rresult.js</filename> - Has some good controls of results page settings at the top of this file but \r
                        requires web development skills for editing this file.</listitem>\r
                        <listitem><filename>/openils/var/web/opac/skin/default/xml/result/rresult_table.xml</filename> - This controls the layout of the items table on results page.</listitem>\r
                </itemizedlist>          \r
        </section>\r
        <section xml:id="deatailspage">\r
                <title>Customizing the Details Page</title>\r
                <indexterm><primary>OPAC</primary><secondary>customizing</secondary><tertiary>details page</tertiary></indexterm>\r
                <para>There are many options when customizing the details page in Evergreen. The default settings are effective for most libraries, but it is important to understand the full potential \r
                of Evergreen when displaying the details of items.</para>               \r
                <para>Some quick features can be turned on and off by changing variable values in the file <filename>/openils/var/web/opac/skin/default/js/rdedail.js</filename>. \r
                You will notice the section at the top of this file called <quote>Per-skin configuration settings</quote>. Changing setting in this section can control several features including \r
                limiting results to local only or showing copy location or displaying serial holdings. Form this section you can also enable refworks and set the Refworks host URL.</para>\r
                <para>Some copy level details settings can be turned on and off from <filename>/openils/var/web/opac/skin/default/js/copy_details.js</filename> including displaying certain fields \r
                such as due date in the OPAC.</para>\r
                <para>An important file is the <filename>/openils/var/web/opac/skin/default/xml/rdetail/rdetail_summary.xml</filename> file. This file allows you to control which field to display in \r
                the details summary of the record. The new <link linkend='BibTemplate'>BibTemplate</link> feature makes this file even more powerful by allowing you to display any marc fields \r
                with a variety of formatting options.</para>\r
                <para>The <filename>/openils/var/web/opac/skin/default/xml/rdetail/rdetail_copyinfo.xml</filename> file allows you to format the display of the copy information.</para>   \r
        </section>              \r
        <section xml:id="BibTemplate">\r
                <title>BibTemplate</title><indexterm><primary>BibTemplate</primary></indexterm>\r
                <para>BibTemplate is an Evergreen-custom Dojo module which can be used to retrieve and format XML  data served by the Evergreen <systemitem class="protocol">unAPI</systemitem> service.                        <systemitem class="protocol">unAPI</systemitem> is a protocol for requesting known objects in specific formats, and Evergreen uses this to supply data – bibliographic records, \r
                metarecords, monograph holdings information, Located URIs, and more to come – in many different formats from MARCXML to MODS to custom XML applications.</para>\r
                <indexterm><primary>unAPI</primary></indexterm> <indexterm><primary>MARCXML</primary></indexterm><indexterm><primary>MODS</primary></indexterm>\r
                <para>Managing the display of information from raw XML can be difficult, and the purpose of BibTemplate  is to make this simpler, as well as move the display closer to the \r
                client and away from the source data. This is good from a separation-of-responsibilities perspective, and also makes it easier to contain and control local customization.</para>\r
                <para>BibTemplate supports the following Evergreen meta data formats:</para>\r
                <itemizedlist>\r
                        <listitem>MARCXML - datatype='marcxml-full' (default)</listitem>                                        \r
                        <listitem>MODS 3.3: datatype='mods33'</listitem>\r
                        <listitem>Dublin Core: datatype='rdf_dc'</listitem><indexterm><primary>Dublin Core</primary></indexterm>\r
                        <listitem>FGDC: datatype='fgdc'</listitem><indexterm><primary>FGDC</primary></indexterm>\r
                </itemizedlist>                 \r
                <simplesect>\r
                        <title>HTML API</title>\r
                        <para>BibTemplate follows the Dojo convention of adding attributes to existing (X)HTML in order to progressively change its behavior. The 1.6.0 HTML API consists of a \r
                        set of attributes that are added to existing OPAC markup, and fall into two classes:</para><indexterm><primary>Dojo toolkit</primary></indexterm>\r
                        <itemizedlist>\r
                                <listitem> The slot marker – Elements that denote the location of bibliographic data to insert.</listitem>\r
                                <listitem>The slot formatter – Elements that specify how the named data should be formatted for display.</listitem>\r
                        </itemizedlist>          \r
                </simplesect>\r
                <simplesect>\r
                        <title>Slot Marker</title><indexterm><primary>slot marker</primary></indexterm>\r
                        <para>A slot marker is any displayable HTML element that has a type attribute with a value starting with opac/slot-data. This element will become the container \r
                        for the formatted data. A slot marker is required in order to retrieve, format and display data using BibTemplate. A slot marker must also have an \r
                        attribute called query containing a CSS3 selector. This selector is applied to the XML returned by the unAPI service in order to gather the specific XML \r
                        Nodes that should be considered for formatting.</para><indexterm><primary>CSS3</primary></indexterm>\r
                        <para>The slot marker can also specify the format of the data to be returned from the unAPI service. This can be specified by adding +{format} to the type \r
                        attribute, as in opac/slot-data+mods33-full. The default data format is marcxml-uri, which is an augmented MARCXML record containing Located URI information \r
                        and unAPI links.</para>\r
                        <para>Example of a slot marker:</para>\r
                        <screen>&lt;p type='opac/slot-data' query='datafield[tag=245]'&gt;&lt;/p&gt;</screen>\r
                        <para>Most useful attribute match operators include:</para>\r
                        <itemizedlist>\r
                                <listitem> datafield[tag=245] - exact match</listitem>\r
                                <listitem>datafield[tag^=65] - match start of value</listitem>\r
                        </itemizedlist> \r
                        <tip><para>Selectors always narrow, so select broadly and iterate through the NodeList</para></tip>\r
                </simplesect>\r
                <simplesect>\r
                        <title>Slot Formatter</title><indexterm><primary>slot formatter</primary></indexterm>\r
                        <para>A slot formatter is any invisible HTML element which has a type attribute with the value of opac/slot-format. (NOTE: before 1.6.0.4, only &lt;script&gt; \r
                        elements were supported, though this restriction is now removed to support Internet Explorer.) Only one slot formatter element is allowed in each slot. The text contents \r
                        of this element are wrapped in a JavaScript<indexterm><primary>JavaScript</primary></indexterm> function and run for each node returned by the query CSS3 selector \r
                        specified on the slot marker. This function is passed \r
                        one argument, called item, which an XML Node captured by the selector. This function should return HTML text. The output for all runs of the slot formatter is \r
                        concatenated into a single string and used to replace the contents of the slot marker.</para>\r
                        <para>The slot formatter is optional, and if not supplied BibTemplate will create a simple function which extracts and returns the text content of the XML Nodes \r
                        specified in the CSS3 selector.</para>\r
                        <para>Example of a slot formatter:</para>\r
<programlisting>\r
        &lt;td class='rdetail_item' id='rdetail_online' type='opac/slot-data' \r
        query='volumes volume uris uri' join=", "&gt;\r
                &lt;script type='opac/slot-format'&gt;&lt;![CDATA[\r
                        var link = '&lt;a href="' + item.getAttribute('href') + '"&gt;' + item.getAttribute('label') + '&lt;/a&gt;';\r
                        if (item.getAttribute('use_restriction'))\r
                                link += ' (Use restriction: ' + item.getAttribute('use_restriction') + ')';\r
                                return link;\r
                ]]&gt;&lt;/script&gt;\r
        &lt;/td&gt;\r
</programlisting>\r
                </simplesect>\r
                <simplesect>\r
                        <title>JavaScript API</title><indexterm><primary>JavaScript</primary></indexterm>\r
                        <para>In order for BibTemplate to find the slot markers and invoke the slot formatters JavaScript renderer must be instantiated and called. This must be done \r
                        for each record that is to contribute to a pages display. The API for this is simple and straight-forward:</para>\r
                        <para>The slot formatter is optional, and if not supplied BibTemplate will create a simple function which extracts and returns the text content of the XML Nodes \r
                        specified in the CSS3 selector.</para><indexterm><primary>CSS3</primary></indexterm>\r
                        <para>Example of a slot formatter:</para>\r
<programlisting>\r
        dojo.require('openils.BibTemplate'); // Tell Dojo to load BibTemplate, if it is not already loaded\r
        \r
        // Create a renderer supplying the record id and the short name of the org unit, if known, \r
        // and call the render() method                                         \r
        new openils.BibTemplate({ record : new CGI().param('r'), org_unit : here.shortname() }).render(); \r
</programlisting>\r
                        <para>The argument hash supplied to the new <systemitem>openils.BibTemplate()</systemitem> constructor can have the following properties:</para>\r
                        <itemizedlist>\r
                                <listitem>record – The bibliographic record ID.</listitem>\r
                                <listitem>org_unit – The relevant Organizational Unit, used to restrict holdings scope as on a search result or record detail page.</listitem>\r
                                <listitem>root – The root element within the web page that BibTemplate should search for slot markers</listitem>\r
                        </itemizedlist>          \r
                </simplesect>\r
                <simplesect>\r
                        <title>BibTemplate Examples</title>\r
                        <para>This is all that we had to add to display the contents of an arbitrary MARC field:</para>\r
<programlisting>\r
&lt;tr&gt;\r
        &lt;td&gt;Bibliography note&lt;/td&gt;\r
        &lt;td type='opac/slot-data' query='datafield[tag=504]'&gt;&lt;/td&gt;\r
&lt;/tr&gt;\r
</programlisting>\r
                        <note><para>If multiple fields match, they are displayed on consecutive lines within the same left-hand cell.</para></note>\r
                        <para>To display a specific MARC subfield, add that subfield to the query attribute.</para><indexterm><primary>MARC</primary></indexterm>\r
                        <para>For example, subfield $a is the only user-oriented subfield in field 586 (Awards Note)</para>\r
<programlisting>\r
&lt;tr&gt;\r
        &lt;td&gt;Awards note&lt;/td&gt;\r
        &lt;td type='opac/slot-data' query='datafield[tag=586] subfield[code=a]'&gt;&lt;/td&gt;\r
&lt;/tr&gt;\r
</programlisting>\r
                        <para>Hide empty rows by default, and display them only if they have content:</para>\r
<programlisting>\r
        &lt;tr class='hide_me' id='tag504'&gt;\r
                &lt;td&gt;Bibliographic note&lt;/td&gt;\r
                &lt;td type='opac/slot-data' query='datafield[tag=504]'&gt;\r
                        &lt;script type='opac/slot-format'&gt;&lt;![CDATA[\r
                                dojo.query('#tag504').removeClass('hide_me');\r
                                return '&lt;span&gt;' + dojox.data.dom.textContent(item) +\r
                                '&lt;/span&gt;&lt;br/&gt;';\r
                        ]]&gt;&lt;/script&gt;\r
                &lt;/td&gt;&lt;/tr&gt;\r
</programlisting>\r
                        <itemizedlist>\r
                                <listitem>&lt;![CDATA[ ... ]]&gt; tells Evergreen Web server to treat the contents as literal <quote>character data</quote> - \r
                                avoids hilarity of entity substitution</listitem>\r
                                <listitem>&lt;script type='opac/slot-format'&gt;...&lt;/script&gt;, contained within an <quote>opac/slot-data</quote> element, receives a variable named item \r
                                containing the results of the query (a NodeList)</listitem>     \r
                        </itemizedlist> \r
                        <para>Suppressing a subfield:</para>\r
<programlisting>\r
&lt;tr class='hide_me' id='tag700'&gt;\r
        &lt;td>Additional authors&lt;/td&gt;\r
        &lt;td type='opac/slot-data' query='datafield[tag=700]'&gt;\r
                &lt;script type='opac/slot-format'&gt;&lt;![CDATA[\r
                        dojo.query('#tag700').removeClass('hide_me');\r
                        var text = '';\r
                        var list = dojo.query('subfield:not([code=4])', item);\r
                        for (var i =0; i &lt; list.length; i++) {\r
                                text += dojox.data.dom.textContent(list[i]) + ' ';\r
                        }\r
                        return '&lt;span&gt;' + text + '&lt;/span&gt;&lt;br/&gt;';\r
                ]]&gt;&lt;/script>\r
        &lt;/td&gt;&lt;/tr&gt;\r
</programlisting>\r
                </simplesect>\r
        </section>\r
        <section xml:id="customizingslimpac">\r
                <title>Customizing the Slimpac</title>\r
                <para>The Slimpac is the an alternative OPAC display for browsers or devices without JavaScript or which may have screen size limitations. There is both a simple and advanced search \r
                option for the Slimpac.</para> \r
                <para>The html files for customizing the Slimpac search display are located in the folder <filename class="directory">/openils/var/web/opac/extras/slimpac</filename>.</para>\r
                <para><filename>start.html</filename> is the basic search display and <filename>advanced.html</filename> is the display for the advanced search option.</para>  \r
                <para>By default, the Slimpac files include the same locale dtd as the regular OPAC (<filename>opac.dtd</filename>). However, the slimpac files do not use the same CSS files as the \r
                regular OPAC which means that if you change the OPAC color scheme, you must also edit the Slimpac files.</para>\r
                <simplesect>\r
                        <title>Customizing the Slimpac Results Display</title>\r
                        <para>Two files control the display results for the slimpac. Edit the XSL stylesheet (<filename>/openils/var/xsl/ATOM2XHTML.xsl</filename>) to edit the elements of the \r
                        record as pulled from the XML output. \r
                        You may also change the style of the page by editing the CSS stylesheet for the results display (<filename>/openils/var/web/opac/extras/os.css</filename>).</para> \r
                </simplesect>\r
                <simplesect>\r
                        <title>Customizing the Slimpac Details/Holdings Display</title> \r
                        <para>It is also possible to customize the details page when viewing specific items from the results list. To edit the holdings display which contains the details of the specific \r
                        record linked from the results display, edit the CSS stylesheet for the holdings/details page \r
                        (<filename>/openils/var/web/opac/extras/htmlcard.css</filename>). You may also control the content of the record by editing <filename>MARC21slim2HTMLCard.xsl</filename>. \r
                        Holdings data may also be controlled by editing <filename>MARC21slim2HTMLCard-holdings.xsl</filename>.</para>     \r
                </simplesect>\r
        </section>\r
        <section xml:id="integratingsearchforms">\r
                <title>Integrating a Evergreen Search Form on a Web Page</title>\r
                <para>It is possible to embed a simple search form into an html page which will allow users to search for materials in your Evergreen catalog. Here is code which can be embedded \r
                anywhere in the body of your web page:</para> \r
<programlisting language="html"><![CDATA[\r
<form action="http://[domain name]/opac/[locale]/skin/default/xml/rresult.xml" method="get">\r
<div>\r
        Quick Catalog Search:<br />\r
        <input type="text" alt="Input Box for Catalog Search" maxlength="250" \r
        size="20" id="t" name="t" value=""  />\r
        <input type="hidden" id="rt" name="rt" value="keyword" />\r
        <input type="hidden" id="tp" name="tp" value="keyword" />\r
        <input type="hidden" id="l" name="l" value="2" />\r
        <input type="hidden" id="d" name="d" value="" />\r
        <input type="hidden" id="f" name="f" value="" />\r
        <input type="submit" value="Search" class="form-submit"  />\r
    </div>\r
</form>\r
]]>\r
</programlisting>\r
                <para> Replace <emphasis>[domain name]</emphasis> with the domain name of your Evergreen server and replace <emphasis>[locale]</emphasis> with the desired locale of \r
                your Evergreen instance (e.g. en-US). This does a basic keyword search. Different types of searches and more advanced search forms can be developed.</para> \r
        </section>\r
</chapter>\r
\r