source: documentation/trunk/tutorial_sample_files/images/image3/etc/collectionConfig.bak@ 27793

<?xml version="1.0" encoding="UTF-8"?>
<CollectionConfig xmlns:gsf="http://www.greenstone.org/greenstone3/schema/ConfigFormat" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
    <metadataList>
        <metadata lang="en" name="creator"/>
        <metadata lang="en" name="maintainer"/>
        <metadata lang="en" name="public">true</metadata>
    </metadataList>
    <displayItemList>
        <displayItem assigned="true" lang="en" name="description">&lt;p&gt;This is a basic image collection that contains no text and no
explicit metadata. Several JPEG files are placed in the import directory prior to importing
and building the collection, that&apos;s all.&lt;/p&gt;
&lt;p&gt;The images in this collection have been produced by members of the Department of Computer Science, University of Waikato.
The University of Waikato holds copyright. They may be distributed freely, without any restrictions.&lt;/p&gt;

&lt;h3&gt;How the collection works&lt;/h3&gt;

&lt;p&gt;&lt;a href=&quot;library/collection/imagee3/document/HASHe65e0fdf1b460cd4f85899&quot;&gt;Here&lt;/a&gt; is a sample document in the collection.
The &lt;a href=&quot;_httpcollection_/etc/collectionConfig.xml&quot; target=collectionConfig.xml&gt; 
configuration file&lt;/a&gt; specifies no indexes, so the search box is suppressed.&lt;/p&gt;

&lt;p&gt;
There is only one plugin, &lt;i&gt;ImagePlugin&lt;/i&gt;, aside from the four that are
always present—&lt;i&gt;GreenstoneXMLPlugin&lt;/i&gt;, &lt;i&gt;MetadataXMLPlugin&lt;/i&gt;, &lt;i&gt;ArchivesInfPlugin&lt;/i&gt;, &lt;i&gt;DirectoryPlugin&lt;/i&gt;
 (the latter three are only visible in the GLI if &apos;Expert&apos; mode is selected).
