Changeset 11892
- Timestamp:
- 2006-05-30T17:36:41+12:00 (18 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/gsdl-documentation/tutorials/xml-source/tutorial_en.xml
r11859 r11892 251 251 </Heading> 252 252 <NumberedItem> 253 <Text id="0154">To run Greenstone, open the Windows Start menu, Programs, and select <i>Greenstone</i>, then the sub menu item<i> Digital Libraries in Education</i>: then <<b><i>Enter Library</i></b>>.</Text>253 <Text id="0154">To run Greenstone, open the Windows Start menu, Programs, and select <i>Greenstone</i>, then the sub-menu item<i> Digital Libraries in Education</i>: then <<b><i>Enter Library</i></b>>.</Text> 254 254 </NumberedItem> 255 255 <NumberedItem> … … 545 545 </Heading> 546 546 <Comment> 547 <Text id="0252y">If you have downloaded Greenstone from the web, then all the la guanges will be enabled by default. However, if you have installed Greenstone from a UNESCO CD-ROM, then only English, French, Spanish and Russian will be enabled.</Text>547 <Text id="0252y">If you have downloaded Greenstone from the web, then all the languages will be enabled by default. However, if you have installed Greenstone from a UNESCO CD-ROM, then only English, French, Spanish and Russian will be enabled.</Text> 548 548 </Comment> 549 549 <NumberedItem> … … 612 612 <Text id="0261">A window pops up. Fill it out with appropriate values—for example,</Text> 613 613 <Indent> 614 <Text id="0261a"> Collection Title: About Hobbits<br/></Text>615 <Text id="0261b"> Description of Content: A collection about hobbits.</Text>614 <Text id="0261a"><AutoText key="glidict::CDM.General.Collection_Name"/>: About Hobbits<br/></Text> 615 <Text id="0261b"><AutoText key="glidict::NewCollectionPrompt.Collection_Description"/>: A collection about hobbits.</Text> 616 616 </Indent> 617 617 <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> … … 624 624 </NumberedItem> 625 625 <NumberedItem> 626 <Text id="0264">Next you must gather together the files that will constitute the collection. A suitable set has been prepared ahead of time in <Path>sample_files </Path> in the folder <Path>hobbits</Path>. Using the left-hand side of the Librarian Interface's <AutoText key="glidict::GUI.Gather"/> panel, interactively navigate to the <Path>sample_files</Path> folder.</Text>626 <Text id="0264">Next you must gather together the files that will constitute the collection. A suitable set has been prepared ahead of time in <Path>sample_files → hobbits</Path>. Using the left-hand side of the Librarian Interface's <AutoText key="glidict::GUI.Gather"/> panel, interactively navigate to the <Path>sample_files</Path> folder.</Text> 627 627 </NumberedItem> 628 628 <Heading> … … 660 660 </NumberedItem> 661 661 <NumberedItem> 662 <Text id="0273">Use the scroll bar on the extreme right to view the bottom part of the list. There you will see fields starting <AutoText text="ex." type="quoted"/> that express the extracted metadata: for example <AutoText key="metadata::ex.Title"/>, based on the text within the HTML Title tags, and <AutoText key="metadata::ex.Language"/>, the document's language (represented using the ISO standard 2-letter mnemonic) which Greenstone determines by analy sing the document's text.</Text>662 <Text id="0273">Use the scroll bar on the extreme right to view the bottom part of the list. There you will see fields starting <AutoText text="ex." type="quoted"/> that express the extracted metadata: for example <AutoText key="metadata::ex.Title"/>, based on the text within the HTML Title tags, and <AutoText key="metadata::ex.Language"/>, the document's language (represented using the ISO standard 2-letter mnemonic) which Greenstone determines by analyzing the document's text.</Text> 663 663 </NumberedItem> 664 664 <NumberedItem> … … 780 780 </Heading> 781 781 <NumberedItem> 782 <Text id="0291a">In the <AutoText key="glidict::GUI.Enrich"/> panel, manually add Dublin Core <AutoText key="metadata::dc.Title"/> metadata to those documents which have incorre nt <AutoText key="metadata::ex.Title"/> metadata. Select <Path>word03.doc</Path> and double-click to open it. Copy the title of this document (<AutoText text="Greenstone: A comprehensive open-source digital library software system" type="quoted"/>) and return to the Librarian Interface. Scroll up or down in the metadata table until you can see <AutoText key="metadata::dc.Title"/>. Click in the value box, paste in the metadata and press <b>Enter</b>. </Text>782 <Text id="0291a">In the <AutoText key="glidict::GUI.Enrich"/> panel, manually add Dublin Core <AutoText key="metadata::dc.Title"/> metadata to those documents which have incorrect <AutoText key="metadata::ex.Title"/> metadata. Select <Path>word03.doc</Path> and double-click to open it. Copy the title of this document (<AutoText text="Greenstone: A comprehensive open-source digital library software system" type="quoted"/>) and return to the Librarian Interface. Scroll up or down in the metadata table until you can see <AutoText key="metadata::dc.Title"/>. Click in the value box, paste in the metadata and press <b>Enter</b>. </Text> 783 783 </NumberedItem> 784 784 <NumberedItem> … … 789 789 </NumberedItem> 790 790 <NumberedItem> 791 <Text id="0293">Next add <AutoText key="metadata::dc.Title"/> and <AutoText key="metadata::dc.Creator"/> metadata for a few of the other documents .</Text>792 </NumberedItem> 793 <NumberedItem> 794 <Text id="0291b">You will notice as you add more values, they appear in the <AutoText key="glidict::EnrichPane.ExistingValues" args="..."/> box below the metadata table. If you are adding the same metadata value to more than one document, you can select it from this list. For example, <Path>pdf01.pdf</Path> and <Path>word03.doc</Path> share the same Title; and many documents have common authors.</Text>791 <Text id="0293">Next add <AutoText key="metadata::dc.Title"/> and <AutoText key="metadata::dc.Creator"/> metadata for a few of the other documents, including <Path>pdf05-notext.pdf</Path>.</Text> 792 </NumberedItem> 793 <NumberedItem> 794 <Text id="0291b">You will notice as you add more values, they appear in the <AutoText key="glidict::EnrichPane.ExistingValues" args="..."/> box below the metadata table. If you are adding the same metadata value to more than one document, you can select it from this list. For example, <Path>pdf01.pdf</Path> and <Path>word03.doc</Path> share the same Title; and many documents have common authors.</Text> 795 795 </NumberedItem> 796 796 <Comment> … … 833 833 </NumberedItem> 834 834 <NumberedItem> 835 <Text id="0312">You can add indexes based on any metadata. Add a new index based on <AutoText key="metadata::dc.Creator"/>. Change the <AutoText key="glidict::CDM.IndexManager.Index_Name"/> field to "authors", and select <AutoText key="metadata::dc.Creator"/> in the <AutoText key="glidict::CDM.IndexManager.Source"/> . You will need to deselect the <AutoText key="metadata::ex.Title"/> and <AutoText key="metadata::dc.Title"/> metadata items. Click <AutoText key="glidict::CDM.IndexManager.Add_Index" type="button"/>.</Text>835 <Text id="0312">You can add indexes based on any metadata. Add a new index based on <AutoText key="metadata::dc.Creator"/>. Change the <AutoText key="glidict::CDM.IndexManager.Index_Name"/> field to "authors", and select <AutoText key="metadata::dc.Creator"/> in the <AutoText key="glidict::CDM.IndexManager.Source"/> list. You will need to deselect the <AutoText key="metadata::ex.Title"/> and <AutoText key="metadata::dc.Title"/> metadata items. Click <AutoText key="glidict::CDM.IndexManager.Add_Index" type="button"/>.</Text> 836 836 </NumberedItem> 837 837 <Comment> … … 842 842 </Heading> 843 843 <NumberedItem> 844 <Text id="0315a">The <AutoText key="glidict::CDM.GUI.Classifiers"/> section adds "classifiers," which provide the collection with browsing functions. Go to this section and observe that Greenstone has provided two classifiers, <i>AZLists</i> based on <AutoText key="metadata::ex.Title"/> and <AutoText key="metadata::ex.Source"/> metadata. These correspond to the <AutoText key="coredm::_Global:labelTitle_" type="italics"/> and <AutoText key="coredm::_Global:labelSource_" type="italics"/> buttons on the collection's access bar. Remove the <AutoText key="metadata::ex.Source"/> classifier by selecting it and clicking <AutoText key="glidict::CDM.ClassifierManager.Remove" type="button"/>.</Text> 844 <Text id="0315a">The <AutoText key="glidict::CDM.GUI.Classifiers"/> section adds "classifiers," which provide the collection with browsing functions. Go to this section and observe that Greenstone has provided two classifiers, <i>AZLists</i> based on <AutoText key="metadata::ex.Title"/> and <AutoText key="metadata::ex.Source"/> metadata. These correspond to the <AutoText key="coredm::_Global:labelTitle_" type="italics"/> and <AutoText key="coredm::_Global:labelSource_" type="italics"/> buttons on the collection's access bar. </Text> 845 <Text id="0315a-1">Remove the <AutoText key="metadata::ex.Source"/> classifier by selecting it and clicking <AutoText key="glidict::CDM.ClassifierManager.Remove" type="button"/>.</Text> 845 846 </NumberedItem> 846 847 <NumberedItem> 847 848 <Text id="0315b">Modify the <AutoText key="metadata::ex.Title"/> classifier to use <AutoText key="metadata::dc.Title"/> instead. Select the classifier and click <AutoText key="glidict::CDM.ClassifierManager.Configure" type="button"/>. In the <AutoText text="metadata"/> box, select <AutoText key="metadata::dc.Title"/> instead of <AutoText key="metadata::ex.Title"/>. Click <AutoText key="glidict::General.OK" type="button"/>.</Text> 848 </NumberedItem>849 <NumberedItem>850 <Text id="0316">Now we add an <AutoText text="AZList"/> classifier for <AutoText key="metadata::dc.Title"/> metadata. Select <AutoText text="AZList"/> from the <AutoText key="glidict::CDM.ClassifierManager.Classifier"/> drop-down list and click <AutoText key="glidict::CDM.ClassifierManager.Add" type="button"/>.</Text>851 </NumberedItem>852 <NumberedItem>853 <Text id="0317">A popup window <AutoText key="glidict::CDM.ArgumentConfiguration.Title"/> appears. Select <AutoText key="metadata::dc.Title"/> from the <AutoText text="metadata"/> drop-down list and click <AutoText key="glidict::General.OK" type="button"/>.</Text>854 849 </NumberedItem> 855 850 <NumberedItem> … … 864 859 </NumberedItem> 865 860 <NumberedItem> 866 <Text id="0321">Check that all the facilities work properly. There should be three full-text indexes, called <i>text</i>, <i>titles</i>, and <i>authors</i>. In the <AutoText key="coredm::_Global:labelTitle_" type="italics"/> list should appear all the documents to which you have assigned <AutoText key="metadata::dc.Title"/> metadata (and only those documents). In the <AutoText key="coredm::_Global:labelCreator_" type="italics"/> list should appearone bookshelf for each author you have assigned as <AutoText key="metadata::dc.Creator"/>, and clicking on that bookshelf should take you to all the documents they authored.</Text>861 <Text id="0321">Check that all the facilities work properly. There should be three full-text indexes, called <i>text</i>, <i>titles</i>, and <i>authors</i>. The <AutoText key="coredm::_Global:labelTitle_" type="italics"/> list should display all the documents to which you have assigned <AutoText key="metadata::dc.Title"/> metadata (and only those documents). The <AutoText key="coredm::_Global:labelCreator_" type="italics"/> list should show one bookshelf for each author you have assigned as <AutoText key="metadata::dc.Creator"/>, and clicking on that bookshelf should take you to all the documents they authored.</Text> 867 862 </NumberedItem> 868 863 <Heading> … … 873 868 </NumberedItem> 874 869 <NumberedItem> 875 <Text id="0321c">In the <AutoText key="glidict::CDM.GUI.Classifiers"/> section of the <AutoText key="glidict::GUI.Design"/> panel, select the <AutoText key="metadata::dc.Title"/> <AutoText text="AZList"/> classifierin the <AutoText key="glidict::CDM.ClassifierManager.Assigned"/> box and click <AutoText key="glidict::CDM.ClassifierManager.Configure" type="button"/>. Note you can achieve the same result by double clicking on the classifier.</Text>876 </NumberedItem> 877 <NumberedItem> 878 <Text id="0321d"> Type <AutoText text=",ex.Title" type="quoted"/> after the <AutoText key="metadata::dc.Title" type="quoted"/>—i.e. make it read</Text>870 <Text id="0321c">In the <AutoText key="glidict::CDM.GUI.Classifiers"/> section of the <AutoText key="glidict::GUI.Design"/> panel, select the <AutoText text="AZList"/> for <AutoText key="metadata::dc.Title"/> in the <AutoText key="glidict::CDM.ClassifierManager.Assigned"/> box and click <AutoText key="glidict::CDM.ClassifierManager.Configure" type="button"/>. Note you can achieve the same result by double clicking on the classifier.</Text> 871 </NumberedItem> 872 <NumberedItem> 873 <Text id="0321d">In the <AutoText text="metadata"/> field, type <AutoText text=",ex.Title" type="quoted"/> after the <AutoText key="metadata::dc.Title" type="quoted"/>—i.e. make it read</Text> 879 874 <Format> 880 875 <AutoText key="metadata::dc.Title" type="plain"/><AutoText text=",ex.Title" type="plain"/> … … 882 877 </NumberedItem> 883 878 <NumberedItem> 884 <Text id="0321e"><b>Build</b> the collection again and <b>preview</b> it. Now all the documents should appear in the <AutoText key="coredm::_Global:labelTitle_" type="italics"/> list.</Text> 879 <Text id="0321d-1">If you have already done the <TutorialRef id="enhanced_word"/> exercise, some of the documents will have extracted ex.Creator metadata, and some will have dc.Creator. To use both of these in the Creators classifier, make a similar change to the <AutoText text="AZCompactList"/>: make the <AutoText text="metadata"/> field read <Format><AutoText key="metadata::dc.Creator" type="plain"/><AutoText text=",ex.Creator" type="plain"/></Format>.</Text> 880 <Text id="0321d-2">You may notice that <AutoText text="AZCompactList"/> has two options after the <AutoText text="metadata"/> option: <AutoText text="firstvalueonly"/> and <AutoText text="allvalues"/>. Manually added metadata can be used to replace or enhance automatically extracted metadata, and these options control exactly which pieces of metadata a document is classified by.</Text> 881 <Text id="0321d-3">For example, say we have two documents. Document 1 has four Creators specified (dc.Creator = dcA, dc.Creator = dcB, ex.Creator = exA, ex.Creator = exB), while document 2 has three (ex.Creator = exA, ex.Creator = exB, ex.Creator = exC). The following table shows which metadata values each document is classified by, for the different classifier options:</Text> 882 <table> 883 <tr><td> 884 <Text id="0321d-4"><u><AutoText text="AZCompactList" type="plain"/> options</u></Text> 885 </td><td> 886 <Text id="0321d-5"><u>Document 1</u></Text> 887 </td><td> 888 <Text id="0321d-6"><u>Document 2</u></Text> 889 </td></tr> 890 <tr><td>-metadata dc.Creator,ex.Creator</td><td>dcA, dcB</td><td>exA, exB, exC</td></tr> 891 <tr><td>-metadata dc.Creator,ex.Creator -firstvalueonly</td><td>dcA</td><td>exA</td></tr> 892 <tr><td>-metadata dc.Creator,ex.Creator -allvalues</td><td>dcA, dcB, exA, exB</td><td>exA, exB, exC</td></tr> 893 </table> 894 </NumberedItem> 895 <NumberedItem> 896 <Text id="0321e"><b>Build</b> the collection again and <b>preview</b> it. Now all of the documents should appear in the <AutoText key="coredm::_Global:labelTitle_" type="italics"/> list (and extracted Creators should appear in the <AutoText key="coredm::_Global:labelCreator_" type="italics"/> list).</Text> 885 897 <Text id="0321f">Extracted metadata is unreliable. But it is very cheap! On the other hand, manually assigned metadata is reliable, but expensive. The previous section of this exercise has shown how to aim for the best of both worlds by using extracted metadata but correcting it when it is wrong. While this may not satisfy the professional librarian, it could provide a useful compromise for the music teacher who wants to get their collection together with a minimum of effort.</Text> 886 898 </NumberedItem> 887 <Comment>888 <Text id="0322">At this point you might like to publish the collection on CD-ROM, See <TutorialRef id="export_to_CDROM"/> for how to do this.</Text>889 </Comment>890 899 </Content> 891 900 </Tutorial> … … 897 906 <Content> 898 907 <NumberedItem> 899 <Text id="fw-2">Open the <b>reports</b> collection in the Librarian Interface and go to the Format Features section of the Designpanel.</Text>908 <Text id="fw-2">Open the <b>reports</b> collection in the Librarian Interface and go to the <AutoText key="glidict::CDM.GUI.Formats"/> section of the <AutoText key="glidict::GUI.Design"/> panel.</Text> 900 909 </NumberedItem> 901 910 <Heading> … … 907 916 <Text id="fw-4">The default <AutoText text="VList"/> format statement looks like the following:</Text> 908 917 <Format> 909 <td valign=top>[link][icon][/link]</td><br/> 910 <td valign=top>[ex.srclink]{Or}{[ex.thumbicon],<br/> 911 [ex.srcicon]}[ex./srclink]</td><br/> 912 <td valign=top>[highlight]<br/> 918 <td valign="top">[link][icon][/link]</td><br/> 919 <td valign="top">[ex.srclink]{Or}{[ex.thumbicon],[ex.srcicon]}[ex./srclink]</td><br/> 920 <td valign="top">[highlight]<br/> 913 921 {Or}{[dls.Title],[dc.Title],[ex.Title],Untitled}<br/> 914 922 [/highlight]{If}{[ex.Source],<br><i>([ex.Source])</i>}</td> … … 916 924 <Text id="fw-5">This format statement is the default used for search results, classifiers, and document table of contents. First we will tidy this up a bit. </Text> 917 925 918 <Text id="fw-6"><Format>{Or}{[ex.thumbicon],[ex.srcicon]}</Format> chooses ex.thumbicon metadata if its there, otherwise chooses ex.srcicon metadata. If neither are present, nothing is displayed. For this collection there is no ex.thumbiconmetadata so the choice is not needed.</Text>926 <Text id="fw-6"><Format>{Or}{[ex.thumbicon],[ex.srcicon]}</Format> chooses <i>ex.thumbicon</i> metadata if its there, otherwise chooses <i>ex.srcicon</i> metadata. If neither are present, nothing is displayed. For this collection there is no <i>ex.thumbicon</i> metadata so the choice is not needed.</Text> 919 927 920 928 <Text id="fw-7">Replace <Format>{Or}{[ex.thumbicon],[ex.srcicon]}</Format> with <Format>[ex.srcicon]</Format>. </Text> 921 929 922 <Text id="fw-8">There is no dls.Titlemetadata, so remove that element from <Format>{Or}{[dls.Title],[dc.Title],[ex.Title],Untitled}</Format>.</Text>930 <Text id="fw-8">There is no <i>dls.Title</i> metadata, so remove that element from <Format>{Or}{[dls.Title],[dc.Title],[ex.Title],Untitled}</Format>.</Text> 923 931 924 932 <Text id="fw-9">The resulting format statement looks like the following:</Text> … … 929 937 {Or}{[dc.Title],[ex.Title],Untitled}[/highlight] {If}{[ex.Source],<br><i>([ex.Source])</i>}</td><br/> 930 938 </Format> 939 <Text id="fw-9a">Click <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/>.</Text> 931 940 <Text id="fw-10">Preview the collection to make sure the display hasn't changed.</Text> 932 941 … … 947 956 </Heading> 948 957 <NumberedItem> 949 <Text id="fw-14">Next, we'll customize the format for the <AutoText key="coredm::_labelCreator_" type="italics"/> list. Classifier nodes have only a few pieces of metadata to display: <Format>[ex.Title]</Format> and <Format>[numleafdocs]</Format>. Whatever metadata the classifier has been built on, the node label is always stored as <Format>[ex.Title]</Format>. This is why a Creator is printed out for each bookshelf node even though dc.Creatoris not specified in the format statement. <Format>[numleafdocs]</Format> is only defined for bookshelf nodes, so this metadata can be used in an <Format>{If}</Format> statement to make bookshelf nodes and document nodes display differently.</Text>958 <Text id="fw-14">Next, we'll customize the format for the <AutoText key="coredm::_labelCreator_" type="italics"/> list. Classifier nodes have only a few pieces of metadata to display: <Format>[ex.Title]</Format> and <Format>[numleafdocs]</Format>. Whatever metadata the classifier has been built on, the node label is always stored as <Format>[ex.Title]</Format>. This is why a Creator is printed out for each bookshelf node even though <i>dc.Creator</i> is not specified in the format statement. <Format>[numleafdocs]</Format> is only defined for bookshelf nodes, so this metadata can be used in an <Format>{If}</Format> statement to make bookshelf nodes and document nodes display differently.</Text> 950 959 951 960 </NumberedItem> 952 961 <NumberedItem> 953 <Text id="fw-15">Make each bookshelf node in the Creator classifier show how many entries it contains. In the <AutoText key="glidict::CDM.GUI.Formats"/> section of the <AutoText key="glidict::GUI.Design"/> panel, select the Creatorclassifier from the <AutoText key="glidict::CDM.FormatManager.Feature"/> drop down list, and <AutoText text="VList"/> from the <AutoText key="glidict::CDM.FormatManager.Part"/> list. Append the following: </Text>962 <Text id="fw-15">Make each bookshelf node in the Creator classifier show how many entries it contains. In the <AutoText key="glidict::CDM.GUI.Formats"/> section of the <AutoText key="glidict::GUI.Design"/> panel, select the dc.Creator <AutoText text="AZCompactList"/> classifier from the <AutoText key="glidict::CDM.FormatManager.Feature"/> drop down list, and <AutoText text="VList"/> from the <AutoText key="glidict::CDM.FormatManager.Part"/> list. Append the following: </Text> 954 963 <Format> 955 964 {If}{[numleafdocs],<td><i>([numleafdocs])</i></td>} 956 965 </Format> 957 <Text id="fw-16">Click <AutoText key="glidict::CDM.FormatManager.Add" type="button"/>, switch to the <AutoText key="glidict::GUI.Create"/> panel, and click <AutoText key="glidict::CreatePane.Preview_Collection" type="button"/> (no need to rebuild). </Text> 958 966 <Text id="fw-16">Click <AutoText key="glidict::CDM.FormatManager.Add" type="button"/>, switch to the <AutoText key="glidict::GUI.Create"/> panel, and click <AutoText key="glidict::CreatePane.Preview_Collection" type="button"/> (no need to rebuild). Preview the <AutoText key="coredm::_labelCreator_" type="italics"/> list.</Text> 959 967 <Text id="fw-17">This revised format statement has the effect of specifying in brackets how many items are contained within a bookshelf. Since only bookshelf nodes define <Format>[numleafdocs]</Format>, only these nodes will display this. By modifying <AutoText text="CL2VList"/> instead of <AutoText text="VList"/>, the change will only apply to the second classifier (Creators).</Text> 960 961 968 </NumberedItem> 962 969 <Heading> … … 964 971 </Heading> 965 972 <NumberedItem> 966 <Text id="fw-18"> Modify the document nodes in the Creator classifier to display all authors. After <Format>{If}{[ex.Source],<br></Format> in the format statement, add <Format>[sibling:ex.Creator]</Format>.</Text>973 <Text id="fw-18">Next we modify the document nodes in the Creator classifier to display all authors. Back in <AutoText key="glidict::CDM.GUI.Formats"/>, select the <AutoText text="CL2VList"/> format in the list of assigned formats. After <Format>{If}{[ex.Source],<br></Format> in the format statement, add <Format>[sibling:dc.Creator]</Format>.</Text> 967 974 <Text id="fw-19"><Format>[ex.Source]</Format> is not defined for bookshelf nodes, so can also be used to differentiate bookshelves and documents.</Text> 968 969 975 <Text id="fw-20">The resulting format statement looks like:</Text> 970 976 <Format> … … 973 979 <td valign=top>[highlight]<br/> 974 980 {Or}{[dc.Title],[ex.Title],Untitled}[/highlight]<br/> 975 {If}{[ex.Source],<br>[sibling: ex.Creator] <br/>981 {If}{[ex.Source],<br>[sibling:dc.Creator] <br/> 976 982 <i>([ex.Source])</i>}</td><br/> 977 983 {If}{[numleafdocs],<td><i>([numleafdocs])</i></td>} 978 984 </Format> 979 <Text id="fw-21">This will display the Greenstone link, the link to the original, then the Title. For bookshelf nodes, it will also display how many documents the bookshelf contains. For document nodes, it will display all the Authors (Creators), and the source document. <Format>[sibling: ex.Creator]</Format> displays all the Creator metadata for the document, separated by <AutoText text=", " type="italics"/>. Preview the <AutoText key="coredm::_labelCreator_" type="italics"/> list.</Text>980 981 <Text id="fw-2 2">Change the separator between the authors. Modify the format statement, and replace <Format>[sibling:ex.Creator]</Format> with <Format>[sibling(All'<br/>'):ex.Creator]</Format>. This will add a new line after each author. Preview the <AutoText key="coredm::_labelCreator_" type="italics"/> list.</Text>985 <Text id="fw-21">This will display the Greenstone link, the link to the original, then the Title. For bookshelf nodes, it will also display how many documents the bookshelf contains. For document nodes, it will display all the Authors (Creators), and the source document. <Format>[sibling:dc.Creator]</Format> displays all the Creator metadata for the document, separated by a space (<AutoText text=" " type="quoted"/>). Preview the <AutoText key="coredm::_Global:labelCreator_" type="italics"/> list.</Text> 986 <Text id="fw-22">Change the separator between the authors. Modify the format statement, and replace <Format>[sibling:dc.Creator]</Format> with <Format>[sibling(All'<br/>'):dc.Creator]</Format>. This will add a new line after each author. Preview the <AutoText key="coredm::_Global:labelCreator_" type="italics"/> list.</Text> 987 <Text id="fw-23">If you have done exercise <TutorialRef id="enhanced_word"/>, the collection will have both dc.Creator and ex.Creator metadata. To display both, you can use <Format>[sibling:dc.Creator] [sibling:ex.Creator]</Format>, or to display dc.Creator if its present, otherwise display ex.Creator, use <Format>{Or}{[sibling:dc.Creator],[sibling:ex.Creator]}</Format>.</Text> 982 988 </NumberedItem> 983 989 </Content> … … 990 996 <Version initial="2.70" current="2.70"/> 991 997 <Content> 992 <Text id="ep-2">Greenstone converts PDF files to HTML using third-party software: <AutoText text="pdftohtml.pl" type="it laics"/>. This lets users view these documents even if they don't have the PDF software installed. Unfortunately, sometimes the formatting of the resulting HTML files is not so good.</Text>998 <Text id="ep-2">Greenstone converts PDF files to HTML using third-party software: <AutoText text="pdftohtml.pl" type="italics"/>. This lets users view these documents even if they don't have the PDF software installed. Unfortunately, sometimes the formatting of the resulting HTML files is not so good.</Text> 993 999 <Text id="ep-3">This exercise explores some extra options to the PDF plugin which may produce a nicer version for display. Some of these options use the standard pdftohtml program, others use ImageMagick and Ghostscript to convert the file to a series of images. Ghostscript is a program that can convert Postscript and PDF files to other formats. You can download it from <Link>http://www.cs.wisc.edu/~ghost/</Link> (follow the link to the current stable release).</Text> 994 1000 <NumberedItem> 995 <Text id="ep-4">In a browser, preview the reports collection created in exercise <TutorialRef id="word_pdf_collection"/>, and view the documents. Remember that <Path>pdf05-notext</Path> couldn't be processed during building, because there was no extracted text, and therefore doesn't appear in the collection. Note that the other PDF documents appear as one long document, with no sections. </Text> 1001 <Text id="ep-3a">In the Librarian Interface, open up the <b>reports</b> collection created in the <TutorialRef id="word_pdf_collection"/> exercise. Rebuild the collection and examine the output. You will notice that one of the documents could not be processed. The following messages are shown: "The file pdf05-notext.pdf was recognised but could not be processed by any plugin.", and "15 documents were processed and included in the collection. 1 was rejected".</Text> 1002 </NumberedItem> 1003 <NumberedItem> 1004 <Text id="ep-4">Preview the collection and view the documents. <Path>pdf05-notext.pdf</Path> does not appear. Note that the other PDF documents appear as one long document, with no sections. </Text> 996 1005 </NumberedItem> 997 1006 <Heading> … … 999 1008 </Heading> 1000 1009 <Comment> 1001 <Text id="0334">The Librarian Interface can operate in different modes. So far, you have been using the default mode, called <AutoText key="glidict::Preferences.Mode.Librarian"/>. </Text> 1002 </Comment> 1003 <NumberedItem> 1004 <Text id="0334a">In the Librarian Interface, rebuild the collection. During the building process this message appears: <AutoText key="perlmodules::plugin.n_included" type="quoted" args="14"/>; <AutoText key="perlmodules::plugin.one_rejected" type="quoted"/>.</Text> 1005 </NumberedItem> 1006 <NumberedItem> 1007 <Text id="0335">Use the <AutoText key="glidict::Menu.File_Options"/> item on the <AutoText key="glidict::Menu.File"/> menu to switch to <AutoText key="glidict::Preferences.Mode.Expert"/> mode and then build the collection again. The <AutoText key="glidict::GUI.Create"/> panel looks different in <AutoText key="glidict::Preferences.Mode.Expert"/> mode because it gives more options: locate the <AutoText key="glidict::CreatePane.Build_Collection" type="button"/> button, near the bottom of the window, and click it. Now a message appears saying that the file could not be processed, and why.</Text> 1010 <Text id="0334">The Librarian Interface can operate in different modes. The default mode is <AutoText key="glidict::Preferences.Mode.Librarian"/> mode. We can use <AutoText key="glidict::Preferences.Mode.Expert"/> mode to work out why the pdf file could not be processed.</Text> 1011 </Comment> 1012 <NumberedItem> 1013 <Text id="0335">Use the <AutoText key="glidict::Menu.File_Options"/> item on the <AutoText key="glidict::Menu.File"/> menu to switch to <AutoText key="glidict::Preferences.Mode.Expert"/> mode and then build the collection again. The <AutoText key="glidict::GUI.Create"/> panel looks different in <AutoText key="glidict::Preferences.Mode.Expert"/> mode because it gives more options: locate the <AutoText key="glidict::CreatePane.Build_Collection" type="button"/> button, near the bottom of the window, and click it. Now a message appears saying that the file could not be processed, and why. Amongst all the output, we get the following message: "Error: PDF contains no extractable text. Could not convert pdf05notext.pdf to HTML format". pdftohtml.pl to convert a PDF file to HTML if the PDF file has no extractable text.</Text> 1008 1014 </NumberedItem> 1009 1015 <NumberedItem> … … 1011 1017 </NumberedItem> 1012 1018 <Heading> 1013 <Text id="ep-5"> Tidying up the HTML format</Text>1019 <Text id="ep-5">Splitting PDFs into sections</Text> 1014 1020 </Heading> 1015 1021 <NumberedItem> 1016 1022 <Text id="ep-6">In the <AutoText key="glidict::CDM.GUI.Plugins"/> section of the <AutoText key="glidict::GUI.Design"/> panel, configure <AutoText text="PDFPlug"/>. Switch on the <AutoText text="use_sections"/> option. </Text> 1017 1018 <Text id="ep-7">Build and preview the collection. Note that all the PDF documents are now split into a series of pages, and a goto page box is provided. The format is still a bit ugly though.</Text> 1019 1020 </NumberedItem> 1021 <NumberedItem> 1022 <Text id="ep-8">Back in the <AutoText key="glidict::CDM.GUI.Plugins"/> section, configure <AutoText text="PDFPlug"/> again. Switch on the <AutoText text="complex"/> option. This will make <AutoText text="PDFPlug"/> use Ghostscript to try and generate nicer HTML. Ghostscript needs to be installed for this to work.</Text> 1023 1024 <Text id="ep-9">Build and preview the collection, and see how the format has changed to more closely resemble the original. In particular, you can see that <Path>pdf01.pdf</Path> has retained its columns in the HTML.</Text> 1025 1026 <Text id="ep-10">The PDF document with no text (<Path>pdf05-notext.pdf</Path>) now appears in the collection, but has no contents. The PDF with weird characters (<Path>pdf06-weirdchars.pdf</Path>) still does not display properly.</Text> 1023 <Text id="ep-7"><b>Build</b> and <b>preview</b> the collection. View the text versions of some of the PDF documents. Note that these are now split into a series of pages, and a "go to page" box is provided. The format is still a bit ugly though.</Text> 1027 1024 </NumberedItem> 1028 1025 <Heading> … … 1034 1031 </NumberedItem> 1035 1032 <NumberedItem> 1036 <Text id="ep-13">In the <AutoText key="glidict::CDM.GUI.Plugins"/> section, configure <AutoText text="PDFPlug"/>. Set the <AutoText text="convert_to"/> option to one of the image types, e.g. <AutoText text="pagedimg_jpg"/>. Switch off the <AutoText text="use_sections"/> and <AutoText text="complex"/> options, as they arenot used with image conversion. </Text>1033 <Text id="ep-13">In the <AutoText key="glidict::CDM.GUI.Plugins"/> section, configure <AutoText text="PDFPlug"/>. Set the <AutoText text="convert_to"/> option to one of the image types, e.g. <AutoText text="pagedimg_jpg"/>. Switch off the <AutoText text="use_sections"/> option, as it is not used with image conversion. </Text> 1037 1034 </NumberedItem> 1038 1035 <NumberedItem> … … 1063 1060 </NumberedItem> 1064 1061 <NumberedItem> 1065 <Text id="ep-21">We achieve this by adding two <AutoText text="PDFPlug"/> plugins to the collection, with different options. Currently, the Librarian Interface does not allow you to add the same plugin twice to the collection (with the exception of <AutoText text="UnknownPlug"/>). You will need to edit the collection configuration file by hand. Close the reports collection in the Librarian Interface. Then open <Path>Greenstone → collect → reports → etc → collect.cfg</Path> using a text editor, e.g. WordPad. In the list of plugins, add another <AutoText text="PDFPlug"/>, i.e.</Text> 1062 <Text id="ep-21">We achieve this by adding two <AutoText text="PDFPlug"/> plugins to the collection, with different options. Currently, the Librarian Interface does not allow you to add the same plugin twice to the collection (with the exception of <AutoText text="UnknownPlug"/>). You will need to edit the collection configuration file by hand.</Text> 1063 <Text id="ep-21a">Close the reports collection in the Librarian Interface. Then open <Path>Greenstone → collect → reports → etc → collect.cfg</Path> using a text editor, e.g. WordPad. In the list of plugins, add another <AutoText text="PDFPlug"/>, i.e.</Text> 1066 1064 <Format> 1067 1065 plugin PDFPlug … … 1069 1067 <Text id="ep-22">Don't worry about the options here - we will add these using the Librarian Interface.</Text> 1070 1068 <Text id="ep-22a">Note that if you ever need to edit a collection's <Path>collect.cfg</Path> file by hand, you must close the collection in the Librarian Interface first, otherwise the next time it saves the file, it will overwrite your changes.</Text> 1071 1072 </NumberedItem> 1073 <NumberedItem> 1074 <Text id="ep-23">Open up the collection again in the Librarian Interface, and go to the Gather panel. Make a new folder called <AutoText text="notext" type="quoted"/>. Right click in the collection panel and select <AutoText key="glidict::CollectionPopupMenu.New_Folder"/> from the menu. Change the <AutoText key="glidict::NewFolderOrFilePrompt.Folder_Name"/> to <AutoText text="notext" type="quoted"/>, and click <AutoText key="glidict::General.OK" type="button"/>. Move the two pdf files that have problems with html (<Path>pdf05-notext.pdf</Path> and <Path>pdf06-weirdchars</Path>.pdf ) into this folder by drag and drop. We will set up the plugins so that PDF files in this <Path>notext</Path> folder are processed differently to the other PDF files.</Text> 1075 1069 </NumberedItem> 1070 <NumberedItem> 1071 <Text id="ep-23">Open up the collection again in the Librarian Interface, and go to the <AutoText key="glidict::GUI.Gather"/> panel. Make a new folder called <AutoText text="notext" type="quoted"/>: right click in the collection panel and select <AutoText key="glidict::CollectionPopupMenu.New_Folder"/> from the menu. Change the <AutoText key="glidict::NewFolderOrFilePrompt.Folder_Name"/> to <AutoText text="notext" type="quoted"/>, and click <AutoText key="glidict::General.OK" type="button"/>.</Text> 1072 <Text id="ep-23a">Move the two pdf files that have problems with html (<Path>pdf05-notext.pdf</Path> and <Path>pdf06-weirdchars</Path>.pdf ) into this folder by drag and drop. We will set up the plugins so that PDF files in this <Path>notext</Path> folder are processed differently to the other PDF files.</Text> 1076 1073 </NumberedItem> 1077 1074 <NumberedItem> 1078 1075 <Text id="ep-24">Switch to the <AutoText key="glidict::CDM.GUI.Plugins"/> section of the <AutoText key="glidict::GUI.Design"/> panel. You will see that there are two PDFPlug plugins in the list. </Text> 1079 1080 1076 </NumberedItem> 1081 1077 <NumberedItem> … … 1090 1086 </Format> 1091 1087 1092 <Text id="ep-27">The paged_img version must come earlier in the list than the html version. The <AutoText text="process_exp"/> for the first <AutoText text="PDFPlug"/> will process any PDffiles in the <Path>notext</Path> directory. The second <AutoText text="PDFPlug"/> will process any PDF files that are not processed by the first one.</Text>1088 <Text id="ep-27">The <AutoText text="paged_img" type="italics"/> version must come earlier in the list than the <AutoText text="html" type="italics"/> version. The <AutoText text="process_exp"/> for the first <AutoText text="PDFPlug"/> will process any PDF files in the <Path>notext</Path> directory. The second <AutoText text="PDFPlug"/> will process any PDF files that are not processed by the first one.</Text> 1093 1089 1094 1090 <Text id="ep-28">Note that all plugins have the <AutoText text="process_exp"/> option, and this can be used to customize which documents are processed by which plugin. This option is only visible in <AutoText key="glidict::Preferences.Mode.Systems"/> and <AutoText key="glidict::Preferences.Mode.Expert"/> modes.</Text> … … 1156 1152 </Bullet> 1157 1153 <Bullet> 1158 <Text id="ew-15"><AutoText text="Chapter Title" type="italics"/>: Level 1 section heading</Text>1154 <Text id="ew-15"><AutoText text="Chapter Title" type="italics"/>: Level 1 section heading</Text> 1159 1155 </Bullet> 1160 1156 <Bullet> … … 1162 1158 </Bullet> 1163 1159 <Bullet> 1164 <Text id="ew-17"><AutoText text="Reference Heading" type="italics"/>: Reference section</Text>1160 <Text id="ew-17"><AutoText text="Reference Heading" type="italics"/>: Reference section</Text> 1165 1161 </Bullet> 1166 1162 </BulletList> … … 1177 1173 </Format> 1178 1174 <Text id="ew-12">These header options define which styles should be considered as title, level 1, level 2 and level 3 styles. </Text> 1179 <Text id="ew-12a">Set the options as follows :</Text>1180 <Format> 1181 level1_header:(SammaryHeader|ChapterTitle|ReferenceHeading |Reference_heading)<br/>1175 <Text id="ew-12a">Set the options as follows (spaces are removed when converting to HTML styles):</Text> 1176 <Format> 1177 level1_header:(SammaryHeader|ChapterTitle|ReferenceHeading)<br/> 1182 1178 level2_header: SectionHeading<br/> 1183 1179 title_header: PaperTitle 1184 1180 </Format> 1181 <Comment> 1182 <Text id="ew-23b">If you can't see these options in the <AutoText text="WordPlug"/> configuration pane, check that you are in <AutoText key="glidict::Preferences.Mode.Systems"/> mode as described above.</Text> 1183 </Comment> 1185 1184 <Text id="ew-23">Once these are set, click <AutoText key="glidict::General.OK" type="button"/>.</Text> 1186 1185 </NumberedItem> … … 1199 1198 </NumberedItem> 1200 1199 <NumberedItem> 1201 <Text id="ew-22">To remove the tables of contents and figures from <Path>word06.doc</Path>, switch on the <AutoText text="delete_toc"/> option in <AutoText text="WordPlug"/>. Set the header styles as follows:</Text> 1202 <Format> 1203 toc_header: (MsoToc1|MsoToc2|MsoToc3)<br/> 1204 tof_header: MsoTof 1205 </Format> 1200 <Text id="ew-22">To remove the tables of contents and figures from <Path>word06.doc</Path>, switch on the <AutoText text="delete_toc"/> option in <AutoText text="WordPlug"/>. Set the <AutoText text="toc_header"/> option to <Format>(MsoToc1|MsoToc2|MsoToc3|MsoTof)</Format>. In this document, the table of contents and list of figures use these four style names. Click <AutoText key="glidict::General.OK" type="button"/>.</Text> 1206 1201 </NumberedItem> 1207 1202 <NumberedItem> 1208 1203 <Text id="ew-24">Build and preview the collection. <Path>word06.doc</Path> should now have only one table of contents.</Text> 1209 1204 </NumberedItem> 1205 <NumberedItem> 1206 <Text id="ew-24a">Switch the Librarian Interface back to <AutoText key="glidict::Preferences.Mode.Librarian"/> mode (<Menu><AutoText key="glidict::Menu.File"/> → <AutoText key="glidict::Menu.File_Options"/> → <AutoText key="glidict::Preferences.Mode"/></Menu>).</Text> 1207 </NumberedItem> 1210 1208 <Heading> 1211 1209 <Text id="ew-25">Extracting document properties as metadata</Text> … … 1215 1213 </NumberedItem> 1216 1214 <NumberedItem> 1217 <Text id="ew-27">In the <AutoText key="glidict::GUI.Enrich"/> panel, look at the metadata that has been extracted for <Path>word05.doc</Path> and <Path>word06.doc</Path>. Now open the documents in Word and look at what properties they have set. (<Menu>File → Properties</Menu>). They have Title, Author, Subject, and Keywords properties. WordPlugcan be configured to look for these properties and extract them.</Text>1218 </NumberedItem> 1219 <NumberedItem> 1220 <Text id="ew-28">In the <AutoText key="glidict::GUI.Design"/> panel, under <AutoText key="glidict::CDM.GUI.Plugins"/>, select WordPlug and click <AutoText key="glidict::CDM.PlugInManager.Configure" type="button"/>. Switch on the configuration option <AutoText text="extracted_word_metadata_fields"/>. Set the value to </Text>1215 <Text id="ew-27">In the <AutoText key="glidict::GUI.Enrich"/> panel, look at the metadata that has been extracted for <Path>word05.doc</Path> and <Path>word06.doc</Path>. Now open the documents in Word and look at what properties have been set (<Menu>File → Properties</Menu>). They have Title, Author, Subject, and Keywords properties. <AutoText text="WordPlug"/> can be configured to look for these properties and extract them.</Text> 1216 </NumberedItem> 1217 <NumberedItem> 1218 <Text id="ew-28">In the <AutoText key="glidict::GUI.Design"/> panel, under <AutoText key="glidict::CDM.GUI.Plugins"/>, configure <AutoText text="WordPlug"/> once again. Switch on the configuration option <AutoText text="metadata_fields"/>. Set the value to </Text> 1221 1219 <Format> 1222 1220 Title,Author<Creator>,Subject,Keywords<Subject> … … 1225 1223 </NumberedItem> 1226 1224 <NumberedItem> 1227 <Text id="ew-30"> Buildthe collection.</Text>1228 </NumberedItem> 1229 <NumberedItem> 1230 <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 these extra metadata items. This metadata can now be used in display or browsing classifiers etc.</Text>1225 <Text id="ew-30">Make sure you have closed all the documents that were opened, then <b>rebuild</b> the collection.</Text> 1226 </NumberedItem> 1227 <NumberedItem> 1228 <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> 1231 1229 </NumberedItem> 1232 1230 </Content> … … 1321 1319 </NumberedItem> 1322 1320 <NumberedItem> 1323 <Text id="0361a">Next click <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/>. The new format statement will be displayed in the <AutoText key="glidict::CDM.FormatManager.Assigned_Formats"/> list. The first substitution alters the fragment of text that appears to the right of the thumbnail image, the second alters the item of metadata that follows it. The addition displays the description after the Title.</Text>1321 <Text id="0361a">Next click <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/>. The new format statement will be displayed in the list of assigned format statements. The first substitution alters the fragment of text that appears to the right of the thumbnail image, the second alters the item of metadata that follows it. The addition displays the description after the Title.</Text> 1324 1322 </NumberedItem> 1325 1323 <NumberedItem> … … 1417 1415 </NumberedItem> 1418 1416 <NumberedItem> 1419 <Text id="0417a">If your computer is behind a firewall or proxy server, you will need to edit the proxy settings in the Librarian Interface. Open the <AutoText key="glidict::Preferences.Connection"/> tab in <Menu><AutoText key="glidict::Menu.File"/> → <AutoText key="glidict::Menu.File_Options"/></Menu> and switch on the <AutoText key="glidict::Preferences.Connection.Use_Proxy"/> checkbox. Enter the proxy server address and port number in the <AutoText key="glidict::Preferences.Connection.Proxy_Host"/> and <AutoText key="glidict::Preferences.Connection.Proxy_Port"/> boxes. Click <AutoText key="General.OK" type="button"/>.</Text>1417 <Text id="0417a">If your computer is behind a firewall or proxy server, you will need to edit the proxy settings in the Librarian Interface. Open the <AutoText key="glidict::Preferences.Connection"/> tab in <Menu><AutoText key="glidict::Menu.File"/> → <AutoText key="glidict::Menu.File_Options"/></Menu> and switch on the <AutoText key="glidict::Preferences.Connection.Use_Proxy"/> checkbox. Enter the proxy server address and port number in the <AutoText key="glidict::Preferences.Connection.Proxy_Host"/> and <AutoText key="glidict::Preferences.Connection.Proxy_Port"/> boxes. Click <AutoText key="General.OK" type="button"/>.</Text> 1420 1418 </NumberedItem> 1421 1419 <NumberedItem> … … 1492 1490 <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> 1493 1491 <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"/>—which others that pertain to only one or some of the files are displayed in grey—e.g. any extracted metadata.</Text> 1494 <Text id="0440a">Metadata inherited from a parent folder is indicated by a folder icon to the left of the metadata name. Select on of the files in the <Path>relative</Path> folder to see this.</Text>1492 <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> 1495 1493 </NumberedItem> 1496 1494 <NumberedItem> … … 1647 1645 </NumberedItem> 1648 1646 <NumberedItem> 1649 <Text id="0489">To insert the <b>[dc.Subject]</b>, position the cursor at the appropriate point and either type it in, or use the <AutoText key="glidict::CDM.FormatManager.Variable"/> drop down menu—the one that says <AutoText text="[Text]"/>. Make it say <b>[dc.Subject]</b> and click <AutoText key="glidict::CDM.FormatManager.Insert" type="button"/> to insert this into the <AutoText key="glidict::CDM.FormatManager.Editor"/>. This menu shows many of the things that you can put in square brackets in the format statement.</Text>1647 <Text id="0489">To insert the <b>[dc.Subject]</b>, position the cursor at the appropriate point and either type it in, or use the <AutoText key="glidict::CDM.FormatManager.Variable"/> drop down menu—the one that says <AutoText text="[Text]"/>. Make it say <b>[dc.Subject]</b> and click <AutoText key="glidict::CDM.FormatManager.Insert" type="button"/> to insert this into the <AutoText key="glidict::CDM.FormatManager.Editor"/>. This menu shows many of the things that you can put in square brackets in the format statement.</Text> 1650 1648 </NumberedItem> 1651 1649 <NumberedItem> … … 1667 1665 </td> 1668 1666 </Format> 1669 <Text id="0496">and click <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/>. Again, you can insert the items in square brackets by selecting them from the <AutoText key="glidict::CDM.FormatManager.Variable"/> drop down box (don't forget to click <AutoText key="glidict::CDM.FormatManager.Insert" type="button"/>).</Text>1667 <Text id="0496">and click <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/>. Again, you can insert the items in square brackets by selecting them from the <AutoText key="glidict::CDM.FormatManager.Variable"/> drop down box (don't forget to click <AutoText key="glidict::CDM.FormatManager.Insert" type="button"/>).</Text> 1670 1668 <Comment> 1671 1669 <Text id="0497">The <AutoText text="If"/> statement tests the value of the variable <AutoText text="numleafdocs"/>. This variable is only set for internal nodes of the hierarchy, i.e. bookshelves, and gives the number of documents below that node. If it is set we take the first branch, otherwise we take the second. Commas are used to separate the branches. The curly brackets serve to indicate that the <AutoText text="If"/> is special—otherwise the word <AutoText text="If" type="quoted"/> itself would be output.</Text> … … 1735 1733 <Tutorial id="bibliography_collection"> 1736 1734 <Title> 1737 <Text id="0520"> A bibliographic collection</Text>1735 <Text id="0520">Bibliographic collection</Text> 1738 1736 </Title> 1739 1737 <SampleFiles folder="marc"/> … … 1754 1752 </NumberedItem> 1755 1753 <NumberedItem> 1756 <Text id="0524">Now select <AutoText key="glidict::CDM.GUI.Classifiers"/> within the <AutoText key="glidict::GUI.Design"/> panel and <b>remove</b> the default classifier for <b>Source</b> metadata. In this collection all records are from the same file, so <b>Source</b> metadata, which is set to the filename, is not particularly interesting.</Text> 1754 <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> 1755 <Text id="0524a">In the <AutoText key="glidict::CDM.GUI.Indexes"/> section, remove the <AutoText key="metadata::ex.Source"/> index.</Text> 1756 <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> 1757 1757 </NumberedItem> 1758 1758 <NumberedItem> … … 1760 1760 </NumberedItem> 1761 1761 <NumberedItem> 1762 <Text id="0526"> Add an <AutoText text="AZCompactList" /> classifier for the <b>Subject</b> metadata. Select this item from the relevant menu of the <AutoText key="glidict::CDM.GUI.Classifiers"/> section of the <AutoText key="glidict::GUI.Design"/> panel and click <AutoText key="glidict::CDM.ClassifierManager.Add" type="button"/>. In the popup window, select <AutoText key="metadata::ex.Subject"/> as the metadata item.</Text>1762 <Text id="0526">Back in the Librarian Interface, go to the <AutoText key="glidict::CDM.GUI.Classifiers"/> section of the <AutoText key="glidict::GUI.Design"/> panel. Select <AutoText text="AZCompactList" /> from the <AutoText key="glidict::CDM.ClassifierManager.Classifier"/> drop down menu, and click <AutoText key="glidict::CDM.ClassifierManager.Add" type="button"/>. In the popup window, select <AutoText key="metadata::ex.Subject"/> as the metadata item. Click <AutoText key="glidict::General.OK" type="button"/>.</Text> 1763 1763 <Comment> 1764 1764 <Text id="0527"><AutoText text="AZCompactList" /> is like <AutoText text="AZList"/>, except that terms that appear multiple times in the hierarchy are automatically grouped together and a new node, shown as a bookshelf icon, is formed.</Text> … … 1781 1781 </NumberedItem> 1782 1782 <NumberedItem> 1783 <Text id="0533a">Look at the search form in the collection. There are three fields that can be searched: <i>text</i>, <i>Title</i> and <i>Source</i>. Add some more fields to search on by going back to the Librarian Interface.</Text> 1784 </NumberedItem> 1785 <NumberedItem> 1786 <Text id="0533b">In the <AutoText key="glidict::GUI.Design"/> panel, go to the <AutoText key="glidict::CDM.GUI.Indexes"/> section. Remove the <i>source</i> index by selecting it in the <AutoText key="glidict::CDM.IndexManager.Indexes"/> list and clicking <AutoText key="glidict::CDM.IndexManager.Add_Index" type="button"/>.</Text> 1787 </NumberedItem> 1788 <NumberedItem> 1789 <Text id="0533c">Add an index on <b>subjects</b> by selecting <AutoText key="metadata::ex.Subject"/> from the <AutoText key="glidict::CDM.IndexManager.Source"/> list (and deselecting anything already selected), and giving it a name in the <AutoText key="glidict::CDM.IndexManager.Index_Name"/> box, e.g. "Subject". Click <AutoText key="glidict::CDM.IndexManager.Add_Index" type="button"/>. Add indexes on any other fields that look interesting.</Text> 1783 <Text id="0533a">Look at the search form in the collection. There are two fields that can be searched: <i>text</i> and <i>Title</i>. Add some more fields to search on by going back to the Librarian Interface.</Text> 1784 </NumberedItem> 1785 <NumberedItem> 1786 <Text id="0533c">In the <AutoText key="glidict::GUI.Design"/> panel, go to the <AutoText key="glidict::CDM.GUI.Indexes"/> section. Add an index on <b>subjects</b> by selecting <AutoText key="metadata::ex.Subject"/> from the <AutoText key="glidict::CDM.IndexManager.Source"/> list (and deselecting anything already selected), and giving it a name in the <AutoText key="glidict::CDM.IndexManager.Index_Name"/> box, e.g. "Subject". Click <AutoText key="glidict::CDM.IndexManager.Add_Index" type="button"/>.</Text> 1790 1787 </NumberedItem> 1791 1788 <NumberedItem> … … 1797 1794 <NumberedItem> 1798 1795 <Text id="0533-3">Go to the <AutoText key="glidict::GUI.Enrich"/> panel and try to see the metadata. It doesn't appear! This is because the metadata is associated with records inside the file, not the file itself.</Text> 1799 <Text id="0533-4">Metadata file types, such as MARC, CDS/ISIS, BibTex etc. can be imported into Greenstone but their metadata cannot be view d in the Librarian Interface. To edit any metadata you need to go back to the program that created the file.</Text>1796 <Text id="0533-4">Metadata file types, such as MARC, CDS/ISIS, BibTex etc. can be imported into Greenstone but their metadata cannot be viewed in the Librarian Interface. To edit any metadata you need to go back to the program that created the file.</Text> 1800 1797 <Text id="0533-5">Greenstone provides a new way of <i>exploding</i> a metadata database so that each record appears as an individual document, with viewable and editable metadata. This process is irreversible: once this step has been done, the database is deleted and can no longer be used in its original program.</Text> 1801 1798 </NumberedItem> … … 1814 1811 </NumberedItem> 1815 1812 <NumberedItem> 1816 <Text id="0533-11"><b>Rebuild</b> and <b>preview</b> the collection. You will notice that...</Text> 1817 <Text id="0533-12">The collection previously used extracted (ex.) metadata, but now it uses exploded (exp.) metadata. There is also no longer any text in the documents. Previously, MARCPlug stored the raw record as the "text" of each record. Now that the metadata is in the Librarian Interface, there is no longer the concept of raw record, and so there is no text. We need to modify the collection design to take note of these changes.</Text> 1818 </NumberedItem> 1819 <NumberedItem> 1820 <Text id="0533-13">In the <AutoText key="glidict::CDM.GUI.Indexes"/> section, change the Title index to use <AutoText key="metadata::exp.Title"/>. Select the Title index in the <AutoText key="glidict::CDM.IndexManager.Indexes"/> list. Deselect <AutoText key="metadata::ex.Title"/> in the <AutoText key="glidict::CDM.IndexManager.Source"/> list, and select <AutoText key="metadata::exp.Title"/>. Click <AutoText key="glidict::CDM.IndexManager.MGPP.Replace_Index" type="button"/>. Do the same thing for the Subject index.</Text> 1821 </NumberedItem> 1822 <NumberedItem> 1823 <Text id="0533-14">The text index is no longer any use, so remove that index by selecting it in the <AutoText key="glidict::CDM.IndexManager.Indexes"/> list and clicking <AutoText key="glidict::CDM.IndexManager.Remove_Index" type="button"/>. To enable combined searching across all indexes at once, tick the <AutoText key="glidict::CDM.IndexManager.Allfields_Index"/> checkbox, enter an appropriate name in the <AutoText key="glidict::CDM.IndexManager.Index_Name"/> field (e.g. "All Fields", then 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 becomes the default field for searching.</Text> 1813 <Text id="0533-11"><b>Rebuild</b> and <b>preview</b> the collection. You will notice that the <AutoText key="coredm::_Global:labelTitle_" type="italics"/> classifier displays the filename not the record title, the <AutoText key="coredm::_Global:labelSubject_" type="italics"/> classifier is empty, searching no longer returns any results, and the document display is useless.</Text> 1814 </NumberedItem> 1815 <Heading> 1816 <Text id="0533-11a">Reformatting the collection to use the exploded metadata</Text> 1817 </Heading> 1818 <Text id="0533-12">The collection previously used extracted (ex.) metadata, but now it uses exploded (exp.) metadata. The classifiers and search indexes were built on ex metadata, which is why they no longer work properly.</Text> 1819 <Text id="0533-12a">There is also no longer any text in the documents. Previously, MARCPlug stored the raw record as the "text" of each record. Now that the metadata is in the Librarian Interface, there is no longer the concept of raw record, and so there is no text.</Text> 1820 <Text id="0533-12b">We need to modify the collection design to take note of these changes.</Text> 1821 <NumberedItem> 1822 <Text id="0533-13">In the <AutoText key="glidict::CDM.GUI.Indexes"/> section, change the Title index to use <AutoText key="metadata::exp.Title"/>: select the Title index in the <AutoText key="glidict::CDM.IndexManager.Indexes"/> list. Deselect <AutoText key="metadata::ex.Title"/> in the <AutoText key="glidict::CDM.IndexManager.Source"/> list, and select <AutoText key="metadata::exp.Title"/>. Click <AutoText key="glidict::CDM.IndexManager.MGPP.Replace_Index" type="button"/>.</Text> 1823 </NumberedItem> 1824 <NumberedItem> 1825 <Text id="0533-13a">Remove the <AutoText key="metadata::ex.Subject"/> index by selecting it in the <AutoText key="glidict::CDM.IndexManager.Indexes"/> list and clicking <AutoText key="glidict::CDM.IndexManager.Remove_Index" type="button"/>. Add an index on <AutoText key="metadata::exp.Subject"/>: type "Subject" in the <AutoText key="glidict::CDM.IndexManager.Index_Name"/> field, select <AutoText key="metadata::exp.Subject"/> in the <AutoText key="glidict::CDM.IndexManager.Source"/> list (making sure nothing else is selected), and click <AutoText key="glidict::CDM.IndexManager.Add_Index" type="button"/>.</Text> 1826 </NumberedItem> 1827 <NumberedItem> 1828 <Text id="0533-14">The text index is no longer any use, so remove that index too.</Text> 1829 </NumberedItem> 1830 <NumberedItem> 1831 <Text id="0533-14a">To enable combined searching across all indexes at once, tick the <AutoText key="glidict::CDM.IndexManager.Allfields_Index"/> checkbox, enter an appropriate name in the <AutoText key="glidict::CDM.IndexManager.Index_Name"/> field (e.g. "All Fields", then 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> 1824 1832 </NumberedItem> 1825 1833 <NumberedItem> … … 1827 1835 </NumberedItem> 1828 1836 <NumberedItem> 1829 <Text id="0533-16">In the <AutoText key="glidict::CDM.GUI.Formats"/> section, select <AutoText text="VList"/> in the <AutoText key="glidict::CDM.FormatManager.Assigned_Formats"/> list. Change the <AutoText key="glidict::CDM.FormatManager.Editor"/>, replacing</Text> 1830 <Format> 1831 {Or}{[dls.Title],[dc.Title],[ex.Title],Untitled} 1832 </Format> 1833 <Text id="0533-17">with</Text> 1834 <Format> 1835 {Or}{[exp.Title],Untitled} 1836 </Format> 1837 <Text id="0533-18">Click <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/></Text> 1838 </NumberedItem> 1839 <NumberedItem> 1840 <Text id="0533-19">Clear the <AutoText text="DocumentHeading"/> format statement by selecting it in the <AutoText key="glidict::CDM.FormatManager.Assigned_Formats"/> list, deleting the contents in the <AutoText key="glidict::CDM.FormatManager.Editor"/>, and clicking <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/>.</Text> 1837 <Text id="0533-16">In the <AutoText key="glidict::CDM.GUI.Formats"/> section, select <AutoText text="VList"/> in the list of assigned format statements.</Text> 1838 <BulletList> 1839 <Bullet> 1840 <Text id="0533-16a">There is no dls or dc Title, so replace <Format>{Or}{[dls.Title],[dc.Title],[ex.Title],Untitled}</Format> with <Format>{Or}{[exp.Title],[ex.Title],Untitled}</Format>.</Text> 1841 </Bullet> 1842 <Bullet> 1843 <Text id="0533-16b">There are no source or thumb icons, so remove the second line: <Format><td valign="top">[ex.srclink]{Or}{[ex.thumbicon],[ex.srcicon]}[ex./srclink]</td></Format>.</Text> 1844 </Bullet> 1845 <Bullet> 1846 <Text id="0533-16c">The ex.Source metadata is set to the nul filename, so remove that from the display: remove <Format>{If}{[ex.Source],<br><i>([ex.Source])</i>}</Format></Text> 1847 </Bullet> 1848 </BulletList> 1849 <Text id="0533-16d">The resulting format statement looks like:</Text> 1850 <Format> 1851 <td valign="top">[link][icon][/link]</td><br/> 1852 <td valign="top">[highlight]<br/> 1853 {Or}{[exp.Title],[ex.Title],Untitled}<br/> 1854 [/highlight]</td> 1855 </Format> 1856 <Text id="0533-18">Click <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/>.</Text> 1857 </NumberedItem> 1858 <NumberedItem> 1859 <Text id="0533-19">Clear the <AutoText text="DocumentHeading"/> format statement by selecting it in the list of assigned format statements, deleting the contents in the <AutoText key="glidict::CDM.FormatManager.Editor"/>, and clicking <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/>. The record Title will be displayed as part of the <AutoText text="DocumentText"/> format, so we don't need it here. </Text> 1860 </NumberedItem> 1861 <NumberedItem> 1841 1862 <Text id="0533-20">Next, edit the <AutoText text="DocumentText"/> format statement. Delete the contents and replace it with</Text> 1842 1863 <Format> … … 1850 1871 </NumberedItem> 1851 1872 <NumberedItem> 1852 <Text id="0533-22">The <AutoText key="coredm::_document:textDETACH_" type="italics"/> and <AutoText key="coredm::_document:textNOHIGHLIGHT_" type="italics"/> buttons are not very useful for this collection, so lets get rid of them. Edit the <AutoText text="DocumentButtons"/> format statement, and make it empty.</Text>1853 </NumberedItem> 1854 <NumberedItem> 1855 <Text id="0533-23"><b>Rebuild</b> and <b>preview</b> the collection. </Text>1873 <Text id="0533-22">The <AutoText key="coredm::_document:textDETACH_" type="italics"/> and <AutoText key="coredm::_document:textNOHIGHLIGHT_" type="italics"/> buttons are not very useful for this collection, so lets get rid of them. Edit the <AutoText text="DocumentButtons"/> format statement, make it empty, and click <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/>.</Text> 1874 </NumberedItem> 1875 <NumberedItem> 1876 <Text id="0533-23"><b>Rebuild</b> and <b>preview</b> the collection. The classifiers should be back to normal, searching should now work, and there should be a nice record display.</Text> 1856 1877 </NumberedItem> 1857 1878 </Content> … … 1888 1909 </NumberedItem> 1889 1910 <NumberedItem> 1890 <Text id="is-11">In the <AutoText key="glidict::CDM.GUI.Formats"/> section, change the <AutoText text="VList"/> format statement to display <AutoText text="Photogra her"/> and <AutoText text="Notes"/> metadata. Change it to look like:</Text>1911 <Text id="is-11">In the <AutoText key="glidict::CDM.GUI.Formats"/> section, change the <AutoText text="VList"/> format statement to display <AutoText text="Photographer"/> and <AutoText text="Notes"/> metadata. Change it to look like:</Text> 1891 1912 <Format> 1892 1913 <td valign=top>[link][icon][/link]</td><br/> … … 1951 1972 <Format> 1952 1973 <style type="text/css"><br/> 1953 #body.bgimage \{ background-image: url("_httpimg_/chalk.gif"); \}<br/>1974 /*body.bgimage \{ background-image: url("_httpimg_/chalk.gif"); \}*/<br/> 1954 1975 body.bgimage \{ background-image: url("_httpimg_/chalk-blue.gif"); \}<br/> 1955 1976 </Format> 1956 <Text id="mf-13"> A hash (#) at the start of a line signals a comment, and Greenstone will ignore this line. We use this to "comment out" the original line and replace it with a modified line. This way it is easy to revert back to the original if necessary. Here we are changing the background image for the <Format>bgimage</Format> section of the <Format>body</Format> of the page to <Format>chalk-blue.gif</Format>.</Text>1977 <Text id="mf-13">/*...*/ around a line signals a comment, and this style element will be ignored. We use this to "comment out" the original line and replace it with a modified line. This way it is easy to revert back to the original if necessary. Here we are changing the background image for the <Format>bgimage</Format> section of the <Format>body</Format> of the page to <Format>chalk-blue.gif</Format>.</Text> 1957 1978 <Text id="mf-14">Save <Path>style.dm</Path> and close the file.</Text> 1958 1979 </NumberedItem> 1959 1980 <NumberedItem> 1960 <Text id="mf-15">Preview the home page in a web browser. (On Windows, restart the Greenstone library server.) The page header and background should now use the new graphics .</Text>1981 <Text id="mf-15">Preview the home page in a web browser. (On Windows, restart the Greenstone library server.) The page header and background should now use the new graphics, and be blue.</Text> 1961 1982 <Comment> 1962 1983 <Text id="mf-15a">The final part of this exercise looks at how we determined which images needed replacing, and which macro files should be edited.</Text> … … 1971 1992 <Text id="mf-19">Open <Path>Greenstone → macros → style.dm</Path> in a text editor, and find the <Format>_cssheader_</Format> macro that you modified previously. Change the <Format>div.navbar</Format> and <Format>div.divbar</Format> parts to use <Format>divb-blue.gif</Format> instead of <Format>bg_green.png</Format>:</Text> 1972 1993 <Format> 1973 #div.navbar \{ background-image: url("_httpimg_/bg_green.png"); \}<br/>1994 /*div.navbar \{ background-image: url("_httpimg_/bg_green.png"); \}*/<br/> 1974 1995 div.navbar \{ background-image: url("_httpimg_/divb-blue.gif"); \}<br/> 1975 #div.divbar \{ background-image: url("_httpimg_/bg_green.png"); \}<br/>1996 /*div.divbar \{ background-image: url("_httpimg_/bg_green.png"); \}*/<br/> 1976 1997 div.divbar \{ background-image: url("_httpimg_/divb-blue.gif"); \}<br/> 1977 1998 </Format> … … 1980 2001 <Text id="mf-20">The selected item on the navigation bar uses the same background, so change that too:</Text> 1981 2002 <Format> 1982 #a.navlink_sel \{ background-image: url("_httpimg_/bg_green.png"); \}<br/>2003 /*a.navlink_sel \{ background-image: url("_httpimg_/bg_green.png"); \}*/<br/> 1983 2004 a.navlink_sel \{ background-image: url("_httpimg_/divb-blue.gif"); \} 1984 2005 </Format> … … 1987 2008 <Text id="mf-21">Next, we get rid of the background green image on the page and collection titles. Comment out the <Format>p.bannertitle</Format> and <Format>p.collectiontitle</Format> parts:</Text> 1988 2009 <Format> 1989 #p.bannertitle \{background-image: url("_httpimg_/banner_bg.png"); \}<br/>1990 #p.collectiontitle \{background-image: url("_httpimg_/banner_bg.png"); \} 2010 /*p.bannertitle \{background-image: url("_httpimg_/banner_bg.png"); \}*/<br/> 2011 /*p.collectiontitle \{background-image: url("_httpimg_/banner_bg.png"); \}*/ 1991 2012 </Format> 1992 2013 </NumberedItem> … … 2119 2140 <br/> 2120 2141 _collectionspecificstyle_ {<br/> 2121 #clear the use of a background image<br/> 2142 <style type="text/css"><br/> 2143 /*clear the use of a background image */<br/> 2122 2144 body.bgimage \{ background-image: none; \}<br/> 2123 # set the background color to pink<br/>2145 /* set the background color to pink */<br/> 2124 2146 body \{ background: pink; \}<br/> 2125 #clear the background image for the navigation bar, and set its color to red<br/>2147 /* clear the background image for the navigation bar, and set its color to red */<br/> 2126 2148 div.navbar \{ background-image: none; background-color: red; \}<br/> 2127 #clear the background image for the divider bars, and set their color to red<br/>2149 /* clear the background image for the divider bars, and set their color to red */<br/> 2128 2150 div.divbar \{ background-image: none; background-color: red; \}<br/> 2151 </style><br/> 2129 2152 } 2130 2153 </Format> … … 2132 2155 </NumberedItem> 2133 2156 <Text id="mf-58">Any macros from the general macro files can be copied into a collection's <Path>extra.dm</Path> file and modified. Remember to include the package declaration to make sure that the macros get applied to the correct page(s).</Text> 2134 <Text id="mf-59">The style modifications made above were minor. The collection still uses the majority of the standard style file. The style declarations in the <Format>_collectionspecif cstyle_</Format> macro get appended to the default ones. To completely change the appearance of a collection, we can use a new style sheet altogether.</Text>2157 <Text id="mf-59">The style modifications made above were minor. The collection still uses the majority of the standard style file. The style declarations in the <Format>_collectionspecificstyle_</Format> macro get appended to the default ones. To completely change the appearance of a collection, we can use a new style sheet altogether.</Text> 2135 2158 <NumberedItem> 2136 2159 <Text id="mf-59a">Add the following to <Path>extra.dm</Path> after the last modifications:</Text> … … 2141 2164 } 2142 2165 </Format> 2143 <Text id="mf-60">Copy the file <Path>sample_files → custom → style-blue.css</Path> into the collection's <Path>images</Path> folder: <Path>Greenstone → collect → reports → images</Path> .</Text>2166 <Text id="mf-60">Copy the file <Path>sample_files → custom → style-blue.css</Path> into the collection's <Path>images</Path> folder: <Path>Greenstone → collect → reports → images</Path> (you may need to create this folder).</Text> 2144 2167 <Text id="mf-61">Preview the collection; it should look radically different.</Text> 2145 2168 </NumberedItem> … … 2161 2184 2162 2185 <Text id="mf-69">To search the macro files for <AutoText text="gsdlhead.gif" type="quoted"/> type</Text> 2163 <Command>find "gsdlhead.gif" "C:\Program Files\Greensto me\macros\*.dm"</Command>2164 <Text id="mf-70"><AutoText text="*.dm"/> means all files ending in <AutoText text=".dm"/>. A list of all macro files will be displayed, along with any matches. You wil see that <Path>home.dm</Path> and <Path>exported_home.dm</Path> both contain <AutoText text="gsdlhead.gif"/>. <Path>home.dm</Path> in the one you want to edit—<Path>exported_home.dm</Path> is used for the home page when you export a collection to CD-ROM.</Text>2186 <Command>find "gsdlhead.gif" "C:\Program Files\Greenstone\macros\*.dm"</Command> 2187 <Text id="mf-70"><AutoText text="*.dm"/> means all files ending in <AutoText text=".dm"/>. A list of all macro files will be displayed, along with any matches. You will see that <Path>home.dm</Path> and <Path>exported_home.dm</Path> both contain <AutoText text="gsdlhead.gif"/>. <Path>home.dm</Path> in the one you want to edit—<Path>exported_home.dm</Path> is used for the home page when you export a collection to CD-ROM.</Text> 2165 2188 2166 2189 <Text id="mf-71">Do the same thing for <AutoText text="chalk.gif" type="quoted"/>:</Text> … … 2199 2222 </NumberedItem> 2200 2223 <NumberedItem> 2201 <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="qu pted"/> 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—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>2224 <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—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> 2202 2225 </NumberedItem> 2203 2226 <NumberedItem> … … 2393 2416 <NumberedItem> 2394 2417 <Text id="0613">To complete the collection, use the browse button of <AutoText key="glidict::CDM.General.Icon_Collection"/> in the <AutoText key="glidict::CDM.GUI.General"/> section of the <AutoText key="glidict::GUI.Design"/> panel to select the following image:</Text> 2395 <Path>advbeat les_large → images → beatlesmm.png</Path>2418 <Path>advbeat_large → images → beatlesmm.png</Path> 2396 2419 <Text id="0616"><b>Build</b> the collection again and <b>preview</b> it.</Text> 2397 2420 </NumberedItem> … … 2592 2615 <Content> 2593 2616 <Comment> 2594 <Text id="0675">Here we build a small replica of Niupepa, the Maori Newspaper collection, using five newspapers taken from two newspaper series. It allows full text searching and browsing by title and date. When a newspaper is viewed, a preview image and its corresponding plain text are presented side by side, with a goto pagenavigation feature at the top of the page.</Text>2595 </Comment> 2596 <Comment> 2597 <Text id="0676">The collection involves a mixture of plug -ins, classifiers, and format statements. The bulk of the work is done by <AutoText text="PagedImgPlug"/>, a plug-in designed precisely for the kind of data we have in this example. For each document, an <AutoText text="item" type="quoted"/> file is prepared that specifies a list of image files that constitute the document, tagged with their page number and (optionally) accompanied by a text file containing the machine-readable version of the image, which is used for full text searching. Three newspapers in our collection (all from the series <AutoText text="Te Whetu o Te Tau" type="quoted"/>) have text representations, and two (from <AutoText text="Te Waka o Te Iwi" type="quoted"/>) have images only. Item files can also specify metadata. In our example the newspaper series is recorded as <AutoText key="metadata::ex.Title"/> and its date of publication as <AutoText key="metadata::ex.Date"/>. This metadata is extracted as part of the building process.</Text>2617 <Text id="0675">Here we build a small replica of Niupepa, the Maori Newspaper collection, using five newspapers taken from two newspaper series. It allows full text searching and browsing by title and date. When a newspaper is viewed, a preview image and its corresponding plain text are presented side by side, with a "go to page" navigation feature at the top of the page.</Text> 2618 </Comment> 2619 <Comment> 2620 <Text id="0676">The collection involves a mixture of plugins, classifiers, and format statements. The bulk of the work is done by <AutoText text="PagedImgPlug"/>, a plugin designed precisely for the kind of data we have in this example. For each document, an <AutoText text="item" type="quoted"/> file is prepared that specifies a list of image files that constitute the document, tagged with their page number and (optionally) accompanied by a text file containing the machine-readable version of the image, which is used for full text searching. Three newspapers in our collection (all from the series <AutoText text="Te Whetu o Te Tau" type="quoted"/>) have text representations, and two (from <AutoText text="Te Waka o Te Iwi" type="quoted"/>) have images only. Item files can also specify metadata. In our example the newspaper series is recorded as <AutoText key="metadata::ex.Title"/> and its date of publication as <AutoText key="metadata::ex.Date"/>. Issue <AutoText key="metadata::ex.Volume"/> and <AutoText key="metadata::ex.Number"/> metadata is also recorded, where appropriate. This metadata is extracted as part of the building process.</Text> 2598 2621 </Comment> 2599 2622 <NumberedItem> … … 2601 2624 </NumberedItem> 2602 2625 <NumberedItem> 2603 <Text id="0679">In the <AutoText key="glidict::GUI.Gather"/> panel, open the <Path>sample_files → niupepa → sample_items</Path> folder and drag the two subfolders into your collection on the right-hand side. A popup window asks whether you want to add <AutoText text="PagedImgPlug"/> to the collection to process this file. Click <AutoText key="glidict::CDM.PlugInManager.QuickAdd" type="button"/>, because this plugin will be needed to process the item files.</Text>2626 <Text id="0679">In the <AutoText key="glidict::GUI.Gather"/> panel, open the <Path>sample_files → niupepa → sample_items</Path> folder and drag the two subfolders into your collection on the right-hand side. A popup window asks whether you want to add <AutoText text="PagedImgPlug"/> to the collection: click <AutoText key="glidict::CDM.PlugInManager.QuickAdd" type="button"/>, because this plugin will be needed to process the item files.</Text> 2604 2627 </NumberedItem> 2605 2628 <NumberedItem> … … 2607 2630 </NumberedItem> 2608 2631 <NumberedItem> 2609 <Text id="0678">Open up the configuration window for <AutoText text="PagedImgPlug"/> by double-clicking on the plugin. Switch on its <AutoText text="screenview"/> configuration option by checking the box. The source images we use were scanned at high resolution and are large files for a browser to download. The <AutoText text="screenview"/> option generates smaller screen-resolution images of each page when the collection is built. </Text>2632 <Text id="0678">Open up the configuration window for <AutoText text="PagedImgPlug"/> by double-clicking on the plugin. Switch on its <AutoText text="screenview"/> configuration option by checking the box. The source images we use were scanned at high resolution and are large files for a browser to download. The <AutoText text="screenview"/> option generates smaller screen-resolution images of each page when the collection is built. Click <AutoText key="glidict::General.OK" type="button"/>.</Text> 2610 2633 </NumberedItem> 2611 2634 <NumberedItem> … … 2619 2642 </Heading> 2620 2643 <Comment> 2621 <Text id="0684">Under <AutoText key="coredm::_Global:labelTitle_"/> documents from the same series are repeated without any distinguishing features such as date . It would be better to group them by series title and display dates within each group. This can be accomplished using an <AutoText text="AZCompactList"/> classifier rather than <AutoText text="AZList"/>, and tuning the <AutoText text="VList"/>format statement.</Text>2644 <Text id="0684">Under <AutoText key="coredm::_Global:labelTitle_"/> documents from the same series are repeated without any distinguishing features such as date, volume or number. It would be better to group them by series title and display other information within each group. This can be accomplished using an <AutoText text="AZCompactList"/> classifier rather than <AutoText text="AZList"/>, and tuning the classifier's format statement.</Text> 2622 2645 </Comment> 2623 2646 <NumberedItem> … … 2628 2651 </NumberedItem> 2629 2652 <NumberedItem> 2630 <Text id="0687"><b>Modify</b> the format statement for <AutoText text="VList" /> (under <AutoText key="glidict::CDM.GUI.Formats"/>). Find the part of the default statement that says</Text> 2631 <Format>{If}{[ex.Source],<br><i>([ex.Source])</i>}</Format> 2632 <Text id="0689">and change it to</Text> 2633 <Format>{If}{[ex.Date],: [ex.Date]}</Format> 2634 <Text id="0690">This has the effect of displaying the extracted date information, if present.</Text> 2635 </NumberedItem> 2636 <NumberedItem> 2637 <Text id="0691">At the end of this format statement, where is says:</Text> 2638 <Format></td></Format> 2639 <Text id="0692">append</Text> 2640 <Format>{If}{[numleafdocs],<td>([numleafdocs])</td>}</Format> 2641 <Text id="0692a">and click <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/>.</Text> 2642 <Comment> 2643 <Text id="0693">As a consequence of using the <AutoText text="AZCompactList"/> classifier, bookshelf icons appear when titles are browsed. This revised format statement has the effect of specifying in brackets how many items are contained within a bookshelf. It works by exploiting the fact that only bookshelf icons define <Format>[numleafdocs]</Format> metadata.</Text> 2644 </Comment> 2645 </NumberedItem> 2646 <NumberedItem> 2647 <Text id="0690a"><b>Build</b> and <b>preview</b> the collection.</Text> 2653 <Text id="0687">In the <AutoText key="glidict::CDM.GUI.Formats"/> section, select the <AutoText key="metadata::ex.Title"/> classifier in the <AutoText key="glidict::CDM.FormatManager.Feature"/> list, and <AutoText text="VList"/> in the <AutoText key="glidict::CDM.FormatManager.Part"/> list. Delete the contents of the <AutoText key="glidict::CDM.FormatManager.Editor"/> box, and add the following:</Text> 2654 <Format> 2655 <td valign="top">[link][icon][/link]</td><br/> 2656 <td valign="top"><br/> 2657 {If}{[numleafdocs],[ex.Title] ([numleafdocs]),<br/> 2658 {If}{[ex.Volume],Volume [ex.Volume] }<br/> 2659 {If}{[ex.Number],Number [ex.Number] }<br/> 2660 {If}{[ex.Date], [ex.Date]}}<br/> 2661 </td> 2662 </Format> 2663 <Text id="0687a">Click <AutoText key="glidict::CDM.FormatManager.Add" type="button"/>.</Text> 2664 <Text id="0687b">(This format statement can be copied and pasted from the file <Path>sample_files → niupepa → formats → titles_tweak.txt</Path>)</Text> 2665 </NumberedItem> 2666 <NumberedItem> 2667 <Text id="0690a"><b>Build</b> the collection, and <b>preview</b> the new <AutoText key="coredm::_Global:labelTitle_" type="italics"/> list.</Text> 2668 <Text id="0687c">As a consequence of using the <AutoText text="AZCompactList"/> classifier, bookshelf icons appear when titles are browsed. This revised format statement has the effect of specifying in brackets how many items are contained within a bookshelf. It works by exploiting the fact that only bookshelf icons define <Format>[numleafdocs]</Format> metadata. For document nodes, Title is not displayed. instead, Volume, Number and Date information are displayed if present.</Text> 2648 2669 </NumberedItem> 2649 2670 <Heading> … … 2656 2677 <Text id="0696">In the <AutoText key="glidict::CDM.GUI.Formats"/> section of the <AutoText key="glidict::GUI.Design"/> panel, select the <AutoText text="DocumentText"/> format statement. The default format string displays the document's plain text, which, if there is none, is set to <AutoText key="perlmodules::BasPlug.dummy_text" type="quoted"/>. Change this to:</Text> 2657 2678 <Format> 2658 <center><table width=_pagewidth_><tr><br/>2679 <center><table><tr><br/> 2659 2680 <td valign=top>[srclink][screenicon][/srclink]</td><br/> 2660 <td >[Text]</td><br/>2681 <td valign=top>[Text]</td><br/> 2661 2682 </tr></table></center> 2662 2683 </Format> 2663 2684 <Text id="0696a">and click <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/>.</Text> 2664 <Text id="0697">(This format statement can be copied and pasted from the file <Path>sample_files → niupepa → doc_tweak.txt</Path>)</Text>2685 <Text id="0697">(This format statement can be copied and pasted from the file <Path>sample_files → niupepa → formats → doc_tweak.txt</Path>)</Text> 2665 2686 <Comment> 2666 2687 <Text id="0698">Including <Format>[screenicon]</Format> has the effect of embedding the screen-sized image generated by switching the <AutoText text="screenview"/> option on in <AutoText text="PagedImgPlug"/>. It is hyperlinked to the original image by the construct <Format>[srclink]...[/srclink]</Format>.</Text> 2667 2688 </Comment> 2668 <Text id="0698a">This modification will display screenview image, but does nothing about the dummy text <AutoText key="perlmodules::BasPlug.dummy_text" type=" plain"/>, which will still be displayed. To get rid of this, edit the <AutoText text="DocumentText"/> format statement again and replace</Text>2669 <Format> 2670 <td >[Text]</td>2689 <Text id="0698a">This modification will display screenview image, but does nothing about the dummy text <AutoText key="perlmodules::BasPlug.dummy_text" type="quoted"/>, which will still be displayed. To get rid of this, edit the <AutoText text="DocumentText"/> format statement again and replace</Text> 2690 <Format> 2691 <td valign=top>[Text]</td> 2671 2692 </Format> 2672 2693 <Text id="0698b">with</Text> 2673 2694 <Format> 2674 {If}{[Text] ne "<AutoText key="perlmodules::BasPlug.dummy_text" type="plain"/> ",<td >[Text]</td>}2675 </Format> 2676 <Text id="0698 c">Preview the collection and view one of the <AutoText text="Te Waka o Te Iwi"/> documents. The line <AutoText key="perlmodules::BasPlug.dummy_text" type="quoted"/> should now be gone. (Note that it important to get the text exactly right for this to work, including the space after the ".".)</Text>2677 </NumberedItem> 2678 <NumberedItem> 2679 <Text id="069 9"><b>Preview</b> the revised collection.</Text>2695 {If}{[Text] ne "<AutoText key="perlmodules::BasPlug.dummy_text" type="plain"/> ",<td valign=top>[Text]</td>} 2696 </Format> 2697 <Text id="0698d">and click <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/>.</Text> 2698 </NumberedItem> 2699 <NumberedItem> 2700 <Text id="0698c"><b>Preview</b> the collection and view one of the <AutoText text="Te Waka o Te Iwi"/> documents. The line <AutoText key="perlmodules::BasPlug.dummy_text" type="quoted"/> should now be gone. (Note that it important to get the text exactly right for this to work, including the space after the ".".)</Text> 2680 2701 </NumberedItem> 2681 2702 <Heading> … … 2686 2707 </NumberedItem> 2687 2708 <NumberedItem> 2688 <Text id="0690d">Go to the <AutoText key="glidict::CDM.GUI.Indexes"/> section of the <AutoText key="glidict::GUI.Design"/> panel. Remove the <AutoText key="metadata::ex.Source"/> index. Select the <AutoText text=" text"/> index in the <AutoText key="glidict::CDM.IndexManager.Indexes"/> box, and change the <AutoText key="glidict::CDM.IndexManager.Index_Name"/> to "whole newspapers". Click <AutoText key="glidict::CDM.IndexManager.MGPP.Replace_Index" type="button"/>. Create a new index: set the <AutoText key="glidict::CDM.IndexManager.Index_Name"/> to "newspaper pages", keep <AutoText text="text"/> selected in <AutoText key="glidict::CDM.IndexManager.Source"/>, and change <AutoText key="glidict::CDM.IndexManager.Level"/> to <AutoText text="section"/>. Click <AutoText key="glidict::CDM.IndexManager.Add_Index" type="button"/>. Click <AutoText key="glidict::CDM.IndexManager.Set_Default" type="button"/> on the right hand side to make the "newspaper pages" index the default.</Text>2709 <Text id="0690d">Go to the <AutoText key="glidict::CDM.GUI.Indexes"/> section of the <AutoText key="glidict::GUI.Design"/> panel. Remove the <AutoText key="metadata::ex.Source"/> index. Select the <AutoText text="document:text"/> index in the <AutoText key="glidict::CDM.IndexManager.Indexes"/> box, and change the <AutoText key="glidict::CDM.IndexManager.Index_Name"/> to "whole newspapers". Click <AutoText key="glidict::CDM.IndexManager.MGPP.Replace_Index" type="button"/>. Create a new index: set the <AutoText key="glidict::CDM.IndexManager.Index_Name"/> to "newspaper pages", keep <AutoText text="text"/> selected in <AutoText key="glidict::CDM.IndexManager.Source"/>, and change <AutoText key="glidict::CDM.IndexManager.Level"/> to <AutoText text="section"/>. Click <AutoText key="glidict::CDM.IndexManager.Add_Index" type="button"/>. Click <AutoText key="glidict::CDM.IndexManager.Set_Default" type="button"/> on the right hand side to make the "newspaper pages" index the default.</Text> 2689 2710 </NumberedItem> 2690 2711 <NumberedItem> … … 2692 2713 </NumberedItem> 2693 2714 <NumberedItem> 2694 <Text id="0690f">You will notice that when searching for individual pages, the newspaper image is displayed in the search results. As these images are very large, this is not very useful. To remove this, edit the format statement for <AutoText text="VList"/> (under <AutoText key="glidict::CDM.GUI.Formats"/>), and remove the second line:</Text>2715 <Text id="0690f">You will notice that when searching for individual pages, the newspaper image is displayed in the search results. As these images are very large, this is not very useful. Go to <AutoText key="glidict::CDM.GUI.Formats"/> in the Librarian Interface and select the <AutoText text="VList"/> format statement from the list of assigned format statements. Remove the second line from the <AutoText key="glidict::CDM.FormatManager.Editor"/>:</Text> 2695 2716 <Format> 2696 2717 <td valign="top">[ex.srclink]{Or}{[ex.thumbicon],[ex.srcicon]}[ex./srclink]</td> 2697 2718 </Format> 2698 <Text id="0690g">Preview the collection—the search results should be back to normal. </Text> 2699 </NumberedItem> 2700 <NumberedItem> 2701 <Text id="0690h">Now you will notice that page level search results on show the Title of the page (the page number), and not the Title of the newspaper. We'll modify the format statement to show the paper title as well as the page number. In the <AutoText key="glidict::CDM.GUI.Formats"/> section of the <AutoText key="glidict::GUI.Design"/> panel, select <AutoText text="Search"/> in <AutoText key="glidict::CDM.FormatManager.Feature"/>, and <AutoText text="VList"/> in <AutoText key="glidict::CDM.FormatManager.Part"/>.</Text> 2719 <Text id="0690f-1">While we are here, lets remove the filename from the display. Remove the following from the last line:</Text> 2720 <Format> 2721 {If}{[ex.Source],<br><i>([ex.Source])</i>} 2722 </Format> 2723 <Text id="0690f-2">Click <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/>.</Text> 2724 <Text id="0690g"><b>Preview</b> the collection—the search results should be back to normal. </Text> 2725 </NumberedItem> 2726 <NumberedItem> 2727 <Text id="0690h">Now you will notice that page level search results only show the Title of the page (the page number), and not the Title of the newspaper. We'll modify the format statement to show the newspaper title as well as the page number. Also, lets add in Volume and Number information too. </Text> 2728 <Text id="0690h-1">In the <AutoText key="glidict::CDM.GUI.Formats"/> section of the <AutoText key="glidict::GUI.Design"/> panel, select <AutoText text="Search"/> in <AutoText key="glidict::CDM.FormatManager.Feature"/>, and <AutoText text="VList"/> in <AutoText key="glidict::CDM.FormatManager.Part"/>. 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> 2702 2729 <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> 2703 2730 <Text id="0690j">Set the format statement to the following:</Text> 2704 2731 <Format> 2705 <td valign=top>[link][icon][/link]</td><br/> 2706 <td valign=top><br/> 2707 {If}{[parent:ex.Title],[parent:ex.Title]: }[ex.Title] <br><br/> 2708 <i>({Or}{[parent:ex.Date],[ex.Date]})</i></td> 2709 </Format> 2710 <Text id="0690k">(The format statement can be copied and pasted from the file <Path>sample_files → niupepa → search_tweak.txt</Path>.)</Text> 2711 <Text id="0690l">The first line links to the document. The third line displays the parent Title if there is one, then the Title of the current page or document. The fourth line displays either the parent Date (in the case of pages) or the Date (in the case of documents), in italics (<Format><i>..</i></Format>).</Text> 2732 <td valign="top">[link][icon][/link]</td><br/> 2733 <td valign="top"><br/> 2734 {If}{[parent:ex.Title],[parent:ex.Title]<br/> 2735 {If}{[parent:ex.Volume],Volume [parent:ex.Volume] }<br/> 2736 {If}{[parent:ex.Number],Number [parent:ex.Number]}: Page [ex.Title],<br/> 2737 [ex.Title] {If}{[ex.Volume], Volume [ex.Volume] }<br/> 2738 {If}{[ex.Number], Number [ex.Number] }}<br/> 2739 <br/><i>({Or}{[parent:ex.Date],[ex.Date]})</i></td><br/> 2740 </td> 2741 </Format> 2742 <Text id="1690j-1">and click <AutoText key="glidict::CDM.FormatManager.Add" type="button"/>.</Text> 2743 <Text id="0690k">(The format statement can be copied and pasted from the file <Path>sample_files → niupepa → formats → search_tweak.txt</Path>.)</Text> 2744 <Text id="0690l"><b>Preview</b> the search results. Items display newspaper title, Volume, Number and Date if available, and pages also display the page number.</Text> 2712 2745 </NumberedItem> 2713 2746 <Comment> … … 2725 2758 <Content> 2726 2759 <Comment> 2727 <Text id="sc2">In this exercise we build upon the collection created in <TutorialRef id="scanned_image_collection"/>. We add a new newspaper by creating an item file for it, add a new newspaper using the extended XML item file format, and modify the formatting.</Text>2760 <Text id="sc2">In this exercise we build upon the collection created in the <TutorialRef id="scanned_image_collection"/> exercise. We add a new newspaper by creating an item file for it, add a new newspaper using the extended XML item file format, and modify the formatting.</Text> 2728 2761 </Comment> 2729 2762 <Heading> … … 2734 2767 </Comment> 2735 2768 <NumberedItem> 2736 <Text id="sc5">In the Librarian Interface, open up the Paged Image collection that was created in exercise <TutorialRef id="scanned_image_collection"/> if it is not already open (<Menu><AutoText key="glidict::Menu.File"/> → <AutoText key="glidict::Menu.File_ New"/></Menu>).</Text>2769 <Text id="sc5">In the Librarian Interface, open up the Paged Image collection that was created in exercise <TutorialRef id="scanned_image_collection"/> if it is not already open (<Menu><AutoText key="glidict::Menu.File"/> → <AutoText key="glidict::Menu.File_Open"/></Menu>).</Text> 2737 2770 </NumberedItem> 2738 2771 <NumberedItem> 2739 2772 <Text id="sc6">In the <AutoText key="glidict::GUI.Gather"/> panel, add the folder <Path>sample_files → niupepa → new_papers → 12</Path> to your collection. </Text> 2740 <Text id="sc7">A series of popups ask you about adding plugins to the collection to process the text and image files. Remember that <AutoText text="ImagePlug"/> and <AutoText text="TextPlug"/> were removed from the collection as we wanted these files to be processed by <AutoText text="PagedImgPlug"/>. Click <AutoText key="glidict::CDM.PlugInManager.Ignore" type="button"/> for each popup.</Text> 2741 <Text id="sc8">You may notice that for text files, the Librarian Interface suggests <AutoText text="ProCitePlug"/> as the plugin to add. If you open up the <AutoText key="glidict::CDM.PlugInManager.PlugIn"/> drop down list, you can see that <AutoText text="TEXTPlug"/> is also suggested. Both these plugins process files with extension <AutoText text=".txt" type="italics"/>.</Text> 2742 </NumberedItem> 2743 <NumberedItem> 2744 <Text id="sc9">Inside the <AutoText text="12 "/>folder you can see that there are 4 images and 4 text files.</Text> 2773 <Text id="sc9">Inside the <AutoText text="12 "/> folder you can see that there are 4 images and 4 text files.</Text> 2745 2774 </NumberedItem> 2746 2775 <NumberedItem> … … 2760 2789 <Text id="sc13">For each page, add a line in the file in the following format:</Text> 2761 2790 <Format> 2762 <Text id="sc14">pagenum:imagefile:textfile ::</Text>2791 <Text id="sc14">pagenum:imagefile:textfile</Text> 2763 2792 </Format> 2764 2793 <Text id="sc15">For example, the first page entry would look like</Text> 2765 2794 <Format> 2766 1:images/12_3_6_1.gif:text/12_3_6_1.txt ::2767 </Format> 2768 <Text id="sc16">Note that if there is no text file, you can leave that space blank. </Text>2769 </NumberedItem> 2770 <NumberedItem> 2771 <Text id="sc17">Save the file using <b>Filename</b> <AutoText text="12_3_6.item" type="italics"/>, and <b>Save as type</b> <i>All files</i>. (Don't save as type <AutoText text=".txt" type="italics"/> as this will save the file as <AutoText text="12_3_6.item.txt"/>.)Back in the <AutoText key="glidict::GUI.Gather"/> panel of the Librarian Interface, locate the new file in the <b>Workspace</b> tree, and drag it into the collection, adding it to the <AutoText text="12"/> folder.</Text>2795 1:images/12_3_6_1.gif:text/12_3_6_1.txt 2796 </Format> 2797 <Text id="sc16">Note that if there is no text file, you can leave that space blank. You need to add a line for each page in the document. Make sure you increment the page number for each line.</Text> 2798 </NumberedItem> 2799 <NumberedItem> 2800 <Text id="sc17">Save the file using <b>Filename</b> <AutoText text="12_3_6.item" type="italics"/>, and save as a plain text document. (If you are using Windows, make sure the file isn't saved as <AutoText text="12_3_6.item.txt" type="italics"/>.) Back in the <AutoText key="glidict::GUI.Gather"/> panel of the Librarian Interface, locate the new file in the <b>Workspace</b> tree, and drag it into the collection, adding it to the <AutoText text="12"/> folder.</Text> 2772 2801 </NumberedItem> 2773 2802 <NumberedItem> … … 2783 2812 </NumberedItem> 2784 2813 <NumberedItem> 2785 <Text id="sc23">Open up the file <Path>xml → 23 → 23__ 1.item</Path> and have a look at the XML. This is <AutoText text="Number"/> <AutoText text="1" type="italics"/> of <AutoText text="Series"/><AutoText text="Matariki 1881" type="italics"/>. The contents of this document have been grouped into two sections: <AutoText text="Supplementary Material"/>, which contains an <AutoText text="Abstract"/>, and <AutoText text="Newspaper Pages"/>, which contains the page images (and OCR text). </Text>2786 </NumberedItem> 2787 <NumberedItem> 2788 <Text id="sc24"> Build and preview the collection. The xml style items have been included, but the displayis not very nice.</Text>2814 <Text id="sc23">Open up the file <Path>xml → 23 → 23__2.item</Path> and have a look at the XML. This is <AutoText text="Number"/> <AutoText text="2" type="italics"/> of the newspaper titled <AutoText text="Matariki 1881" type="italics"/>. The contents of this document have been grouped into two sections: <AutoText text="Supplementary Material"/>, which contains an <AutoText text="Abstract"/>, and <AutoText text="Newspaper Pages"/>, which contains the page images (and OCR text). </Text> 2815 </NumberedItem> 2816 <NumberedItem> 2817 <Text id="sc24"><b>Build</b> and <b>preview</b> the collection. The xml style items have been included, but the document display for these items is not very nice.</Text> 2789 2818 </NumberedItem> 2790 2819 <Heading> … … 2792 2821 </Heading> 2793 2822 <NumberedItem> 2794 <Text id="sc25">Paged documents can be presented with a hierarchical table of contents, or with next and previous page arrows, and a goto page box (like we have done so far). The display type is specified by the <AutoText text="documenttype (hierarchy|paged)"/> option to <AutoText text="PagedImgPlug"/>. The next and previous arrows suit the linear sequence documents, while the table of contents suits the hierarchically organised document. </Text> 2795 <Text id="sc25a">Ordinarily, a Greenstone collection would have one plugin per document type, and all documents of that type get the same processing. In this case, we want to treat the XML-based item files differently from the text-based item files. We can achieve this by adding two PagedImgPlug plugins to the collection, and configuring them differently.</Text> 2796 </NumberedItem> 2797 <NumberedItem> 2798 <Text id="sc26">Close the collection in the Librarian Interface. It will not let you add two of the same plugin (apart from <AutoText text="UnknownPlug"/>), so the second <AutoText text="PagedImgPlug"/> must be added to the collect.cfg file manually.</Text> 2799 </NumberedItem> 2800 <NumberedItem> 2801 <Text id="sc27">Open the file <Path>greenstone → collect → pagedimg → etc → collect.cfg</Path> in a text editor. Copy the <AutoText text="plugin PagedImgPlug"/> line and paste it above the existing one. Edit the first one so that the two plugins look like:</Text> 2802 <Format> 2803 plugin PagedImgPlug -screenview -minimumsize 100 -documenttype hierarchy -process_exp xml.*.item$<br/> 2804 plugin PagedImgPlug -screenview -minimumsize 100 -documenttype paged 2805 </Format> 2806 <Text id="sc28">The XML based newpapers have been grouped into a folder called <Path>xml</Path>. This enables us to process these files differently, by utilising the <AutoText text="process_exp"/> option which all plugins support. The first <AutoText text="PagedImgPlug"/> in the list looks for item files underneath the <Path>xml</Path> folder. These documents will be processed as hierarchical documents. Item files that don't match the process expression (i.e. aren't underneath the <Path>xml</Path> folder) will be passed onto the second <AutoText text="PagedImgPlug"/>, and these are treated as paged documents.</Text> 2823 <Text id="sc25">Paged documents can be presented with a hierarchical table of contents, or with next and previous page arrows, and a "go to page" box (like we have done so far). The display type is specified by the <AutoText text="documenttype (hierarchy|paged)"/> option to <AutoText text="PagedImgPlug"/>. The next and previous arrows suit the linear sequence documents, while the table of contents suits the hierarchically organised document. </Text> 2824 <Text id="sc25a">Ordinarily, a Greenstone collection would have one plugin per document type, and all documents of that type get the same processing. In this case, we want to treat the XML-based item files differently from the text-based item files. We can achieve this by adding two <AutoText text="PagedImgPlug"/> plugins to the collection, and configuring them differently.</Text> 2825 </NumberedItem> 2826 <NumberedItem> 2827 <Text id="sc26"><b>Close</b> the collection in the Librarian Interface (<Menu><AutoText key="glidict::Menu.File"/> → <AutoText key="glidict::Menu.File_Close"/></Menu>). It will not let you add two of the same plugin (apart from <AutoText text="UnknownPlug"/>), so the second <AutoText text="PagedImgPlug"/> must be added to the collect.cfg file manually.</Text> 2828 </NumberedItem> 2829 <NumberedItem> 2830 <Text id="sc27">Open the file <Path>greenstone → collect → pagedima → etc → collect.cfg</Path> in a text editor. Copy the <AutoText text="plugin PagedImgPlug"/> line and paste it above the existing one. Edit the two <AutoText text="plugin PagedImgPlug"/> lines so that they look like:</Text> 2831 <Format> 2832 plugin PagedImgPlug -screenview -documenttype hierarchy -process_exp xml.*.item$<br/> 2833 plugin PagedImgPlug -screenview -documenttype paged 2834 </Format> 2835 <Text id="sc27a">Save and close the file.</Text> 2836 <Text id="sc28">The XML based newspapers have been grouped into a folder called <Path>xml</Path>. This enables us to process these files differently, by utilizing the <AutoText text="process_exp"/> option which all plugins support. The first <AutoText text="PagedImgPlug"/> in the list looks for item files underneath the <Path>xml</Path> folder. These documents will be processed as 'hierarchical' documents. Item files that don't match the process expression (i.e. aren't underneath the <Path>xml</Path> folder) will be passed onto the second <AutoText text="PagedImgPlug"/>, and these are treated as 'paged' documents.</Text> 2837 <Text id="sc28a">Open the collection in the Librarian Interface (<Menu><AutoText key="glidict::Menu.File"/> → <AutoText key="glidict::Menu.File_Open"/></Menu>). Check the <AutoText key="glidict::CDM.GUI.Plugins"/> section of the <AutoText key="glidict::GUI.Design"/> panel to make sure that the two <AutoText text="PagedImgPlug"/> plugins appear.</Text> 2807 2838 <Text id="sc29"><b>Rebuild</b> and <b>preview</b> the collection. Compare the document display for a paged document e.g. <AutoText text="Te Waka o Te Iwi, Vol. 1, No. 1"/> with a hierarchical document, e.g. <AutoText text="Matariki 1881, No. 1"/>.</Text> 2808 2839 </NumberedItem> … … 2812 2843 <Text id="sc31">We can modify the document display to switch between the text version and the screenview and full size versions. We do this using a combination of format statements and macro files.</Text> 2813 2844 <NumberedItem> 2814 <Text id="sc32">First, copy the new macro file into the collection. C opy <Path>sample_files → niupepa → extra.dm</Path> into the <Path>Greenstone → collect → pagedimg → macros</Path>folder.</Text>2845 <Text id="sc32">First, copy the new macro file into the collection. Create a new folder <Path>Greenstone → collect → pagedimg → macros</Path>. Copy <Path>sample_files → niupepa → macros → extra.dm</Path> into this folder.</Text> 2815 2846 </NumberedItem> 2816 2847 <NumberedItem> … … 2818 2849 </NumberedItem> 2819 2850 <NumberedItem> 2820 <Text id="sc33b">Select <AutoText text="AllowExtendedOptions"/> in the <AutoText key="glidict::CDM.FormatManager.Feature"/> list, and tick <AutoText key="glidict::CDM.FormatManager.Enabled"/>. This allows us to use some extended formatting options.</Text>2851 <Text id="sc33b">Select <AutoText text="AllowExtendedOptions"/> in the <AutoText key="glidict::CDM.FormatManager.Feature"/> list, and tick <AutoText key="glidict::CDM.FormatManager.Enabled"/>. Click <AutoText key="glidict::CDM.FormatManager.Add" type="button"/>. This gives us more control over the layout of the page—in this case, we want to replace the standard <AutoText key="coredm::_document:textDETACH_" type="italics"/> and <AutoText key="coredm::_document:textNOHIGHLIGHT_" type="italics"/> buttons with buttons that switch between images and text.</Text> 2821 2852 </NumberedItem> 2822 2853 <NumberedItem> 2823 2854 <Text id="sc33c">Select the <AutoText text="DocumentHeading"/> format item and set it to the following:</Text> 2824 2855 <Format> 2825 <center><table width=_pagewidth_><br/> 2826 <tr valign=top><td>{Or}{[parent(Top):Series],[Series]}</td></tr><br/> 2827 <tr valign=top><td><table><tr><td><br/> 2828 [DocumentButtonDetach][DocumentButtonHighlight]<br/> 2829 {If}{_cgiargp_ eq 'fullsize',<br/> 2830 {If}{[screenicon],_document:viewpreview_}<br/> 2831 {If}{[Text] ne \'This document has no text. \',_document:viewtext_},<br/> 2832 {If}{_cgiargp_ eq 'preview',{If}{[srcicon],_document:viewfullsize_}<br/> 2833 {If}{[Text] ne \'This document has no text. \',_document:viewtext_},<br/> 2856 <div class="heading_title">{Or}{[parent(Top):ex.Title],[ex.Title]}</div><br/> 2857 <div class="buttons" id="toc_buttons"><br/> 2834 2858 {If}{[srcicon],_document:viewfullsize_}<br/> 2835 2859 {If}{[screenicon],_document:viewpreview_}<br/> 2836 }}<br/> 2837 </td></tr></table></td><br/> 2838 <td>[DocTOC]</td></tr></table></center> 2839 </Format> 2840 <Text id="sc33d">This format statement can be copied from <Path>sample_files → niupepa → adv_doc_heading.txt</Path>. It is quite complicated. </Text> 2841 <Text id="sc33e"><Format>{Or}{[parent(Top):Series],[Series]}</Format> outputs the Series metadata. This is only stored at the top level document level, so if we are at a subsection, we need to get it from the top level (<Format>[parent(Top):Series]</Format>).</Text> 2842 <Text id="sc33f"><Format>[DocumentButtonDetach][DocumentButtonHighlight]</Format> outputs the <AutoText key="coredm::_document:textDETACH_" type="italics"/> and <AutoText key="coredm::_document:textNOHIGHLIGHT_" type="italics"/> buttons.</Text> 2843 <Text id="sc33g"><Format>_document:viewpreview_, _document:viewfullsize_, _document:viewtext_</Format> are macros defined in <Path>extra.dm</Path> which output buttons for preview, fullsize and text versions, respectively.</Text> 2844 <Text id="sc33h">The set of nested <Format>{If}</Format> statements determine which buttons are output, depending on which option is currently selected and which options are available. For example, if the user is currently viewing the full sized image, then the fullsize image button is suppressed, and preview and text buttons are only displayed if that information is available for the current page.</Text> 2860 {If}{[Text] ne 'This document has no text. ',_document:viewtext_}<br/> 2861 </div><br/> 2862 <div class="toc">[DocTOC]</div><br/> 2863 </Format> 2864 <Text id="sc33c-1">Click <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/>.</Text> 2865 <Text id="sc33d">This format statement can be copied from <Path>sample_files → niupepa → formats → adv_doc_heading.txt</Path>.</Text> 2866 <Text id="sc33e"><Format>{Or}{[parent(Top):ex.Title],[ex.Title]}</Format> outputs the newspaper Title metadata. This is only stored at the top level of the document, so if we are at a subsection, we need to get it from the top (<Format>[parent(Top):ex.Title]</Format>). Note that we can't just use <Format>[parent:ex.Title]</Format> as this retrieves the Title from the immediate parent node, which may not be the top node of the document.</Text> 2867 <Text id="sc33g"><Format>_document:viewpreview_, _document:viewfullsize_, _document:viewtext_</Format> are macros defined in <Path>extra.dm</Path> which output buttons for preview, fullsize and text versions, respectively. We choose which buttons to display based on what metadata and text the document has.</Text> 2868 <Text id="sc33h"><Format>[DocTOC]</Format> is the document table of contents or "go to page" navigation element. Since we are using extended options, we need to explicitly specify this for it to appear in the page.</Text> 2869 <Text id="sc33i">The different pieces are surrounded by <Format><div></Format> elements, so that the appropriate styling information can be used.</Text> 2845 2870 </NumberedItem> 2846 2871 <NumberedItem> 2847 2872 <Text id="sc34a">Select the <AutoText text="DocumentText"/> format statement and set it to:</Text> 2848 2873 <Format> 2849 <center><table width=_pagewidth_><tr><td><br/>2850 2874 {If}{_cgiargp_ eq 'fullsize',[srcicon],<br/> 2851 {If}{_cgiargp_ eq 'preview',[screenicon],{If}{[Text] ne \'This document has no text. \',[Text]}}}<br/> 2852 </td></tr></table></center><br/> 2853 </Format> 2854 <Text id="sc34b">This format statement can be copied from <Path>sample_files → niupepa → adv_doc_text.txt</Path>. It changes the display based on the <AutoText text="p" type="quoted"/> argument (<Format>_cgiargp_</Format>). This is not used normally for document display, so we can use it here to switch between full size image (<Format>[srcicon]</Format>), preview size image (<Format>[screenicon]</Format>) and text (<Format>[Text]</Format>) versions of each page.</Text> 2855 </NumberedItem> 2856 <NumberedItem> 2857 <Text id="sc35">Preview the collection. View some of the documents—once you have reaced a newspaper page, you should get fullsize, preview and text options.</Text> 2875 {If}{_cgiargp_ eq 'preview',[screenicon],<br/> 2876 {If}{[Text] ne \'This document has no text. \',[Text],[screenicon]}}} 2877 </Format> 2878 <Text id="sc34a-1">Remember to click <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/>.</Text> 2879 <Text id="sc34b">This format statement can be copied from <Path>sample_files → niupepa → formats → adv_doc_text.txt</Path>. It changes the display based on the <AutoText text="p" type="quoted"/> argument (<Format>_cgiargp_</Format>). This is not used normally for document display, so we can use it here to switch between full size image (<Format>[srcicon]</Format>), preview size image (<Format>[screenicon]</Format>) and text (<Format>[Text]</Format>) versions of each page.</Text> 2880 </NumberedItem> 2881 <NumberedItem> 2882 <Text id="sc35"><b>Preview</b> the collection. View some of the documents—once you have reached a newspaper page, you should get fullsize, preview and text options.</Text> 2858 2883 </NumberedItem> 2859 2884 </Content> … … 2932 2957 <Text id="0722">Next, select <AutoText text="DocumentHeading"/> from the <AutoText key="glidict::CDM.FormatManager.Feature"/> pull-down list and change its format statement to: </Text> 2933 2958 <Format><h3>[Subject]</h3></Format> 2934 <Comment> 2935 <Text id="0723">The document heading appears above the <AutoText key="coredm::_document:textDETACH_" type="italics"/> and <AutoText key="coredm::_document:textNOHIGHLIGHT_" type="italics"/> buttons when you get to a document in the collection. By default <AutoText text="DocumentHeading"/> displays the document's <AutoText key="metadata::ex.Title"/> metadata. In this particular set of OAI exported records, titles are filenames of JPEG images, and the filenames are particularly uninformative (for example, 01dla14). You can see them in the <AutoText key="glidict::GUI.Enrich"/> panel if you select an image in <Path>sample_small → oai → JCDLPICS → srcdocs</Path> and check its <AutoText key="metadata::ex.Filename"/> and <AutoText key="metadata::ex.Title"/> metadata. The above format statement displays <AutoText key="metadata::ex.Subject"/> metadata instead.</Text> 2959 <Text id="0722a">Click <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/>.</Text> 2960 <Comment> 2961 <Text id="0723">The document heading appears above the <AutoText key="coredm::_document:textDETACH_" type="italics"/> and <AutoText key="coredm::_document:textNOHIGHLIGHT_" type="italics"/> buttons when you get to a document in the collection. By default <AutoText text="DocumentHeading"/> displays the document's <AutoText key="metadata::ex.Title"/> metadata. In this particular set of OAI exported records, titles are filenames of JPEG images, and the filenames are particularly uninformative (for example, 01dla14). You can see them in the <AutoText key="glidict::GUI.Enrich"/> panel if you select an image in <Path>sample_small → oai → JCDLPICS → srcdocs</Path> and check its <AutoText key="metadata::ex.Source"/> and <AutoText key="metadata::ex.Title"/> metadata. The above format statement displays <AutoText key="metadata::ex.Subject"/> metadata instead.</Text> 2936 2962 </Comment> 2937 2963 </NumberedItem> … … 3037 3063 </NumberedItem> 3038 3064 <NumberedItem> 3039 <Text id="0759">In your Windows file browser, locate the <Path>archives</Path> folder for the Tudor collection. For each document in the collection, Greenstone has generated two files: <Path>docmets.xml</Path>, the core METS description, and <Path>doctxt.xml</Path>, a supporting file. (Note: unless you are connected to the Internet you will be unable to view <Path>doctxt.xml</Path> in your web browser, because it refers to a remote resource.) Depending on the source documents there may be additional files, such as the images used within a web page. One of MET 'smany features is the ability to reference information in external XML files. Greenstone uses this to tie the content of the document, which is stored in the external XML file <Path>doctxt.xml</Path>, to its hierarchical structure, which is described in the core METS file <Path>docmets.xml</Path>.</Text>3065 <Text id="0759">In your Windows file browser, locate the <Path>archives</Path> folder for the Tudor collection. For each document in the collection, Greenstone has generated two files: <Path>docmets.xml</Path>, the core METS description, and <Path>doctxt.xml</Path>, a supporting file. (Note: unless you are connected to the Internet you will be unable to view <Path>doctxt.xml</Path> in your web browser, because it refers to a remote resource.) Depending on the source documents there may be additional files, such as the images used within a web page. One of METS' many features is the ability to reference information in external XML files. Greenstone uses this to tie the content of the document, which is stored in the external XML file <Path>doctxt.xml</Path>, to its hierarchical structure, which is described in the core METS file <Path>docmets.xml</Path>.</Text> 3040 3066 </NumberedItem> 3041 3067 </Content> … … 3055 3081 </NumberedItem> 3056 3082 <NumberedItem> 3057 <Text id="0764">Switch to the <AutoText key="glidict::GUI.Design"/> panel and select the <AutoText key="glidict::CDM.GUI.Plugins"/> section on the left-hand side. <b>Remove</b> <AutoText text=" TEXTPlug" />, <AutoText text="HTMLPlug" /> and <AutoText text="EMAILPlug" />. Strictly speaking we do not need to remove these, however it reduces clutter.</Text>3083 <Text id="0764">Switch to the <AutoText key="glidict::GUI.Design"/> panel and select the <AutoText key="glidict::CDM.GUI.Plugins"/> section on the left-hand side. <b>Remove</b> <AutoText text="ZIPPlug" />, <AutoText text="TEXTPlug" />, <AutoText text="HTMLPlug" />, <AutoText text="EMAILPlug" />, <AutoText text="PSPlug" />, <AutoText text="ImagePlug" />, <AutoText text="ISISPlug" /> and <AutoText text="NULPlug" />. Strictly speaking we do not need to remove these, however it reduces clutter.</Text> 3058 3084 </NumberedItem> 3059 3085 <NumberedItem> … … 3061 3087 </NumberedItem> 3062 3088 <NumberedItem> 3063 <Text id="0766">Using the up and down arrows, <b>Move</b> the position of <AutoText text="DSpacePlug" /> to above <AutoText text="GAPlug" /> and below <AutoText text="ZIPPlug" />.</Text> 3064 </NumberedItem> 3065 <NumberedItem> 3066 <Text id="0767">Now add <AutoText text="MP3Plug" />, with the default configuration options. Its position in the plug-in pipeline need not be changed.</Text> 3067 </NumberedItem> 3068 <NumberedItem> 3069 <Text id="0768">In the <AutoText key="glidict::GUI.Gather"/> panel, locate the folder <Path>sample_files → dspace → exported_docs</Path>. It contains five example items exported from a DSpace institutional repository. Copy them into your collection by dragging them over to the right-hand side of the panel.</Text> 3089 <Text id="0766">Using the up and down arrows, <b>Move</b> the position of <AutoText text="DSpacePlug" /> to the top of the list (above <AutoText text="GAPlug" />).</Text> 3090 </NumberedItem> 3091 <NumberedItem> 3092 <Text id="0768">In the <AutoText key="glidict::GUI.Gather"/> panel, locate the folder <Path>sample_files → dspace</Path>. It contains five example items exported from a DSpace institutional repository. Copy them into your collection by dragging them over to the right-hand side of the panel.</Text> 3070 3093 </NumberedItem> 3071 3094 <NumberedItem> … … 3082 3105 </Comment> 3083 3106 <NumberedItem> 3084 <Text id="0773">Select <AutoText text="DSpacePlug" /> and click <AutoText key="glidict::CDM.PlugInManager.Configure" type="button"/>. Switch on its configuration option <AutoText text="first_inorder_ext"/>. Set its value to <AutoText text="pdf,doc, mp3" type="quoted"/> in the popup window that appears and press <AutoText key="glidict::General.OK" type="button"/>.</Text>3107 <Text id="0773">Select <AutoText text="DSpacePlug" /> and click <AutoText key="glidict::CDM.PlugInManager.Configure" type="button"/>. Switch on its configuration option <AutoText text="first_inorder_ext"/>. Set its value to <AutoText text="pdf,doc,rtf" type="quoted"/> in the popup window that appears and press <AutoText key="glidict::General.OK" type="button"/>.</Text> 3085 3108 </NumberedItem> 3086 3109 <NumberedItem> … … 3103 3126 </NumberedItem> 3104 3127 <NumberedItem> 3105 <Text id="0780">Now select the <AutoText key="glidict::CDM.GUI.Formats"/> section of the <AutoText key="glidict::GUI.Design"/> panel and replace the <AutoText text="VList" /> format statement with this:</Text> 3106 <Format> 3107 <td valign=top>[link][icon][/link]</td><br/> 3108 <td valign=top><br/> 3109 [srclink][srcicon][/srclink]<br/> 3110 </td><br/> 3111 <td valign=top><br/> 3112 [highlight]{Or}{[dc.Title],[ex.Title],Untitled}[/highlight]<br/> 3113 {If}{[ex.Source],<br><i>([ex.Source])</i>}<br/> 3114 {If}{[equivlink],<br>Also available as:[equivlink]}<br/> 3115 </td> 3116 </Format> 3117 <Text id="0781">You will find this text in the file <Path>format_tweak.txt</Path> in the <Path>dspace</Path> folder of <Path>sample_files</Path>, and you can copy and paste this. Remember to press <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/> when finished.</Text> 3128 <Text id="0780">Now select the <AutoText key="glidict::CDM.GUI.Formats"/> section of the <AutoText key="glidict::GUI.Design"/> panel, and select the <AutoText text="VList" /> format statement in the list of assigned format statements. Add the following text before the final <Format></td></Format>:</Text> 3129 <Format> 3130 {If}{[ex.equivlink],<br>Also available as:[ex.equivlink]} 3131 </Format> 3132 <Text id="0781">Click <AutoText key="glidict::CDM.FormatManager.Replace" type="button"/>.</Text> 3118 3133 </NumberedItem> 3119 3134 <NumberedItem> … … 3124 3139 </NumberedItem> 3125 3140 <NumberedItem> 3126 <Text id="0783">Leave <AutoText text="VList" /> as the <AutoText key="glidict::CDM.FormatManager.Part"/> and edit the text in the <AutoText key="glidict::CDM.FormatManager.Editor"/> box so that it looks like:</Text> 3127 <Format> 3128 <td valign=top>[link][icon][/link]</td><br/> 3129 <td valign=top><br/> 3130 [srclink][srcicon][/srclink]<br/> 3131 </td><br/> 3132 <td valign=top><br/> 3133 [highlight]<br/> 3134 {If}{[numleafdocs],([numleafdocs]) [ex.Title],[dc.Title]}<br/> 3135 [/highlight]<br/> 3136 {If}{[ex.Source],<br><i>([ex.Source])</i>}<br/> 3137 {If}{[equivlink],<br>Also available as:[equivlink]}<br/> 3138 </td> 3141 <Text id="0783">Leave <AutoText text="VList" /> as the <AutoText key="glidict::CDM.FormatManager.Part"/> and edit the text in the <AutoText key="glidict::CDM.FormatManager.Editor"/> box. Replace</Text> 3142 <Format> 3143 {Or}{[dls.Title],[dc.Title],[ex.Title],Untitled} 3144 </Format> 3145 <Text id="0783a">with</Text> 3146 <Format> 3147 {If}{[numleafdocs],([numleafdocs]) [ex.Title],[dc.Title]} 3139 3148 </Format> 3140 3149 <Text id="0784">and click <AutoText key="glidict::CDM.FormatManager.Add" type="button"/>. This will display the number of documents for each bookshelf in the authors classifier.</Text> 3141 <Text id="0785">You will find this text in the file <Path>format_contributor.txt</Path> in the <Path>dspace</Path> folder of <Path>sample_files</Path>, and you can copy and paste this.</Text>3142 3150 </NumberedItem> 3143 3151 <NumberedItem>
Note:
See TracChangeset
for help on using the changeset viewer.
