- Timestamp:
- 2006-03-17T11:45:04+13:00 (18 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/gsdl-documentation/tutorials/xml-source/tutorial_en.xml
r11352 r11383 56 56 </Heading> 57 57 <NumberedItem> 58 <Text id="0099">Launch the prebuilt library by clicking: 58 <Text id="0099">Launch the prebuilt library by clicking:</Text> 59 59 <Menu> 60 60 <Text id="0100">Start --></Text> … … 74 74 </NumberedItem> 75 75 <NumberedItem> 76 <Text id="0107">Access the <b>first book</b> in the list of titles by clicking the <b>book icon</b> next to the title: 76 <Text id="0107">Access the <b>first book</b> in the list of titles by clicking the <b>book icon</b> next to the title:</Text> 77 77 <Text id="0108"><i>About UNAIDS</i>.</Text> 78 78 </NumberedItem> … … 162 162 <Bullet> 163 163 <Question> 164 <Text id="0134">What does AAVP stand for? 164 <Text id="0134">What does AAVP stand for?</Text> 165 165 </Question> 166 166 <Answer>African Aids Vaccination Programme</Answer> … … 385 385 <Text id="0201">From http://www.greenstone.org</Text> 386 386 <Text id="0202">Most people download the Windows distribution from http://www.greenstone.org, which contains the latest version of the Greenstone. There are several optional modules that must be downloaded separately (to avoid a single massive download): <b>documented example collections</b>, the <b>Export to CD-ROM</b> package, and the <b>Language Pack</b>. There is also the set of <b>sample files</b> used in these exercises. (To reduce the download size the documented example collections are distributed in unbuilt form and need to be built.)</Text> 387 <Text id="0203">You need <b>Java</b> to run Greenstone. You might already have it; otherwise download it from http://java.sun.com. To work with image collections, you need <b>ImageMagick</b> (from http://www.imagemagick.org). 387 <Text id="0203">You need <b>Java</b> to run Greenstone. You might already have it; otherwise download it from http://java.sun.com. To work with image collections, you need <b>ImageMagick</b> (from http://www.imagemagick.org).</Text> 388 388 </NumberedItem> 389 389 <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>--></Text> … … 489 489 </NumberedItem> 490 490 <NumberedItem> 491 <Text id="0238">Remove the old version by going to the Windows Control Panel (from the <i>Settings</i> item on the <i>Start</i> menu). Click <b>Add or Remove Programs</b>, select <b>Greenstone Digital Library Software</b>, and <b>Remove</b> it. (To do this you may need Windows "Administrator" privileges.) 491 <Text id="0238">Remove the old version by going to the Windows Control Panel (from the <i>Settings</i> item on the <i>Start</i> menu). Click <b>Add or Remove Programs</b>, select <b>Greenstone Digital Library Software</b>, and <b>Remove</b> it. (To do this you may need Windows "Administrator" privileges.)</Text> 492 492 </NumberedItem> 493 493 <NumberedItem> … … 504 504 </NumberedItem> 505 505 <Comment> 506 <Text id="0243">There have been some superficial changes to the installation procedure in moving to Greenstone Version 2.60, because it uses a different installer program. 506 <Text id="0243">There have been some superficial changes to the installation procedure in moving to Greenstone Version 2.60, because it uses a different installer program.</Text> 507 507 </Comment> 508 508 <Comment> … … 525 525 </Comment> 526 526 <NumberedItem> 527 <Text id="0250">Locate the Greenstone Language Pack. This may be on the CD-ROM from which you installed Greenstone, or you may have to download it from <i>http://www.greenstone.org</i>. 527 <Text id="0250">Locate the Greenstone Language Pack. This may be on the CD-ROM from which you installed Greenstone, or you may have to download it from <i>http://www.greenstone.org</i>.</Text> 528 528 </NumberedItem> 529 529 <NumberedItem> … … 572 572 </NumberedItem> 573 573 <NumberedItem> 574 <Text id="0264">Next you must gather together the files that will constitute the collection. A suitable set has been prepared ahead of time in <i>sample_files</i> in the folder <i>hobbits</i>. Using the left-hand side of the Librarian Interface's <b>Gather</b> panel, interactively navigate to the <i>sample_files</i> folder. 574 <Text id="0264">Next you must gather together the files that will constitute the collection. A suitable set has been prepared ahead of time in <i>sample_files</i> in the folder <i>hobbits</i>. Using the left-hand side of the Librarian Interface's <b>Gather</b> panel, interactively navigate to the <i>sample_files</i> folder.</Text> 575 575 </NumberedItem> 576 576 <NumberedItem> … … 593 593 </NumberedItem> 594 594 <NumberedItem> 595 <Text id="0271">Back in the Librarian Interface, click the <b>Enrich</b> tab to view the metadata associated with the documents in the collection. 595 <Text id="0271">Back in the Librarian Interface, click the <b>Enrich</b> tab to view the metadata associated with the documents in the collection.</Text> 596 596 </NumberedItem> 597 597 <NumberedItem> … … 631 631 <Text id="0283"><i>Word_and_PDF</i>--></Text> 632 632 <Text id="0284"><i>Documents</i></Text> 633 <Text id="0285"> 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. 633 <Text id="0285"> 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.</Text> 634 634 <Text id="0286">(This is the normal technique of multiple selection.)</Text> 635 635 </NumberedItem> … … 665 665 </NumberedItem> 666 666 <NumberedItem> 667 <Text id="0297">Click on the <<b>Browse</b>> button associated with "URL to about page icon", and browse to the image 667 <Text id="0297">Click on the <<b>Browse</b>> button associated with "URL to about page icon", and browse to the image</Text> 668 668 <Text id="0298"><i>sample_files</i>--></Text> 669 669 <Text id="0299"><i>Word_and_PDF</i>--></Text> … … 679 679 </Heading> 680 680 <NumberedItem> 681 <Text id="0304">Now look at the <b>Document Plugins</b> section, by clicking on this in the list to the left. Here you can add, configure or remove plugins to be used in the collection. There is no need to remove any plugins, but it will speed up processing a little. In this case we have only Word, PDF, RTF, and PostScript documents, and can remove the ZIPPlug, TEXTPlug, HTMLPlug, EMAILPlug ImagePlug and NULPlug plugins. To delete a plugin, select it and click <<b>Remove Plugin</b>>. GAPlug is required for any type of source collection and should not be removed. 681 <Text id="0304">Now look at the <b>Document Plugins</b> section, by clicking on this in the list to the left. Here you can add, configure or remove plugins to be used in the collection. There is no need to remove any plugins, but it will speed up processing a little. In this case we have only Word, PDF, RTF, and PostScript documents, and can remove the ZIPPlug, TEXTPlug, HTMLPlug, EMAILPlug ImagePlug and NULPlug plugins. To delete a plugin, select it and click <<b>Remove Plugin</b>>. GAPlug is required for any type of source collection and should not be removed.</Text> 682 682 </NumberedItem> 683 683 <Heading> … … 712 712 </Heading> 713 713 <NumberedItem> 714 <Text id="0315">The <b>Browsing Classifiers</b> section adds "classifiers," which provide the collection with browsing functions. Go to this section and observe that Greenstone has provided two classifiers, <i>AZLists</i> based on <i>ex.Title</i> and <i>ex.Source</i> metadata. Remove both of these by selecting them in turn and clicking <<b>Remove Classifier</b>>. 714 <Text id="0315">The <b>Browsing Classifiers</b> section adds "classifiers," which provide the collection with browsing functions. Go to this section and observe that Greenstone has provided two classifiers, <i>AZLists</i> based on <i>ex.Title</i> and <i>ex.Source</i> metadata. Remove both of these by selecting them in turn and clicking <<b>Remove Classifier</b>>.</Text> 715 715 </NumberedItem> 716 716 <NumberedItem> … … 763 763 </NumberedItem> 764 764 <NumberedItem> 765 <Text id="0330" funky="1">In order to view the documents properly we need to modify a format statement. In the <b>Format Features</b> section on the <b>Design</b> panel, select the <b>DocumentText</b> format statement. Replace:<Format>[Text]</Format></Text>765 <Text id="0330">In order to view the documents properly we need to modify a format statement. In the <b>Format Features</b> section on the <b>Design</b> panel, select the <b>DocumentText</b> format statement. Replace:<Format>[Text]</Format></Text> 766 766 <Text id="0331">with</Text> 767 767 <Format>[srcicon]</Format> 768 768 </NumberedItem> 769 769 <NumberedItem> 770 <Text id="0332"><b>Preview</b> the collection from the <b>Create</b> panel. (There is no need to build it). Images from the documents are now displayed instead of the extracted text. Both <i>No extractable text.pdf</i> and <i>Weird characters.pdf</i> display nicely now. 770 <Text id="0332"><b>Preview</b> the collection from the <b>Create</b> panel. (There is no need to build it). Images from the documents are now displayed instead of the extracted text. Both <i>No extractable text.pdf</i> and <i>Weird characters.pdf</i> display nicely now.</Text> 771 771 </NumberedItem> 772 772 <Heading> … … 774 774 </Heading> 775 775 <Comment> 776 <Text id="0334">The Librarian Interface can operate in different modes. So far, you have been using the default mode, called "Librarian." 776 <Text id="0334">The Librarian Interface can operate in different modes. So far, you have been using the default mode, called "Librarian."</Text> 777 777 </Comment> 778 778 <NumberedItem> … … 1011 1011 <Text id="0408">The necessary files for export are written to:</Text> 1012 1012 <Path>C:\Program Files\Greenstone\tmp\exported_Tudorcollection</Path> 1013 <Text id="0409">You need to use your own computer's software to write these on to CD-ROM. On Windows XP 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>1013 <Text id="0409">You need to use your own computer's software to write these on to CD-ROM. On Windows XP 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> 1014 1014 <Comment> 1015 1015 <Text id="0410">The result will be a self-installing Greenstone CD-ROM, which starts the installation process as soon as it is placed in the drive.</Text> … … 1210 1210 [/highlight]{If}{[ex.Source],<br><i>([ex.Source])</i>}</td> 1211 1211 </Format> 1212 <Text id="0469" funky="1">This displays</Text>1213 <Text id="0470">something that looks like this: 1212 <Text id="0469">This displays</Text> 1213 <Text id="0470">something that looks like this:</Text> 1214 1214 <Indent> 1215 1215 <table><tr><td><img width='15' height='20' src="tutorial_images/itext.gif"/></td><td width='408' valign='top'>A discussion of question five from Tudor Quiz: Henry VIII <br/><i>(quizstuff.html)</i></td></tr></table> … … 1229 1229 </td> 1230 1230 </Format> 1231 <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 1232 <Text id="0477">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. 1233 <Comment> 1234 <Text id="0478">But there's a problem. Beside the bookshelves in the hierarchy browser, beneath the subject appears a mysterious "() </Text>1235 <Text id="0479"> ". What is printed on these bookshelf nodes is governed by the same format statement, and though bookshelf nodes of the hierarchy have associated</Text>1236 <Text id="0480">Title metadata--their title is the name of the metadata value associated with that bookshelf--they do not have 1231 <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</Text> 1232 <Text id="0477">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> 1233 <Comment> 1234 <Text id="0478">But there's a problem. Beside the bookshelves in the hierarchy browser, beneath the subject appears a mysterious "()".</Text> 1235 <Text id="0479">What is printed on these bookshelf nodes is governed by the same format statement, and though bookshelf nodes of the hierarchy have associated</Text> 1236 <Text id="0480">Title metadata--their title is the name of the metadata value associated with that bookshelf--they do not have</Text> 1237 1237 <Text id="0481">ex.Source metadata, so it comes out blank.</Text> 1238 1238 </Comment> … … 1271 1271 <table><tr><td><img width='15' height='20' src="tutorial_images/itext.gif" /></td><td width='408' valign='top'>A discussion of question five from Tudor Quiz: Henry VIII <br/> 1272 1272 Tudor period|Others</td></tr></table> 1273 <Text id="0493">(The vertical bar appears because this <i>dc.Subject and Keywords</i> metadata is hierarchical metadata. Unfortunately there is no way to get at individual components of the hierarchy. For most metadata, such as title and author, this isn't a problem.) 1274 </NumberedItem> 1275 <NumberedItem> 1276 <Text id="0494">Finally, let's return to the <i>subjects</i> hierarchy and learn how to do different things to the bookshelves and to the documents themselves. In the <b>Choose Feature </b>menu, re-select the item 1273 <Text id="0493">(The vertical bar appears because this <i>dc.Subject and Keywords</i> metadata is hierarchical metadata. Unfortunately there is no way to get at individual components of the hierarchy. For most metadata, such as title and author, this isn't a problem.)</Text> 1274 </NumberedItem> 1275 <NumberedItem> 1276 <Text id="0494">Finally, let's return to the <i>subjects</i> hierarchy and learn how to do different things to the bookshelves and to the documents themselves. In the <b>Choose Feature </b>menu, re-select the item</Text> 1277 1277 <Indent> 1278 1278 CL2: Hierarchy -metadata dc.Subject and Keywords … … 1291 1291 </NumberedItem> 1292 1292 <NumberedItem> 1293 <Text id="0498">Go to the <b>Create </b>panel, click <<b>Preview</b>>, and examine the subject hierarchy again to see the effect of your changes. 1293 <Text id="0498">Go to the <b>Create </b>panel, click <<b>Preview</b>>, and examine the subject hierarchy again to see the effect of your changes.</Text> 1294 1294 </NumberedItem> 1295 1295 <Heading> … … 1297 1297 </Heading> 1298 1298 <Comment> 1299 <Text id="0500">The appearance of all pages produced by Greenstone is governed by macro files, which reside in the folder 1300 <Text id="0501">C:\Program Files\Greenstone\macros. The 1301 <Text id="0502">garish example collection is a version of the 1302 <Text id="0503">demo collection with bizarre layout and coloring. Now we apply the same bizarre layout and coloring to the 1299 <Text id="0500">The appearance of all pages produced by Greenstone is governed by macro files, which reside in the folder</Text> 1300 <Text id="0501">C:\Program Files\Greenstone\macros. The</Text> 1301 <Text id="0502">garish example collection is a version of the</Text> 1302 <Text id="0503">demo collection with bizarre layout and coloring. Now we apply the same bizarre layout and coloring to the</Text> 1303 1303 <Text id="0504">tudor collection.</Text> 1304 1304 </Comment> … … 1313 1313 </NumberedItem> 1314 1314 <Comment> 1315 <Text id="0508">A small but important enhancement to Greenstone has been made since the garish collection was written. Instead of using the 1316 <Text id="0509">[c=garish] macro argument to restrict the macros to apply to a certain collection, you can now put collection-specific macros in the 1317 <Text id="0510">macros directory of the collection, in a file called 1318 <Text id="0511">extra.dm. In fact, this is what you have just done. 1315 <Text id="0508">A small but important enhancement to Greenstone has been made since the garish collection was written. Instead of using the</Text> 1316 <Text id="0509">[c=garish] macro argument to restrict the macros to apply to a certain collection, you can now put collection-specific macros in the</Text> 1317 <Text id="0510">macros directory of the collection, in a file called</Text> 1318 <Text id="0511">extra.dm. In fact, this is what you have just done.</Text> 1319 1319 </Comment> 1320 1320 <Heading> … … 1328 1328 </NumberedItem> 1329 1329 <NumberedItem> 1330 <Text id="0515">Go to the folder <i>C:\Program Files\Greenstone\etc</i> and edit the file called <i>main.cfg</i>. This is Greenstone's main configuration file, and contains a list of the macros that will be loaded in on startup. One of them, <i>home.dm</i>, dictates how the Greenstone home page will look, which is specified in the file <i>C:\Program Files\Greenstone\macros\home.dm</i>. This <i>macros</i> folder contains an alternative version, called <i>yourhome.dm</i>, which is not currently being used. To use it instead, in <i>main.cfg</i> change the string <i>home.dm</i> to <i>yourhome.dm</i>. 1330 <Text id="0515">Go to the folder <i>C:\Program Files\Greenstone\etc</i> and edit the file called <i>main.cfg</i>. This is Greenstone's main configuration file, and contains a list of the macros that will be loaded in on startup. One of them, <i>home.dm</i>, dictates how the Greenstone home page will look, which is specified in the file <i>C:\Program Files\Greenstone\macros\home.dm</i>. This <i>macros</i> folder contains an alternative version, called <i>yourhome.dm</i>, which is not currently being used. To use it instead, in <i>main.cfg</i> change the string <i>home.dm</i> to <i>yourhome.dm</i>.</Text> 1331 1331 </NumberedItem> 1332 1332 <NumberedItem> … … 1337 1337 </NumberedItem> 1338 1338 <Comment> 1339 <Text id="0518">To learn how more about macros, read 1339 <Text id="0518">To learn how more about macros, read</Text> 1340 1340 <Text id="0519">Customizing the Greenstone User Interface, an illustrated guide to customizing the user interface, by Allison Zhang of the Washington Research Library Consortium, available at http://www.wrlc.org/dcpc/UserInterface/interface.htm.</Text> 1341 1341 </Comment> … … 1551 1551 [/highlight]{If}{[ex.Source],<br><i>([ex.Source])</i>}</td> 1552 1552 </Format> 1553 <Text id="0583">to this: 1553 <Text id="0583">to this:</Text> 1554 1554 <Format> 1555 1555 <td valign=top><br/> … … 1572 1572 <Text id="0589">Preview</Text> 1573 1573 </b> 1574 <Text id="0590"> the result. If 1574 <Text id="0590"> the result. If</Text> 1575 1575 <Text id="0591">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> 1576 1576 <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> … … 1661 1661 </Comment> 1662 1662 <Comment> 1663 <Text id="0618">In the next exercise we incorporate the MIDI files. Greenstone has no MIDI plugin (yet). But that doesn't mean you can't use MIDI files! We also clean up the 1663 <Text id="0618">In the next exercise we incorporate the MIDI files. Greenstone has no MIDI plugin (yet). But that doesn't mean you can't use MIDI files! We also clean up the</Text> 1664 1664 <Text id="0619">titles a-z</Text> 1665 1665 <Text id="0620"><b> </b>browser.<b></b></Text> … … 1722 1722 </Comment> 1723 1723 <Comment> 1724 <Text id="0640">One powerful use of regular expressions in the exercise was to clean up the 1724 <Text id="0640">One powerful use of regular expressions in the exercise was to clean up the</Text> 1725 1725 <Text id="0641">titles a-z</Text> 1726 1726 <Text id="0642"> browser. Perhaps the best way of doing this would be to have proper title metadata. The metadata extracted from HTML files is messy and inconsistent, and this was reflected in the original titles a-z browser. Defining proper title metadata would be simple but rather laborious. Instead, we have opted to use regular expressions in the AZCompactList classifier to clean up the title metadata. This is difficult to understand, and a bit fiddly to do, but if you can cope with its idiosyncrasies it provides a quick way to clean up the extracted metadata and avoid having to enter a large amount of metadata.</Text> … … 1853 1853 </NumberedItem> 1854 1854 <NumberedItem> 1855 <Text id="0678">Add <b>PagedImgPlug</b> and 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. 1855 <Text id="0678">Add <b>PagedImgPlug</b> and 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> 1856 1856 </NumberedItem> 1857 1857 <NumberedItem> … … 1865 1865 </NumberedItem> 1866 1866 <Comment> 1867 <Text id="0682">This collection was built with Greenstone's default settings. You can locate items of interest, but the information is less clearly and attractively presented than in the full Niupepa collection. 1867 <Text id="0682">This collection was built with Greenstone's default settings. You can locate items of interest, but the information is less clearly and attractively presented than in the full Niupepa collection.</Text> 1868 1868 </Comment> 1869 1869 <Heading> … … 1929 1929 <Content> 1930 1930 <Comment> 1931 <Text id="0703">This exercise explores service-level interoperability using the Open Archive Initiative Protocol for Metadata Harvesting (OAI-PMH). So that you can do this on a stand-alone computer, we do not actually connect to the external server that is acting as the data provider. Instead we have provided an appropriate set of files that take the form of XML records produced by the OAI-PMH protocol. 1931 <Text id="0703">This exercise explores service-level interoperability using the Open Archive Initiative Protocol for Metadata Harvesting (OAI-PMH). So that you can do this on a stand-alone computer, we do not actually connect to the external server that is acting as the data provider. Instead we have provided an appropriate set of files that take the form of XML records produced by the OAI-PMH protocol.</Text> 1932 1932 </Comment> 1933 1933 <Comment> … … 2003 2003 </NumberedItem> 2004 2004 <NumberedItem> 2005 <Text id="0727">Finally, you will have noticed that where the document itself should appear, you see only <i>This document has no text</i>. To rectify this, select <b>DocumentText</b> in the <b>Choose Feature</b> pull-down list and use the following as its format statement (which is currently blank) (this text is in 2005 <Text id="0727">Finally, you will have noticed that where the document itself should appear, you see only <i>This document has no text</i>. To rectify this, select <b>DocumentText</b> in the <b>Choose Feature</b> pull-down list and use the following as its format statement (which is currently blank) (this text is in</Text> 2006 2006 <Text id="0728"><i>doctxt_tweak.txt</i></Text> 2007 2007 <Text id="0729"> in the <i>format_tweaks</i> folder mentioned earlier):</Text>
Note:
See TracChangeset
for help on using the changeset viewer.