Ignore:
Timestamp:
2009-05-28T17:11:19+12:00 (15 years ago)
Author:
anna
Message:

updated some of the tutorials to version 2.82

File:
1 edited

Legend:

Unmodified
Added
Removed

  • documentation/trunk/tutorials/xml-source/tutorial_en.xml

    r19638 r19651  
    88<TutorialList>
    99<Title>
    10 <Text id="0001">Greenstone tutorial exercises (March 2008)</Text>
     10<Text id="0001">Greenstone tutorial exercises (May 2009)</Text>
    1111</Title>
    12 <Version current="2.80"/>
     12<Version current="2.82"/>
    1313<SupplementaryText>
    1414<Text id="title">Greenstone tutorial exercise</Text>
    … …  
    2020<Text id="wiki">Back to wiki</Text>
    2121<Text id="print">Print version</Text>
    22 <Text id="copyright">Copyright &copy; 2005 2006 2007 2008 by the <Link url="http://www.nzdl.org">New Zealand Digital Library Project</Link> at <Link url="http://www.waikato.ac.nz">the University of Waikato</Link>, New Zealand<br/>Permission is granted to copy, distribute and/or modify this document under the terms of the <Link url="http://www.gnu.org/licenses/fdl.html">GNU Free Documentation License</Link>, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled <Link url="http://greenstonewiki.cs.waikato.ac.nz/wiki/gsdoc/GNUFDL.html">“GNU Free Documentation License.”</Link></Text>
     22<Text id="copyright">Copyright &copy; 2005 2006 2007 2008 2009 by the <Link url="http://www.nzdl.org">New Zealand Digital Library Project</Link> at <Link url="http://www.waikato.ac.nz">the University of Waikato</Link>, New Zealand<br/>Permission is granted to copy, distribute and/or modify this document under the terms of the <Link url="http://www.gnu.org/licenses/fdl.html">GNU Free Documentation License</Link>, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled <Link url="http://greenstonewiki.cs.waikato.ac.nz/wiki/gsdoc/GNUFDL.html">“GNU Free Documentation License.”</Link></Text>
    2323</SupplementaryText>
    2424<Comment>
    … …  
    376376<Text id="0193">Installing Greenstone</Text>
    377377</Title>
    378 <Version initial="2.60" current="2.80"/>
     378<Version initial="2.60" current="2.82"/>
    379379<Content>
    380380<Heading>
    … …  
    398398</NumberedItem>
    399399<NumberedItem>
    400 <Text id="0201">From <Link>http://www.greenstone.org</Link></Text>
    401 <Text id="0202">Most people download the Windows distribution from <Link>http://www.greenstone.org</Link>, which contains the latest version of Greenstone. There are several optional modules that must be downloaded separately (to avoid a single massive download): <b>documented example collections</b>, the <b>Export to CD-ROM</b> package (Greenstone 2.70 and earlier), the <b>Language Pack</b> (Greenstone 2.62 and earlier) and <b>Classic Interface Pack</b> (Greenstone 2.63 and later). There is also the set of <b>sample files</b> used in these exercises. (To reduce the download size the documented example collections are distributed in unbuilt form and need to be built.)</Text>
    402 <Text id="0203">You need <b>Java</b> to run Greenstone. You might already have it; otherwise download it from <Link>http://java.sun.com</Link>. To work with image collections, you need <b>ImageMagick</b> (from <Link>http://www.imagemagick.org</Link>). </Text>
     400<Text id="0201">From <Link>http://www.greenstone.org/download</Link></Text>
     401<Text id="0202">Most people download the Windows distribution from <Link>http://www.greenstone.org/download</Link>, which contains the latest version of Greenstone. There are several optional modules that must be downloaded separately (to avoid a single massive download): <b>documented example collections</b>, the <b>Export to CD-ROM</b> package (Greenstone 2.70 and earlier), the <b>Greenstone Language Pack</b> (Greenstone 2.62 and earlier) and <b>Classic Interface Pack</b> (Greenstone 2.63 and later). There is also the set of <b>sample files</b> used in these exercises. (To reduce the download size the documented example collections are distributed in unbuilt form and need to be built.)</Text>
     402<Text id="0203">You need <b>Java</b> to run Greenstone. You might already have it; otherwise download it from <Link>http://java.sun.com</Link>. To work with image collections, you need <b>ImageMagick</b> (from <Link>http://www.imagemagick.org</Link>).</Text>
    403403</NumberedItem>
    404404<Text id="0204">Most Greenstone CD-ROMs start the installation process as soon as they are inserted into the drive, assuming that the AutoPlay feature is enabled on your computer. If installation does not begin by itself, locate the file <i>setup.exe</i> and double click it to start the installation process. (On the IMARK CD-ROM this file resides in the folder <Path>software_tools &rarr; Greenstone</Path>). If you download Greenstone over the web, what you get is the installer&mdash;just double-click it.</Text>
    … …  
    410410</Bullet>
    411411<Bullet>
    412 <Text id="0209">Welcome to the InstallShield Wizard for the Greenstone Digital Library Software. Click &lt;<b>Next</b>&gt;</Text>
    413 </Bullet>
    414 <Bullet>
    415 <Text id="0210">License Agreement. Accept the agreement and then click &lt;<b>Next</b>&gt;</Text>
     412<Text id="0209">Welcome to the Greenstone Digital Library Software Installer. It is recommended that you uninstall any previous installations of Greenstone2 before running this installer. Click &lt;<b>Next</b>&gt;</Text>
     413</Bullet>
     414<Bullet>
     415<Text id="0210">License Agreement. Click &lt;<b>Accept</b>&gt;</Text>
    416416</Bullet>
    417417<Bullet>
    … …  
    419419</Bullet>
    420420<Bullet>
    421 <Text id="0212">Setup Type. Leave at the default (Local Library) and click &lt;<b>Next</b>&gt;</Text>
     421<Text id="0212">Components. Click the question mark button on the right of each component will display the description of this component in a popup window. Leave at the default (all components are selected) and click &lt;<b>Next</b>&gt;</Text>
    422422</Bullet>
    423423<Bullet>
    … …  
    425425</Bullet>
    426426<Bullet>
    427 <Text id="0214">Set admin password. Choose a suitable password and click &lt;<b>Next</b>&gt; (If your computer will not be serving collections online, the password doesn't matter)</Text>
    428 </Bullet>
    429 <Bullet>
    430 <Text id="0215">Click &lt;<b>Install</b>&gt; to complete the installation</Text>
     427<Text id="0214">Enable administration pages. Read the description on this page, if you check to enable, click &lt;<b>Next</b>&gt; to set admin password. Choose a suitable password and click &lt;<b>Next</b>&gt; (If your computer will not be serving collections online, the password doesn't matter)</Text>
     428</Bullet>
     429<Bullet>
     430<Text id="0215">Click &lt;<b>Install</b>&gt; to start the installation. Click &lt;<b>Show Details</b>&gt; to show the details of this installation</Text>
    431431</Bullet>
    432432<Bullet>
    … …  
    434434</Bullet>
    435435<Bullet>
    436 <Text id="0217">Installation is complete. If you are installing from a CD-ROM, the installer will offer to install ImageMagick (see below), and Java, if necessary.</Text>
     436<Text id="0217">Installation is complete. We have changed to a new installer in 2008. This installer will automatically install ImageMagick and GhostScript. However, if you are installing from a CD-ROM, the installer will offer to install ImageMagick (see below), and Java, if necessary.</Text>
    437437</Bullet>
    438438</BulletList>
    … …  
    442442</Heading>
    443443<Text id="0220">Once Greenstone has been installed, you should ensure that ImageMagick is installed on your computer if you wish to build any image collections. If you are installing from a Greenstone CD-ROM, you will be asked whether you want to install ImageMagick: say <b>Yes</b>. If you are not, you will need to download ImageMagick (from <Link>http://www.imagemagick.org</Link>). To install this program you must have Windows "Administrator" privileges. (If you do not have Windows Administrator privileges, the ImageMagick installer will give a cryptic error complaining that it failed to set a particular Windows registry value. If this happens you can continue your work with Greenstone, but you will not be able to build collections of images.)</Text>
    444 <Text id="0221"> The remaining steps are straightforward, and, as before, we recommend the default settings. Here is what you need to do.</Text>
     444<Text id="0221">The remaining steps are straightforward, and, as before, we recommend the default settings. Here is what you need to do.</Text>
    445445<BulletList>
    446446<Bullet>
    … …  
    487487</Title>
    488488<Prerequisite id="install_greenstone"/>
    489 <Version initial="2.60" current="2.80"/>
     489<Version initial="2.60" current="2.82"/>
    490490<Content>
    491491<Comment>
    … …  
    505505</NumberedItem>
    506506<NumberedItem>
    507 <Text id="0238">Remove the old version by going to the Windows Control Panel (from the <i>Settings</i> item on the <i>Start</i> menu). Click <b>Add or Remove Programs</b>, select <b>Greenstone Digital Library Software</b>, and <b>Remove</b> it. (To do this you may need Windows "Administrator" privileges.)</Text>
    508 </NumberedItem>
    509 <NumberedItem>
    510 <Text id="0239">At the end of this procedure you will be asked whether you would like all your Greenstone collections to be removed: you should probably say <i>No</i> if you wish to preserve your work.</Text>
    511 </NumberedItem>
    512 <Comment>
    513 <Text id="0240">Occasionally, problems are encountered if older Greenstone installations are not fully removed. To clean up your system, move your Greenstone collect folder, which contains all your collections, to the desktop. Then check for the folder C:\Program Files\gsdl or C:\Program Files\Greenstone, which is where Greenstone is usually installed, and remove it completely if it exists.</Text>
     507<Text id="0238">If the installed Greenstone version is 2.81 and above, to remove the old version, go to the Greenstone home directory (eg. C:\Users\&lt;username&gt;\Greenstone2 by default, where &lt;username&gt; is your user name) and click <b>Uninstall.bat</b>. Otherwise, if the version is lower than 2.81, remove the old version by going to the Windows Control Panel (from the <i>Settings</i> item on the <i>Start</i> menu). Click <b>Add or Remove Programs</b>, select <b>Greenstone Digital Library Software</b>, and <b>Remove</b> it. (To do this you may need Windows "Administrator" privileges.)</Text>
     508</NumberedItem>
     509<NumberedItem>
     510<Text id="0239">For version 2.81 and above, the uninstaller has an option for keeping all your Greenstone collections, leave it at default as selected. For versions lower than 2.81, at the end of the uninstallation procedure you will be asked whether you would like all your Greenstone collections to be removed: you should probably say <i>No</i> if you wish to preserve your work.</Text>
     511</NumberedItem>
     512<Comment>
     513<Text id="0240">Occasionally, problems are encountered if older Greenstone installations are not fully removed. To clean up your system, move your Greenstone collect folder, which contains all your collections, to the desktop. Then check for the folder C:\Program Files\gsdl or C:\Program Files\Greenstone or C:\Users\&lt;username&gt;\Greenstone2 for version 2.81 and above, which is where Greenstone is usually installed, and remove it completely if it exists.</Text>
    514514</Comment>
    515515<Heading>
    … …  
    569569</Heading>
    570570<Comment>
    571 <Text id="0252b">Greenstone now comes with all languages enabled.
    572 The generated HTML uses text + CSS rather than images for navigation bar,
    573 home, help, preferences buttons etc. The classic interface pack is not needed if you want to use Greenstone in another language. It is only needed if you want to revert back to the old style HTML with text images. This may be useful if you have customized your Greenstone, or if you require compatibility with Netscape 4.</Text>
     571<Text id="0252b">Greenstone now comes with all languages enabled. The generated HTML uses text + CSS rather than images for navigation bar, home, help, preferences buttons etc. The classic interface pack is not needed if you want to use Greenstone in another language. It is only needed if you want to revert back to the old style HTML with text images. This may be useful if you have customized your Greenstone, or if you require compatibility with Netscape 4.</Text>
    574572</Comment>
    575573<NumberedItem>
    … …  
    592590</Title>
    593591<SampleFiles folder="simple_html"/>
    594 <Version initial="2.60" current="2.80"/>
     592<Version initial="2.60" current="2.82"/>
    595593<Content>
    596594<Comment>
    … …  
    603601<Text id="0255">Start the Greenstone Librarian Interface:</Text>
    604602<Menu>
    605 <Text id="0255a">Start &rarr; All Programs &rarr; Greenstone Digital Library Software v2.74 &rarr; Greenstone Librarian Interface</Text>
     603<Text id="0255a">Start &rarr; All Programs &rarr; Greenstone-2.82 &rarr; Librarian Interface (GLI)</Text>
    606604</Menu>
    607605<Comment>
    … …  
    672670<NumberedItem>
    673671<Text id="0275a">Hyperlinks in a Greenstone collection work like this. If the link is to a document that is also in the collection, clicking it takes you to that document in the collection. If the link is to a document that is <i>not</i> in the collection, clicking it takes you to that document on the web.</Text>
    674 <Text id="0257b">Open <Path>boleyn.html</Path> and look for the link to <Path>Katharine of Aragon</Path> (in the 5th paragraph of the <Path>Biography</Path> section). This links to a document inside the collection--<Path>aragon.html</Path>. View this document by clicking the link.  For an external link, click <Path>letters written by Katharine</Path> (in the <Path>Primary Sources</Path> section). This takes you out on to the web. (A warning message is displayed first. You can also get rid of the warning by add <Format>cgiarg shortname=el argdefault=direct
    675 </Format> in the <Path>Greenstone &rarr; etc &rarr; main.cfg</Path> file)</Text>
     672<Text id="0257b">Open <Path>boleyn.html</Path> and look for the link to <Path>Katharine of Aragon</Path> (in the 5th paragraph of the <Path>Biography</Path> section). This links to a document inside the collection--<Path>aragon.html</Path>. View this document by clicking the link. For an external link, click <Path>letters written by Katharine</Path> (in the <Path>Primary Sources</Path> section). This takes you out on to the web. If you want a warning message to be displayed first, you can open <Path>Greenstone &rarr; etc &rarr; main.cfg</Path> file and uncomment the line <Format>cgiarg shortname=el argdefault=prompt</Format>.</Text>
    676673</NumberedItem>
    677674<Heading>
    … …  
    688685</Title>
    689686<SampleFiles folder="images"/>
    690 <Version initial="2.60" current="2.80"/>
     687<Version initial="2.60" current="2.82"/>
    691688<Content>
    692689<NumberedItem>
    … …  
    715712</Heading>
    716713<NumberedItem>
    717 <Text id="0352">We work with just the first three files (<Path>Bear.jpg</Path>, <Path>Cat.jpg</Path> and <Path>Cheetah.jpg</Path>) to get a flavour of what is possible. First, set each file's <AutoText key="metadata::dc.Title"/> field to be the same as its filename but without the filename extension:</Text>
     714<Text id="0352">We work with just the first three files (<Path>Bear.jpg</Path>, <Path>Cat.jpg</Path> and <Path>Cheetah.jpg</Path>) to get a flavour of what is possible. First, we need to add the <AutoText text="Dublin Core"/> metadata set which is not used in the <b>Simple image collection (image-e)</b> collection. Click the <AutoText key="glidict::MetadataSetDialog.Add_Title" type="button"/> button at the left bottom coner. A new window pops up showing the metadata sets used by current collection, click <AutoText key="glidict::MetadataSetDialog.Add" type="button"/> button brings up another window showing the available metadata sets. Select <AutoText text="Dublin Core Metadata Element Set, Version 1.1: Reference Description (dc)"/> from the list and click <AutoText key="glidict::MetadataSetDialog.Add_Set" type="button"/>. Click <AutoText key="glidict::General.Close" type="button"/> to return to the <AutoText key="glidict::GUI.Enrich"/> panel.</Text>
     715<Text id="0352a">First, set each file's <AutoText key="metadata::dc.Title"/> field to be the same as its filename but without the filename extension.</Text>
    718716<Text id="0353">Click on <Path>Bear.jpg</Path> so its metadata fields are available, then click on its <AutoText key="metadata::dc.Title"/> field on the right-hand side. Type in <b>Bear</b>.</Text>
    719717<Text id="0355">Repeat the process for <Path>Cat.jpg</Path> and <Path>Cheetah.jpg</Path>.</Text>
    … …  
    765763</Heading>
    766764<NumberedItem>
    767 <Text id="0366">Lets change the size of the thumbnail image and make it smaller. Thumbnail images are created by the <AutoText text="ImagePlug"/> plug-in, so we need to access its configuration settings. To do this, switch to the <AutoText key="glidict::GUI.Design"/> panel and select <AutoText key="glidict::CDM.GUI.Plugins"/> from the list on the left. Double-click <AutoText text="ImagePlug"/> to pop up a window that shows its settings. (Alternatively, select <AutoText text="ImagePlug"/> with a single click and then click <AutoText key="glidict::CDM.PlugInManager.Configure" type="button"/> further down the screen). Currently all options are off, so standard defaults are used. Select <AutoText text="thumbnailsize"/>, set it to <AutoText text="50"/>, and click <AutoText key="glidict::General.OK" type="button"/>.</Text>
     765<Text id="0366">Lets change the size of the thumbnail image and make it smaller. Thumbnail images are created by the <AutoText text="ImagePlugin"/> plug-in, so we need to access its configuration settings. To do this, switch to the <AutoText key="glidict::GUI.Design"/> panel and select <AutoText key="glidict::CDM.GUI.Plugins"/> from the list on the left. Double-click <AutoText text="ImagePlugin"/> to pop up a window that shows its settings. (Alternatively, select <AutoText text="ImagePlugin"/> with a single click and then click <AutoText key="glidict::CDM.PlugInManager.Configure" type="button"/> further down the screen). Currently most options are off, so standard defaults are used. Select <AutoText text="thumbnailsize"/>, set it to <AutoText text="50"/>, and click <AutoText key="glidict::General.OK" type="button"/>.</Text>
    768766</NumberedItem>
    769767<NumberedItem>
    … …  
    771769</NumberedItem>
    772770<NumberedItem>
    773 <Text id="0368">Once you have seen the result of the change, return to the <AutoText key="glidict::GUI.Design"/> panel, select the configuration options for <AutoText text="ImagePlug"/>, and switch the <AutoText text="thumbnailsize"/> option off so that the thumbnail reverts to its normal size when the collection is re-built.</Text>
     771<Text id="0368">Once you have seen the result of the change, return to the <AutoText key="glidict::GUI.Design"/> panel, select the configuration options for <AutoText text="ImagePlugin"/>, and switch the <AutoText text="thumbnailsize"/> option off so that the thumbnail reverts to its normal size when the collection is re-built.</Text>
    774772</NumberedItem>
    775773<Heading>
    … …  
    777775</Heading>
    778776<NumberedItem>
    779 <Text id="0381">Now we'll add a new browsing option based on the descriptions. In the <AutoText key="glidict::GUI.Design"/> panel, select <AutoText key="glidict::CDM.GUI.Classifiers"/> from the left-hand list. Set the menu item for <AutoText key="glidict::CDM.ClassifierManager.Classifier"/> to <AutoText text="AZList" />; then click <AutoText key="glidict::CDM.ClassifierManager.Add" type="button"/>.</Text>
     777<Text id="0381">Now we'll add a new browsing option based on the descriptions. In the <AutoText key="glidict::GUI.Design"/> panel, select <AutoText key="glidict::CDM.GUI.Classifiers"/> from the left-hand list. Set the menu item for <AutoText key="glidict::CDM.ClassifierManager.Classifier"/> to <AutoText text="List" />; then click <AutoText key="glidict::CDM.ClassifierManager.Add" type="button"/>.</Text>
    780778</NumberedItem>
    781779<NumberedItem>
    … …  
    795793</NumberedItem>
    796794<NumberedItem>
    797 <Text id="0386">Switch to the <AutoText key="glidict::GUI.Create"/> panel, <b>build</b> the collection, then <b>preview</b> it. There is now a <AutoText key="coredm::_Global:labelSearch_"/> button in the navigation bar. As an example, search for the term "bear" in the <i>document:dc.Description</i> index (which is the only index at this point).</Text>
    798 </NumberedItem>
    799 <NumberedItem>
    800 <Text id="0386a">To change the text that is displayed for the index (document:dc.Description), go to the <AutoText key="glidict::GUI.Format"/> panel back in the Librarian Interface. Select <AutoText key="glidict::CDM.GUI.SearchMetadata"/> from the left-hand list. This panel allows you to change the text that is displayed on the search form. Change the <AutoText key="glidict::CDM.SearchMetadataManager.Component_Name"/> for the <AutoText text="document:dc.Description"/> index to "descriptions" (or other suitable text). Go back to the browser and reload the search page. Your new text will appear in the search form.</Text>
     795<Text id="0386">Switch to the <AutoText key="glidict::GUI.Create"/> panel, <b>build</b> the collection, then <b>preview</b> it. There is now a <AutoText key="coredm::_Global:labelSearch_"/> button in the navigation bar. As an example, search for the term "bear" in the <AutoText key="coredm::_Global:labelDescription_" type="italics"/> index (which is the only index at this point).</Text>
     796</NumberedItem>
     797<NumberedItem>
     798<Text id="0386a">To change the text that is displayed for the index (document:dc.Description), go to the <AutoText key="glidict::GUI.Format"/> panel back in the Librarian Interface. Select <AutoText key="glidict::CDM.GUI.SearchMetadata"/> from the left-hand list. This panel allows you to change the text that is displayed on the search form. Change the <AutoText key="glidict::CDM.SearchMetadataManager.Component_Name"/> for the <AutoText key="coredm::_Global:labelDescription_" type="italics"/> index to "image descriptions" (or other suitable text). Go back to the browser and reload the search page. Your new text will appear in the search form.</Text>
    801799</NumberedItem>
    802800</Content>
    … …  
    807805</Title>
    808806<SampleFiles folder="Word_and_PDF"/>
    809 <Version initial="2.60" current="2.80"/>
     807<Version initial="2.60" current="2.82"/>
    810808<Content>
    811809<Comment>
    … …  
    816814</NumberedItem>
    817815<NumberedItem>
    818 <Text id="0282">Copy all the .doc, .rtf, .pdf and .ps files from <Path>sample_files &rarr; Word_and_PDF &rarr; Documents</Path> into the collection. There are 10 files in all: you can select multiple files by clicking on the first one and shift-clicking on the last one, and drag them all across together. (This is the normal technique of multiple selection.)</Text>
     816<Text id="0282">Copy all the .doc, .rtf, .pdf and .ps files from <Path>sample_files &rarr; Word_and_PDF &rarr; Documents</Path> into the collection. There are 9 files in all: you can select multiple files by clicking on the first one and shift-clicking on the last one, and drag them all across together. (This is the normal technique of multiple selection.)</Text>
    819817</NumberedItem>
    820818<NumberedItem>
    … …  
    828826</NumberedItem>
    829827<NumberedItem>
    830 <Text id="0289a">Back in the Librarian Interface, click the <AutoText key="glidict::GUI.Enrich"/> tab to view the automatically extracted metadata. You will need to scroll down to see the extracted metadata, which begins with <AutoText text="ex." type="quoted"/>. </Text>
     828<Text id="0289a">Back in the Librarian Interface, click the <AutoText key="glidict::GUI.Enrich"/> tab to view the automatically extracted metadata. You will need to scroll down to see the extracted metadata, which begins with <AutoText text="ex." type="quoted"/>.</Text>
    831829</NumberedItem>
    832830<NumberedItem>
    … …  
    861859</Heading>
    862860<NumberedItem>
    863 <Text id="0304">In the Librarian Interface, look at the <AutoText key="glidict::CDM.GUI.Plugins"/> section of the <AutoText key="glidict::GUI.Design"/> panel, by clicking on this in the list to the left. Here you can add, configure or remove plugins to be used in the collection. There is no need to remove any plugins, but it will speed up processing a little. In this case we have only Word, PDF, RTF, and PostScript documents, and can remove the <AutoText text="ZIPPlug"/>, <AutoText text="TEXTPlug"/>, <AutoText text="HTMLPlug"/>, <AutoText text="EMAILPlug"/>, <AutoText text="ImagePlug"/>, <AutoText text="ISISPlug"/> and <AutoText text="NULPlug"/> plugins. To delete a plugin, select it and click <AutoText key="glidict::CDM.PlugInManager.Remove" type="button"/>. <AutoText text="GAPlug"/> and <AutoText text="MetadataXMLPlug"/> are required for any type of source collection and should not be removed. </Text>
     861<Text id="0304">In the Librarian Interface, look at the <AutoText key="glidict::CDM.GUI.Plugins"/> section of the <AutoText key="glidict::GUI.Design"/> panel, by clicking on this in the list to the left. Here you can add, configure or remove plugins to be used in the collection. There is no need to remove any plugins, but it will speed up processing a little. In this case we have only Word, PDF, RTF, and PostScript documents, and can remove the <AutoText text="ZIPPlugin"/>, <AutoText text="TextPlugin"/>, <AutoText text="HTMLPlugin"/>, <AutoText text="EmailPlugin"/>, <AutoText text="PowerPointPlugin"/>, <AutoText text="ExcelPlugin"/>, <AutoText text="ImagePlugin"/>, <AutoText text="ISISPlug"/> and <AutoText text="NULPlugin"/> plugins. To delete a plugin, select it and click <AutoText key="glidict::CDM.PlugInManager.Remove" type="button"/>. <AutoText text="GreenstoneXMLPlugin"/> is required for any type of source collection and should not be removed.</Text>
    864862</NumberedItem>
    865863<Heading>
    … …  
    870868</NumberedItem>
    871869<NumberedItem>
    872 <Text id="0310b">Modify the <AutoText key="metadata::ex.Title"/> index to include <AutoText key="metadata::dc.Title"/> by selecting the index in the <AutoText key="glidict::CDM.IndexManager.Indexes"/> box and clicking <AutoText key="glidict::CDM.IndexManager.Edit_Index" type="button"/>. Select <AutoText key="metadata::dc.Title"/> from the list of metadata, and click <AutoText key="glidict::CDM.IndexManager.Replace_Index" type="button"/>. Searching this index will search both <AutoText key="metadata::dc.Title"/> and <AutoText key="metadata::ex.Title"/> metadata. If you want to restrict searching to just the manually added <AutoText key="metadata::dc.Title"/> metadata, edit the index again and deselect <AutoText key="metadata::ex.Title"/> from the list of metadata.</Text>
     870<Text id="0310b">By default the title index <AutoText text="dc.Title,ex.Title"/> includes <AutoText key="metadata::dc.Title"/> and <AutoText key="metadata::ex.Title"/>. Searching this index will search both <AutoText key="metadata::dc.Title"/> and <AutoText key="metadata::ex.Title"/> metadata. If you want to restrict searching to just the manually added <AutoText key="metadata::dc.Title"/> metadata, edit the index again and deselect <AutoText key="metadata::ex.Title"/> from the list of metadata.</Text>
    873871</NumberedItem>
    874872<NumberedItem>
    … …  
    879877</Heading>
    880878<NumberedItem>
    881 <Text id="0315a">The <AutoText key="glidict::CDM.GUI.Classifiers"/> section adds "classifiers," which provide the collection with browsing functions. Go to this section and observe that Greenstone has provided two classifiers, <i>AZLists</i> based on <AutoText key="metadata::ex.Title"/> and <AutoText key="metadata::ex.Source"/> metadata. These correspond to the <AutoText key="coredm::_Global:labelTitle_" type="italics"/> and <AutoText key="coredm::_Global:labelSource_" type="italics"/> buttons on the collection's access bar. </Text>
     879<Text id="0315a">The <AutoText key="glidict::CDM.GUI.Classifiers"/> section adds "classifiers," which provide the collection with browsing functions. Go to this section and observe that Greenstone has provided two classifiers, <i>List</i> based on <AutoText text="dc.Title;Title"/> and <AutoText key="metadata::ex.Source"/> metadata. These correspond to the <AutoText key="coredm::_Global:labelTitle_" type="italics"/> and <AutoText key="coredm::_Global:labelSource_" type="italics"/> buttons on the collection's access bar. </Text>
    882880<Text id="0315a-1">Remove the <AutoText key="metadata::ex.Source"/> classifier by selecting it and clicking <AutoText key="glidict::CDM.ClassifierManager.Remove" type="button"/>.</Text>
    883881</NumberedItem>
    884882<NumberedItem>
    885 <Text id="0315b">Modify the <AutoText key="metadata::ex.Title"/> classifier to use <AutoText key="metadata::dc.Title"/> instead. Select the classifier and click <AutoText key="glidict::CDM.ClassifierManager.Configure" type="button"/>. In the <AutoText text="metadata"/> box, select <AutoText key="metadata::dc.Title"/> instead of <AutoText key="metadata::ex.Title"/>. Click <AutoText key="glidict::General.OK" type="button"/>.</Text>
     883<Text id="0315b">Modify the <AutoText text="dc.Title;Title"/> classifier to use <AutoText key="metadata::dc.Title"/> instead. Select the classifier and click <AutoText key="glidict::CDM.ClassifierManager.Configure" type="button"/>. In the <AutoText text="metadata"/> box, select <AutoText key="metadata::dc.Title"/> instead of <AutoText text="dc.Title;Title"/>. Click <AutoText key="glidict::General.OK" type="button"/>.</Text>
    886884</NumberedItem>
    887885<NumberedItem>
    888886<Text id="0318a">Now add an <AutoText text="AZCompactList"/> classifier for <AutoText key="metadata::dc.Creator"/>. Select <AutoText text="AZCompactList"/> from the <AutoText key="glidict::CDM.ClassifierManager.Classifier"/> drop-down list and click <AutoText key="glidict::CDM.ClassifierManager.Add" type="button"/>. A popup window <AutoText key="glidict::CDM.ArgumentConfiguration.Title"/> appears. Select <AutoText key="metadata::dc.Creator"/> from the <AutoText text="metadata"/> drop-down list and click <AutoText key="glidict::General.OK" type="button"/>.</Text>
    889 <Text id="0318b"><AutoText text="AZCompactList"/> is like <AutoText text="AZList"/>, except that values that appear multiple times in the hierarchy are automatically grouped together and a new node, shown as a bookshelf icon, is formed.</Text>
     887<Text id="0318b"><AutoText text="AZCompactList"/> is like <AutoText text="List"/>, except that values that appear multiple times in the hierarchy are automatically grouped together and a new node, shown as a bookshelf icon, is formed.</Text>
    890888</NumberedItem>
    891889<NumberedItem>
    … …  
    893891</NumberedItem>
    894892<NumberedItem>
    895 <Text id="0321">Check that all the facilities work properly. There should be three full-text indexes, called <i>text</i>, <i>dc.Title</i>, and <i>dc.Creator</i>. The <AutoText key="coredm::_Global:labelTitle_" type="italics"/> list should display all the documents to which you have assigned <AutoText key="metadata::dc.Title"/> metadata (and only those documents). The <AutoText key="coredm::_Global:labelCreator_" type="italics"/> list should show one bookshelf for each author you have assigned as <AutoText key="metadata::dc.Creator"/>, and clicking on that bookshelf should take you to all the documents they authored.</Text>
    896 </NumberedItem>
     893<Text id="0321">Check that all the facilities work properly. There should be three full-text indexes, called <i>text</i>, <AutoText key="coredm::_Global:labelTitle_" type="italics"/>, and <AutoText key="coredm::_Global:labelCreator_" type="italics"/>. The <AutoText key="coredm::_Global:labelTitle_" type="italics"/> list should display all the documents to which you have assigned <AutoText key="metadata::dc.Title"/> metadata (and only those documents). The <AutoText key="coredm::_Global:labelCreator_" type="italics"/> list should show one bookshelf for each author you have assigned as <AutoText key="metadata::dc.Creator"/>, and clicking on that bookshelf should take you to all the documents they authored.</Text>
     894</NumberedItem>
     895<!-- This is no longer needed and we have changed index names in the simple image tutorial before -->
     896<!--
    897897<Heading>
    898898<Text id="0321-1">Renaming the search indexes</Text>
    … …  
    902902</NumberedItem>
    903903<NumberedItem>
    904 <Text id="0321-3">Select <AutoText key="glidict::CDM.GUI.SearchMetadata"/> in the left hand list. This section allows you to modify what text is displayed for the drop-down lists in the search form (indexes, subcollections, levels etc). Set the  <AutoText key="glidict::CDM.SearchMetadataManager.Component_Name"/> for the <AutoText text="dc.Title,Title"/> index to be "titles", and that for the <AutoText text="dc.Creator"/> index to be "creators". Preview the collection by clicking the <AutoText key="glidict::CreatePane.Preview_Collection"/>. The search form should display the new text.</Text>
    905 </NumberedItem>
     904<Text id="0321-3">Select <AutoText key="glidict::CDM.GUI.SearchMetadata"/> in the left hand list. This section allows you to modify what text is displayed for the drop-down lists in the search form (indexes, subcollections, levels etc). Set the  <AutoText key="glidict::CDM.SearchMetadataManager.Component_Name"/> for the <AutoText text="dc.Title"/> (or <AutoText text="dc.Title,Title"/> if you didn't deselect <AutoText key="metadata::ex.Title"/> in the search index) index to be "titles", and that for the <AutoText text="dc.Creator"/> index to be "creators". Preview the collection by clicking the <AutoText key="glidict::CreatePane.Preview_Collection"/>. The search form should display the new text.</Text>
     905</NumberedItem>
     906-->
    906907<Heading>
    907908<Text id="0321a">Classifying on multiple metadata</Text>
    … …  
    911912</NumberedItem>
    912913<NumberedItem>
    913 <Text id="0321c">In the <AutoText key="glidict::CDM.GUI.Classifiers"/> section of the <AutoText key="glidict::GUI.Design"/> panel, select the <AutoText text="AZList"/> for <AutoText key="metadata::dc.Title"/> in the <AutoText key="glidict::CDM.ClassifierManager.Assigned"/> box and click <AutoText key="glidict::CDM.ClassifierManager.Configure" type="button"/>. Note you can achieve the same result by double clicking on the classifier.</Text>
    914 </NumberedItem>
    915 <NumberedItem>
    916 <Text id="0321d">In the <AutoText text="metadata"/> field, type <AutoText text=",ex.Title" type="quoted"/> after the <AutoText key="metadata::dc.Title" type="quoted"/>&mdash;i.e. make it read</Text>
    917 <Format>
    918 <AutoText key="metadata::dc.Title" type="plain"/><AutoText text=",ex.Title" type="plain"/>
     914<Text id="0321c">In the <AutoText key="glidict::CDM.GUI.Classifiers"/> section of the <AutoText key="glidict::GUI.Design"/> panel, select the <AutoText text="List"/> for <AutoText key="metadata::dc.Title"/> in the <AutoText key="glidict::CDM.ClassifierManager.Assigned"/> box and click <AutoText key="glidict::CDM.ClassifierManager.Configure" type="button"/>. Note you can achieve the same result by double clicking on the classifier.</Text>
     915</NumberedItem>
     916<NumberedItem>
     917<Text id="0321d">In the <AutoText text="metadata"/> field, type <AutoText text=";Title" type="quoted"/> after the <AutoText key="metadata::dc.Title" type="quoted"/>&mdash;i.e. make it read</Text>
     918<Format>
     919<AutoText key="metadata::dc.Title" type="plain"/><AutoText text=";Title" type="plain"/>
    919920</Format>
    920921</NumberedItem>
    … …  
    933934</Title>
    934935<Prerequisite id="word_pdf_collection"/>
    935 <Version initial="2.70w" current="2.80"/>
     936<Version initial="2.70w" current="2.82"/>
    936937<Content>
    937938<Comment>
    … …  
    10531054</Title>
    10541055<SampleFiles folder="Word_and_PDF"/>
    1055 <Version initial="2.70" current="2.80"/>
     1056<Version initial="2.70" current="2.82"/>
    10561057<Content>
    10571058<Text id="ep-2">Greenstone converts PDF files to HTML using third-party software: <AutoText text="pdftohtml.pl" type="italics"/>. This lets users view these documents even if they don't have the PDF software installed. Unfortunately, sometimes the formatting of the resulting HTML files is not so good.</Text>
    … …  
    10811082</Heading>
    10821083<NumberedItem>
    1083 <Text id="ep-6">In the <AutoText key="glidict::CDM.GUI.Plugins"/> section of the <AutoText key="glidict::GUI.Design"/> panel, configure <AutoText text="PDFPlug"/>. Switch on the <AutoText text="use_sections"/> option. </Text>
     1084<Text id="ep-6">In the <AutoText key="glidict::CDM.GUI.Plugins"/> section of the <AutoText key="glidict::GUI.Design"/> panel, configure <AutoText text="PDFPlugin"/>. Switch on the <AutoText text="use_sections"/> option. </Text>
    10841085<Text id="ep-6a">In the <AutoText key="glidict::CDM.GUI.Indexes"/> section, check the <AutoText key="glidict::CDM.LevelManager.Section"/> checkbox to build the indexes on section level as well as document level.</Text>
    10851086<Text id="ep-7"><b>Build</b> and <b>preview</b> the collection. View the text versions of some of the PDF documents. Note that these are now split into a series of pages, and a "go to page" box is provided. The format is still a bit ugly though, and pdf05-notext.pdf is still not processed.</Text>
    … …  
    10921093</NumberedItem>
    10931094<NumberedItem>
    1094 <Text id="ep-13">In the <AutoText key="glidict::CDM.GUI.Plugins"/> section, configure <AutoText text="PDFPlug"/>. Set the <AutoText text="convert_to"/> option to one of the image types, e.g. <AutoText text="pagedimg_jpg"/>. Switch off the <AutoText text="use_sections"/> option, as it is not used with image conversion. </Text>
     1095<Text id="ep-13">In the <AutoText key="glidict::CDM.GUI.Plugins"/> section, configure <AutoText text="PDFPlugin"/>. Set the <AutoText text="convert_to"/> option to one of the image types, e.g. <AutoText text="pagedimg_jpg"/>. Switch off the <AutoText text="use_sections"/> option, as it is not used with image conversion. </Text>
    10951096</NumberedItem>
    10961097<NumberedItem>
    … …  
    11241125</NumberedItem>
    11251126<NumberedItem>
    1126 <Text id="ep-21">We achieve this by putting the problem files into a separate folder, and adding another <AutoText text="PDFPlug"/> plugin with different options.</Text>
     1127<Text id="ep-21">We achieve this by putting the problem files into a separate folder, and adding another <AutoText text="PDFPlugin"/> plugin with different options.</Text>
    11271128</NumberedItem>
    11281129<NumberedItem>
    … …  
    11311132</NumberedItem>
    11321133<NumberedItem>
    1133 <Text id="ep-23b">Change to <AutoText key="glidict::Preferences.Mode.Systems"/> mode so that you can add two of the same plugin, and use regular expressions in the plugin options (<Menu><AutoText key="glidict::Menu.File"/> &rarr; <AutoText key="glidict::Menu.File_Options"/> &rarr; <AutoText key="glidict::Preferences.Mode"/></Menu>). </Text>
     1134<Text id="ep-23b">For versions before 2.82, you need to change to <AutoText text="Library Systems Specialist"/> mode in order to add two of the same plugin, and use regular expressions in the plugin options (<Menu><AutoText key="glidict::Menu.File"/> &rarr; <AutoText key="glidict::Menu.File_Options"/> &rarr; <AutoText key="glidict::Preferences.Mode"/></Menu>). </Text>
    11341135<Comment>
    11351136<Text id="ep-23c">For version 2.71, you'll need to close GLI now then restart it to get the list of plugins to update properly.</Text>
    … …  
    11371138</NumberedItem>
    11381139<NumberedItem>
    1139 <Text id="ep-24">Switch to the <AutoText key="glidict::CDM.GUI.Plugins"/> section of the <AutoText key="glidict::GUI.Design"/> panel. Add a second PDF plugin by selecting <AutoText text="PDFPlug"/> from the <AutoText key="glidict::CDM.PlugInManager.PlugIn"/> drop-down list, and clicking <AutoText key="glidict::CDM.PlugInManager.Add" type="button"/>. This plugin will come after the first PDF plugin, so we configure it to process PDF documents as HTML. Set the <AutoText text="convert_to"/> option to <AutoText text="html"/>, and switch on the <AutoText text="use_sections"/> option. Click <AutoText key="glidict::General.OK" type="button"/>.</Text>
     1140<Text id="ep-24">Switch to the <AutoText key="glidict::CDM.GUI.Plugins"/> section of the <AutoText key="glidict::GUI.Design"/> panel. Add a second PDF plugin by selecting <AutoText text="PDFPlugin"/> from the <AutoText key="glidict::CDM.PlugInManager.PlugIn"/> drop-down list, and clicking <AutoText key="glidict::CDM.PlugInManager.Add" type="button"/>. This plugin will come after the first PDF plugin, so we configure it to process PDF documents as HTML. Set the <AutoText text="convert_to"/> option to <AutoText text="html"/>, and switch on the <AutoText text="use_sections"/> option. Click <AutoText key="glidict::General.OK" type="button"/>.</Text>
    11401141</NumberedItem>
    11411142<NumberedItem>
    … …  
    11451146<Text id="ep-26">The two PDF plugins should have options like the following:</Text>
    11461147<Format>
    1147 plugin PDFPlug -convert_to pagedimg_jpg -process_exp "notext.*\.pdf"<br/>
    1148 plugin PDFPlug -convert_to html -use_sections
    1149 </Format>
    1150 <Text id="ep-27">The <AutoText text="paged_img" type="italics"/> version must come earlier in the list than the <AutoText text="html" type="italics"/> version. The <AutoText text="process_exp"/> for the first <AutoText text="PDFPlug"/> will process any PDF files in the <Path>notext</Path> directory. The second <AutoText text="PDFPlug"/> will process any PDF files that are not processed by the first one.</Text>
    1151 <Text id="ep-28">Note that all plugins have the <AutoText text="process_exp"/> option, and this can be used to customize which documents are processed by which plugin. This option is only visible in <AutoText key="glidict::Preferences.Mode.Systems"/> and <AutoText key="glidict::Preferences.Mode.Expert"/> modes.</Text>
    1152 <Text id="ep-29">Change back to <AutoText key="glidict::Preferences.Mode.Librarian"/> mode.</Text>
     1148plugin PDFPlugin -convert_to pagedimg_jpg -process_exp "notext.*\.pdf"<br/>
     1149plugin PDFPlugin -convert_to html -use_sections
     1150</Format>
     1151<Text id="ep-27">The <AutoText text="paged_img" type="italics"/> version must come earlier in the list than the <AutoText text="html" type="italics"/> version. The <AutoText text="process_exp"/> for the first <AutoText text="PDFPlugin"/> will process any PDF files in the <Path>notext</Path> directory. The second <AutoText text="PDFPlugin"/> will process any PDF files that are not processed by the first one.</Text>
     1152<Text id="ep-28">Note that all plugins have the <AutoText text="process_exp"/> option, and this can be used to customize which documents are processed by which plugin. For versions before 2.82, this option is only visible in <AutoText text="Library Systems Specialist"/> and <AutoText key="glidict::Preferences.Mode.Expert"/> modes.</Text>
     1153<Text id="ep-29">For versions before 2.82, change back to <AutoText key="glidict::Preferences.Mode.Librarian"/> mode.</Text>
    11531154</NumberedItem>
    11541155<NumberedItem>
    … …  
    11661167<NumberedItem>
    11671168<Text id="fw-24c">The search terms are kept in the macro variable <AutoText text="_cgiargq_"/>, and we append <AutoText text="#search=&quot;_cgiargq_&quot;"/> to the end of a PDF file link to pass the query terms to the PDF file.</Text>
    1168 <Text id="fw-24d"><AutoText text="PDFPlug"/> renames each PDF file as <AutoText text="doc.pdf"/> and saves it in a unique directory for that document, so we use</Text>
     1169<Text id="fw-24d"><AutoText text="PDFPlugin"/> renames each PDF file as <AutoText text="doc.pdf"/> and saves it in a unique directory for that document, so we use</Text>
    11691170<Format>_httpcollection_/index/assoc/[archivedir]/doc.pdf</Format>
    1170 <Text id="fw-24e">to refer to the PDF source file. (However, if you used the <AutoText text="-keep_original_filename"/> option to <AutoText text="PDFPlug"/> when building the collection, the original name of the PDF file is kept, and we use</Text>
     1171<Text id="fw-24e">to refer to the PDF source file. (However, if you used the <AutoText text="-keep_original_filename"/> option to <AutoText text="PDFPlugin"/> when building the collection, the original name of the PDF file is kept, and we use</Text>
    11711172<Format>_httpcollection_/index/assoc/[archivedir]/[Source]</Format>
    11721173<Text id="fw-24f">instead to locate the PDF source file.)</Text>
    11731174</NumberedItem>
    11741175<NumberedItem>
    1175 <Text id="fw-24g">Select <AutoText text="SearchVList"/> from the list of assigned formats. We need to test whether the file is a PDF file before linking to doc.pdf, using <Format>{If}{[ex.FileFormat] eq 'PDF',,}</Format>. For PDF files, we use the above format instead of the <Format>[ex.srclink]</Format> and <Format>[ex./srclink]</Format> variables to link to the file.</Text>
     1176<Text id="fw-24g">Add <AutoText text="SearchVList"/> by selecting <AutoText text="Search"/> from the <AutoText key="glidict::CDM.FormatManager.Feature"/> drop down list, and <AutoText text="VList"/> from the <AutoText key="glidict::CDM.FormatManager.Part"/> list. Click <AutoText key="glidict::CDM.FormatManager.Add" type="button"/> to add the <AutoText text="SearchVList"/> format statement into the list of assigned formats. We need to test whether the file is a PDF file before linking to doc.pdf, using <Format>{If}{[ex.FileFormat] eq 'PDF',,}</Format>. For PDF files, we use the above format instead of the <Format>[ex.srclink]</Format> and <Format>[ex./srclink]</Format> variables to link to the file.</Text>
    11761177<Text id="fw-24b">The resulting format statement is:</Text>
    11771178<Format>
    11781179&lt;td valign="top"&gt;[link][icon][/link]&lt;/td&gt;<br/>
    11791180&lt;td valign="top"&gt;<highlight>{If}{[ex.FileFormat] eq 'PDF', &lt;a
    1180 href=\"_httpcollection_/index/assoc/[archivedir]/doc.pdf#search=&amp;quot;_cgiargq_&amp;quot;\"&gt;[ex.srcicon]&lt;/a&gt;,<br/>[ex.srclink][ex.srcicon][ex./srclink]}</highlight>&lt;/td&gt;<br/>
     1181href=\"_httpcollection_/index/assoc/[archivedir]/doc.pdf#search=&amp;quot;_cgiargq_&amp;quot;\"&gt;{Or}{[ex.thumbicon],[ex.srcicon]}&lt;/a&gt;,<br/>[ex.srclink]{Or}{[ex.thumbicon],[ex.srcicon]}[ex./srclink]}</highlight>&lt;/td&gt;<br/>
    11811182&lt;td valign="top"&gt;[highlight]<br/>
    11821183{Or}{[dc.Title],[ex.Title],Untitled}<br/>
    … …  
    11911192<Text id="ew-a">Enhanced Word document handling</Text>
    11921193</Title>
    1193 <Version initial="2.70w" current="2.80"/>
     1194<Version initial="2.70w" current="2.82"/>
    11941195<Prerequisite id="word_pdf_collection"/>
    11951196<Content>
    … …  
    12021203</Heading>
    12031204<NumberedItem>
    1204 <Text id="ew-4">In the Librarian Interface, open up the <b>reports</b> collection. Switch to the <AutoText key="glidict::GUI.Design"/> panel and select the <AutoText key="glidict::CDM.GUI.Plugins"/> section on the left-hand side. Double click the <AutoText text="WordPlug"/> plugin and switch on the <AutoText text="windows_scripting"/> option.</Text>
     1205<Text id="ew-4">In the Librarian Interface, open up the <b>reports</b> collection. Switch to the <AutoText key="glidict::GUI.Design"/> panel and select the <AutoText key="glidict::CDM.GUI.Plugins"/> section on the left-hand side. Double click the <AutoText text="WordPlugin"/> plugin and switch on the <AutoText text="windows_scripting"/> option.</Text>
    12051206<Text id="ew-4a">In the <AutoText key="glidict::CDM.GUI.Indexes"/> section, check the <AutoText key="glidict::CDM.LevelManager.Section"/> checkbox to build the indexes on section level as well as document level.</Text>
    12061207</NumberedItem>
    12071208<NumberedItem>
    12081209<Text id="ew-5"><b>Build</b> the collection. You will notice that the Microsoft Word program is started up for each Word document&mdash;the document is saved as HTML from Word itself, to get a better conversion. <b>Preview</b> the collection. In the <AutoText key="coredm::_Global:labelTitle_"/> list, notice that <Path>word03.doc</Path> and <Path>word06.doc</Path> now have a book icon, rather than a page icon. These now appear with hierarchical structure.</Text>
    1209 <Text id="ew-6">The default behaviour for <AutoText text="WordPlug"/> with <AutoText text="windows_scripting"/> is to section the document based on <AutoText text="Heading 1" type="quoted"/>, <AutoText text="Heading 2" type="quoted"/>, <AutoText text="Heading 3" type="quoted"/> styles. If you open up the <Path>word03.doc</Path> or <Path>word06.doc</Path> documents in Word, you will see that the sections use these Heading styles.</Text>
     1210<Text id="ew-6">The default behaviour for <AutoText text="WordPlugin"/> with <AutoText text="windows_scripting"/> is to section the document based on <AutoText text="Heading 1" type="quoted"/>, <AutoText text="Heading 2" type="quoted"/>, <AutoText text="Heading 3" type="quoted"/> styles. If you open up the <Path>word03.doc</Path> or <Path>word06.doc</Path> documents in Word, you will see that the sections use these Heading styles.</Text>
    12101211<Text id="ew-7">Note, to view style information in Word, you can select <Menu>Format &rarr; Styles and Formatting</Menu> from the menu, and a side bar will appear on the right hand side. Click on a section heading and the formatting information will be displayed in this side bar.</Text>
    12111212</NumberedItem>
    12121213<NumberedItem>
    1213 <Text id="ew-8">Some of the documents do not use styles (e.g. <Path>word01.doc</Path>) and no structure can be extracted from them. Some documents use user-defined styles. <AutoText text="WordPlug"/> can be configured to use these styles instead of <AutoText text="Heading 1" type="plain"/>, <AutoText text="Heading 2" type="plain"/> etc. Next we will configure <AutoText text="WordPlug"/> to use the styles found in <Path>word05.doc</Path>.</Text>
     1214<Text id="ew-8">Some of the documents do not use styles (e.g. <Path>word01.doc</Path>) and no structure can be extracted from them. Some documents use user-defined styles. <AutoText text="WordPlugin"/> can be configured to use these styles instead of <AutoText text="Heading 1" type="plain"/>, <AutoText text="Heading 2" type="plain"/> etc. Next we will configure <AutoText text="WordPlugin"/> to use the styles found in <Path>word05.doc</Path>.</Text>
    12141215</NumberedItem>
    12151216<Heading>
    … …  
    12171218</Heading>
    12181219<NumberedItem>
    1219 <Text id="ew-8b">The Librarian Interface can operate in four modes. Go to <Menu><AutoText key="glidict::Menu.File"/> &rarr; <AutoText key="glidict::Menu.File_Options"/> &rarr; <AutoText key="glidict::Preferences.Mode"/></Menu> and see the four modes and what functionality they provide access to. <AutoText key="glidict::Preferences.Mode.Librarian"/> is the default mode.</Text>
    1220 </NumberedItem>
    1221 <NumberedItem>
    1222 <Text id="ew-10">Change the mode to <AutoText key="glidict::Preferences.Mode.Systems"/> because you will need to use regular expressions to set up the style options in the next part of the exercise.</Text>
     1220<Text id="ew-8b">Since versions 2.82, the Librarian Interface operates in three modes, while for versions before 2.82 GLI operates in four modes. Go to <Menu><AutoText key="glidict::Menu.File"/> &rarr; <AutoText key="glidict::Menu.File_Options"/> &rarr; <AutoText key="glidict::Preferences.Mode"/></Menu> and see the modes and what functionality they provide access to. <AutoText key="glidict::Preferences.Mode.Librarian"/> is the default mode.</Text>
     1221</NumberedItem>
     1222<NumberedItem>
     1223<Text id="ew-10">For versions before 2.82, change the mode to <AutoText text="Library Systems Specialist"/> because you will need to use regular expressions to set up the style options in the next part of the exercise.</Text>
    12231224</NumberedItem>
    12241225<Heading>
    … …  
    12461247</NumberedItem>
    12471248<NumberedItem>
    1248 <Text id="ew-11">In the <AutoText key="glidict::CDM.GUI.Plugins"/> section of the <AutoText key="glidict::GUI.Design"/> panel, select <AutoText text="WordPlug"/> and click <AutoText key="glidict::CDM.PlugInManager.Configure" type="button"/>. Four types of header can be set which are:</Text>
     1249<Text id="ew-11">In the <AutoText key="glidict::CDM.GUI.Plugins"/> section of the <AutoText key="glidict::GUI.Design"/> panel, select <AutoText text="WordPlugin"/> and click <AutoText key="glidict::CDM.PlugInManager.Configure" type="button"/>. Four types of header can be set which are:</Text>
    12491250<Format>
    12501251<BulletList>
    … …  
    12631264title_header: ManualTitle
    12641265</Format>
    1265 <Comment>
    1266 <Text id="ew-23b">If you can't see these options in the <AutoText text="WordPlug"/> configuration pane, check that you are in <AutoText key="glidict::Preferences.Mode.Systems"/> mode as described above.</Text>
    1267 </Comment>
     1266<!--
     1267<Comment>
     1268<Text id="ew-23b">If you can't see these options in the <AutoText text="WordPlugin"/> configuration pane, check that you are in <AutoText text="Library Systems Specialist"/> mode as described above.</Text>
     1269</Comment>
     1270-->
    12681271<Text id="ew-23">Once these are set, click <AutoText key="glidict::General.OK" type="button"/>.</Text>
    12691272</NumberedItem>
    … …  
    12791282</Heading>
    12801283<NumberedItem>
    1281 <Text id="ew-21">If you look at the HTML versions of <Path>word05.doc</Path> and <Path>word06.doc</Path>, you will see that it now has two tables of contents. One is generated by Greenstone based on the document's styles, the other was already defined in the Word document. WordPlug can be configured to remove predefined tables of contents and tables of figures. The tables must be defined with Word styles in order for this to work.</Text>
    1282 </NumberedItem>
    1283 <NumberedItem>
    1284 <Text id="ew-22">To remove the tables of contents and figures from <Path>word06.doc</Path> and the table of contents from <Path>word05.doc</Path>, switch on the <AutoText text="delete_toc"/> option in <AutoText text="WordPlug"/>. Set the <AutoText text="toc_header"/> option to <Format>(MsoToc1|MsoToc2|MsoToc3|MsoTof|TOA)</Format>. In this document, the table of contents and list of figures use these four style names. Click <AutoText key="glidict::General.OK" type="button"/>.</Text>
     1284<Text id="ew-21">If you look at the HTML versions of <Path>word05.doc</Path> and <Path>word06.doc</Path>, you will see that it now has two tables of contents. One is generated by Greenstone based on the document's styles, the other was already defined in the Word document. <AutoText text="WordPlugin"/> can be configured to remove predefined tables of contents and tables of figures. The tables must be defined with Word styles in order for this to work.</Text>
     1285</NumberedItem>
     1286<NumberedItem>
     1287<Text id="ew-22">To remove the tables of contents and figures from <Path>word06.doc</Path> and the table of contents from <Path>word05.doc</Path>, switch on the <AutoText text="delete_toc"/> option in <AutoText text="WordPlugin"/>. Set the <AutoText text="toc_header"/> option to <Format>(MsoToc1|MsoToc2|MsoToc3|MsoTof|TOA)</Format>. In this document, the table of contents and list of figures use these four style names. Click <AutoText key="glidict::General.OK" type="button"/>.</Text>
    12851288</NumberedItem>
    12861289<NumberedItem>
    … …  
    12881291</NumberedItem>
    12891292<NumberedItem>
    1290 <Text id="ew-24a">Switch the Librarian Interface back to <AutoText key="glidict::Preferences.Mode.Librarian"/> mode (<Menu><AutoText key="glidict::Menu.File"/> &rarr; <AutoText key="glidict::Menu.File_Options"/> &rarr; <AutoText key="glidict::Preferences.Mode"/></Menu>).</Text>
     1293<Text id="ew-24a">For versions before 2.82, switch the Librarian Interface back to <AutoText key="glidict::Preferences.Mode.Librarian"/> mode (<Menu><AutoText key="glidict::Menu.File"/> &rarr; <AutoText key="glidict::Menu.File_Options"/> &rarr; <AutoText key="glidict::Preferences.Mode"/></Menu>).</Text>
    12911294</NumberedItem>
    12921295<Heading>
    … …  
    12971300</NumberedItem>
    12981301<NumberedItem>
    1299 <Text id="ew-27">In the <AutoText key="glidict::GUI.Enrich"/> panel, look at the metadata that has been extracted for <Path>word05.doc</Path> and <Path>word06.doc</Path>. Now open the documents in Word and look at what properties have been set (<Menu>File &rarr; Properties</Menu>). They have Title, Author, Subject, and Keywords properties. <AutoText text="WordPlug"/> can be configured to look for these properties and extract them.</Text>
    1300 </NumberedItem>
    1301 <NumberedItem>
    1302 <Text id="ew-28">In the <AutoText key="glidict::GUI.Design"/> panel, under <AutoText key="glidict::CDM.GUI.Plugins"/>, configure <AutoText text="WordPlug"/> once again. Switch on the configuration option <AutoText text="metadata_fields"/>. Set the value to </Text>
     1302<Text id="ew-27">In the <AutoText key="glidict::GUI.Enrich"/> panel, look at the metadata that has been extracted for <Path>word05.doc</Path> and <Path>word06.doc</Path>. Now open the documents in Word and look at what properties have been set (<Menu>File &rarr; Properties</Menu>). They have Title, Author, Subject, and Keywords properties. <AutoText text="WordPlugin"/> can be configured to look for these properties and extract them.</Text>
     1303</NumberedItem>
     1304<NumberedItem>
     1305<Text id="ew-28">In the <AutoText key="glidict::GUI.Design"/> panel, under <AutoText key="glidict::CDM.GUI.Plugins"/>, configure <AutoText text="WordPlugin"/> once again. Switch on the configuration option <AutoText text="metadata_fields"/>. Set the value to </Text>
    13031306<Format>
    13041307Title,Author&lt;Creator&gt;,Subject,Keywords&lt;Subject&gt;
    13051308</Format>
    1306 <Text id="ew-29">This will make <AutoText text="WordPlug"/> try to extract Title, Author, Subject and Keywords metadata. Title and Subject will be saved with the same name, while Author will be saved as Creator metadata, and Keywords as Subject metadata.</Text>
     1309<Text id="ew-29">This will make <AutoText text="WordPlugin"/> try to extract Title, Author, Subject and Keywords metadata. Title and Subject will be saved with the same name, while Author will be saved as Creator metadata, and Keywords as Subject metadata.</Text>
    13071310</NumberedItem>
    13081311<NumberedItem>
    … …  
    13181321<Text id="0403">Exporting a collection to CD-ROM/DVD</Text>
    13191322</Title>
    1320 <Version initial="2.60" current="2.80"/>
     1323<Version initial="2.60" current="2.82"/>
    13211324<Content>
    13221325<Comment>
    … …  
    13431346</Title>
    13441347<SampleFiles folder="tudor"/>
    1345 <Version initial="2.60" current="2.80"/>
     1348<Version initial="2.60" current="2.82"/>
    13461349<Content>
    13471350<Comment>
    … …  
    13731376 </NumberedItem>
    13741377<NumberedItem>
    1375 <Text id="0393b">By default, <AutoText text="HTMLPlug"/> only looks for Title metadata. Configure the plugin so that it looks for the other metadata too. Switch to the <AutoText key="glidict::GUI.Design"/> panel and select the <AutoText key="glidict::CDM.GUI.Plugins"/> section. Select the <AutoText text="plugin HTMLPlug"/> line and click <AutoText key="glidict::CDM.PlugInManager.Configure" type="button"/>. A popup window appears. Switch on the <AutoText text="metadata_fields"/> option, and set the value to</Text>
     1378<Text id="0393b">By default, <AutoText text="HTMLPlugin"/> only looks for Title metadata. Configure the plugin so that it looks for the other metadata too. Switch to the <AutoText key="glidict::GUI.Design"/> panel and select the <AutoText key="glidict::CDM.GUI.Plugins"/> section. Select the <AutoText text="plugin HTMLPlugin"/> line and click <AutoText key="glidict::CDM.PlugInManager.Configure" type="button"/>. A popup window appears. Switch on the <AutoText text="metadata_fields"/> option, and set the value to</Text>
    13761379<Format>
    13771380Title,Author,Page_topic,Content
    … …  
    13811384<NumberedItem>
    13821385<Text id="0393c">Switch to the <AutoText key="glidict::GUI.Create"/> panel and <b>rebuild</b> the collection. Go back to the <AutoText key="glidict::GUI.Enrich"/> panel and look at the extracted metadata for some of the HTML files in <Path>englishhistory.net &rarr; tudor &rarr; monarchs</Path>. The new metadata should now be visible.</Text>
    1383 </NumberedItem>
    1384 <Heading>
    1385 <Text id="0393d">Blocking the stray images</Text>
    1386 </Heading>
    1387 <Comment>
    1388 <Text id="0394">You've probably noticed that the collection contains a few stray image files, as well as the HTML documents. This is a mistake. The issue is that many of the HTML documents include images, and although Greenstone attempts to determine which images belong to HTML pages and only considers other images for inclusion in the collection, in this case it hasn't been completely successful. (This is because the web site from which these files were downloaded occasionally departs from the usual convention of hierarchical structuring.)</Text>
    1389 </Comment>
    1390 <NumberedItem>
    1391 <Text id="0395">Switch back to the <AutoText key="glidict::CDM.GUI.Plugins"/> section of the <AutoText key="glidict::GUI.Design"/> panel. Beside <AutoText text="plugin HTMLPlug"/> you will see <AutoText text="-smart_block"/>. This is the option that attempts to identify images in the HTML pages and block them from inclusion&mdash;in this case, it's not smart enough! Configure <AutoText text="plugin HTMLPlug"/> again, scroll down the page to locate the <AutoText text="smart_block"/> option, and switch it off.</Text>
    1392 </NumberedItem>
    1393 <NumberedItem>
    1394 <Text id="0396"><b>Rebuild</b> and <b>preview</b> the collection. The collection is exactly as before except that these stray images are suppressed. What is happening is that plug-ins operate as a pipeline: files are passed to each one in turn until one is found that can process it. By default (i.e. without <AutoText text="smart_block"/>) the HTML plug-in blocks <i>all</i> images, which is appropriate for this collection.</Text>
    13951386</NumberedItem>
    13961387<Heading>
    … …  
    14161407</Title>
    14171408<Prerequisite id="large_html_collection"/>
    1418 <Version initial="2.60" current="2.80"/>
     1409<Version initial="2.60" current="2.82"/>
    14191410<Content>
    14201411<Comment>
    … …  
    14691460<Text id="0445">Next we partition the full-text index into four separate pieces. To do this we first define four subcollections obtained by "filtering" the documents according to a criterion based on their <AutoText key="metadata::dc.Subject"/> metadata. Then an index is assigned to each subcollection. This will enable users to restrict a search to a subset of the documents.</Text>
    14701461</Comment>
    1471 
    1472 <NumberedItem>
    1473 <Text id="0447">Switch to the <AutoText key="glidict::GUI.Design"/> panel, and click <AutoText key="glidict::CDM.GUI.Subcollections"/>. This feature is disabled because you are operating in <AutoText key="glidict::Preferences.Mode.Librarian"/> mode (this is indicated in the title bar at the top of the window).</Text>
    1474 </NumberedItem>
    1475 <NumberedItem>
    1476 <Text id="0448">Switch to <AutoText key="glidict::Preferences.Mode.Systems"/> mode by going to <AutoText key="glidict::Menu.File_Options"/> (on the <AutoText key="glidict::Menu.File"/> menu) and clicking <AutoText key="glidict::Preferences.Mode" type="button"/>. Read about the other modes too.</Text>
     1462<NumberedItem>
     1463<Text id="0447">Switch to the <AutoText key="glidict::GUI.Design"/> panel, and click <AutoText key="glidict::CDM.GUI.Subcollections"/>.</Text>
     1464</NumberedItem>
     1465<NumberedItem>
     1466<Text id="0448">For versions before 2.82, this feature is disabled because you are operating in <AutoText key="glidict::Preferences.Mode.Librarian"/> mode (this is indicated in the title bar at the top of the window). Switch to <AutoText text="Library Systems Specialist"/> mode by going to <AutoText key="glidict::Menu.File_Options"/> (on the <AutoText key="glidict::Menu.File"/> menu) and clicking <AutoText key="glidict::Preferences.Mode" type="button"/>. Read about the other modes too.</Text>
    14771467</NumberedItem>
    14781468<NumberedItem>
    … …  
    14931483</NumberedItem>
    14941484<NumberedItem>
    1495 <Text id="0453">To allow users to search the collection as a whole as well as each subcollection individually, return to the <AutoText key="glidict::CDM.GUI.Subcollections"/> section of the <AutoText key="glidict::GUI.Design"/> panel and select the <AutoText key="glidict::CDM.SubcollectionManager.Subindex_Controls"/> tab. Select all four subcollections by checking their boxes and click <AutoText key="glidict::CDM.SubcollectionIndexManager.Add_Subindex" type="button"/>.</Text>
     1485<Text id="0453">To allow users to search the collection as a whole as well as each subcollection individually, return to the <AutoText key="glidict::CDM.GUI.Subcollections"/> section of the <AutoText key="glidict::GUI.Design"/> panel and select the <AutoText key="glidict::CDM.SubcollectionManager.Subindex_Controls"/> tab. Select all four subcollections by either checking their boxes or press the <AutoText key="glidict::CDM.IndexManager.Select_All"/> button, and click <AutoText key="glidict::CDM.SubcollectionIndexManager.Add_Subindex" type="button"/>.</Text>
    14961486</NumberedItem>
    14971487<NumberedItem>
    … …  
    15051495</NumberedItem>
    15061496<NumberedItem>
    1507 <Text id="0456">In the Librarian Interface, return to <AutoText key="glidict::Preferences.Mode.Librarian"/> mode, using <AutoText key="glidict::Menu.File_Options"/> (on the <AutoText key="glidict::Menu.File"/> menu).</Text>
     1497<Text id="0456">For versions before 2.82, now return to <AutoText key="glidict::Preferences.Mode.Librarian"/> mode in the Librarian Interface, using <AutoText key="glidict::Menu.File_Options"/> (on the <AutoText key="glidict::Menu.File"/> menu).</Text>
    15081498</NumberedItem>
    15091499<Heading>
    … …  
    15291519</Title>
    15301520<Prerequisite id="large_html_collection"/>
    1531 <Version initial="2.60" current="2.80"/>
     1521<Version initial="2.60" current="2.82"/>
    15321522<Content>
    15331523<NumberedItem>
    … …  
    16231613<Text id="st-1">Section tagging for HTML documents</Text>
    16241614</Title>
    1625 <Version initial="2.70w" current="2.80"/>
     1615<Version initial="2.70w" current="2.82"/>
    16261616<Content>
    16271617<NumberedItem>
    … …  
    16681658</NumberedItem>
    16691659<NumberedItem>
    1670 <Text id="st-7">Open the Greenstone demo collection in the Librarian Interface. In the <AutoText key="glidict::CDM.GUI.Plugins"/> section of the <AutoText key="glidict::GUI.Design"/> panel, note that <AutoText text="HTMLPlug"/> has the <AutoText text="description_tags"/> option set. This option is needed when <Format>&lt;Section&gt;</Format> tags are used in the source documents.</Text>
     1660<Text id="st-7">Open the Greenstone demo collection in the Librarian Interface. In the <AutoText key="glidict::CDM.GUI.Plugins"/> section of the <AutoText key="glidict::GUI.Design"/> panel, note that <AutoText text="HTMLPlugin"/> has the <AutoText text="description_tags"/> option set. This option is needed when <Format>&lt;Section&gt;</Format> tags are used in the source documents.</Text>
    16711661</NumberedItem>
    16721662<NumberedItem>
    … …  
    16791669<Text id="0411">Downloading files from the web</Text>
    16801670</Title>
    1681 <Version initial="2.60" current="2.80"/>
     1671<Version initial="2.60" current="2.82"/>
    16821672<Content>
    16831673<Comment>
    … …  
    16931683</NumberedItem>
    16941684<NumberedItem>
    1695 <Text id="0415a">Go to the <AutoText key="glidict::GUI.Download"/> panel by clicking its tab. There are four download types listed on the left hand side. For this exercise, we only use the <AutoText key="glidict::DOWNLOAD.MODE.WebDownload"/> type. Make sure this is selected in the list.</Text>
     1685<Text id="0415a">Go to the <AutoText key="glidict::GUI.Download"/> panel by clicking its tab. There are five download types listed on the left hand side. For this exercise, we only use the <AutoText key="glidict::DOWNLOAD.MODE.WebDownload"/> type. Make sure this is selected in the list.</Text>
    16961686<Text id="0415b">Enter this URL</Text>
    16971687<Link>http://englishhistory.net/tudor/citizens/</Link>
    1698 <Text id="0417">into the <AutoText text="url"/> box. There are several other options that govern how the download process proceeds. To see a description of an option, hover the mouse over it and a tooltip will appear. To copy just the <i>citizens</i> section of the website, switch on the <AutoText text="below"/> option by checking its box and set the <AutoText text="depth"/> option to 1. If you don't do this (or if you miss out the terminating "/" in the URL), the downloading process will follow links to other areas of the <i>englishhistory.net</i> website and grab those as well.</Text>
     1688<Text id="0417">into the <AutoText text="Source URL"/> box. There are several other options that govern how the download process proceeds. To see a description of an option, hover the mouse over it and a tooltip will appear. To copy just the <i>citizens</i> section of the website, switch on the <AutoText text="Only filese below URL"/> option by checking its box and set the <AutoText text="Download Depth"/> option to 1. If you don't do this (or if you miss out the terminating "/" in the URL), the downloading process will follow links to other areas of the <i>englishhistory.net</i> website and grab those as well.</Text>
    16991689</NumberedItem>
    17001690<NumberedItem>
    … …  
    17211711</Title>
    17221712<Prerequisite id="downloading_from_internet"/>
    1723 <Version initial="2.60" current="2.80"/>
     1713<Version initial="2.60" current="2.82"/>
    17241714<Content>
    17251715<NumberedItem>
    … …  
    17271717</NumberedItem>
    17281718<NumberedItem>
    1729 <Text id="0425">In the <AutoText key="glidict::GUI.Design"/> panel, select the <AutoText key="glidict::CDM.GUI.Plugins"/> section, then select the <AutoText text="plugin HTMLPlug"/> line and click <AutoText key="glidict::CDM.PlugInManager.Configure" type="button"/>. A popup window appears. Locate the <AutoText text="file_is_url"/> option (about halfway down the first block of items) and switch it on. While you are there, switch off the <AutoText text="smart_block"/> option so that stray images are not processed. Click <AutoText key="glidict::General.OK" type="button"/>.</Text>
    1730 <Text id="0426">Setting this option to the <AutoText text="HTMLPlug"/> means that Greenstone sets an additional piece of metadata for each document called <AutoText text="URL"/>, which gives its original URL.</Text>
     1719<Text id="0425">In the <AutoText key="glidict::GUI.Design"/> panel, select the <AutoText key="glidict::CDM.GUI.Plugins"/> section, then select the <AutoText text="plugin HTMLPlugin"/> line and click <AutoText key="glidict::CDM.PlugInManager.Configure" type="button"/>. A popup window appears. Locate the <AutoText text="file_is_url"/> option (about halfway down the first block of items) and switch it on. Click <AutoText key="glidict::General.OK" type="button"/>.</Text>
     1720<Text id="0426">Setting this option to the <AutoText text="HTMLPlugin"/> means that Greenstone sets an additional piece of metadata for each document called <AutoText text="URL"/>, which gives its original URL.</Text>
    17311721<Text id="0427">It is important that the files gathered in the collection start with the web domain name (<i>englishhistory.net</i> in this case). The conversion process will not work if you dragged over a subfolder, for example the <Path>tudor</Path> folder, because this will set <AutoText text="URL"/> metadata to something like</Text>
    17321722<Indent>
    … …  
    17371727http://englishhistory.net/tudor/citizens/...
    17381728</Indent>
    1739 <Text id="0429">If you have copied over a subfolder previously, delete it and make a fresh copy. Drag the folder in the right-hand side of the <AutoText key="glidict::GUI.Gather"/> panel on to the trash can in the lower right corner. Then obtain a fresh copy of the files by dragging across the <Path>englishhistory.net</Path> folder from the <AutoText key="glidict::Tree.DownloadedFiles"/> folder on the left-hand side.</Text>
     1729<Text id="0429">If you have copied over a subfolder previously, delete it and make a fresh copy. Drag the folder in the right-hand side of the <AutoText key="glidict::GUI.Gather"/> panel on to the trash can in the lower right corner. Then obtain a fresh copy of the files by dragging across the <Path>englishhistory.net</Path> folder from the <Path>sample_files &rarr; tudor</Path> folder (or the <AutoText key="glidict::Tree.DownloadedFiles"/> folder if you have done exercise <TutorialRef id="downloading_from_internet"/>) on the left-hand side.</Text>
    17401730</NumberedItem>
    17411731<NumberedItem>
    … …  
    17551745</Title>
    17561746<SampleFiles folder="marc"/>
    1757 <Version initial="2.60" current="2.80"/>
     1747<Version initial="2.60" current="2.82"/>
    17581748<Content>
    17591749<Comment>
    … …  
    17641754</NumberedItem>
    17651755<NumberedItem>
    1766 <Text id="0522">In the <AutoText key="glidict::GUI.Gather"/> panel, open the <Path>sample_files &rarr; marc</Path> folder, drag <Path>CMSwp-all.marc</Path> into the right-hand pane and drop it there. A popup window asks whether you want to add <AutoText text="MARCPlug" /> to the collection to process this file. Click <AutoText key="glidict::CDM.PlugInManager.QuickAdd" type="button"/>, because this plugin will be needed to process the MARC records.</Text>
    1767 </NumberedItem>
    1768 <!-- don't need to remove the plugins -->
    1769 <!--
    1770 <NumberedItem>
    1771 <Text id="0523">In the <AutoText key="glidict::CDM.GUI.Plugins"/> section of the <AutoText key="glidict::GUI.Design"/> panel, remove the plugins <AutoText text="TextPlug" /> to <AutoText text="NULPlug" /> by selecting each one in the <AutoText key="glidict::CDM.PlugInManager.Assigned"/> list and clicking <AutoText key="glidict::CDM.PlugInManager.Remove" type="button"/> (<AutoText text="ZIPPlug" />, <AutoText text="GAPlug" />, <AutoText text="MetadataXMLPlug"/> and <AutoText text="MARCPlug" /> remain). It is not strictly necessary to remove these redundant plugins, but it is good practice to include only plugins that are needed, to avoid unwanted (and unexpected) side effects.</Text>
    1772 </NumberedItem>
    1773 -->
     1756<Text id="0522">In the <AutoText key="glidict::GUI.Gather"/> panel, open the <Path>sample_files &rarr; marc</Path> folder, drag <Path>CMSwp-all.marc</Path> into the right-hand pane and drop it there. A popup window asks whether you want to add <AutoText text="MARCPlugin" /> to the collection to process this file. Click <AutoText key="glidict::CDM.PlugInManager.QuickAdd" type="button"/>, because this plugin will be needed to process the MARC records.</Text>
     1757</NumberedItem>
    17741758<NumberedItem>
    17751759<Text id="0524">Now select <AutoText key="glidict::CDM.GUI.Classifiers"/> within the <AutoText key="glidict::GUI.Design"/> panel and <b>remove</b> the default classifier for <b>Source</b> metadata.</Text>
    … …  
    17821766</NumberedItem>
    17831767<NumberedItem>
    1784 <Text id="0526">Back in the Librarian Interface, go to the <AutoText key="glidict::CDM.GUI.Classifiers"/> section of the <AutoText key="glidict::GUI.Design"/> panel. Select <AutoText text="AZCompactList" /> from the <AutoText key="glidict::CDM.ClassifierManager.Classifier"/> drop down menu, and click <AutoText key="glidict::CDM.ClassifierManager.Add" type="button"/>. In the popup window, select <AutoText key="metadata::ex.Subject"/> as the metadata item. Click <AutoText key="glidict::General.OK" type="button"/>.</Text>
    1785 <Comment>
    1786 <Text id="0527"><AutoText text="AZCompactList" /> is like <AutoText text="AZList"/>, except that terms that appear multiple times in the hierarchy are automatically grouped together and a new node, shown as a bookshelf icon, is formed.</Text>
     1768<Text id="0526">Back in the Librarian Interface, go to the <AutoText key="glidict::CDM.GUI.Classifiers"/> section of the <AutoText key="glidict::GUI.Design"/> panel. Select <AutoText text="AZCompactList" /> from the <AutoText key="glidict::CDM.ClassifierManager.Classifier"/> drop down menu, and click <AutoText key="glidict::CDM.ClassifierManager.Add" type="button"/>. In the popup window, select <AutoText key="metadata::dc.Subject"/> as the metadata item. Click <AutoText key="glidict::General.OK" type="button"/>.</Text>
     1769<Comment>
     1770<Text id="0527"><AutoText text="AZCompactList" /> is like <AutoText text="List"/>, except that terms that appear multiple times in the hierarchy are automatically grouped together and a new node, shown as a bookshelf icon, is formed.</Text>
    17871771</Comment>
    17881772</NumberedItem>
    … …  
    17941778</Heading>
    17951779<NumberedItem>
    1796 <Text id="0531a">Now let's look at fielded searching. In the browser, go to the <AutoText key="coredm::_Global:linktextPREFERENCES_" type="italics"/> page. You will notice that there is a <AutoText key="coredm::_preferences:textsearchtype_" /> option which enables you to switch between "normal" and "fielded" search. Change to fielded search now and click on the <AutoText key="coredm::_Global:labelSearch_"/> button. The search form has changed to a fielded form.</Text>
     1780<Text id="0531a">Now let's look at fielded searching. In the browser, go to the <AutoText key="coredm::_Global:linktextPREFERENCES_" type="italics"/> page. You will notice that there is a <AutoText key="coredm::_preferences:textsearchtype_" /> option which enables you to switch between "normal" and "fielded" search. Change to fielded search now, press the <AutoText key="coredm::_preferences:textsetprefs_"/>, and click on the <AutoText key="coredm::_Global:labelSearch_"/> button to go back to the Search page. The search form has changed to a fielded form.</Text>
    17971781</NumberedItem>
    17981782<NumberedItem>
    … …  
    18031787</NumberedItem>
    18041788<NumberedItem>
    1805 <Text id="0533"><b>Preview</b> the collection again. Notice that the collection's home page no longer includes a query box. (This is because the search form is too big to fit here nicely.) To search, you have to click <AutoText key="coredm::_Global:labelSearch_"/> in the navigation bar. Note that the <AutoText key="coredm::_Global:linktextPREFERENCES_" type="italics"/> page has changed so that the "normal" query style is no longer the default value.</Text>
    1806 </NumberedItem>
    1807 <NumberedItem>
    1808 <Text id="0533a">Look at the search form in the collection. There are two fields that can be searched: <i>text</i> and <i>Title</i>. Add some more fields to search on by going back to the Librarian Interface.</Text>
    1809 </NumberedItem>
    1810 <NumberedItem>
    1811 <Text id="0533c">In the <AutoText key="glidict::GUI.Design"/> panel, go to the <AutoText key="glidict::CDM.GUI.Indexes"/> section. Add a new index based on <AutoText key="metadata::ex.Subject"/> by clicking <AutoText key="glidict::CDM.IndexManager.New_Index" type="button"/>, selecting <AutoText key="metadata::ex.Subject"/> in the list of metadata, and clicking <AutoText key="glidict::CDM.IndexManager.Add_Index" type="button"/>.</Text>
     1789<Text id="0533"><b>Preview</b> the collection again. Notice that the collection's home page no longer includes a query box. (This is because the search form is too big to fit here nicely.) To search, you have to click <AutoText key="coredm::_Global:labelSearch_"/> in the navigation bar. Note that the <AutoText key="coredm::_Global:linktextPREFERENCES_" type="italics"/> page has changed so that the "normal" query style is no longer offered.</Text>
     1790</NumberedItem>
     1791<NumberedItem>
     1792<Text id="0533a">Look at the search form in the collection. There are two fields that can be searched: <i>text</i> and <i>titles</i>. Add some more fields to search on by going back to the Librarian Interface.</Text>
     1793</NumberedItem>
     1794<NumberedItem>
     1795<Text id="0533c">In the <AutoText key="glidict::GUI.Design"/> panel, go to the <AutoText key="glidict::CDM.GUI.Indexes"/> section. Add a new index based on <AutoText key="metadata::ex.Subject"/> by clicking <AutoText key="glidict::CDM.IndexManager.New_Index" type="button"/>, selecting <AutoText key="metadata::dc.Subject"/> in the list of metadata, and clicking <AutoText key="glidict::CDM.IndexManager.Add_Index" type="button"/>.</Text>
    18121796</NumberedItem>
    18131797<NumberedItem>
    … …  
    18361820</NumberedItem>
    18371821<NumberedItem>
    1838 <Text id="0533-10">Because the MARC file is no longer present, and the collection contains empty (.nul) files, we need to change the list of plugins. In the <AutoText key="glidict::CDM.GUI.Plugins"/> section of the <AutoText key="glidict::GUI.Design"/> panel, remove <AutoText text="MARCPlug"/>.</Text>
     1822<Text id="0533-10">Because the MARC file is no longer present, and the collection contains empty (.nul) files, we need to change the list of plugins. In the <AutoText key="glidict::CDM.GUI.Plugins"/> section of the <AutoText key="glidict::GUI.Design"/> panel, remove <AutoText text="MARCPlugin"/>.</Text>
    18391823</NumberedItem>
    18401824<NumberedItem>
    … …  
    18481832[/highlight]{If}{[ex.Source],&lt;br&gt;&lt;i&gt;([ex.Source])&lt;/i&gt;}
    18491833</Format>
    1850 <Text id="0533-11c">Since there is no <AutoText key="metadata::dc.Title"/> metadata and <AutoText key="metadata::exp.Title"/> comes before <AutoText key="metadata::ex.Title"/>, the expoded titles will be displayed.</Text>
     1834<Text id="0533-11c">Since there is no <AutoText key="metadata::dc.Title"/> metadata and <AutoText key="metadata::exp.Title"/> comes before <AutoText key="metadata::ex.Title"/>, the exploded titles will be displayed.</Text>
    18511835</NumberedItem>
    18521836<Heading>
    … …  
    18541838</Heading>
    18551839<Text id="0533-12">The collection previously used extracted (ex.) metadata, but now it uses exploded (exp.) metadata. The <AutoText key="coredm::_Global:labelSubject_" type="italics"/> classifier and search indexes were built on ex metadata, which is why they no longer work properly.</Text>
    1856 <Text id="0533-12a">There is also no longer any text in the documents. Previously, MARCPlug stored the raw record as the "text" of each record. Now that the metadata is in the Librarian Interface, there is no longer the concept of raw record, and so there is no text.</Text>
     1840<Text id="0533-12a">There is also no longer any text in the documents. Previously, <AutoText text="MARCPlugin"/> stored the raw record as the "text" of each record. Now that the metadata is in the Librarian Interface, there is no longer the concept of raw record, and so there is no text.</Text>
    18571841<Text id="0533-12b">We need to modify the collection design to take note of these changes.</Text>
    18581842<NumberedItem>
    1859 <Text id="0533-13">In the <AutoText key="glidict::CDM.GUI.Indexes"/> section, change the Title index to use <AutoText key="metadata::exp.Title"/>: select the Title index in the <AutoText key="glidict::CDM.IndexManager.Indexes"/> list and click <AutoText key="glidict::CDM.IndexManager.Edit_Index" type="button"/>. Deselect <AutoText key="metadata::ex.Title"/> in the list of metadata, and select <AutoText key="metadata::exp.Title"/>. Click <AutoText key="glidict::CDM.IndexManager.Replace_Index" type="button"/>.</Text>
    1860 </NumberedItem>
    1861 <NumberedItem>
    1862 <Text id="0533-13a">Remove the <AutoText key="metadata::ex.Subject"/> index by selecting it in the <AutoText key="glidict::CDM.IndexManager.Indexes"/> list and clicking <AutoText key="glidict::CDM.IndexManager.Remove_Index" type="button"/>. Add an index on <AutoText key="metadata::exp.Subject"/>: click <AutoText key="glidict::CDM.IndexManager.New_Index" type="button"/>,  select <AutoText key="metadata::exp.Subject"/> in the metadata list, and click <AutoText key="glidict::CDM.IndexManager.Add_Index" type="button"/>.</Text>
     1843<Text id="0533-13">In the <AutoText key="glidict::CDM.GUI.Indexes"/> section, change the Title index to use <AutoText key="metadata::exp.Title"/>: select the Title index in the <AutoText key="glidict::CDM.IndexManager.Indexes"/> list and click <AutoText key="glidict::CDM.IndexManager.Edit_Index" type="button"/>. Deselect <AutoText key="metadata::dc.Title"/> and <AutoText key="metadata::ex.Title"/> in the list of metadata, and select <AutoText key="metadata::exp.Title"/>. Click <AutoText key="glidict::CDM.IndexManager.Replace_Index" type="button"/>.</Text>
     1844</NumberedItem>
     1845<NumberedItem>
     1846<Text id="0533-13a">Remove the <AutoText key="metadata::dc.Subject"/> index by selecting it in the <AutoText key="glidict::CDM.IndexManager.Indexes"/> list and clicking <AutoText key="glidict::CDM.IndexManager.Remove_Index" type="button"/>. Add an index on <AutoText key="metadata::exp.Subject"/>: click <AutoText key="glidict::CDM.IndexManager.New_Index" type="button"/>,  select <AutoText key="metadata::exp.Subject"/> in the metadata list, and click <AutoText key="glidict::CDM.IndexManager.Add_Index" type="button"/>.</Text>
    18631847</NumberedItem>
    18641848<NumberedItem>
    … …  
    18661850</NumberedItem>
    18671851<NumberedItem>
    1868 <Text id="0533-14a">To enable combined searching across all indexes at once, click <AutoText key="glidict::CDM.IndexManager.New_Index" type="button"/>, tick the <AutoText key="glidict::CDM.IndexManager.Allfields_Index"/> checkbox, and click <AutoText key="glidict::CDM.IndexManager.Add_Index" type="button"/>. Move this to the top of the list using the <AutoText key="glidict::CDM.Move.Move_Up" type="button"/> button, so that it appears first in the drop down list. Click <AutoText key="glidict::CDM.IndexManager.Set_Default" type="button"/> so that it becomes the default field for searching.</Text>
    1869 </NumberedItem>
    1870 <NumberedItem>
    1871 <Text id="0533-15">To explicitly use the <AutoText key="metadata::exp.Title"/> metadata, in the <AutoText key="glidict::CDM.GUI.Classifiers"/> section, change the <AutoText key="metadata::ex.Title"/> <AutoText text="AZList"/> to use <AutoText key="metadata::exp.Title"/> metadata. Double click the <AutoText key="metadata::ex.Title"/> <AutoText text="AZList"/> in the <AutoText key="glidict::CDM.ClassifierManager.Assigned"/> list, and change the <AutoText text="metadata"/> option to use <AutoText key="metadata::exp.Title"/>. Click <AutoText key="glidict::General.OK" type="button"/>. Do the same thing for the Subject <AutoText text="AZCompactList"/>, changing <AutoText key="metadata::ex.Subject"/> to <AutoText key="metadata::exp.Subject"/>.</Text>
     1852<Text id="0533-14a">To enable combined searching across all indexes at once, click <AutoText key="glidict::CDM.IndexManager.New_Index" type="button"/>, tick the <AutoText key="glidict::CDM.IndexManager.Allfields_Index"/> checkbox, and click <AutoText key="glidict::CDM.IndexManager.Add_Index" type="button"/>. Move this to the top of the list using the <AutoText key="glidict::CDM.Move.Move_Up" type="button"/> button, so that it appears first in the drop down list. Click <AutoText key="glidict::CDM.IndexManager.Set_Default" type="button"/> on the right so that it becomes the default field for searching.</Text>
     1853</NumberedItem>
     1854<NumberedItem>
     1855<Text id="0533-15">To explicitly use the <AutoText key="metadata::exp.Title"/> metadata, in the <AutoText key="glidict::CDM.GUI.Classifiers"/> section, change the <AutoText text="dc.Title;Title"/> <AutoText text="List"/> to use <AutoText key="metadata::exp.Title"/> metadata. Double click the <AutoText key="metadata::ex.Title"/> <AutoText text="AZList"/> in the <AutoText key="glidict::CDM.ClassifierManager.Assigned"/> list, and change the <AutoText text="metadata"/> option to use <AutoText key="metadata::exp.Title"/>. Click <AutoText key="glidict::General.OK" type="button"/>. Do the same thing for the Subject <AutoText text="AZCompactList"/>, changing <AutoText key="metadata::dc.Subject"/> to <AutoText key="metadata::exp.Subject"/>.</Text>
    18721856</NumberedItem>
    18731857<NumberedItem>
    … …  
    19181902</Title>
    19191903<SampleFiles folder="isis"/>
    1920 <Version initial="2.70w" current="2.80"/>
     1904<Version initial="2.70w" current="2.82"/>
    19211905<Content>
    19221906<Comment>
    … …  
    19271911</NumberedItem>
    19281912<NumberedItem>
    1929 <Text id="is-4">Drag the files from <Path>sample_files &rarr; isis</Path> (excluding the <Path>format_tweaks</Path> folder) into the collection. </Text>
     1913<Text id="is-4">Drag the files from <Path>sample_files &rarr; isis</Path> (excluding the <Path>format_tweaks</Path> folder and the README.txt file) into the collection. </Text>
    19301914</NumberedItem>
    19311915<NumberedItem>
    … …  
    19331917</NumberedItem>
    19341918<NumberedItem>
    1935 <Text id="is-8">In the <AutoText key="glidict::CDM.GUI.Indexes"/> section of the <AutoText key="glidict::GUI.Design"/> panel, remove the useless Source and Title indexes, and add new indexes for Photographer^all, Country^all and Notes^all metadata.</Text>
     1919<Text id="is-8">In the <AutoText key="glidict::CDM.GUI.Indexes"/> section of the <AutoText key="glidict::GUI.Design"/> panel, remove the useless Source and Title indexes, and add new indexes for <AutoText text="ex.Photographer^all"/>, <AutoText text="ex.Country^all"/> and <AutoText text="ex.Notes^all"/> metadata.</Text>
    19361920<Text id="is-9">CDS/ISIS metadata has subfields, and these are represented using ^.</Text>
    19371921</NumberedItem>
    19381922<NumberedItem>
    1939 <Text id="is-10">In the <AutoText key="glidict::CDM.GUI.Classifiers"/> section, remove the existing (useless) classifiers for <AutoText text="Title"/> and <AutoText text="Source"/>, and add a new <AutoText text="AZList"/> for <AutoText text="Photographer"/>.</Text>
     1923<Text id="is-10">In the <AutoText key="glidict::CDM.GUI.Classifiers"/> section, remove the existing (useless) classifiers for <AutoText text="dc.Title;Title"/> and <AutoText text="ex.Source"/>, and add a new <AutoText text="List"/> for <AutoText text="ex.Photographer"/>.</Text>
    19401924</NumberedItem>
    19411925<NumberedItem>
    … …  
    19801964</Title>
    19811965<SampleFiles folder="custom"/>
    1982 <Version initial="2.70" current="2.80"/>
     1966<Version initial="2.70" current="2.82"/>
    19831967<Content>
    1984 <Text id="mf-2">The appearance of all pages produced by Greenstone is governed by macro files, which reside in the folder <Path>Greenstone &rarr; macros</Path>, images, and CSS stylesheets, both of which reside in <Path>Greenstone &rarr; images</Path>. </Text>
     1968<Text id="mf-2">The appearance of all pages produced by Greenstone is governed by macro files, which reside in the folder <Path>Greenstone &rarr; macros</Path>, and images and CSS stylesheets reside in <Path>Greenstone &rarr; web &rarr; style</Path> (for versions before 2.82 it's <Path>Greenstone &rarr; images</Path>). </Text>
    19851969<Text id="mf-3">A macro takes the form <Format>_macroname_ {macro value}</Format>. Macro names start and end with underscores (_), and the macro value is enclosed in curly brackets ({}). Macro values can be text or HTML, and can include other macros.</Text>
    19861970<Text id="mf-4">Macros are grouped into packages, and different packages control the appearance of different pages. For example, the <AutoText text="home"/>, <AutoText text="help"/>, <AutoText text="preferences"/>, <AutoText text="query"/>, <AutoText text="document"/> packages control the home, help, preferences, query, and document pages, respectively. Some macro files contain macros for just one package, for example, <Path>home.dm</Path>, <Path>query.dm</Path>, <Path>document.dm</Path>, while others contain macros for many packages. <Path>base.dm</Path> contains macros used globally, <Path>style.dm</Path> controls the common style of each page, <Path>english.dm</Path>, <Path>french.dm</Path> and other language files contain the text fragments for the entire interface, in that language. </Text>
    1987 <Text id="mf-5">The output of the library program is a page of HTML which is viewed in a web browser. CSS (Cascading Style Sheets) are often used alongside HTML pages to control the formatting, such as layout, colour, font etc. The default Greenstone stylesheet is <Path>Greenstone &rarr; images &rarr; style.css</Path>.</Text>
     1971<Text id="mf-5">The output of the library program is a page of HTML which is viewed in a web browser. CSS (Cascading Style Sheets) are often used alongside HTML pages to control the formatting, such as layout, colour, font etc. The default Greenstone stylesheet is <Path>Greenstone &rarr; web &rarr; style &rarr; style.css</Path> (for versions before 2.82 it's <Path>Greenstone &rarr; images &rarr; style.css</Path>).</Text>
    19881972<Text id="mf-6">In this exercise, we customize the macros, images and stylesheets to change the appearance of our library.</Text>
    19891973<Heading>
    … …  
    20662050</Format>
    20672051<Text id="mf-60">Outside of the Librarian Interface, locate the collection folder <Path>Greenstone &rarr; collect &rarr; reports</Path>. Create an <Path>images</Path> folder inside this (if not already present), and copy the file <Path>sample_files &rarr; custom &rarr; style-blue.css</Path> into this folder.</Text>
    2068 <Text id="mf-61">Preview the collection; it should look radically different.</Text>
     2052<Text id="mf-61">Preview the collection; the about page should look radically different.</Text>
    20692053</NumberedItem>
    20702054<Heading>
    … …  
    20722056</Heading>
    20732057<Text id="mf-17">In the previous exercises we changed a single collection. Now we change all the pages in our Greenstone installation by modifying style and macro files outside the Librarian Interface. First, we format the page so that some other parts are blue. Preview any collection after each change to make sure that it has worked properly. On Windows, macro file changes require a restart of the Greenstone local library server. Stylesheet changes may require a forced reload in the web browser.</Text>
    2074 <!--
    2075 <NumberedItem>
    2076 <Text id="mf-18">First, we'll change the colour of the navigation bar and green divider bars. These use an image as a background, specified in the same macro as the page background.</Text>
    2077 <Text id="mf-19">Open <Path>Greenstone &rarr; macros &rarr; style.dm</Path> in a text editor, and find the <Format>_cssheader_</Format> macro that you modified previously. Change the <Format>div.navbar</Format> and <Format>div.divbar</Format> parts to use <Format>divb-blue.gif</Format> instead of <Format>bg_green.png</Format>:</Text>
    2078 <Format>
    2079 /*div.navbar \{ background-image: url("_httpimg_/bg_green.png"); \}*/<br/>
    2080 div.navbar \{ background-image: url("_httpimg_/divb-blue.gif"); \}<br/>
    2081 /*div.divbar \{ background-image: url("_httpimg_/bg_green.png"); \}*/<br/>
    2082 div.divbar \{ background-image: url("_httpimg_/divb-blue.gif"); \}<br/>
    2083 </Format>
    2084 <Text id="mf-19a">Preview the collection, now the navigation bar and the green divider change to a blue background. Note that when you select a classifier, the background of the selected item is still green.</Text>
    2085 </NumberedItem>
    2086 <NumberedItem>
    2087 <Text id="mf-20">The selected item on the navigation bar uses the same background, so change that too:</Text>
    2088 <Format>
    2089 /*a.navlink_sel \{ background-image: url("_httpimg_/bg_green.png"); \}*/<br/>
    2090 a.navlink_sel \{ background-image: url("_httpimg_/divb-blue.gif"); \}
    2091 </Format>
    2092 <Text id="mf-20a">Preview the collection, now the selected classifier is also in a blue background.</Text>
    2093 </NumberedItem>
    2094 <NumberedItem>
    2095 <Text id="mf-21">Next, we get rid of the background green image on the page and collection titles. Comment out the
    2096 <Format>p.bannertitle</Format> and <Format>p.collectiontitle</Format>
    2097 parts.(If a collection title image is used, you won't see the change of the background on the collection titles.)</Text>
    2098 <Format>
    2099 /*p.bannertitle \{background-image: url("_httpimg_/banner_bg.png"); \}*/<br/>
    2100 /*p.collectiontitle \{background-image: url("_httpimg_/banner_bg.png"); \}*/
    2101 </Format>
    2102 <Text id="mf-21a">Preview the collection, the small green background on the collection title image and the page title image is gone.</Text>
    2103 </NumberedItem>
    2104 <Text id="mf-22">The above style definitions were included in the macro file so that image paths could be dynamically generated. </Text>
    2105 -->
    2106 <NumberedItem>
    2107 <Text id="mf-23">The majority of the style definitions reside in an external style file, <Path>Greenstone &rarr; images &rarr; style.css</Path>, and most style changes involve modifying that file. Open <Path>Greenstone &rarr; images &rarr; style.css</Path> in a text editor, e.g. WordPad (and save a .backup copy). Make the following modifications. You might want to preview after each one to see the effect.</Text>
     2058<NumberedItem>
     2059<Text id="mf-23">The majority of the style definitions reside in an external style file, <Path>Greenstone &rarr; web &rarr; style &rarr; style.css</Path> (<Path>Greenstone &rarr; images &rarr; style.css</Path> for versions before 2.82), and most style changes involve modifying that file. Open the <Path>style.css</Path> file in a text editor, e.g. WordPad (and save a .backup copy). Make the following modifications. You might want to preview after each one to see the effect.</Text>
    21082060<Text id="mf-24">Change some of the colours:</Text>
    21092061<BulletList>
    … …  
    21402092</NumberedItem>
    21412093<NumberedItem>
    2142 <Text id="mf-8">Now we will customize the default Greenstone header image and the background image. Two new images for this exercise can be found in <Path>sample_files &rarr; custom</Path>. Copy <Path>newbgimg.gif</Path>, <Path>newheadimg.gif</Path> from the <Path>custom</Path> folder into the <Path>Greenstone &rarr; images</Path> folder.</Text>
     2094<Text id="mf-8">Now we will customize the default Greenstone header image and the background image. Two new images for this exercise can be found in <Path>sample_files &rarr; custom</Path>. Copy <Path>newbgimg.gif</Path>, <Path>newheadimg.gif</Path> from the <Path>custom</Path> folder into the <Path>Greenstone &rarr; web &rarr; images</Path> (for versions before 2.82 it's <Path>Greenstone &rarr; images</Path>) folder.</Text>
    21432095</NumberedItem>
    21442096<NumberedItem>
    … …  
    21812133</NumberedItem>
    21822134<NumberedItem>
    2183 <Text id="mf-47">Preview the newly structured home page in a web browser. (On Windows, restart the Greenstone library server.) Look at the file macros/yourhome.dm in a text editor to see hoe these changes are expressed.</Text>
     2135<Text id="mf-47">Preview the newly structured home page in a web browser. (On Windows, restart the Greenstone library server.) Look at the file macros/yourhome.dm in a text editor to see how these changes are expressed.</Text>
    21842136</NumberedItem>
    21852137<NumberedItem>
    … …  
    22192171</Title>
    22202172<SampleFiles folder="beatles"/>
    2221 <Version initial="2.60" current="2.80"/>
     2173<Version initial="2.60" current="2.81"/>
    22222174<Content>
    22232175<NumberedItem>
    22242176<Text id="0541">Copy the entire folder</Text>
    22252177<Path>sample_files &rarr; beatles &rarr; advbeat_large</Path>
    2226 <Text id="0542">(with all its contents) into your Greenstone <Path>collect</Path> folder. If you have installed Greenstone in the usual place, this is</Text>
     2178<Text id="0542">(with all its contents) into your Greenstone <Path>collect</Path> folder. If you have installed Greenstone in the usual place, for Greenstone version 2.81 and above, this is</Text>
    22272179<Path>
    2228 <Text id="0542a"><Path>My Computer &rarr; Local Disk (C:) &rarr; Program Files &rarr; Greenstone &rarr; collect</Path></Text>
     2180<Text id="0542a"><Path>My Computer &rarr; Local Disk (C:) &rarr; Users &rarr; &lt;Username&gt; &rarr; collect</Path></Text>
    22292181</Path>
     2182<Text id="0542b">where &lt;Username&gt; is the username under with Greenstone is installed. For versions below 2.81, this is</Text>
     2183<Path>
     2184<Text id="0542c"><Path>My Computer &rarr; Local Disk (C:) &rarr; Program Files &rarr; Greenstone &rarr; collect</Path></Text>
     2185</Path>
    22302186<Text id="0543">Put <Path>advbeat_large</Path> in there.</Text>
    22312187</NumberedItem>
    22322188<NumberedItem>
    2233 <Text id="0544">If the Greenstone Digital Library Local Library Server is already running, re-start it by clicking the CD icon on the task bar and then pressing <i>Restart Library</i>. If not, start it up by selecting <i>Greenstone Digital Library</i> from the <i>Start</i> menu.</Text>
     2189<Text id="0544">On Windows, if the Greenstone Digital Library Local Library Server is already running, re-start it by clicking the CD icon on the task bar and then pressing <i>Restart Library</i>. If not, start it up by selecting <i>Greenstone Digital Library</i> from the <i>Start</i> menu. On Linux and Mac, just do a forced reload/refresh of the web browser.</Text>
    22342190</NumberedItem>
    22352191<NumberedItem>
    … …  
    22432199</NumberedItem>
    22442200<NumberedItem>
    2245 <Text id="0548">In the Windows file browser, take a look at the files that makes up the collection, in the</Text>
     2201<Text id="0548">In the file browser, take a look at the files that makes up the collection, in the</Text>
    22462202<Path>sample_files &rarr; beatles &rarr; advbeat_large &rarr; import</Path>
    22472203<Text id="0549">folder. What a mess! There are over 450 files under seven top-level sub-folders. Organization is minimal, reflecting the different times and ways the files were gathered. For example, <i>html_lyrics</i> and <i>discography</i> are excerpts of web sites, and <i>images</i> contains various images in JPEG format. For each type, drill down through the hierarchy and look at a sample document.</Text>
    … …  
    22552211<Prerequisite id="multimedia_collection_explore"/>
    22562212<SampleFiles folder="beatles"/>
    2257 <Version initial="2.60" current="2.80"/>
     2213<Version initial="2.60" current="2.81"/>
    22582214<Content>
    22592215<Comment>
    … …  
    22662222<Text id="0554">Copy the files provided in</Text>
    22672223<Path>sample_files &rarr; beatles &rarr; advbeat_small</Path>
    2268 <Text id="0555">into your new collection. Do this by opening up <Path>advbeat_small</Path>, selecting the eight items within it (from <Path>discography</Path> to <Path>beatles_midi.zip</Path>), and dragging them across. Because some of these files are in MP3 and MARC formats you will be asked whether to include <AutoText text="MP3Plug" /> and <AutoText text="MARCPlug" /> in your collection. Click <AutoText key="glidict::CDM.PlugInManager.QuickAdd" type="button"/>.</Text>
     2224<Text id="0555">into your new collection. Do this by opening up <Path>advbeat_small</Path>, selecting the eight items within it (from <Path>discography</Path> to <Path>beatles_midi.zip</Path>), and dragging them across. Because some of these files are in MP3 and MARC formats you will be asked whether to include <AutoText text="MP3Plugin" /> and <AutoText text="MARCPlugin" /> in your collection. Click <AutoText key="glidict::CDM.PlugInManager.QuickAdd" type="button"/>.</Text>
    22692225</NumberedItem>
    22702226<NumberedItem>
    … …  
    24482404</NumberedItem>
    24492405<Heading>
    2450 <Text id="0623">Using <AutoText text="UnknownPlug"/></Text>
     2406<Text id="0623">Using <AutoText text="UnknownPlugin"/></Text>
    24512407</Heading>
    24522408<Comment>
    … …  
    24542410</Comment>
    24552411<NumberedItem>
    2456 <Text id="0627"><AutoText text="UnknownPlug" /> is a useful generic plugin. It knows nothing about any given format but can be tailored to process particular document types&mdash;like MIDI&mdash;based on their filename extension, and set basic metadata.</Text>
     2412<Text id="0627"><AutoText text="UnknownPlugin" /> is a useful generic plugin. It knows nothing about any given format but can be tailored to process particular document types&mdash;like MIDI&mdash;based on their filename extension, and set basic metadata.</Text>
    24572413<Text id="0627a">In the <AutoText key="glidict::CDM.GUI.Plugins"/> section of the <AutoText key="glidict::GUI.Design"/> panel:</Text>
    24582414<BulletList>
    24592415<Bullet>
    2460 <Text id="0628">add <AutoText text="UnknownPlug" />;</Text>
     2416<Text id="0628">add <AutoText text="UnknownPlugin" />;</Text>
    24612417</Bullet>
    24622418<Bullet>
    … …  
    24672423</Bullet>
    24682424</BulletList>
    2469 <Text id="0631">In this collection, all MIDI files are contained in the file <Path>beatles_midi.zip</Path>. <AutoText text="ZIPPlug" /> (already in the list of default plugins) is used to unpack the files and pass them down the list of plugins until they reach <AutoText text="UnknownPlug"/>.</Text>
     2425<Text id="0631">In this collection, all MIDI files are contained in the file <Path>beatles_midi.zip</Path>. <AutoText text="ZIPPlugin" /> (already in the list of default plugins) is used to unpack the files and pass them down the list of plugins until they reach <AutoText text="UnknownPlugin"/>.</Text>
    24702426</NumberedItem>
    24712427<NumberedItem>
    … …  
    24842440</Comment>
    24852441<Comment>
    2486 <Text id="0621">To do this we must put the Librarian Interface into a different mode. The interface supports four levels of user: <AutoText key="glidict::Preferences.Mode.Assistant"/>, who can add documents and metadata to collections, and create new ones whose structure mirrors that of existing collections; <AutoText key="glidict::Preferences.Mode.Librarian"/>, who can, in addition, design new collections, but cannot use specialist IT features (e.g. regular expressions); <AutoText key="glidict::Preferences.Mode.Systems"/>, who can use all design features, but cannot perform troubleshooting tasks (e.g. interpreting debugging output from Perl programs); and <AutoText key="glidict::Preferences.Mode.Expert"/>, who can perform all functions.</Text>
    2487 </Comment>
    2488 <Comment>
    2489 <Text id="0622">So far you have mostly been operating in <AutoText key="glidict::Preferences.Mode.Librarian"/> mode. We switch to <AutoText key="glidict::Preferences.Mode.Systems"/> mode for the next exercise.</Text>
    2490 </Comment>
    2491 <NumberedItem>
    2492 <Text id="0624">To switch modes, click <Menu><AutoText key="glidict::Menu.File"/> &rarr; <AutoText key="glidict::Menu.File_Options"/> &rarr; <AutoText key="glidict::Preferences.Mode"/></Menu> and change to <AutoText key="glidict::Preferences.Mode.Systems"/>. Note from the description that appears that you need to be able to formulate regular expressions to use this mode fully. That is what we do below.</Text>
     2442<Text id="0621">To do this we must put the Librarian Interface into a different mode. The interface supports four levels of user: <AutoText key="glidict::Preferences.Mode.Assistant"/>, who can add documents and metadata to collections, and create new ones whose structure mirrors that of existing collections; <AutoText key="glidict::Preferences.Mode.Librarian"/>, who can, in addition, design new collections, but cannot use specialist IT features (e.g. regular expressions); <AutoText text="Library Systems Specialist"/>, who can use all design features, but cannot perform troubleshooting tasks (e.g. interpreting debugging output from Perl programs); and <AutoText key="glidict::Preferences.Mode.Expert"/>, who can perform all functions.</Text>
     2443</Comment>
     2444<Comment>
     2445<Text id="0622">So far you have mostly been operating in <AutoText key="glidict::Preferences.Mode.Librarian"/> mode. We switch to <AutoText text="Library Systems Specialist"/> mode for the next exercise.</Text>
     2446</Comment>
     2447<NumberedItem>
     2448<Text id="0624">To switch modes, click <Menu><AutoText key="glidict::Menu.File"/> &rarr; <AutoText key="glidict::Menu.File_Options"/> &rarr; <AutoText key="glidict::Preferences.Mode"/></Menu> and change to <AutoText text="Library Systems Specialist"/>. Note from the description that appears that you need to be able to formulate regular expressions to use this mode fully. That is what we do below.</Text>
    24932449</NumberedItem>
    24942450<NumberedItem>
    … …  
    25062462</NumberedItem>
    25072463<Comment>
    2508 <Text id="0639">The previous exercise was done in <AutoText key="glidict::Preferences.Mode.Systems"/> mode because it requires the use of regular expressions, something librarians are not normally trained in.</Text>
     2464<Text id="0639">The previous exercise was done in <AutoText text="Library Systems Specialist"/> mode because it requires the use of regular expressions, something librarians are not normally trained in.</Text>
    25092465</Comment>
    25102466<Comment>
    … …  
    26222578</Title>
    26232579<SampleFiles folder="niupepa"/>
    2624 <Version initial="2.60" current="2.80"/>
     2580<Version initial="2.60" current="2.82"/>
    26252581<Content>
    26262582<Comment>
    … …  
    26282584</Comment>
    26292585<Comment>
    2630 <Text id="0676">The collection involves a mixture of plugins, classifiers, and format statements. The bulk of the work is done by <AutoText text="PagedImgPlug"/>, a plugin designed precisely for the kind of data we have in this example. For each document, an <AutoText text="item" type="quoted"/> file is prepared that specifies a list of image files that constitute the document, tagged with their page number and (optionally) accompanied by a text file containing the machine-readable version of the image, which is used for full text searching. Three newspapers in our collection (all from the series <AutoText text="Te Whetu o Te Tau" type="quoted"/>) have text representations, and two (from <AutoText text="Te Waka o Te Iwi" type="quoted"/>) have images only. Item files can also specify metadata. In our example the newspaper series is recorded as <AutoText key="metadata::ex.Title"/> and its date of publication as <AutoText key="metadata::ex.Date"/>. Issue <AutoText key="metadata::ex.Volume"/> and <AutoText key="metadata::ex.Number"/> metadata is also recorded, where appropriate. This metadata is extracted as part of the building process.</Text>
     2586<Text id="0676">The collection involves a mixture of plugins, classifiers, and format statements. The bulk of the work is done by <AutoText text="PagedImagePlugin"/>, a plugin designed precisely for the kind of data we have in this example. For each document, an <AutoText text="item" type="quoted"/> file is prepared that specifies a list of image files that constitute the document, tagged with their page number and (optionally) accompanied by a text file containing the machine-readable version of the image, which is used for full text searching. Three newspapers in our collection (all from the series <AutoText text="Te Whetu o Te Tau" type="quoted"/>) have text representations, and two (from <AutoText text="Te Waka o Te Iwi" type="quoted"/>) have images only. Item files can also specify metadata. In our example the newspaper series is recorded as <AutoText key="metadata::ex.Title"/> and its date of publication as <AutoText key="metadata::ex.Date"/>. Issue <AutoText key="metadata::ex.Volume"/> and <AutoText key="metadata::ex.Number"/> metadata is also recorded, where appropriate. This metadata is extracted as part of the building process.</Text>
    26312587</Comment>
    26322588<NumberedItem>
    … …  
    26342590</NumberedItem>
    26352591<NumberedItem>
    2636 <Text id="0679">In the <AutoText key="glidict::GUI.Gather"/> panel, open the <Path>sample_files &rarr; niupepa &rarr; sample_items</Path> folder and drag the two subfolders into your collection on the right-hand side. A popup window asks whether you want to add <AutoText text="PagedImgPlug"/> to the collection: click <AutoText key="glidict::CDM.PlugInManager.QuickAdd" type="button"/>, because this plugin will be needed to process the item files.</Text>
    2637 </NumberedItem>
    2638 <NumberedItem>
    2639 <Text id="0680">Some of the files you have just dragged in are the newspaper images; others are text files that contain the text extracted from these images. We want these to be processed by <AutoText text="PagedImgPlug"/>, not <AutoText text="ImagePlug"/> or <AutoText text="TEXTPlug"/>. Switch to the <AutoText key="glidict::CDM.GUI.Plugins"/> section of the <AutoText key="glidict::GUI.Design"/> panel and <i>delete <AutoText text="ImagePlug"/> and <AutoText text="TEXTPlug"/></i>.</Text>
    2640 </NumberedItem>
    2641 <NumberedItem>
    2642 <Text id="0678">Open up the configuration window for <AutoText text="PagedImgPlug"/> by double-clicking on the plugin. Switch on its <AutoText text="screenview"/> configuration option by checking the box. The source images we use were scanned at high resolution and are large files for a browser to download. The <AutoText text="screenview"/> option generates smaller screen-resolution images of each page when the collection is built. Click <AutoText key="glidict::General.OK" type="button"/>.</Text>
     2592<Text id="0679">In the <AutoText key="glidict::GUI.Gather"/> panel, open the <Path>sample_files &rarr; niupepa &rarr; sample_items</Path> folder and drag the two subfolders into your collection on the right-hand side. A popup window asks whether you want to add <AutoText text="PagedImagePlugin"/> to the collection: click <AutoText key="glidict::CDM.PlugInManager.QuickAdd" type="button"/>, because this plugin will be needed to process the item files.</Text>
     2593</NumberedItem>
     2594<NumberedItem>
     2595<Text id="0680">Some of the files you have just dragged in are the newspaper images; others are text files that contain the text extracted from these images. We want these to be processed by <AutoText text="PagedImagePlugin"/>, not <AutoText text="ImagePlugin"/> or <AutoText text="TextPlugin"/>. Switch to the <AutoText key="glidict::CDM.GUI.Plugins"/> section of the <AutoText key="glidict::GUI.Design"/> panel and <i>delete <AutoText text="ImagePlugin"/> and <AutoText text="TextPlugin"/></i>.</Text>
     2596</NumberedItem>
     2597<NumberedItem>
     2598<Text id="0678">Open up the configuration window for <AutoText text="PagedImagePlugin"/> by double-clicking on the plugin. Switch on its <AutoText text="create_screenview"/> configuration option by checking the box. The source images we use were scanned at high resolution and are large files for a browser to download. The <AutoText text="create_screenview"/> option generates smaller screen-resolution images of each page when the collection is built. Click <AutoText key="glidict::General.OK" type="button"/>.</Text>
    26432599</NumberedItem>
    26442600<NumberedItem>
    … …  
    26522608</Heading>
    26532609<Comment>
    2654 <Text id="0684">Under <AutoText key="coredm::_Global:labelTitle_"/> documents from the same series are repeated without any distinguishing features such as date, volume or number. It would be better to group them by series title and display other information within each group. This can be accomplished using an <AutoText text="AZCompactList"/> classifier rather than <AutoText text="AZList"/>, and tuning the classifier's format statement.</Text>
    2655 </Comment>
    2656 <NumberedItem>
    2657 <Text id="0685">In the <AutoText key="glidict::GUI.Design"/> panel, under the <AutoText key="glidict::CDM.GUI.Classifiers"/> section, delete the <AutoText text="AZList" /> classifiers for <AutoText key="metadata::ex.Source"/> and <AutoText key="metadata::ex.Title"/>.</Text>
    2658 </NumberedItem>
    2659 <NumberedItem>
    2660 <Text id="0686">Now add an <AutoText text="AZCompactList" /> classifier, setting its <AutoText text="metadata"/> option to <AutoText key="metadata::ex.Title"/>, and add a <AutoText text="DateList" /> classifier, setting its <AutoText text="metadata"/> option to <AutoText key="metadata::ex.Date"/>.</Text>
     2610<Text id="0684">Under <AutoText key="coredm::_Global:labelTitle_"/> documents from the same series are repeated without any distinguishing features such as date, volume or number. It would be better to group them by series title and display other information within each group. This can be accomplished using an <AutoText text="AZCompactList"/> classifier rather than <AutoText text="List"/>, and tuning the classifier's format statement.</Text>
     2611</Comment>
     2612<NumberedItem>
     2613<Text id="0685">In the <AutoText key="glidict::GUI.Design"/> panel, under the <AutoText key="glidict::CDM.GUI.Classifiers"/> section, delete the <AutoText text="List" /> classifiers for <AutoText key="metadata::ex.Source"/>. Select <AutoText text="dc.Title;Title"/> and click <AutoText key="glidict::CDM.ClassifierManager.Configure" type="button"/>. Set <AutoText text="bookshelf_type"/> to <AutoText text="always"/>. This will create a bookshelf as in the <AutoText text="AZCompactList"/> classifier for duplicate items.</Text>
     2614</NumberedItem>
     2615<NumberedItem>
     2616<Text id="0686">Now add a <AutoText text="DateList" /> classifier, setting its <AutoText text="metadata"/> option to <AutoText key="metadata::ex.Date"/>.</Text>
    26612617</NumberedItem>
    26622618<NumberedItem>
    … …  
    26642620</NumberedItem>
    26652621<NumberedItem>
    2666 <Text id="0687">Now we change the format statement for <AutoText key="coredm::_Global:labelTitle_" type="italics"/> to display more information about the documents. In the <AutoText key="glidict::CDM.GUI.Formats"/> section of the <AutoText key="glidict::GUI.Format"/> panel, select the <AutoText key="metadata::ex.Title"/> classifier in the <AutoText key="glidict::CDM.FormatManager.Feature"/> list, and <AutoText text="VList"/> in the <AutoText key="glidict::CDM.FormatManager.Part"/> list. Click <AutoText key="glidict::CDM.FormatManager.Add" type="button"/> to add this format statement to your collection. Delete the contents of the <AutoText key="glidict::CDM.FormatManager.Editor"/> box, and add the following text. (This format statement can be copied and pasted from the file <Path>sample_files &rarr; niupepa &rarr; formats &rarr; titles_tweak.txt</Path>.)</Text>
     2622<Text id="0687">Now we change the format statement for <AutoText key="coredm::_Global:labelTitle_" type="italics"/> to display more information about the documents. In the <AutoText key="glidict::CDM.GUI.Formats"/> section of the <AutoText key="glidict::GUI.Format"/> panel, select the <AutoText text="dc.Title;Title"/> classifier (CL1) in the <AutoText key="glidict::CDM.FormatManager.Feature"/> list, and <AutoText text="VList"/> in the <AutoText key="glidict::CDM.FormatManager.Part"/> list. Click <AutoText key="glidict::CDM.FormatManager.Add" type="button"/> to add this format statement to your collection. Delete the contents of the <AutoText key="glidict::CDM.FormatManager.Editor"/> box, and add the following text. (This format statement can be copied and pasted from the file <Path>sample_files &rarr; niupepa &rarr; formats &rarr; titles_tweak.txt</Path>.)</Text>
    26672623<Format>
    26682624&lt;td valign="top"&gt;[link][icon][/link]&lt;/td&gt;<br/>
    … …  
    26752631<NumberedItem>
    26762632<Text id="0690a">Refresh in the web browser to view the new <AutoText key="coredm::_Global:labelTitle_" type="italics"/> list.</Text>
    2677 <Text id="0687c">As a consequence of using the <AutoText text="AZCompactList"/> classifier, bookshelf icons appear when titles are browsed. This revised format statement has the effect of specifying in brackets how many items are contained within a bookshelf. It works by exploiting the fact that only bookshelf icons define <Format>[numleafdocs]</Format> metadata. For document nodes, Title is not displayed. Instead, Volume, Number and Date information are displayed.</Text>
    2678 </NumberedItem>
    2679 <NumberedItem>
    2680 <Text id="0691">The <AutoText key="coredm::_Global:labelDate_" type="italics"/> list groups documents by date. A numeric date is displayed at the end of each document title, for example 18580601. This is in the Greenstone internal date format, which is crucial for the <AutoText text="DateList" /> classifier to correctly parse date metadata and generate an ordered date list. However, you can make the date look nice by adding a <AutoText text="[Format:]"/> macro to date metadata.</Text>
     2633<Text id="0687c">As a consequence of using the <AutoText text="bookshelf_type"/> option of the <AutoText text="List"/> classifier, bookshelf icons appear when titles are browsed. This revised format statement has the effect of specifying in brackets how many items are contained within a bookshelf. It works by exploiting the fact that only bookshelf icons define <Format>[numleafdocs]</Format> metadata. For document nodes, Title is not displayed. Instead, Volume, Number and Date information are displayed.</Text>
     2634</NumberedItem>
     2635<NumberedItem>
     2636<Text id="0691">The <AutoText key="coredm::_Global:labelDate_" type="italics"/> list groups documents by date. A numeric date is displayed at the end of each document title, for example 18580601. This is in the Greenstone internal date format, which is crucial for the <AutoText text="DateList" /> classifier (CL2) to correctly parse date metadata and generate an ordered date list. However, you can make the date look nice by adding a <AutoText text="[Format:]"/> macro to date metadata.</Text>
    26812637</NumberedItem>
    26822638<NumberedItem>
    … …  
    27062662</Format>
    27072663<Comment>
    2708 <Text id="0698">Including <Format>[screenicon]</Format> has the effect of embedding the screen-sized image generated by switching the <AutoText text="screenview"/> option on in <AutoText text="PagedImgPlug"/>. It is hyperlinked to the original image by the construct <Format>[srclink]...[/srclink]</Format>. This is a large image but it may be scaled by your browser.</Text>
     2664<Text id="0698">Including <Format>[screenicon]</Format> has the effect of embedding the screen-sized image generated by switching the <AutoText text="screenview"/> option on in <AutoText text="PagedImagePlugin"/>. It is hyperlinked to the original image by the construct <Format>[srclink]...[/srclink]</Format>. This is a large image but it may be scaled by your browser.</Text>
    27092665</Comment>
    27102666<Text id="0698a">This modification will display screenview image, but does nothing about the dummy text <AutoText key="perlmodules::BasePlugin.dummy_text" type="quoted"/>, which will still be displayed. To get rid of this, edit the <AutoText text="DocumentText"/> format statement again and replace</Text>
    … …  
    27372693</NumberedItem>
    27382694<NumberedItem>
    2739 <Text id="0690f">**I think this section is no longer valid - test and remove**You will notice that when searching for individual pages, the newspaper image is displayed in the search results. As these images are very large, this is not very useful. Go to <AutoText key="glidict::CDM.GUI.Formats"/> section of the <AutoText key="glidict::GUI.Format"/> panel in the Librarian Interface, choose <AutoText key="glidict::CDM.FormatManager.AllFeatures"/>  in <AutoText key="glidict::CDM.FormatManager.Feature"/> list, and select the <AutoText text="VList"/> format statement from the list of assigned format statements. Remove the second line from the <AutoText key="glidict::CDM.FormatManager.Editor"/>:</Text>
     2695<Text id="0690f">You will notice that when searching for individual pages, the newspaper image is displayed in the search results. As these images are very large, this is not very useful. Go to <AutoText key="glidict::CDM.GUI.Formats"/> section of the <AutoText key="glidict::GUI.Format"/> panel in the Librarian Interface, choose <AutoText key="glidict::CDM.FormatManager.AllFeatures"/>  in <AutoText key="glidict::CDM.FormatManager.Feature"/> list, and select the <AutoText text="VList"/> format statement from the list of assigned format statements. Remove the second line from the <AutoText key="glidict::CDM.FormatManager.Editor"/>:</Text>
    27402696<Format>
    27412697&lt;td valign="top"&gt;[ex.srclink]{Or}{[ex.thumbicon],[ex.srcicon]}[ex./srclink]&lt;/td&gt;
    27422698</Format>
    2743 <Text id="0690f-1">The reason why this is causing a problem is that the <AutoText text="PagedImgPlug"/> does not produce ex.thumbicon, and as a consequence this format statement displays ex.srcicon, which is very large  </Text>
     2699<Text id="0690f-1">The reason why this is causing a problem is that the <AutoText text="PagedImagePlugin"/> does not produce ex.thumbicon, and as a consequence this format statement displays ex.srcicon, which is very large  </Text>
    27442700<Text id="0690f-2">While we are here, let's remove the filename from the display. Remove the following from the last line of the format string:</Text>
    27452701<Format>
    … …  
    28082764<SampleFiles folder="niupepa"/>
    28092765<Prerequisite id="scanned_image_collection"/>
    2810 <Version initial="2.70" current="2.80"/>
     2766<Version initial="2.70" current="2.82"/>
    28112767<Content>
    28122768<Comment>
    … …  
    28742830</Heading>
    28752831<NumberedItem>
    2876 <Text id="sc25">Paged documents can be presented with a hierarchical table of contents, or with next and previous page arrows, and a "go to page" box (like we have done so far). The display type is specified by the <AutoText text="documenttype (hierarchy|paged)"/> option to <AutoText text="PagedImgPlug"/>. The next and previous arrows suit the linear sequence documents, while the table of contents suits the hierarchically organised document. </Text>
    2877 <Text id="sc25a">Ordinarily, a Greenstone collection would have one plugin per document type, and all documents of that type get the same processing. In this case, we want to treat the XML-based item files differently from the text-based item files. We can achieve this by adding two <AutoText text="PagedImgPlug"/> plugins to the collection, and configuring them differently.</Text>
    2878 </NumberedItem>
    2879 <NumberedItem>
    2880 <Text id="sc25b">Change the mode in the Librarian Interface to <AutoText key="glidict::Preferences.Mode.Systems"/> (or <AutoText key="glidict::Preferences.Mode.Expert"/>) mode (using <Menu><AutoText key="glidict::Menu.File"/> &rarr; <AutoText key="glidict::Menu.File_Options"/> &rarr; <AutoText key="glidict::Preferences.Mode"/></Menu>), because you will need to change the order of plugins, and use regular expressions in the plugin options.</Text>
     2832<Text id="sc25">Paged documents can be presented with a hierarchical table of contents, or with next and previous page arrows, and a "go to page" box (like we have done so far). The display type is specified by the <AutoText text="documenttype (hierarchy|paged)"/> option to <AutoText text="PagedImagePlugin"/>. The next and previous arrows suit the linear sequence documents, while the table of contents suits the hierarchically organised document. </Text>
     2833<Text id="sc25a">Ordinarily, a Greenstone collection would have one plugin per document type, and all documents of that type get the same processing. In this case, we want to treat the XML-based item files differently from the text-based item files. We can achieve this by adding two <AutoText text="PagedImagePlugin"/> plugins to the collection, and configuring them differently.</Text>
     2834</NumberedItem>
     2835<NumberedItem>
     2836<Text id="sc25b">For versions before 2.82, you need to change the mode in the Librarian Interface to <AutoText text="Library Systems Specialist"/> (or <AutoText key="glidict::Preferences.Mode.Expert"/>) mode (using <Menu><AutoText key="glidict::Menu.File"/> &rarr; <AutoText key="glidict::Menu.File_Options"/> &rarr; <AutoText key="glidict::Preferences.Mode"/></Menu>), because you will need to change the order of plugins, and use regular expressions in the plugin options.</Text>
    28812837<Comment>
    28822838<Text id="ep-23c-1">For version 2.71, you'll need to close GLI now then restart it to get the list of plugins to update properly.</Text>
    … …  
    28842840</NumberedItem>
    28852841<NumberedItem>
    2886 <Text id="sc25c">Go to the <AutoText key="glidict::CDM.GUI.Plugins"/> section of the <AutoText key="glidict::GUI.Design"/> panel, and add a new <AutoText text="PagedImgPlug"/> plugin. Enable the <AutoText text="screenview"/> option, set the <AutoText text="documenttype"/> option to <AutoText text="hierarchy"/> and set the <AutoText text="process_exp"/> option to <AutoText text="xml.*.item$"/>.</Text>
    2887 </NumberedItem>
    2888 <NumberedItem>
    2889 <Text id="sc25d">Move this <AutoText text="PagedImgPlug"/> plugin above the original one in the <AutoText key="glidict::CDM.PlugInManager.Assigned"/> list.</Text>
    2890 </NumberedItem>
    2891 <NumberedItem>
    2892 <Text id="sc28">The XML based newspapers have been grouped into a folder called <Path>xml</Path>. This enables us to process these files differently, by utilizing the <AutoText text="process_exp"/> option which all plugins support. The first <AutoText text="PagedImgPlug"/> in the list looks for item files underneath the <Path>xml</Path> folder. These documents will be processed as 'hierarchical' documents. Item files that don't match the process expression (i.e. aren't underneath the <Path>xml</Path> folder) will be passed onto the second <AutoText text="PagedImgPlug"/>, and these are treated as 'paged' documents.</Text>
     2842<Text id="sc25c">Go to the <AutoText key="glidict::CDM.GUI.Plugins"/> section of the <AutoText key="glidict::GUI.Design"/> panel, and add a new <AutoText text="PagedImagePlugin"/> plugin. Enable the <AutoText text="create_screenview"/> option, set the <AutoText text="documenttype"/> option to <AutoText text="hierarchy"/> and set the <AutoText text="process_exp"/> option to <AutoText text="xml.*.item$"/>.</Text>
     2843</NumberedItem>
     2844<NumberedItem>
     2845<Text id="sc25d">Move this <AutoText text="PagedImagePlugin"/> plugin above the original one in the <AutoText key="glidict::CDM.PlugInManager.Assigned"/> list.</Text>
     2846</NumberedItem>
     2847<NumberedItem>
     2848<Text id="sc28">The XML based newspapers have been grouped into a folder called <Path>xml</Path>. This enables us to process these files differently, by utilizing the <AutoText text="process_exp"/> option which all plugins support. The first <AutoText text="PagedImagePlugin"/> in the list looks for item files underneath the <Path>xml</Path> folder. These documents will be processed as 'hierarchical' documents. Item files that don't match the process expression (i.e. aren't underneath the <Path>xml</Path> folder) will be passed onto the second <AutoText text="PagedImagePlugin"/>, and these are treated as 'paged' documents.</Text>
    28932849<Text id="sc29"><b>Rebuild</b> and <b>preview</b> the collection. Compare the document display for a paged document e.g. <AutoText text="Te Waka o Te Iwi, Vol. 1, No. 1"/> with a hierarchical document, e.g. <AutoText text="Matariki 1881, No. 1"/>.</Text>
    28942850</NumberedItem>
    … …  
    29422898</Title>
    29432899<SampleFiles folder="oai"/>
    2944 <Version initial="2.60" current="2.80"/>
     2900<Version initial="2.60" current="2.81"/>
    29452901<Content>
    29462902<Comment>
    … …  
    29572913</NumberedItem>
    29582914<NumberedItem>
    2959 <Text id="0707">During the copy operation, a popup window appears asking whether to add <AutoText text="OAIPlug" /> to the list of plug-ins used in the collection, because the Librarian Interface has not found an existing plug-in that can handle this file type. Press the <AutoText key="glidict::CDM.PlugInManager.QuickAdd" type="button"/> button to include it.</Text>
     2915<Text id="0707">During the copy operation, a popup window appears asking whether to add <AutoText text="OAIPlugin" /> to the list of plug-ins used in the collection, because the Librarian Interface has not found an existing plug-in that can handle this file type. Press the <AutoText key="glidict::CDM.PlugInManager.QuickAdd" type="button"/> button to include it.</Text>
    29602916<Text id="0707a">The files for this collection consist of a set of images (in <Path>JCDLPICS &rarr; srcdocs</Path>) and a set of OAI records (in <Path>JCDLPICS</Path>) which contain metadata for the images.</Text>
    29612917</NumberedItem>
    … …  
    29672923</Comment>
    29682924<NumberedItem>
    2969 <Text id="0710">You need to configure the image plug-in. In the <AutoText key="glidict::GUI.Design"/> panel, select the <AutoText key="glidict::CDM.GUI.Plugins"/> section, then select the <AutoText text="ImagePlug"/> line and click <AutoText key="glidict::CDM.PlugInManager.Configure" type="button"/>. In the resulting popup window locate the <AutoText text="screenviewsize"/> option, switch it on, and type the number <AutoText text="300"/> in the box beside it to create a screen-view image of 300 pixels. Click <AutoText key="glidict::General.OK" type="button"/>.</Text>
     2925<Text id="oai-plugin-option">You need to specifiy which document the OAI metadata values should be attached to. In the <AutoText key="glidict::GUI.Design"/> panel, select the <AutoText key="glidict::CDM.GUI.Plugins"/> section, then select the <AutoText text="OAIPlugin"/> and click <AutoText key="glidict::CDM.PlugInManager.Configure" type="button"/>. Locate the <AutoText text="document_field"/> option in the popup window and select <AutoText text="dc.Resource Identifier"/> from the drop-down list. Click <AutoText key="glidict::General.OK" type="button"/>.</Text>
     2926</NumberedItem>
     2927<NumberedItem>
     2928<Text id="0710">You also need to configure the image plug-in. Select the <AutoText text="ImagePlugin"/> line in the <AutoText key="glidict::CDM.GUI.Plugins"/> section and click <AutoText key="glidict::CDM.PlugInManager.Configure" type="button"/>. In the resulting popup window locate the <AutoText text="screenviewsize"/> option, switch it on, and type the number <AutoText text="300"/> in the box beside it to create a screen-view image of 300 pixels. Click <AutoText key="glidict::General.OK" type="button"/>.</Text>
    29702929</NumberedItem>
    29712930<NumberedItem>
    29722931<Text id="0711">Now switch to the <AutoText key="glidict::GUI.Create"/> panel and <b>build</b> and <b>preview</b> the collection.</Text>
    2973 <Text id="0711a"><AutoText text="OAIPlug"/> will process the OAI records, and assign metadata to the images, which are processed by <AutoText text="ImagePlug"/>.</Text>
     2932<Text id="0711a"><AutoText text="OAIPlugin"/> will process the OAI records, and assign metadata to the images, which are processed by <AutoText text="ImagePlugin"/>.</Text>
    29742933</NumberedItem>
    29752934<Comment>
    … …  
    29802939</NumberedItem>
    29812940<NumberedItem>
    2982 <Text id="0714">Add an <AutoText text="AZCompactList" /> classifier based on <AutoText key="metadata::ex.Subject"/> metadata.</Text>
    2983 </NumberedItem>
    2984 <NumberedItem>
    2985 <Text id="0715">Now add an <AutoText text="AZCompactList" /> classifier based on <AutoText key="metadata::ex.Description"/> metadata. In its configuration panel set <AutoText text="mingroup"/> to <AutoText text="2"/>, <AutoText text="mincompact"/> to <AutoText text="1"/>, <AutoText text="maxcompact"/> to <AutoText text="10"/> and <AutoText text="buttonname"/> to <AutoText text="Captions"/>.</Text><Text id="0715a">Setting <AutoText text="mingroup"/> to 2 will mean that two or more documents with the same description will be grouped into a bookshelf; the default <AutoText text="mingroup"/> of 1 means that every document will get a bookshelf. <AutoText text="mincompact"/> and <AutoText text="maxcompact"/> control how many documents are grouped into each section of the horizontal A-Z list. In this case, each group can have as few as one document, and no more than ten.</Text>
    2986 </NumberedItem>
    2987 <NumberedItem>
    2988 <Text id="0716">In the <AutoText key="glidict::CDM.GUI.Indexes"/> section of the <AutoText key="glidict::GUI.Design"/> panel, delete all indexes and add a new one based on <AutoText key="metadata::ex.Description"/> metadata.</Text>
     2941<Text id="0714">Add an <AutoText text="AZCompactList" /> classifier based on <AutoText key="metadata::dc.Subject"/> metadata.</Text>
     2942</NumberedItem>
     2943<NumberedItem>
     2944<Text id="0715">Now add an <AutoText text="AZCompactList" /> classifier based on <AutoText key="metadata::dc.Description"/> metadata. In its configuration panel set <AutoText text="mingroup"/> to <AutoText text="2"/>, <AutoText text="mincompact"/> to <AutoText text="1"/>, <AutoText text="maxcompact"/> to <AutoText text="10"/> and <AutoText text="buttonname"/> to <AutoText text="Captions"/>.</Text>
     2945<Text id="0715a">Setting <AutoText text="mingroup"/> to 2 will mean that two or more documents with the same description will be grouped into a bookshelf; the default <AutoText text="mingroup"/> of 1 means that every document will get a bookshelf. <AutoText text="mincompact"/> and <AutoText text="maxcompact"/> control how many documents are grouped into each section of the horizontal A-Z list. In this case, each group can have as few as one document, and no more than ten.</Text>
     2946</NumberedItem>
     2947<NumberedItem>
     2948<Text id="0716">In the <AutoText key="glidict::CDM.GUI.Indexes"/> section of the <AutoText key="glidict::GUI.Design"/> panel, delete all indexes and add a new one based on <AutoText key="metadata::dc.Description"/> metadata.</Text>
    29892949</NumberedItem>
    29902950<NumberedItem>
    … …  
    30012961&lt;/td&gt;<br/>
    30022962&lt;td valign=middle&gt;<br/>
    3003 &nbsp;&nbsp;{If}{[numleafdocs],[Title],&lt;i&gt;[Description]&lt;/i&gt;}<br/>
     2963&nbsp;&nbsp;{If}{[numleafdocs],[Title],&lt;i&gt;[dc.Description]&lt;/i&gt;}<br/>
    30042964&lt;/td&gt;
    30052965</Format>
    … …  
    30102970<NumberedItem>
    30112971<Text id="0722">Next, select <AutoText text="DocumentHeading"/> from the <AutoText key="glidict::CDM.FormatManager.Feature"/> pull-down list and change its format statement to: </Text>
    3012 <Format>&lt;h3&gt;[Subject]&lt;/h3&gt;</Format>
    3013 <Comment>
    3014 <Text id="0723">The document heading appears above the <AutoText key="coredm::_document:textDETACH_" type="italics"/> and <AutoText key="coredm::_document:textNOHIGHLIGHT_" type="italics"/> buttons when you get to a document in the collection. By default <AutoText text="DocumentHeading"/> displays the document's <AutoText key="metadata::ex.Title"/> metadata. In this particular set of OAI exported records, titles are filenames of JPEG images, and the filenames are particularly uninformative (for example, 01dla14). You can see them in the <AutoText key="glidict::GUI.Enrich"/> panel if you select an image in <Path>oai &rarr; JCDLPICS &rarr; srcdocs</Path> and check its <AutoText key="metadata::ex.Source"/> and <AutoText key="metadata::ex.Title"/> metadata. The above format statement displays <AutoText key="metadata::ex.Subject"/> metadata instead.</Text>
     2972<Format>&lt;h3&gt;[dc.Subject]&lt;/h3&gt;</Format>
     2973<Comment>
     2974<Text id="0723">The document heading appears above the <AutoText key="coredm::_document:textDETACH_" type="italics"/> and <AutoText key="coredm::_document:textNOHIGHLIGHT_" type="italics"/> buttons when you get to a document in the collection. By default <AutoText text="DocumentHeading"/> displays the document's <AutoText key="metadata::ex.Title"/> metadata. In this particular set of OAI exported records, titles are filenames of JPEG images, and the filenames are particularly uninformative (for example, 01dla14). You can see them in the <AutoText key="glidict::GUI.Enrich"/> panel if you select an image in <Path>oai &rarr; JCDLPICS &rarr; srcdocs</Path> and check its <AutoText key="metadata::ex.Source"/> and <AutoText key="metadata::ex.Title"/> metadata. The above format statement displays <AutoText key="metadata::dc.Subject"/> metadata instead.</Text>
    30152975</Comment>
    30162976</NumberedItem>
    … …  
    30192979<Format>&lt;center&gt;&lt;table width=_pagewidth_ border=1&gt;<br/>
    30202980&nbsp;&nbsp;&lt;tr&gt;&lt;td colspan=2 align=center&gt;<br/>
    3021 &nbsp;&nbsp;&nbsp;&nbsp;&lt;a href=[OrigURL]&gt;[screenicon]&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;<br/>
    3022 &nbsp;&nbsp;&lt;tr&gt;&lt;td&gt;Caption:&lt;/td&gt;&lt;td&gt; &lt;i&gt;[Description]&lt;/i&gt; &lt;br&gt;<br/>
    3023 &nbsp;&nbsp;&nbsp;&nbsp;(&lt;a href=[OrigURL]&gt;original [ImageWidth]x[ImageHeight] [ImageType] available&lt;/a&gt;)<br/>
     2981&nbsp;&nbsp;&nbsp;&nbsp;&lt;a href=[dc.OrigURL]&gt;[screenicon]&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;<br/>
     2982&nbsp;&nbsp;&lt;tr&gt;&lt;td&gt;Caption:&lt;/td&gt;&lt;td&gt; &lt;i&gt;[dc.Description]&lt;/i&gt; &lt;br&gt;<br/>
     2983&nbsp;&nbsp;&nbsp;&nbsp;(&lt;a href=[dc.OrigURL]&gt;original [ImageWidth]x[ImageHeight] [ImageType] available&lt;/a&gt;)<br/>
    30242984&nbsp;&nbsp;&nbsp;&nbsp;&lt;/td&gt;&lt;/tr&gt;<br/>
    3025 &nbsp;&nbsp;&lt;tr&gt;&lt;td&gt;Subject:&lt;/td&gt;&lt;td&gt; [Subject]&lt;/td&gt;&lt;/tr&gt;<br/>
    3026 &nbsp;&nbsp;&lt;tr&gt;&lt;td&gt;Publisher:&lt;/td&gt;&lt;td&gt; [Publisher]&lt;/td&gt;&lt;/tr&gt;<br/>
    3027 &nbsp;&nbsp;&lt;tr&gt;&lt;td&gt;Rights:&lt;td&gt; [Rights]&lt;/td&gt;&lt;/tr&gt;<br/>
     2985&nbsp;&nbsp;&lt;tr&gt;&lt;td&gt;Subject:&lt;/td&gt;&lt;td&gt; [dc.Subject]&lt;/td&gt;&lt;/tr&gt;<br/>
     2986&nbsp;&nbsp;&lt;tr&gt;&lt;td&gt;Publisher:&lt;/td&gt;&lt;td&gt; [dc.Publisher]&lt;/td&gt;&lt;/tr&gt;<br/>
     2987&nbsp;&nbsp;&lt;tr&gt;&lt;td&gt;Rights:&lt;td&gt; [dc.Rights]&lt;/td&gt;&lt;/tr&gt;<br/>
    30282988&lt;/table&gt;&lt;/center&gt;</Format>
    30292989<Text id="0730">This format statement alters how the document view is presented. It includes a screen-sized version of the image that hyperlinks back to the original larger version available on the web. Factual information extracted from the image, such as width, height and type, is also displayed.</Text>
    … …  
    30423002</Title>
    30433003<Prerequisite id="OAI_collection"/>
    3044 <Version initial="2.60" current="2.80"/>
     3004<Version initial="2.60" current="2.81"/>
    30453005<Content>
    30463006<Comment>
    … …  
    30583018</NumberedItem>
    30593019<NumberedItem>
    3060 <Text id="oai-4">We want to download the documents as well as the metadata, so tick the <AutoText text="get_doc"/> checkbox.</Text>
     3020<Text id="oai-4">We want to download the documents as well as the metadata, so tick the <AutoText text="Get document"/> checkbox.</Text>
    30613021</NumberedItem>
    30623022<NumberedItem>
    … …  
    31223082<Text id="0750">Use METS as Greenstone's Internal Representation</Text>
    31233083</Title>
    3124 <Version initial="2.60" current="2.80"/>
     3084<Version initial="2.60" current="2.81"/>
    31253085<Content>
    31263086<NumberedItem>
    … …  
    31283088</NumberedItem>
    31293089<Comment>
    3130 <Text id="0752">To be able to substitute <AutoText text="METSPlug"/> for <AutoText text="GAPlug"/> you need to be in <AutoText key="glidict::Preferences.Mode.Expert"/> mode.</Text>
     3090<Text id="0752">To be able to substitute <AutoText text="GreenstoneMETSPlugin"/> for <AutoText text="GreenstoneXMLPlugin"/> you need to be in <AutoText key="glidict::Preferences.Mode.Expert"/> mode.</Text>
    31313091</Comment>
    31323092<NumberedItem>
    … …  
    31343094</NumberedItem>
    31353095<NumberedItem>
    3136 <Text id="0756">Switch to the <AutoText key="glidict::GUI.Design"/> panel and select <AutoText key="glidict::CDM.GUI.Plugins"/>. Remove <AutoText text="GAPlug"/> from the list of plug-ins and add <AutoText text="METSPlug" />, with the default configuration options.</Text>
     3096<Text id="0756">Switch to the <AutoText key="glidict::GUI.Design"/> panel and select <AutoText key="glidict::CDM.GUI.Plugins"/>. Remove <AutoText text="GreenstoneXMLPlugin"/> from the list of plug-ins and add <AutoText text="GreenstoneMETSPlugin" />, with the default configuration options.</Text>
    31373097</NumberedItem>
    31383098<NumberedItem>
    … …  
    31523112</Title>
    31533113<SampleFiles folder="dspace"/>
    3154 <Version initial="2.60" current="2.80"/>
     3114<Version initial="2.60" current="2.81"/>
    31553115<Content>
    31563116<NumberedItem>
    3157 <Text id="0761">First, change to <AutoText key="glidict::Preferences.Mode.Systems"/> (or <AutoText key="glidict::Preferences.Mode.Expert"/>) mode (using <Menu><AutoText key="glidict::Menu.File"/> &rarr; <AutoText key="glidict::Menu.File_Options"/></Menu>), because you will need to change the order of plug-ins in the <AutoText key="glidict::GUI.Design"/> panel.</Text>
     3117<Text id="0761">First, change to <AutoText text="Library Systems Specialist"/> (or <AutoText key="glidict::Preferences.Mode.Expert"/>) mode (using <Menu><AutoText key="glidict::Menu.File"/> &rarr; <AutoText key="glidict::Menu.File_Options"/></Menu>), because you will need to change the order of plug-ins in the <AutoText key="glidict::GUI.Design"/> panel.</Text>
    31583118</NumberedItem>
    31593119<NumberedItem>
    31603120<Text id="0763">Start a <b>new collection</b> called <b>StoneD</b> and fill out its fields appropriately. Leave the metadata set at Dublin Core, the default.</Text>
    31613121</NumberedItem>
    3162 <!-- don't need to remove the plugins -->
    3163 <!--
    3164 <NumberedItem>
    3165 <Text id="0764">Switch to the <AutoText key="glidict::GUI.Design"/> panel and select the <AutoText key="glidict::CDM.GUI.Plugins"/> section on the left-hand side. <b>Remove</b> <AutoText text="ZIPPlug" />, <AutoText text="TEXTPlug" />, <AutoText text="HTMLPlug" />, <AutoText text="EMAILPlug" />, <AutoText text="PSPlug" />, <AutoText text="ImagePlug" />, <AutoText text="ISISPlug" /> and <AutoText text="NULPlug" />. Strictly speaking we do not need to remove these, however it reduces clutter.</Text>
    3166 </NumberedItem>
    3167 -->
    3168 <NumberedItem>
    3169 <Text id="0765">Now add <AutoText text="DSpacePlug" />. Leave the plugin options at their defaults and press <AutoText key="glidict::General.OK" type="button"/>.</Text>
    3170 </NumberedItem>
    3171 <NumberedItem>
    3172 <Text id="0766">Using the up arrow, <b>move</b> the position of <AutoText text="DSpacePlug" /> to the top of the list (above <AutoText text="GAPlug" />).</Text>
     3122<NumberedItem>
     3123<Text id="0765">Now add <AutoText text="DSpacePlugin" />. Leave the plugin options at their defaults and press <AutoText key="glidict::General.OK" type="button"/>.</Text>
     3124</NumberedItem>
     3125<NumberedItem>
     3126<Text id="0766">Using the up arrow, <b>move</b> the position of <AutoText text="DSpacePlugin" /> to the top of the list (above <AutoText text="GreenstoneXMLPlugin" />).</Text>
    31733127</NumberedItem>
    31743128<NumberedItem>
    … …  
    31883142</Comment>
    31893143<NumberedItem>
    3190 <Text id="0773">Select <AutoText text="DSpacePlug" /> and click <AutoText key="glidict::CDM.PlugInManager.Configure" type="button"/>. Switch on its configuration option <AutoText text="first_inorder_ext"/>. Set its value to <AutoText text="pdf,doc,rtf" type="quoted"/> in the popup window that appears and press <AutoText key="glidict::General.OK" type="button"/>.</Text>
     3144<Text id="0773">Select <AutoText text="DSpacePlugin" /> and click <AutoText key="glidict::CDM.PlugInManager.Configure" type="button"/>. Switch on its configuration option <AutoText text="first_inorder_ext"/>. Set its value to <AutoText text="pdf,doc,rtf" type="quoted"/> in the popup window that appears and press <AutoText key="glidict::General.OK" type="button"/>.</Text>
    31913145</NumberedItem>
    31923146<NumberedItem>
    … …  
    32043158</NumberedItem>
    32053159<NumberedItem>
    3206 <Text id="0779">Staying within the <AutoText key="glidict::GUI.Design"/> panel, select <AutoText key="glidict::CDM.GUI.Classifiers"/> and <b>delete</b> both <AutoText text="AZList" /> classifiers (<AutoText key="metadata::ex.Title"/> and <AutoText key="metadata::ex.Source"/>). Add an <AutoText text="AZList" /> classifier for <AutoText key="metadata::dc.Title"/> and an <AutoText text="AZCompactList" /> classifier for <AutoText key="metadata::dc.Contributor"/>.</Text>
     3160<Text id="0779">Go back to the <AutoText key="glidict::GUI.Design"/> panel, select <AutoText key="glidict::CDM.GUI.Classifiers"/> and <b>delete</b> both <AutoText text="AZList" /> classifiers (<AutoText key="metadata::ex.Title"/> and <AutoText key="metadata::ex.Source"/>). Add an <AutoText text="AZList" /> classifier for <AutoText key="metadata::dc.Title"/> and an <AutoText text="AZCompactList" /> classifier for <AutoText key="metadata::dc.Contributor"/>.</Text>
    32073161</NumberedItem>
    32083162<NumberedItem>
    … …  
    32213175<Text id="0783">Leave <AutoText text="VList" /> as the <AutoText key="glidict::CDM.FormatManager.Part"/> and click <AutoText key="glidict::CDM.FormatManager.Add" type="button"/>. Edit the text in the <AutoText key="glidict::CDM.FormatManager.Editor"/> box. Replace</Text>
    32223176<Format>
    3223 {Or}{[dls.Title],[dc.Title],[ex.Title],Untitled}
     3177{Or}{[dc.Title],[exp.Title],[ex.Title],Untitled}
    32243178</Format>
    32253179<Text id="0783a">with</Text>
    … …  
    32423196</Title>
    32433197<Prerequisite id="dspace_to_greenstone"/>
    3244 <Version initial="2.60" current="2.80"/>
     3198<Version initial="2.60" current="2.81"/>
    32453199<Content>
    32463200<Comment>
    … …  
    32853239<Text id="gems-1">Editing metadata sets</Text>
    32863240</Title>
    3287 <Version initial="2.70w" current="2.80"/>
     3241<Version initial="2.70w" current="2.81"/>
    32883242<Content>
    32893243<Text id="gems-2">GEMS (Greenstone Editor for Metadata Sets) can be used to modify existing metadata sets or create new ones. GEMS is launched from the Librarian Interface when you want to create a new metadata set, or edit an existing one. In this exercise, we run GEMS outside of the Librarian Interface.</Text>
    … …  
    32923246</Heading>
    32933247<NumberedItem>
    3294 <Text id="gems-4">Start the Greenstone Editor for Metadata Sets (GEMS):</Text>
    3295 <Text id="gems-5"><Menu>Start &rarr; All Programs &rarr; Greenstone Digital Library Software &rarr; Greenstone Editor for Metadata Sets</Menu></Text>
     3248<Text id="gems-4">Start the Greenstone Editor for Metadata Sets (GEMS), for versions 2.81 and greater:</Text>
     3249<Text id="gems-5"><Menu>Start &rarr; All Programs &rarr; Greenstone-2.81 &rarr; Metadata Set Editor</Menu></Text>
     3250<Text id="gems-5a">and for versions below 2.81:</Text>
     3251<Text id="gems-5b"><Menu>Start &rarr; All Programs &rarr; Greenstone Digital Library Software &rarr; Greenstone Editor for Metadata Sets</Menu></Text>
    32963252</NumberedItem>
    32973253<NumberedItem>
    … …  
    33193275<Text id="gems-13">Save the new metadata set by <Menu><AutoText key="glidict::Menu.File"/> &rarr; <AutoText key="glidict::Menu.File_Save"/></Menu>, then close the GEMS by <Menu><AutoText key="glidict::Menu.File"/> &rarr; <AutoText key="glidict::Menu.File_Exit"/></Menu>.</Text>
    33203276</NumberedItem>
     3277</Content>
     3278</Tutorial>
     3279<Tutorial id="indexers">
     3280<Title>
     3281<Text id="indexers-1">Building and searching with different indexers</Text>
     3282</Title>
     3283<SampleFiles folder="demo"/>
     3284<Version initial="2.70w" current="2.81"/>
     3285<Content>
     3286<Text id="indexers-2">Greenstone supports three indexers <b>MG</b>, <b>MGPP</b> and <b>Lucene</b>. </Text>
     3287<Text id="indexers-3"><b>MG</b> is the original indexer used by Greenstone which is described in the book <b>"Managing Gigabytes"</b>. It does section level indexing and compression of the source documents. <b>MG</b> is implemented in C. </Text>
     3288<Text id="indexers-4"><b>MGPP</b> is re-implementation of <b>MG</b> that provides word-level indexes and enables proximity, phrase and field searching. <b>MGPP</b> is implemented in C++ and is the default indexer for new collections.</Text>
     3289<Text id="indexers-5"><b>Lucene</b> (http://lucene.apache.org/) is java-based full-featured text indexing and searching system developed by Apache. It provides a similar range of search functionality to MGPP with the addition of single-character wildcards and range searching. It was added to Greenstone to facilitate incremental collection building, which <b>MG</b> and <b>MGPP</b> can't provide.</Text>
     3290<Heading>
     3291<Text id="indexers-6">Build with Lucene</Text>
     3292</Heading>
     3293<NumberedItem>
     3294<Text id="indexers-7">Start a new collection (<Menu><AutoText key="glidict::Menu.File"/> &rarr; <AutoText key="glidict::Menu.File_New"/></Menu>) called <b>Demo Lucene</b> and base it on the <b>Greenstone demo (demo)</b> collection, fill out its fields appropriately.</Text>
     3295</NumberedItem>
     3296<NumberedItem>
     3297<Text id="indexers-8">In the <AutoText key="glidict::GUI.Gather"/> panel, click <AutoText key="glidict::Tree.World"/> and click <b>Greenstone demo (demo)</b>, it will show the documents in the <b>Greenstone demo</b> collection. Drag all 11 folders underneath <Path>Greenstone demo (demo)</Path> into the new collection.</Text>
     3298<Comment>
     3299<Text id="demo-collection">If you haven't installed the <b>Greenstone demo (demo)</b> collection yet, you can download the <Path>demo.zip</Path> file from the link above, unzip it and put it into the <Path>collect</Path> folder in your Greenstone installation.</Text>
     3300</Comment>
     3301</NumberedItem>
     3302<NumberedItem>
     3303<Text id="indexers-9">Go to the <AutoText key="glidict::GUI.Enrich"/> panel, look at the metadata that associated with each directory. Go to the <AutoText key="glidict::CDM.GUI.Indexes"/> section in the <AutoText key="glidict::GUI.Design"/> panel. The <b>MG indexer</b> is in use because the original <b>Greenstone Demo</b> collection, which this collection is based on, uses <b>MG indexer</b>.</Text>
     3304</NumberedItem>
     3305<NumberedItem>
     3306<Text id="indexers-11">Click the <AutoText key="glidict::CDM.BuildTypeManager.Change"/> button at the right top corner of the panel. A new window will pop up for selecting the Indexers. After selecting an indexer, a brief description will appear in the box below. Select Lucene and click <AutoText key="glidict::General.OK"/>. Please note that the <AutoText key="glidict::CDM.IndexManager.Indexes"/> has changed accordingly.</Text>
     3307</NumberedItem>
     3308<NumberedItem>
     3309<Text id="indexers-13"><b>Build</b> and <b>preview</b> the collection.</Text>
     3310</NumberedItem>
     3311<Heading>
     3312<Text id="indexers-14">Search with Lucene</Text>
     3313</Heading>
     3314<NumberedItem>
     3315<Text id="indexers-15">Lucene provides single letter and multiple letter wildcards and range searching. The query syntax could be quite complicated (for more information please see http://lucene.apache.org/java/docs/queryparsersyntax.html). Here we will learn how to use the wildcards while constructing queries.</Text>
     3316</NumberedItem>
     3317<NumberedItem>
     3318<Text id="lucene-1"><b>*</b> is a multiple letter wildcard. To perform a a multiple letter wildcard  search, append <b>*</b> to the end of the query term. For example, <i>econom*</i> will search for words like <i>econometrics</i>, <i>economist</i>, <i>economical</i>, <i>economy</i>, which have the common part <i>econom</i> but different word endings.</Text>
     3319</NumberedItem>
     3320<NumberedItem>
     3321<Text id="lucene-2">To perform a single letter wildcard search, use <b>?</b> instead. For example, search for <i>economi??</i> will only match words that have two and only two letters left after <i>economi</i>, such as <i>economist</i>, <i>economics</i>, and <i>economies</i>.</Text>
     3322</NumberedItem>
     3323<NumberedItem>
     3324<Text id="lucene-3">Please note that stopwords are used by default with Lucene indexer, so search for words like <i>the</i> will match 0 document. There is also a message on the search page saying that such words are too common and were ignored.</Text>
     3325</NumberedItem>
     3326<Heading>
     3327<Text id="indexers-19">Build with MGPP</Text>
     3328</Heading>
     3329<NumberedItem>
     3330<Text id="indexers-20">Start a new collection called <b>Greenstone Demo MGPP</b> and also base it on the <b>Greenstone demo (demo)</b>.</Text>
     3331</NumberedItem>
     3332<NumberedItem>
     3333<Text id="indexers-21">In the <AutoText key="glidict::GUI.Gather"/> panel, drag all the 11 folders from <Path><AutoText key="glidict::Tree.World"/> &rarr; Greenstone demo (demo)</Path> into the new collection. </Text>
     3334</NumberedItem>
     3335<NumberedItem>
     3336<Text id="indexers-22">Go to the <AutoText key="glidict::CDM.GUI.Indexes"/> section in the <AutoText key="glidict::GUI.Design"/> panel, click the <AutoText key="glidict::CDM.BuildTypeManager.Change"/> button and select <b>MGPP</b>. Click <AutoText key="glidict::General.OK"/>. Check the <AutoText key="glidict::CDM.IndexManager.Indexes"/> has changed accordingly.</Text>
     3337</NumberedItem>
     3338<NumberedItem>
     3339<Text id="indexers-23">There are three options at the bottom of the panel &mdash; <AutoText key="glidict::CDM.IndexingManager.Stem"/>, <AutoText key="glidict::CDM.IndexingManager.Casefold"/> and <AutoText key="glidict::CDM.IndexingManager.Accent_fold"/>. Notice that <AutoText key="glidict::CDM.IndexingManager.Stem"/> and <AutoText key="glidict::CDM.IndexingManager.Casefold"/> are enabled. Once an option is enabled, it will also appear in the collection's <AutoText key="coredm::_Global:linktextPREFERENCES_"/> page.</Text>
     3340</NumberedItem>
     3341<NumberedItem>
     3342<Text id="indexers-23a">In the <AutoText key="glidict::CDM.LevelManager.Level_Title"/> section, also select <AutoText key="glidict::CDM.LevelManager.Section"/>.</Text>
     3343</NumberedItem>
     3344<NumberedItem>
     3345<Text id="indexers-24"><b>Build</b> and <b>preview</b> the collection.</Text>
     3346</NumberedItem>
     3347<Heading>
     3348<Text id="indexers-25">Search with MGPP</Text>
     3349</Heading>
     3350<NumberedItem>
     3351<Text id="indexers-26">MGPP supports stemming and casefolding. By default search in collections built with MGPP indexer is set to <AutoText key="coredm::_preferences:textnostem_"/> and <AutoText key="coredm::_preferences:textignorecase_"/>. So search <i>econom</i> will return 0 document. Search for <i>fao</i> and <i>FAO</i> return the same result &mdash; 78 word counts and 9 matched documents.</Text>
     3352<Text id="indexers-26a">Go to the <AutoText key="coredm::_Global:linktextPREFERENCES_"/> page by click the <AutoText key="coredm::_Global:linktextPREFERENCES_"/> button at the top right corner. You can see that the <AutoText key="coredm::_preferences:textwordends_"/> option is set to <AutoText key="coredm::_preferences:textnostem_"/> and the <AutoText key="coredm::_preferences:textcasediffs_"/> option is set to <AutoText key="coredm::_preferences:textignorecase_"/>.</Text>
     3353</NumberedItem>
     3354<NumberedItem>
     3355<Text id="indexers-27">Sometimes we may want to ignore word endings while searching so as to match different variations of the term. Go to the <AutoText key="coredm::_Global:linktextPREFERENCES_"/> page and change the <AutoText key="coredm::_preferences:textwordends_"/> option from <AutoText key="coredm::_preferences:textnostem_"/> to <AutoText key="coredm::_preferences:textstem_"/>. Click the <AutoText key="coredm::_preferences:textsetprefs_"/> button. Click <AutoText key="coredm::_Global:textSearch_"/>. This time try search for <i>econom</i> again, 9 documents are found.</Text>
     3356<Text id="indexers-27a">Please note that word endings are determined according to the third-party stemming tables incorporated in Greenstone, not by the user. Thus the searches may not do precisely what is expected, especially when cultural variations or dialects are concerned. Besides, not all languages support stemming, only English and French have steming at the moment.</Text>
     3357<Text id="indexers-27b">Go to the <AutoText key="coredm::_Global:linktextPREFERENCES_"/> page and change back to <AutoText key="coredm::_preferences:textnostem_"/> to avoid confusion later on. Click the <AutoText key="coredm::_preferences:textsetprefs_"/> button.</Text>
     3358</NumberedItem>
     3359<NumberedItem>
     3360<Text id="indexers-28">Sometimes we may want to search the exact term, that is, differentiate the upper cases from lower cases. Set the <AutoText key="coredm::_preferences:textcasediffs_"/> option from <AutoText key="coredm::_preferences:textignorecase_"/> to <AutoText key="coredm::_preferences:textmatchcase_"/>. Click the <AutoText key="coredm::_preferences:textsetprefs_"/> button. Click <AutoText key="coredm::_Global:textSearch_"/>. Now try search for <i>fao</i> and <i>FAO</i> respectively this time, notice the difference in the results?</Text>
     3361<Text id="indexers-28a">Go back to the <AutoText key="coredm::_Global:linktextPREFERENCES_"/> page and change the <AutoText key="coredm::_preferences:textcasediffs_"/> option back to <AutoText key="coredm::_preferences:textignorecase_"/> to avoid confusion later on. Click <AutoText key="coredm::_preferences:textsetprefs_"/> button.</Text>
     3362</NumberedItem>
     3363<Heading>
     3364<Text id="indexers-29">Use search mode hotkeys with query term</Text>
     3365</Heading>
     3366<Comment>
     3367<Text id="mgpp-1">MGPP have several hotkeys to set search modes for a query term. These hotkeys explicitly set the <AutoText key="coredm::_preferences:textwordends_"/> option and the <AutoText key="coredm::_preferences:textcasediffs_"/> option for the query being constructed.</Text>
     3368</Comment>
     3369<NumberedItem>
     3370<Text id="mgpp-2"><b>#s</b> and <b>#u</b> are hotkeys for the <AutoText key="coredm::_preferences:textwordends_"/> option. Appending <b>#s</b> to a query term will specifically enable the <AutoText key="coredm::_preferences:textstem_"/> function. For example, try search for <i>econom#s</i>, 7 documents are found, which is the same as in step 17. Remember that we have set it back to <AutoText key="coredm::_preferences:textnostem_"/>. This means using hotkeys will override the current preference settings.</Text>
     3371</NumberedItem>
     3372<NumberedItem>
     3373<Text id="mgpp-3">Appending <b>#u</b> to a query term will explicitly set the current search to <AutoText key="coredm::_preferences:textnostem_"/>. </Text>
     3374<Text id="mgpp-4">Note that using hotkeys will only affect that query term. That is, hotkeys are used per term. For example, if a query expresssion contains more than one terms, some tems can have hotkeys and others not, and the hotkeys can be different for different terms. This provides a fine-grained control of the query, whereas changing settings in the <AutoText key="coredm::_Global:linktextPREFERENCES_"/> page will affect the query as a whole.</Text>
     3375</NumberedItem>
     3376<NumberedItem>
     3377<Text id="mgpp-5">Hotkeys <b>#i</b> and <b>#c</b> control the case sensitivity. Appending <b>#i</b> to a query term will explicitly set the search to <AutoText key="coredm::_preferences:textignorecase_"/> (ie. case insensitive).</Text>
     3378</NumberedItem>
     3379<NumberedItem>
     3380<Text id="mgpp-6">On the contrary, appending <b>#c</b> will specifically turn off the casefolding, that is, <AutoText key="coredm::_preferences:textmatchcase_"/>. For example, search for <i>fao#c</i> returns 0 document.</Text>
     3381</NumberedItem>
     3382<NumberedItem>
     3383<Text>Finally, the hotkeys can also be used in combination. For example, you can append <i>#uc</i> to a query term so as to match the whole term (without stemming) and in its exact form (differentiate upper cases and lower cases).</Text>
     3384</NumberedItem>
     3385<Heading>
     3386<Text id="quickref-1">A quick reference of the search mode hotkeys in MGPP</Text>
     3387</Heading>
     3388<Comment>
     3389<Format><AutoText key="coredm::_preferences:textwordends_"/></Format>
     3390<Format>&nbsp;&nbsp;&nbsp;&nbsp;<b>#s</b>&nbsp;&nbsp;&nbsp;&nbsp;<AutoText key="coredm::_preferences:textstem_"/></Format>
     3391<Format>&nbsp;&nbsp;&nbsp;&nbsp;<b>#u</b>&nbsp;&nbsp;&nbsp;&nbsp;<AutoText key="coredm::_preferences:textnostem_"/></Format>
     3392<Format><AutoText key="coredm::_preferences:textcasediffs_"/></Format>
     3393<Format>&nbsp;&nbsp;&nbsp;&nbsp;<b>#i</b>&nbsp;&nbsp;&nbsp;&nbsp;<AutoText key="coredm::_preferences:textignorecase_"/></Format>
     3394<Format>&nbsp;&nbsp;&nbsp;&nbsp;<b>#c</b>&nbsp;&nbsp;&nbsp;&nbsp;<AutoText key="coredm::_preferences:textmatchcase_"/></Format>
     3395</Comment>
     3396</Content>
     3397</Tutorial>
     3398<Tutorial id="depositor">
     3399<Title>
     3400<Text id="depositor-1">Incremental building of a collection</Text>
     3401</Title>
     3402<SampleFiles folder="demo_NewFiles"/>
     3403<Prerequisite id="indexers"/>
     3404<Version initial="2.71" current="2.81"/>
     3405<Content>
     3406<Text id="depositor-2">Collections built with <i>Lucene</i> indexer support incremental addition of documents. The <b>import</b> and <b>build</b> process by default delete old index files in the <b>index</b> directory and intermediate files in the <b>archives</b> directory. With incremental building, the <b>import</b> and <b>build</b> process will keep the old files and only process the new ones that haven’t been indexed.</Text>
     3407<Text id="depositor-3">In this tutorial we will learn how to use <AutoText key="coredm::_depositor:textdepositor_"/> for incremental building. Please note that Greenstone supports incremental addition of documents, but if you want to change the metadata or classifier or to delete or modify an existing document in the collection, then you will need to do a full import and build.</Text>
     3408<Heading>
     3409<Text id="depositor-5"><AutoText key="coredm::_depositor:textdepositor_"/></Text>
     3410</Heading>
     3411<Text id="depositor-6"><AutoText key="coredm::_depositor:textdepositor_"/> is Greenstone’s runtime support for institutional repositories since Greenstone 2.71. It provides the collection building work flow through web interface. <AutoText key="coredm::_depositor:textdepositor_"/> only works with the Web server, not the local server. Greenstone users belongs to the <AutoText text="all-collections-editor"/> user group have access <AutoText key="coredm::_depositor:textdepositor_"/>.</Text>
     3412<Heading>
     3413<Text id="depositor-7">Enable <AutoText key="coredm::_depositor:textdepositor_"/></Text>
     3414</Heading>
     3415<Text id="depositor-8">Enable <AutoText key="coredm::_depositor:textdepositor_"/> involves two steps: first we need to install a Web Server (Apache) and configure Greenstone to use the Web Server instead of local server; then we can enable <AutoText key="coredm::_depositor:textdepositor_"/>.</Text>
     3416<NumberedItem>
     3417<Text id="depositor-apache">We are going to use the Apache HTTP Server as the Web Server. Apache is an open source HTTP server developed by The Apache Software Foundation. It can be downloaded from <Link url="http://httpd.apache.org/download.cgi">the Apache Server website</Link>. <Link url="http://wiki.greenstone.org/wiki/index.php/Setting_up_an_Apache_Web_Server_for_Greenstone_2_Walkthrough">This page</Link> in GreenstoneWiki provides a detailed walkthrough of how to install Apache on Linux, MacOS and Windows, and configure Greenstone to work with Apache. Please follow this page unless you have already configured Greenstone with a Web Server.</Text>
     3418<Text id="depositor-access">Note: You might need to set permissions for the <Path>GSDLHOME &rarr; tmp</Path> and <Path>GSDLHOME &rarr; collect</Path> or <Path>GSDLHOME &rarr; collect &rarr; your_accessible_collection</Path> directory.</Text>
     3419</NumberedItem>
     3420<NumberedItem>
     3421<Text id="depositor-enable">Now suppose we have already installed Apache and have configured Greenstone to use the Apache Web server. In Greenstone <AutoText key="coredm::_depositor:textdepositor_"/> is disabled by default. To enable it, edit the file <Path>GSDLHOME &rarr; etc &rarr; main.cfg</Path>. Look for the "depositor" line, and change <i>disabled</i> to <i>enabled</i>.</Text>
     3422<Text id="user-group">There is one more thing need to be done here. By default only users from the <AutoText text="all-collections-editor"/> user group have access to <AutoText key="coredm::_depositor:textdepositor_"/> so we need to add the <AutoText text="admin"/> account, which we are going to use, to this group. To do this, we need the <AutoText text="Maintenance and Administration"/> facility, which is also disabled by default. To enable it, look for the "status" line in <Path>main.cfg</Path> file and change <i>disabled</i> to <i>enabled</i>.</Text>
     3423</NumberedItem>
     3424<NumberedItem>
     3425<Text id="depositor-win">If we are on a Windows machine, restart the Greenstone library.</Text>
     3426</NumberedItem>
     3427<NumberedItem>
     3428<Text id="change-group">Now we change the group membership of the <AutoText text="admin"/> account. Go to the Greenstone library home page. Two new buttons appears right below <AutoText key="coredm::_gli:textgli_"/> button, named <AutoText key="coredm::_depositor:textdepositor_"/> and <AutoText key="coredm::_home:textadmin_"/> respectively. Click <AutoText key="coredm::_home:textadmin_"/> button, click the <AutoText key="auxdm::_status:textlistusers_"/> link on the left under <AutoText key="auxdm::_status:textusermanage_"/> section. Sign in and you will see a list of all the registered accounts in Greenstone library. At the end of each entry there are two links: <AutoText key="auxdm::_userslistusers:textedituser_"/> and <AutoText key="auxdm::_userslistusers:textdeleteuser_"/>. Click <AutoText key="auxdm::_userslistusers:textedituser_"/> and we will see more detailed information about the current user account. Add <AutoText text="all-collections-editor"/> at the end of the <AutoText key="auxdm::_userslistusers:textgroups_"/> and make it read:</Text>
     3429<Format>
     3430administrator,colbuilder,all-collections-editor
     3431</Format>
     3432<Text id="back">Click <AutoText text="submit"/>. Click the <AutoText key="auxdm::_status:textreturnhome_"/> link on the left side and return to the Greenstone home page.</Text>
     3433</NumberedItem>
     3434<Heading>
     3435<Text id="depositor-10">Use the Depositor to do incremental addition</Text>
     3436</Heading>
     3437<NumberedItem>
     3438<Text id="depositor-11">On the Greenstone library home page, click <AutoText key="coredm::_depositor:textdepositor_"/> button. Sign in with the <AutoText text="admin"/> account and you will see a drop-down selection list of all the available collections. Select <b>Demo Lucene</b> from the list.</Text>
     3439</NumberedItem>
     3440<NumberedItem>
     3441<Text id="depositor-12">The next page asks to fill in the metadata fields &mdash; <AutoText key="coredm::_Global:textTitle_"/>, <AutoText key="coredm::_Global:textOrganization_"/>, <AutoText key="coredm::_Global:textSubject_"/>, <AutoText key="coredm::_Global:textKeyword_"/> and <AutoText key="coredm::_Global:textLanguage_"/>. These metadata fields are from the <b>Development Library Subset</b> (DLS) metadata set, which is the metadata set used in the <b>Demo Luecene</b> collection. In order to ensure the new document will be displayed in the classifiers, next we will specify these metadata for the new document.</Text>
     3442<Comment>
     3443<Text id="">However, the default metadata fields to be displayed here are the <AutoText key="coredm::_Global:textTitle_"/>, <AutoText key="coredm::_Global:textCreator_"/> and <AutoText key="coredm::_Global:textDescription_"/> from the <b>Dublin Core Metadata Set</b>. You can customize which metadata fields are required for items added through <AutoText key="coredm::_depositor:textdepositor_"/> in <AutoText key="glidict::CDM.GUI.DepositorMetadata"/> section on the <AutoText key="glidict::GUI.Format"/> panel in Greenstone Librarian Interface.</Text>
     3444</Comment>
     3445<Text id="depositor-intro">We are going to depositor this file: <Path>sample_files &rarr; demo_NewFiles &rarr; r9006e.htm</Path>. Double click <Path>r9006e.htm</Path> and have a look at its content. Suppose we already have the values for these metadata fields.</Text>
     3446<Text id="depositor-meta1">Type in the <AutoText key="coredm::_Global:textTitle_"/> filed:</Text>
     3447<Format>Selected guidelines for the management of records and archives: a RAMP reader (r9006e)</Format>
     3448<Text id="depositor-meta2">In the <AutoText key="coredm::_Global:textOrganization_"/> field, type <Format>UNESCO</Format></Text>
     3449<Text id="depositor-meta3">In the <AutoText key="coredm::_Global:textSubject_"/> field, type: </Text>
     3450<Format>Communication, Information and Documentation|Records and Archives Management Programme (RAMP) of  UNESCO, Archive Management</Format>
     3451<Text id="depositor-meta4">In <AutoText key="coredm::_Global:textKeyword_"/> field, type: </Text>
     3452<Format>manage records and archives</Format>
     3453<Text id="depositor-meta5">Finally in the <AutoText key="coredm::_Global:textLanguage_"/> field, type: <Format>English</Format></Text>
     3454<Text id="depositor-meta6">(You can copy these metadata values across from the <Path>sample_files &rarr; demo_NewFiles &rarr; r9006e-metadata.txt</Path>).</Text>
     3455</NumberedItem>
     3456<NumberedItem>
     3457<Text id="depositor-13">Click the <AutoText key="auxdm::_depositor:textintro_"/> button. Click <b>Browse...</b> button and select <Path>sample_files &rarr; demo &rarr; new &rarr; r9006e.htm</Path>, click <AutoText key="auxdm::_depositor:textconfirm_"/> button and check the document has been uploaded successfully.</Text>
     3458</NumberedItem>
     3459<NumberedItem>
     3460<Text id="depositor-15">Click <AutoText key="auxdm::_depositor:textbild_"/> button and wait for the process being finished. You will see the <AutoText key="auxdm::_wizard:textbildsuc_"/> message if the collection has been built successfully or error messages if something goes wrong. </Text>
     3461</NumberedItem>
     3462<NumberedItem>
     3463<Text id="depositor-16">Click <AutoText key="auxdm::_wizard:textview_"/> to preview the newly built collection and check out the newly added document is displayed correctly. For example, in the <b>organizations</b> classifier you will find a new bookshelf named <AutoText text="UNESCO"/> has been created, and click it will show the new document.</Text>
     3464</NumberedItem>
     3465<Heading>
     3466<Text id="depositor-17">Batch addition with the Depositor</Text>
     3467</Heading>
     3468<NumberedItem>
     3469<Text id="depositor-18"><AutoText key="coredm::_depositor:textdepositor_"/> also supports batch addition of new documents. This is achieved by zipping the new documents (together with their metadata files) first and upload/deposit the zip file. Please note that the collection must have <AutoText text="ZIPPlugin"/> in order to be able process the uploaded zip file, otherwise you need to add the <AutoText text="ZIPPlugin"/> first in Librarian Interface.</Text>
     3470</NumberedItem>
     3471<NumberedItem>
     3472<Text id="depositor-19">Because the <b>Demo Lucene</b> collection doesn't have <AutoText text="ZIPPlugin"/> yet, so we change this first. Open the <b>Demo Lucene</b> collection in the Greenstone Librarian Interface. Go to the <AutoText key="glidict::CDM.GUI.Plugins"/> section on the <AutoText key="glidict::GUI.Design"/> panel. Add <AutoText text="ZIPPlugin"/> from the <AutoText key="glidict::CDM.PlugInManager.PlugIn"/> drop down list and close the Greenstone Librarian Interface.</Text>
     3473</NumberedItem>
     3474<NumberedItem>
     3475<Text id="depositor-20">Go to the Greenstone's home page and click the <AutoText key="auxdm::_depositor:textbild_"/> button. Log in and select <b>Demo Lucene</b> from the list.</Text>
     3476</NumberedItem>
     3477<NumberedItem>
     3478<Text id="depositor-zip1">Leave the metadata fields as blank because the zip file we are addding contains a <AutoText text="metadata.xml"/> file which specifies these metadata values. Click the <AutoText key="auxdm::_depositor:textintro_"/> button, select <Path>sample_files &rarr; demo_NewFiles &rarr; new_files.zip</Path>, which contains two new HTML documents and a <AutoText text="metadata.xml"/> file. Click <AutoText key="auxdm::_depositor:textconfirm_"/> and then the <AutoText key="auxdm::_depositor:textbild_"/> button.</Text>
     3479</NumberedItem>
     3480<NumberedItem>
     3481<Text id="depositor-21">After the building is finished, click <AutoText key="auxdm::_wizard:textview_"/> to preview the collection. On the collection's home page, it says the collection now contains 14 documents. Check the <b>titles</b> classifier for the new documents <Format>Above and beyond</Format> and <Format>Utilization and construction of pit silos</Format> have been added successfully.</Text>
     3482</NumberedItem>
     3483<Text id="depositor-22">A major benefit of using <AutoText key="coredm::_depositor:textdepositor_"/> is that user can upload documents and metadata remotely, without having to have Greenstone installed at the client end. Actually, <AutoText key="coredm::_depositor:textdepositor_"/> is a tool for remote data input, which means you can also deposit items to collections built with MG or MGPP indexer. The difference is that MG and MGPP indexer needs to rebuild the index after adding a new item while the Lucene indexer doesn't need to.</Text>
    33213484</Content>
    33223485</Tutorial>
Note: See TracChangeset for help on using the changeset viewer.