Ignore:
Timestamp:
2006-10-25T16:17:03+13:00 (18 years ago)
Author:
kjdon
Message:

a few small tidy ups

File:
1 edited

Legend:

Unmodified
Added
Removed

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

    r13143 r13159  
    618618<Text id="0261">A window pops up. Fill it out with appropriate values&mdash;for example,</Text>
    619619<Indent>
    620 <Text id="0261a"><AutoText key="glidict::CDM.General.Collection_Name"/>: About Hobbits<br/></Text>
    621 <Text id="0261b"><AutoText key="glidict::NewCollectionPrompt.Collection_Description"/>: A collection about hobbits.</Text>
     620<Text id="0261a"><AutoText key="glidict::CDM.General.Collection_Name"/> About Hobbits<br/></Text>
     621<Text id="0261b"><AutoText key="glidict::NewCollectionPrompt.Collection_Description"/> A collection about hobbits.</Text>
    622622</Indent>
    623623<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>
    … …  
    696696</NumberedItem>
    697697<NumberedItem>
    698 <Text id="0344">Click on <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>
     698<Text id="0344">Click on <AutoText key="coredm::_Global:labelBrowse_"/> 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>
    699699</NumberedItem>
    700700<NumberedItem>
    … …  
    759759</NumberedItem>
    760760<NumberedItem>
    761 <Text id="0362b">Preview the collection by clicking the <AutoText key="glidict::CreatePane.Preview_Collection" type="button"/> button. When you click on <AutoText key="coredm::_Global:labelBrwse_"/> in the navigation bar the presentation has changed to "Title: Bear" and so on. Each image's description should appear beside the thumbnail, following the title.</Text>
     761<Text id="0362b">Preview the collection by clicking the <AutoText key="glidict::CreatePane.Preview_Collection" type="button"/> button. When you click on <AutoText key="coredm::_Global:labelBrowse_"/> in the navigation bar the presentation has changed to "Title: Bear" and so on. Each image's description should appear beside the thumbnail, following the title.</Text>
    762762</NumberedItem>
    763763<Comment>
    … …  
    789789</NumberedItem>
    790790<NumberedItem>
    791 <Text id="0382a"><b>Build</b> the collection, and <b>preview</b> it. Choose the new <b>descriptions</b> link that appears in the navigation bar.</Text>
    792 </NumberedItem>
    793 <Comment>
    794 <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>
     791<Text id="0382a"><b>Build</b> the collection, and <b>preview</b> it. Choose the new <AutoText key="coredm::_Global:labelDescription_"/> link that appears in the navigation bar.</Text>
     792</NumberedItem>
     793<Comment>
     794<Text id="0383">Only three items are shown, because only items with the relevant metadata (<AutoText key="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>
    795795</Comment>
    796796<Heading>
    … …  
    804804</NumberedItem>
    805805<NumberedItem>
    806 <Text id="0386a">To change the text that is displayed for the index (document:dc.Description), go to the <AutoText key="glidict::GUI.Format"/> panel back in the GLI. Select <AutoText key="glidict::CDM.GUI.SearchMetadata"/> from the left-hand list. This panel allows you to change the text that is displayed on the search form. Change the <AutoText key="glidict::CDM.SearchMetadataManager.Component_Name"/> for the <AutoText text="document:dc.Description"/> index to "descriptions" (or other suitable text). Go back to the browser and reload the search page. Your new text will appear in the search form.</Text>
     806<Text id="0386a">To change the text that is displayed for the index (document:dc.Description), go to the <AutoText key="glidict::GUI.Format"/> panel back in the Librarian Interface. Select <AutoText key="glidict::CDM.GUI.SearchMetadata"/> from the left-hand list. This panel allows you to change the text that is displayed on the search form. Change the <AutoText key="glidict::CDM.SearchMetadataManager.Component_Name"/> for the <AutoText text="document:dc.Description"/> index to "descriptions" (or other suitable text). Go back to the browser and reload the search page. Your new text will appear in the search form.</Text>
    807807</NumberedItem>
    808808</Content>
    … …  
    861861</NumberedItem>
    862862<Comment>
    863 <Text id="0294">If you build and preview your collection at this point, you will see that the <AutoText key="coredm::_Global:labelTitle_" type="italics"/> now shows your new Titles. However, the <AutoText key="metadata::dc.Creator"/> metadata is not displayed. You need to alter the collection design to use the new Dublin Core metadata.</Text>
     863<Text id="0294">If you build and preview your collection at this point, you will see that the <AutoText key="coredm::_Global:labelTitle_"/> list now shows your new Titles. However, the <AutoText key="metadata::dc.Creator"/> metadata is not displayed. You need to alter the collection design to use this metadata.</Text>
    864864</Comment>
    865865<Heading>
    … …  
    876876</NumberedItem>
    877877<NumberedItem>
    878 <Text id="0310b">Modify the <AutoText key="metadata::ex.Title"/> index to include <AutoText key="metadata::dc.Title"/> by selecting the index in the <AutoText key="glidict::CDM.IndexManager.Indexes"/> box and clicking <AutoText key="glidict::CDM.IndexManager.Edit_Index" type="button"/>. Select <AutoText key="metadata::dc.Title"/> from the list of metadata, and click <AutoText key="glidict::CDM.IndexManager.Replace_Index" type="button"/>. Searching this index will search both dc.Title and ex.Title metadata. If you want to restrict searching to just the manually added dc.Title metadata, edit the index again and deselect <AutoText key="metadata::ex.Title"/> from the list of metadata.</Text>
     878<Text id="0310b">Modify the <AutoText key="metadata::ex.Title"/> index to include <AutoText key="metadata::dc.Title"/> by selecting the index in the <AutoText key="glidict::CDM.IndexManager.Indexes"/> box and clicking <AutoText key="glidict::CDM.IndexManager.Edit_Index" type="button"/>. Select <AutoText key="metadata::dc.Title"/> from the list of metadata, and click <AutoText key="glidict::CDM.IndexManager.Replace_Index" type="button"/>. Searching this index will search both <AutoText key="metadata::dc.Title"/> and <AutoText key="metadata::ex.Title"/> metadata. If you want to restrict searching to just the manually added <AutoText key="metadata::dc.Title"/> metadata, edit the index again and deselect <AutoText key="metadata::ex.Title"/> from the list of metadata.</Text>
    879879</NumberedItem>
    880880<NumberedItem>
    … …  
    911911</NumberedItem>
    912912<NumberedItem>
    913 <Text id="0321-3">Select <AutoText key="glidict::CDM.GUI.SearchMetadata"/> in the left hand list. This pane allows you to modify what text is displayed for the drop-down lists in the search form (indexes, subcollections, levels etc). Set the  <AutoText key="glidict::CDM.SearchMetadataManager.Component_Name"/> for the <AutoText text="dc.Title,Title"/> index to be "titles", and that for the <AutoText text="dc.Creator"/> index to be "creators". Preview the collection by clicking the <AutoText key="glidict::CreatePane.Preview_Collection"/>. The search form should display the new text.</Text>
     913<Text id="0321-3">Select <AutoText key="glidict::CDM.GUI.SearchMetadata"/> in the left hand list. This section allows you to modify what text is displayed for the drop-down lists in the search form (indexes, subcollections, levels etc). Set the  <AutoText key="glidict::CDM.SearchMetadataManager.Component_Name"/> for the <AutoText text="dc.Title,Title"/> index to be "titles", and that for the <AutoText text="dc.Creator"/> index to be "creators". Preview the collection by clicking the <AutoText key="glidict::CreatePane.Preview_Collection"/>. The search form should display the new text.</Text>
    914914</NumberedItem>
    915915<Heading>
    … …  
    10951095</Heading>
    10961096<NumberedItem>
    1097 <Text id="ep-12">If conversion to HTML doesn't produce the result you like, PDF documents can be converted to a series of images, one per page or slide. This requires ImageMagick and Ghostscript to be installed.</Text>
     1097<Text id="ep-12">If conversion to HTML doesn't produce the result you like, PDF documents can be converted to a series of images, one per page. This requires ImageMagick and Ghostscript to be installed.</Text>
    10981098</NumberedItem>
    10991099<NumberedItem>
    … …  
    11301130</NumberedItem>
    11311131<NumberedItem>
    1132 <Text id="ep-21">We achieve this by putting the problem files into a separate folder, and adding two <AutoText text="PDFPlug"/> plugins to the collection, with different options.</Text>
     1132<Text id="ep-21">We achieve this by putting the problem files into a separate folder, and adding another <AutoText text="PDFPlug"/> plugin with different options.</Text>
    11331133</NumberedItem>
    11341134<NumberedItem>
    … …  
    11651165</Title>
    11661166<Version initial="2.70w" current="2.71"/>
     1167<Prerequisite id="word_pdf_collection"/>
    11671168<Content>
    11681169<Text id="ew-1">The standard way Greenstone processes Word documents is to convert them to HTML format using a third-party program, wvWare. This sometimes doesn't do a very good job of conversion. If you are using Windows, and have Microsoft Word installed, you can take advantage of Windows native scripting to do a better job of conversion. If the original document was hierarchically structured using Word styles, these can be used to structure the resulting HTML. Word document properties can also be extracted as metadata.</Text>
    … …  
    12271228</Format>
    12281229<Text id="ew-12">These header options define which styles should be considered as title, level 1, level 2 and level 3 styles. </Text>
    1229 <Text id="ew-12a">Set the options as follows (spaces are removed when converting to HTML styles):</Text>
     1230<Text id="ew-12a">Set the options as follows (spaces in the Word styles are removed when converting to HTML styles, and these options must match the HTML styles):</Text>
    12301231<Format>
    12311232level1_header:(SammaryHeader|ChapterTitle|ReferenceHeading)<br/>
    … …  
    12801281</NumberedItem>
    12811282<NumberedItem>
    1282 <Text id="ew-31">Look at the metadata for the two documents again in the <AutoText key="glidict::GUI.Enrich"/> panel. You should now see ex.Creator and ex.Subject metadata items . This metadata can now be used in display or browsing classifiers etc.</Text>
     1283<Text id="ew-31">Look at the metadata for the two documents again in the <AutoText key="glidict::GUI.Enrich"/> panel. You should now see ex.Creator and ex.Subject metadata items. This metadata can now be used in display or browsing classifiers etc.</Text>
    12831284</NumberedItem>
    12841285</Content>
    … …  
    12971298</NumberedItem>
    12981299<NumberedItem>
    1299 <Text id="0406">Choose <Menu><AutoText key="glidict::Menu.File"/> &rarr; <AutoText key="glidict::Menu.File_CDimage"/></Menu>. In the resulting popup window, select the collection or collections that you wish to export by ticking their check boxes. You can optionally enter a name for the CD-ROM: this is the name that will appear in the menu when the CDROM is run. If a name is not entered, the default <AutoText text="Greenstone Collections"/> will be used. You can also specify whether the resulting CD-ROM will install files onto the host machine when used or not. Click <AutoText key="glidict::WriteCDImagePrompt.Export" type="button"/> to start the export process.</Text>
     1300<Text id="0406">Choose <Menu><AutoText key="glidict::Menu.File"/> &rarr; <AutoText key="glidict::Menu.File_CDimage"/></Menu>. In the resulting popup window, select the collection or collections that you wish to export by ticking their check boxes. You can optionally enter a name for the CD-ROM: this is the name that will appear in the menu when the CD-ROM is run. If a name is not entered, the default <AutoText text="Greenstone Collections"/> will be used. You can also specify whether the resulting CD-ROM will install files onto the host machine when used or not. Click <AutoText key="glidict::WriteCDImagePrompt.Export" type="button"/> to start the export process.</Text>
    13001301<Text id="0408">The necessary files for export are written to:</Text>
    13011302<Path>Greenstone &rarr; tmp &rarr; exported_xxx</Path>
    … …  
    13371338</NumberedItem>
    13381339<NumberedItem>
    1339 <Text id="0393a">Many HTML documents contain metadata in <Format>&lt;meta&gt;</Format> tags in the <Format>&lt;head&gt;</Format> of the page. Open up the <Path>englishhistory.net &rarr; tudor &rarr; monarchs &rarr; boleyn.html</Path> file by navigating to it in the tree on the left hand side, and double clicking it. This will open it in a web browser. View the HTML source of the page (<Menu>View &rarr; Source</Menu> in Internet Explorer, <Menu>View &rarr; Page Source</Menu> in Mozilla). You will notice that this page has <AutoText text="page_topic,content" type="italics"/> and <AutoText text="author" type="italics"/> metadata.</Text>
     1340<Text id="0393a">Many HTML documents contain metadata in <Format>&lt;meta&gt;</Format> tags in the <Format>&lt;head&gt;</Format> of the page. Open up the <Path>englishhistory.net &rarr; tudor &rarr; monarchs &rarr; boleyn.html</Path> file by navigating to it in the tree on the left hand side, and double clicking it. This will open it in a web browser. View the HTML source of the page (<Menu>View &rarr; Source</Menu> in Internet Explorer, <Menu>View &rarr; Page Source</Menu> in Mozilla). You will notice that this page has <AutoText text="page_topic, content" type="italics"/> and <AutoText text="author" type="italics"/> metadata.</Text>
    13401341 </NumberedItem>
    13411342<NumberedItem>
    … …  
    13561357</Comment>
    13571358<NumberedItem>
    1358 <Text id="0395">Switch back to the <AutoText key="glidict::CDM.GUI.Plugins"/> section of the <AutoText key="glidict::GUI.Design"/> panel. Beside <AutoText text="plugin HTMLPlug"/> you will see <AutoText text="-smart_block"/>. This is the option that attempts to identify images in the HTML pages and block them from inclusion&mdash;in this case, it's not smart enough! <b>Configure</b> <AutoText text="plugin HTMLPlug"/> again, scroll down the page to locate the <AutoText text="smart_block"/> option, and switch it off.</Text>
     1359<Text id="0395">Switch back to the <AutoText key="glidict::CDM.GUI.Plugins"/> section of the <AutoText key="glidict::GUI.Design"/> panel. Beside <AutoText text="plugin HTMLPlug"/> you will see <AutoText text="-smart_block"/>. This is the option that attempts to identify images in the HTML pages and block them from inclusion&mdash;in this case, it's not smart enough! Configure <AutoText text="plugin HTMLPlug"/> again, scroll down the page to locate the <AutoText text="smart_block"/> option, and switch it off.</Text>
    13591360</NumberedItem>
    13601361<NumberedItem>
    … …  
    14001401<NumberedItem>
    14011402<Text id="0440">Finally, select all remaining files&mdash;the ones that are not in the <Path>citizens</Path>, <Path>monarchs</Path>, or <Path>relative</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>
    1402 <Text id="0440a">When multiple files are selected in the left hand collection tree, all metadata values for all files are shown on the right hand side. Items that are common to all files are displayed in black&mdash;e.g. <AutoText key="metadata::dc.Subject"/>&mdash;which others that pertain to only one or some of the files are displayed in grey&mdash;e.g. any extracted metadata.</Text>
     1403<Text id="0440a">When multiple files are selected in the left hand collection tree, all metadata values for all files are shown on the right hand side. Items that are common to all files are displayed in black&mdash;e.g. <AutoText key="metadata::dc.Subject"/>&mdash;while others that pertain to only one or some of the files are displayed in grey&mdash;e.g. any extracted metadata.</Text>
    14031404<Text id="0440a">Metadata inherited from a parent folder is indicated by a folder icon to the left of the metadata name. Select one of the files in the <Path>relative</Path> folder to see this.</Text>
    14041405</NumberedItem>
    … …  
    14281429</NumberedItem>
    14291430<NumberedItem>
    1430 <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>
     1431<Text id="0460"><b>Build</b> the collection again, <b>preview</b> it, and try out the new <AutoText key="coredm::_Global:labelPhrase_"/> option in the navigation bar. An interesting PHIND search term for this collection is <AutoText text="king" type="quoted"/>. Note that even though it is called a phrase browser, only single terms can be used as the starting point for browsing.</Text>
    14311432</NumberedItem>
    14321433<Heading>
    … …  
    14631464</NumberedItem>
    14641465<NumberedItem>
    1465 <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>
     1466<Text id="0454">To ensure that the combined 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>
    14661467</NumberedItem>
    14671468<NumberedItem>
    … …  
    14721473</NumberedItem>
    14731474<NumberedItem>
    1474 <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>
     1475<Text id="0456">In the Librarian Interface, return to <AutoText key="glidict::Preferences.Mode.Librarian"/> mode, using <AutoText key="glidict::Menu.File_Options"/> (on the <AutoText key="glidict::Menu.File"/> menu).</Text>
    14751476</NumberedItem>
    14761477<Heading>
    … …  
    15331534<Text id="0482">In the <AutoText key="glidict::CDM.GUI.Formats"/> section of the <AutoText key="glidict::GUI.Format"/> panel, the <AutoText key="glidict::CDM.FormatManager.Feature"/> menu (just above <AutoText key="glidict::CDM.FormatManager.Part"/> menu) displays <AutoText key="glidict::CDM.FormatManager.AllFeatures" type="italics"/>. 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. 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>
    15341535<Indent>
    1535 CL2: Hierarchy -metadata dc.Subject and Keywords
     1536CL2: Hierarchy -metadata <AutoText key="metadata::dc.Subject" type="plain"/>
    15361537</Indent>
    1537 <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>
     1538<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 <AutoText key="metadata::dc.Subject"/> metadata.</Text>
    15381539<Text id="0483a">Click <AutoText key="glidict::CDM.FormatManager.Add" type="button"/> to add this format statement to the collection.</Text>
    15391540<Text id="0484">Edit the <AutoText key="glidict::CDM.FormatManager.Editor"/> box below to read</Text>
    … …  
    15731574&lt;td&gt;[link][icon][/link]&lt;/td&gt;<br/>
    15741575&lt;td&gt;{If}{[numleafdocs],&lt;b&gt;Bookshelf title:&lt;/b&gt; [ex.Title],<br/>
    1575 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;b&gt;Title:&lt;/b&gt; [ex.Title]}<br/>
     1576&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Title:&lt;/b&gt; [ex.Title]}<br/>
    15761577&lt;/td&gt;
    15771578</Format>
    … …  
    16171618</NumberedItem>
    16181619<NumberedItem>
    1619 <Text id="st-4">Add a new Section into this document. For example, add a new subsection into the <AutoText text="Introduction"/> chapter. In the text editor, add the following just after the Section tag for the <AutoText text="Introduction"/> section:</Text>
     1620<Text id="st-4">Add a new Section into this document. For example, lets add a new subsection into the <AutoText text="Introduction"/> chapter. In the text editor, add the following just after the Section tag for the <AutoText text="Introduction"/> section:</Text>
    16201621<Format>
    16211622&lt;!--<br/>
    … …  
    16351636</NumberedItem>
    16361637<NumberedItem>
    1637 <Text id="st-7">Open the Greenstone demo collection in the Librarian Interface. In the <AutoText key="glidict::CDM.GUI.Plugins"/> section of the <AutoText key="glidict::GUI.Design"/> panel, note that <AutoText text="HTMLPlug"/> has the <AutoText text="description_tags"/> option set. This option is needed when Section tags are used in the source documents.</Text>
     1638<Text id="st-7">Open the Greenstone demo collection in the Librarian Interface. In the <AutoText key="glidict::CDM.GUI.Plugins"/> section of the <AutoText key="glidict::GUI.Design"/> panel, note that <AutoText text="HTMLPlug"/> has the <AutoText text="description_tags"/> option set. This option is needed when <Format>&lt;Section&gt;</Format> tags are used in the source documents.</Text>
    16381639</NumberedItem>
    16391640<NumberedItem>
    … …  
    16521653</Comment>
    16531654<NumberedItem>
    1654 <Text id="0413">Start a new collection called <b>webtudor</b>, and base it on <AutoText key="glidict::NewCollectionPrompt.NewCollection"/></Text>
     1655<Text id="0413">Start a new collection called <b>webtudor</b>, and base it on <AutoText key="glidict::NewCollectionPrompt.NewCollection"/>.</Text>
    16551656</NumberedItem>
    16561657<NumberedItem>
    … …  
    16631664<Text id="0415b">Enter this URL</Text>
    16641665<Link>http://englishhistory.net/tudor/citizens/</Link>
    1665 <Text id="0417">into the <AutoText text="url"/> box. There are several other options that govern how the download process proceeds. To see a description of the option, hover the mouse over the option and a tooltip will appear. To copy just the <i>citizens</i> section of the website, switch on the <AutoText text="below"/> option by checking its box. If you don't do this (or if you miss out the terminating "/" in the URL), the downloading process will follow links to other areas of the <i>englishhistory.net</i> website and grab those as well.</Text>
     1666<Text id="0417">into the <AutoText text="url"/> box. There are several other options that govern how the download process proceeds. To see a description of an option, hover the mouse over it and a tooltip will appear. To copy just the <i>citizens</i> section of the website, switch on the <AutoText text="below"/> option by checking its box. If you don't do this (or if you miss out the terminating "/" in the URL), the downloading process will follow links to other areas of the <i>englishhistory.net</i> website and grab those as well.</Text>
    16661667</NumberedItem>
    16671668<NumberedItem>
    … …  
    17381739<NumberedItem>
    17391740<Text id="0524">Now select <AutoText key="glidict::CDM.GUI.Classifiers"/> within the <AutoText key="glidict::GUI.Design"/> panel and <b>remove</b> the default classifier for <b>Source</b> metadata.</Text>
    1740 <Text id="0524a">In the <AutoText key="glidict::CDM.GUI.Indexes"/> section, remove the <AutoText key="metadata::ex.Source"/> index.</Text>
    1741 <Text id="0524b">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 or useful.</Text>
     1741</NumberedItem>
     1742<NumberedItem>
     1743<Text id="0524a">In the <AutoText key="glidict::CDM.GUI.Indexes"/> section, <b>remove</b> the <AutoText key="metadata::ex.Source"/> index. In this collection all records are from the same file, so <AutoText key="metadata::ex.Source"/> metadata, which is set to the filename, is not particularly interesting or useful.</Text>
    17421744</NumberedItem>
    17431745<NumberedItem>
    … …  
    17571759</Heading>
    17581760<NumberedItem>
    1759 <Text id="0531a">Collections built with MGPP (the default indexer) provide the option of fielded searching. In the browser, go to the <AutoText key="coredm::_Global:linktextPREFERENCES_" type="italics"/> page. You will notice that there is a <AutoText key="coredm::_preferences:textsearchtype_" /> option which enables you to switch between "normal" and "fielded" search. Change to fielded search now and click on the <AutoText key="coredm::_Global:labelSearch_"/>. The search form has changed to a fielded form.</Text>
    1760 </NumberedItem>
    1761 <NumberedItem>
    1762 <Text id="0531b">You can specify which search form types are available for a particular collection, and which one is the default using the <AutoText text="SearchTypes"/> format statement. In the <AutoText key="glidict::GUI.Format"/> panel select <AutoText key="glidict::CDM.GUI.Formats"/> from the left-hand list. Select the <AutoText text="SearchTypes"/> format statement from the list of assigned formats, and set the contents to <AutoText text="form"/>. This will make only fielded searching available for this collection.</Text>
     1761<Text id="0531a">Collections built with MGPP (the default indexer) provide the option of fielded searching. In the browser, go to the <AutoText key="coredm::_Global:linktextPREFERENCES_" type="italics"/> page. You will notice that there is a <AutoText key="coredm::_preferences:textsearchtype_" /> option which enables you to switch between "normal" and "fielded" search. Change to fielded search now and click on the <AutoText key="coredm::_Global:labelSearch_"/> button. The search form has changed to a fielded form.</Text>
     1762</NumberedItem>
     1763<NumberedItem>
     1764<Text id="0531b">You can specify which search form types are available for a particular collection, and which one is the default, using the <AutoText text="SearchTypes"/> format statement. In the <AutoText key="glidict::GUI.Format"/> panel select <AutoText key="glidict::CDM.GUI.Formats"/> from the left-hand list. Select the <AutoText text="SearchTypes"/> format statement from the list of assigned formats, and set the contents to <AutoText text="form"/>. This will make only fielded searching available for this collection.</Text>
    17631765<Comment>
    17641766<Text id="0531c">Search type options include <AutoText text="form"/> and <AutoText text="plain"/>. You can specify one or both separated by a comma. If both are specified, the first one is used as the default: this is the one that the user will see when they first enter the collection.</Text>
    … …  
    18201822</NumberedItem>
    18211823<NumberedItem>
    1822 <Text id="0533-14a">To enable combined searching across all indexes at once, click <AutoText key="glidict::CDM.IndexManager.New_Index" type="button"/>, tick the <AutoText key="glidict::CDM.IndexManager.Allfields_Index"/> checkbox, and click <AutoText key="glidict::CDM.IndexManager.Add_Index" type="button"/>. Move this to the top of the list using the <AutoText key="glidict::CDM.Move.Move_Up" type="button"/> and <AutoText key="glidict::CDM.Move.Move_Down" type="button"/> buttons, so that it appears first in the drop down list. Click <AutoText key="glidict::CDM.IndexManager.Set_Default" type="button"/> so that it becomes the default field for searching.</Text>
    1823 </NumberedItem>
    1824 <NumberedItem>
    1825 <Text id="0533-15">In the <AutoText key="glidict::CDM.GUI.Classifiers"/> section, change the Title <AutoText text="AZList"/> to use <AutoText key="metadata::exp.Title"/> metadata. Double click the Title <AutoText text="AZList"/> in the <AutoText key="glidict::CDM.ClassifierManager.Assigned"/> list, and change the <AutoText text="metadata"/> option to use <AutoText key="metadata::exp.Title"/>. Click <AutoText key="glidict::General.OK" type="button"/>. Do the same thing for the Subject <AutoText text="AZCompactList"/>, changing <AutoText key="metadata::ex.Subject"/> to <AutoText key="metadata::exp.Subject"/>.</Text>
     1824<Text id="0533-14a">To enable combined searching across all indexes at once, click <AutoText key="glidict::CDM.IndexManager.New_Index" type="button"/>, tick the <AutoText key="glidict::CDM.IndexManager.Allfields_Index"/> checkbox, and click <AutoText key="glidict::CDM.IndexManager.Add_Index" type="button"/>. Move this to the top of the list using the <AutoText key="glidict::CDM.Move.Move_Up" type="button"/> button, so that it appears first in the drop down list. Click <AutoText key="glidict::CDM.IndexManager.Set_Default" type="button"/> so that it becomes the default field for searching.</Text>
     1825</NumberedItem>
     1826<NumberedItem>
     1827<Text id="0533-15">In the <AutoText key="glidict::CDM.GUI.Classifiers"/> section, change the <AutoText key="metadata::ex.Title"/> <AutoText text="AZList"/> to use <AutoText key="metadata::exp.Title"/> metadata. Double click the <AutoText key="metadata::ex.Title"/> <AutoText text="AZList"/> in the <AutoText key="glidict::CDM.ClassifierManager.Assigned"/> list, and change the <AutoText text="metadata"/> option to use <AutoText key="metadata::exp.Title"/>. Click <AutoText key="glidict::General.OK" type="button"/>. Do the same thing for the Subject <AutoText text="AZCompactList"/>, changing <AutoText key="metadata::ex.Subject"/> to <AutoText key="metadata::exp.Subject"/>.</Text>
    18261828</NumberedItem>
    18271829<NumberedItem>
    … …  
    18711873<Text id="is-1">CDS/ISIS collection</Text>
    18721874</Title>
     1875<SampleFiles folder="isis"/>
    18731876<Version initial="2.70w" current="2.71"/>
    18741877<Content>
    … …  
    19511954</NumberedItem>
    19521955<NumberedItem>
    1953 <Text id="mf-11">Open the file <Path>Greenstone &rarr; macros &rarr; style.dm</Path> with the same program. Locate the following part of the file (this is part of the <Format>_cssheader_</Format> macro:</Text>
     1956<Text id="mf-11">Open the file <Path>Greenstone &rarr; macros &rarr; style.dm</Path> with the same program. Locate the following part of the file (this is part of the <Format>_cssheader_</Format> macro):</Text>
    19541957<Format>
    19551958&lt;style type="text/css"&gt;<br/>
    … …  
    20072010<Text id="mf-27">Find the <Format>body</Format> style instructions:</Text>
    20082011<Format>
    2009 body {
     2012body {<br/>
    20102013  background: #ffffff;<br/>
    20112014  color: #000000;<br/>
    … …  
    20662069</NumberedItem>
    20672070<NumberedItem>
    2068 <Text id="mf-39">Adding text into the main <Format>_footer_</Format> macro adds it to all pages. To add a footer just to a particular page, use <Format>_pagefooterextra_</Format> in the appropriate macro file. For example, lets add some more text to the footer, this time just on the home page</Text>
     2071<Text id="mf-39">Adding text into the main <Format>_footer_</Format> macro adds it to all pages. To add a footer just to a particular page, use <Format>_pagefooterextra_</Format> in the appropriate macro file. For example, lets add some more text to the footer, this time just on the home page.</Text>
    20692072<Text id="mf-40">Open the file <Path>Greenstone &rarr; macros &rarr; home.dm</Path> in a text editor. After the line <Format>package home</Format>, add the following text:</Text>
    20702073<Format>
    … …  
    21482151}
    21492152</Format>
    2150 <Text id="mf-60">Outside of the Librarian Interface, locate the collection folder <Path>Greenstone &rarr; collect &rarr; reports &rarr;</Path>. Create an <Path>images</Path> folder inside this, and copy the file <Path>sample_files &rarr; custom &rarr; style-blue.css</Path> into this folder.</Text>
     2153<Text id="mf-60">Outside of the Librarian Interface, locate the collection folder <Path>Greenstone &rarr; collect &rarr; reports</Path>. Create an <Path>images</Path> folder inside this (if not already present), and copy the file <Path>sample_files &rarr; custom &rarr; style-blue.css</Path> into this folder.</Text>
    21512154<Text id="mf-61">Preview the collection; it should look radically different.</Text>
    21522155</NumberedItem>
    … …  
    21962199</NumberedItem>
    21972200<NumberedItem>
    2198 <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>
     2201<Text id="0545">Explore the Beatles collection. Note how the <AutoText key="coredm::_Global:labelBrowse_" type="italics"/> 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>
    21992202</NumberedItem>
    22002203<NumberedItem>
    … …  
    22022205</NumberedItem>
    22032206<NumberedItem>
    2204 <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="quoted"/> 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>
     2207<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="quoted"/> in the <AutoText key="coredm::_Global:labelTitle_" type="italics"/> 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>
    22052208</NumberedItem>
    22062209<NumberedItem>
    … …  
    22232226</Comment>
    22242227<NumberedItem>
    2225 <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 <AutoText key="glidict::NewCollectionPrompt.NewCollection"/>. (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.</Text>
     2228<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 <AutoText key="glidict::NewCollectionPrompt.NewCollection"/>. (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!)</Text>
    22262229</NumberedItem>
    22272230<NumberedItem>
    … …  
    23972400<NumberedItem>
    23982401<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>
    2399 <Text id="0612b"><b>Build</b> the collection again and <b>preview</b> it. Select the new <AutoText key="coredm::_Global:labelPhrases_"/> option from the navigation bar. Enter a single word in the text box, such as <AutoText text="band" type="quotes"/>. The phrase browser will present you with phrases found in the collection containing the search term. This can provide a useful way of browsing a very large collection. Note that even though it is called a phrase browser, only single terms can be used as the starting point for browsing.</Text>
     2402<Text id="0612b"><b>Build</b> the collection again and <b>preview</b> it. Select the new <AutoText key="coredm::_Global:labelPhrase_"/> option from the navigation bar. Enter a single word in the text box, such as <AutoText text="band" type="quotes"/>. The phrase browser will present you with phrases found in the collection containing the search term. This can provide a useful way of browsing a very large collection. Note that even though it is called a phrase browser, only single terms can be used as the starting point for browsing.</Text>
    24002403</NumberedItem>
    24012404<Heading>
    … …  
    25972600</NumberedItem>
    25982601<NumberedItem>
    2599 <Text id="0680">Some of the files you have just dragged in are the newspaper images; others are text files that contain the text extracted from these images. We want these to be processed by <AutoText text="PagedImgPlug"/>, not <AutoText text="ImagePlug"/> or <AutoText text="TEXTPlug"/>. Switch to the <AutoText key="glidict::GUI.Design"/> panel and delete <AutoText text="ImagePlug"/> and <AutoText text="TEXTPlug"/>. While you are at it, you could tidy things up by deleting <AutoText text="ZIPPlug"/> and all plugins from <AutoText text="HTMLPlug"/> to <AutoText text="NULPlug"/> as well, since they will not be used. <AutoText text="GAPlug"/> and <AutoText text="PagedImgPlug"/> remain.</Text>
     2602<Text id="0680">Some of the files you have just dragged in are the newspaper images; others are text files that contain the text extracted from these images. We want these to be processed by <AutoText text="PagedImgPlug"/>, not <AutoText text="ImagePlug"/> or <AutoText text="TEXTPlug"/>. Switch to the <AutoText key="glidict::CDM.GUI.Plugins"/> section of the <AutoText key="glidict::GUI.Design"/> panel and delete <AutoText text="ImagePlug"/> and <AutoText text="TEXTPlug"/>. While you are at it, you could tidy things up by deleting <AutoText text="ZIPPlug"/> and all plugins from <AutoText text="HTMLPlug"/> to <AutoText text="NULPlug"/> as well, since they will not be used. <AutoText text="GAPlug"/> and <AutoText text="PagedImgPlug"/> remain.</Text>
    26002603</NumberedItem>
    26012604<NumberedItem>
    … …  
    26952698<Text id="0690h-1">In the <AutoText key="glidict::CDM.GUI.Formats"/> section, select <AutoText text="Search"/> in <AutoText key="glidict::CDM.FormatManager.Feature"/>, and <AutoText text="VList"/> in <AutoText key="glidict::CDM.FormatManager.Part"/>. Click <AutoText key="glidict::CDM.FormatManager.Add" type="button"/> to add this format to the collection. The previous changes modified <AutoText text="VList"/>, so they will apply to all <AutoText text="VList"/>s that don't have specific format statements. These next changes are made to <AutoText text="SearchVList"/> so will only apply to search results. </Text>
    26962699<Text id="0690i">The extracted Title for the current section is specified as <Format>[ex.Title]</Format> while the Title for the parent section is <Format>[parent:ex.Title]</Format>. Since the same <AutoText text="SearchVList"/> format statement is used when searching both whole newspapers and newspaper pages, we need to make sure it works in both cases.</Text>
    2697 <Text id="0690j">Set the format statement to the following text (it can be copied and pasted from the file <Path>sample_files &rarr; niupepa &rarr; formats &rarr; search_tweak.txt</Path>.)</Text>
     2700<Text id="0690j">Set the format statement to the following text (it can be copied and pasted from the file <Path>sample_files &rarr; niupepa &rarr; formats &rarr; search_tweak.txt</Path>):</Text>
    26982701<Format>
    26992702&lt;td valign="top"&gt;[link][icon][/link]&lt;/td&gt;<br/>
    … …  
    30143017</NumberedItem>
    30153018<NumberedItem>
    3016 <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>
     3019<Text id="0756">Switch to the <AutoText key="glidict::GUI.Design"/> panel and select <AutoText key="glidict::CDM.GUI.Plugins"/>. Remove <AutoText text="GAPlug"/> from the list of plug-ins and add <AutoText text="METSPlug" />, with the default configuration options.</Text>
    30173020</NumberedItem>
    30183021<NumberedItem>
    … …  
    30923095<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.Format"/> panel), select the item that says:</Text>
    30933096<Indent>
    3094 CL2: AZCompactList -metadata <AutoText key="metadata::dc.Contributor"/>
     3097CL2: AZCompactList -metadata <AutoText key="metadata::dc.Contributor" type="plain"/>
    30953098</Indent>
    30963099</NumberedItem>
Note: See TracChangeset for help on using the changeset viewer.