name=MARC Demo
index_text=text
index_Title=Title
sampleoid=D0s156

shortDescription=This collection is based on a selection of MARC records of working papers published by the Computer Science Department at the University of Waikato.
description1a=<p>This collection, which contains {0-numdocs} MARC entries, is based on the MARC records of working papers published by <a href="{1-cs url}">Computer Science Department</a> at <a href="{2-waikato url}">the University of Waikato</a>. <a href="{3-doc url}">Here</a> is a sample document in the collection.</p>
description1=<h3>How the collection works</h3><p>The configuration file, <tt>collectionConfig.xml</tt>, uses <i>MARCPlugin</i> to process the MARC records, as well as the standard plugins. There are three classifiers, based on <i>dc.Title</i>, <i>dc.Creator</i>, and <i>dc.Subject</i> metadata. The <i>Title</i> classifier uses AZList, while the other two use AZCompactList, which groups items with the same metadata into a bookshelf. The <i>-removesuffix</i> argument for the <i>Title</i> and <i>Creator</i> classifiers removes suffixes from the metadata string (<i>dc.Title</i> and <i>dc.Creator</i> respectively). This is specified as a PERL regular expression, and trims characters (such as trailing punctuation) from the strings for display.</p>

description2=<p>The <i>VList</i> format statement controls the display of search results and all classifiers. For bookshelves, the number of leaf documents is displayed on the right-hand side. For documents, <i>dc.Title</i> is displayed, along with <i>dc.Creator</i> and <i>dc.Publisher</i>. <i>[sibling\:dc.Creator]</i> is used as dc.Creator has multiple values, and specifies that all values be output, not just the first one.</p>

description3=<p>The MARC plugin uses a special file to map MARC field numbers to Greenstone-style metadata. This file resides in the greenstone3 installation folder's <i>gs2build/etc</i> directory, and is called <tt>marc2dc.txt</tt>. It lists the correspondences between MARC field numbers and Greenstone metadata. Any MARC fields that are not listed simply do not appear as metadata, though they are still present in the Greenstone document. Each line in the file has the format <blockquote> &lt;MARC field number&gt; -&gt; GreenstoneMetadataName </blockquote> Lines in the file that begin with "\#" are comments.</p>

description4=<p>The standard version of this file is loosely based on the MARC to Dublin Core mapping found at <a href="http\://www.loc.gov/marc/marc2dc.html">http\://www.loc.gov/marc/marc2dc.html</a> (which assumes USMARC/MARC21).</p>

description5=<p>Multiple MARC fields may map to a single Dublin Core field. For example, fields 720 ("Uncontrolled name"), 100 ("Personal name"), 110 ("Corporate name") and 111 ("Meeting name") all map to <i>dc.Creator</i>. Actual MARC records normally define only one of these fields, and anyway Greenstone allows multi-valued metadata.</p>

description6=<p>Some mappings are dependent on subfields. For example, MARC field 260 contains information about publication and distribution. Subfields "c" (Date of Publication) and "g" (Date of manufacture) are mapped to <i>dc.Date</i>, using the following mapping line\: <blockquote> 260$c$g -&gt; dc.Date </blockquote>  Greenstone also provides a file for mapping MARC to <b>qualified</b> dublin core\: in your Greenstone 3 installation folder's <tt>gs2build/etc/marc2qdc.txt</tt>. This can be used by the MARC plugin by setting the <i>-metadata_mapping_file</i> option to "marc2qdc.txt".</p>
