source: documented-examples/trunk/image-e/resources/collectionConfig.properties@ 36458

Last change on this file since 36458 was 36458, checked in by anupama, 21 months ago

The DEC collection image-e had already been ported to GS3 before I started porting the DEC collections. However, the collection descriptions (displayItemList section) had not been ported, and there were still macros in the collectionConfig.xml instead of using the gsf variables to load them. Have now ported the displayItemList (collection descriptions) for image-e from GS2 to GS3. I'll still need to rewrite them for GS3.

File size: 4.7 KB
Line 
1name=Simple image collection
2Height=Height
3Size=Size
4Width=Width
5ImageName=Image Name
6sampleoid=D2
7
8
9shortDescription=<p>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's all.</p>
10
11description1=<p>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.</p>
12
13description2=<h3>How the collection works</h3><p><a href="?a=d&d=_sampleoid_">Here</a> is a sample document in the collection. The <a href="_httpcollection_/etc/collect.cfg" target=collect.cfg> configuration file</a> specifies no indexes, so the search button is suppressed.</p>
14
15description3=<p>There is only one plugin, <i>ImagePlugin</i>, aside from the four that are always present (<i>GreenstoneXMLPlugin</i>, <i>MetadataXMLPlugin</i>, <i>ArchivesInfPlugin</i>, <i>DirectoryPlugin</i>). <i>ImagePlugin</i> relies on the existence of two programs from the ImageMagick suite (<a href="http://www.imagemagick.org">http://www.imagemagick.org</a>): <i>convert</i> and <i>identify</i>. Greenstone will not be able to build the collection correctly unless ImageMagick is installed on your computer.</p>
16
17description4=<p><i>ImagePlugin</i> automatically creates a thumbnail and generates the following metadata for each image in the collection: <blockquote> <table border=0 cellspacing=0> <tr><td width=125 valign=top><i>Image</i></td><td>Name of file containing the image <tr> <tr><td valign=top><i>ImageWidth</i></td><td>Width of image (in pixels) <tr> <tr><td valign=top><i>ImageHeight</i></td><td>Height of image (in pixels) <tr> <tr><td valign=top><i>Thumb</i></td><td> Name of gif file containing thumbnail of image <tr> <tr><td valign=top><i>ThumbWidth</i></td><td>Width of thumbnail image (in pixels) <tr> <tr><td valign=top><i>ThumbHeight</i></td><td>Height of thumbnail image (in pixels) <tr> <tr><td valign=top><i>thumbicon</i></td><td>Full pathname specification of thumbnail image <tr> <tr><td valign=top><i>assocfilepath</i></td><td>Pathname of image directory in the collection's <i>assoc</i> directory <tr> </table> </blockquote></p>
18
19description5=<p>The image is stored as an "associated file" in the <i>assoc</i> subdirectory of the collection's <i>index</i> directory. (<i>Index</i> is where all files necessary to serve the collection are placed, to make it self-contained.) The pathname &#095;<i>httpassocdir</i>&#095;, which is the same as &#095;<i>httpcollection</i>&#095;<i>/index/assoc</i>, refers to this directory. For any document, its thumbnail and image are both in a subdirectory whose filename is given by <i>assocfilepath</i>. The metadata element <i>thumbicon</i> is set to the full pathname specification of the thumbnail image, and can be used in the same way as <i>srcicon</i> (see the MSWord and PDF demonstration collection).</p>
20
21description6=<p>The second format statement in the <a href="_httpcollection_/etc/collect.cfg" target=collect.cfg>configuration file</a>, <i>DocumentText</i>, dictates how the document will appear, and <a href="?a=d&d=_sampleoid_">this</a> is the result. There is no document text (if there were, it would be producible by [<i>Text</i>]). What is shown is the image itself, along with some metadata extracted from it.</p>
22
23description7=<p>The configuration file specifies one classifier, a <i>List</i> based on <i>Image</i> metadata, shown <a href="?a=d&cl=CL1">here</a>. 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.)</p>
24
25description8=<p>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: <pre> &lt;td&gt;[link]&lt;img src='_httpassocdir_/[assocfilepath] /[Image]' width=[ThumbWidth] height=[ThumbHeight]&gt; [/link]&lt;\/td&gt;&lt;td valign=middle&gt;&lt;i&gt;[Title]&lt;\/i&gt;&lt;\/td&gt; </pre></p>
26
27description9=<p>The reason is to save communication bandwidth by not sending large images when small ones would do.</p>
28
29description10=<p>For a more comprehensive image collection, see the <a href="http://www.nzdl.org/cgi-bin/library?a=p&sa=about&c=aircraft">kiwi aircraft images</a> 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 <i>HTMLPlugin</i> also processes image files, but it does so in a different way from ImagePlugin (for example, it does not produce the metadata described above).</p>
Note: See TracBrowser for help on using the repository browser.