- Timestamp:
- 2016-08-22T15:49:59+12:00 (8 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
documentation/trunk/tutorials/xml-source/tutorial_en.xml
r30732 r30734 754 754 </NumberedItem> 755 755 <NumberedItem> 756 <Text id="0386a">To change the text that is displayed for the index<MajorVersion number="2"> (<AutoText key="coredm::_Global:labelDescription_" type="italics"/>)</MajorVersion><MajorVersion number="3"> (<AutoText text="Descriptions" type="italics"/>)</MajorVersion>, 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. <MajorVersion number="2">Change</MajorVersion><MajorVersion number="3">Set</MajorVersion> the <AutoText key="glidict::CDM.SearchMetadataManager.Component_Name"/> for the "dc.Description" index to "image descriptions" (or other suitable text). Go back to the browser and reload the search page. Your new text will appear in the search form. </Text>756 <Text id="0386a">To change the text that is displayed for the index<MajorVersion number="2"> (<AutoText key="coredm::_Global:labelDescription_" type="italics"/>)</MajorVersion><MajorVersion number="3"> (<AutoText text="Descriptions" type="italics"/>)</MajorVersion>, 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. <MajorVersion number="2">Change</MajorVersion><MajorVersion number="3">Set</MajorVersion> the <AutoText key="glidict::CDM.SearchMetadataManager.Component_Name"/> for the "dc.Description" index to "image descriptions" (or other suitable text). Press the <AutoText key="glidict::CreatePane.Preview_Collection" type="button"/> button. In the browser, visit the collection's search page again. Your new text will appear in the search form. </Text> 757 757 <MajorVersion number="2"><Text id="0386a">To change the text that is displayed for the index (<AutoText key="coredm::_Global:labelDescription_" type="italics"/>), 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 "dc.Description" index to "image descriptions" (or other suitable text). Go back to the browser and reload the search page. Your new text will appear in the search form.</Text></MajorVersion> 758 758 <Comment> … … 787 787 </NumberedItem> 788 788 <NumberedItem> 789 <Text id="images-gps-3"> In the <b>Browsing Classifiers</b> section, choose <b>AZCompactList</b> from the <b>select classifier to add</b> dropdown box and press <b>Add Classifier...</b>. In the configuration dialog that appears, set the metadata field to <b>dc.Title</b> and tick the buttonname option and set its value to <Format>locations</Format>. This will create a classifier labelled <Format>locations</Format> that groups all images under Eiffel Tower into one bookshelf and similarly creates bookshelves for the other 3 categories.</Text>789 <Text id="images-gps-3">Go to the <AutoText key="glidict::GUI.Design"/> panel. In the <b>Browsing Classifiers</b> section, choose <b>AZCompactList</b> from the <b>select classifier to add</b> dropdown box and press <b>Add Classifier...</b>. In the configuration dialog that appears, set the metadata field to <b>dc.Title</b> and tick the buttonname option and set its value to <Format>locations</Format>. This will create a classifier labelled <Format>locations</Format> that groups all images under Eiffel Tower into one bookshelf and similarly creates bookshelves for the other 3 categories.</Text> 790 790 </NumberedItem> 791 791 <NumberedItem> … … 793 793 </NumberedItem> 794 794 <NumberedItem> 795 <Text id="images-gps-5">Preview the collection and click the <b>Locations</b> tab in the web browser. Expand the bookshelf icons displayed in the web browser to see thumbnail pictures of the photos gathered under the displayed metadata heading. Explore further, and click on a thumbnail photo sor two to view larger versions of the photos in the document view.</Text>795 <Text id="images-gps-5">Preview the collection and click the <b>Locations</b> tab in the web browser. Expand the bookshelf icons displayed in the web browser to see thumbnail pictures of the photos gathered under the displayed metadata heading. Explore further, and click on a thumbnail photo or two to view larger versions of the photos in the document view.</Text> 796 796 </NumberedItem> 797 797 … … 811 811 812 812 <NumberedItem> 813 <Text id="images-gps-9">Now go to the <b>Enrich</b> panel, expand the <b>eiffel-tower</b> folder and select the first image. Scroll down to see the metadata extracted during the building process. Among the extracted metad ta, you will find several pieces of Latitude and Longitude metadata, which we will be taking advantage of shortly: ex.Latitude, ex.Longitude, ex.LatShort, and ex.LngShort. </Text>813 <Text id="images-gps-9">Now go to the <b>Enrich</b> panel, expand the <b>eiffel-tower</b> folder and select the first image. Scroll down to see the metadata extracted during the building process. Among the extracted metadata, you will find several pieces of Latitude and Longitude metadata, which we will be taking advantage of shortly: ex.Latitude, ex.Longitude, ex.LatShort, and ex.LngShort. </Text> 814 814 </NumberedItem> 815 815 … … 818 818 </Heading> 819 819 <Text id="image-gps-10"> 820 Greenstone has a map view, based on the Google Maps API, that can make use of this location metadata. The map view can be controlled to appear in different parts of the interface: as part of a collection's search results page when browsing the collection, and/or when viewing a document. For this view to be operational in a Gre nstone, it is necessary for the collection to index the GPS metadata.</Text>820 Greenstone has a map view, based on the Google Maps API, that can make use of this location metadata. The map view can be controlled to appear in different parts of the interface: as part of a collection's search results page when browsing the collection, and/or when viewing a document. For this view to be operational in a Greenstone, it is necessary for the collection to index the GPS metadata.</Text> 821 821 <NumberedItem> 822 822 <Text id="images-gps-11">In the <b>Search Indexes</b> section of the <b>Design</b> panel, press the <b>New Index...</b> button. Scroll down and tick the boxes for <b>ex.LatShort</b>, <b>ex.Latitude</b>, <b>ex.LngShort</b> and <b>ex.Longitude</b> and press <b>Add Index</b> to create an index on all these 4 pieces of metadata.</Text> … … 829 829 </NumberedItem> 830 830 <NumberedItem> 831 <Text id="images-gps-14">To enable the map, go to the <b>Format Features</b> section of the <b>Format</b> panel, and select the <b>browse</b> format feature. In the editor below, enter the following format statement <i>a bove</i> the documentNode template:</Text>831 <Text id="images-gps-14">To enable the map, go to the <b>Format Features</b> section of the <b>Format</b> panel, and select the <b>browse</b> format feature. In the editor below, enter the following format statement <i>after</i> the line <Format><gsf:option name="TOC" value="true" /></Format>:</Text> 832 832 <Format><gsf:option name="mapEnabled" value="true" /></Format> 833 833 </NumberedItem> … … 946 946 </NumberedItem> 947 947 <MajorVersion number="3"><NumberedItem> 948 Next, go to <AutoText key="glidict::CDM.FormatManager.Feature"/> in the <AutoText key="glidict::GUI.Format"/> panel, and select the <AutoText key="glidict::CDM.GUI.SearchMetadata"/> section. Set the display text value for <b>Index: dc.Creator</b> to creators.948 Next, go to the <AutoText key="glidict::GUI.Format"/> panel, and select the <AutoText key="glidict::CDM.GUI.SearchMetadata"/> section to the left. On the right, set the display text value for <b>Index: dc.Creator</b> to <Format>creators</Format>. 949 949 </NumberedItem></MajorVersion> 950 950 <NumberedItem> … … 1058 1058 </MajorVersion> 1059 1059 <Heading> 1060 <Text id="fw-10a">Linking to Greenstone version or original version of documents</Text>1060 <Text id="fw-10a">Linking to the Greenstone version or original version of documents</Text> 1061 1061 </Heading> 1062 1062 <MajorVersion number="2"> … … 1255 1255 <Text id="pdfbox-ext-6">All going well, you will have a folder called <Format>pdf-box</Format> inside your Greenstone's <Format>ext</Format> folder.</Text> 1256 1256 </NumberedItem> 1257 </MajorVersion>1258 1257 <Heading>Turning on the PDFBox extension functionality in GLI</Heading> 1259 1258 <NumberedItem> … … 1264 1263 </Comment> 1265 1264 </NumberedItem> 1266 <NumberedItem> 1267 <Text id="pdfbox-ext-10">Launch GLI once more, in the manner you're accustomed to. On Windows, the easiest way is the shortcut to GLI available through the Windows <b>Start</b> menu.</Text> 1265 </MajorVersion> 1266 <NumberedItem> 1267 <Text id="pdfbox-ext-10">Launch GLI <MajorVersion number="2">once more, </MajorVersion>in the manner you're accustomed to. On Windows, the easiest way is the shortcut to GLI available through the Windows <b>Start</b> menu.</Text> 1268 1268 </NumberedItem> 1269 1269 <NumberedItem> … … 1271 1271 </NumberedItem> 1272 1272 <NumberedItem> 1273 <Text id="pdfbox-ext-11">Now that you've installed the PDFBox extension, this will be available as an option in the plugin's configuration dialog. To turn on the PDFBox extension, go to the <AutoText key="glidict::GUI.Design"/> panel, select <AutoText key="glidict::CDM.GUI.Plugins"/> from the left, and on the right double click the <AutoText text="PDFPlugin"/> (alternatively, select this plugin and click the <AutoText key="glidict::CDM.PlugInManager.Configure" type="button"/> below) to open the dialog to configure this plugin. In the <AutoText key="glidict::CDM.PlugInManager.Configure"/> dialog, scroll down to the section <AutoText text="AutoLoadConverters"/> and select the checkbox next to the <AutoText text="pdfbox_conversion"/> option. Click <AutoText key="glidict::General.OK"/> to close the dialog, switch to the <AutoText key="glidict::GUI.Create"/> panel and build your collection. This time, PDF files will be processed by PDFBox which will extract their text.</Text>1273 <Text id="pdfbox-ext-11">Now that you've installed the PDFBox extension, this will be available as an option in the plugin's configuration dialog. To turn on the PDFBox extension, go to the <AutoText key="glidict::GUI.Design"/> panel, select <AutoText key="glidict::CDM.GUI.Plugins"/> from the left, and on the right double click the <AutoText text="PDFPlugin"/> (alternatively, select this plugin and click the <AutoText key="glidict::CDM.PlugInManager.Configure" type="button"/> below) to open the dialog to configure this plugin. In the <AutoText key="glidict::CDM.PlugInManager.Configure"/> dialog, scroll down to the section <AutoText text="AutoLoadConverters"/> and select the checkbox next to the <AutoText text="pdfbox_conversion"/> option. Click <AutoText key="glidict::General.OK"/> to close the dialog, switch to the <AutoText key="glidict::GUI.Create"/> panel and build your collection. This time, the PDF files will be processed by PDFBox which will extract their text.</Text> 1274 1274 <Text id="pdfbox-ext-12">Try this feature out on a collection of recent PDF files, by configuring its PDFPlugin with the <AutoText text="pdfbox_conversion"/> option turned on.</Text> 1275 1275 </NumberedItem> … … 1618 1618 </NumberedItem> 1619 1619 <NumberedItem> 1620 <Text id="assoc-files-5">Copy the files pdf01.pdf and word03.doc provided in sample_files → Word_and_PDF → Documentsinto your new collection. Do this by dragging these files across from the filesystem view on the left of the <AutoText key="glidict::GUI.Gather"/> panel into the <b>Collection view</b> on the right.</Text>1620 <Text id="assoc-files-5">Copy the files pdf01.pdf and word03.doc provided in <Path>sample_files → Word_and_PDF → Documents</Path> into your new collection. Do this by dragging these files across from the filesystem view on the left of the <AutoText key="glidict::GUI.Gather"/> panel into the <b>Collection view</b> on the right.</Text> 1621 1621 </NumberedItem> 1622 1622 <NumberedItem> … … 1630 1630 </Heading> 1631 1631 <NumberedItem> 1632 <Text id="assoc-files-8">In <AutoText key="glidict::CDM.GUI.Plugins"/>, select the <AutoText text="WordPlugin"/> and press the <AutoText key="glidict::CDM.PlugInManager.Configure" type="button"/> button. In the resulting popup, scroll down to find the <Format>associate_ext</Format> option, and set this option to <AutoText text="pdf" type="italics"/>. Now, for Word documents, Greenstone will look for documents with the exact same name but the PDF file extension. These PDFs will not be processed separately; instead, they will be associated with their equivalent Word documents. (Alternatively, you could make the PDF document the primary document, by setting the <Format>associate_ext</Format> option in the <AutoText text="PDFPlugin"/> to <AutoText text="doc" type="italics"/>.)</Text>1632 <Text id="assoc-files-8">In <AutoText key="glidict::CDM.GUI.Plugins"/>, select the <AutoText text="WordPlugin"/> and press the <AutoText key="glidict::CDM.PlugInManager.Configure" type="button"/> button. In the resulting popup, scroll down to find the <Format>associate_ext</Format> option, and set this option to <AutoText text="pdf" type="italics"/>. Now, for Word documents, Greenstone will look for documents with the exact same name but the PDF file extension. These PDFs will not be processed separately; instead, they will be associated with their equivalent Word documents. (Alternatively, you could make the PDF document the primary document, by setting the <Format>associate_ext</Format> option in the <AutoText text="PDFPlugin"/> to <AutoText text="doc" type="italics"/>.)</Text> 1633 1633 </NumberedItem> 1634 1634 <NumberedItem> … … 1640 1640 <NumberedItem> 1641 1641 <Text id="assoc-files-15">Greenstone has internally associated the PDF version with the Word version of the document. However, with the default format statement, the end-user will have no idea that the PDF version exists. The collection built at this point (with default settings) only gives the user the choice of viewing either the Word version or the Greenstone-generated HTML version of the document. They are not given the option to view the PDF version.</Text> 1642 <Text id="assoc-files-16">To allow users to view the PDF version of the document,<MajorVersion number="2">change the default VList statement from this:</MajorVersion><MajorVersion number="3"> edit the <AutoText text="documentNode"/> template of the <AutoText text="Browse" /> to reference the <Format>equivDocIcon</Format> with a link to the PDF document <Format>equivDocLink</Format> as follows.</MajorVersion></Text>1642 <Text id="assoc-files-16">To allow users to view the PDF version of the document,<MajorVersion number="2">change the default VList statement from this:</MajorVersion><MajorVersion number="3"> edit the <AutoText text="documentNode"/> template of the <AutoText text="Browse" /> Format Feature in the <AutoText key="glidict::GUI.Format"/> panel, to reference the <Format>equivDocIcon</Format> with a link to the PDF document <Format>equivDocLink</Format> as follows.</MajorVersion></Text> 1643 1643 <MajorVersion number="2"> 1644 1644 <Format> … … 1833 1833 </Heading> 1834 1834 <NumberedItem> 1835 <Text id="0398">Switch to the <AutoText key="glidict::GUI.Gather"/> panel and in the right-hand side open <Path>englishhistory.net → tudor</Path>.</Text>1835 <Text id="0398">Switch to the <AutoText key="glidict::GUI.Gather"/> panel and on the right-hand side open <Path>englishhistory.net → tudor</Path>.</Text> 1836 1836 </NumberedItem> 1837 1837 <NumberedItem> … … 1860 1860 </Heading> 1861 1861 <NumberedItem> 1862 <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>citizens</Path> folder (a subfolder of <Path>englishhistory.net → tudor</Path>). Set its <AutoText key="metadata::dc.Subject"/> metadata to <b>Tudor period|Citizens</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. Click <AutoText key="glidict::General.OK" type="button"/> to close the popup.</Text>1862 <Text id="0438">Open up your <b>tudor</b> collection (the original version, not the <b>webtudor</b> version, in case you've already done that tutorial), switch to the <AutoText key="glidict::GUI.Enrich"/> panel and select the <Path>citizens</Path> folder (a subfolder of <Path>englishhistory.net → tudor</Path>). Set its <AutoText key="metadata::dc.Subject"/> metadata to <b>Tudor period|Citizens</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. Click <AutoText key="glidict::General.OK" type="button"/> to close the popup.</Text> 1863 1863 </NumberedItem> 1864 1864 <NumberedItem> … … 1867 1867 </NumberedItem> 1868 1868 <NumberedItem> 1869 <Text id="0440">Finally, select all remaining files—the ones that are not in the <Path>citizens</Path>, <Path>monarchs</Path>, or <Path>relative</Path> folders—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>1869 <Text id="0440">Finally, select all remaining files—the ones that are not in the <Path>citizens</Path>, <Path>monarchs</Path>, or <Path>relative</Path> folders—by selecting the first and shift-clicking the last. Set their <AutoText key="metadata::dc.Subject"/> metadata to <b>Tudor period|Others</b> and click outside the cell for the metadata to be assigned. This is done in a single operation (there is a short delay before it completes).</Text> 1870 1870 <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—e.g. <AutoText key="metadata::dc.Subject"/>—while others that pertain to only one or some of the files are displayed in grey—e.g. any extracted metadata.</Text> 1871 1871 <Text id="0440a-1">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> … … 1933 1933 </NumberedItem> 1934 1934 <NumberedItem> 1935 <Text id="0455">Search for a common term (like <i>the</i>)in all five index partitions, and check that the numbers of words (not documents) add up.</Text>1935 <Text id="0455">Search for the term <i>Mary</i> again, as that is likely to be common in all five index partitions, and check that the numbers of words (not documents) add up.</Text> 1936 1936 </NumberedItem> 1937 1937 <NumberedItem> … … 1999 1999 </MajorVersion> 2000 2000 <MajorVersion number="3"> 2001 <Text id="0475-3">In the <AutoText text="browse"/> format feature, replace the default <AutoText text="documentNode"/> template shown on the left with the simpler version on the right. <i>(The highlighted lines on the left are the ones that have been removed or modified. )</i></Text>2001 <Text id="0475-3">In the <AutoText text="browse"/> format feature, replace the default <AutoText text="documentNode"/> template shown on the left with the simpler version on the right. <i>(The highlighted lines on the left are the ones that have been removed or modified. Those highlighted on the right have been newly added.)</i></Text> 2002 2002 <table> 2003 2003 <th> … … 2050 2050 <Tab n="1"/><td valign="top"><br/> 2051 2051 <Tab n="2"/><gsf:link type="document"><br/><br/><br/><br/> 2052 <Tab n="3"/> <gsf:metadata name="Title"/><br/><br/><br/><br/>2052 <Tab n="3"/><highlight><gsf:metadata name="Title"/></highlight><br/><br/><br/><br/> 2053 2053 <Tab n="3"/><br/><br/> 2054 2054 <Tab n="3"/><i>(<gsf:metadata name="Source"/>)</i><br/><br/><br/> … … 2118 2118 <Tab n="1"/><td valign="top"><br/> 2119 2119 <Tab n="2"/><gsf:link type="document"><br/> 2120 <highlight><!--</highlight><br/>2121 <highlight>Defined in the global format statement</highlight><br/>2122 <highlight>--></highlight><br/>2123 2120 <Tab n="3"/><highlight><xsl:call-template name="choose-title"/></highlight><br/> 2124 <Tab n="3"/><highlight><gsf:switch></highlight><br/>2125 <Tab n="4"/><highlight><gsf:metadata name="Source"/></highlight><br/>2126 <Tab n="4"/><highlight><gsf:when test="exists"></highlight><br/>2127 <Tab n="5"/><highlight><br/></highlight><br/>2128 <Tab n="5"/><highlight><i>(<gsf:metadata name="Source"/>)</i></highlight><br/>2129 <Tab n="4"/><highlight></gsf:when></highlight><br/>2130 <Tab n="3"/><highlight></gsf:switch></highlight><br/>2131 2121 <Tab n="2"/></gsf:link><br/> 2122 <Tab n="2"/><highlight><gsf:switch></highlight><br/> 2123 <Tab n="3"/><highlight><gsf:metadata name="Source"/></highlight><br/> 2124 <Tab n="3"/><highlight><gsf:when test="exists"></highlight><br/> 2125 <Tab n="4"/><highlight><br/></highlight><br/> 2126 <Tab n="4"/><highlight><i>(<gsf:metadata name="Source"/>)</i></highlight><br/> 2127 <Tab n="3"/><highlight></gsf:when></highlight><br/> 2128 <Tab n="2"/><highlight></gsf:switch></highlight><br/> 2132 2129 <Tab n="1"/></td><br/> 2133 2130 </gsf:template><br/> … … 2274 2271 <Content> 2275 2272 <NumberedItem> 2276 <Text id="st-1a">In a browser, take a look at the Greenstone demo collection. Browse to one of the documents. This collection is based on HTML files, but they appear structured in the collection. This is because these HTML files were tagged by hand into sections.</Text>2273 <Text id="st-1a">In a browser, visit the Greenstone demo collection and have a ook at it. Browse to one of the documents. This collection is based on HTML files, but they appear structured in the collection. This is because these HTML files were tagged by hand into sections.</Text> 2277 2274 </NumberedItem> 2278 2275 <NumberedItem> … … 2333 2330 --> 2334 2331 </Format> 2335 <Text id="st-6"> The effect of these changes is to make a new subsection inside the <AutoText text="Introduction"/> chapter.</Text>2332 <Text id="st-6">Save the edited file and close it. The effect of these changes is to make a new subsection inside the <AutoText text="Introduction"/> chapter.</Text> 2336 2333 </NumberedItem> 2337 2334 <NumberedItem> … … 2429 2426 </NumberedItem> 2430 2427 <NumberedItem> 2431 <Text id="0433">Switch to the <AutoText key="glidict::GUI.Create"/> panel and <b>build</b> and <b>preview</b> the collection. Note that the document icons have changed. T he collection behaves exactly as before, except that when you click a document iconyour 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>2428 <Text id="0433">Switch to the <AutoText key="glidict::GUI.Create"/> panel and <b>build</b> and <b>preview</b> the collection. Note that the document icons have changed. Try clicking on <i>boleyn.html</i>. The collection behaves exactly as before, except that when you click a <i>document icon</i> 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> 2432 2429 </NumberedItem> 2433 2430 </Content> … … 2479 2476 </NumberedItem> 2480 2477 <NumberedItem> 2481 <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 <MajorVersion number="2"><AutoText text="form"/></MajorVersion><MajorVersion number="3">just <AutoText text="simpleform"/></MajorVersion>. This will make only fielded searching available for this collection.</Text>2478 <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="searchType"/> 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="searchType"/> format statement from the list of assigned formats, and set the contents to <MajorVersion number="2"><AutoText text="form"/></MajorVersion><MajorVersion number="3">just <AutoText text="simpleform"/></MajorVersion>. This will make only fielded searching available for this collection.</Text> 2482 2479 <Comment> 2483 2480 <MajorVersion number="2"><Text id="0531d">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></MajorVersion> … … 2764 2761 <MajorVersion number="2"> 2765 2762 <NumberedItem> 2766 <Text id="is-12b">Make fielded searching the default by changing the <AutoText text=" SearchTypes"/> format statement to <AutoText text="form,plain"/> (instead of <AutoText text="plain,form"/>).</Text>2763 <Text id="is-12b">Make fielded searching the default by changing the <AutoText text="searchType"/> format statement to <AutoText text="form,plain"/> (instead of <AutoText text="plain,form"/>).</Text> 2767 2764 </NumberedItem> 2768 2765 </MajorVersion> … … 3088 3085 </Format> 3089 3086 <Comment> 3090 <Text id="themes-12">ThemeRoller will not affect some aspects of you Greenstone library's appearance, e.g. the actual design layout, the background color, the font, the search button.</Text>3087 <Text id="themes-12">ThemeRoller will not affect some aspects of your Greenstone library's appearance, e.g. the actual design layout, the background color, the font, the search button.</Text> 3091 3088 </Comment> 3092 3089 </NumberedItem> … … 3129 3126 </NumberedItem> 3130 3127 <NumberedItem> 3131 <Text id="themes-14">Click the <AutoText text="Download theme"/> button. Ensure the Stable version of jQuery is selected. Under <AutoText text="Components"/> uncheck <AutoText text="Toggle All" type="italics"/>, which will uncheck all of the boxes. Under <AutoText text="UI Core"/> check <AutoText text="Core" type="italics"/>, and under <AutoText text="Widgets"/> check <AutoText text="Datepicker" type="italics"/>. At the bottom of the page, under <AutoText text="Theme"/>, <AutoText text="Custom Theme" type="italics"/> should be selected. (If there's an option to provide a <AutoText text="Theme Folder Name"/>, enter <AutoText text="TutorialTheme" type="italics"/>.) Leave <AutoText text="CSS Scope"/> blank. Click <AutoText text="Download"/>. In the pop-up window, select <AutoText text="Save File"/> and click <AutoText text="OK"/> to download the zip file.</Text>3132 </NumberedItem> 3133 <NumberedItem> 3134 <Text id="themes-15">Go to the folder where the zip file was downloaded, and unzip the folder (on Windows, right-click, select <AutoText text="Extract All..."/> and click <AutoText text="Extract"/>).</Text>3128 <Text id="themes-14">Click the <AutoText text="Download theme"/> button. <!--Ensure the Stable version of jQuery is selected.--> Select "<i>1.11.4 (Legacy, for jQuery1.6+)</i>". Under <AutoText text="Components"/> uncheck <AutoText text="Toggle All" type="italics"/>, which will uncheck all of the boxes. Under <AutoText text="UI Core"/> check <AutoText text="Core" type="italics"/>, and under <AutoText text="Widgets"/> check <AutoText text="Datepicker" type="italics"/>. At the bottom of the page, under <AutoText text="Theme"/>, <AutoText text="Custom Theme" type="italics"/> should be selected. (If there's an option to provide a <AutoText text="Theme Folder Name"/>, enter <AutoText text="TutorialTheme" type="italics"/>.) Leave <AutoText text="CSS Scope"/> blank. Click <AutoText text="Download"/>. In the pop-up window, select <AutoText text="Save File"/> and click <AutoText text="OK"/> to download the zip file.</Text> 3129 </NumberedItem> 3130 <NumberedItem> 3131 <Text id="themes-15">Go to the folder where the zip file was downloaded, and unzip the folder. On Windows, unzip as follows: right-click and select <AutoText text="Extract All..."/> Remove the folder name "jquery-ui-1.11.4.custom" from the end of the suggested zip extraction path. (For example, if it suggests <Path>C:\Users\me\Downloads\jquery-ui-1.11.4.custom</Path>, then change it to <Path>C:\Users\me\Downloads\</Path>.) Then click <AutoText text="Extract"/>.</Text> 3135 3132 <Text id="themes-16">The extracted folder will be called <AutoText text="jquery-ui-1.11.1.custom" type="italics"/>, or something similar. Rename it to <AutoText text="TutorialTheme"/>. It should contain css files, an index.html file, a couple of js files and 2 subfolders (called images and external). We largely only need the folder's structure, the css files (particularly jquery-ui.theme.min.css) and the images sufolder, but it's easiest just to copy the entire folder into <Path>Greenstone3 → web → interfaces → default → style → themes</Path>.</Text> 3136 3133 <!--<Text id="themes-16">The extracted folder should be named <AutoText text="jquery-ui-1.10.2.custom" type="italics"/>, or something similar, and should contain three folders (css, development-bundle, js) and an html file (index.html). In the <AutoText text="css"/> folder, there is a folder called <AutoText text="TutorialTheme"/>. Copy this entire folder into <Path>Greenstone3 → web → interfaces → default → style → themes</Path>.</Text>--> … … 3224 3221 </NumberedItem> 3225 3222 <NumberedItem> 3226 <Text id="customize-04">Click the <AutoText text="Download theme"/> button. Ensure the Stable version of jQuery is selected. Under <AutoText text="Components"/> uncheck <AutoText text="Toggle All" type="italics"/>, which will uncheck all of the boxes. Under <AutoText text="UI Core"/> check <AutoText text="Core" type="italics"/>, and under <AutoText text="Widgets"/> check <AutoText text="Datepicker" type="italics"/>. At the bottom of the page, under <AutoText text="Theme"/>, <AutoText text="Custom Theme" type="italics"/> should be selected. (If there's an option to provide a <AutoText text="Theme Folder Name"/>, enter <AutoText text="CollectionTheme" type="italics"/>.) Leave <AutoText text="CSS Scope"/> blank. Click <AutoText text="Download"/>. In the pop-up window, select <AutoText text="Save File"/> and click <AutoText text="OK"/> to download the zip file.</Text>3227 </NumberedItem> 3228 <NumberedItem> 3229 <Text id="customize-05">Go to the folder where the zip file was downloaded, and unzip the folder (on Windows, right-click, select <AutoText text="Extract All..."/> andclick <AutoText text="Extract"/>).</Text>3223 <Text id="customize-04">Click the <AutoText text="Download theme"/> button. <!--Ensure the Stable version of jQuery is selected.--> Select "<i>1.11.4 (Legacy, for jQuery1.6+)</i>". Under <AutoText text="Components"/> uncheck <AutoText text="Toggle All" type="italics"/>, which will uncheck all of the boxes. Under <AutoText text="UI Core"/> check <AutoText text="Core" type="italics"/>, and under <AutoText text="Widgets"/> check <AutoText text="Datepicker" type="italics"/>. At the bottom of the page, under <AutoText text="Theme"/>, <AutoText text="Custom Theme" type="italics"/> should be selected. (If there's an option to provide a <AutoText text="Theme Folder Name"/>, enter <AutoText text="CollectionTheme" type="italics"/>.) Leave <AutoText text="CSS Scope"/> blank. Click <AutoText text="Download"/>. In the pop-up window, select <AutoText text="Save File"/> and click <AutoText text="OK"/> to download the zip file.</Text> 3224 </NumberedItem> 3225 <NumberedItem> 3226 <Text id="customize-05">Go to the folder where the zip file was downloaded, and unzip the folder (on Windows, right-click, select <AutoText text="Extract All..."/>, remove the folder name <Format>jquery-ui-1.11.4.custom</Format> from the end of the suggested zip extraction path and then click <AutoText text="Extract"/>).</Text> 3230 3227 <Text id="customie-06">The extracted folder will be called <AutoText text="jquery-ui-1.11.1.custom" type="italics"/>, or something similar. Rename it to <AutoText text="CollectionTheme"/>. It should contain css files, an index.html file, a couple of js files and 2 subfolders (called images and external). Copy the entire folder into <Path>Greenstone3 → web → sites → localsite → collect → backdrop → style</Path>.</Text> 3231 3228 <!--<Text id="customie-06">The extracted folder should be named <AutoText text="jquery-ui-1.10.2.custom" type="italics"/>, or something similar, and should contain three folders (css, development-bundle, js) and an html file (index.html). In the <AutoText text="css"/> folder, there is a folder called <AutoText text="CollectionTheme"/>. Copy this entire folder into <Path>Greenstone3 → web → sites → localsite → collect → backdrop → style</Path>.</Text>--> … … 3323 3320 </NumberedItem> 3324 3321 <NumberedItem> 3325 <Text id="0554">Copy the files provided in</Text>3322 <Text id="0554">Copy the files and folders provided in</Text> 3326 3323 <Path>sample_files → beatles → advbeat_small</Path> 3327 3324 <Text id="0555">into your new collection. Do this by opening up <Path>advbeat_small</Path>, selecting the eight items within it (from <Path>discography</Path> to <Path>beatles_midi.zip</Path>), and dragging them across. Because some of these files are in MP3 and MARC formats you will be asked whether to include <AutoText text="MP3Plugin" /> and <AutoText text="MARCPlugin" /> in your collection. Click <AutoText key="glidict::CDM.PlugInManager.QuickAdd" type="button"/>.</Text> … … 3473 3470 </Bullet> 3474 3471 </BulletList> 3475 <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 (Be sure to use WordPad rather than Notepad, because Notepad does not display the line breaks correctly.):</Text>3472 <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. (Do not use Notepad, because Notepad does not display the line breaks correctly.)</Text> 3476 3473 <Path>sample_files → beatles → format_tweaks → audio_tweak_3.txt</Path> 3477 3474 <Text id="0586">The <Format>gsf:switch</Format> statement allows you to display different things depending on the value (or existence) of a metadata field. This switch statement is based on the value of <b>dc.Format</b>. If dc.Format equals <i>Audio</i>, then the source icon will be displayed, linking to the source document. (For the MP3 files, the MP3 icon will display, and clicking the icon will play the MP3.) If dc.Format equals <i>Images</i>, the image thumbnail will appear, linking to the full-size image. If dc.Format equals <i>Supplementary</i>, both the source and document icons will appear, linking to the source document and the document display page, respectively. Finally, the <Format>gsf:otherwise</Format> statement says what to do in all other cases.</Text> … … 3527 3524 </Bullet> 3528 3525 <Bullet> 3529 <Text id="0599">Remove the <AutoText key="metadata::dc.Title; ex.Title"/> classifier (at the top)</Text>3526 <Text id="0599">Remove the <AutoText key="metadata::dc.Title;Title"/> classifier (at the top)</Text> 3530 3527 </Bullet> 3531 3528 <Bullet> … … 4574 4571 <MajorVersion number="3"> 4575 4572 <Text id="oaiserver-22">Greenstone 3's OAI implementation uses the OAI standard for Dublin Core, <AutoText text="oai_dc" type="italics"/>, metadata format. By default, it maps all Dublin Core metadata you may have assigned to your collections into <AutoText text="oai_dc" type="italics"/>. This default mapping is specified in the <Path>web\WEB-INF\classes\OAIConfig.xml</Path> file. If all (or most) of your collections will be using a different metadata format, you can edit the OAIConfig.xml file's <Format>elementList</Format> section to create mappings from the metadata fields you're using to those in <AutoText text="oai_dc" type="italics"/>. You can also specify mappings at a collection-level, overriding the mappings in OAIConfig.xml for that collection. So if a collection specifies metadata for a different metadata set format from the default mappings in OAIConfig.xml, adjust the collection's <Path>web\sites\localsite\collect\<collection-name>\etc\collectionConfig.xml</Path> file to tell Greenstone how to map the metadata fields of your chosen metadata set format into the <AutoText text="oai_dc" type="italics"/> Dublin Core metadata set supported by the Greenstone OAI server.</Text> 4576 <Text id="oaiserver-23">For instance, look in the <b>demo</b> collection's collectionConfig.xml file (<Path>web\sites\localsite\collect\lucene-jdbm-demo\etc\collectionConfig.xml</Path>) and scroll down to the definition for the <Format>OAIPMH</Format> ServiceRack. Look at its section of <Format>element mappings</Format>, which will explain and provide an example for how to specify such an oai mapping from the <AutoText text="DLS" type="italics"/> metadata format that the <b>demo</b> collection uses, to the Dublin Core (<AutoText text="oai_dc" type="italics"/>) metadata used by Greenstone's OAI server. Its <AutoText key="metadata::dls.Organi sation"/> metadata is mapped to <AutoText text="oai_dc.publisher"/> using the following line in the collectionConfig.xml configuration file (note the use of case):</Text>4573 <Text id="oaiserver-23">For instance, look in the <b>demo</b> collection's collectionConfig.xml file (<Path>web\sites\localsite\collect\lucene-jdbm-demo\etc\collectionConfig.xml</Path>) and scroll down to the definition for the <Format>OAIPMH</Format> ServiceRack. Look at its section of <Format>element mappings</Format>, which will explain and provide an example for how to specify such an oai mapping from the <AutoText text="DLS" type="italics"/> metadata format that the <b>demo</b> collection uses, to the Dublin Core (<AutoText text="oai_dc" type="italics"/>) metadata used by Greenstone's OAI server. Its <AutoText key="metadata::dls.Organization"/> metadata is mapped to <AutoText text="oai_dc.publisher"/> using the following line in the collectionConfig.xml configuration file (note the use of case):</Text> 4577 4574 <Format><element name="dc:publisher"><br /> 4578 4575 <Tab n="1"/><mapping elements="dls.Organization" /><br /> … … 4819 4816 </Comment> 4820 4817 <NumberedItem> 4821 <Text id="0773"> Select <AutoText text="DSpacePlugin" /> and click <AutoText key="glidict::CDM.PlugInManager.Configure" type="button"/>. Switch on its configuration option <AutoText text="first_inorder_ext"/>. Set its value to <AutoText text="pdf,doc,rtf" type="quoted"/>.</Text>4818 <Text id="0773">Back in the <AutoText key="glidict::GUI.Design"/> panel's <AutoText key="glidict::CDM.GUI.Plugins"/> section, select <AutoText text="DSpacePlugin" /> and click <AutoText key="glidict::CDM.PlugInManager.Configure" type="button"/>. Switch on its configuration option <AutoText text="first_inorder_ext"/>. Set its value to <AutoText text="pdf,doc,rtf" type="quoted"/>.</Text> 4822 4819 </NumberedItem> 4823 4820 <NumberedItem> … … 5099 5096 </NumberedItem> 5100 5097 <NumberedItem> 5101 <Text id="indexers-27">Sometimes we may want to ignore word endings while searching so as to match different variations of the term. Go to the <AutoText key="coredm::_Global:linktextPREFERENCES_"/> page and change the <AutoText key="coredm::_preferences:textwordends_"/> option from <AutoText key="coredm::_preferences:textnostem_"/> to <AutoText key="coredm::_preferences:textstem_"/>. Click the <AutoText key="coredm::_preferences:textsetprefs_"/> button. Click <AutoText key="coredm::_Global:textSearch_"/>. This time try searching for <i>econom</i> again ,9 documents are found.</Text>5098 <Text id="indexers-27">Sometimes we may want to ignore word endings while searching so as to match different variations of the term. Go to the <AutoText key="coredm::_Global:linktextPREFERENCES_"/> page and change the <AutoText key="coredm::_preferences:textwordends_"/> option from <AutoText key="coredm::_preferences:textnostem_"/> to <AutoText key="coredm::_preferences:textstem_"/>. Click the <AutoText key="coredm::_preferences:textsetprefs_"/> button. Click <AutoText key="coredm::_Global:textSearch_"/>. This time try searching for <i>econom</i> again. 9 documents are found.</Text> 5102 5099 <Text id="indexers-27a">Please note that word endings are determined according to the third-party stemming tables incorporated in Greenstone, not by the user. Thus the searches may not do precisely what is expected, especially when cultural variations or dialects are concerned. Besides, not all languages support stemming, only English and French have stemming at the moment.</Text> 5103 5100 <Text id="indexers-27b">Go to the <AutoText key="coredm::_Global:linktextPREFERENCES_"/> page and change back to <AutoText key="coredm::_preferences:textnostem_"/> to avoid confusion later on. Click the <AutoText key="coredm::_preferences:textsetprefs_"/> button.</Text> … … 5534 5531 <Text id="dl-02">Start up your Greenstone server (<Path>Start → All Programs → Greenstone3.07 → Greenstone3 Server</Path>) and click the <b>Enter Library</b> button. This will take you to the default library's home page. This library uses the site called <b>localsite</b> and the interface called <b>default</b>. </Text> 5535 5532 5536 <Text id="dl-03">Change the url from <i>http://localhost:8383/greenstone3/library</i> to <i>http://localhost:8383/greenstone3/ gs2-library</i> and reload the page. This is another library that is defined by Greenstone3. Again, the site it uses is <b>localsite</b>, but this library (called <b>gs2-library</b>) uses the <b>gs2</b> interface, which is based on the Greenstone2 layout. Let's take a look at where these libraries are defined.</Text>5533 <Text id="dl-03">Change the url from <i>http://localhost:8383/greenstone3/library</i> to <i>http://localhost:8383/greenstone3/halftone-library</i> and reload the page. This is another library that is defined by Greenstone3. Again, the site it uses is <b>localsite</b>, but this library (called <b>halftone-library</b>) uses the <b>halftone</b> interface, which is based on the Greenstone2 layout. Let's take a look at where these libraries are defined.</Text> 5537 5534 </NumberedItem> 5538 5535 <NumberedItem> … … 5558 5555 5559 5556 5560 <Text id="hp-05">This <i>library servlet</i> defines the default Greenstone3 library (called <b>library</b>). As you can see, the <b>library_name</b> is <i>library</i>, the <b>site_name</b> is <i>localsite</i>, and the <b>interface_name</b> is <i>default</i>. If you look at the next servlet section, you will see that it has a library_name of <i> gs2-library</i>, uses <i>localsite</i> and the interface <i>gs2</i>. If you continue to scroll down, you will see several other library servlets defined. There are also other kinds of servlets, for example, you will see a servlet called <i>oaiserver</i>, which provides the functionality for the OAI server (located at <i>http://localhost:8383/greenstone3/oaiserver</i> ).</Text>5557 <Text id="hp-05">This <i>library servlet</i> defines the default Greenstone3 library (called <b>library</b>). As you can see, the <b>library_name</b> is <i>library</i>, the <b>site_name</b> is <i>localsite</i>, and the <b>interface_name</b> is <i>default</i>. If you look at the next servlet section, you will see that it has a library_name of <i>halftone-library</i>, uses <i>localsite</i> and the interface <i>halftone</i>. If you continue to scroll down, you will see several other library servlets defined. There are also other kinds of servlets, for example, you will see a servlet called <i>oaiserver</i>, which provides the functionality for the OAI server (located at <i>http://localhost:8383/greenstone3/oaiserver</i> ).</Text> 5561 5558 </NumberedItem> 5562 5559 <NumberedItem> … … 5707 5704 </NumberedItem> 5708 5705 <NumberedItem> 5709 <Text id="ni1-03">From <Path>sample_files → interfaces → aybara</Path> folder, copy the file <b>interfaceConfig.xml</b>into the <b>perrin</b> folder. Open the file <Path>perrin → interfaceConfig.xml</Path> in a text editor. The interface configuration file is used to specify the languages the interface is available in, certain options, and what "actions" are available. <b>Actions</b> create the web pages for the library and specify what XSL file should be used for each. For example, if you completed the Home Page Tutorial, you changed the <i>home</i> subaction to point to <i>home-tutorial.xsl</i> instead of <i>home.xsl</i>.</Text>5706 <Text id="ni1-03">From <Path>sample_files → interfaces → aybara</Path> folder, copy the <b>interfaceConfig.xml</b> file and the <b>galleryviewthemes</b> folder into the <b>perrin</b> folder. Open the file <Path>perrin → interfaceConfig.xml</Path> in a text editor. The interface configuration file is used to specify the languages the interface is available in, certain options, and what "actions" are available. <b>Actions</b> create the web pages for the library and specify what XSL file should be used for each. For example, if you completed the Home Page Tutorial, you changed the <i>home</i> subaction to point to <i>home-tutorial.xsl</i> instead of <i>home.xsl</i>.</Text> 5710 5707 5711 5708 <Text id="ni1-04">We are going to make one important change to this file. Our new interface is going to borrow heavily from the default interface. We will be reusing many of the XSL files, Javascript, and images. We could copy all of these files into our new interface, however, there are a few drawbacks to this solution:<br /><br /> … … 5778 5775 </NumberedItem> 5779 5776 <NumberedItem> 5780 <Text id="ni1-13">Visit <Link>http://www.os-templates.com/free-website-templates/news-magazine</Link> and click the <b>Download This Template</b> button. In the popup window, select <b>Save File</b> and click <b>OK</b>. This will download the file news-magazine.7z, which has a <i>7zip</i>extension. If you have 7zip installed, then you can extract the file in place. If not, you can either download the free utility, 7zip, from the web, or alternatively use an online service to convert it to a zip file that Windows can extract.</Text>5781 <Text id="ni1-13a">To do the latter, visit <AutoText text=" wobzip.org" />. Click the <AutoText text="Browse from computer" /> button, and in the file browser dialog that appears, navigate to where you downloaded the <i>news-magazine.7z</i> file, select the file and confirm to close the file browser dialog. Next, click the <AutoText text="Uncompress" /> button at <i>wobzip.org</i> and wait until the site has extracted the 7z file and takes you to its download page. When that page now loads, click the <AutoText text="Download as zip" /> button. (<i>After</i> downloading has finished, you can press the <AutoText text="Delete Upload" /> button to clear all your files from WOBZIP's server.)</Text>5782 <Text id="ni1-13b">On Windows, this will save the file <b>news-magazine.zip</b>in your <b>Downloads</b> folder. <i>This template is free to use and modify, but the Copyright and link information <b>must remain intact</b> in files and in the footer of every page. The template <b>cannot be distributed</b> (modified or otherwise) without express permission from OS-Templates. (The full license is provided in the <b>license.txt</b> file included with the template).</i></Text>5777 <Text id="ni1-13">Visit <Link>http://www.os-templates.com/free-website-templates/news-magazine</Link> and click the <b>Download This Template</b> button. In the popup window, select <b>Save File</b> and click <b>OK</b>. This will download a file with a <i>7z</i> (<i>7zip</i>) extension. If you have 7zip installed, then you can extract the file in place. If not, you can either download the free utility, 7zip, from the web, or alternatively use an online service to convert it to a zip file that Windows can extract.</Text> 5778 <Text id="ni1-13a">To do the latter, visit <AutoText text="http://convertio.co/uz-zip/" />. Click the red <AutoText text="From computer" /> button. In the file browser dialog that appears, navigate to where you downloaded the <i>7zip</i> file. Select this file and confirm to close the file browser dialog. Once the file has finished uploading, the online service will say "ready" and a red <AutoText text="Convert" /> button will appear. Click that button and wait until the convertio.co site has converted your 7z file to zip. When it's done, it will say "finished" and a small green button marked <AutoText text="Download" /> will appear. Click this button to download the zip version of the file. (<i>After</i> downloading has finished, you can press the close button, marked with a cross next to the download button, which will presumably clear your uploaded files from the convertio.co's server.)</Text> 5779 <Text id="ni1-13b">On Windows, your converted <i>zip</i> version of the template will have been saved in your <b>Downloads</b> folder. <i>This template is free to use and modify, but the Copyright and link information <b>must remain intact</b> in files and in the footer of every page. The template <b>cannot be distributed</b> (modified or otherwise) without express permission from OS-Templates. (The full license is provided in the <b>license.txt</b> file included with the template).</i></Text> 5783 5780 <Text id="ni1-14">In an Explorer window, navigate to your Downloads folder (<Path>C:\Users\<user-name>\Downloads</Path>). Right-click <b>news-magazine.zip</b>, select <b>Extract All...</b> and, in the popup window, click <b>Extract</b>.</Text> 5784 5781 </NumberedItem>
Note:
See TracChangeset
for help on using the changeset viewer.
