Changeset 11642


Ignore:
Timestamp:
2006-04-11T17:22:37+12:00 (18 years ago)
Author:
kjdon
Message:

modified this to get strings form various dictionaries and files - using AutoText tag

File:
1 edited

Legend:

Unmodified
Added
Removed

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

    r11578 r11642  
    105105</NumberedItem>
    106106<NumberedItem>
    107 <Text id="0114">You can return to the currently selected page of document titles by clicking the <b>book icon </b>next to the title of the book at the top of the table of contents (this signifies closing the book). You also get to the document titles using <b>titles a-z</b> in the navigation bar, in this case to the titles beginning with A-D.</Text>
     107<Text id="0114">You can return to the currently selected page of document titles by clicking the <b>book icon</b> next to the title of the book at the top of the table of contents (this signifies closing the book). You also get to the document titles using <b>titles a-z</b> in the navigation bar, in this case to the titles beginning with A-D.</Text>
    108108<Comment>
    109109<Text id="0115">If the table of contents is open at the top level&mdash;showing all the chapters&mdash;then clicking <b>Expand Document or Chapter</b> expands the full document. For long documents, which take some time to load in, Greenstone seeks confirmation for this action: clicking 'continue' loads the full document.</Text>
    … …  
    120120</NumberedItem>
    121121<NumberedItem>
    122 <Text id="0119">In the query box under <b>Search for chapters in any language which contain some of the words</b>,<b> </b>enter the term <b>gender</b> then click <b>&lt;Begin Search&gt;</b>.</Text>
     122<Text id="0119">In the query box under <b>Search for chapters in any language which contain some of the words</b>,<b></b> enter the term <b>gender</b> then click <b>&lt;Begin Search&gt;</b>.</Text>
    123123<Comment>
    124124<Text id="0120">After a short pause, the web browser loads a fresh page showing the results of the search.</Text>
    … …  
    126126</NumberedItem>
    127127<NumberedItem>
    128 <Text id="0121">Click the <b>page icon </b>for the <b>first matching document</b> in the result set (</Text>
     128<Text id="0121">Click the <b>page icon</b> for the <b>first matching document</b> in the result set (</Text>
    129129<Text id="0122"><i>Five Year Implementation Review of the Vienna Declaration and Programme of Action</i>) to view the document. Because the search was at the chapter level, you are taken directly to the matching chapter within the document.</Text>
    130130</NumberedItem>
    … …  
    279279</NumberedItem>
    280280<NumberedItem>
    281 <Text id="0163">Click the collection icon <b>Digital Libraries in Education </b>at the top left. This takes you back to the collection's <b>about</b> page.</Text>
     281<Text id="0163">Click the collection icon <b>Digital Libraries in Education</b> at the top left. This takes you back to the collection's <b>about</b> page.</Text>
    282282<Text id="0164">Beneath the access bar on the collection's about page is a search box (just the same as the one that appears on the search page), a description of the collection under the heading <b>About this collection</b>, and instructions on how to find information in this collection.</Text>
    283283<Text id="0165">Above the access bar is the collection's icon, saying <b>Digital Libraries in Education</b>. On the right is an icon saying <b>about</b>, above which are three buttons, <b>home</b>, <b>help</b>, and <b>preferences</b>.</Text>
    … …  
    435435</Bullet>
    436436</BulletList>
    437 <Text id="0218">To invoke the Greenstone Reader's interface, go to the <i>Greenstone Digital Library Software </i>item under <i>Programs</i> on the Windows <i>Start</i> menu and select <i>Greenstone Digital Library</i>. To invoke the Librarian interface, go to the same item and select <i>Greenstone Librarian Interface</i>.</Text>
     437<Text id="0218">To invoke the Greenstone Reader's interface, go to the <i>Greenstone Digital Library Software</i> item under <i>Programs</i> on the Windows <i>Start</i> menu and select <i>Greenstone Digital Library</i>. To invoke the Librarian interface, go to the same item and select <i>Greenstone Librarian Interface</i>.</Text>
    438438<Heading>
    439439<Text id="0219">Installing ImageMagick on a Windows system</Text>
    … …  
    549549</Comment>
    550550<NumberedItem>
    551 <Text id="0252x">To enable a new language, edit the file <Path>greenstone\etc\main.cfg</Path>. Look for the appropriate "Language" line, and uncomment it (i.e. remove the # from the start). Check that the required encoding is also enabled.</Text>
    552 <Text id="0252w">For example, suppose that we want to enable Turkish. The Language line for Turkish looks like:</Text>
     551<Text id="0252x">To enable a new language, edit the file <Path>greenstone &rarr;etc &rarr;main.cfg</Path>. Look for the appropriate <AutoText text="Language" type="quoted"/> line, and uncomment it (i.e. remove the # from the start). Check that the required encoding is also enabled.</Text>
     552<Text id="0252w">For example, suppose that we want to enable Turkish. The <AutoText text="Language" type="quoted"/> line for Turkish looks like:</Text>
    553553<Format>#Language shortname=tr longname=Turkish default_encoding=windows-1254</Format>
    554554<Text id="0252v">To enable it, we remove the #, i.e. make it look like:</Text>
    … …  
    573573</NumberedItem>
    574574<NumberedItem>
    575 <Text id="1252e">Enable the use of the old-style macros by editing <Path>greenstone\etc\main.cfg</Path>: replace <i>nav_css.dm</i> with <i>nav_ns4.dm</i> in the <i>macrofiles</i> list.</Text>
     575<Text id="1252e">Enable the use of the old-style macros by editing <Path>greenstone &rarr; etc &rarr; main.cfg</Path>: replace <AutoText text="nav_css.dm" type="quoted"/> with <AutoText text="nav_ns4.dm" type="quoted"/> in the <AutoText text="macrofiles" type="quoted"/> list.</Text>
    576576</NumberedItem>
    577577<NumberedItem>
    … …  
    588588<Content>
    589589<Comment>
    590 <Text id="0254">You will need some HTML files, such as those in the hobbits folder in sample_files.</Text>
     590<Text id="0254">You will need some HTML files, such as those in the <Path>hobbits</Path> folder in <Path>sample_files</Path>.</Text>
    591591</Comment>
    592592<NumberedItem>
    … …  
    601601<NumberedItem>
    602602<Text id="0257">Start a new collection within the Librarian Interface:</Text>
    603 <Text id="0258"><Menu>File &rarr; New</Menu></Text>
     603<Menu><AutoText key="glidict::Menu.File"/> &rarr; <AutoText key="glidict::Menu.File_New"/></Menu>
    604604</NumberedItem>
    605605<NumberedItem>
    … …  
    610610<Text id="0261b">Description of Content: A collection about hobbits.</Text>
    611611</Indent>
    612 <Text id="0262">Leave the setting for <b>Base this collection on:</b> at its default <b>New Collection,</b> and click <b>&lt;OK&gt;</b>.</Text>
    613 </NumberedItem>
    614 <NumberedItem>
    615 <Text id="0263">Another window pops up, from which you select the metadata set (or sets) to use. This is discussed in other exercises. For now, select <b>Dublin Core Metadata Element Set Version 1.1 </b>followed by <b>&lt;OK&gt;</b>.</Text>
     612<Text id="0262">Leave the setting for <AutoText key="glidict::NewCollectionPrompt.Base_Collection"/> at its default: <AutoText key="glidict::NewCollectionPrompt.NewCollection"/>, and click <AutoText key="glidict::General.OK" type="button"/>.</Text>
     613</NumberedItem>
     614<NumberedItem>
     615<Text id="0263">Another window pops up, from which you select the metadata set (or sets) to use. This is discussed in other exercises. For now, select <b>Dublin Core Metadata Element Set Version 1.1</b> followed by <AutoText key="glidict::General.OK" type="button"/>.</Text>
    616616<Comment>
    617617<Text id="0263a">If this is the first time you have opened a collection in the Librarian Interface, two popup progress bars will appear, to show progress while loading plugins and classifiers.</Text>
    … …  
    619619</NumberedItem>
    620620<NumberedItem>
    621 <Text id="0264">Next you must gather together the files that will constitute the collection. A suitable set has been prepared ahead of time in <i>sample_files</i> in the folder <i>hobbits</i>. Using the left-hand side of the Librarian Interface's <b>Gather</b> panel, interactively navigate to the <i>sample_files</i> folder.</Text>
    622 </NumberedItem>
    623 <NumberedItem>
    624 <Text id="0265">Now drag the <i>hobbits</i> folder from the left-hand side and drop it on the right. The progress bar at the bottom shows some activity. Gradually, duplicates of all the files will appear in the collection panel.</Text>
     621<Text id="0264">Next you must gather together the files that will constitute the collection. A suitable set has been prepared ahead of time in <Path>sample_files</Path> in the folder <Path>hobbits</Path>. Using the left-hand side of the Librarian Interface's <AutoText key="glidict::GUI.Gather"/> panel, interactively navigate to the <Path>sample_files</Path> folder.</Text>
     622</NumberedItem>
     623<NumberedItem>
     624<Text id="0265">Now drag the <Path>hobbits</Path> folder from the left-hand side and drop it on the right. The progress bar at the bottom shows some activity. Gradually, duplicates of all the files will appear in the collection panel.</Text>
    625625<Comment>
    626626<Text id="0266">You can inspect the files that have been copied by double-clicking on the folder in the right-hand side.</Text>
    … …  
    628628</NumberedItem>
    629629<NumberedItem>
    630 <Text id="0267">Since this is our first collection, we won't complicate matters by manually assigning metadata or altering the collection's design. Instead we rely on default behaviour. So pass directly to the <b>Create</b> panel by clicking the <b>Create </b>tab.</Text>
    631 </NumberedItem>
    632 <NumberedItem>
    633 <Text id="0268">To start building the collection, click the <b>&lt;Build Collection&gt;</b> button.</Text>
    634 </NumberedItem>
    635 <NumberedItem>
    636 <Text id="0269">Once the collection has built successfully, a window pops up to confirm this. Click <b>&lt;OK&gt;</b>.</Text>
    637 </NumberedItem>
    638 <NumberedItem>
    639 <Text id="0270">Click the <b>&lt;Preview Collection&gt;</b> button to look at the end result. This loads the relevant page into your web browser (starting it up if necessary). Look around the collection and learn about Hobbits!</Text>
    640 </NumberedItem>
    641 <NumberedItem>
    642 <Text id="0271">Back in the Librarian Interface, click the <b>Enrich</b> tab to view the metadata associated with the documents in the collection.</Text>
    643 </NumberedItem>
    644 <NumberedItem>
    645 <Text id="0272">Presently there is no manually assigned metadata, but the act of building the collection has extracted metadata from the documents. Double click the <i>hobbits</i> folder to expand its content. Then single-click <i>bilbo.html</i> to display all its metadata in the right-hand side of the panel. The initial fields, starting "dc.", are empty. These are Dublin Core metadata fields (we asked you to include this metadata set when the collection was initially formed) for manually entered data.</Text>
    646 </NumberedItem>
    647 <NumberedItem>
    648 <Text id="0273">Use the scroll bar on the extreme right to view the bottom part of the list. There you will see fields starting "ex." that express the extracted metadata: for example <i>ex.Title</i>, based on the text within the HTML Title tags, and <i>ex.Language</i>, the document's language (represented using the ISO standard 2-letter mnemonic) which Greenstone determines by analysing the document's text.</Text>
    649 </NumberedItem>
    650 <NumberedItem>
    651 <Text id="0274">Close the collection by clicking <Menu>File &rarr; Close</Menu>. This automatically saves the collection to disk.</Text>
     630<Text id="0267">Since this is our first collection, we won't complicate matters by manually assigning metadata or altering the collection's design. Instead we rely on default behaviour. So pass directly to the <AutoText key="glidict::GUI.Create"/> panel by clicking its tab.</Text>
     631</NumberedItem>
     632<NumberedItem>
     633<Text id="0268">To start building the collection, click the <AutoText key="glidict::CreatePane.Build_Collection" type="button"/> button.</Text>
     634</NumberedItem>
     635<NumberedItem>
     636<Text id="0269">Once the collection has built successfully, a window pops up to confirm this. Click <AutoText key="glidict::General.OK" type="button"/>.</Text>
     637</NumberedItem>
     638<NumberedItem>
     639<Text id="0270">Click the <AutoText key="glidict::CreatePane.Preview_Collection" type="button"/> button to look at the end result. This loads the relevant page into your web browser (starting it up if necessary). Look around the collection and learn about Hobbits!</Text>
     640</NumberedItem>
     641<NumberedItem>
     642<Text id="0271">Back in the Librarian Interface, click the <AutoText key="glidict::GUI.Enrich"/> tab to view the metadata associated with the documents in the collection.</Text>
     643</NumberedItem>
     644<NumberedItem>
     645<Text id="0272">Presently there is no manually assigned metadata, but the act of building the collection has extracted metadata from the documents. Double click the <Path>hobbits</Path> folder to expand its content. Then single-click <Path>bilbo.html</Path> to display all its metadata in the right-hand side of the panel. The initial fields, starting <AutoText text="dc." type="quoted"/>, are empty. These are Dublin Core metadata fields (we asked you to include this metadata set when the collection was initially formed) for manually entered data.</Text>
     646</NumberedItem>
     647<NumberedItem>
     648<Text id="0273">Use the scroll bar on the extreme right to view the bottom part of the list. There you will see fields starting <AutoText text="ex." type="quoted"/> that express the extracted metadata: for example <AutoText key="metadata::ex.Title"/>, based on the text within the HTML Title tags, and <AutoText key="metadata::ex.Language"/>, the document's language (represented using the ISO standard 2-letter mnemonic) which Greenstone determines by analysing the document's text.</Text>
     649</NumberedItem>
     650<NumberedItem>
     651<Text id="0274">Close the collection by clicking <Menu><AutoText key="glidict::Menu.File"/> &rarr; <AutoText key="glidict::Menu.File_Close"/></Menu>. This automatically saves the collection to disk.</Text>
    652652</NumberedItem>
    653653<Heading>
    … …  
    655655</Heading>
    656656<NumberedItem>
    657 <Text id="0278">To set up a shortcut to the source files, in the <b>Gather</b> panel navigate to the folder in your local file space that contains the files you want to use&mdash;in our case, the <i>sample_files</i> folder. Select this folder and then right-click it. Follow the instructions to set up a shortcut. Close all the folders in the file tree and you will see the shortcut to your source files in the left-hand pane of the <b>Gather</b> panel.</Text>
     657<Text id="0278">To set up a shortcut to the source files, in the <AutoText key="glidict::GUI.Gather"/> panel navigate to the folder in your local file space that contains the files you want to use&mdash;in our case, the <Path>sample_files</Path> folder. Select this folder and then right-click it. Follow the instructions to set up a shortcut. Close all the folders in the file tree and you will see the shortcut to your source files in the left-hand pane of the <AutoText key="glidict::GUI.Gather"/> panel.</Text>
    658658</NumberedItem>
    659659</Content>
    … …  
    667667<Content>
    668668<Comment>
    669 <Text id="0280">You will need some source files like those in the sample_files\Word_and_PDF folder.</Text>
     669<Text id="0280">You will need some source files like those in the <Path>sample_files &rarr; Word_and_PDF</Path> folder.</Text>
    670670</Comment>
    671671<NumberedItem>
    … …  
    676676</NumberedItem>
    677677<NumberedItem>
    678 <Text id="0287">Switch to the <b>Create</b> panel, and <b>build</b> and <b>preview</b> the collection.</Text>
     678<Text id="0287">Switch to the <AutoText key="glidict::GUI.Create"/> panel, and <b>build</b> and <b>preview</b> the collection.</Text>
    679679</NumberedItem>
    680680<NumberedItem>
    … …  
    682682</NumberedItem>
    683683<NumberedItem>
    684 <Text id="0289">Back in the Librarian Interface, click the <b>Enrich</b> tab to view the automatically extracted metadata. You will need to scroll down to see the extracted metadata, which begins with "ex.".<i> </i>The PostScript documents (<i>cluster.ps</i> and <i>langmodl.ps</i> do not have extracted titles: what appears in the <i>titles a-z </i>list is just the first few characters of the document).</Text>
     684<Text id="0289">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"/>. The PostScript documents (<Path>cluster.ps</Path> and <Path>langmodl.ps</Path> do not have extracted titles: what appears in the <i>titles a-z</i> list is just the first few characters of the document).</Text>
    685685</NumberedItem>
    686686<Heading>
    … …  
    688688</Heading>
    689689<NumberedItem>
    690 <Text id="0291">In the <b>Enrich</b> panel, manually add Dublin Core <i>dc.Title</i> metadata to one of these documents. Select <i>word03.doc</i> and double-click to open it. Copy the title of this document ("Greenstone: A comprehensive open-source digital library software system") and return to the Librarian Interface. Scroll up or down in the metadata table until you can see <b>dc.Title</b>. Click in the value box, paste in the metadata and press <b>Enter</b>. </Text>
    691 </NumberedItem>
    692 <NumberedItem>
    693 <Text id="0292">Now add <i>dc.Creator</i> information for the same document. You can add more than one value for the same field: when you press <b>Enter</b> in a metadata value field, a new empty field of the same type will be generated.</Text>
     690<Text id="0291">In the <AutoText key="glidict::GUI.Enrich"/> panel, manually add Dublin Core <AutoText key="metadata::dc.Title"/> metadata to one of these documents. Select <Path>word03.doc</Path> and double-click to open it. Copy the title of this document (<AutoText text="Greenstone: A comprehensive open-source digital library software system" type="quoted"/>) and return to the Librarian Interface. Scroll up or down in the metadata table until you can see <AutoText key="metadata::dc.Title"/>. Click in the value box, paste in the metadata and press <b>Enter</b>. </Text>
     691</NumberedItem>
     692<NumberedItem>
     693<Text id="0292">Now add <AutoText key="metadata::dc.Creator"/> information for the same document. You can add more than one value for the same field: when you press <b>Enter</b> in a metadata value field, a new empty field of the same type will be generated.</Text>
    694694</NumberedItem>
    695695<NumberedItem>
    … …  
    706706</Heading>
    707707<NumberedItem>
    708 <Text id="0296">Change to the <b>Design</b> panel, which is split into several sections. The first section <b>General</b> appears. This allows you to modify the values you provided when defining the collection, if desired. You can also brand the collection using a suitable image.</Text>
    709 </NumberedItem>
    710 <NumberedItem>
    711 <Text id="0297">Click on the &lt;<b>Browse...</b>&gt; button associated with <b>URL to about page icon</b>, and browse to the image <Path>sample_files &rarr; Word_and_PDF &rarr; wrdpdf.gif</Path> on your computer. When you select this image, Greenstone automatically generates an appropriate URL for the image. <b>Preview</b> the collection.</Text>
     708<Text id="0296">Change to the <AutoText key="glidict::GUI.Design"/> panel, which is split into several sections. The first section <AutoText key="glidict::CDM.GUI.General"/> appears. This allows you to modify the values you provided when defining the collection, if desired. You can also brand the collection using a suitable image.</Text>
     709</NumberedItem>
     710<NumberedItem>
     711<Text id="0297">Click on the <AutoText key="glidict::General.Browse" type="button"/> button associated with <AutoText key="glidict::CDM.General.Icon_Collection"/>, and browse to the image <Path>sample_files &rarr; Word_and_PDF &rarr; wrdpdf.gif</Path> on your computer. When you select this image, Greenstone automatically generates an appropriate URL for the image. <b>Preview</b> the collection.</Text>
    712712</NumberedItem>
    713713<NumberedItem>
    … …  
    720720</Heading>
    721721<NumberedItem>
    722 <Text id="0304">Now look at the <b>Document Plugins</b> section, 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 ZIPPlug, TEXTPlug, HTMLPlug, EMAILPlug, ImagePlug, ISISPlug and NULPlug plugins. To delete a plugin, select it and click &lt;<b>Remove Plugin</b>&gt;. GAPlug is required for any type of source collection and should not be removed. </Text>
     722<Text id="0304">Now look at the <AutoText key="glidict::CDM.GUI.Plugins"/> section, 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 ZIPPlug, TEXTPlug, HTMLPlug, EMAILPlug, ImagePlug, ISISPlug and NULPlug plugins. To delete a plugin, select it and click <AutoText key="glidict::CDM.PlugInManager.Remove" type="button"/>. GAPlug is required for any type of source collection and should not be removed. </Text>
    723723</NumberedItem>
    724724<Heading>
    … …  
    726726</Heading>
    727727<NumberedItem>
    728 <Text id="0306">Go to the <b>Search Types</b> section. This specifies what kind of search interface and what search indexes will be provided for the collection. Let's add a form search option. Click &lt;<b>Enable Advanced Searches</b>&gt;; this allows form searching to be added to the collection.</Text>
    729 </NumberedItem>
    730 <NumberedItem>
    731 <Text id="0307">To include "form search" as well as the default "plain search", pull down the <b>Search Types</b> menu and select <b>form</b>; then click &lt;<b>Add Search Type</b>&gt;.</Text>
     728<Text id="0306">Go to the <AutoText key="glidict::CDM.GUI.SearchTypes"/> section. This specifies what kind of search interface and what search indexes will be provided for the collection. Let's add a form search option. Click <AutoText key="glidict::CDM.SearchTypeManager.Enable"/>; this allows form searching to be added to the collection.</Text>
     729</NumberedItem>
     730<NumberedItem>
     731<Text id="0307">To include "form search" as well as the default "plain search", pull down the <AutoText key="glidict::CDM.SearchTypeManager.SearchType_Selection"/> menu and select <AutoText text="form"/>; then click <AutoText key="glidict::CDM.SearchTypeManager.Add" type="button"/>.</Text>
    732732<Text id="0308">Plain search will be the default search type as it is first in the list.</Text>
    733733</NumberedItem>
    … …  
    736736</Heading>
    737737<NumberedItem>
    738 <Text id="0310">The next step in the <b>Design</b> panel is <b>Search Indexes</b>. These specify what parts of the collection are searchable (e.g. searching by title and author). Delete the <i>ex.Title</i> and <i>ex.Source</i> indexes, which are not particularly useful, by selecting them one at a time and clicking &lt;<b>Remove Index</b>&gt;. Only the <i>text</i> index remains.</Text>
    739 </NumberedItem>
    740 <NumberedItem>
    741 <Text id="0311">Now add a Title index based on <i>dc.Title</i> by providing an <b>Index Name </b>(e.g. "Document Title") and selecting <i>dc.Title</i> from the <b>Index Source</b> box. Then click &lt;<b>Add Index</b>&gt;.</Text>
    742 </NumberedItem>
    743 <NumberedItem>
    744 <Text id="0312">You can add indexes based on any metadata. Add an index called "Authors" based on <i>dc.Creator</i> metadata.</Text>
    745 </NumberedItem>
    746 <Comment>
    747 <Text id="0313">The next two sections are <b>Partition Indexes</b> and <b>Cross-Collection Search</b>. In this exercise, we will not make any changes to these.</Text>
     738<Text id="0310">The next step in the <AutoText key="glidict::GUI.Design"/> panel is <AutoText key="glidict::CDM.GUI.Indexes"/>. These specify what parts of the collection are searchable (e.g. searching by title and author). Delete the <AutoText key="metadata::ex.Title"/> and <AutoText key="metadata::ex.Source"/> indexes, which are not particularly useful, by selecting them one at a time and clicking <AutoText key="glidict::CDM.IndexManager.Remove_Index" type="button"/>. Only the <i>text</i> index remains.</Text>
     739</NumberedItem>
     740<NumberedItem>
     741<Text id="0311">Now add a Title index based on <AutoText key="metadata::dc.Title"/> by providing an <b>Index Name</b> (e.g. "Document Title") and selecting <AutoText key="metadata::dc.Title"/> from the <b>Index Source</b> box. Then click <AutoText key="glidict::CDM.IndexManager.Add_Index" type="button"/>.</Text>
     742</NumberedItem>
     743<NumberedItem>
     744<Text id="0312">You can add indexes based on any metadata. Add an index called "Authors" based on <AutoText key="metadata::dc.Creator"/> metadata.</Text>
     745</NumberedItem>
     746<Comment>
     747<Text id="0313">The next two sections are <AutoText key="glidict::CDM.GUI.Subcollections"/> and <AutoText key="glidict::CDM.GUI.SuperCollection"/>. In this exercise, we will not make any changes to these.</Text>
    748748</Comment>
    749749<Heading>
    … …  
    751751</Heading>
    752752<NumberedItem>
    753 <Text id="0315">The <b>Browsing Classifiers</b> 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 <i>ex.Title</i> and <i>ex.Source</i> metadata. Remove both of these by selecting them in turn and clicking &lt;<b>Remove Classifier</b>&gt;.</Text>
    754 </NumberedItem>
    755 <NumberedItem>
    756 <Text id="0316">Now we add an <i>AZList</i> classifier for <i>dc.Title</i> metadata. Select <i>AZList</i> from the <b>Select classifier to add</b> drop-down list and click &lt;<b>Add Classifier</b>&gt;</Text>
    757 </NumberedItem>
    758 <NumberedItem>
    759 <Text id="0317">A popup window <b>Configuring Arguments</b> appears. Select <i>dc.Title</i> from the <b>metadata</b> drop-down list and click &lt;<b>OK</b>&gt;.</Text>
    760 </NumberedItem>
    761 <NumberedItem>
    762 <Text id="0318">Now add an <i>AZCompactList</i> classifier. Click &lt;<b>Add Classifier</b>&gt; and configure it to use <i>dc.Creator</i> metadata, with button name "Creator". Click &lt;<b>OK</b>&gt;.</Text>
    763 <Comment>
    764 <Text id="0319">The last three sections are <b>Format Features</b>, <b>Translate Text</b> and <b>Metadata Sets</b>. In this exercise, we will not make any changes to these.</Text>
    765 </Comment>
    766 </NumberedItem>
    767 <NumberedItem>
    768 <Text id="0320">Switch to the <b>Create</b> panel, and <b>build</b> and <b>preview</b> the collection.</Text>
    769 </NumberedItem>
    770 <NumberedItem>
    771 <Text id="0321">Check that all the facilities work properly. There should be three full-text indexes, called <i>text</i>, <i>Document Title</i>, and <i>Authors</i>. In the <i>titles a-z</i> list should appear all the documents to which you have assigned <i>dc.Title</i> metadata (and only those documents). In the <i>authors a­-z</i> list should appear one bookshelf for each author you have assigned as <i>dc.Creator</i>, and clicking on that bookshelf should take you to all the documents they authored.</Text>
     753<Text id="0315">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. Remove both of these by selecting them in turn and clicking <AutoText key="glidict::CDM.ClassifierManager.Remove" type="button"/>.</Text>
     754</NumberedItem>
     755<NumberedItem>
     756<Text id="0316">Now we add an <i>AZList</i> classifier for <AutoText key="metadata::dc.Title"/> metadata. Select <i>AZList</i> from the <AutoText key="glidict::CDM.ClassifierManager.Classifier"/> drop-down list and click <AutoText key="glidict::CDM.ClassifierManager.Add" type="button"/>.</Text>
     757</NumberedItem>
     758<NumberedItem>
     759<Text id="0317">A popup window <AutoText key="glidict::CDM.ArgumentConfiguration.Title"/> appears. Select <AutoText key="metadata::dc.Title"/> from the <AutoText text="metadata"/> drop-down list and click <AutoText key="glidict::General.OK" type="button"/>.</Text>
     760</NumberedItem>
     761<NumberedItem>
     762<Text id="0318">Now add an <AutoText text="AZCompactList"/> classifier. Click <AutoText key="glidict::CDM.ClassifierManager.Add" type="button"/> and configure it to use <AutoText key="metadata::dc.Creator"/> metadata, with button name "Creator". Click <AutoText key="glidict::General.OK" type="button"/>.</Text>
     763<Comment>
     764<Text id="0319">The last three sections are <AutoText key="glidict::CDM.GUI.Formats"/>, <AutoText key="glidict::CDM.GUI.Translation"/> and <AutoText key="glidict::CDM.GUI.MetadataSets"/>. In this exercise, we will not make any changes to these.</Text>
     765</Comment>
     766</NumberedItem>
     767<NumberedItem>
     768<Text id="0320">Switch to the <AutoText key="glidict::GUI.Create"/> panel, and <b>build</b> and <b>preview</b> the collection.</Text>
     769</NumberedItem>
     770<NumberedItem>
     771<Text id="0321">Check that all the facilities work properly. There should be three full-text indexes, called <i>text</i>, <i>Document Title</i>, and <i>Authors</i>. In the <i>titles a-z</i> list should appear all the documents to which you have assigned <AutoText key="metadata::dc.Title"/> metadata (and only those documents). In the <i>authors a-z</i> list should appear 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>
    772772</NumberedItem>
    773773<Comment>
    … …  
    784784<Content>
    785785<NumberedItem>
    786 <Text id="0324">Build a fresh Greenstone collection from the two files in <i>sample_files\difficult_documents.</i> Use the default collection configuration: that is, simply gather the files into a new collection, and build it.</Text>
    787 <Comment>
    788 <Text id="0325">These files are called No extractable text.pdf and Weird characters.pdf&mdash;their names hint at the problems they will cause!</Text>
     786<Text id="0324">Build a fresh Greenstone collection from the two files in <Path>sample_files &rarr; difficult_documents.</Path> Use the default collection configuration: that is, simply gather the files into a new collection, and build it.</Text>
     787<Comment>
     788<Text id="0325">These files are called <Path>No extractable text.pdf</Path> and <Path>Weird characters.pdf</Path>&mdash;their names hint at the problems they will cause!</Text>
    789789</Comment>
    790790</NumberedItem>
    … …  
    796796</Heading>
    797797<Comment>
    798 <Text id="0334">The Librarian Interface can operate in different modes. So far, you have been using the default mode, called "Librarian." </Text>
    799 </Comment>
    800 <NumberedItem>
    801 <Text id="0335">Use the <i>Preferences</i> item on the <i>File</i> menu to switch to <i>Expert</i> mode and then build the collection again. The <b>Create</b> panel looks different in Expert mode because it gives more options: locate the <b>Build Collection</b> button, near the bottom of the window, and click it. Now a message appears saying that the file could not be processed, and why.</Text>
    802 </NumberedItem>
    803 <NumberedItem>
    804 <Text id="0336">We recommend that you switch back to <i>Librarian</i> mode for subsequent exercises, to avoid confusion.</Text>
     798<Text id="0334">The Librarian Interface can operate in different modes. So far, you have been using the default mode, called <AutoText key="glidict::Preferences.Mode.Librarian"/>. </Text>
     799</Comment>
     800<NumberedItem>
     801<Text id="0335">Use the <AutoText key="glidict::Menu.File_Options"/> item on the <AutoText key="glidict::Menu.File"/> menu to switch to <AutoText key="glidict::Preferences.Mode.Expert"/> mode and then build the collection again. The <AutoText key="glidict::GUI.Create"/> panel looks different in <AutoText key="glidict::Preferences.Mode.Expert"/> mode because it gives more options: locate the <AutoText key="glidict::CreatePane.Build_Collection" type="button"/> button, near the bottom of the window, and click it. Now a message appears saying that the file could not be processed, and why.</Text>
     802</NumberedItem>
     803<NumberedItem>
     804<Text id="0336">We recommend that you switch back to <AutoText key="glidict::Preferences.Mode.Librarian"/> mode for subsequent exercises, to avoid confusion.</Text>
    805805</NumberedItem>
    806806<Heading>
    … …  
    811811</Comment>
    812812<NumberedItem>
    813 <Text id="0327">Greenstone can convert PDF files into a series of images with a corresponding file that details how they are composed into the complete document (called an <i>item</i> file). For this part of the exercise, ImageMagick also needs to be installed (see <TutorialRef id="install_greenstone"/>).</Text>
    814 </NumberedItem>
    815 <NumberedItem>
    816 <Text id="0328">In the <b>Document Plugins</b> list in the <b>Design</b> panel, double-click <b>PDFPlug </b>to pop up a window that shows its settings, and set the <b>convert_to</b> option to <i>pagedimg_gif</i>.</Text>
    817 </NumberedItem>
    818 <NumberedItem>
    819 <Text id="0329"><b>Build</b> the collection and <b>preview </b>it. Both PDF documents have been processed and divided into pages, but each page displays "This document has no text" because when converting PDF documents to images, no text is extracted.</Text>
    820 </NumberedItem>
    821 <NumberedItem>
    822 <Text id="0330">In order to view the documents properly we need to modify a format statement. In the <b>Format Features</b> section on the <b>Design</b> panel, select the <b>DocumentText</b> format statement. Replace <Format>[Text]</Format> with <Format>[srcicon]</Format> and click <b>Replace Format</b>.</Text>
    823 </NumberedItem>
    824 <NumberedItem>
    825 <Text id="0332"><b>Preview</b> the collection from the <b>Create</b> panel. (There is no need to build it). Images from the documents are now displayed instead of the extracted text. Both <i>No extractable text.pdf</i> and <i>Weird characters.pdf</i> display nicely now. </Text>
     813<Text id="0327">Greenstone can convert PDF files into a series of images with a corresponding file that details how they are composed into the complete document (called an <AutoText text="item" type="quoted"/> file). For this part of the exercise, ImageMagick also needs to be installed (see <TutorialRef id="install_greenstone"/>).</Text>
     814</NumberedItem>
     815<NumberedItem>
     816<Text id="0328">In the <AutoText key="glidict::CDM.GUI.Plugins"/> list in the <AutoText key="glidict::GUI.Design"/> panel, double-click <AutoText text="PDFPlug"/> to pop up a window that shows its settings, and set the <AutoText text="convert_to"/> option to <AutoText text="pagedimg_gif"/>.</Text>
     817</NumberedItem>
     818<NumberedItem>
     819<Text id="0329"><b>Build</b> the collection and <b>preview</b> it. Both PDF documents have been processed and divided into pages, but each page displays <AutoText key="perlmodules::BasPlug.dummy_text" type="quoted"/> because when converting PDF documents to images, no text is extracted.</Text>
     820</NumberedItem>
     821<NumberedItem>
     822<Text id="0330">In order to view the documents properly we need to modify a format statement. In the <AutoText key="glidict::CDM.GUI.Formats"/> section on the <AutoText key="glidict::GUI.Design"/> panel, select the <AutoText text="DocumentText"/> format statement. Replace <Format>[Text]</Format> with <Format>[srcicon]</Format> and click <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/>.</Text>
     823</NumberedItem>
     824<NumberedItem>
     825<Text id="0332"><b>Preview</b> the collection from the <AutoText key="glidict::GUI.Create"/> panel. (There is no need to build it). Images from the documents are now displayed instead of the extracted text. Both <Path>No extractable text.pdf</Path> and <Path>Weird characters.pdf</Path> display nicely now. </Text>
    826826</NumberedItem>
    827827</Content>
    … …  
    835835<Content>
    836836<NumberedItem>
    837 <Text id="0338">Start a new collection (<Menu>File &rarr; New</Menu>) called <b>backdrop</b>. Fill out the fields with appropriate information. For <b>Base this collection on</b>, select the item <b>Simple image collection (image-e)</b> from the pull-down menu.</Text>
     837<Text id="0338">Start a new collection (<Menu><AutoText key="glidict::Menu.File"/> &rarr; <AutoText key="glidict::Menu.File_New"/></Menu>) called <b>backdrop</b>. Fill out the fields with appropriate information. For <AutoText key="glidict::NewCollectionPrompt.Base_Collection"/>, select the item <b>Simple image collection (image-e)</b> from the pull-down menu.</Text>
    838838<Comment>
    839839<Text id="0340">Greenstone does not ask you to choose a metadata set because the new collection inherits whatever is used by the base collection.</Text>
    … …  
    841841</NumberedItem>
    842842<NumberedItem>
    843 <Text id="0341">Copy the images provided in <i>sample_files\images</i> into your newly-formed collection.</Text>
    844 </NumberedItem>
    845 <NumberedItem>
    846 <Text id="0342">Change to the <b>Create </b>panel and <b>build</b> the collection.</Text>
     843<Text id="0341">Copy the images provided in <Path>sample_files &rarr; images</Path> into your newly-formed collection.</Text>
     844</NumberedItem>
     845<NumberedItem>
     846<Text id="0342">Change to the <AutoText key="glidict::GUI.Create"/> panel and <b>build</b> the collection.</Text>
    847847</NumberedItem>
    848848<NumberedItem>
    … …  
    850850</NumberedItem>
    851851<NumberedItem>
    852 <Text id="0344">Click <i>browse</i> in the navigation bar to view a list of the photos ordered by filename and presented as a thumbnail accompanied by some basic data about the image. The structure of this collection is the same as <b>Simple image collection (image-e)</b>, but the content is different.</Text>
    853 </NumberedItem>
    854 <NumberedItem>
    855 <Text id="0345">Change to the <b>Enrich</b> panel and view the extracted metadata for <i>Ascent.jpg</i>.</Text>
     852<Text id="0344">Click <AutoText key="coredm::_Global:labelBrwse_"/> in the navigation bar to view a list of the photos ordered by filename and presented as a thumbnail accompanied by some basic data about the image. The structure of this collection is the same as <b>Simple image collection (image-e)</b>, but the content is different.</Text>
     853</NumberedItem>
     854<NumberedItem>
     855<Text id="0345">Change to the <AutoText key="glidict::GUI.Enrich"/> panel and view the extracted metadata for <Path>Ascent.jpg</Path>.</Text>
    856856</NumberedItem>
    857857<Comment>
    … …  
    862862</Heading>
    863863<NumberedItem>
    864 <Text id="0348">The collection (image-e) on which <b>backdrop</b> is based uses only extracted metadata. To add another metadata set, go to the <b>Design</b> panel of the Librarian Interface and click <b>Metadata Sets</b> in the list on the left (the last one). Then click  &lt;<b>Add Metadata Set...</b>&gt; (lower left button).</Text>
    865 </NumberedItem>
    866 <NumberedItem>
    867 <Text id="0349">In the window that pops up, select <b>dublin.mds </b>and click &lt;<b>Add Metadata Set</b>&gt;.</Text>
     864<Text id="0348">The collection (image-e) on which <b>backdrop</b> is based uses only extracted metadata. To add another metadata set, go to the <AutoText key="glidict::GUI.Design"/> panel of the Librarian Interface and click <AutoText key="glidict::CDM.GUI.MetadataSets"/> in the list on the left (the last one). Then click  <AutoText key="glidict::CDM.MetadataSetManager.Add" type="button"/> (lower left button).</Text>
     865</NumberedItem>
     866<NumberedItem>
     867<Text id="0349">In the window that pops up, select <AutoText text="dublin.mds"/> and click <AutoText key="glidict::CDM.MetadataSetManager.Chooser.Add" type="button"/>.</Text>
    868868</NumberedItem>
    869869<Heading>
    … …  
    871871</Heading>
    872872<NumberedItem>
    873 <Text id="0351">Now switch to the <b>Enrich</b> panel by clicking this tab. The metadata for each file now shows the Dublin core <i>dc.</i> fields as well as the extracted <i>ex.</i> fields.</Text>
    874 </NumberedItem>
    875 <NumberedItem>
    876 <Text id="0352">We work with just the first three files (<i>Ascent.jpg</i>, <i>Autumn.jpg </i>and <i>Azul.jpg</i>) to get a flavour of what is possible. First, set each file's <b>dc.Title</b> field to be the same as its filename but without the filename extension.</Text>
    877 </NumberedItem>
    878 <NumberedItem>
    879 <Text id="0353">Click on <b><i>Ascent.jpg </i></b>so its metadata fields are available, then click on its <b>dc.Title </b>field on the right-hand side. Type in <b>Ascent</b>, and click <b>Enter</b>.</Text>
    880 </NumberedItem>
    881 <Comment>
    882 <Text id="0354">The <b>Existing values for ...</b>box will become more useful when more entries have been added.</Text>
    883 </Comment>
    884 <NumberedItem>
    885 <Text id="0355">Repeat the process for <b>Autumn.jpg </b>and <b>Azul.jpg</b>.</Text>
     873<Text id="0351">Now switch to the <AutoText key="glidict::GUI.Enrich"/> panel by clicking this tab. The metadata for each file now shows the Dublin core <AutoText text="dc."/> fields as well as the extracted <AutoText text="ex."/> fields.</Text>
     874</NumberedItem>
     875<NumberedItem>
     876<Text id="0352">We work with just the first three files (<Path>Ascent.jpg</Path>, <Path>Autumn.jpg</Path> and <Path>Azul.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>
     877</NumberedItem>
     878<NumberedItem>
     879<Text id="0353">Click on <Path>Ascent.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>Ascent</b>, and click <b>Enter</b>.</Text>
     880</NumberedItem>
     881<Comment>
     882<Text id="0354">The <AutoText key="glidict::EnrichPane.ExistingValues" args="..."/> box will become more useful when more entries have been added.</Text>
     883</Comment>
     884<NumberedItem>
     885<Text id="0355">Repeat the process for <b>Autumn.jpg</b> and <b>Azul.jpg</b>.</Text>
    886886</NumberedItem>
    887887<Comment>
    … …  
    892892</Heading>
    893893<NumberedItem>
    894 <Text id="0358">Go to the <b>Design</b> panel and select <b>Format Features</b> from the left-hand list. Leave the feature selection controls at their default values, so that <b>Choose Feature</b> remains blank and <b>VList</b> is selected as the <b>Affected Component</b>. In the <b>HTML Format String</b>, edit the text as follows:</Text>
     894<Text id="0358">Go to the <AutoText key="glidict::GUI.Design"/> panel and select <AutoText key="glidict::CDM.GUI.Formats"/> from the left-hand list. Leave the feature selection controls at their default values, so that <AutoText key="glidict::CDM.FormatManager.Feature"/> remains blank and <AutoText text="VList" /> is selected as the <AutoText key="glidict::CDM.FormatManager.Part"/>. In the <AutoText key="glidict::CDM.FormatManager.Editor"/>, edit the text as follows:</Text>
    895895<Indent>
    896896<Text id="0359">Change "_ImageName_:" to "Title:" <br/> Change "[Image]" to "[dc.Title]"</Text>
    … …  
    901901</NumberedItem>
    902902<NumberedItem>
    903 <Text id="0361">Next click <b>&lt;Replace Format&gt;</b>. The first of the above changes alters the fragment of text that appears to the right of the thumbnail image, the second alters the item of metadata that follows it.</Text>
    904 </NumberedItem>
    905 <NumberedItem>
    906 <Text id="0362">Go to the <b>Create</b> panel and click <b>&lt;Build Collection&gt;</b>. Now <b>preview </b>the collection. When you click on <b>browse</b> in the navigation bar the presentation has changed to "Title: Ascent" and so on.</Text>
     903<Text id="0361">Next click <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/>. The first of the above changes alters the fragment of text that appears to the right of the thumbnail image, the second alters the item of metadata that follows it.</Text>
     904</NumberedItem>
     905<NumberedItem>
     906<Text id="0362">Go to the <AutoText key="glidict::GUI.Create"/> panel and click <AutoText key="glidict::CreatePane.Build_Collection" type="button"/>. Now <b>preview</b> the collection. When you click on <AutoText key="coredm::_Global:labelBrwse_"/> in the navigation bar the presentation has changed to "Title: Ascent" and so on.</Text>
    907907</NumberedItem>
    908908<Comment>
    … …  
    916916</Heading>
    917917<NumberedItem>
    918 <Text id="0366">Thumbnail images are created by the <i>ImagePlug</i> plug-in, so we need to access its configuration settings. To do this, switch to the <b>Design</b> panel and select <b>Document Plugins</b> from the list on the left. Double-click <b>plugin ImagePlug</b> to pop up a window that shows its settings. (Alternatively, select <b>ImagePlug </b>with a single click and then click <b>&lt;Configure Plugin...&gt;</b> further down the screen). Currently all options are off, so standard defaults are used. Select <b>thumbnailsize</b>, set it to <b>50</b>, and click <b>&lt;OK&gt;</b>.</Text>
    919 </NumberedItem>
    920 <NumberedItem>
    921 <Text id="0367"><b>Build </b>and <b>preview </b>the collection.</Text>
    922 </NumberedItem>
    923 <NumberedItem>
    924 <Text id="0368">Once you have seen the result of the change, return to the <b>Design</b> panel, select the configuration options for <i>ImagePlug</i>, and switch the thumbnail size option off so that the thumbnail reverts to its normal size when the collection is re-built.</Text>
    925 </NumberedItem>
    926 <Comment>
    927 <Text id="0369">Now add metadata that describes the photos in the collection. Again, for illustration, we focus on the first three images (Ascent.jpg, Autumn.jpg and Azul.jpg).</Text>
     918<Text id="0366">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="plugin ImagePlug"/> to pop up a window that shows its settings. (Alternatively, select <AutoText text="plugin 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>
     919</NumberedItem>
     920<NumberedItem>
     921<Text id="0367"><b>Build</b> and <b>preview</b> the collection.</Text>
     922</NumberedItem>
     923<NumberedItem>
     924<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>
     925</NumberedItem>
     926<Comment>
     927<Text id="0369">Now add metadata that describes the photos in the collection. Again, for illustration, we focus on the first three images (<Path>Ascent.jpg</Path>, <Path>Autumn.jpg</Path> and <Path>Azul.jpg</Path>).</Text>
    928928</Comment>
    929929<Heading>
    … …  
    931931</Heading>
    932932<NumberedItem>
    933 <Text id="0371">Switch to the <b>Enrich</b> panel and select <i>Ascent.jpg</i>. We'll store our description in the <b>dc.Description </b>metadata element, so select it now in the right-hand panel.</Text>
     933<Text id="0371">Switch to the <AutoText key="glidict::GUI.Enrich"/> panel and select <Path>Ascent.jpg</Path>. We'll store our description in the <AutoText key="metadata::dc.Description"/> metadata element, so select it now in the right-hand panel.</Text>
    934934</NumberedItem>
    935935<Comment>
    … …  
    937937</Comment>
    938938<NumberedItem>
    939 <Text id="0373">Back in the Librarian Interface enter the text <b>Moon rising over mountain landscape </b>as the <b>dc.Description </b>field's value and click <b>Enter</b> to have it added.</Text>
    940 </NumberedItem>
    941 <NumberedItem>
    942 <Text id="0374">Repeat this process for <i>Autumn.jpg </i>and <i>Azul.jpg</i>, adding a suitable description for each.</Text>
     939<Text id="0373">Back in the Librarian Interface enter the text <b>Moon rising over mountain landscape</b> as the <AutoText key="metadata::dc.Description"/> field's value and click <b>Enter</b> to have it added.</Text>
     940</NumberedItem>
     941<NumberedItem>
     942<Text id="0374">Repeat this process for <Path>Autumn.jpg</Path> and <Path>Azul.jpg</Path>, adding a suitable description for each.</Text>
    943943</NumberedItem>
    944944<NumberedItem>
    … …  
    946946</NumberedItem>
    947947<NumberedItem>
    948 <Text id="0376">Now update the format statement to use the new <b>dc.Description </b>metadata. Switch back to the <b>Format Features</b> section of the <b>Design </b>panel, and ensure the <b>Choose Feature</b> box is blank, and <b>VList</b> is selected in the <b>Affected Component</b> box. In the <b>HTML Format String</b>, place your cursor after the text that says</Text>
     948<Text id="0376">Now update the format statement to use the new <AutoText key="metadata::dc.Description"/> metadata. Switch back to the <AutoText key="glidict::CDM.GUI.Formats"/> section of the <AutoText key="glidict::GUI.Design"/> panel, and ensure the <AutoText key="glidict::CDM.FormatManager.Feature"/> box is blank, and <AutoText text="VList" /> is selected in the <AutoText key="glidict::CDM.FormatManager.Part"/> box. In the <AutoText key="glidict::CDM.FormatManager.Editor"/>, place your cursor after the text that says</Text>
    949949<Format>[dc.Title]&lt;br&gt;</Format>
    950950</NumberedItem>
    … …  
    954954</NumberedItem>
    955955<NumberedItem>
    956 <Text id="0378">Then click <b>&lt;Replace Format&gt;</b>.</Text>
     956<Text id="0378">Then click <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/>.</Text>
    957957</NumberedItem>
    958958<NumberedItem>
    … …  
    963963</Heading>
    964964<NumberedItem>
    965 <Text id="0381">Switch to the <b>Design</b> panel and select <b>Browsing Classifiers </b>from the left-hand list. Set the menu item for <b>Select classifier to add </b>to <b>AZList</b>; then click &lt;<b>Add Classifier...</b>&gt;.</Text>
    966 </NumberedItem>
    967 <NumberedItem>
    968 <Text id="0382">A window pops up to control the classifier's options. Set the menu item for metadata to <b>dc.Description</b> and click <b>&lt;OK&gt;</b>. Now switch to the <b>Create </b>panel, <b>build </b>the collection, and <b>preview </b>it. Choose the new <b>descriptions </b>link that appears in the navigation bar.</Text>
    969 </NumberedItem>
    970 <Comment>
    971 <Text id="0383">Only three items are shown, because only items with the relevant metadata (dc.Description in this case) appear in the list. The original browse list includes all photos in the collection because it is based on ex.Image, extracted metadata that reflects an image's filename, which is set for all images in the collection.</Text>
     965<Text id="0381">Switch to the <AutoText key="glidict::GUI.Design"/> panel and 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>
     966</NumberedItem>
     967<NumberedItem>
     968<Text id="0382">A window pops up to control the classifier's options. Set the menu item for metadata to <AutoText key="metadata::dc.Description"/> and click <AutoText key="glidict::General.OK" type="button"/>. Now switch to the <AutoText key="glidict::GUI.Create"/> panel, <b>build</b> the collection, and <b>preview</b> it. Choose the new <b>descriptions</b> link that appears in the navigation bar.</Text>
     969</NumberedItem>
     970<Comment>
     971<Text id="0383">Only three items are shown, because only items with the relevant metadata (dc.Description in this case) appear in the list. The original browse list includes all photos in the collection because it is based on <AutoText key="metadata::ex.Image"/>, extracted metadata that reflects an image's filename, which is set for all images in the collection.</Text>
    972972</Comment>
    973973<Heading>
    … …  
    975975</Heading>
    976976<NumberedItem>
    977 <Text id="0385">Switch to the <b>Design </b>panel and select <b>Search Indexes </b>from the left-hand list. Enter the text "descriptions" as the <b>Index Name</b>, select <b>dc.Description </b>and click <b>&lt;Add Index&gt;</b>.</Text>
    978 </NumberedItem>
    979 <NumberedItem>
    980 <Text id="0386">Switch to the <b>Create</b> panel, <b>build</b> the collection, then <b>preview</b> it. As an example, search for the term "mountain" in the <i>descriptions</i> index (which is the only index at this point).</Text>
     977<Text id="0385">Switch to the <AutoText key="glidict::GUI.Design"/> panel and select <AutoText key="glidict::CDM.GUI.Indexes"/> from the left-hand list. Enter the text "descriptions" as the <AutoText key="glidict::CDM.IndexManager.Index_Name"/>, select <AutoText key="metadata::dc.Description"/> and click <AutoText key="glidict::CDM.IndexManager.Add_Index" type="button"/>.</Text>
     978</NumberedItem>
     979<NumberedItem>
     980<Text id="0386">Switch to the <AutoText key="glidict::GUI.Create"/> panel, <b>build</b> the collection, then <b>preview</b> it. As an example, search for the term "mountain" in the <i>descriptions</i> index (which is the only index at this point).</Text>
    981981</NumberedItem>
    982982</Content>
    … …  
    990990<Content>
    991991<NumberedItem>
    992 <Text id="0388">Invoke the Greenstone Librarian Interface (from the Windows <i>Start</i> menu) and start a new collection called <b>tudor</b> (use the <i>File</i> menu). Fill out the pop-up dialog with appropriate values and leave <b>Dublin Core</b>, which is selected by default, as the metadata set.</Text>
    993 </NumberedItem>
    994 <NumberedItem>
    995 <Text id="0389">In the <b>Gather</b> panel, open the <i>tudor </i>folder in <i>sample_files</i>.</Text>
    996 </NumberedItem>
    997 <NumberedItem>
    998 <Text id="0390">Drag <i>englishhistory.net </i>from the left-hand side to the right to include it in your <b>tudor</b> collection.</Text>
    999 </NumberedItem>
    1000 <NumberedItem>
    1001 <Text id="0391">Switch to the <b>Create</b> panel and click <b>&lt;Build Collection&gt;</b>.</Text>
     992<Text id="0388">Invoke the Greenstone Librarian Interface (from the Windows <i>Start</i> menu) and start a new collection called <b>tudor</b> (use the <AutoText key="glidict::Menu.File"/> menu). Fill out the pop-up dialog with appropriate values and leave <b>Dublin Core</b>, which is selected by default, as the metadata set.</Text>
     993</NumberedItem>
     994<NumberedItem>
     995<Text id="0389">In the <AutoText key="glidict::GUI.Gather"/> panel, open the <Path>tudor</Path> folder in <Path>sample_files</Path>.</Text>
     996</NumberedItem>
     997<NumberedItem>
     998<Text id="0390">Drag <Path>englishhistory.net</Path> from the left-hand side to the right to include it in your <b>tudor</b> collection.</Text>
     999</NumberedItem>
     1000<NumberedItem>
     1001<Text id="0391">Switch to the <AutoText key="glidict::GUI.Create"/> panel and click <AutoText key="glidict::CreatePane.Build_Collection" type="button"/>.</Text>
    10021002</NumberedItem>
    10031003<NumberedItem>
    … …  
    10111011</Comment>
    10121012<NumberedItem>
    1013 <Text id="0395">Switch to the <b>Design</b> panel and select the <b>Document Plugins</b> section. Beside <b>plugin HTMLPlug</b> you will see <i>-smart_block</i>. 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! Select the <b>plugin HTMLPlug</b> line and click &lt;<b>Configure Plugin...&gt;</b>. A popup window appears. Scroll down the page to locate the <b>smart_block</b> option and switch it off. Click &lt;<b>OK&gt;</b>.</Text>
    1014 </NumberedItem>
    1015 <NumberedItem>
    1016 <Text id="0396">Switch to the <b>Create</b> panel and <b>build</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 <i>smart_block</i>) the HTML plug-in blocks <i>all</i> images, which is appropriate for this collection.</Text>
     1013<Text id="0395">Switch to the <AutoText key="glidict::GUI.Design"/> panel and select the <AutoText key="glidict::CDM.GUI.Plugins"/> section. 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! Select the <AutoText text="plugin HTMLPlug"/> line and click <AutoText key="glidict::CDM.PlugInManager.Configure" type="button"/>. A popup window appears. Scroll down the page to locate the <AutoText text="smart_block"/> option and switch it off. Click <AutoText key="glidict::General.OK" type="button"/>.</Text>
     1014</NumberedItem>
     1015<NumberedItem>
     1016<Text id="0396">Switch to the <AutoText key="glidict::GUI.Create"/> panel and <b>build</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>
    10171017</NumberedItem>
    10181018<Heading>
    … …  
    10201020</Heading>
    10211021<NumberedItem>
    1022 <Text id="0398">Switch to the <b>Gather</b> panel and in the right-hand side open <Path>englishhistory.net &rarr; tudor</Path>.</Text>
    1023 </NumberedItem>
    1024 <NumberedItem>
    1025 <Text id="0400">Change the <b>Show Files</b> menu for the right-hand side from <b>All Files</b> to <b>HTM &amp; HTML</b>. Notice the files displayed above are filtered accordingly, to show only files of this type.</Text>
    1026 </NumberedItem>
    1027 <NumberedItem>
    1028 <Text id="0401">Change the <b>Show Files</b> menu to <b>Images</b>. Again, the files shown above alter.</Text>
    1029 </NumberedItem>
    1030 <NumberedItem>
    1031 <Text id="0402">Now return the <b>Show Files</b> setting back to <b>All Files</b>, otherwise you may get confused later. Remember, if the <b>Gather</b> or <b>Enrich</b> panels do not seem to be showing all your files, this could be the problem.</Text>
     1022<Text id="0398">Switch to the <AutoText key="glidict::GUI.Gather"/> panel and in the right-hand side open <Path>englishhistory.net &rarr; tudor</Path>.</Text>
     1023</NumberedItem>
     1024<NumberedItem>
     1025<Text id="0400">Change the <AutoText key="glidict::Filter.Filter_Tree"/> menu for the right-hand side from <AutoText key="glidict::Filter.All_Files"/> to <AutoText key="glidict::Filter.0"/>. Notice the files displayed above are filtered accordingly, to show only files of this type.</Text>
     1026</NumberedItem>
     1027<NumberedItem>
     1028<Text id="0401">Change the <AutoText key="glidict::Filter.Filter_Tree"/> menu to <AutoText key="glidict::Filter.3"/>. Again, the files shown above alter.</Text>
     1029</NumberedItem>
     1030<NumberedItem>
     1031<Text id="0402">Now return the <AutoText key="glidict::Filter.Filter_Tree"/> setting back to <AutoText key="glidict::Filter.All_Files"/>, otherwise you may get confused later. Remember, if the <AutoText key="glidict::GUI.Gather"/> or <AutoText key="glidict::GUI.Enrich"/> panels do not seem to be showing all your files, this could be the problem.</Text>
    10321032</NumberedItem>
    10331033</Content>
    … …  
    10481048</NumberedItem>
    10491049<NumberedItem>
    1050 <Text id="0406">Choose <Menu>File &rarr; Write CD/DVD image...</Menu>, and in the popup window select the <b>tudor</b> collection as the collection to export. You can optionally name the CD-ROM; otherwise the default "collections" is used. Do so now, entering "Tudor collection" in the field for <b>CD/DVD name</b>; then click <b>&lt;Write CD/DVD image&gt;</b>.</Text>
     1050<Text id="0406">Choose <Menu><AutoText key="glidict::Menu.File"/> &rarr; <AutoText key="glidict::Menu.File_CDimage"/></Menu>, and in the popup window select the <b>tudor</b> collection as the collection to export. You can optionally name the CD-ROM; otherwise the default <AutoText text="collections" type="quoted"/> is used. Do so now, entering <AutoText text="Tudor collection" type="quoted"/> in the field for <AutoText key="glidict::WriteCDImagePrompt.CD_Name"/>; then click <AutoText key="glidict::WriteCDImagePrompt.Export" type="button"/>.</Text>
    10511051<Text id="0408">The necessary files for export are written to:</Text>
    1052 <Text id="0408a"><Path>C:\Program Files\Greenstone\tmp\exported_Tudorcollection</Path></Text>
     1052<Path>Greenstone &rarr; tmp &rarr; exported_Tudorcollection</Path>
    10531053<Comment>
    10541054<Text id="0408b">Note, if you didn't specify a name for the CD-ROM, then the folder name will be <Path>exported_collections</Path> instead of <Path>exported_Tudorcollections</Path>.</Text>
    10551055</Comment>
    1056 <Text id="0409">You need to use your own computer's software to write these on to CD-ROM. On <i>Windows XP</i> this ability is built into the operating system: assuming you have a CD-ROM or DVD writer insert a blank disk into the drive and drag the contents of <i>exported_Tudorcollection</i> into the folder that represents the disk.</Text>
     1056<Text id="0409">You need to use your own computer's software to write these on to CD-ROM. On <i>Windows XP</i> this ability is built into the operating system: assuming you have a CD-ROM or DVD writer insert a blank disk into the drive and drag the contents of <Path>exported_Tudorcollection</Path> into the folder that represents the disk.</Text>
    10571057<Comment>
    10581058<Text id="0410">The result will be a self-installing Windows Greenstone CD-ROM or DVD, which starts the installation process as soon as it is placed in the drive.</Text>
    … …  
    10751075</NumberedItem>
    10761076<NumberedItem>
    1077 <Text id="0414">In a web browser, visit <Link>http://englishhistory.net</Link>, follow the link to <i>Tudor England</i>, and click &lt;<b>enter</b>&gt;. You should be at the URL</Text>
     1077<Text id="0414">In a web browser, visit <Link>http://englishhistory.net</Link>, follow the link to <i>Tudor England</i>, and click &lt;<b>Enter</b>&gt;. You should be at the URL</Text>
    10781078<Link>http://englishhistory.net/tudor/contents.html</Link>
    10791079<Text id="0415">This is where we started the downloading process to obtain the files you have been using for the <b>tudor</b> collection.</Text>
    10801080</NumberedItem>
    10811081<NumberedItem>
    1082 <Text id="0416">You could do the same thing by copying this URL from the web browser, pasting it into the <b>Download </b>panel, and clicking the &lt;<b>Download&gt;</b> button. However, several megabytes will be downloaded, which might strain your network resources&mdash;or your patience! For a faster exercise we focus on a smaller section of the site. In the <b>Download</b> panel, enter this URL</Text>
     1082<Text id="0416">You could do the same thing by copying this URL from the web browser, pasting it into the <AutoText key="glidict::GUI.Download"/> panel, and clicking the <AutoText key="glidict::Mirroring.Download" type="button"/> button. However, several megabytes will be downloaded, which might strain your network resources&mdash;or your patience! For a faster exercise we focus on a smaller section of the site. In the <AutoText key="glidict::GUI.Download"/> panel, enter this URL</Text>
    10831083<Link>http://englishhistory.net/tudor/citizens/</Link>
    1084 <Text id="0417">into the <b>Source URL</b> box. There are several options that govern how the download process proceeds. To copy the <i>citizens</i> section of the website, select <b>Only mirror files below this URL</b>. If you don't do this (or if you miss out the terminating "/"), the downloading process will follow links to other areas of the <i>englishhistory.net</i> website and grab those as well. Set <b>Download</b> <b>depth</b> to <b>Unlimited</b>&mdash;we want to follow as many links as necessary to download all the pages.</Text>
    1085 </NumberedItem>
    1086 <NumberedItem>
    1087 <Text id="0418">Now click &lt;<b>Download&gt;</b>. A progress bar appears in the lower half of the panel that reports on how the downloading process is doing.</Text>
    1088 <Comment>
    1089 <Text id="0419">More detailed information can be obtained by clicking &lt;<b>View Log&gt;</b>. The process can be paused and restarted as needed, or stopped altogether by clicking &lt;<b>Close&gt;</b>. Downloading can be a lengthy process involving multiple sites, and so Greenstone allows additional downloads to be queued up. When new URLs are pasted into the Source URL box and &lt;<b>Download&gt;</b> clicked, a new progress bar is appended to those already present in the lower half of the panel. When the currently active download item completes, the next is started automatically.</Text>
    1090 </Comment>
    1091 </NumberedItem>
    1092 <NumberedItem>
    1093 <Text id="0420">Downloaded files are stored in a top-level folder called <b>Downloaded Files</b> that appears on the left-hand side of the <b>Gather</b> panel. You may not need all the downloaded files, and you choose which you want by dragging selected files from this folder over into the collection area on the right-hand side, just like we have done before when selecting data from the <i>sample_files</i> folder. In this example we will include everything that has been downloaded.</Text>
    1094 <Text id="0421">Select the <b>englishhistory.net</b> folder within <b>Downloaded Files</b> and drag it across into the collection area.</Text>
    1095 </NumberedItem>
    1096 <NumberedItem>
    1097 <Text id="0422">Switch to the <b>Create</b> panel to <b>build</b> and <b>preview</b> the collection. It is smaller than the previous collection because we included only the <i>citizens</i> files. However, these now represent the latest versions of the documents.</Text>
     1084<Text id="0417">into the <AutoText key="glidict::Mirroring.Source_URL"/> box. There are several options that govern how the download process proceeds. To copy the <i>citizens</i> section of the website, select <AutoText key="glidict::Mirroring.Higher_Directories"/>. If you don't do this (or if you miss out the terminating "/"), the downloading process will follow links to other areas of the <i>englishhistory.net</i> website and grab those as well. Set <AutoText key="glidict::Mirroring.Download_Depth"/> to <AutoText key="glidict::Mirroring.Download_Depth.Unlimited"/>&mdash;we want to follow as many links as necessary to download all the pages.</Text>
     1085</NumberedItem>
     1086<NumberedItem>
     1087<Text id="0418">Now click <AutoText key="glidict::Mirroring.Download" type="button"/>. A progress bar appears in the lower half of the panel that reports on how the downloading process is doing.</Text>
     1088<Comment>
     1089<Text id="0419">More detailed information can be obtained by clicking <AutoText key="glidict::Mirroring.DownloadJob.Log" type="button"/>. The process can be paused and restarted as needed, or stopped altogether by clicking <AutoText key="glidict::Mirroring.DownloadJob.Close" type="button"/>. Downloading can be a lengthy process involving multiple sites, and so Greenstone allows additional downloads to be queued up. When new URLs are pasted into the <AutoText key="glidict::Mirroring.Source_URL"/> box and <AutoText key="glidict::Mirroring.Download" type="button"/> clicked, a new progress bar is appended to those already present in the lower half of the panel. When the currently active download item completes, the next is started automatically.</Text>
     1090</Comment>
     1091</NumberedItem>
     1092<NumberedItem>
     1093<Text id="0420">Downloaded files are stored in a top-level folder called <AutoText key="glidict::Tree.DownloadedFiles"/> that appears on the left-hand side of the <AutoText key="glidict::GUI.Gather"/> panel. You may not need all the downloaded files, and you choose which you want by dragging selected files from this folder over into the collection area on the right-hand side, just like we have done before when selecting data from the <Path>sample_files</Path> folder. In this example we will include everything that has been downloaded.</Text>
     1094<Text id="0421">Select the <Path>englishhistory.net</Path> folder within <AutoText key="glidict::Tree.DownloadedFiles"/> and drag it across into the collection area.</Text>
     1095</NumberedItem>
     1096<NumberedItem>
     1097<Text id="0422">Switch to the <AutoText key="glidict::GUI.Create"/> panel to <b>build</b> and <b>preview</b> the collection. It is smaller than the previous collection because we included only the <i>citizens</i> files. However, these now represent the latest versions of the documents.</Text>
    10981098</NumberedItem>
    10991099</Content>
    … …  
    11071107<Content>
    11081108<NumberedItem>
    1109 <Text id="0424">Open up your <b>webtudor</b> collection, and in the <b>Gather</b> panel inspect the files you dragged into it. The first folder is <i>englishhistory.net</i>, which opens up to reveal <i>tudor</i>, and so on. The files represent a complete sweep of the pages (and supporting images) that constitute the <i>Tudor citizens</i> section of the <i>englishhistory.net</i> web site. They were downloaded from the web in a way that preserved the structure of the original site. This allows any page's original URL to be reconstructed from the folder hierarchy.</Text>
    1110 </NumberedItem>
    1111 <NumberedItem>
    1112 <Text id="0425">In the <b>Design</b> panel, select the <b>Document Plugins</b> section, then select the <b>plugin HTMLPlug</b> line and click &lt;<b>Configure Plugin...&gt;</b>. A popup window appears. Locate the <b>file_is_url</b> option (about halfway down the first block of items) and switch it on. Click &lt;<b>OK&gt;</b>.</Text>
    1113 <Text id="0426">Setting this option to the HTMLPlug means that Greenstone sets an additional piece of metadata for each document called URL, which gives its original URL.</Text>
    1114 <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 <i>tudor</i> folder, because this will set URL metadata to something like</Text>
     1109<Text id="0424">Open up your <b>webtudor</b> collection, and in the <AutoText key="glidict::GUI.Gather"/> panel inspect the files you dragged into it. The first folder is <Path>englishhistory.net</Path>, which opens up to reveal <Path>tudor</Path>, and so on. The files represent a complete sweep of the pages (and supporting images) that constitute the <i>Tudor citizens</i> section of the <i>englishhistory.net</i> web site. They were downloaded from the web in a way that preserved the structure of the original site. This allows any page's original URL to be reconstructed from the folder hierarchy.</Text>
     1110</NumberedItem>
     1111<NumberedItem>
     1112<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. Click <AutoText key="glidict::General.OK" type="button"/>.</Text>
     1113<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>
     1114<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>
    11151115<Indent>
    11161116http://tudor/citizens/...
    … …  
    11201120http://englishhistory.net/tudor/citizens/...
    11211121</Indent>
    1122 <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 <b>Gather</b> panel on to the trash can in the lower right corner. Then obtain a fresh copy of the files by dragging across the <i>englishhistory.net</i> folder from the Downloaded Files folder on the left-hand side.</Text>
    1123 </NumberedItem>
    1124 <NumberedItem>
    1125 <Text id="0430">To make use of the new URL metadata, the icon link must be changed to serve up the original URL rather than the copy stored in the digital library. Go to the <b>Design</b> panel, select the <b>Format Features</b> section and edit the <b>VList</b> format statement by replacing</Text>
     1122<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>
     1123</NumberedItem>
     1124<NumberedItem>
     1125<Text id="0430">To make use of the new URL metadata, the icon link must be changed to serve up the original URL rather than the copy stored in the digital library. Go to the <AutoText key="glidict::GUI.Design"/> panel, select the <AutoText key="glidict::CDM.GUI.Formats"/> section and edit the <AutoText text="VList" /> format statement by replacing</Text>
    11261126<Format>[link][icon][/link]</Format>
    11271127<Text id="0431">with</Text>
    11281128<Format>[weblink][webicon][/weblink]</Format>
    1129 <Text id="0432">Click &lt;<b>Replace Format&gt;</b> to commit the change.</Text>
    1130 </NumberedItem>
    1131 <NumberedItem>
    1132 <Text id="0433">Switch to the <b>Create</b> panel and <b>build</b> and <b>preview</b> the collection. The collection behaves exactly as before, except that when you click a document icon your web browser retrieves the original document from the web (assuming it is still there by the time you do this exercise!). If you are working offline you will be unable to retrieve the document.</Text>
     1129<Text id="0432">Click <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/> to commit the change.</Text>
     1130</NumberedItem>
     1131<NumberedItem>
     1132<Text id="0433">Switch to the <AutoText key="glidict::GUI.Create"/> panel and <b>build</b> and <b>preview</b> the collection. The collection behaves exactly as before, except that when you click a document icon your web browser retrieves the original document from the web (assuming it is still there by the time you do this exercise!). If you are working offline you will be unable to retrieve the document.</Text>
    11331133</NumberedItem>
    11341134</Content>
    … …  
    11481148</Heading>
    11491149<NumberedItem>
    1150 <Text id="0438">Open up your <b>tudor</b> collection (the original version, not the <b>webtudor</b> version), switch to the <b>Enrich </b>panel and select the <i>monarchs</i> folder (a subfolder of <i>tudor</i>). Set its <b>dc.Subject and Keywords</b> metadata to <b>Tudor period|Monarchs</b>. (For brevity, we refer to this metadata element in future simply as <b>dc.Subject</b>.) The vertical bar ("|") is a hierarchy marker. Selecting a <i>folder</i> and adding metadata has the effect of setting this metadata value for all files contained in this folder, its subfolders, and so on. A popup alerts you to this fact.</Text>
    1151 </NumberedItem>
    1152 <NumberedItem>
    1153 <Text id="0439">Repeat for the <i>relative</i> and <i>citizens</i> folder, setting their <b>dc.Subject</b> metadata to <b>Tudor period|Relatives</b> and <b>Tudor period|Citizens</b> respectively. Note that the hierarchy appears in the <b>Existing values for dc.Subject and Keywords</b> area.</Text>
    1154 </NumberedItem>
    1155 <NumberedItem>
    1156 <Text id="0440">Finally, select all remaining files&mdash;the ones that are not in the <i>monarchs</i>, <i>relative</i>, and <i>citizens</i> folders&mdash;by selecting the first and shift-clicking the last. Set their <b>dc.Subject</b> metadata to <b>Tudor period|Others</b>: this is done in a single operation (there is a short delay before it completes).</Text>
    1157 </NumberedItem>
    1158 <NumberedItem>
    1159 <Text id="0441">Switch to the <b>Design</b> panel and select <b>Browsing Classifiers </b>from the left-hand list. Set the menu item for <b>Select classifier to add </b>to <b>Hierarchy</b>; then click &lt;<b>Add Classifier...</b>&gt;.</Text>
    1160 </NumberedItem>
    1161 <NumberedItem>
    1162 <Text id="0442">A window pops up to control the classifier's options. Change the <b>metadata</b> to <i>dc.Subject</i> and then click <b>&lt;OK&gt;</b>.</Text>
     1150<Text id="0438">Open up your <b>tudor</b> collection (the original version, not the <b>webtudor</b> version), switch to the <AutoText key="glidict::GUI.Enrich"/> panel and select the <Path>monarchs</Path> folder (a subfolder of <Path>tudor</Path>). Set its <b>dc.Subject and Keywords</b> metadata to <b>Tudor period|Monarchs</b>. (For brevity, we refer to this metadata element in future simply as <b>dc.Subject</b>.) The vertical bar ("|") is a hierarchy marker. Selecting a <i>folder</i> and adding metadata has the effect of setting this metadata value for all files contained in this folder, its subfolders, and so on. A popup alerts you to this fact.</Text>
     1151</NumberedItem>
     1152<NumberedItem>
     1153<Text id="0439">Repeat for the <Path>relative</Path> and <Path>citizens</Path> folders, setting their <AutoText key="metadata::dc.Subject"/> metadata to <b>Tudor period|Relatives</b> and <b>Tudor period|Citizens</b> respectively. Note that the hierarchy appears in the <AutoText key="glidict::EnrichPane.ExistingValues" args="dc.Subject and Keywords"/> area.</Text>
     1154</NumberedItem>
     1155<NumberedItem>
     1156<Text id="0440">Finally, select all remaining files&mdash;the ones that are not in the <Path>monarchs</Path>, <Path>relative</Path>, and <Path>citizens</Path> folders&mdash;by selecting the first and shift-clicking the last. Set their <AutoText key="metadata::dc.Subject"/> metadata to <b>Tudor period|Others</b>: this is done in a single operation (there is a short delay before it completes).</Text>
     1157</NumberedItem>
     1158<NumberedItem>
     1159<Text id="0441">Switch to the <AutoText key="glidict::GUI.Design"/> panel and 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="Hierarchy"/>; then click <AutoText key="glidict::CDM.ClassifierManager.Add" type="button"/>.</Text>
     1160</NumberedItem>
     1161<NumberedItem>
     1162<Text id="0442">A window pops up to control the classifier's options. Change the <b>metadata</b> to <AutoText key="metadata::dc.Subject"/> and then click <AutoText key="glidict::General.OK" type="button"/>.</Text>
    11631163</NumberedItem>
    11641164<NumberedItem>
    … …  
    11661166</NumberedItem>
    11671167<NumberedItem>
    1168 <Text id="0444">Now switch to the <b>Create </b>panel, <b>build </b>the collection, and <b>preview </b>it. Choose the new <b>subjects </b>link that appears in the navigation bar, and click the bookshelves to navigate around the four-entry hierarchy that you have created.</Text>
    1169 </NumberedItem>
    1170 <Comment>
    1171 <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 <b>dc.Subject</b> metadata. Then an index is assigned to each subcollection.</Text>
     1168<Text id="0444">Now switch to the <AutoText key="glidict::GUI.Create"/> panel, <b>build</b> the collection, and <b>preview</b> it. Choose the new <AutoText key="coredm::_Global:labelSubject_"/> link that appears in the navigation bar, and click the bookshelves to navigate around the four-entry hierarchy that you have created.</Text>
     1169</NumberedItem>
     1170<Comment>
     1171<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.</Text>
    11721172</Comment>
    11731173<Heading>
    … …  
    11751175</Heading>
    11761176<NumberedItem>
    1177 <Text id="0447">Switch to the <b>Design</b> panel, and click &lt;<b>Partition Indexes</b>&gt;. This feature is disabled because you are operating in <i>Librarian Mode</i> (this is indicated in the title bar at the top of the window).</Text>
    1178 </NumberedItem>
    1179 <NumberedItem>
    1180 <Text id="0448">Switch to <i>Library Systems Specialist</i> mode by going to <b>Preferences</b> (on the <i>File</i> menu) and clicking &lt;<b>Mode</b>&gt;. Read about the other modes too. Note that the mode appears in the title bar.</Text>
    1181 </NumberedItem>
    1182 <NumberedItem>
    1183 <Text id="0449">Return to the <b>Partition Indexes</b> section of the <b>Design</b> panel. Ensure that the <b>Define Filters</b> tab is selected (the default). Define a subcollection filter with name <b>monarchs</b> that matches against <b>dc.Subject and Keywords, </b>and type <b>Monarchs</b> as the regular expression to match with. Click &lt;<b>Add Filter</b>&gt;. This filter includes any file whose <b>dc.Subject</b> metadata contains the word <i>Monarchs</i>.</Text>
    1184 </NumberedItem>
    1185 <NumberedItem>
    1186 <Text id="0450">Define another filter, <b>relatives</b>, which matches <b>dc.Subject </b>against the word <b>Relatives</b>.<b> </b>Define a third and fourth, <b>citizens</b> and <b>others</b>, which matches it against the words <b>Citizens</b> and <b>Others</b> respectively.</Text>
    1187 </NumberedItem>
    1188 <NumberedItem>
    1189 <Text id="0451">Having defined the subcollections, we partition the index into corresponding parts. Click the &lt;<b>Assign Partitions</b>&gt; tab. Select the first subcollection and give it the name <b>citizens</b>; click &lt;<b>Add Partition</b>&gt;. Repeat for the other three subcollections, naming their partitions <b>monarchs</b>, <b>others</b> and <b>relatives</b>. <b>Build</b> and <b>preview</b> the collection.</Text>
     1177<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>
     1178</NumberedItem>
     1179<NumberedItem>
     1180<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. Note that the mode appears in the title bar.</Text>
     1181</NumberedItem>
     1182<NumberedItem>
     1183<Text id="0449">Return to the <AutoText key="glidict::CDM.GUI.Subcollections"/> section of the <AutoText key="glidict::GUI.Design"/> panel. Ensure that the <AutoText key="glidict::CDM.SubcollectionManager.Subcollection_Controls"/> tab is selected (the default). Define a subcollection filter with name <b>monarchs</b> that matches against <b>dc.Subject and Keywords,</b> and type <b>Monarchs</b> as the regular expression to match with. Click <AutoText key="glidict::CDM.SubcollectionManager.Add" type="button"/>. This filter includes any file whose <AutoText key="metadata::dc.Subject"/> metadata contains the word <i>Monarchs</i>.</Text>
     1184</NumberedItem>
     1185<NumberedItem>
     1186<Text id="0450">Define another filter, <b>relatives</b>, which matches <AutoText key="metadata::dc.Subject"/> against the word <b>Relatives</b>.<b></b> Define a third and fourth, <b>citizens</b> and <b>others</b>, which matches it against the words <b>Citizens</b> and <b>Others</b> respectively.</Text>
     1187</NumberedItem>
     1188<NumberedItem>
     1189<Text id="0451">Having defined the subcollections, we partition the index into corresponding parts. Click the <AutoText key="glidict::CDM.SubcollectionManager.Subindex_Controls"/> tab. Select the first subcollection and give it the name <b>citizens</b>; click <AutoText key="glidict::CDM.SubcollectionIndexManager.Add_Subindex" type="button"/>. Repeat for the other three subcollections, naming their partitions <b>monarchs</b>, <b>others</b> and <b>relatives</b>. <b>Build</b> and <b>preview</b> the collection.</Text>
    11901190</NumberedItem>
    11911191<NumberedItem>
    … …  
    11931193</NumberedItem>
    11941194<NumberedItem>
    1195 <Text id="0453">To allow users to search the collection as a whole as well as each subcollection individually, return to the <b>Partition Indexes</b> section of the <b>Design</b> panel and select the <b>Assign Partitions </b>tab.<b> </b>Type <b>all</b> into the <b>Partition Name </b>and select all four subcollections by checking their boxes.</Text>
    1196 </NumberedItem>
    1197 <NumberedItem>
    1198 <Text id="0454">To ensure that the <i>all</i> index appears first in the list on the reader's web page, use the &lt;<b>Move Up</b>&gt; button to get it to the top of the list here in the <b>Design</b> panel. Then <b>build</b> and <b>preview</b> the collection.</Text>
     1195<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.<b></b> Type <b>all</b> into the <AutoText key="glidict::CDM.SubcollectionIndexManager.PartitionName"/> and select all four subcollections by checking their boxes.</Text>
     1196</NumberedItem>
     1197<NumberedItem>
     1198<Text id="0454">To ensure that the <i>all</i> index appears first in the list on the reader's web page, use the <AutoText key="glidict::CDM.Move.Move_Up" type="button"/> button to get it to the top of the list here in the <AutoText key="glidict::GUI.Design"/> panel. Then <b>build</b> and <b>preview</b> the collection.</Text>
    11991199</NumberedItem>
    12001200<NumberedItem>
    … …  
    12021202</NumberedItem>
    12031203<NumberedItem>
    1204 <Text id="0456">Return to <i>Librarian </i>mode, using <b>Preferences</b> (on the <i>File</i> menu).</Text>
     1204<Text id="0456">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>
    12051205</NumberedItem>
    12061206<Heading>
    … …  
    12081208</Heading>
    12091209<NumberedItem>
    1210 <Text id="0458">Switch to the <b>Design</b> panel and choose the <b>Browsing Classifiers</b> item from the left-hand list.</Text>
    1211 </NumberedItem>
    1212 <NumberedItem>
    1213 <Text id="0459">Choose <b>Phind</b> from the <b>Select classifier to add</b> menu. Click &lt;<b>Add Classifier...</b>&gt;. A window pops asking for configuration options: leave the values at their preset defaults (this will base the phrase index on the full text) and click <b>&lt;OK&gt;</b>.</Text>
    1214 </NumberedItem>
    1215 <NumberedItem>
    1216 <Text id="0460"><b>Build</b> the collection again, <b>preview</b> it, and try out the new <b>phrases</b> option in the navigation bar. An interesting PHIND search term for this collection is <b>king</b>.</Text>
    1217 </NumberedItem>
    1218 <Comment>
    1219 <Text id="0461">Finally we look at how the building process can be controlled. Developing a new collection usually involves numerous cycles of building, previewing, adjusting some enrich and design features, and so on. While prototyping, it is best to temporarily reduce the number of documents in the collection. This can be accomplished through the "maxdocs" parameter to the building process.</Text>
     1210<Text id="0458">Switch to the <AutoText key="glidict::GUI.Design"/> panel and choose the <AutoText key="glidict::CDM.GUI.Classifiers"/> item from the left-hand list.</Text>
     1211</NumberedItem>
     1212<NumberedItem>
     1213<Text id="0459">Choose <AutoText text="Phind"/> from the <AutoText key="glidict::CDM.ClassifierManager.Classifier"/> menu. Click <AutoText key="glidict::CDM.ClassifierManager.Add" type="button"/>. A window pops asking for configuration options: leave the values at their preset defaults (this will base the phrase index on the full text) and click <AutoText key="glidict::General.OK" type="button"/>.</Text>
     1214</NumberedItem>
     1215<NumberedItem>
     1216<Text id="0460"><b>Build</b> the collection again, <b>preview</b> it, and try out the new <AutoText key="coredm::_Global:labelphrases_"/> option in the navigation bar. An interesting PHIND search term for this collection is <AutoText text="king" type="quoted"/>.</Text>
     1217</NumberedItem>
     1218<Comment>
     1219<Text id="0461">Finally we look at how the building process can be controlled. Developing a new collection usually involves numerous cycles of building, previewing, adjusting some enrich and design features, and so on. While prototyping, it is best to temporarily reduce the number of documents in the collection. This can be accomplished through the <AutoText text="maxdocs"/> parameter to the building process.</Text>
    12201220</Comment>
    12211221<Heading>
    … …  
    12231223</Heading>
    12241224<NumberedItem>
    1225 <Text id="0463">Switch to the <b>Create</b> panel and view the options that are displayed in the top portion of the screen. Select <b>maxdocs</b> and set its numeric counter to <b>3</b>. Now <b>build</b>.</Text>
    1226 </NumberedItem>
    1227 <NumberedItem>
    1228 <Text id="0464">Preview the newly rebuilt collection's <b>titles a-z</b> page. Previously this listed more than a dozen pages per letter of the alphabet, but now there are just three&mdash;the first three files encountered by the building process.</Text>
    1229 </NumberedItem>
    1230 <NumberedItem>
    1231 <Text id="0464a">Go back to the <b>Create</b> panel and turn off the <b>maxdocs</b> option. <b>Rebuild</b> the collection so that all the documents are included.</Text>
     1225<Text id="0463">Switch to the <AutoText key="glidict::GUI.Create"/> panel and view the options that are displayed in the top portion of the screen. Select <AutoText text="maxdocs"/> and set its numeric counter to <AutoText text="3"/>. Now <b>build</b>.</Text>
     1226</NumberedItem>
     1227<NumberedItem>
     1228<Text id="0464">Preview the newly rebuilt collection's <AutoText key="coredm::_Global:labelTitle_"/> page. Previously this listed more than a dozen pages per letter of the alphabet, but now there are just three&mdash;the first three files encountered by the building process.</Text>
     1229</NumberedItem>
     1230<NumberedItem>
     1231<Text id="0464a">Go back to the <AutoText key="glidict::GUI.Create"/> panel and turn off the <AutoText text="maxdocs"/> option. <b>Rebuild</b> the collection so that all the documents are included.</Text>
    12321232</NumberedItem>
    12331233</Content>
    … …  
    12471247</Heading>
    12481248<NumberedItem>
    1249 <Text id="0468">Open up your <b>tudor</b> collection, go to the <b>Design</b> panel (by clicking on its tab) and select <b>Format Features </b>from the left-hand list. Leave the editing controls at their default value, so that <b>Choose Feature </b>remains blank and <b>VList </b>is selected as the <b>Affected Component</b>. The text in the <b>HTML Format String</b> box reads as follows:</Text>
     1249<Text id="0468">Open up your <b>tudor</b> collection, go to the <AutoText key="glidict::GUI.Design"/> panel (by clicking on its tab) and select <AutoText key="glidict::CDM.GUI.Formats"/> from the left-hand list. Leave the editing controls at their default value, so that <AutoText key="glidict::CDM.FormatManager.Feature"/> remains blank and <AutoText text="VList"/> is selected as the <AutoText key="glidict::CDM.FormatManager.Part"/>. The text in the <AutoText key="glidict::CDM.FormatManager.Editor"/> box reads as follows:</Text>
    12501250<Format>
    12511251&lt;td valign=top&gt;[link][icon][/link]&lt;/td&gt;<br/>
    … …  
    12591259<table><tr><td><img width='15' height='20' src="../tutorial_files/itext.gif"/></td><td width='408' valign='top'>A discussion of question five from Tudor Quiz: Henry VIII <br/><i>(quizstuff.html)</i></td></tr></table>
    12601260</Indent>
    1261 <Text id="0472">for a particular document whose <i>Title</i> metadata is <i>A discussion of question five from Tudor Quiz: Henry VIII</i> and whose <i>Source</i> metadata is <i>quizstuff.html</i>.</Text>
    1262 <Text id="0473">This format appears in the search results list, in the <i>titles a-z</i> list, and also when you get down to individual documents in the <i>subjects</i> hierarchy. This is Greenstone's default format statement.</Text>
     1261<Text id="0472">for a particular document whose <i>Title</i> metadata is <AutoText text="A discussion of question five from Tudor Quiz: Henry VIII"/> and whose <i>Source</i> metadata is <AutoText text="quizstuff.html"/>.</Text>
     1262<Text id="0473">This format appears in the search results list, in the <AutoText key="coredm::_Global:labelTitle_"/> list, and also when you get down to individual documents in the <AutoText key="coredm::_Global:labelTitle_"/> hierarchy. This is Greenstone's default format statement.</Text>
    12631263</NumberedItem>
    12641264<Comment>
    … …  
    12661266</Comment>
    12671267<NumberedItem>
    1268 <Text id="0475">Delete the contents of the <b>HTML</b> <b>Format String</b> box and replace it with this simpler version:</Text>
     1268<Text id="0475">Delete the contents of the <AutoText key="glidict::CDM.FormatManager.Editor"/> box and replace it with this simpler version:</Text>
    12691269<Format>
    12701270&lt;td&gt;[link][icon][/link]&lt;/td&gt; <br/>
    … …  
    12731273&lt;/td&gt;
    12741274</Format>
    1275 <Text id="0475a">Remember to click <b>&lt;Replace Format&gt;</b>.</Text>
    1276 <Text id="0476"><b>Preview</b> the result (you don't need to build the collection, because changes to format statements take effect immediately). Look at some search results and at the <i>titles a-z</i> list. They are just the same as before! Under most circumstances this far simpler format statement is entirely equivalent to Greenstone's more complex default. </Text>
    1277 <Comment>
    1278 <Text id="0478">But there's a problem. Beside the bookshelves in the <b>subjects</b> browser, beneath the subject appears a mysterious "()". What is printed on these bookshelf nodes is governed by the same format statement, and though bookshelf nodes of the hierarchy have associated <i>Title</i> metadata&mdash;their title is the name of the metadata value associated with that bookshelf&mdash;they do not have <i>ex.Source</i> metadata, so it comes out blank.</Text>
    1279 </Comment>
    1280 </NumberedItem>
    1281 <NumberedItem>
    1282 <Text id="0482">In the <b>Format Features</b> section of the <b>Design</b> panel, the <b>Choose Feature</b> menu (just above <b>Affected Component</b> menu) is blank. That implies that the same format is used for the search results, titles, and all nodes in the subject hierarchy&mdash;including internal nodes (that is, bookshelves). The <b>Choose Feature</b> menu can be used to restrict a format statement to a specific one of these lists; when it's blank, the <b>VList</b> specification applies throughout. We will override this format statement for the hierarchical <i>subject</i> classifier. In the <b>Choose Feature</b> menu, scroll down to the item that says</Text>
     1275<Text id="0475a">Remember to click <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/>.</Text>
     1276<Text id="0476"><b>Preview</b> the result (you don't need to build the collection, because changes to format statements take effect immediately). Look at some search results and at the <AutoText key="coredm::_Global:labelTitle_"/> list. They are just the same as before! Under most circumstances this far simpler format statement is entirely equivalent to Greenstone's more complex default. </Text>
     1277<Comment>
     1278<Text id="0478">But there's a problem. Beside the bookshelves in the <AutoText key="coredm::_Global:labelSubject_"/> browser, beneath the subject appears a mysterious "()". What is printed on these bookshelf nodes is governed by the same format statement, and though bookshelf nodes of the hierarchy have associated <i>Title</i> metadata&mdash;their title is the name of the metadata value associated with that bookshelf&mdash;they do not have <AutoText key="metadata::ex.Source"/> metadata, so it comes out blank.</Text>
     1279</Comment>
     1280</NumberedItem>
     1281<NumberedItem>
     1282<Text id="0482">In the <AutoText key="glidict::CDM.GUI.Formats"/> section of the <AutoText key="glidict::GUI.Design"/> panel, the <AutoText key="glidict::CDM.FormatManager.Feature"/> menu (just above <AutoText key="glidict::CDM.FormatManager.Part"/> menu) is blank. That implies that the same format is used for the search results, titles, and all nodes in the subject hierarchy&mdash;including internal nodes (that is, bookshelves). The <AutoText key="glidict::CDM.FormatManager.Feature"/> menu can be used to restrict a format statement to a specific one of these lists; when it's blank, the <AutoText text="VList" /> specification applies throughout. We will override this format statement for the hierarchical <i>subject</i> classifier. In the <AutoText key="glidict::CDM.FormatManager.Feature"/> menu, scroll down to the item that says</Text>
    12831283<Indent>
    12841284CL2: Hierarchy -metadata dc.Subject and Keywords
    12851285</Indent>
    1286 <Text id="0483">and select it. This is the format statement that affects the second classifier (i.e., "CL2"), which is a <b>Hierarchy</b> classifier based on <b>dc.Subject and Keywords</b> metadata.</Text>
    1287 <Text id="0484">Edit the <b>HTML Format String</b> box below to read</Text>
     1286<Text id="0483">and select it. This is the format statement that affects the second classifier (i.e., "CL2"), which is a <AutoText text="Hierarchy"/> classifier based on <b>dc.Subject and Keywords</b> metadata.</Text>
     1287<Text id="0484">Edit the <AutoText key="glidict::CDM.FormatManager.Editor"/> box below to read</Text>
    12881288<Format>
    12891289&lt;td&gt;[link][icon][/link]&lt;/td&gt;<br/>
    12901290&lt;td&gt;[ex.Title]&lt;/td&gt;
    12911291</Format>
    1292 <Text id="0485">and click &lt;<b>Add Format</b>&gt;.</Text>
    1293 </NumberedItem>
    1294 <NumberedItem>
    1295 <Text id="0486">Now go to the <b>Create</b> panel and click &lt;<b>Preview Collection</b>&gt;. First, the offending "()" has disappeared from the bookshelves. Second, when you get down to a list of documents in the subject hierarchy, the filename does not appear beside the title, because <i>ex.Source</i> is not specified in the format statement and this format statement applies to all nodes in the <i>subject</i> classifier. Note that the search results and titles lists have not changed: they still display the filename underneath the title.</Text>
    1296 </NumberedItem>
    1297 <NumberedItem>
    1298 <Text id="0487">Let's change the search results format so that <i>dc.Subject and Keywords </i>metadata is displayed here instead of the filename. In the <b>Choose Feature </b>menu (under <b>Format Features </b>on the <b>Design </b>panel), scroll down to the item <b>Search</b> and select it. Change the <b>HTML Format String</b> box below to read</Text>
     1292<Text id="0485">and click <AutoText key="glidict::CDM.FormatManager.Add" type="button"/>.</Text>
     1293</NumberedItem>
     1294<NumberedItem>
     1295<Text id="0486">Now go to the <AutoText key="glidict::GUI.Create"/> panel and click <AutoText key="glidict::CreatePane.Preview_Collection" type="button"/>. First, the offending "()" has disappeared from the bookshelves. Second, when you get down to a list of documents in the subject hierarchy, the filename does not appear beside the title, because <AutoText key="metadata::ex.Source"/> is not specified in the format statement and this format statement applies to all nodes in the <i>subject</i> classifier. Note that the search results and titles lists have not changed: they still display the filename underneath the title.</Text>
     1296</NumberedItem>
     1297<NumberedItem>
     1298<Text id="0487">Let's change the search results format so that <i>dc.Subject and Keywords</i> metadata is displayed here instead of the filename. In the <AutoText key="glidict::CDM.FormatManager.Feature"/> menu (under <AutoText key="glidict::CDM.GUI.Formats"/> on the <AutoText key="glidict::GUI.Design"/> panel), scroll down to the item <AutoText text="Search"/> and select it. Change the <AutoText key="glidict::CDM.FormatManager.Editor"/> box below to read</Text>
    12991299<Format>
    13001300&lt;td&gt;[link][icon][/link]&lt;/td&gt;<br/>
    … …  
    13031303&lt;/td&gt;<br/>
    13041304</Format>
    1305 <Text id="0488">and click &lt;<b>Add Format</b>&gt;.</Text>
    1306 </NumberedItem>
    1307 <NumberedItem>
    1308 <Text id="0489">To insert the <b>[dc.Subject]</b>, position the cursor at the appropriate point and either type it in, or use the <b>Variables</b> dropdown menu&mdash;the one that says <b>[Text]</b>. Make it say <b>[dc.Subject]</b> and click <b>Insert </b>to insert this into the <b>HTML Format String</b>. This menu shows many of the things that you can put in square brackets in the format statement. The only exception is <b>[Text]</b>, which gives the full text of the document, and can only be used when <b>DocumentText</b> is the <b>Affected Component</b>.</Text>
    1309 </NumberedItem>
    1310 <NumberedItem>
    1311 <Text id="0490">Now go to the <b>Create</b> panel and click &lt;<b>Preview Collection</b>&gt;. Documents in the search results list will be displayed like this:</Text>
     1305<Text id="0488">and click <AutoText key="glidict::CDM.FormatManager.Add" type="button"/>.</Text>
     1306</NumberedItem>
     1307<NumberedItem>
     1308<Text id="0489">To insert the <b>[dc.Subject]</b>, position the cursor at the appropriate point and either type it in, or use the <AutoText key="glidict::CDM.FormatManager.Variable"/> dropdown menu&mdash;the one that says <AutoText text="[Text]"/>. Make it say <b>[dc.Subject]</b> and click <AutoText key="glidict::CDM.FormatManager.Insert" type="button"/> to insert this into the <AutoText key="glidict::CDM.FormatManager.Editor"/>. This menu shows many of the things that you can put in square brackets in the format statement.</Text>
     1309</NumberedItem>
     1310<NumberedItem>
     1311<Text id="0490">Now go to the <AutoText key="glidict::GUI.Create"/> panel and click <AutoText key="glidict::CreatePane.Preview_Collection" type="button"/>. Documents in the search results list will be displayed like this:</Text>
    13121312<table><tr><td><img width='15' height='20' src="../tutorial_files/itext.gif" /></td><td width='408' valign='top'>A discussion of question five from Tudor Quiz: Henry VIII <br/>
    13131313Tudor period|Others</td></tr></table>
    … …  
    13151315</NumberedItem>
    13161316<NumberedItem>
    1317 <Text id="0494">Finally, let's return to the <i>subjects</i> hierarchy and learn how to do different things to the bookshelves and to the documents themselves. In the <b>Choose Feature </b>menu, re-select the item</Text>
     1317<Text id="0494">Finally, let's return to the <i>subjects</i> hierarchy and learn how to do different things to the bookshelves and to the documents themselves. In the <AutoText key="glidict::CDM.FormatManager.Feature"/> menu, re-select the item</Text>
    13181318<Indent>
    13191319CL2: Hierarchy -metadata dc.Subject and Keywords
    13201320</Indent>
    1321 <Text id="0495">Edit the <b>HTML Format String </b>box below to read</Text>
     1321<Text id="0495">Edit the <AutoText key="glidict::CDM.FormatManager.Editor"/> box below to read</Text>
    13221322<Format>
    13231323&lt;td&gt;[link][icon][/link]&lt;/td&gt;<br/>
    … …  
    13261326&lt;/td&gt;
    13271327</Format>
    1328 <Text id="0496">and click <b>Replace Format</b>. Again, you can insert the items in square brackets by selecting them from the <b>Variables</b> dropdown box (don't forget to click <b>Insert</b>).</Text>
    1329 <Comment>
    1330 <Text id="0497">The <b>If</b> statement tests the value of the variable <b>numleafdocs</b>. This variable is only set for internal nodes of the hierarchy, i.e. bookshelves, and gives the number of documents below that node. If it is set we take the first branch, otherwise we take the second. Commas are used to separate the branches. The curly brackets serve to indicate that the <b>If</b> is special&mdash;otherwise the word "If" itself would be output.</Text>
    1331 </Comment>
    1332 </NumberedItem>
    1333 <NumberedItem>
    1334 <Text id="0498">Go to the <b>Create </b>panel, click &lt;<b>Preview Collection</b>&gt;, and examine the subject hierarchy again to see the effect of your changes.</Text>
     1328<Text id="0496">and click <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/>. Again, you can insert the items in square brackets by selecting them from the <AutoText key="glidict::CDM.FormatManager.Variable"/> dropdown box (don't forget to click <AutoText key="glidict::CDM.FormatManager.Insert" type="button"/>).</Text>
     1329<Comment>
     1330<Text id="0497">The <AutoText text="If"/> statement tests the value of the variable <AutoText text="numleafdocs"/>. This variable is only set for internal nodes of the hierarchy, i.e. bookshelves, and gives the number of documents below that node. If it is set we take the first branch, otherwise we take the second. Commas are used to separate the branches. The curly brackets serve to indicate that the <AutoText text="If"/> is special&mdash;otherwise the word <AutoText text="If" type="quoted"/> itself would be output.</Text>
     1331</Comment>
     1332</NumberedItem>
     1333<NumberedItem>
     1334<Text id="0498">Go to the <AutoText key="glidict::GUI.Create"/> panel, click <AutoText key="glidict::CreatePane.Preview_Collection" type="button"/>, and examine the subject hierarchy again to see the effect of your changes.</Text>
    13351335</NumberedItem>
    13361336<Heading>
    … …  
    13381338</Heading>
    13391339<Comment>
    1340 <Text id="0500">The appearance of all pages produced by Greenstone is governed by macro files, which reside in the folder <Path>C:\Program Files\Greenstone\macros</Path>. The garish example collection is a version of the demo collection with bizarre layout and coloring. Now we apply the same bizarre layout and coloring to the tudor collection.</Text>
    1341 </Comment>
    1342 <NumberedItem>
    1343 <Text id="0505">Go to the folder <Path>C:\Program Files\Greenstone\collect\garish\macros</Path>. Copy the file <i>extra.dm</i>. Now go to your collection folder <Path>C:\Program Files\Greenstone\collect\tudor</Path> and create a new folder in there called <i>macros</i>. Paste <i>extra.dm</i> into that new folder. The overall effect is that you have created a new file <Path>C:\Program Files\Greenstone\collect\tudor\macros\extra.dm</Path>.</Text>
    1344 </NumberedItem>
    1345 <NumberedItem>
    1346 <Text id="0505a">This macro file uses a CSS style file and some images which you will also need to copy from the garish collection. Go to the folder <Path>C:\Program Files\Greenstone\collect\garish\images</Path>. Select the three files <i>style.css</i>, <i>horzline.gif</i> and <i>bg_blue.gif</i>. <b>Copy</b> these files and paste them into the <Path>C:\Program Files\Greenstone\collect\tudor\images</Path> folder.</Text>
    1347 </NumberedItem>
    1348 <NumberedItem>
    1349 <Text id="0507">Go to the <b>Create </b>panel and click &lt;<b>Preview Collection</b>&gt;. The content of your collection remains the same, but its appearance has changed completely&mdash;for example, all the pages are pink! To learn about how to control these changes, go to the documented example collection called <i>Garish version of demo collection</i>, and read about it.</Text>
     1340<Text id="0500">The appearance of all pages produced by Greenstone is governed by macro files, which reside in the folder <Path>Greenstone &rarr; macros</Path>. The garish example collection is a version of the demo collection with bizarre layout and coloring. Now we apply the same bizarre layout and coloring to the tudor collection.</Text>
     1341</Comment>
     1342<NumberedItem>
     1343<Text id="0505">Go to the folder <Path>Greenstone &rarr; collect &rarr; garish &rarr; macros</Path>. Copy the file <Path>extra.dm</Path>. Now go to your collection folder <Path>Greenstone &rarr; collect &rarr; tudor</Path> and create a new folder in there called <Path>macros</Path>. Paste <Path>extra.dm</Path> into that new folder. The overall effect is that you have created a new file <Path>Greenstone &rarr; collect &rarr; tudor &rarr; macros &rarr; extra.dm</Path>.</Text>
     1344</NumberedItem>
     1345<NumberedItem>
     1346<Text id="0505a">This macro file uses a CSS style file and some images which you will also need to copy from the garish collection. Go to the folder <Path>Greenstone &rarr; collect &rarr; garish &rarr; images</Path>. Select the three files <Path>style.css</Path>, <Path>horzline.gif</Path> and <Path>bg_blue.gif</Path>. <b>Copy</b> these files and paste them into the <Path>Greenstone &rarr; collect &rarr; tudor &rarr; images</Path> folder.</Text>
     1347</NumberedItem>
     1348<NumberedItem>
     1349<Text id="0507">Go to the <AutoText key="glidict::GUI.Create"/> panel and click <AutoText key="glidict::CreatePane.Preview_Collection" type="button"/>. The content of your collection remains the same, but its appearance has changed completely&mdash;for example, all the pages are pink! To learn about how to control these changes, go to the documented example collection called <i>Garish version of demo collection</i>, and read about it.</Text>
    13501350</NumberedItem>
    13511351<Heading>
    … …  
    13591359</NumberedItem>
    13601360<NumberedItem>
    1361 <Text id="0515">Go to the folder <i>C:\Program Files\Greenstone\etc</i> and edit the file called <i>main.cfg</i>. This is Greenstone's main configuration file, and contains a list of the macros that will be loaded in on startup. One of them, <i>home.dm</i>, dictates how the Greenstone home page will look, which is specified in the file <i>C:\Program Files\Greenstone\macros\home.dm</i>. This <i>macros</i> folder contains an alternative version, called <i>yourhome.dm</i>, which is not currently being used. To use it instead, in <i>main.cfg</i> change the string <i>home.dm</i> to <i>yourhome.dm</i>.</Text>
     1361<Text id="0515">Go to the folder <Path>Greenstone &rarr; etc</Path> and edit the file called <Path>main.cfg</Path>. This is Greenstone's main configuration file, and contains a list of the macros that will be loaded in on startup. One of them, <Path>home.dm</Path>, dictates how the Greenstone home page will look, which is specified in the file <Path>Greenstone &rarr; macros &rarr; home.dm</Path>. This <Path>macros</Path> folder contains an alternative version, called <Path>yourhome.dm</Path>, which is not currently being used. To use it instead, in <Path>main.cfg</Path> change the string <AutoText text="home.dm" type="quoted"/> to <AutoText text="yourhome.dm" type="quoted"/>.</Text>
    13621362</NumberedItem>
    13631363<NumberedItem>
    … …  
    13651365</NumberedItem>
    13661366<NumberedItem>
    1367 <Text id="0517">Instead of substituting <i>yourhome.dm</i> for <i>home.dm</i> in the file <i>main.cfg</i>, you could have simply edited <i>home.dm</i> and left <i>main.cfg</i> as it is. However, we wanted to preserve <i>home.dm</i> so that you could revert to your original Greenstone home page! Do this now by editing <i>main.cfg</i> and changing the string <i>yourhome.dm</i> back to <i>home.dm</i>. You will need to re-start Greenstone for this to take effect.</Text>
     1367<Text id="0517">Instead of substituting <AutoText text="yourhome.dm" type="quoted"/> for <AutoText text="home.dm" type="quoted"/> in the file <Path>main.cfg</Path>, you could have simply edited <Path>home.dm</Path> and left <Path>main.cfg</Path> as it is. However, we wanted to preserve <Path>home.dm</Path> so that you could revert to your original Greenstone home page! Do this now by editing <Path>main.cfg</Path> and changing the string <AutoText text="yourhome.dm" type="quoted"/> back to <AutoText text="home.dm" type="quoted"/>. You will need to re-start Greenstone for this to take effect.</Text>
    13681368</NumberedItem>
    13691369<Comment>
    … …  
    13801380<Content>
    13811381<NumberedItem>
    1382 <Text id="0521">Start a new collection called <b>Beatles Bibliography</b>. Enter the requested information and make it a <b>New Collection</b>. There is no need to include any metadata sets because the metadata extracted from the MARC records will appear as extracted metadata. Deselect the <b>Dublin Core</b> metadata set, and click &lt;<b>OK</b>&gt;.</Text>
    1383 <Text id="0521a">A <b>No metadata Sets Selected</b> warning message will pop-up, alerting you to the fact that you won't be able to manually assign metadata to the collection. In this collection, all the metadata will come from the MARC file; click &lt;<b>OK</b>&gt; to continue. (If you don't want to see this popup again, tick the <b>Do not show this warning again</b> checkbox.)</Text>
    1384 </NumberedItem>
    1385 <NumberedItem>
    1386 <Text id="0522">In the <b>Gather</b> panel, open the <i>marc</i> folder, drag <b>locbeatles50.marc</b> into the right-hand pane and drop it there. A popup window asks whether you want to add <b>MARCPlug</b> to the collection to process this file. Click &lt;<b>Add Plugin</b>&gt;, because this plugin will be needed to process the MARC records.</Text>
    1387 </NumberedItem>
    1388 <NumberedItem>
    1389 <Text id="0523">Remove the plugins <b>TextPlug</b> to <b>NULPlug</b> by selecting each one in the <b>Currently Assigned Plugins</b> list and clicking &lt;<b>Remove Plugin</b>&gt; (<b>ZIPPlug</b>, <b>GAPlug</b> and <b>MARCPlug</b> 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 accidentally including stray documents.</Text>
    1390 </NumberedItem>
    1391 <NumberedItem>
    1392 <Text id="0524">Now select <b>Browsing Classifiers</b> within the <b>Design</b> panel and <b>remove</b> the default classifier for <b>Source</b> metadata. In this collection all records are from the same file, so <b>Source</b> metadata, which is set to the filename, is not particularly interesting.</Text>
    1393 </NumberedItem>
    1394 <NumberedItem>
    1395 <Text id="0525">Switch to the <b>Create</b> panel, <b>build </b>the collection, and <b>preview</b> it. Browse through the <b>titles a-z</b> and view a record or two. Try searching&mdash;for example, find items that include <b>George Martin</b>.</Text>
    1396 </NumberedItem>
    1397 <NumberedItem>
    1398 <Text id="0526">Add an <b>AZCompactList</b> classifier for the <b>Subject</b> metadata. Select this item from the relevant menu of the <b>Browsing Classifiers </b>section of the <b>Design</b> panel and click <b>&lt;Add Classifier...&gt;</b>. In the popup window, select <b>ex.Subject </b>as the metadata item.</Text>
    1399 <Comment>
    1400 <Text id="0527"><b>AZCompactList</b> is like <b>AZList,</b> 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>
     1382<Text id="0521">Start a new collection called <b>Beatles Bibliography</b>. Enter the requested information and make it a <b>New Collection</b>. There is no need to include any metadata sets because the metadata extracted from the MARC records will appear as extracted metadata. Deselect the <b>Dublin Core</b> metadata set, and click <AutoText key="glidict::General.OK" type="button"/>.</Text>
     1383<Text id="0521a">A <AutoText key="glidict::NoMetadataSetsSelected.Title"/> warning message will pop-up, alerting you to the fact that you won't be able to manually assign metadata to the collection. In this collection, all the metadata will come from the MARC file; click <AutoText key="glidict::General.OK" type="button"/> to continue. (If you don't want to see this popup again, tick the <AutoText key="glidict::WarningDialog.Dont_Show_Again"/> checkbox.)</Text>
     1384</NumberedItem>
     1385<NumberedItem>
     1386<Text id="0522">In the <AutoText key="glidict::GUI.Gather"/> panel, open the <Path>marc</Path> folder, drag <Path>locbeatles50.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.Add" type="button"/>, because this plugin will be needed to process the MARC records.</Text>
     1387</NumberedItem>
     1388<NumberedItem>
     1389<Text id="0523">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" /> 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 accidentally including stray documents.</Text>
     1390</NumberedItem>
     1391<NumberedItem>
     1392<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. In this collection all records are from the same file, so <b>Source</b> metadata, which is set to the filename, is not particularly interesting.</Text>
     1393</NumberedItem>
     1394<NumberedItem>
     1395<Text id="0525">Switch to the <AutoText key="glidict::GUI.Create"/> panel, <b>build</b> the collection, and <b>preview</b> it. Browse through the <b>titles a-z</b> and view a record or two. Try searching&mdash;for example, find items that include <AutoText text="George Martin"/>.</Text>
     1396</NumberedItem>
     1397<NumberedItem>
     1398<Text id="0526">Add an <AutoText text="AZCompactList" /> classifier for the <b>Subject</b> metadata. Select this item from the relevant menu of the <AutoText key="glidict::CDM.GUI.Classifiers"/> section of the <AutoText key="glidict::GUI.Design"/> panel and click <AutoText key="glidict::CDM.ClassifierManager.Add" type="button"/>. In the popup window, select <AutoText key="metadata::ex.Subject"/> as the metadata item.</Text>
     1399<Comment>
     1400<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>
    14011401</Comment>
    14021402</NumberedItem>
    … …  
    14051405</NumberedItem>
    14061406<NumberedItem>
    1407 <Text id="0529">Make each bookshelf node show how many entries it contains by appending this to the <b>Format Features</b> for the <b>VList</b> format statement in the <b>Design</b> panel:</Text>
     1407<Text id="0529">Make each bookshelf node show how many entries it contains by appending this to the <AutoText key="glidict::CDM.GUI.Formats"/> for the <AutoText text="VList" /> format statement in the <AutoText key="glidict::GUI.Design"/> panel:</Text>
    14081408<Format>{If}{[numleafdocs],&lt;td&gt;&lt;i&gt;([numleafdocs])&lt;/i&gt;&lt;/td&gt;}</Format>
    14091409</NumberedItem>
    14101410<NumberedItem>
    1411 <Text id="0530">Click <b>&lt;Replace Format&gt;</b>, switch to the <b>Create</b> panel, and click <b>&lt;Preview Collection&gt;</b> (no need to build the collection again).</Text>
     1411<Text id="0530">Click <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/>, switch to the <AutoText key="glidict::GUI.Create"/> panel, and click <AutoText key="glidict::CreatePane.Preview_Collection" type="button"/> (no need to build the collection again).</Text>
    14121412</NumberedItem>
    14131413<Heading>
    … …  
    14151415</Heading>
    14161416<NumberedItem>
    1417 <Text id="0532">In the <b>Design</b> panel select <b>Search Types</b> from the left-hand list and activate the <b>Enable Advanced Searches</b> option.</Text>
    1418 </NumberedItem>
    1419 <NumberedItem>
    1420 <Text id="0532a">Add form searching to the collection by selecting <b>form</b> in the <b>Search Types</b> menu and clicking &lt;<b>Add Search Type</b>&gt;. Remove plain searching by selecting <b>plain</b> in the <b>Currently Assigned Search Types</b> list, and clicking &lt;<b>Remove Search Type</b>&gt;.</Text>
    1421 </NumberedItem>
    1422 <NumberedItem>
    1423 <Text id="0533"><b>Build</b> the collection once again, and <b>preview</b> the results. 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 <b>search</b> in the navigation bar. Note that the <i>Preferences </i>page has changed to control the advanced searching options.</Text>
     1417<Text id="0532">In the <AutoText key="glidict::GUI.Design"/> panel select <AutoText key="glidict::CDM.GUI.SearchTypes"/> from the left-hand list and activate the <AutoText key="glidict::CDM.SearchTypeManager.Enable"/> option.</Text>
     1418</NumberedItem>
     1419<NumberedItem>
     1420<Text id="0532a">Add form searching to the collection by selecting <AutoText text="form"/> in the <AutoText key="glidict::CDM.SearchTypeManager.SearchType_Selection"/> menu and clicking <AutoText key="glidict::CDM.SearchTypeManager.Add" type="button"/>. Remove plain searching by selecting <AutoText text="plain"/> in the <AutoText key="glidict::CDM.SearchTypeManager.Assigned"/> list, and clicking <AutoText key="glidict::CDM.SearchTypeManager.Remove" type="button"/>.</Text>
     1421</NumberedItem>
     1422<NumberedItem>
     1423<Text id="0533"><b>Build</b> the collection once again, and <b>preview</b> the results. 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_"/> page has changed to control the advanced searching options.</Text>
    14241424</NumberedItem>
    14251425<Comment>
    … …  
    14301430</Heading>
    14311431<NumberedItem>
    1432 <Text id="0536">From the <b>General</b> section of the <b>Design</b> panel, click the <b>&lt;Browse...&gt;</b> button next to the label <b>URL to 'about page' icon</b> and use the resulting popup file browser to access the folder <i>sample_files\marc</i>. Select <i>beatles_logo.jpg</i> and click &lt;<b>Open</b>&gt;.</Text>
     1432<Text id="0536">From the <AutoText key="glidict::CDM.GUI.General"/> section of the <AutoText key="glidict::GUI.Design"/> panel, click the <AutoText key="glidict::General.Browse" type="button"/> button next to the label <AutoText key="glidict::CDM.General.Icon_Collection"/> and use the resulting popup file browser to access the folder <Path>sample_files &rarr; marc</Path>. Select <Path>beatles_logo.jpg</Path> and click &lt;<b>Open</b>&gt;.</Text>
    14331433<Comment>
    14341434<Text id="0537">Greenstone copies the image into your collection area, so the collection will still work when the CD-ROM is removed from the drive.</Text>
    … …  
    14361436</NumberedItem>
    14371437<NumberedItem>
    1438 <Text id="0538">Repeat this process for the <b>URL to 'home page' icon</b>, selecting the same image.</Text>
     1438<Text id="0538">Repeat this process for the <AutoText key="glidict::CDM.General.Icon_Collection_Small"/>, selecting the same image.</Text>
    14391439</NumberedItem>
    14401440<NumberedItem>
    … …  
    14531453<Text id="0541">Copy the entire folder</Text>
    14541454<Path>sample_files &rarr; beatles &rarr; advbeat_large</Path>
    1455 <Text id="0542">(with all its contents) into your Greenstone <i>collect</i> folder. If you have installed Greenstone in the usual place, this is</Text>
     1455<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>
    14561456<Path>
    1457 <Text id="0542a">My Computer &rarr; Local Disk (C:) &rarr; Program Files &rarr; Greenstone &rarr; collect</Text>
     1457<Text id="0542a"><Path>My Computer &rarr; Local Disk (C:) &rarr; Program Files &rarr; Greenstone &rarr; collect</Path></Text>
    14581458</Path>
    1459 <Text id="0543">Put <i>advbeat_large</i> in there.</Text>
     1459<Text id="0543">Put <Path>advbeat_large</Path> in there.</Text>
    14601460</NumberedItem>
    14611461<NumberedItem>
    … …  
    14631463</NumberedItem>
    14641464<NumberedItem>
    1465 <Text id="0545">Explore the Beatles collection. Note how the <i>browse</i> button divides the material into seven different types. Within each category, the documents have appropriate icons. Some documents have an audio icon: when you click these you hear the music (assuming your computer is set up with appropriate player software). Others have an image thumbnail: when you click these you see the images.</Text>
    1466 </NumberedItem>
    1467 <NumberedItem>
    1468 <Text id="0546">Look at the <i>titles a-z</i> browser. Each title has a bookshelf that may include several related items. For example, <i>Hey Jude</i> has a cover image, MP3 audio and MIDI versions, lyrics, and a discography item.</Text>
    1469 </NumberedItem>
    1470 <NumberedItem>
    1471 <Text id="0547">Observe the low quality of the metadata. For example, the four items under <i>A Hard Day's Night</i> (under "H" in the <i>titles a-z</i> browser) have different variants as their titles. The collection would have been easier to organize had the metadata been cleaned up manually first, but that would be a big job. Only a tiny amount of metadata was added by hand&mdash;fewer than ten items. The original metadata was left untouched and Greenstone facilities used to clean it up automatically. (You will find in <TutorialRef id="multimedia_collection_build"/> that this is possible but tricky.)</Text>
     1465<Text id="0545">Explore the Beatles collection. Note how the <AutoText key="coredm::_Global:labelBrowse_"/> button divides the material into seven different types. Within each category, the documents have appropriate icons. Some documents have an audio icon: when you click these you hear the music (assuming your computer is set up with appropriate player software). Others have an image thumbnail: when you click these you see the images.</Text>
     1466</NumberedItem>
     1467<NumberedItem>
     1468<Text id="0546">Look at the <AutoText key="coredm::_Global:labelTitle_"/> browser. Each title has a bookshelf that may include several related items. For example, <AutoText text="Hey Jude"/> has a cover image, MP3 audio and MIDI versions, lyrics, and a discography item.</Text>
     1469</NumberedItem>
     1470<NumberedItem>
     1471<Text id="0547">Observe the low quality of the metadata. For example, the four items under <AutoText text="A Hard Day's Night"/> (under <AutoText text="H" type="qupted"/> in the <AutoText key="coredm::_Global:labelTitle_"/> browser) have different variants as their titles. The collection would have been easier to organize had the metadata been cleaned up manually first, but that would be a big job. Only a tiny amount of metadata was added by hand&mdash;fewer than ten items. The original metadata was left untouched and Greenstone facilities used to clean it up automatically. (You will find in <TutorialRef id="multimedia_collection_build"/> that this is possible but tricky.)</Text>
    14721472</NumberedItem>
    14731473<NumberedItem>
    14741474<Text id="0548">In the Windows file browser, take a look at the files that makes up the collection, in the</Text>
    14751475<Path>sample_files &rarr; beatles &rarr; advbeat_large &rarr; import</Path>
    1476 <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>cover_images </i>contains album covers in JPEG format. For each type, drill down through the hierarchy and look at a sample document.</Text>
     1476<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, <Path>html_lyrics</Path> and <Path>discography</Path> are excerpts of web sites, and <Path>cover_images</Path> contains album covers in JPEG format. For each type, drill down through the hierarchy and look at a sample document.</Text>
    14771477</NumberedItem>
    14781478</Content>
    … …  
    14901490</Comment>
    14911491<NumberedItem>
    1492 <Text id="0552">Start a new collection (<Menu>File &rarr; New</Menu>) called <b>small_beatles</b>, basing it on the default "New Collection." (Basing it on the existing Advanced Beatles collection would make your life far easier, but we want you to learn how to build it from scratch!) Fill out the fields with appropriate information. Use the Dublin Core metadata set (set by default).</Text>
     1492<Text id="0552">Start a new collection (<Menu><AutoText key="glidict::Menu.File"/> &rarr; <AutoText key="glidict::Menu.File_New"/></Menu>) called <b>small_beatles</b>, basing it on the default "New Collection." (Basing it on the existing Advanced Beatles collection would make your life far easier, but we want you to learn how to build it from scratch!) Fill out the fields with appropriate information. Use the Dublin Core metadata set (set by default).</Text>
    14931493</NumberedItem>
    14941494<NumberedItem>
    14951495<Text id="0554">Copy the files provided in</Text>
    14961496<Path>sample_files &rarr; beatles &rarr; advbeat_small</Path>
    1497 <Text id="0555">into your new collection. Do this by opening up <i>advbeat_small</i>,<i> </i>selecting the eight items within it (from <i>cover_images</i> to <i>beatles_midi.zip</i>), and dragging them across. Because some of these files are in MP3 and MARC formats you will be asked whether to include <b>MP3Plug</b> and <b>MARCPlug</b> in your collection. Click &lt;<b>Add Plugin</b>&gt;.</Text>
    1498 </NumberedItem>
    1499 <NumberedItem>
    1500 <Text id="0556">Change to the <b>Enrich</b> panel and browse around the files. There is no metadata&mdash;yet. Recall that you can double-click files to view them.</Text>
     1497<Text id="0555">into your new collection. Do this by opening up <Path>advbeat_small</Path>, selecting the eight items within it (from <Path>cover_images</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.Add" type="button"/>.</Text>
     1498</NumberedItem>
     1499<NumberedItem>
     1500<Text id="0556">Change to the <AutoText key="glidict::GUI.Enrich"/> panel and browse around the files. There is no metadata&mdash;yet. Recall that you can double-click files to view them.</Text>
    15011501<Text id="0557">(There are no MIDI files in the collection: these require more advanced customisation because there is no MIDI plugin. We will deal with them later.)</Text>
    15021502</NumberedItem>
    15031503<NumberedItem>
    1504 <Text id="0558">Change to the <b>Create</b> panel and <b>build </b>the collection.</Text>
     1504<Text id="0558">Change to the <AutoText key="glidict::GUI.Create"/> panel and <b>build</b> the collection.</Text>
    15051505</NumberedItem>
    15061506<NumberedItem>
    … …  
    15111511</Heading>
    15121512<NumberedItem>
    1513 <Text id="0561">You might want to correct some of the metadata&mdash;for example, the atrocious misspelling in the titles "MAGICAL MISTERY TOUR." These documents are in the discography section, with filenames that contain the same misspelling. Locate one of them in the <b>Enrich</b> panel. Notice that the extracted metadata element <b>ex.Title</b> is now filled in, and misspelt. You cannot correct this element, for it is extracted from the file and will be re-extracted every time the collection is re-built.</Text>
    1514 </NumberedItem>
    1515 <NumberedItem>
    1516 <Text id="0562">Instead, add <b>dc.Title</b> metadata for these two files: "Magical Mystery Tour." Change to the <b>Enrich</b> panel, open the discography folder and drill down to the individual files. Set the <b>dc.Title</b> value for the two offending items.</Text>
    1517 </NumberedItem>
    1518 <Comment>
    1519 <Text id="0563">Now there's a twist. The <b>dc.Title</b> metadata won't appear in titles a-z because the classifier has been instructed to use <b>ex.Title</b>. But changing the classifier to use <b>dc.Title</b> would miss out all the extracted titles! Fortunately, there's a way of dealing with this by specifying a list of metadata names in the classifier.</Text>
    1520 </Comment>
    1521 <NumberedItem>
    1522 <Text id="0564">Change to the <b>Design</b> panel and select the <b>Browsing Classifiers</b> section. Double-click the <b>Title</b> classifier (the first one) to edit its configuration settings.</Text>
     1513<Text id="0561">You might want to correct some of the metadata&mdash;for example, the atrocious misspelling in the titles "MAGICAL MISTERY TOUR." These documents are in the discography section, with filenames that contain the same misspelling. Locate one of them in the <AutoText key="glidict::GUI.Enrich"/> panel. Notice that the extracted metadata element <AutoText key="metadata::ex.Title"/> is now filled in, and misspelt. You cannot correct this element, for it is extracted from the file and will be re-extracted every time the collection is re-built.</Text>
     1514</NumberedItem>
     1515<NumberedItem>
     1516<Text id="0562">Instead, add <AutoText key="metadata::dc.Title"/> metadata for these two files: "Magical Mystery Tour." Change to the <AutoText key="glidict::GUI.Enrich"/> panel, open the discography folder and drill down to the individual files. Set the <AutoText key="metadata::dc.Title"/> value for the two offending items.</Text>
     1517</NumberedItem>
     1518<Comment>
     1519<Text id="0563">Now there's a twist. The <AutoText key="metadata::dc.Title"/> metadata won't appear in titles a-z because the classifier has been instructed to use <AutoText key="metadata::ex.Title"/>. But changing the classifier to use <AutoText key="metadata::dc.Title"/> would miss out all the extracted titles! Fortunately, there's a way of dealing with this by specifying a list of metadata names in the classifier.</Text>
     1520</Comment>
     1521<NumberedItem>
     1522<Text id="0564">Change to the <AutoText key="glidict::GUI.Design"/> panel and select the <AutoText key="glidict::CDM.GUI.Classifiers"/> section. Double-click the <AutoText key="metadata::ex.Title"/> classifier (the first one) to edit its configuration settings.</Text>
    15231523<BulletList>
    15241524<Bullet>
    1525 <Text id="0565">Type "dc.Title," before the <i>ex.Title </i>in the metadata box&mdash;i.e. make it read</Text>
     1525<Text id="0565">Type <Format><AutoText key="metadata::dc.Title" type="plain"/>,</Format> before the <Format><AutoText key="metadata::ex.Title" type="plain"/></Format> in the metadata box&mdash;i.e. make it read</Text>
    15261526<Format>
    1527 dc.Title,ex.Title
     1527<AutoText key="metadata::dc.Title" type="plain"/>,<AutoText key="metadata::ex.Title" type="plain"/>
    15281528</Format>
    1529 <Text id="0565a">and click <b>&lt;OK&gt;</b>.</Text>
     1529<Text id="0565a">and click <AutoText key="glidict::General.OK" type="button"/>.</Text>
    15301530</Bullet>
    15311531</BulletList>
    1532 <Text id="0566"><b>Build </b>the collection again, and <b>preview </b>it.</Text>
     1532<Text id="0566"><b>Build</b> the collection again, and <b>preview</b> it.</Text>
    15331533<Text id="0567">Extracted metadata is unreliable. But it is very cheap! On the other hand, manually assigned metadata is reliable, but expensive. The previous section of this exercise has shown how to aim for the best of both worlds by using extracted metadata but correcting it when it is wrong. While this may not satisfy the professional librarian, it could provide a useful compromise for the music teacher who wants to get their collection together with a minimum of effort.</Text>
    15341534</NumberedItem>
    … …  
    15371537</Heading>
    15381538<NumberedItem>
    1539 <Text id="0569">First let's remove the <b>AZList</b> classifier for filenames, which isn't very useful, and replace it with a browsing structure that groups documents by category (discography, lyrics, audio etc.). Categories are defined by manually assigned metadata.</Text>
     1539<Text id="0569">First let's remove the <AutoText text="AZList" /> classifier for filenames, which isn't very useful, and replace it with a browsing structure that groups documents by category (discography, lyrics, audio etc.). Categories are defined by manually assigned metadata.</Text>
    15401540<BulletList>
    15411541<Bullet>
    1542 <Text id="0570">Change to the <b>Enrich</b> panel, select the folder <i>cover_images</i> and set its <b>dc.Format</b> metadata value to "Images". Setting this value at the folder level means that all files within the folder inherit it.</Text>
    1543 </Bullet>
    1544 <Bullet>
    1545 <Text id="0571">Repeat the process. Assign "Discography" to the <i>discography</i> folder, "Lyrics" to <i>html_lyrics</i>, "MARC" to <i>marc</i>, "Audio" to <i>mp3</i>, "Tablature" to <i>tablature_txt</i>, and "Supplementary" to <i>wordpdf</i>.</Text>
    1546 </Bullet>
    1547 <Bullet>
    1548 <Text id="0572">Switch to the <b>Design</b> panel and select the <b>Browsing Classifiers </b>section.</Text>
    1549 </Bullet>
    1550 <Bullet>
    1551 <Text id="0573">Delete the <b>ex.Source </b>classifier (the second one).</Text>
    1552 </Bullet>
    1553 <Bullet>
    1554 <Text id="0574">Add an <b>AZCompactList</b> classifier. Select <b>dc.Format</b> as the metadata field and specify "browse" as the <b>buttonname</b>. Click the <b>sort</b> checkbox, and specify "Title" in the adjacent text box: this will make the classifier display documents in alphabetical order of title.</Text>
     1542<Text id="0570">Change to the <AutoText key="glidict::GUI.Enrich"/> panel, select the folder <Path>cover_images</Path> and set its <AutoText key="metadata::dc.Format"/> metadata value to "Images". Setting this value at the folder level means that all files within the folder inherit it.</Text>
     1543</Bullet>
     1544<Bullet>
     1545<Text id="0571">Repeat the process. Assign "Discography" to the <Path>discography</Path> folder, "Lyrics" to <Path>html_lyrics</Path>, "MARC" to <Path>marc</Path>, "Audio" to <Path>mp3</Path>, "Tablature" to <Path>tablature_txt</Path>, and "Supplementary" to <Path>wordpdf</Path>.</Text>
     1546</Bullet>
     1547<Bullet>
     1548<Text id="0572">Switch to the <AutoText key="glidict::GUI.Design"/> panel and select the <AutoText key="glidict::CDM.GUI.Classifiers"/> section.</Text>
     1549</Bullet>
     1550<Bullet>
     1551<Text id="0573">Delete the <AutoText key="metadata::ex.Source"/> classifier (the second one).</Text>
     1552</Bullet>
     1553<Bullet>
     1554<Text id="0574">Add an <AutoText text="AZCompactList" /> classifier. Select <AutoText key="metadata::dc.Format"/> as the <AutoText text="metadata"/> field and specify "browse" as the <AutoText text="buttonname"/>. Click the <AutoText text="sort"/> checkbox, and specify "Title" in the adjacent text box: this will make the classifier display documents in alphabetical order of title.</Text>
    15551555</Bullet>
    15561556</BulletList>
    … …  
    15641564<BulletList>
    15651565<Bullet>
    1566 <Text id="0581">Change to the <b>Design</b> panel and select the <b>Format Features</b> section.</Text>
    1567 </Bullet>
    1568 <Bullet>
    1569 <Text id="0582">Ensure that <b>VList</b> is selected, and make the changes that are highlighted below. You need to insert three lines into the first line, and delete the second line.<br/> <br/> Change:</Text>
     1566<Text id="0581">Change to the <AutoText key="glidict::GUI.Design"/> panel and select the <AutoText key="glidict::CDM.GUI.Formats"/> section.</Text>
     1567</Bullet>
     1568<Bullet>
     1569<Text id="0582">Ensure that <AutoText text="VList" /> is selected, and make the changes that are highlighted below. You need to insert three lines into the first line, and delete the second line.<br/> <br/> Change:</Text>
    15701570<Format>
    15711571&lt;td valign=top&gt;<highlight>[link][icon][/link]</highlight>&lt;/td&gt;<br/>
    … …  
    15851585</Bullet>
    15861586<Bullet>
    1587 <Text id="0584">Then click &lt;<b>Replace Format</b>&gt;.</Text>
     1587<Text id="0584">Then click <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/>.</Text>
    15881588</Bullet>
    15891589</BulletList>
    15901590<Text id="0585">To make this easier for you we have prepared a plain text file that contains the new text. In WordPad open the following file:</Text>
    15911591<Path>sample_files &rarr; beatles &rarr; format_tweaks &rarr; audio_tweak.txt</Path>
    1592 <Text id="0586">(Be sure to use WordPad rather than Notepad, because Notepad does not display the line breaks correctly.) Place it in the copy buffer by highlighting the text in WordPad and selecting <Menu>Edit &rarr; Copy</Menu>. Now move back to the Librarian Interface, highlight all the text that makes up the current VList format statement, and use <Menu>Edit &rarr; Paste</Menu> to transform the old statement to the new one. Remember to press &lt;<b>Replace Format</b>&gt; when finished.</Text>
     1592<Text id="0586">(Be sure to use WordPad rather than Notepad, because Notepad does not display the line breaks correctly.) Place it in the copy buffer by highlighting the text in WordPad and selecting <Menu>Edit &rarr; Copy</Menu>. Now move back to the Librarian Interface, highlight all the text that makes up the current VList format statement, and use <Menu><AutoText key="glidict::Menu.Edit"/> &rarr; <AutoText key="glidict::Menu.Edit_Paste"/></Menu> to transform the old statement to the new one. Remember to press <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/> when finished.</Text>
    15931593<Text id="0589"><b>Preview</b> the result. You may need to click the browser's &lt;<b>Reload</b>&gt; button to force it to re-load the page.</Text>
    15941594</NumberedItem>
    … …  
    15971597<BulletList>
    15981598<Bullet>
    1599 <Text id="0594">In the VList format feature, delete the text that is highlighted below:</Text>
     1599<Text id="0594">In the <AutoText text="VList"/> format feature, delete the text that is highlighted below:</Text>
    16001600<Format>
    16011601&lt;td valign=top&gt;<br/>
    … …  
    16061606</Bullet>
    16071607</BulletList>
    1608 <Text id="0595">Don't forget to click &lt;<b>Replace Format</b>&gt; after all this work! <b>Preview</b> the result (you don't need to build the collection.)</Text>
    1609 </NumberedItem>
    1610 <Heading>
    1611 <Text id="0596">Using AZCompactList rather than AZList</Text>
    1612 </Heading>
    1613 <NumberedItem>
    1614 <Text id="0597">There are sometimes several documents with the same title. For example, <i>All My Loving </i>appears both as lyrics and tablature (under <i>ALL MY LOVING</i>). The <i>titles a-z</i> browser might be improved by grouping these together under a bookshelf icon. This is a job for an <b>AZCompactList</b>.</Text>
     1608<Text id="0595">Don't forget to click <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/> after all this work! <b>Preview</b> the result (you don't need to build the collection.)</Text>
     1609</NumberedItem>
     1610<Heading>
     1611<Text id="0596">Using <AutoText text="AZCompactList"/> rather than <AutoText text="AZList"/></Text>
     1612</Heading>
     1613<NumberedItem>
     1614<Text id="0597">There are sometimes several documents with the same title. For example, <AutoText text="All My Loving" type="italics"/> appears both as lyrics and tablature (under <AutoText text="ALL MY LOVING" type="italics"/>). The <AutoText key="coredm::_Global:labelTitle_"/> browser might be improved by grouping these together under a bookshelf icon. This is a job for an <AutoText text="AZCompactList" />.</Text>
    16151615<BulletList>
    16161616<Bullet>
    1617 <Text id="0598">Change to the <b>Design</b> panel and select the <b>Browsing Classifiers </b>section.</Text>
    1618 </Bullet>
    1619 <Bullet>
    1620 <Text id="0599">Remove the <b>Title</b> classifier (at the top)</Text>
    1621 </Bullet>
    1622 <Bullet>
    1623 <Text id="0600">Add an <b>AZCompactList</b> classifier, and enter <b>dc.Title,ex.Title</b> as its metadata.</Text>
    1624 </Bullet>
    1625 <Bullet>
    1626 <Text id="0602">Finish by pressing &lt;<b>OK</b>&gt;.</Text>
    1627 </Bullet>
    1628 <Bullet>
    1629 <Text id="0603">Move the new classifier to the top of the list (<b>Move Up</b> button).</Text>
     1617<Text id="0598">Change to the <AutoText key="glidict::GUI.Design"/> panel and select the <AutoText key="glidict::CDM.GUI.Classifiers"/> section.</Text>
     1618</Bullet>
     1619<Bullet>
     1620<Text id="0599">Remove the <AutoText key="metadata::ex.Title"/> classifier (at the top)</Text>
     1621</Bullet>
     1622<Bullet>
     1623<Text id="0600">Add an <AutoText text="AZCompactList" /> classifier, and enter <AutoText key="metadata::dc.Title"/><b>,</b><AutoText key="metadata::ex.Title"/> as its metadata.</Text>
     1624</Bullet>
     1625<Bullet>
     1626<Text id="0602">Finish by pressing <AutoText key="glidict::General.OK" type="button"/>.</Text>
     1627</Bullet>
     1628<Bullet>
     1629<Text id="0603">Move the new classifier to the top of the list (<AutoText key="glidict::CDM.Move.Move_Up" type="button"/> button).</Text>
    16301630</Bullet>
    16311631</BulletList>
    1632 <Text id="0604"><b>Build </b>the collection again and <b>preview </b>it. Both items for <i>All My Loving </i>now appear under the same bookshelf. However, many entries haven't been amalgamated because of non-uniform titles: for example <i>A Hard Day's Night</i> appears as four different variants. We will learn below how to amalgamate these.</Text>
     1632<Text id="0604"><b>Build</b> the collection again and <b>preview</b> it. Both items for <AutoText text="All My Loving" type="italics"/> now appear under the same bookshelf. However, many entries haven't been amalgamated because of non-uniform titles: for example <AutoText text="A Hard Day's Night" type="italics"/> appears as four different variants. We will learn below how to amalgamate these.</Text>
    16331633</NumberedItem>
    16341634<Heading>
    … …  
    16361636</Heading>
    16371637<NumberedItem>
    1638 <Text id="0606">Make the bookshelves show how many documents they contain by inserting a line in the VList format statement in the <b>Format Features</b> section of the <b>Design</b> panel:</Text>
     1638<Text id="0606">Make the bookshelves show how many documents they contain by inserting a line in the <AutoText text="VList"/> format statement in the <AutoText key="glidict::CDM.GUI.Formats"/> section of the <AutoText key="glidict::GUI.Design"/> panel:</Text>
    16391639<Format>
    16401640&lt;td valign=top&gt;<br/>
    … …  
    16441644<highlight>&lt;td&gt;{If}{[numleafdocs],([numleafdocs])}&lt;/td&gt;</highlight><br/>
    16451645&lt;td valign=top&gt;[highlight] {Or}{[dls.Title],[dc.Title],[Title],Untitled} [/highlight]&lt;/td&gt;</Format>
    1646 <Text id="0607">You will find this text in <Path>format_tweaks &rarr; show_num_docs.txt</Path>, which can be copied and pasted in as before. Don't forget to click &lt;<b>Replace Format</b>&gt;.</Text>
     1646<Text id="0607">You will find this text in <Path>format_tweaks &rarr; show_num_docs.txt</Path>, which can be copied and pasted in as before. Don't forget to click <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/>.</Text>
    16471647<Text id="0609"><b>Preview</b> the result (you don't need to build the collection.)</Text>
    16481648</NumberedItem>
    16491649<NumberedItem>
    1650 <Text id="0610">Now turn to the images. Dummy documents are displayed here too. First change to the <b>Enrich</b> panel, open the folder <i>cover_images</i> and add <b>dc.Title</b> metadata, assigning to each of the ten documents the title of the corresponding album. Remember, you can double-click a file to view it.</Text>
    1651 </NumberedItem>
    1652 <NumberedItem>
    1653 <Text id="0611">To suppress the dummy documents, change the <b>VList</b> format statement in the <b>Format Features</b> section of the <b>Design</b> panel again by adding the two highlighted lines, and the close curly bracket:</Text>
     1650<Text id="0610">Now turn to the images. Dummy documents are displayed here too. First change to the <AutoText key="glidict::GUI.Enrich"/> panel, open the folder <Path>cover_images</Path> and add <AutoText key="metadata::dc.Title"/> metadata, assigning to each of the ten documents the title of the corresponding album. Remember, you can double-click a file to view it.</Text>
     1651</NumberedItem>
     1652<NumberedItem>
     1653<Text id="0611">To suppress the dummy documents, change the <AutoText text="VList" /> format statement in the <AutoText key="glidict::CDM.GUI.Formats"/> section of the <AutoText key="glidict::GUI.Design"/> panel again by adding the two highlighted lines, and the close curly bracket:</Text>
    16541654<Format>&lt;td valign=top&gt;<br/>
    16551655{If}{[dc.Format] eq 'Audio',<br/>
    … …  
    16621662</NumberedItem>
    16631663<NumberedItem>
    1664 <Text id="0612">In the <b>Browsing Classifiers</b> section on the <b>Design</b> panel, add a <b>Phind</b> classifier. Leave the settings at their defaults: this generates a phrase browsing classifier that sources its phrases from <i>Title</i> and <i>text</i>.</Text>
    1665 </NumberedItem>
    1666 <NumberedItem>
    1667 <Text id="0613">To complete the collection, use the browse button of <b>URL to 'about page' icon</b> in the <b>General</b> section of the <b>Design</b> panel to select the following image:</Text>
     1664<Text id="0612">In the <AutoText key="glidict::CDM.GUI.Classifiers"/> section on the <AutoText key="glidict::GUI.Design"/> panel, add a <AutoText text="Phind"/> classifier. Leave the settings at their defaults: this generates a phrase browsing classifier that sources its phrases from <i>Title</i> and <i>text</i>.</Text>
     1665</NumberedItem>
     1666<NumberedItem>
     1667<Text id="0613">To complete the collection, use the browse button of <AutoText key="glidict::CDM.General.Icon_Collection"/> in the <AutoText key="glidict::CDM.GUI.General"/> section of the <AutoText key="glidict::GUI.Design"/> panel to select the following image:</Text>
    16681668<Path>advbeatles_large &rarr; images &rarr; flick4.gif.</Path>
    16691669<Text id="0616"><b>Build</b> the collection again and <b>preview</b> it.</Text>
    … …  
    16731673</Comment>
    16741674<Heading>
    1675 <Text id="0623">Using UnknownPlug</Text>
     1675<Text id="0623">Using <AutoText text="UnknownPlug"/></Text>
    16761676</Heading>
    16771677<Comment>
    … …  
    16791679</Comment>
    16801680<NumberedItem>
    1681 <Text id="0627"><b>UnknownPlug</b> 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>
    1682 <Text id="0627a">In the <b>Document Plugins</b> section of the <b>Design</b> panel:</Text>
     1681<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>
     1682<Text id="0627a">In the <AutoText key="glidict::CDM.GUI.Plugins"/> section of the <AutoText key="glidict::GUI.Design"/> panel:</Text>
    16831683<BulletList>
    16841684<Bullet>
    1685 <Text id="0628">add <b>UnknownPlug</b>;</Text>
    1686 </Bullet>
    1687 <Bullet>
    1688 <Text id="0629">activate its <i>process_extension</i> field and set it to <i>mid</i> to make it recognize files with extension .<i>mid</i>;</Text>
    1689 </Bullet>
    1690 <Bullet>
    1691 <Text id="0630">Set <i>file_format</i> to "MIDI" and <i>mime_type</i> to "audio/midi".</Text>
     1685<Text id="0628">add <AutoText text="UnknownPlug" />;</Text>
     1686</Bullet>
     1687<Bullet>
     1688<Text id="0629">activate its <AutoText text="process_extension"/> field and set it to <AutoText text="mid" type="quoted"/> to make it recognize files with extension <AutoText text=".mid" type="italics"/>;</Text>
     1689</Bullet>
     1690<Bullet>
     1691<Text id="0630">Set <AutoText text="file_format"/> to <AutoText text="MIDI" type="quoted"/> and <AutoText text="mime_type"/> to <AutoText text="audio/midi" type="quoted"/>.</Text>
    16921692</Bullet>
    16931693</BulletList>
    1694 <Text id="0631">In this collection, all MIDI files are contained in the file <i>beatles_midi.zip</i>. <b>ZIPPlug</b> (already in the list of default plugins) is used to unpack the files and pass them down the list of plugins until they reach UnknownPlug.</Text>
    1695 </NumberedItem>
    1696 <NumberedItem>
    1697 <Text id="0632"><b>Build</b> the collection and <b>preview</b> it. Unfortunately the MIDI files don't appear as Audio under the <i>browse</i> button. That's because they haven't been assigned <b>dc.Format</b> metadata.</Text>
     1694<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>
     1695</NumberedItem>
     1696<NumberedItem>
     1697<Text id="0632"><b>Build</b> the collection and <b>preview</b> it. Unfortunately the MIDI files don't appear as Audio under the <i>browse</i> button. That's because they haven't been assigned <AutoText key="metadata::dc.Format"/> metadata.</Text>
    16981698<BulletList>
    16991699<Bullet>
    1700 <Text id="0633">Back in the <b>Enrich</b> panel, click on the file <i>beatles_midi.zip</i> and assign its <b>dc.Format</b> value to "Audio"&mdash;do this by clicking on "Audio" in the <b>Existing values for dc.Format</b> list. All files extracted from the Zip file inherit its settings.</Text>
     1700<Text id="0633">Back in the <AutoText key="glidict::GUI.Enrich"/> panel, click on the file <Path>beatles_midi.zip</Path> and assign its <AutoText key="metadata::dc.Format"/> value to "Audio"&mdash;do this by clicking on "Audio" in the <AutoText key="glidict::EnrichPane.ExistingValues" args="dc.Format"/> list. All files extracted from the Zip file inherit its settings.</Text>
    17011701</Bullet>
    17021702</BulletList>
    … …  
    17061706</Heading>
    17071707<Comment>
    1708 <Text id="0618a">We now clean up the <i>titles a-z</i> browser.</Text>
    1709 </Comment>
    1710 <Comment>
    1711 <Text id="0621">To do this we must put the Librarian Interface into a different mode. The interface supports four levels of user: Library Assistants, who can add documents and metadata to collections, and create new ones whose structure mirrors that of existing collections; Librarians, who can, in addition, design new collections, but cannot use specialist IT features (e.g. regular expressions); Library Systems Specialists, who can use all design features, but cannot perform troubleshooting tasks (e.g. interpreting debugging output from Perl programs); and Experts, who can perform all functions.</Text>
    1712 </Comment>
    1713 <Comment>
    1714 <Text id="0622">So far you have mostly been operating in Librarian mode. We switch to Library Systems Specialist mode for the next exercise.</Text>
    1715 </Comment>
    1716 <NumberedItem>
    1717 <Text id="0624">To switch modes, click <Menu>File &rarr; Preferences &rarr; Mode</Menu> and change to <b>Library Systems Specialist</b>. 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>
    1718 </NumberedItem>
    1719 <NumberedItem>
    1720 <Text id="0635">Next we return to our <i>titles a-z</i> browser and clean it up. The aim is to amalgamate variants of titles by stripping away extraneous text. For example, we would like to treat "ANTHOLOGY 1", "ANTHOLOGY 2" and "ANTHOLOGY 3" the same for grouping purposes. To achieve this:</Text>
     1708<Text id="0618a">We now clean up the <AutoText key="coredm::_Global:labelTitle_"/> browser.</Text>
     1709</Comment>
     1710<Comment>
     1711<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.Assistant"/>, 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>
     1712</Comment>
     1713<Comment>
     1714<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>
     1715</Comment>
     1716<NumberedItem>
     1717<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>
     1718</NumberedItem>
     1719<NumberedItem>
     1720<Text id="0635">Next we return to our <AutoText key="coredm::_Global:labelTitle_"/> browser and clean it up. The aim is to amalgamate variants of titles by stripping away extraneous text. For example, we would like to treat <AutoText text="ANTHOLOGY 1" type="quoted"/>, <AutoText text="ANTHOLOGY 2" type="quoted"/> and <AutoText text="ANTHOLOGY 3" type="quoted"/> the same for grouping purposes. To achieve this:</Text>
    17211721<BulletList>
    17221722<Bullet>
    1723 <Text id="0636">Go to the Title <b>AZCompactList</b> under <b>Browsing Classifiers</b> on the <b>Design</b> panel;</Text>
    1724 </Bullet>
    1725 <Bullet>
    1726 <Text id="0637">Activate <b>removesuffix</b> and set it to:</Text>
     1723<Text id="0636">Go to the Title <AutoText text="AZCompactList" /> under <AutoText key="glidict::CDM.GUI.Classifiers"/> on the <AutoText key="glidict::GUI.Design"/> panel;</Text>
     1724</Bullet>
     1725<Bullet>
     1726<Text id="0637">Activate <AutoText text="removesuffix"/> and set it to:</Text>
    17271727<Format>(?i)(\\s+\\d+)|(\\s+[[:punct:]].*)</Format>
    17281728</Bullet>
    17291729</BulletList>
    1730 <Text id="0638"><b>Build</b> the collection and <b>preview</b> the result. Observe how many more times similar titles have been amalgamated under the same bookshelf. Test your understanding of regular expressions by trying to rationalize the amalgamations. (Note: <i>[[:punct:]]</i> stands for any punctuation character.) The icons beside the Word and PDF documents are not the correct ones, but that will be fixed in the next format statement.</Text>
    1731 </NumberedItem>
    1732 <Comment>
    1733 <Text id="0639">The previous exercise was done in Librarian Systems Specialist mode because it requires the use of regular expressions, something librarians are not normally trained in.</Text>
    1734 </Comment>
    1735 <Comment>
    1736 <Text id="0640">One powerful use of regular expressions in the exercise was to clean up the <i>titles a-z</i> browser. Perhaps the best way of doing this would be to have proper title metadata. The metadata extracted from HTML files is messy and inconsistent, and this was reflected in the original titles a-z browser. Defining proper title metadata would be simple but rather laborious. Instead, we have opted to use regular expressions in the <i>AZCompactList</i> classifier to clean up the title metadata. This is difficult to understand, and a bit fiddly to do, but if you can cope with its idiosyncrasies it provides a quick way to clean up the extracted metadata and avoid having to enter a large amount of metadata.</Text>
     1730<Text id="0638"><b>Build</b> the collection and <b>preview</b> the result. Observe how many more times similar titles have been amalgamated under the same bookshelf. Test your understanding of regular expressions by trying to rationalize the amalgamations. (Note: <AutoText text="[[:punct:]]" type="italics"/> stands for any punctuation character.) The icons beside the Word and PDF documents are not the correct ones, but that will be fixed in the next format statement.</Text>
     1731</NumberedItem>
     1732<Comment>
     1733<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>
     1734</Comment>
     1735<Comment>
     1736<Text id="0640">One powerful use of regular expressions in the exercise was to clean up the <AutoText key="coredm::_Global:labelTitle_"/> browser. Perhaps the best way of doing this would be to have proper title metadata. The metadata extracted from HTML files is messy and inconsistent, and this was reflected in the original titles a-z browser. Defining proper title metadata would be simple but rather laborious. Instead, we have opted to use regular expressions in the <AutoText text="AZCompactList"/> classifier to clean up the title metadata. This is difficult to understand, and a bit fiddly to do, but if you can cope with its idiosyncrasies it provides a quick way to clean up the extracted metadata and avoid having to enter a large amount of metadata.</Text>
    17371737</Comment>
    17381738<Heading>
    … …  
    17471747</NumberedItem>
    17481748<NumberedItem>
    1749 <Text id="0646">Copy the <i>images</i> and <i>macros</i> folders located there into your collection's top-level folder. (It's OK to overwrite the existing <i>images</i> folder: the image in it is included in the folder being copied.) The <i>images</i> folder includes some useful icons, and the <i>macros</i> folder defines some macro names that use these images. To see the macro definitions, take a look by using a text editor to open the file <i>extra.dm</i> in the <i>macros</i> folder.</Text>
     1749<Text id="0646">Copy the <Path>images</Path> and <Path>macros</Path> folders located there into your collection's top-level folder. (It's OK to overwrite the existing <Path>images</Path> folder: the image in it is included in the folder being copied.) The <Path>images</Path> folder includes some useful icons, and the <Path>macros</Path> folder defines some macro names that use these images. To see the macro definitions, take a look by using a text editor to open the file <Path>extra.dm</Path> in the <Path>macros</Path> folder.</Text>
    17501750</NumberedItem>
    17511751<Heading>
    … …  
    17531753</Heading>
    17541754<NumberedItem>
    1755 <Text id="0648">Re-Edit your <b>VList</b> format statement to be the following (in <Menu>Design &rarr; Format Features</Menu>)</Text>
     1755<Text id="0648">Re-Edit your <AutoText text="VList" /> format statement to be the following (in <AutoText key="glidict::CDM.GUI.Formats"/> on the <AutoText key="glidict::GUI.Design"/> panel)</Text>
    17561756<Format><highlight>&lt;td valign=top&gt;</highlight><br/>
    17571757&nbsp;&nbsp;<highlight>{If}{[numleafdocs],[link][icon][/link]}</highlight><br/>
    … …  
    17771777</NumberedItem>
    17781778<NumberedItem>
    1779 <Text id="0651"><b>Preview</b> your collection as before. Now different icons are used for discography, lyrics, tablature, and MARC metadata. Even MP3 and MIDI audio file types are distinguished. If you let the mouse hover over one of these images a "tool tip" appears explaining what file type the icon represents in the current interface language (note: <i>extra.dm</i> only defines English and French).</Text>
     1779<Text id="0651"><b>Preview</b> your collection as before. Now different icons are used for discography, lyrics, tablature, and MARC metadata. Even MP3 and MIDI audio file types are distinguished. If you let the mouse hover over one of these images a "tool tip" appears explaining what file type the icon represents in the current interface language (note: <Path>extra.dm</Path> only defines English and French).</Text>
    17801780</NumberedItem>
    17811781<Heading>
    … …  
    17831783</Heading>
    17841784<NumberedItem>
    1785 <Text id="0653">Open your collection's <i>macros</i> folder and locate the <i>extra.dm</i> file within it. <b>Right-click </b>on it. If prompted, select <b>WordPad</b> as the application to open it with.</Text>
     1785<Text id="0653">Open your collection's <Path>macros</Path> folder and locate the <Path>extra.dm</Path> file within it. <b>Right-click</b> on it. If prompted, select <b>WordPad</b> as the application to open it with.</Text>
    17861786</NumberedItem>
    17871787<NumberedItem>
    … …  
    18111811}
    18121812</Format>
    1813 <Text id="0656">A hash (#) at the start of line signals a comment, and Greenstone ignores the following text. We use this to comment out the original statements and replace them with modified lines. It is useful to retain the original version in case we need to restore the original lines at a later date. These lines relate to the background image used. The new image <i>tile.jpg</i> was also in the <i>images</i> folder that was copied across previously.</Text>
     1813<Text id="0656">A hash (#) at the start of line signals a comment, and Greenstone ignores the following text. We use this to comment out the original statements and replace them with modified lines. It is useful to retain the original version in case we need to restore the original lines at a later date. These lines relate to the background image used. The new image <Path>tile.jpg</Path> was also in the <Path>images</Path> folder that was copied across previously.</Text>
    18141814</NumberedItem>
    18151815<NumberedItem>
    … …  
    18211821</NumberedItem>
    18221822<NumberedItem>
    1823 <Text id="0660">If you want to you can reverse the most recent change you made by commenting out the new lines added (add #) and uncommenting the original lines (delete # character). Remember to save the file. To undo all the customized changes made, delete the content of the <i>macros</i> and <i>images</i> folders.</Text>
     1823<Text id="0660">If you want to you can reverse the most recent change you made by commenting out the new lines added (add #) and uncommenting the original lines (delete # character). Remember to save the file. To undo all the customized changes made, delete the content of the <Path>macros</Path> and <Path>images</Path> folders.</Text>
    18241824</NumberedItem>
    18251825<Heading>
    … …  
    18301830<BulletList>
    18311831<Bullet>
    1832 <Text id="0663">Close the current collection (<Menu>File &rarr; Close</Menu>).</Text>
    1833 </Bullet>
    1834 <Bullet>
    1835 <Text id="0664">Start a new collection called <i>advbeat</i> (<Menu>File &rarr; New</Menu>).</Text>
     1832<Text id="0663">Close the current collection (<Menu><AutoText key="glidict::Menu.File"/> &rarr; <AutoText key="glidict::Menu.File_Close"/></Menu>).</Text>
     1833</Bullet>
     1834<Bullet>
     1835<Text id="0664">Start a new collection called <i>advbeat</i> (<Menu><AutoText key="glidict::Menu.File"/> &rarr; <AutoText key="glidict::Menu.File_New"/></Menu>).</Text>
    18361836</Bullet>
    18371837<Bullet>
    … …  
    18421842</Bullet>
    18431843<Bullet>
    1844 <Text id="0670"><b>Build</b> the collection and preview the result. (If you want the collection to have an icon, you will have to add it from the <b>Design</b> panel.)</Text>
     1844<Text id="0670"><b>Build</b> the collection and preview the result. (If you want the collection to have an icon, you will have to add it from the <AutoText key="glidict::GUI.Design"/> panel.)</Text>
    18451845</Bullet>
    18461846</BulletList>
    … …  
    18501850</Heading>
    18511851<NumberedItem>
    1852 <Text id="0672">Switch to the <b>Design</b> panel and select the <b>Browsing Classifiers</b> section. Pull down the <b>select classifier to add</b> menu and select <b>Collage</b>. Click &lt;<b>Add Classifier...</b>&gt;. There is no need to customize the options, so click &lt;<b>OK</b>&gt; at the bottom of the resulting popup.</Text>
    1853 </NumberedItem>
    1854 <NumberedItem>
    1855 <Text id="0673">Now change to the <b>Create</b> panel and <b>build</b> and <b>preview</b> the collection.</Text>
     1852<Text id="0672">Switch to the <AutoText key="glidict::GUI.Design"/> panel and select the <AutoText key="glidict::CDM.GUI.Classifiers"/> section. Pull down the <AutoText key="glidict::CDM.ClassifierManager.Classifier"/> menu and select <AutoText text="Collage"/>. Click <AutoText key="glidict::CDM.ClassifierManager.Add" type="button"/>. There is no need to customize the options, so click <AutoText key="glidict::General.OK" type="button"/> at the bottom of the resulting popup.</Text>
     1853</NumberedItem>
     1854<NumberedItem>
     1855<Text id="0673">Now change to the <AutoText key="glidict::GUI.Create"/> panel and <b>build</b> and <b>preview</b> the collection.</Text>
    18561856</NumberedItem>
    18571857</Content>
    … …  
    18681868</Comment>
    18691869<Comment>
    1870 <Text id="0676">The collection involves a mixture of plug-ins, classifiers, and format statements. The bulk of the work is done by PagedImgPlug, a plug-in designed precisely for the kind of data we have in this example. For each document, an "item" 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 Te Whetu o Te Tau) have text representations, and two (from Te Waka o Te Iwi) have images only. Item files can also specify metadata. In our example the newspaper series is recorded as ex.Title and its date of publication as ex.Date. This metadata is extracted as part of the building process.</Text>
    1871 </Comment>
    1872 <NumberedItem>
    1873 <Text id="0677">Start a new collection called <b>Paged Images</b> and fill out the fields with appropriate information: it is a collection sourced from an excerpt of Niupepa documents; the only metadata used is document title and date, and these are extracted from the "item" files included in the source documents so no metadata set need be stipulated.</Text>
    1874 </NumberedItem>
    1875 <NumberedItem>
    1876 <Text id="0678">In <Menu>Design &rarr; Document Plugins</Menu>, add <b>PagedImgPlug</b>. Switch on its <b>screenview</b> 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 <i>screenview</i> option generates smaller screen-resolution images of each page when the collection is built.</Text>
    1877 </NumberedItem>
    1878 <NumberedItem>
    1879 <Text id="0679">In the <b>Gather </b>panel, open the <i>niupepa\sample_items </i>folder in <i>sample_files </i>and drag it into your collection on the right-hand side.</Text>
    1880 </NumberedItem>
    1881 <NumberedItem>
    1882 <Text id="0680">Some of the files you have just dragged in are text files that contain the text extracted from page images. We want these to be processed by <b>PagedImgPlug</b>, not <b>TEXTPlug</b>. Switch to the <b>Design</b> panel and delete <b>TEXTPlug</b>. While you are at it, you could tidy things up by deleting <b>HTMLPlug</b>, <b>EMAILPlug</b>, <b>PDFPlug</b>, <b>RTFPlug</b>, <b>WordPlug</b>, <b>PSPlug</b>, <b>ISISPlug</b> and <b>NULPlug</b> as well, since they will not be used.</Text>
    1883 </NumberedItem>
    1884 <NumberedItem>
    1885 <Text id="0681">Now go to the <b>Create</b> panel, <b>build</b> the collection and <b>preview</b> the result. Search for <i>waka</i> and view one of the titles listed (all three appear as <i>Te Whetu o Te Tau</i>). Browse by <i>titles a-z </i>and view one of the <i>Te Waka o Te Iwi</i> titles.</Text>
     1870<Text id="0676">The collection involves a mixture of plug-ins, classifiers, and format statements. The bulk of the work is done by <AutoText text="PagedImgPlug"/>, a plug-in 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"/>. This metadata is extracted as part of the building process.</Text>
     1871</Comment>
     1872<NumberedItem>
     1873<Text id="0677">Start a new collection called <b>Paged Images</b> and fill out the fields with appropriate information: it is a collection sourced from an excerpt of Niupepa documents; the only metadata used is document title and date, and these are extracted from the <AutoText text="item" type="quoted"/> files included in the source documents so no metadata set need be stipulated.</Text>
     1874</NumberedItem>
     1875<NumberedItem>
     1876<Text id="0678">In the <AutoText key="glidict::CDM.GUI.Plugins"/> section on the <AutoText key="glidict::GUI.Design"/> panel, add <AutoText text="PagedImgPlug" />. 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.</Text>
     1877</NumberedItem>
     1878<NumberedItem>
     1879<Text id="0679">In the <AutoText key="glidict::GUI.Gather"/> panel, open the <Path>niupepa &rarr; sample_items</Path> folder in <Path>sample_files</Path> and drag it into your collection on the right-hand side.</Text>
     1880</NumberedItem>
     1881<NumberedItem>
     1882<Text id="0680">Some of the files you have just dragged in are text files that contain the text extracted from page images. We want these to be processed by <AutoText text="PagedImgPlug" />, not <AutoText text="TEXTPlug" />. Switch to the <AutoText key="glidict::GUI.Design"/> panel and delete <AutoText text="TEXTPlug" />. While you are at it, you could tidy things up by deleting <AutoText text="HTMLPlug" />, <AutoText text="EMAILPlug" />, <AutoText text="PDFPlug" />, <AutoText text="RTFPlug" />, <AutoText text="WordPlug" />, <AutoText text="PSPlug" />, <AutoText text="ISISPlug" /> and <AutoText text="NULPlug" /> as well, since they will not be used.</Text>
     1883</NumberedItem>
     1884<NumberedItem>
     1885<Text id="0681">Now go to the <AutoText key="glidict::GUI.Create"/> panel, <b>build</b> the collection and <b>preview</b> the result. Search for <AutoText text="waka" type="quoted"/> and view one of the titles listed (all three appear as <AutoText text="Te Whetu o Te Tau" type="italics"/>). Browse by <AutoText key="coredm::_Global:labelTitle_"/> and view one of the <AutoText text="Te Waka o Te Iwi" type="italics"/> titles.</Text>
    18861886</NumberedItem>
    18871887<Comment>
    … …  
    18921892</Heading>
    18931893<Comment>
    1894 <Text id="0684">Under titles a-z documents from the same series are repeated without any distinguishing features such as date. It would be better to group them by series title and display dates within each group. This can be accomplished using an AZCompactList classifier rather than AZList, and tuning the VList format statement.</Text>
    1895 </Comment>
    1896 <NumberedItem>
    1897 <Text id="0685">In the <b>Design</b> panel, under the <b>Browsing Classifiers </b>section, delete the <b>AZList</b> classifiers for <i>ex.Source </i>and <i>ex.Title</i>.</Text>
    1898 </NumberedItem>
    1899 <NumberedItem>
    1900 <Text id="0686">Now add an <b>AZCompactList</b> classifier, setting its <b>metadata</b> option to <i>ex.Title</i>, and add a <b>DateList</b> classifier, setting its <b>metadata</b> option to <i>ex.Date</i>.</Text>
    1901 </NumberedItem>
    1902 <NumberedItem>
    1903 <Text id="0687"><b>Modify</b> the format statement for <b>VList</b>. Find the part of the default statement that says</Text>
     1894<Text id="0684">Under titles a-z documents from the same series are repeated without any distinguishing features such as date. It would be better to group them by series title and display dates within each group. This can be accomplished using an <AutoText text="AZCompactList"/> classifier rather than <AutoText text="AZList"/>, and tuning the <AutoText text="VList"/> format statement.</Text>
     1895</Comment>
     1896<NumberedItem>
     1897<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>
     1898</NumberedItem>
     1899<NumberedItem>
     1900<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>
     1901</NumberedItem>
     1902<NumberedItem>
     1903<Text id="0687"><b>Modify</b> the format statement for <AutoText text="VList" />. Find the part of the default statement that says</Text>
    19041904<Format>{If}{[ex.Source],&lt;br&gt;&lt;i&gt;([ex.Source])&lt;/i&gt;}</Format>
    19051905<Text id="0689">and change it to</Text>
    … …  
    19121912<Text id="0692">append</Text>
    19131913<Format>{If}{[numleafdocs],&lt;td&gt;([numleafdocs] items)&lt;/td&gt;}</Format>
    1914 <Text id="0692a">and click <b>&lt;Replace Format&gt;</b>.</Text>
    1915 <Comment>
    1916 <Text id="0693">As a consequence of using the 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 [numleafdocs] metadata.</Text>
     1914<Text id="0692a">and click <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/>.</Text>
     1915<Comment>
     1916<Text id="0693">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 <AutoText text="numleafdocs"/> metadata.</Text>
    19171917</Comment>
    19181918</NumberedItem>
    … …  
    19211921</Heading>
    19221922<Comment>
    1923 <Text id="0695">When you reach a newspaper, only its associated text is displayed. When either of the Te Waka o Te Iwi newspapers is accessed, the document view presents the message "This document has no text". No scanned image information (screen-view resolution or otherwise) is shown, even though it has been computed and stored with the document. This can be fixed by a format statement that modifies the default behaviour for DocumentText.</Text>
    1924 </Comment>
    1925 <NumberedItem>
    1926 <Text id="0696">Staying within the <b>Format Features</b> section of the <b>Design </b>panel, under "Choose Feature" select <b>DocumentText</b>. The default format string displays the document's plain text, which, if there is none, is set to "This document has no text". Change this to:</Text>
     1923<Text id="0695">When you reach a newspaper, only its associated text is displayed. When either of the <AutoText text="Te Waka o Te Iwi"/> newspapers is accessed, the document view presents the message <AutoText key="perlmodules::BasPlug.dummy_text" type="quoted"/>. No scanned image information (screen-view resolution or otherwise) is shown, even though it has been computed and stored with the document. This can be fixed by a format statement that modifies the default behaviour for <AutoText text="DocumentText"/>.</Text>
     1924</Comment>
     1925<NumberedItem>
     1926<Text id="0696">Staying within the <AutoText key="glidict::CDM.GUI.Formats"/> section of the <AutoText key="glidict::GUI.Design"/> panel, under <AutoText key="glidict::CDM.FormatManager.Feature"/> select <AutoText text="DocumentText"/>. The default format string displays the document's plain text, which, if there is none, is set to <AutoText key="perlmodules::BasPlug.dummy_text" type="quoted"/>. Change this to:</Text>
    19271927<Format>
    19281928&lt;center&gt;<br/> 
    … …  
    19351935&lt;/center&gt;
    19361936</Format>
    1937 <Text id="0696a">and click <b>&lt;Replace Format&gt;</b>.</Text>
    1938 <Text id="0697">(available as niupepa\doc_tweak.txt)</Text>
    1939 <Comment>
    1940 <Text id="0698">Including [screenicon] has the effect of embedding the screen-sized image generated by switching the screenview option on in PagedImgPlug. It is hyperlinked to the original image by the construct [srclink]...[/srclink].</Text>
    1941 </Comment>
    1942 </NumberedItem>
    1943 <NumberedItem>
    1944 <Text id="0699">Switch to the <b>Create </b>panel<b>;</b> <b>build</b> and <b>preview</b> the revised collection.</Text>
    1945 </NumberedItem>
    1946 <NumberedItem>
    1947 <Text id="0700">If you like, add a logo and change the background as you have done before. You will find a suitable image in the file <i>niupepa\images</i>, that is activated through <i>macros\extra.dm</i>.</Text>
     1937<Text id="0696a">and click <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/>.</Text>
     1938<Text id="0697">(available as <Path>niupepa &rarr; doc_tweak.txt</Path>)</Text>
     1939<Comment>
     1940<Text id="0698">Including <Format>[screenicon]</Format> has the effect of embedding the screen-sized image generated by switching the screenview option on in <AutoText text="PagedImgPlug"/>. It is hyperlinked to the original image by the construct <Format>[srclink]...[/srclink]</Format>.</Text>
     1941</Comment>
     1942</NumberedItem>
     1943<NumberedItem>
     1944<Text id="0699">Switch to the <AutoText key="glidict::GUI.Create"/> panel<b>;</b> <b>build</b> and <b>preview</b> the revised collection.</Text>
     1945</NumberedItem>
     1946<NumberedItem>
     1947<Text id="0700">If you like, add a logo and change the background as you have done before. You will find a suitable image in the file <Path>niupepa &rarr; images</Path>, that is activated through <Path>macros &rarr; extra.dm</Path>.</Text>
    19481948</NumberedItem>
    19491949<Comment>
    … …  
    19691969</NumberedItem>
    19701970<NumberedItem>
    1971 <Text id="0706">In the <b>Gather</b> panel, navigate to the <i>sample_small </i>folder in <i>sample_files/oai</i>. Drag this folder into the collection and drop it there.</Text>
    1972 </NumberedItem>
    1973 <NumberedItem>
    1974 <Text id="0707">During the copy operation, a popup window appears asking whether to add <b>OAIPlug</b> 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 <b>&lt;Add Plugin&gt;</b> button to include it.</Text>
     1971<Text id="0706">In the <AutoText key="glidict::GUI.Gather"/> panel, navigate to the <Path>sample_small</Path> folder in <Path>sample_files &rarr; oai</Path>. Drag this folder into the collection and drop it there.</Text>
     1972</NumberedItem>
     1973<NumberedItem>
     1974<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>
    19751975</NumberedItem>
    19761976<Comment>
    … …  
    19781978</Comment>
    19791979<Comment>
    1980 <Text id="0709">Sometimes there is more than one plug-in that could process a file&mdash;for example, the .xml extension is used for many different XML formats. The popup window, therefore, offers a choice of all possible plug-ins that matched. It is normally easy to determine the correct choice. If you wish, you can ignore the prompt (click &lt;Don't Add Plugin&gt;), because plug-ins can be added later, in the Document Plugins section of the Design panel.</Text>
    1981 </Comment>
    1982 <NumberedItem>
    1983 <Text id="0710">You need to configure the Image plug-in. In the <b>Design</b> panel, select the <b>Document Plugins</b> section, then select the <b>plugin ImagePlug</b> line and click &lt;<b>Configure Plugin...&gt;</b>. In the resulting popup window locate the <b>screenviewsize</b> option, switch it on, and type the number 300 in the box beside it to create a screen-view image of 300 pixels. Click &lt;<b>OK&gt;</b>.</Text>
    1984 </NumberedItem>
    1985 <NumberedItem>
    1986 <Text id="0711">Now switch to the <b>Create</b> panel and <b>build</b> and <b>preview</b> the collection.</Text>
     1980<Text id="0709">Sometimes there is more than one plug-in that could process a file&mdash;for example, the .xml extension is used for many different XML formats. The popup window, therefore, offers a choice of all possible plug-ins that matched. It is normally easy to determine the correct choice. If you wish, you can ignore the prompt (click <AutoText key="glidict::CDM.PlugInManager.Ignore" type="button"/>), because plug-ins can be added later, in the <AutoText key="glidict::CDM.GUI.Plugins"/> section of the <AutoText key="glidict::GUI.Design"/> panel.</Text>
     1981</Comment>
     1982<NumberedItem>
     1983<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="plugin 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>
     1984</NumberedItem>
     1985<NumberedItem>
     1986<Text id="0711">Now switch to the <AutoText key="glidict::GUI.Create"/> panel and <b>build</b> and <b>preview</b> the collection.</Text>
    19871987</NumberedItem>
    19881988<Comment>
    … …  
    19901990</Comment>
    19911991<NumberedItem>
    1992 <Text id="0713">In the <b>Browsing Classifiers</b> section of the <b>Design </b>panel, delete the two <b>AZList</b> classifiers (<i>ex.Title</i> and <i>ex.Source</i>).</Text>
    1993 </NumberedItem>
    1994 <NumberedItem>
    1995 <Text id="0714">Add an <b>AZCompactList</b> classifier based on <b>ex.Subject</b> metadata.</Text>
    1996 </NumberedItem>
    1997 <NumberedItem>
    1998 <Text id="0715">Now add an <b>AZCompactList</b> classifier based on <b>ex.Description </b>metadata. In its configuration panel select <b>mincompact</b> = <b>1</b>, <b>maxcompact</b> = <b>10</b> and <b>buttonname</b> = <b>Captions</b>.</Text>
    1999 </NumberedItem>
    2000 <NumberedItem>
    2001 <Text id="0716">In the <b>Search Indexes</b> section of the <b>Design</b> panel, delete all indexes and add a new one called "captions" based on <i>ex.Description </i>metadata.</Text>
     1992<Text id="0713">In the <AutoText key="glidict::CDM.GUI.Classifiers"/> section of the <AutoText key="glidict::GUI.Design"/> panel, delete the two <AutoText text="AZList" /> classifiers (<AutoText key="metadata::ex.Title"/> and <AutoText key="metadata::ex.Source"/>).</Text>
     1993</NumberedItem>
     1994<NumberedItem>
     1995<Text id="0714">Add an <AutoText text="AZCompactList" /> classifier based on <AutoText key="metadata::ex.Subject"/> metadata.</Text>
     1996</NumberedItem>
     1997<NumberedItem>
     1998<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="mincompact"/> to  <AutoText text="1"/>, <AutoText text="maxcompact"/> to <AutoText text="10"/> and <AutoText text="buttonname"/> to <AutoText text="Captions"/>.</Text>
     1999</NumberedItem>
     2000<NumberedItem>
     2001<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 called "captions" based on <AutoText key="metadata::ex.Description"/> metadata.</Text>
    20022002</NumberedItem>
    20032003<NumberedItem>
    … …  
    20082008</Heading>
    20092009<NumberedItem>
    2010 <Text id="0719">In the <b>Design</b> panel, select <b>Format Features</b>. First replace the <b>VList</b> format statement with this:</Text>
     2010<Text id="0719">In the <AutoText key="glidict::GUI.Design"/> panel, select <AutoText key="glidict::CDM.GUI.Formats"/>. First replace the <AutoText text="VList" /> format statement with this:</Text>
    20112011<Format>
    20122012&lt;td&gt;<br/>
    … …  
    20172017&lt;/td&gt;
    20182018</Format>
    2019 <Text id="0720">You will find this text in the file <i>vlist_tweak.txt </i>in the <i>oai/format_tweaks</i> folder of <i>sample_files. </i>Remember to press &lt;<b>Replace Format</b>&gt; when finished</Text>
    2020 <Comment>
    2021 <Text id="0721">This format statement customizes the appearance of vertical lists such as the search results and captions lists to show a thumbnail icon followed by Description metadata. Greenstone's default is to use extracted metadata, so [Description] is the same as [ex.Description].</Text>
    2022 </Comment>
    2023 </NumberedItem>
    2024 <NumberedItem>
    2025 <Text id="0722">Next, select <b>DocumentHeading</b> from the <b>Choose Feature</b> pull-down list and change its format statement to: </Text>
     2019<Text id="0720">You will find this text in the file <Path>vlist_tweak.txt</Path> in the <Path>oai &rarr;format_tweaks</Path> folder of <Path>sample_files</Path>. Remember to press <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/> when finished</Text>
     2020<Comment>
     2021<Text id="0721">This format statement customizes the appearance of vertical lists such as the search results and captions lists to show a thumbnail icon followed by Description metadata. Greenstone's default is to use extracted metadata, so <Format>[Description]</Format> is the same as <Format>[ex.Description]</Format>.</Text>
     2022</Comment>
     2023</NumberedItem>
     2024<NumberedItem>
     2025<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>
    20262026<Format>&lt;h3&gt;[Subject]&lt;/h3&gt;</Format>
    20272027<Comment>
    2028 <Text id="0723">The document heading appears above the detach and no highlighting buttons when you get to a document in the collection. By default DocumentHeading displays the document's 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 <b>Enrich</b> panel if you select an image in <Path>sample_small &rarr; oai &rarr; JCDLPICS &rarr; srcdocs</Path> and check its filename and <i>ex.Title</i> metadata. The above format statement displays <i>ex.Subject</i> metadata instead.</Text>
    2029 </Comment>
    2030 </NumberedItem>
    2031 <NumberedItem>
    2032 <Text id="0727">Finally, you will have noticed that where the document itself should appear, you see only <i>This document has no text</i>. To rectify this, select <b>DocumentText</b> in the <b>Choose Feature</b> pull-down list and use the following as its format statement (this text is in <i>doctxt_tweak.txt</i> in the <i>format_tweaks</i> folder mentioned earlier):</Text>
     2028<Text id="0723">The document heading appears above the detach and no highlighting 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>sample_small &rarr; oai &rarr; JCDLPICS &rarr; srcdocs</Path> and check its <AutoText key="metadata::ex.Filename"/> and <AutoText key="metadata::ex.Title"/> metadata. The above format statement displays <AutoText key="metadata::ex.Subject"/> metadata instead.</Text>
     2029</Comment>
     2030</NumberedItem>
     2031<NumberedItem>
     2032<Text id="0727">Finally, you will have noticed that where the document itself should appear, you see only <AutoText key="perlmodules::BasPlug.dummy_text" type="quoted"/>. To rectify this, select <AutoText text="DocumentText"/> in the <AutoText key="glidict::CDM.FormatManager.Feature"/> pull-down list and use the following as its format statement (this text is in <Path>doctxt_tweak.txt</Path> in the <Path>format_tweaks</Path> folder mentioned earlier):</Text>
    20332033<Format>&lt;center&gt;&lt;table width=_pagewidth_ border=1&gt;<br/>
    20342034&lt;tr&gt;&lt;td colspan=2 align=center&gt;<br/>
    … …  
    20412041&lt;tr&gt;&lt;td&gt;Rights:&lt;td&gt; [Rights]&lt;/td&gt;&lt;/tr&gt;<br/>
    20422042&lt;/table&gt;&lt;/center&gt;</Format>
    2043 <Text id="0727a">Click <b>&lt;Replace Format&gt;</b>.</Text>
     2043<Text id="0727a">Click <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/>.</Text>
    20442044<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>
    20452045</NumberedItem>
    20462046<NumberedItem>
    2047 <Text id="0731">Format statements are processed by the runtime system, so the collection does not need to be rebuilt for these changes to take effect. Switch to the <b>Design</b> panel and press &lt;<b>Preview Collection</b>&gt; to see the changes.</Text>
     2047<Text id="0731">Format statements are processed by the runtime system, so the collection does not need to be rebuilt for these changes to take effect. Switch to the <AutoText key="glidict::GUI.Design"/> panel and press <AutoText key="glidict::CreatePane.Preview_Collection" type="button"/> to see the changes.</Text>
    20482048</NumberedItem>
    20492049<Comment>
    … …  
    20632063</Comment>
    20642064<NumberedItem>
    2065 <Text id="0735"><b>Save</b> your collection. Note its directory name, which should be <i>oaiservi </i>(it appears in the title bar of the Librarian Interface), and <b>quit</b> the Librarian Interface.</Text>
    2066 </NumberedItem>
    2067 <NumberedItem>
    2068 <Text id="0736">In a text editor (e.g. WordPad), open the collection's configuration file, which is in <i>C:\Program Files\Greenstone\collect\oaiservi\etc\collect.cfg</i>. Add the following line (all on one line):</Text>
     2065<Text id="0735"><b>Save</b> your collection. Note its directory name, which should be <i>oaiservi</i> (it appears in the title bar of the Librarian Interface), and <b>quit</b> the Librarian Interface.</Text>
     2066</NumberedItem>
     2067<NumberedItem>
     2068<Text id="0736">In a text editor (e.g. WordPad), open the collection's configuration file, which is in <Path>Greenstone &rarr; collect &rarr; oaiservi &rarr; etc &rarr; collect.cfg</Path>. Add the following line (all on one line):</Text>
    20692069<Command>acquire OAI -src rocky.dlib.vt.edu/~jcdlpix/cgi-bin/OAI1.1/jcdlpix.pl -getdoc</Command>
    20702070<Text id="0737">Although the position of this line is not critical, we recommend that you place it near the beginning of the file, after the public and creator lines but before the index line. Save the file and quit the editor.</Text>
    20712071</NumberedItem>
    20722072<NumberedItem>
    2073 <Text id="0738">Delete the contents of the collection's <i>import</i> folder. This contains the canned version of the collection files, put there during the previous exercise. Now we want to witness the data arriving anew from the external OAI server.</Text>
     2073<Text id="0738">Delete the contents of the collection's <Path>import</Path> folder. This contains the canned version of the collection files, put there during the previous exercise. Now we want to witness the data arriving anew from the external OAI server.</Text>
    20742074</NumberedItem>
    20752075<NumberedItem>
    … …  
    21152115</NumberedItem>
    21162116<Comment>
    2117 <Text id="0752">To be able to substitute METSPlug for GAPlug you need to be in Expert mode.</Text>
    2118 </Comment>
    2119 <NumberedItem>
    2120 <Text id="0753">Click <Menu>File &rarr; Preferences &rarr; Mode</Menu> and change to <i>Expert</i> mode.</Text>
    2121 </NumberedItem>
    2122 <NumberedItem>
    2123 <Text id="0756">Switch to the <b>Design</b> panel select <b>Document Plugins</b>. Remove <b>GAPlug </b>from the list of plug-ins and add <b>METSPlug</b>, with the default configuration options.</Text>
    2124 </NumberedItem>
    2125 <NumberedItem>
    2126 <Text id="0757">Now change to the <b>Create </b>panel, locate the options for the import process and set <i>saveas </i>to <i>METS</i>. Import options are not available unless you are in <i>Expert</i> mode.</Text>
     2117<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>
     2118</Comment>
     2119<NumberedItem>
     2120<Text id="0753">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.Expert"/> mode.</Text>
     2121</NumberedItem>
     2122<NumberedItem>
     2123<Text id="0756">Switch to the <AutoText key="glidict::GUI.Design"/> panel 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>
     2124</NumberedItem>
     2125<NumberedItem>
     2126<Text id="0757">Now change to the <AutoText key="glidict::GUI.Create"/> panel, locate the options for the import process and set <AutoText text="saveas"/> to <AutoText text="METS"/>. Import options are not available unless you are in <AutoText key="glidict::Preferences.Mode.Expert"/> mode.</Text>
    21272127</NumberedItem>
    21282128<NumberedItem>
    … …  
    21302130</NumberedItem>
    21312131<NumberedItem>
    2132 <Text id="0759">In your Windows file browser, locate the <i>archives </i>folder for the Tudor collection. For each document in the collection, Greenstone has generated two files: <i>docmets.xml</i>, the core METS description, and <i>doctxt.xml</i>,<i> </i>a supporting file. (Note: unless you are connected to the Internet you will be unable to view <i>doctxt.xml</i> in your web browser, because it refers to a remote resource.) Depending on the source documents there may be additional files, such as the images used within a web page. One of MET's many features is the ability to reference information in external XML files. Greenstone uses this to tie the content of the document, which is stored in the external XML file <i>doctxt.xml</i>, to its hierarchical structure, which is described in the core METS file <i>docmets.xml</i>.</Text>
     2132<Text id="0759">In your Windows file browser, locate the <Path>archives</Path> folder for the Tudor collection. For each document in the collection, Greenstone has generated two files: <Path>docmets.xml</Path>, the core METS description, and <Path>doctxt.xml</Path>, a supporting file. (Note: unless you are connected to the Internet you will be unable to view <Path>doctxt.xml</Path> in your web browser, because it refers to a remote resource.) Depending on the source documents there may be additional files, such as the images used within a web page. One of MET's many features is the ability to reference information in external XML files. Greenstone uses this to tie the content of the document, which is stored in the external XML file <Path>doctxt.xml</Path>, to its hierarchical structure, which is described in the core METS file <Path>docmets.xml</Path>.</Text>
    21332133</NumberedItem>
    21342134</Content>
    … …  
    21422142<Content>
    21432143<NumberedItem>
    2144 <Text id="0761">First, change to <i>Library System Specialist</i> (or <i>Expert</i>) mode (using <Menu>File &rarr; Preferences</Menu>), because you will need to change the order of plug-ins in the <b>Design</b> panel.</Text>
     2144<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>
    21452145</NumberedItem>
    21462146<NumberedItem>
    … …  
    21482148</NumberedItem>
    21492149<NumberedItem>
    2150 <Text id="0764">Switch to the <b>Design </b>panel and select the <b>Document Plugins</b> section on the left-hand side. <b>Remove</b> <b>TEXTPlug</b>, <b>HTMLPlug</b> and <b>EMAILPlug</b>. Strictly speaking we do not need to remove these, however it reduces clutter.</Text>
    2151 </NumberedItem>
    2152 <NumberedItem>
    2153 <Text id="0765">Now add <b>DSpacePlug</b>. Leave the plugin options at their defaults and press &lt;<b>OK</b>&gt;.</Text>
    2154 </NumberedItem>
    2155 <NumberedItem>
    2156 <Text id="0766">Using the up and down arrows, <b>Move</b> the position of <b>DSpacePlug</b> to above <b>GAPlug</b> and below <b>ZIPPlug</b>.</Text>
    2157 </NumberedItem>
    2158 <NumberedItem>
    2159 <Text id="0767">Now add <b>MP3Plug</b>, with the default configuration options. Its position in the plug-in pipeline need not be changed.</Text>
    2160 </NumberedItem>
    2161 <NumberedItem>
    2162 <Text id="0768">In the <b>Gather</b> panel, locate the folder <b>sample_files\dspace\exported_docs</b>. It contains five example items exported from a DSpace institutional repository. Copy them into your collection by dragging them over to the right-hand side of the panel.</Text>
     2150<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="TEXTPlug" />, <AutoText text="HTMLPlug" /> and <AutoText text="EMAILPlug" />. Strictly speaking we do not need to remove these, however it reduces clutter.</Text>
     2151</NumberedItem>
     2152<NumberedItem>
     2153<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>
     2154</NumberedItem>
     2155<NumberedItem>
     2156<Text id="0766">Using the up and down arrows, <b>Move</b> the position of <AutoText text="DSpacePlug" /> to above <AutoText text="GAPlug" /> and below <AutoText text="ZIPPlug" />.</Text>
     2157</NumberedItem>
     2158<NumberedItem>
     2159<Text id="0767">Now add <AutoText text="MP3Plug" />, with the default configuration options. Its position in the plug-in pipeline need not be changed.</Text>
     2160</NumberedItem>
     2161<NumberedItem>
     2162<Text id="0768">In the <AutoText key="glidict::GUI.Gather"/> panel, locate the folder <Path>sample_files &rarr; dspace &rarr; exported_docs</Path>. It contains five example items exported from a DSpace institutional repository. Copy them into your collection by dragging them over to the right-hand side of the panel.</Text>
    21632163</NumberedItem>
    21642164<NumberedItem>
    … …  
    21692169</Comment>
    21702170<Comment>
    2171 <Text id="0771">Below we use a plug-in option (first_inorder_ext) to fuse the alternative forms together. This option has the effect of treating documents with the same filename but different extensions as a single entity within a collection. One of the files is viewed as the primary document&mdash;it is indexed, and metadata is extracted from it if possible&mdash;while the others are handled as "associated files."</Text>
    2172 </Comment>
    2173 <Comment>
    2174 <Text id="0772">The first_inorder_ext option takes as its argument a list of file extensions (separated by commas): the first one in the list that matches becomes the primary document.</Text>
    2175 </Comment>
    2176 <NumberedItem>
    2177 <Text id="0773">Select <b>DSpacePlug</b> and click &lt;<b>Configure Plugin...</b>&gt;. Switch on its configuration option <b>first_inorder_ext</b>. Set its value to <i>pdf,doc,mp3</i> in the popup window that appears and press <b>&lt;OK&gt;</b>.</Text>
     2171<Text id="0771">Below we use a plug-in option (<AutoText text="first_inorder_ext"/>) to fuse the alternative forms together. This option has the effect of treating documents with the same filename but different extensions as a single entity within a collection. One of the files is viewed as the primary document&mdash;it is indexed, and metadata is extracted from it if possible&mdash;while the others are handled as "associated files."</Text>
     2172</Comment>
     2173<Comment>
     2174<Text id="0772">The <AutoText text="first_inorder_ext"/> option takes as its argument a list of file extensions (separated by commas): the first one in the list that matches becomes the primary document.</Text>
     2175</Comment>
     2176<NumberedItem>
     2177<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,mp3" type="quoted"/> in the popup window that appears and press <AutoText key="glidict::General.OK" type="button"/>.</Text>
    21782178</NumberedItem>
    21792179<NumberedItem>
    … …  
    21902190</Heading>
    21912191<NumberedItem>
    2192 <Text id="0778">In the <b>Design</b> panel, select <b>Search Indexes</b>. Delete the <i>ex.Title </i>and <i>ex.Source </i>indexes, and add one for <b>dc.Title</b> called "titles" and another for <b>dc.Contributor</b> called "authors".</Text>
    2193 </NumberedItem>
    2194 <NumberedItem>
    2195 <Text id="0779">Staying within the <b>Design</b> panel, select <b>Browsing Classifiers</b> and <b>delete</b> both <b>AZList</b> classifiers (<i>ex.Title </i>and <i>ex.Source</i>). Add an <b>AZList</b> classifier for <b>dc.Title</b> and an <b>AZCompactList</b> classifier for <b>dc.Contributor</b>.</Text>
    2196 </NumberedItem>
    2197 <NumberedItem>
    2198 <Text id="0780">Now select the <b>Format Features </b>section of the <b>Design</b> panel and replace the <b>VList</b> format statement with this:</Text>
     2192<Text id="0778">In the <AutoText key="glidict::GUI.Design"/> panel, select <AutoText key="glidict::CDM.GUI.Indexes"/>. Delete the <AutoText key="metadata::ex.Title"/> and <AutoText key="metadata::ex.Source"/> indexes, and add one for <AutoText key="metadata::dc.Title"/> called "titles" and another for <AutoText key="metadata::dc.Contributor"/> called "authors".</Text>
     2193</NumberedItem>
     2194<NumberedItem>
     2195<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>
     2196</NumberedItem>
     2197<NumberedItem>
     2198<Text id="0780">Now select the <AutoText key="glidict::CDM.GUI.Formats"/> section of the <AutoText key="glidict::GUI.Design"/> panel and replace the <AutoText text="VList" /> format statement with this:</Text>
    21992199<Format>
    22002200&lt;td valign=top&gt;[link][icon][/link]&lt;/td&gt;<br/>
    … …  
    22082208&lt;/td&gt;
    22092209</Format>
    2210 <Text id="0781">You will find this text in the file <i>format_tweak.txt </i>in the <i>dspace </i>folder of <i>sample_files</i>, and you can copy and paste this. Remember to press &lt;<b>Replace Format</b>&gt; when finished.</Text>
    2211 </NumberedItem>
    2212 <NumberedItem>
    2213 <Text id="0782">Also, let's add a format statement for the classifier based on <b>dc.Contributor</b> metadata. In the <b>Choose Feature </b>menu (under <b>Format Features </b>on the <b>Design </b>panel), select the item that says:</Text>
     2210<Text id="0781">You will find this text in the file <Path>format_tweak.txt</Path> in the <Path>dspace</Path> folder of <Path>sample_files</Path>, and you can copy and paste this. Remember to press <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/> when finished.</Text>
     2211</NumberedItem>
     2212<NumberedItem>
     2213<Text id="0782">Also, let's add a format statement for the classifier based on <AutoText key="metadata::dc.Contributor"/> metadata. In the <AutoText key="glidict::CDM.FormatManager.Feature"/> menu (under <AutoText key="glidict::CDM.GUI.Formats"/> on the  <AutoText key="glidict::GUI.Design"/> panel), select the item that says:</Text>
    22142214<Indent>
    2215 CL2: AZCompactList -metadata dc.Contributor
     2215CL2: AZCompactList -metadata <AutoText key="metadata::dc.Contributor"/>
    22162216</Indent>
    22172217</NumberedItem>
    22182218<NumberedItem>
    2219 <Text id="0783">Leave <b>VList</b> as the <b>Affected Component</b> and edit the text in the <b>HTML Format String</b> box so that it looks like:</Text>
     2219<Text id="0783">Leave <AutoText text="VList" /> as the <AutoText key="glidict::CDM.FormatManager.Part"/> and edit the text in the <AutoText key="glidict::CDM.FormatManager.Editor"/> box so that it looks like:</Text>
    22202220<Format>
    22212221&lt;td valign=top&gt;[link][icon][/link]&lt;/td&gt;<br/>
    … …  
    22312231&lt;/td&gt;
    22322232</Format>
    2233 <Text id="0784">and click &lt;<b>Add Format</b>&gt;. This will display the number of documents for each bookshelf in the authors classifier.</Text>
    2234 <Text id="0785">You will find this text in the file <i>format_contributor.txt </i>in the <i>dspace </i>folder of <i>sample_files</i>, and you can copy and paste this.</Text>
     2233<Text id="0784">and click <AutoText key="glidict::CDM.FormatManager.Add" type="button"/>. This will display the number of documents for each bookshelf in the authors classifier.</Text>
     2234<Text id="0785">You will find this text in the file <Path>format_contributor.txt</Path> in the <Path>dspace</Path> folder of <Path>sample_files</Path>, and you can copy and paste this.</Text>
    22352235</NumberedItem>
    22362236<NumberedItem>
    … …  
    22382238</NumberedItem>
    22392239<Comment>
    2240 <Text id="0787">There are still only 5 documents, but against some of the entries&mdash;for example, Interview with Bob Dylan&mdash;appears the line "Also available as," followed by icons that link to the alternative representations.</Text>
     2240<Text id="0787">There are still only 5 documents, but against some of the entries&mdash;for example, <AutoText text="Interview with Bob Dylan" type="quoted"/>&mdash;appears the line <AutoText text="Also available as:" type="quoted"/> followed by icons that link to the alternative representations.</Text>
    22412241</Comment>
    22422242</Content>
    … …  
    22502250<Content>
    22512251<Comment>
    2252 <Text id="0789">In this exercise you export a Greenstone collection in a form suitable for DSpace. It is possible to do this from the Librarian Interface's File menu, which contains an item called Export... that allows you to export collections in different forms. However, to gain a deeper understanding of Greenstone, we perform the work by invoking a program from the Windows command-line prompt. This requires some technical skill; if you are not used to working in the command-line environment we recommend that you skip this exercise.</Text>
     2252<Text id="0789">In this exercise you export a Greenstone collection in a form suitable for DSpace. It is possible to do this from the Librarian Interface's <AutoText key="glidict::Menu.File"/> menu, which contains an item called <AutoText key="glidict::Menu.File_ExportAs"/>, that allows you to export collections in different forms. However, to gain a deeper understanding of Greenstone, we perform the work by invoking a program from the Windows command-line prompt. This requires some technical skill; if you are not used to working in the command-line environment we recommend that you skip this exercise.</Text>
    22532253</Comment>
    22542254<Heading>
    … …  
    22562256</Heading>
    22572257<NumberedItem>
    2258 <Text id="0790a">Open a DOS window to access the command-line prompt. This facility should be located somewhere within your <Menu>Start &rarr; Programs</Menu> menu, but details vary between different Windows systems. If you cannot locate it, select <Menu>Start &rarr; Run</Menu> and enter <i>cmd</i> in the popup window that appears.</Text>
     2258<Text id="0790a">Open a DOS window to access the command-line prompt. This facility should be located somewhere within your <Menu>Start &rarr; Programs</Menu> menu, but details vary between different Windows systems. If you cannot locate it, select <Menu>Start &rarr; Run</Menu> and enter <Command>cmd</Command> in the popup window that appears.</Text>
    22592259</NumberedItem>
    22602260<NumberedItem>
    … …  
    22762276</NumberedItem>
    22772277<Comment>
    2278 <Text id="0793">Exporting in Greenstone is an additive process. If you ran the export.pl command once again, the new files exported would be added&mdash;with different folder names&mdash;to those already in the export folder. For the kind of explorations we are conducting we might re-run the command several times. The -removeold option deletes files that have previously been exported.</Text>
    2279 </Comment>
    2280 <NumberedItem>
    2281 <Text id="0794">This command has created a new subfolder, <i>collect\stoned\export</i>. Use the file browser to explore it. In it are the files needed to ingest this set of documents into DSpace.</Text>
    2282 </NumberedItem>
    2283 <Comment>
    2284 <Text id="0795">You could equally well run the export.pl command on a different Greenstone collection and transfer the output to a DSpace installation by using DSpace's batch-import facility.</Text>
     2278<Text id="0793">Exporting in Greenstone is an additive process. If you ran the <Command>export.pl</Command> command once again, the new files exported would be added&mdash;with different folder names&mdash;to those already in the export folder. For the kind of explorations we are conducting we might re-run the command several times. The <Command>-removeold</Command> option deletes files that have previously been exported.</Text>
     2279</Comment>
     2280<NumberedItem>
     2281<Text id="0794">This command has created a new subfolder, <Path>collect &rarr; stoned &rarr; export</Path>. Use the file browser to explore it. In it are the files needed to ingest this set of documents into DSpace.</Text>
     2282</NumberedItem>
     2283<Comment>
     2284<Text id="0795">You could equally well run the <Command>export.pl</Command> command on a different Greenstone collection and transfer the output to a DSpace installation by using DSpace's batch-import facility.</Text>
    22852285</Comment>
    22862286</Content>
Note: See TracChangeset for help on using the changeset viewer.