&lt;i&gt;ImagePlugin&lt;/i&gt; relies on the existence of two programs from the ImageMagick suite
(&lt;a href=&quot;http://www.imagemagick.org&quot;&gt;http://www.imagemagick.org&lt;/a&gt;): &lt;i&gt;convert&lt;/i&gt; and
&lt;i&gt;identify&lt;/i&gt;. Greenstone will not be able to build the collection correctly unless
ImageMagick is installed on your computer.&lt;/p&gt;

&lt;p&gt; &lt;i&gt;ImagePlugin&lt;/i&gt; automatically creates a thumbnail and generates the following
metadata for each image in the collection:&lt;/p&gt;

&lt;table border=0 cellspacing=0&gt;
&lt;tr&gt;&lt;td width=125 valign=top&gt;&lt;i&gt;Image&lt;/i&gt;&lt;/td&gt;&lt;td&gt;Name of file containing the image &lt;tr&gt;
&lt;tr&gt;&lt;td valign=top&gt;&lt;i&gt;ImageWidth&lt;/i&gt;&lt;/td&gt;&lt;td&gt;Width of image (in pixels) &lt;tr&gt;
&lt;tr&gt;&lt;td valign=top&gt;&lt;i&gt;ImageHeight&lt;/i&gt;&lt;/td&gt;&lt;td&gt;Height of image (in pixels) &lt;tr&gt;
&lt;tr&gt;&lt;td valign=top&gt;&lt;i&gt;Thumb&lt;/i&gt;&lt;/td&gt;&lt;td&gt; Name of gif file containing thumbnail of image &lt;tr&gt;
&lt;tr&gt;&lt;td valign=top&gt;&lt;i&gt;ThumbWidth&lt;/i&gt;&lt;/td&gt;&lt;td&gt;Width of thumbnail image (in pixels) &lt;tr&gt;
&lt;tr&gt;&lt;td valign=top&gt;&lt;i&gt;ThumbHeight&lt;/i&gt;&lt;/td&gt;&lt;td&gt;Height of thumbnail image (in pixels) &lt;tr&gt;
&lt;tr&gt;&lt;td valign=top&gt;&lt;i&gt;thumbicon&lt;/i&gt;&lt;/td&gt;&lt;td&gt;Full pathname specification of thumbnail image &lt;tr&gt;
&lt;tr&gt;&lt;td valign=top&gt;&lt;i&gt;assocfilepath&lt;/i&gt;&lt;/td&gt;&lt;td&gt;Pathname of image directory in the collection&apos;s &lt;i&gt;assoc&lt;/i&gt; directory &lt;tr&gt;
&lt;/table&gt;&lt;br/&gt;

&lt;p&gt;
The image is stored as an &quot;associated file&quot; in the &lt;i&gt;assoc&lt;/i&gt; subdirectory
of the collection&apos;s &lt;i&gt;index&lt;/i&gt; directory. (&lt;i&gt;Index&lt;/i&gt; is where all files
necessary to serve the collection are placed, to make it self-contained.) The
pathname &amp;#095;&lt;i&gt;httpassocdir&lt;/i&gt;&amp;#095;, which is the same as
&amp;#095;&lt;i&gt;httpcollection&lt;/i&gt;&amp;#095;&lt;i&gt;/index/assoc&lt;/i&gt;, refers to this directory. For any
document, its thumbnail and image are both in a subdirectory whose filename is
given by &lt;i&gt;assocfilepath&lt;/i&gt;. The metadata element &lt;i&gt;thumbicon&lt;/i&gt; is set to
the full pathname specification of the thumbnail image, and can be used in the
same way as &lt;i&gt;srcicon&lt;/i&gt; (see the MSWord and PDF demonstration collection).&lt;/p&gt;

&lt;p&gt;
The &lt;i&gt;&amp;lt;display&amp;gt;&lt;/i&gt; section in the
&lt;a href=&quot;_httpcollection_/etc/collectionConfig.xml&quot; target=collectionConfig.xml&gt;configuration file&lt;/a&gt;,
dictates how the document will appear, and
&lt;a href=&quot;library/collection/imagee3/document/HASH015484508b3a74f07194ade4&quot;&gt;this&lt;/a&gt; is the
result. There is no document text (if there were, it would be producible by
&lt;i&gt;&amp;lt;xsl:call-template name=&quot;wrappedSectionText&quot;/&amp;gt;&lt;/i&gt;). What is shown is the image itself (produced by 
the &lt;i&gt;&amp;lt;xsl:call-template name=&quot;wrappedSectionImage&quot;/&amp;gt;&lt;/i&gt;), along with some metadata extracted
from it.&lt;/p&gt;

&lt;p&gt;
The configuration file
specifies one classifier in the &lt;i&gt;&amp;lt;browse&amp;gt;&lt;/i&gt; section, a &lt;i&gt;List&lt;/i&gt; based on &lt;i&gt;Image&lt;/i&gt; metadata, shown
&lt;a href=&quot;library/collection/imagee3/browse/CL1&quot;&gt;here&lt;/a&gt;. The format statement shows the thumbnail image along with
some metadata. (Any other classifiers would have the same format, since this
statement does not name the classifier.) &lt;/p&gt;

&lt;p&gt;
You may wonder why the thumbnail image is generated and stored explicitly, when
the same effect would be obtained by using the original image and scaling it. The reason is to save communication bandwidth by not sending large images when
small ones would do.&lt;/p&gt;

&lt;p&gt;For a more comprehensive image collection, see the
&lt;a href=&quot;http://www.nzdl.org/cgi-bin/library?a=p&amp;p=about&amp;c=aircraft&quot;&gt;kiwi aircraft images&lt;/a&gt;
in the New Zealand Digital Library. The structure of this collection is
quite different, however: it is a collection of web pages that include many
images along with the text. The HTML plugin &lt;i&gt;HTMLPlugin&lt;/i&gt; also processes image
files, but it does so in a different way from ImagePlugin (for example, it
does not produce the metadata described above).&lt;/p&gt;</displayItem>
        <displayItem assigned="true" lang="en" name="name">Simple image collection</displayItem>
        <displayItem assigned="true" lang="en" name="document:text">text</displayItem>
        <displayItem assigned="true" lang="en" name="document:ex.Title">Title</displayItem>
        <displayItem assigned="true" lang="en" name="document:ex.Source">Source</displayItem>
        <displayItem assigned="true" lang="en" name="text">text</displayItem>
        <displayItem assigned="true" lang="en" name="dc.Title,ex.dc.Title,Title">titles</displayItem>
        <displayItem assigned="true" lang="en" name="Source">filenames</displayItem>
        <displayItem assigned="true" lang="en" name="document">document</displayItem>
        <displayItem assigned="true" lang="en" name="section">section</displayItem>
        <displayItem assigned="true" lang="en" name="shortDescription">imagee3</displayItem>
    </displayItemList>
    <format>  <gsf:template name="choose-title">
    <gsf:choose-metadata>
      <gsf:metadata name="dc.Title"/>
      <gsf:metadata name="exp.Title"/>
      <gsf:metadata name="ex.dc.Title"/>
      <gsf:metadata name="Title"/>
      <gsf:default>Untitled</gsf:default>
    </gsf:choose-metadata>
  </gsf:template>

</format>
    <search type="mgpp">
        <searchType name="plain"/>
        <searchType name="simpleform"/>
        <searchType name="advancedform"/>
        <format>  <gsf:template match="documentNode">
    <td valign="top">
      <gsf:link type="document">
        <gsf:icon type="document"/>
      </gsf:link>
    </td>
    <td>
      <gsf:link type="document">
        <xsl:call-template name="choose-title"/>
      </gsf:link>
    </td>
  </gsf:template>

</format>
    </search>
    <infodb type="gdbm"/>
    <import>
        <pluginList>
            <plugin name="ImagePlugin"/>
            <plugin name="GreenstoneXMLPlugin"/>
            <plugin name="MetadataXMLPlugin"/>
            <plugin name="ArchivesInfPlugin"/>
            <plugin name="DirectoryPlugin"/>
        </pluginList>
    </import>
    <browse>
        <classifier name="List">
            <option name="-metadata" value="Image"/>
            <option name="-partition_type_within_level" value="approximate_size"/>
            <option name="-buttonname" value="Browse"/>
        </classifier>
        <format>  <gsf:template match="documentNode">
    <td valign="center">
      <gsf:link type="document">
        <gsf:choose-metadata>
          <gsf:metadata name="thumbicon"/>
          <gsf:metadata name="srcicon"/>
        </gsf:choose-metadata>
      </gsf:link>
    </td>
    <td style="padding-left:10px;" valign="center">
      <table>
        <tr>
          <td style="padding-right:10px;" valign="top">
            <b>Image Name:</b>
          </td>
          <td>
            <gsf:metadata name="Image"/>
          </td>
        </tr>
        <tr>
          <td>
            <b>Width:</b>
          </td>
          <td>
            <gsf:metadata name="ImageWidth"/>
          </td>
        </tr>
        <tr>
          <td>
            <b>Height:</b>
          </td>
          <td>
            <gsf:metadata name="ImageHeight"/>
          </td>
        </tr>
        <tr>
          <td>
            <b>Size:</b>
          </td>
          <td>
            <gsf:metadata name="ImageSize"/>
          </td>
        </tr>
      </table>
    </td>
  </gsf:template>
  <gsf:template match="classifierNode[@classifierStyle = 'VList']">
    <td valign="top">
      <gsf:link type="classifier">
        <gsf:icon type="classifier"/>
      </gsf:link>
    </td>
    <td valign="top">
      <gsf:metadata name="Title"/>
    </td>
  </gsf:template>
  <gsf:template match="classifierNode[@classifierStyle = 'HList']">
    <gsf:link type="classifier">
      <gsf:metadata name="Title"/>
    </gsf:link>
  </gsf:template>

</format>
    </browse>
    <display>
        <format>  <gsf:option name="TOC" value="true"/>
<!--
Overwriting this template allows you to change the heading of the document.
-->
  <gsf:template name="documentHeading"/>
<!--
Overwriting this template can be used to redefine the content of the whole document. This is useful for simple documents, but not recommended for more complex documents (e.g. hierachical and paged documents) as it can prevent any sub-sections from showing.
-->
  <gsf:template name="documentContent">
    <xsl:call-template name="wrappedSectionImage"/>
    <xsl:call-template name="wrappedSectionText"/>
    <table>
      <tr>
        <td style="padding-right:10px;" valign="top">
          <b>Image Name:</b>
        </td>
        <td>
          <gsf:metadata name="Image"/>
        </td>
      </tr>
      <tr>
        <td>
          <b>Width:</b>
        </td>
        <td>
          <gsf:metadata name="ImageWidth"/>
        </td>
      </tr>
      <tr>
        <td>
          <b>Height:</b>
        </td>
        <td>
          <gsf:metadata name="ImageHeight"/>
        </td>
      </tr>
      <tr>
        <td>
          <b>Size:</b>
        </td>
        <td>
          <gsf:metadata name="ImageSize"/>
        </td>
      </tr>
    </table>
  </gsf:template>
<!--
Overwriting this template can be used to change the content of section headings.
-->
<!--
<gsf:template name="sectionHeading">
<xsl:call-template name="choose-title"/>
</gsf:template>
-->
<!--
Overwriting this template can be used to change the content of the top-level section.
-->
<!--
<gsf:template name="topLevelSectionContent">
<xsl:call-template name="wrappedSectionImage"/>
<xsl:call-template name="wrappedSectionText"/>
</gsf:template>
-->
<!--
Overwriting this template can be used to change the content of sections.
-->
<!--
<gsf:template name="sectionContent">
<xsl:call-template name="wrappedSectionImage"/>
<xsl:call-template name="wrappedSectionText"/>
</gsf:template>
-->

</format>
    </display>
    <replaceListRef id="gs2-standard"/>
    <replaceListRef id="gs2-image"/>
    <serviceRackList><!-- comment out the following serviceRack if you want to disable OAI for this collection -->
        <serviceRack name="OAIPMH">
            <ListMetadataFormats><!--What metadata sets to support is collection specific. To support other metadata schema, simply add a metadataFormat element here.
                    The support of unqualified Dublin Core metadata set is mandatory in the oai specification.
                -->
                <metadataFormat metadataPrefix="oai_dc">
                    <metadataPrefix>oai_dc</metadataPrefix>
                    <schema>http://www.openarchives.org/OAI/2.0/oai_dc.xsd</schema>
                    <metadataNamespace>http://www.openarchives.org/OAI/2.0/oai_dc/</metadataNamespace><!--<metadataElements>dc.Title,dc.Creator,dc.Subject,dc.Description,dc.Publisher,dc.Contributor,dc.Date,dc.Type,dc.Format,dc.Identifier,dc.Source,dc.Language,dc.Relation,dc.Coverage,dc.Rights</metadataElements>-->
                    <mappingList><!-- 
                            The mapping is in the form: <publicly supported metadata name>,<mapped metadata name>, short as <A>,<B> 
                            The first metadata name is medatory; if there is no mapped name followed, then the first name must be used by the records and
                            searchable in the database, otherwise it is the mapped name stored in the database. The number of mapping elements matches the
                            number of external metadata of the records. If only one name is present, the returned metadata will use this name plus the retrieved value;
                            if both <A>,<B> are present, the returned metadata will use <A>'s name plus <B>'s value retrieved from database.
                    
                            **Bear in mind: if this mapping list is not present, the standard dc. metadata names (15 in total) will be used to retrieve metadata in the database.
                    
                            **The only case when this mapping is not present is that: 1. this metadata format is oai_dc; 2. the metadata is also stored in the database by Dublin Core's names.
                        -->
                        <mapping>dc:title,Title</mapping><!-- This mapping example means that the dc.Title is requested and the value of the metadata Title, which is used in this repository, is returned as response. -->
                    </mappingList>
                </metadataFormat>
            </ListMetadataFormats>
        </serviceRack>
    </serviceRackList>
</CollectionConfig>