Changeset 11496
- Timestamp:
- 2006-03-27T15:29:05+12:00 (18 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/gsdl-documentation/tutorials/xml-source/tutorial_en.xml
r11469 r11496 2 2 <!DOCTYPE TutorialList [ 3 3 <!ENTITY nbsp " "> 4 <!ENTITY rarr "→"> 5 <!ENTITY mdash "—"> 4 6 ]> 5 7 <TutorialList> … … 26 28 </Heading> 27 29 <NumberedItem> 28 <Text id="0085">On inserting the <b>UNAIDS CD-ROM</b>, for many computers installation will begin automatically. If not, "auto-run" --a configurable setting under Windows--is disabled on your computer and you need to double-click <i>setup.exe</i> on the CD-ROM.</Text>30 <Text id="0085">On inserting the <b>UNAIDS CD-ROM</b>, for many computers installation will begin automatically. If not, "auto-run"—a configurable setting under Windows—is disabled on your computer and you need to double-click <i>setup.exe</i> on the CD-ROM.</Text> 29 31 <Menu> 30 <Text id="0086">My Computer --> UNAIDS20 --> setup.exe</Text>32 <Text id="0086">My Computer → UNAIDS20 → setup.exe</Text> 31 33 </Menu> 32 34 </NumberedItem> … … 49 51 <Text id="0094">Click <b><OK</b>> to confirm completion of UNAIDS collection (twice).</Text> 50 52 <Comment> 51 <Text id="0095">InstallShield quits --the UNAIDS Library is installed.</Text>53 <Text id="0095">InstallShield quits—the UNAIDS Library is installed.</Text> 52 54 </Comment> 53 55 </NumberedItem> … … 61 63 <Text id="0099">Launch the prebuilt library by clicking:</Text> 62 64 <Menu> 63 <Text id="0100">Start --> All Programs --> UNAIDS Library 2.0 [CD-ROM] --> UNAIDS Library 2.0 (Standard Version).</Text>65 <Text id="0100">Start → All Programs → UNAIDS Library 2.0 [CD-ROM] → UNAIDS Library 2.0 (Standard Version).</Text> 64 66 </Menu> 65 67 <Comment> … … 95 97 <Text id="0114">You can return to the currently selected page of document titles by clicking the <b>book icon </b>next to the title of the book at the top of the table of contents (this signifies closing the book). You also get to the document titles using <b>titles a-z</b> in the navigation bar, in this case to the titles beginning with A-D.</Text> 96 98 <Comment> 97 <Text id="0115">If the table of contents is open at the top level --showing all the chapters--then clicking <b>Expand Document or Chapter</b> expands the full document. For long documents, which take some time to load in, Greenstone seeks confirmation for this action: clicking 'continue' loads the full document.</Text>99 <Text id="0115">If the table of contents is open at the top level—showing all the chapters—then clicking <b>Expand Document or Chapter</b> expands the full document. For long documents, which take some time to load in, Greenstone seeks confirmation for this action: clicking 'continue' loads the full document.</Text> 98 100 </Comment> 99 101 </NumberedItem> … … 282 284 </NumberedItem> 283 285 <NumberedItem> 284 <Text id="0169">Now explore the collection by navigating freely around it. Click liberally: all images that appear on the screen are clickable. If you hold the mouse stationary over an image, most browsers will soon pop up a brief "mouse-over" message that tells you what will happen if you click. Experiment! Choose common words like "the" or "and" to search for --that should evoke some response, and nothing will break. (Note: unlike many search systems, Greenstone indexes all words, including these ones.)</Text>286 <Text id="0169">Now explore the collection by navigating freely around it. Click liberally: all images that appear on the screen are clickable. If you hold the mouse stationary over an image, most browsers will soon pop up a brief "mouse-over" message that tells you what will happen if you click. Experiment! Choose common words like "the" or "and" to search for—that should evoke some response, and nothing will break. (Note: unlike many search systems, Greenstone indexes all words, including these ones.)</Text> 285 287 </NumberedItem> 286 288 <Heading> … … 377 379 <Comment> 378 380 <Text id="0199">In addition to all the above software, these CD-ROMs contain the tutorial exercises and a set of <b>sample files</b> to be used for these exercises.</Text> 379 <Text id="0199a">CD-ROM Swith Greenstone version 2.62 or earlier also include the <b>Greenstone Language Pack</b>, which gives reader's interfaces in many languages (currently about 40). This has its own installer which you have to invoke separately, after you have installed Greenstone.</Text>380 <Text id="0199b">CD-ROM S with version 2.70 or later now come with reader's interfaces in all available languages. Textual images have been removed from the interface; they are now done using CSS. The Greenstone Language Pack is no longer needed. Instead, these CD-ROMS come with the <b>Classic Interface Pack</b>, which contains the old text images for use with a backwards compatiliblity macro file.</Text>381 <Text id="0199a">CD-ROMs with Greenstone version 2.62 or earlier also include the <b>Greenstone Language Pack</b>, which gives reader's interfaces in many languages (currently about 40). This has its own installer which you have to invoke separately, after you have installed Greenstone.</Text> 382 <Text id="0199b">CD-ROMs with version 2.70 or later now come with reader's interfaces in all available languages. Textual images have been removed from the interface; they are now done using CSS (Cascading Style Sheets). The Greenstone Language Pack is no longer needed. Instead, these CD-ROMs come with the <b>Classic Interface Pack</b>, which contains the old text images for use with a backwards compatibility macro file.</Text> 381 383 </Comment> 382 384 <Comment> … … 389 391 <Text id="0203">You need <b>Java</b> to run Greenstone. You might already have it; otherwise download it from <Link>http://java.sun.com</Link>. To work with image collections, you need <b>ImageMagick</b> (from <Link>http://www.imagemagick.org</Link>). </Text> 390 392 </NumberedItem> 391 <Text id="0204">Most Greenstone CD-ROMs start the installation process as soon as they are inserted into the drive, assuming that the AutoPlay feature is enabled on your computer. If installation does not begin by itself, locate the file <i>setup.exe</i> and double click it to start the installation process. (On the IMARK CD-ROM this file resides in the folder < i>software_tools</i>--><i>Greenstone</i>). If you download Greenstone over the web, what you get is the installer--just double-click it.</Text>393 <Text id="0204">Most Greenstone CD-ROMs start the installation process as soon as they are inserted into the drive, assuming that the AutoPlay feature is enabled on your computer. If installation does not begin by itself, locate the file <i>setup.exe</i> and double click it to start the installation process. (On the IMARK CD-ROM this file resides in the folder <Path>software_tools → Greenstone</Path>). If you download Greenstone over the web, what you get is the installer—just double-click it.</Text> 392 394 <Text id="0206"><b>If Greenstone has been installed on your computer before, you should completely remove the old version before installing a new one</b>. (However, you need not remove any pre-packaged collections that you may have installed.) To do this, see <TutorialRef id="update_greenstone_installation"/>.</Text> 393 395 <Text id="0207">Here is what you need to do to install Greenstone. Older versions of the installer follow much the same sequence but use slightly different wording.</Text> … … 553 555 <Text id="0252b">Greenstone now comes with all languages enabled. 554 556 The generated HTML uses text + CSS rather than images for navigation bar, 555 home, help, preferences buttons etc. The classic interface pack is not needed if you want to use Greenstone in another language. It is only needed if you want to revert back to the old style HTML with text images. This may be useful if you have customized your greenstone, or if you require compatibility with Netscape 4.</Text>557 home, help, preferences buttons etc. The classic interface pack is not needed if you want to use Greenstone in another language. It is only needed if you want to revert back to the old style HTML with text images. This may be useful if you have customized your Greenstone, or if you require compatibility with Netscape 4.</Text> 556 558 </Comment> 557 559 <NumberedItem> … … 582 584 <Text id="0255">Start the Greenstone Librarian Interface:</Text> 583 585 <Menu> 584 <Text id="0255a">Start -->All Programs-->Greenstone Digital Library Software v2.70-->Greenstone Librarian Interface</Text>586 <Text id="0255a">Start → All Programs → Greenstone Digital Library Software v2.70 → Greenstone Librarian Interface</Text> 585 587 </Menu> 586 588 <Comment> … … 590 592 <NumberedItem> 591 593 <Text id="0257">Start a new collection within the Librarian Interface:</Text> 592 <Text id="0258"><Menu>File -->New</Menu></Text>594 <Text id="0258"><Menu>File → New</Menu></Text> 593 595 </NumberedItem> 594 596 <NumberedItem> 595 597 <Text id="0260">You will create a collection based on a few HTML web pages that describe some Hobbits in <i>Lord of the Rings</i>.</Text> 596 <Text id="0261">A window pops up. Fill it out with appropriate values --for example,</Text>598 <Text id="0261">A window pops up. Fill it out with appropriate values—for example,</Text> 597 599 <Indent> 598 600 <Text id="0261a">Collection Title: About Hobbits<br/></Text> … … 638 640 </NumberedItem> 639 641 <NumberedItem> 640 <Text id="0274">Close the collection by clicking <Menu>File -->Close</Menu>. This automatically saves the collection to disk.</Text>642 <Text id="0274">Close the collection by clicking <Menu>File → Close</Menu>. This automatically saves the collection to disk.</Text> 641 643 </NumberedItem> 642 644 <Heading> … … 644 646 </Heading> 645 647 <NumberedItem> 646 <Text id="0278">To set up a shortcut to the source files, in the <b>Gather</b> panel navigate to the folder in your local file space that contains the files you want to use --in our case, the <i>sample_files</i> folder. Select this folder and then right-click it. Follow the instructions to set up a shortcut. Close all the folders in the file tree and you will see the shortcut to your source files in the left-hand pane of the <b>Gather</b> panel.</Text>648 <Text id="0278">To set up a shortcut to the source files, in the <b>Gather</b> panel navigate to the folder in your local file space that contains the files you want to use—in our case, the <i>sample_files</i> folder. Select this folder and then right-click it. Follow the instructions to set up a shortcut. Close all the folders in the file tree and you will see the shortcut to your source files in the left-hand pane of the <b>Gather</b> panel.</Text> 647 649 </NumberedItem> 648 650 </Content> … … 662 664 </NumberedItem> 663 665 <NumberedItem> 664 <Text id="0282">Copy the 12 files from <Path>sample_files -->Word_and_PDF-->Documents</Path> into the collection. You can select multiple files by clicking on the first one and shift-clicking on the last one, and drag them all across together. (This is the normal technique of multiple selection.)</Text>666 <Text id="0282">Copy the 12 files from <Path>sample_files → Word_and_PDF → Documents</Path> into the collection. You can select multiple files by clicking on the first one and shift-clicking on the last one, and drag them all across together. (This is the normal technique of multiple selection.)</Text> 665 667 </NumberedItem> 666 668 <NumberedItem> … … 668 670 </NumberedItem> 669 671 <NumberedItem> 670 <Text id="0288">Again, this collection contains no manually assigned metadata. All the information that appears --title and filename--is extracted automatically from the documents themselves. Because of this the quality of some of the title metadata is suspect.</Text>672 <Text id="0288">Again, this collection contains no manually assigned metadata. All the information that appears—title and filename—is extracted automatically from the documents themselves. Because of this the quality of some of the title metadata is suspect.</Text> 671 673 </NumberedItem> 672 674 <NumberedItem> … … 698 700 </NumberedItem> 699 701 <NumberedItem> 700 <Text id="0297">Click on the <<b>Browse </b>> button associated with <b>URL to about page icon</b>, and browse to the image <Path>sample_files-->Word_and_PDF-->wrdpdf.gif</Path> on your computer. When you select this image, Greenstone automatically generates an appropriate URL for the image. <b>Preview</b> the collection.</Text>702 <Text id="0297">Click on the <<b>Browse...</b>> button associated with <b>URL to about page icon</b>, and browse to the image <Path>sample_files → Word_and_PDF → wrdpdf.gif</Path> on your computer. When you select this image, Greenstone automatically generates an appropriate URL for the image. <b>Preview</b> the collection.</Text> 701 703 </NumberedItem> 702 704 <NumberedItem> … … 775 777 <Text id="0324">Build a fresh Greenstone collection from the two files in <i>sample_files\difficult_documents.</i> Use the default collection configuration: that is, simply gather the files into a new collection, and build it.</Text> 776 778 <Comment> 777 <Text id="0325">These files are called No extractable text.pdf and Weird characters.pdf --their names hint at the problems they will cause!</Text>779 <Text id="0325">These files are called No extractable text.pdf and Weird characters.pdf—their names hint at the problems they will cause!</Text> 778 780 </Comment> 779 781 </NumberedItem> … … 824 826 <Content> 825 827 <NumberedItem> 826 <Text id="0338">Start a new collection (<Menu>File -->New</Menu>) called <b>backdrop</b>. Fill out the fields with appropriate information. For <b>Base this collection on</b>, select the item <b>Simple image collection (image-e)</b> from the pull-down menu.</Text>828 <Text id="0338">Start a new collection (<Menu>File → New</Menu>) called <b>backdrop</b>. Fill out the fields with appropriate information. For <b>Base this collection on</b>, select the item <b>Simple image collection (image-e)</b> from the pull-down menu.</Text> 827 829 <Comment> 828 830 <Text id="0340">Greenstone does not ask you to choose a metadata set because the new collection inherits whatever is used by the base collection.</Text> … … 899 901 </Comment> 900 902 <Comment> 901 <Text id="0364">For some design parameters the collection must be rebuilt before the effect of changes can be seen. However, changes to format statements take place immediately and you can see the result straightaway by clicking <<b>Preview Collection</b>> in the <b>Create</b> panel.</Text>903 <Text id="0364">For some design parameters the collection must be rebuilt before the effect of changes can be seen. However, changes to format statements take place immediately and you can see the result straightaway by clicking <b>reload</b> (or <b>refresh</b>) in the web browser.</Text> 902 904 </Comment> 903 905 <Heading> … … 973 975 <Tutorial id="large_html_collection"> 974 976 <Title> 975 <Text id="0387">A large collection of HTML files --Tudor</Text>977 <Text id="0387">A large collection of HTML files—Tudor</Text> 976 978 </Title> 977 979 <SampleFiles folder="tudor"/> … … 1000 1002 </Comment> 1001 1003 <NumberedItem> 1002 <Text id="0395">Switch to the <b>Design</b> panel and select the <b>Document Plugins</b> section. Beside <b>plugin HTMLPlug</b> you will see <i>-smart_block</i>. This is the option that attempts to identify images in the HTML pages and block them from inclusion --in this case, it's not smart enough! Select the <b>plugin HTMLPlug</b> line and click <<b>Configure Plugin...></b>. A popup window appears. Scroll down the page to locate the <b>smart_block</b> option and switch it off. Click <<b>OK></b>.</Text>1004 <Text id="0395">Switch to the <b>Design</b> panel and select the <b>Document Plugins</b> section. Beside <b>plugin HTMLPlug</b> you will see <i>-smart_block</i>. This is the option that attempts to identify images in the HTML pages and block them from inclusion—in this case, it's not smart enough! Select the <b>plugin HTMLPlug</b> line and click <<b>Configure Plugin...></b>. A popup window appears. Scroll down the page to locate the <b>smart_block</b> option and switch it off. Click <<b>OK></b>.</Text> 1003 1005 </NumberedItem> 1004 1006 <NumberedItem> … … 1009 1011 </Heading> 1010 1012 <NumberedItem> 1011 <Text id="0398">Switch to the <b>Gather</b> panel and in the right-hand side open <Path>englishhistory.net --> tudor</Path>.</Text>1013 <Text id="0398">Switch to the <b>Gather</b> panel and in the right-hand side open <Path>englishhistory.net → tudor</Path>.</Text> 1012 1014 </NumberedItem> 1013 1015 <NumberedItem> … … 1037 1039 </NumberedItem> 1038 1040 <NumberedItem> 1039 <Text id="0406">Choose <Menu>File -->Write CD/DVD image...</Menu>, and in the popup window select the <b>tudor</b> collection as the collection to export. You can optionally name the CD-ROM; otherwise the default "collections" is used. Do so now, entering "Tudor collection" in the field for <b>CD/DVD name</b>; then click <b><Write CD/DVD image></b>.</Text>1041 <Text id="0406">Choose <Menu>File → Write CD/DVD image...</Menu>, and in the popup window select the <b>tudor</b> collection as the collection to export. You can optionally name the CD-ROM; otherwise the default "collections" is used. Do so now, entering "Tudor collection" in the field for <b>CD/DVD name</b>; then click <b><Write CD/DVD image></b>.</Text> 1040 1042 <Text id="0408">The necessary files for export are written to:</Text> 1041 1043 <Text id="0408a"><Path>C:\Program Files\Greenstone\tmp\exported_Tudorcollection</Path></Text> 1044 <Comment> 1045 <Text id="0408b">Note, if you didn't specify a name for the CD-ROM, then the folder name will be <Path>exported_collections</Path> instead of <Path>exported_Tudorcollections</Path>.</Text> 1046 </Comment> 1042 1047 <Text id="0409">You need to use your own computer's software to write these on to CD-ROM. On <i>Windows XP</i> this ability is built into the operating system: assuming you have a CD-ROM or DVD writer insert a blank disk into the drive and drag the contents of <i>exported_Tudorcollection</i> into the folder that represents the disk.</Text> 1043 1048 <Comment> … … 1066 1071 </NumberedItem> 1067 1072 <NumberedItem> 1068 <Text id="0416">You could do the same thing by copying this URL from the web browser, pasting it into the <b>Download </b>panel, and clicking the <<b>Download></b> button. However, several megabytes will be downloaded, which might strain your network resources --or your patience! For a faster exercise we focus on a smaller section of the site. In the <b>Download</b> panel, enter this URL</Text>1069 <Link>http://englishhistory.net/tudor/ monarchs/edward6.html</Link>1070 <Text id="0417">into the <b>Source URL</b> box. There are several options that govern how the download process proceeds. To copy the <i> monarchs </i>section of the website, select <b>Only mirror files below this URL</b>. If you don't do this, the downloading process will follow links to other areas of the <i>englishhistory.net</i> website and grab those as well. Set <b>Download</b> <b>depth</b> to <b>Unlimited</b>-we want to follow as many links as necessary to download all the pages.</Text>1073 <Text id="0416">You could do the same thing by copying this URL from the web browser, pasting it into the <b>Download </b>panel, and clicking the <<b>Download></b> button. However, several megabytes will be downloaded, which might strain your network resources—or your patience! For a faster exercise we focus on a smaller section of the site. In the <b>Download</b> panel, enter this URL</Text> 1074 <Link>http://englishhistory.net/tudor/citizens/</Link> 1075 <Text id="0417">into the <b>Source URL</b> box. There are several options that govern how the download process proceeds. To copy the <i>citizens</i> section of the website, select <b>Only mirror files below this URL</b>. If you don't do this (or if you miss out the terminating "/"), the downloading process will follow links to other areas of the <i>englishhistory.net</i> website and grab those as well. Set <b>Download</b> <b>depth</b> to <b>Unlimited</b>—we want to follow as many links as necessary to download all the pages.</Text> 1071 1076 </NumberedItem> 1072 1077 <NumberedItem> … … 1081 1086 </NumberedItem> 1082 1087 <NumberedItem> 1083 <Text id="0422">Switch to the <b>Create</b> panel to <b>build</b> and <b>preview</b> the collection. It is smaller than the previous collection because we included only the <i> monarchs</i> files. However, these now represent the latest versions of the documents.</Text>1088 <Text id="0422">Switch to the <b>Create</b> panel to <b>build</b> and <b>preview</b> the collection. It is smaller than the previous collection because we included only the <i>citizens</i> files. However, these now represent the latest versions of the documents.</Text> 1084 1089 </NumberedItem> 1085 1090 </Content> … … 1093 1098 <Content> 1094 1099 <NumberedItem> 1095 <Text id="0424">Open up your <b>webtudor</b> collection, and in the <b>Gather</b> panel inspect the files you dragged into it. The first folder is <i>englishhistory.net</i>, which opens up to reveal <i>tudor</i>, and so on. The files represent a complete sweep of the pages (and supporting images) that constitute the <i>Tudor monarchs</i> section of the <i>englishhistory.net</i> web site. They were downloaded from the web in a way that preserved the structure of the original site. This allows any page's original URL to be reconstructed from the folder hierarchy.</Text>1100 <Text id="0424">Open up your <b>webtudor</b> collection, and in the <b>Gather</b> panel inspect the files you dragged into it. The first folder is <i>englishhistory.net</i>, which opens up to reveal <i>tudor</i>, and so on. The files represent a complete sweep of the pages (and supporting images) that constitute the <i>Tudor citizens</i> section of the <i>englishhistory.net</i> web site. They were downloaded from the web in a way that preserved the structure of the original site. This allows any page's original URL to be reconstructed from the folder hierarchy.</Text> 1096 1101 </NumberedItem> 1097 1102 <NumberedItem> … … 1100 1105 <Text id="0427">It is important that the files gathered in the collection start with the web domain name (<i>englishhistory.net</i> in this case). The conversion process will not work if you dragged over a subfolder, for example the <i>tudor</i> folder, because this will set URL metadata to something like</Text> 1101 1106 <Indent> 1102 http://tudor/ monarchs/...1107 http://tudor/citizens/... 1103 1108 </Indent> 1104 1109 <Text id="0428">rather than</Text> 1105 1110 <Indent> 1106 http://englishhistory.net/tudor/ monarchs/...1111 http://englishhistory.net/tudor/citizens/... 1107 1112 </Indent> 1108 1113 <Text id="0429">If you have copied over a subfolder previously, delete it and make a fresh copy. Drag the folder in the right-hand side of the <b>Gather</b> panel on to the trash can in the lower right corner. Then obtain a fresh copy of the files by dragging across the <i>englishhistory.net</i> folder from the Downloaded Files folder on the left-hand side.</Text> … … 1137 1142 </NumberedItem> 1138 1143 <NumberedItem> 1139 <Text id="0439">Repeat for the <i>relative</i> and <i>citizens</i> folder, setting their <b>dc.Subject</b> metadata to <b>Tudor period|Relatives</b> and <b>Tudor period|Citizens</b> respectively. Note that the hierarchy appears in the <b>Existing values for d ls.Subject and Keywords</b> area.</Text>1140 </NumberedItem> 1141 <NumberedItem> 1142 <Text id="0440">Finally, select all remaining files --the ones that are not in the <i>monarchs</i>, <i>relative</i>, and <i>citizens</i> folders--by selecting the first and shift-clicking the last. Set their <b>dc.Subject</b> metadata to <b>Tudor period|Others</b>: this is done in a single operation (there is a short delay before it completes).</Text>1144 <Text id="0439">Repeat for the <i>relative</i> and <i>citizens</i> folder, setting their <b>dc.Subject</b> metadata to <b>Tudor period|Relatives</b> and <b>Tudor period|Citizens</b> respectively. Note that the hierarchy appears in the <b>Existing values for dc.Subject and Keywords</b> area.</Text> 1145 </NumberedItem> 1146 <NumberedItem> 1147 <Text id="0440">Finally, select all remaining files—the ones that are not in the <i>monarchs</i>, <i>relative</i>, and <i>citizens</i> folders—by selecting the first and shift-clicking the last. Set their <b>dc.Subject</b> metadata to <b>Tudor period|Others</b>: this is done in a single operation (there is a short delay before it completes).</Text> 1143 1148 </NumberedItem> 1144 1149 <NumberedItem> … … 1173 1178 </NumberedItem> 1174 1179 <NumberedItem> 1175 <Text id="0451">Having defined the subcollections, we partition the index into corresponding parts. Click the <<b>Assign Partitions</b>> tab. Select the first subcollection and give it the name <b> monarchs</b>; click <<b>Add Partition</b>>. Repeat for the other three subcollections, naming their partitions <b>relatives</b>, <b>citizens</b> and <b>others</b>. <b>Build</b> and <b>preview</b> the collection.</Text>1180 <Text id="0451">Having defined the subcollections, we partition the index into corresponding parts. Click the <<b>Assign Partitions</b>> tab. Select the first subcollection and give it the name <b>citizens</b>; click <<b>Add Partition</b>>. Repeat for the other three subcollections, naming their partitions <b>monarchs</b>, <b>others</b> and <b>relatives</b>. <b>Build</b> and <b>preview</b> the collection.</Text> 1176 1181 </NumberedItem> 1177 1182 <NumberedItem> … … 1185 1190 </NumberedItem> 1186 1191 <NumberedItem> 1187 <Text id="0455">Search for a common term (like <i>the</i>) in all five index partitions, and check that the numbers add up.</Text>1192 <Text id="0455">Search for a common term (like <i>the</i>) in all five index partitions, and check that the numbers of words (not documents) add up.</Text> 1188 1193 </NumberedItem> 1189 1194 <NumberedItem> … … 1212 1217 </NumberedItem> 1213 1218 <NumberedItem> 1214 <Text id="0464">Preview the newly rebuilt collection's <b>titles a-z</b> page. Previously this listed more than a dozen pages per letter of the alphabet, but now there are just three --the first three files encountered by the building process.</Text>1219 <Text id="0464">Preview the newly rebuilt collection's <b>titles a-z</b> page. Previously this listed more than a dozen pages per letter of the alphabet, but now there are just three—the first three files encountered by the building process.</Text> 1215 1220 </NumberedItem> 1216 1221 <NumberedItem> … … 1233 1238 </Heading> 1234 1239 <NumberedItem> 1235 <Text id="0468">Open up your <b>tudor</b> collection, go to the <b>Design</b> panel (by clicking on its tab) and select <b>Format Features </b>from the left-hand list. Leave the <b>Editing Controls </b>at their default value, so that <b>Choose Feature </b>remains blank and <b>VList </b>is selected as the <b>Affected Component</b>. The text in the <b>HTML Format String</b> box reads as follows:</Text>1240 <Text id="0468">Open up your <b>tudor</b> collection, go to the <b>Design</b> panel (by clicking on its tab) and select <b>Format Features </b>from the left-hand list. Leave the editing controls at their default value, so that <b>Choose Feature </b>remains blank and <b>VList </b>is selected as the <b>Affected Component</b>. The text in the <b>HTML Format String</b> box reads as follows:</Text> 1236 1241 <Format> 1237 1242 <td valign=top>[link][icon][/link]</td><br/> … … 1249 1254 </NumberedItem> 1250 1255 <Comment> 1251 <Text id="0474">Greenstone's default format statement is complex --even baroque--because it is designed to produce something reasonable under almost any conditions, and also because for practical reasons it needs to be backwards compatible with legacy collections.</Text>1256 <Text id="0474">Greenstone's default format statement is complex—even baroque—because it is designed to produce something reasonable under almost any conditions, and also because for practical reasons it needs to be backwards compatible with legacy collections.</Text> 1252 1257 </Comment> 1253 1258 <NumberedItem> … … 1262 1267 <Text id="0476"><b>Preview</b> the result (you don't need to build the collection, because changes to format statements take effect immediately). Look at some search results and at the <i>titles a-z</i> list. They are just the same as before! Under most circumstances this far simpler format statement is entirely equivalent to Greenstone's more complex default. </Text> 1263 1268 <Comment> 1264 <Text id="0478">But there's a problem. Beside the bookshelves in the hierarchy browser, beneath the subject appears a mysterious "()". What is printed on these bookshelf nodes is governed by the same format statement, and though bookshelf nodes of the hierarchy have associated <i>Title</i> metadata--their title is the name of the metadata value associated with that bookshelf--they do not have <i>ex.Source</i> metadata, so it comes out blank.</Text>1265 </Comment> 1266 </NumberedItem> 1267 <NumberedItem> 1268 <Text id="0482">In the <b>Format Features</b> section of the <b>Design</b> panel, the <b>Choose Feature</b> menu (just above <b>Affected Component</b> menu) is blank. That implies that the same format is used for the search results, titles, and all nodes in the subject hierarchy --including internal nodes (that is, bookshelves). The <b>Choose Feature</b> menu can be used to restrict a format statement to a specific one of these lists; when it's blank, the <b>VList</b> specification applies throughout. We will override this format statement for the hierarchical <i>subject</i> classifier. In the <b>Choose Feature</b> menu, scroll down to the item that says</Text>1269 <Text id="0478">But there's a problem. Beside the bookshelves in the <b>subjects</b> browser, beneath the subject appears a mysterious "()". What is printed on these bookshelf nodes is governed by the same format statement, and though bookshelf nodes of the hierarchy have associated <i>Title</i> metadata—their title is the name of the metadata value associated with that bookshelf—they do not have <i>ex.Source</i> metadata, so it comes out blank.</Text> 1270 </Comment> 1271 </NumberedItem> 1272 <NumberedItem> 1273 <Text id="0482">In the <b>Format Features</b> section of the <b>Design</b> panel, the <b>Choose Feature</b> menu (just above <b>Affected Component</b> menu) is blank. That implies that the same format is used for the search results, titles, and all nodes in the subject hierarchy—including internal nodes (that is, bookshelves). The <b>Choose Feature</b> menu can be used to restrict a format statement to a specific one of these lists; when it's blank, the <b>VList</b> specification applies throughout. We will override this format statement for the hierarchical <i>subject</i> classifier. In the <b>Choose Feature</b> menu, scroll down to the item that says</Text> 1269 1274 <Indent> 1270 1275 CL2: Hierarchy -metadata dc.Subject and Keywords … … 1292 1297 </NumberedItem> 1293 1298 <NumberedItem> 1294 <Text id="0489">To insert the <b>[dc.Subject]</b>, position the cursor at the appropriate point and either type it in, or use the <b>Variables</b> dropdown menu --the one that says <b>[Text]</b>. Make it say <b>[dc.Subject]</b> and click <b>Insert </b>to insert this into the <b>HTML Format String</b>. This menu shows many of the things that you can put in square brackets in the format statement. The only exception is <b>[Text]</b>, which gives the full text of the document, and can only be used when <b>DocumentText</b> is the <b>Affected Component</b>.</Text>1299 <Text id="0489">To insert the <b>[dc.Subject]</b>, position the cursor at the appropriate point and either type it in, or use the <b>Variables</b> dropdown menu—the one that says <b>[Text]</b>. Make it say <b>[dc.Subject]</b> and click <b>Insert </b>to insert this into the <b>HTML Format String</b>. This menu shows many of the things that you can put in square brackets in the format statement. The only exception is <b>[Text]</b>, which gives the full text of the document, and can only be used when <b>DocumentText</b> is the <b>Affected Component</b>.</Text> 1295 1300 </NumberedItem> 1296 1301 <NumberedItem> … … 1314 1319 <Text id="0496">and click <b>Replace Format</b>. Again, you can insert the items in square brackets by selecting them from the <b>Variables</b> dropdown box (don't forget to click <b>Insert</b>).</Text> 1315 1320 <Comment> 1316 <Text id="0497">The <b>If</b> statement tests the value of the variable <b>numleafdocs</b>. This variable is only set for internal nodes of the hierarchy, i.e. bookshelves, and gives the number of documents below that node. If it is set we take the first branch, otherwise we take the second. Commas are used to separate the branches. The curly brackets serve to indicate that the <b>If</b> is special--otherwise the word "If" itself would be output.</Text>1321 <Text id="0497">The <b>If</b> statement tests the value of the variable <b>numleafdocs</b>. This variable is only set for internal nodes of the hierarchy, i.e. bookshelves, and gives the number of documents below that node. If it is set we take the first branch, otherwise we take the second. Commas are used to separate the branches. The curly brackets serve to indicate that the <b>If</b> is special—otherwise the word "If" itself would be output.</Text> 1317 1322 </Comment> 1318 1323 </NumberedItem> … … 1333 1338 </NumberedItem> 1334 1339 <NumberedItem> 1335 <Text id="0507">Go to the <b>Create </b>panel and click <<b>Preview Collection</b>>. The content of your collection remains the same, but its appearance has changed completely --for example, all the pages are pink! To learn about how to control these changes, go to the documented example collection called <i>Garish version of demo collection</i>, and read about it.</Text>1340 <Text id="0507">Go to the <b>Create </b>panel and click <<b>Preview Collection</b>>. The content of your collection remains the same, but its appearance has changed completely—for example, all the pages are pink! To learn about how to control these changes, go to the documented example collection called <i>Garish version of demo collection</i>, and read about it.</Text> 1336 1341 </NumberedItem> 1337 1342 <Heading> … … 1366 1371 <Content> 1367 1372 <NumberedItem> 1368 <Text id="0521">Start a new collection called <b>Beatles Bibliography</b>. Enter the requested information and make it a <b>New Collection</b>. There is no need to include any metadata sets because the metadata extracted from the MARC records will appear as extracted metadata. Deselect the <b>Dublin Core</b> metadata set, and click <<b>OK</b>></Text> 1373 <Text id="0521">Start a new collection called <b>Beatles Bibliography</b>. Enter the requested information and make it a <b>New Collection</b>. There is no need to include any metadata sets because the metadata extracted from the MARC records will appear as extracted metadata. Deselect the <b>Dublin Core</b> metadata set, and click <<b>OK</b>>.</Text> 1374 <Text id="0521a">A <b>No metadata Sets Selected</b> warning message will pop-up, alerting you to the fact that you won't be able to manually assign metadata to the collection. In this collection, all the metadata will come from the MARC file; click <<b>OK</b>> to continue. (If you don't want to see this popup again, tick the <b>Do not show this warning again</b> checkbox.)</Text> 1369 1375 </NumberedItem> 1370 1376 <NumberedItem> … … 1372 1378 </NumberedItem> 1373 1379 <NumberedItem> 1374 <Text id="0523">Remove the plugins <b>TextPlug</b> to <b>NULPlug</b> by selecting each one in the <b>Currently Assigned Plugins</b> list and clicking <b>Remove Plugin</b>(<b>ZIPPlug</b>, <b>GAPlug</b> and <b>MARCPlug</b> remain). It is not strictly necessary to remove these redundant plugins, but it is good practice to include only plugins that are needed, to avoid accidentally including stray documents.</Text>1380 <Text id="0523">Remove the plugins <b>TextPlug</b> to <b>NULPlug</b> by selecting each one in the <b>Currently Assigned Plugins</b> list and clicking <<b>Remove Plugin</b>> (<b>ZIPPlug</b>, <b>GAPlug</b> and <b>MARCPlug</b> remain). It is not strictly necessary to remove these redundant plugins, but it is good practice to include only plugins that are needed, to avoid accidentally including stray documents.</Text> 1375 1381 </NumberedItem> 1376 1382 <NumberedItem> … … 1378 1384 </NumberedItem> 1379 1385 <NumberedItem> 1380 <Text id="0525">Switch to the <b>Create</b> panel, <b>build </b>the collection, and <b>preview</b> it. Browse through the <b>titles a-z</b> and view a record or two. Try searching --for example, find items that include <b>George Martin</b>.</Text>1386 <Text id="0525">Switch to the <b>Create</b> panel, <b>build </b>the collection, and <b>preview</b> it. Browse through the <b>titles a-z</b> and view a record or two. Try searching—for example, find items that include <b>George Martin</b>.</Text> 1381 1387 </NumberedItem> 1382 1388 <NumberedItem> … … 1390 1396 </NumberedItem> 1391 1397 <NumberedItem> 1392 <Text id="0529">Make each bookshelf node show how many entries it contains by appending this to the <b>Format Features </b>for<b>VList</b> format statement in the <b>Design</b> panel:</Text>1398 <Text id="0529">Make each bookshelf node show how many entries it contains by appending this to the <b>Format Features</b> for the <b>VList</b> format statement in the <b>Design</b> panel:</Text> 1393 1399 <Format>{If}{[numleafdocs],<td><i>([numleafdocs])</i></td>}</Format> 1394 1400 </NumberedItem> … … 1400 1406 </Heading> 1401 1407 <NumberedItem> 1402 <Text id="0532">In the <b>Design</b> panel select <b>Search Types</b> from the left-hand list and activate the <b>Enable Advanced Searches </b>options.</Text>1408 <Text id="0532">In the <b>Design</b> panel select <b>Search Types</b> from the left-hand list and activate the <b>Enable Advanced Searches</b> option.</Text> 1403 1409 </NumberedItem> 1404 1410 <NumberedItem> … … 1415 1421 </Heading> 1416 1422 <NumberedItem> 1417 <Text id="0536">From the <b>General</b> section of the <b>Design</b> panel, click the <b><Browse ></b> button next to the label <b>URL to 'about page' icon</b> and use the resulting popup file browser to access the folder <i>sample_files\marc</i>. Select <i>beatles_logo.jpg</i> and click <<b>Open</b>>.</Text>1423 <Text id="0536">From the <b>General</b> section of the <b>Design</b> panel, click the <b><Browse...></b> button next to the label <b>URL to 'about page' icon</b> and use the resulting popup file browser to access the folder <i>sample_files\marc</i>. Select <i>beatles_logo.jpg</i> and click <<b>Open</b>>.</Text> 1418 1424 <Comment> 1419 1425 <Text id="0537">Greenstone copies the image into your collection area, so the collection will still work when the CD-ROM is removed from the drive.</Text> … … 1437 1443 <NumberedItem> 1438 1444 <Text id="0541">Copy the entire folder</Text> 1439 <Path>sample_files -->beatles-->advbeat_large</Path>1445 <Path>sample_files → beatles → advbeat_large</Path> 1440 1446 <Text id="0542">(with all its contents) into your Greenstone <i>collect</i> folder. If you have installed Greenstone in the usual place, this is</Text> 1441 1447 <Path> 1442 <Text id="0542a">My Computer -->Local Disk (C:)-->Program Files-->Greenstone-->collect</Text>1448 <Text id="0542a">My Computer → Local Disk (C:) → Program Files → Greenstone → collect</Text> 1443 1449 </Path> 1444 1450 <Text id="0543">Put <i>advbeat_large</i> in there.</Text> … … 1454 1460 </NumberedItem> 1455 1461 <NumberedItem> 1456 <Text id="0547">Observe the low quality of the metadata. For example, the four items under <i>A Hard Day's Night</i> (under " A" in the <i>titles a-z</i> browser) have different variants as their titles. The collection would have been easier to organize had the metadata been cleaned up manually first, but that would be a big job. Only a tiny amount of metadata was added by hand--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>1462 <Text id="0547">Observe the low quality of the metadata. For example, the four items under <i>A Hard Day's Night</i> (under "H" in the <i>titles a-z</i> browser) have different variants as their titles. The collection would have been easier to organize had the metadata been cleaned up manually first, but that would be a big job. Only a tiny amount of metadata was added by hand—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> 1457 1463 </NumberedItem> 1458 1464 <NumberedItem> 1459 1465 <Text id="0548">In the Windows file browser, take a look at the files that makes up the collection, in the</Text> 1460 <Path>sample_files -->beatles-->advbeat_large-->import</Path>1466 <Path>sample_files → beatles → advbeat_large → import</Path> 1461 1467 <Text id="0549">folder. What a mess! There are over 450 files under seven top-level sub-folders. Organization is minimal, reflecting the different times and ways the files were gathered. For example, <i>html_lyrics</i> and <i>discography</i> are excerpts of web sites, and <i>cover_images </i>contains album covers in JPEG format. For each type, drill down through the hierarchy and look at a sample document.</Text> 1462 1468 </NumberedItem> … … 1475 1481 </Comment> 1476 1482 <NumberedItem> 1477 <Text id="0552">Start a new collection (<Menu>File -->New</Menu>) called <b>small_beatles</b>, basing it on the default "New Collection." (Basing it on the existing Advanced Beatles collection would make your life far easier, but we want you to learn how to build it from scratch!) Fill out the fields with appropriate information. Use the Dublin Core metadata set (set by default).</Text>1483 <Text id="0552">Start a new collection (<Menu>File → New</Menu>) called <b>small_beatles</b>, basing it on the default "New Collection." (Basing it on the existing Advanced Beatles collection would make your life far easier, but we want you to learn how to build it from scratch!) Fill out the fields with appropriate information. Use the Dublin Core metadata set (set by default).</Text> 1478 1484 </NumberedItem> 1479 1485 <NumberedItem> 1480 1486 <Text id="0554">Copy the files provided in</Text> 1481 <Path>sample_files -->beatles-->advbeat_small</Path>1482 <Text id="0555">into your new collection. Do this by opening up <i>advbeat_small</i>,<i> </i>selecting the eight items within it (from <i>cover_images</i> to <i>beatles_midi.zip</i>), and dragging them across. Because some of these files are in MP3 and MARC formats you will be asked whether to include <b>MP3Plug</b> and <b>MARCPlug</b> in your collection. Click <<b>Add Plugin</b>>. Also, a popup window will tell you that no plugins can process the .css file: click <<b>OK</b>> to close this popup.</Text>1483 </NumberedItem> 1484 <NumberedItem> 1485 <Text id="0556">Change to the <b>Enrich</b> panel and browse around the files. There is no metadata --yet. Recall that you can double-click files to view them.</Text>1487 <Path>sample_files → beatles → advbeat_small</Path> 1488 <Text id="0555">into your new collection. Do this by opening up <i>advbeat_small</i>,<i> </i>selecting the eight items within it (from <i>cover_images</i> to <i>beatles_midi.zip</i>), and dragging them across. Because some of these files are in MP3 and MARC formats you will be asked whether to include <b>MP3Plug</b> and <b>MARCPlug</b> in your collection. Click <<b>Add Plugin</b>>.</Text> 1489 </NumberedItem> 1490 <NumberedItem> 1491 <Text id="0556">Change to the <b>Enrich</b> panel and browse around the files. There is no metadata—yet. Recall that you can double-click files to view them.</Text> 1486 1492 <Text id="0557">(There are no MIDI files in the collection: these require more advanced customisation because there is no MIDI plugin. We will deal with them later.)</Text> 1487 1493 </NumberedItem> … … 1496 1502 </Heading> 1497 1503 <NumberedItem> 1498 <Text id="0561">You might want to correct some of the metadata --for example, the atrocious misspelling in the titles "MAGICAL MISTERY TOUR." These documents are in the discography section, with filenames that contain the same misspelling. Locate one of them in the <b>Enrich</b> panel. Notice that the extracted metadata element <b>ex.Title</b> is now filled in, and misspelt. You cannot correct this element, for it is extracted from the file and will be re-extracted every time the collection is re-built.</Text>1504 <Text id="0561">You might want to correct some of the metadata—for example, the atrocious misspelling in the titles "MAGICAL MISTERY TOUR." These documents are in the discography section, with filenames that contain the same misspelling. Locate one of them in the <b>Enrich</b> panel. Notice that the extracted metadata element <b>ex.Title</b> is now filled in, and misspelt. You cannot correct this element, for it is extracted from the file and will be re-extracted every time the collection is re-built.</Text> 1499 1505 </NumberedItem> 1500 1506 <NumberedItem> … … 1508 1514 <BulletList> 1509 1515 <Bullet> 1510 <Text id="0565">Type "dc.Title," before the <i>ex.Title </i>in the metadata box --i.e. make it read</Text>1516 <Text id="0565">Type "dc.Title," before the <i>ex.Title </i>in the metadata box—i.e. make it read</Text> 1511 1517 <Format> 1512 1518 dc.Title,ex.Title … … 1537 1543 </Bullet> 1538 1544 <Bullet> 1539 <Text id="0574">Add an <b>AZCompactList</b> classifier. Select <b>dc.Format</b> as the metadata field and specify " Browse" as the <b>buttonname</b>. Click the <b>sort</b> checkbox, and specify "Title" in the adjacent text box: this will make the classifier display documents in alphabetical order of title.</Text>1545 <Text id="0574">Add an <b>AZCompactList</b> classifier. Select <b>dc.Format</b> as the metadata field and specify "browse" as the <b>buttonname</b>. Click the <b>sort</b> checkbox, and specify "Title" in the adjacent text box: this will make the classifier display documents in alphabetical order of title.</Text> 1540 1546 </Bullet> 1541 1547 </BulletList> … … 1574 1580 </BulletList> 1575 1581 <Text id="0585">To make this easier for you we have prepared a plain text file that contains the new text. In WordPad open the following file:</Text> 1576 <Path>sample_files -->beatles-->format_tweaks-->audio_tweak.txt</Path>1577 <Text id="0586">(Be sure to use WordPad rather than Notepad, because Notepad does not display the line breaks correctly.) Place it in the copy buffer by highlighting the text in WordPad and selecting <Menu>Edit -->Copy</Menu>. Now move back to the Librarian Interface, highlight all the text that makes up the current VList format statement, and use <Menu>Edit-->Paste</Menu> to transform the old statement to the new one. Remember to press <<b>Replace Format</b>> when finished.</Text>1582 <Path>sample_files → beatles → format_tweaks → audio_tweak.txt</Path> 1583 <Text id="0586">(Be sure to use WordPad rather than Notepad, because Notepad does not display the line breaks correctly.) Place it in the copy buffer by highlighting the text in WordPad and selecting <Menu>Edit → Copy</Menu>. Now move back to the Librarian Interface, highlight all the text that makes up the current VList format statement, and use <Menu>Edit → Paste</Menu> to transform the old statement to the new one. Remember to press <<b>Replace Format</b>> when finished.</Text> 1578 1584 <Text id="0589"><b>Preview</b> the result. If you are using the Greenstone Local Library server, change to the <b>Create </b>panel and click <<b>Preview Collection</b>>, which causes the local library server to rescan the format statements. You do not need to build the collection again because format statements are only used by the runtime system.</Text> 1579 1585 <Text id="0592">However, you may need to click the browser's <<b>Reload</b>> button to force it to re-load the page.</Text> … … 1630 1636 <highlight><td>{If}{[numleafdocs],([numleafdocs])}</td></highlight><br/> 1631 1637 <td valign=top>[highlight] {Or}{[dls.Title],[dc.Title],[Title],Untitled} [/highlight]</td></Format> 1632 <Text id="0607">You will find this text in <i>format_tweaks</i>--></Text> 1633 <Text id="0608"><i>show_num_docs.txt</i>, which can be copied and pasted in as before. Don't forget to click <<b>Replace Format</b>>.</Text> 1638 <Text id="0607">You will find this text in <Path>format_tweaks → show_num_docs.txt</Path>, which can be copied and pasted in as before. Don't forget to click <<b>Replace Format</b>>.</Text> 1634 1639 <Text id="0609"><b>Preview</b> the result (you don't need to build the collection.)</Text> 1635 1640 </NumberedItem> 1636 1641 <NumberedItem> 1637 <Text id="0610">Now turn to the images. Dummy documents are displayed here too. First change to the <b>Enrich</b> panel, open the folder <i>cover_images</i> and add <b>dc.Title</b> <i> </i>metadata, assigning to each of the ten documents the title of the corresponding album. Remember, you can double-click a file to view it.</Text>1642 <Text id="0610">Now turn to the images. Dummy documents are displayed here too. First change to the <b>Enrich</b> panel, open the folder <i>cover_images</i> and add <b>dc.Title</b> metadata, assigning to each of the ten documents the title of the corresponding album. Remember, you can double-click a file to view it.</Text> 1638 1643 </NumberedItem> 1639 1644 <NumberedItem> … … 1653 1658 <NumberedItem> 1654 1659 <Text id="0613">To complete the collection, use the browse button of <b>URL to 'about page' icon</b> in the <b>General</b> section of the <b>Design</b> panel to select the following image:</Text> 1655 <Path>advbeatles_large -->images-->flick4.gif.</Path>1660 <Path>advbeatles_large → images → flick4.gif.</Path> 1656 1661 <Text id="0616"><b>Build</b> the collection again and <b>preview</b> it.</Text> 1657 1662 </NumberedItem> … … 1666 1671 </Comment> 1667 1672 <NumberedItem> 1668 <Text id="0627"><b>UnknownPlug</b> is a useful generic plugin. It knows nothing about any given format but can be tailored to process particular document types --like MIDI--based on their filename extension, and set basic metadata.</Text>1673 <Text id="0627"><b>UnknownPlug</b> is a useful generic plugin. It knows nothing about any given format but can be tailored to process particular document types—like MIDI—based on their filename extension, and set basic metadata.</Text> 1669 1674 <Text id="0627a">In the <b>Document Plugins</b> section of the <b>Design</b> panel:</Text> 1670 1675 <BulletList> … … 1685 1690 <BulletList> 1686 1691 <Bullet> 1687 <Text id="0633">Back in the <b>Enrich</b> panel, click on the file <i>beatles_midi.zip</i> and assign its <b>dc.Format</b> value to "Audio" --do this by clicking on "Audio" in the <b>Existing values for dc.Format</b> list. All files extracted from the Zip file inherit its settings.</Text>1692 <Text id="0633">Back in the <b>Enrich</b> panel, click on the file <i>beatles_midi.zip</i> and assign its <b>dc.Format</b> value to "Audio"—do this by clicking on "Audio" in the <b>Existing values for dc.Format</b> list. All files extracted from the Zip file inherit its settings.</Text> 1688 1693 </Bullet> 1689 1694 </BulletList> … … 1702 1707 </Comment> 1703 1708 <NumberedItem> 1704 <Text id="0624">To switch modes, click <Menu>File -->Preferences-->Mode</Menu> and change to <b>Library Systems Specialist</b>. Note from the description that appears that you need to be able to formulate regular expressions to use this mode fully. That is what we do below.</Text>1709 <Text id="0624">To switch modes, click <Menu>File → Preferences → Mode</Menu> and change to <b>Library Systems Specialist</b>. Note from the description that appears that you need to be able to formulate regular expressions to use this mode fully. That is what we do below.</Text> 1705 1710 </NumberedItem> 1706 1711 <NumberedItem> … … 1731 1736 <NumberedItem> 1732 1737 <Text id="0645">Using your Windows file browser outside Greenstone, locate the folder</Text> 1733 <Path>sample_files -->beatles-->advbeat_large</Path>1738 <Path>sample_files → beatles → advbeat_large</Path> 1734 1739 </NumberedItem> 1735 1740 <NumberedItem> … … 1740 1745 </Heading> 1741 1746 <NumberedItem> 1742 <Text id="0648">Re-Edit your <b>VList</b> format statement to be the following (in <Menu>Design -->Format Features</Menu>)</Text>1747 <Text id="0648">Re-Edit your <b>VList</b> format statement to be the following (in <Menu>Design → Format Features</Menu>)</Text> 1743 1748 <Format><highlight><td valign=top></highlight><br/> 1744 1749 <highlight>{If}{[numleafdocs],[link][icon][/link]}</highlight><br/> … … 1761 1766 </NumberedItem> 1762 1767 <NumberedItem> 1763 <Text id="0649">The complete statement is in the file <Path>format_tweaks -->multi_icons.txt</Path>.</Text>1768 <Text id="0649">The complete statement is in the file <Path>format_tweaks → multi_icons.txt</Path>.</Text> 1764 1769 </NumberedItem> 1765 1770 <NumberedItem> … … 1805 1810 <NumberedItem> 1806 1811 <Text id="0658"><b>Preview</b> the collection's home page. The page background is now the new graphic.</Text> 1807 <Text id="0659">Other features can be altered by editing the macro files --for example, the headers and footers used on each page, and the highlighting style used for search terms (specify a different colour, use bold etc.).</Text>1812 <Text id="0659">Other features can be altered by editing the macro files—for example, the headers and footers used on each page, and the highlighting style used for search terms (specify a different colour, use bold etc.).</Text> 1808 1813 </NumberedItem> 1809 1814 <NumberedItem> … … 1817 1822 <BulletList> 1818 1823 <Bullet> 1819 <Text id="0663">Close the current collection (<Menu>File -->Close</Menu>).</Text>1820 </Bullet> 1821 <Bullet> 1822 <Text id="0664">Start a new collection called <i>advbeat_large</i> (<Menu>File -->New</Menu>).</Text>1824 <Text id="0663">Close the current collection (<Menu>File → Close</Menu>).</Text> 1825 </Bullet> 1826 <Bullet> 1827 <Text id="0664">Start a new collection called <i>advbeat_large</i> (<Menu>File → New</Menu>).</Text> 1823 1828 </Bullet> 1824 1829 <Bullet> … … 1826 1831 </Bullet> 1827 1832 <Bullet> 1828 <Text id="0666">Copy the content of <Path>sample_files -->beatles-->advbeat_large-->import</Path> into this newly formed collection. Since there are considerably more files in this set of documents the copy will take longer.</Text>1833 <Text id="0666">Copy the content of <Path>sample_files → beatles → advbeat_large → import</Path> into this newly formed collection. Since there are considerably more files in this set of documents the copy will take longer.</Text> 1829 1834 <Text id="0670"><b>Build</b> the collection and preview the result. (If you want the collection to have an icon, you will have to add it from the <b>Design</b> panel.)</Text> 1830 1835 </Bullet> … … 1859 1864 </NumberedItem> 1860 1865 <NumberedItem> 1861 <Text id="0678">In <Menu>Design -->DocumentPlugins</Menu>, add <b>PagedImgPlug</b>. Switch on its <b>screenview</b> configuration option by checking the box. The source images we use were scanned at high resolution and are large files for a browser to download. The <i>screenview</i> option generates smaller screen-resolution images of each page when the collection is built.</Text>1866 <Text id="0678">In <Menu>Design → DocumentPlugins</Menu>, add <b>PagedImgPlug</b>. Switch on its <b>screenview</b> configuration option by checking the box. The source images we use were scanned at high resolution and are large files for a browser to download. The <i>screenview</i> option generates smaller screen-resolution images of each page when the collection is built.</Text> 1862 1867 </NumberedItem> 1863 1868 <NumberedItem> … … 1963 1968 </Comment> 1964 1969 <Comment> 1965 <Text id="0709">Sometimes there is more than one plug-in that could process a file --for example, the .xml extension is used for many different XML formats. The popup window, therefore, offers a choice of all possible plug-ins that matched. It is normally easy to determine the correct choice. If you wish, you can ignore the prompt (click <Don't Add Plugin>), because plug-ins can be added later, in the Document Plugins section of the Design panel.</Text>1970 <Text id="0709">Sometimes there is more than one plug-in that could process a file—for example, the .xml extension is used for many different XML formats. The popup window, therefore, offers a choice of all possible plug-ins that matched. It is normally easy to determine the correct choice. If you wish, you can ignore the prompt (click <Don't Add Plugin>), because plug-ins can be added later, in the Document Plugins section of the Design panel.</Text> 1966 1971 </Comment> 1967 1972 <NumberedItem> … … 2012 2017 <Format><h3>[Subject]</h3></Format> 2013 2018 <Comment> 2014 <Text id="0723">The document heading appears above the detach and no highlighting buttons when you get to a document in the collection. By default DocumentHeading displays the document's ex.Title metadata. In this particular set of OAI exported records, titles are filenames of JPEG images, and the filenames are particularly uninformative (for example, 01dla14). You can see them in the <b>Enrich</b> panel if you select an image in <Path>sample_small -->oai-->JCDLPICS-->srcdocs</Path> and check its filename and <i>ex.Title</i> metadata. The above format statement displays <i>ex.Subject</i> metadata instead.</Text>2019 <Text id="0723">The document heading appears above the detach and no highlighting buttons when you get to a document in the collection. By default DocumentHeading displays the document's ex.Title metadata. In this particular set of OAI exported records, titles are filenames of JPEG images, and the filenames are particularly uninformative (for example, 01dla14). You can see them in the <b>Enrich</b> panel if you select an image in <Path>sample_small → oai → JCDLPICS → srcdocs</Path> and check its filename and <i>ex.Title</i> metadata. The above format statement displays <i>ex.Subject</i> metadata instead.</Text> 2015 2020 </Comment> 2016 2021 </NumberedItem> … … 2046 2051 <Content> 2047 2052 <Comment> 2048 <Text id="0734">The previous exercise did not obtain the data from an external OAI-PMH server. This missing step is accomplished by running a command-line program. To do this, your computer must have a direct connection to the Internet --being behind a firewall may interfere with the ability to download the information.</Text>2053 <Text id="0734">The previous exercise did not obtain the data from an external OAI-PMH server. This missing step is accomplished by running a command-line program. To do this, your computer must have a direct connection to the Internet—being behind a firewall may interfere with the ability to download the information.</Text> 2049 2054 </Comment> 2050 2055 <NumberedItem> … … 2060 2065 </NumberedItem> 2061 2066 <NumberedItem> 2062 <Text id="0739">Open a DOS window to access the command-line prompt. This facility should be located somewhere within your <Menu>Start -->Programs</Menu> menu, but details vary between different Windows systems. If you cannot locate it, select <Menu>Start-->Run</Menu> and enter <i>cmd</i> in the popup window that appears.</Text>2067 <Text id="0739">Open a DOS window to access the command-line prompt. This facility should be located somewhere within your <Menu>Start → Programs</Menu> menu, but details vary between different Windows systems. If you cannot locate it, select <Menu>Start → Run</Menu> and enter <i>cmd</i> in the popup window that appears.</Text> 2063 2068 </NumberedItem> 2064 2069 <NumberedItem> … … 2104 2109 </Comment> 2105 2110 <NumberedItem> 2106 <Text id="0753">Click <Menu>File -->Preferences-->Mode</Menu> and change to <i>Expert</i> mode.</Text>2111 <Text id="0753">Click <Menu>File → Preferences → Mode</Menu> and change to <i>Expert</i> mode.</Text> 2107 2112 </NumberedItem> 2108 2113 <NumberedItem> … … 2128 2133 <Content> 2129 2134 <NumberedItem> 2130 <Text id="0761">First, change to <i>Library System Specialist</i> (or <i>Expert</i>) mode (using <Menu>File -->Preferences</Menu>), because you will need to change the order of plug-ins in the <b>Design</b> panel.</Text>2135 <Text id="0761">First, change to <i>Library System Specialist</i> (or <i>Expert</i>) mode (using <Menu>File → Preferences</Menu>), because you will need to change the order of plug-ins in the <b>Design</b> panel.</Text> 2131 2136 </NumberedItem> 2132 2137 <NumberedItem> … … 2155 2160 </Comment> 2156 2161 <Comment> 2157 <Text id="0771">Below we use a plug-in option (first_inorder_ext) to fuse the alternative forms together. This option has the effect of treating documents with the same filename but different extensions as a single entity within a collection. One of the files is viewed as the primary document --it is indexed, and metadata is extracted from it if possible--while the others are handled as "associated files."</Text>2162 <Text id="0771">Below we use a plug-in option (first_inorder_ext) to fuse the alternative forms together. This option has the effect of treating documents with the same filename but different extensions as a single entity within a collection. One of the files is viewed as the primary document—it is indexed, and metadata is extracted from it if possible—while the others are handled as "associated files."</Text> 2158 2163 </Comment> 2159 2164 <Comment> … … 2167 2172 </NumberedItem> 2168 2173 <Comment> 2169 <Text id="0775">There are now only 5 documents, because only one version of each document has been included --the primary version.</Text>2174 <Text id="0775">There are now only 5 documents, because only one version of each document has been included—the primary version.</Text> 2170 2175 </Comment> 2171 2176 <Comment> … … 2214 2219 </NumberedItem> 2215 2220 <Comment> 2216 <Text id="0787">There are still only 5 documents, but against some of the entries --for example, Interview with Bob Dylan--appears the line "Also available as," followed by icons that link to the alternative representations.</Text>2221 <Text id="0787">There are still only 5 documents, but against some of the entries—for example, Interview with Bob Dylan—appears the line "Also available as," followed by icons that link to the alternative representations.</Text> 2217 2222 </Comment> 2218 2223 </Content> … … 2239 2244 </NumberedItem> 2240 2245 <Comment> 2241 <Text id="0793">Exporting in Greenstone is an additive process. If you ran the export.pl command once again, the new files exported would be added --with different folder names--to those already in the export folder. For the kind of explorations we are conducting we might re-run the command several times. The -removeold option deletes files that have previously been exported.</Text>2246 <Text id="0793">Exporting in Greenstone is an additive process. If you ran the export.pl command once again, the new files exported would be added—with different folder names—to those already in the export folder. For the kind of explorations we are conducting we might re-run the command several times. The -removeold option deletes files that have previously been exported.</Text> 2242 2247 </Comment> 2243 2248 <NumberedItem>
Note:
See TracChangeset
for help on using the changeset viewer.
