Changeset 11409
- Timestamp:
- 2006-03-20T09:13:07+12:00 (18 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/gsdl-documentation/tutorials/xml-source/tutorial_en.xml
r11406 r11409 387 387 </NumberedItem> 388 388 <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> 389 <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 below under <i>Updating a Greenstone installation</i>.</Text>389 <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> 390 390 <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> 391 391 <BulletList> … … 459 459 </Bullet> 460 460 </BulletList> 461 <Footnote id="foot1">462 <Text id="0796"> </Text>463 </Footnote>464 461 </Content> 465 462 </Tutorial> … … 709 706 </Heading> 710 707 <NumberedItem> 711 <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, NULPlug and ISISPlug 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>708 <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, ISISPlug 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> 712 709 </NumberedItem> 713 710 <Heading> … … 749 746 </NumberedItem> 750 747 <NumberedItem> 751 <Text id="0318">Now add an <i>AZCompactList</i> classifier. Click <<b>Add Classifier</b>> and configure it to use <i>dc.Creator</i> metadata, with button name "Creator". C heck the <b>mingroup</b> box and select 1 (to group all publications by the same author under a single bookshelf icon). Click <<b>OK</b>>.</Text>748 <Text id="0318">Now add an <i>AZCompactList</i> classifier. Click <<b>Add Classifier</b>> and configure it to use <i>dc.Creator</i> metadata, with button name "Creator". Click <<b>OK</b>>.</Text> 752 749 <Comment> 753 750 <Text id="0319">The last three sections are <b>Format Features</b>, <b>Translate Text</b> and <b>Metadata Sets</b>. In this exercise, we will not make any changes to these.</Text> … … 761 758 </NumberedItem> 762 759 <Comment> 763 <Text id="0322">At this point you might like to publish the collection on CD-ROM, See below under "Exporting a collection to CD-ROM"for how to do this.</Text>760 <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> 764 761 </Comment> 765 762 </Content> … … 869 866 </NumberedItem> 870 867 <Comment> 871 <Text id="0354">The <b> All Previous Values</b>box will become more useful when more entries have been added.</Text>868 <Text id="0354">The <b>Existing values for ...</b>box will become more useful when more entries have been added.</Text> 872 869 </Comment> 873 870 <NumberedItem> … … 899 896 </Comment> 900 897 <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>reload </b>in the web browser.</Text>898 <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> 902 899 </Comment> 903 900 <Heading> … … 926 923 </Comment> 927 924 <NumberedItem> 928 <Text id="0373">Back in the Librarian Interface enter the text <b>Moon rising over mountain landscape </b>as the <b>dc.Description </b>field's value and click <b>Enter</b> to have it added.</Text>925 <Text id="0373">Back in the Librarian Interface enter the text <b>Moon rising over mountain landscape </b>as the <b>dc.Description </b>field's value and click <b>Enter</b> to have it added.</Text> 929 926 </NumberedItem> 930 927 <NumberedItem> … … 1031 1028 <Content> 1032 1029 <Comment> 1033 <Text id="0404">To publish a collection on CD-ROM, Greenstone's Export to CD-ROM export module must be installed (see above, under "Installing Greenstone").</Text>1030 <Text id="0404">To publish a collection on CD-ROM, Greenstone's Export to CD-ROM export module must be installed (see <TutorialRef id="install_greenstone"/>).</Text> 1034 1031 </Comment> 1035 1032 <NumberedItem> … … 1137 1134 </NumberedItem> 1138 1135 <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> All Previous Values</b> area.</Text>1136 <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 dls.Subject and Keywords</b> area.</Text> 1140 1137 </NumberedItem> 1141 1138 <NumberedItem> … … 1146 1143 </NumberedItem> 1147 1144 <NumberedItem> 1148 <Text id="0442">A window pops up to control the classifier's options. Change the metadatato <i>dc.Subject</i> and then click <b><OK></b>.</Text>1145 <Text id="0442">A window pops up to control the classifier's options. Change the <b>metadata</b> to <i>dc.Subject</i> and then click <b><OK></b>.</Text> 1149 1146 </NumberedItem> 1150 1147 <NumberedItem> … … 1176 1173 </NumberedItem> 1177 1174 <NumberedItem> 1178 <Text id="0452">The search page includes a pulldown menu that allows you to select one of these partitions for searching. For example, try searching the <i>relatives</i> partition for <i>mary</i> .and then search the <i>monarchs</i> partition for the same thing.</Text>1175 <Text id="0452">The search page includes a pulldown menu that allows you to select one of these partitions for searching. For example, try searching the <i>relatives</i> partition for <i>mary</i> and then search the <i>monarchs</i> partition for the same thing.</Text> 1179 1176 </NumberedItem> 1180 1177 <NumberedItem> … … 1276 1273 </NumberedItem> 1277 1274 <NumberedItem> 1278 <Text id="0486">Now go to the <b>Create</b> panel and click <<b>Preview</b>>. First, the offending " <i>()</i>" has disappeared from the bookshelves. Second, when you get down to a list of documents in the subject hierarchy, the filename does not appear beside the title, because <i>ex.Source</i> is not specified in the format statement and this format statement applies to all nodes in the <i>subject</i> classifier. Note that the search results and titles lists have not changed: they still display the filename underneath the title.</Text>1275 <Text id="0486">Now go to the <b>Create</b> panel and click <<b>Preview</b>>. First, the offending "()" has disappeared from the bookshelves. Second, when you get down to a list of documents in the subject hierarchy, the filename does not appear beside the title, because <i>ex.Source</i> is not specified in the format statement and this format statement applies to all nodes in the <i>subject</i> classifier. Note that the search results and titles lists have not changed: they still display the filename underneath the title.</Text> 1279 1276 </NumberedItem> 1280 1277 <NumberedItem> … … 1289 1286 </NumberedItem> 1290 1287 <NumberedItem> 1291 <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 allthe 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>1288 <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> 1292 1289 </NumberedItem> 1293 1290 <NumberedItem> … … 1311 1308 <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> 1312 1309 <Comment> 1313 <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>1310 <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> 1314 1311 </Comment> 1315 1312 </NumberedItem> … … 1324 1321 </Comment> 1325 1322 <NumberedItem> 1326 <Text id="0505">Go to the folder < i>C:\Program Files\Greenstone\macros</i>. Copy the file <i>garish.dm</i> (do not <i>cut</i> it; it must remain in this folder, otherwise Greenstone will not start up). Now go to your collection folder <i>C:\Program Files\Greenstone\collect\tudor </i>and create a new folder in there called <i>macros</i>. Paste <i>garish.dm</i> into that new folder, and change its name to <i>extra.dm</i>. The overall effect is that you have created a new file <i>C:\Program Files\Greenstone\collect\ tudor\macros\extra.dm</i> with the contents of <i>garish.dm</i>. Make sure that the new file is called <i>extra.dm</i> and not <i>extra.dm.dm</i>, which Windows sometimes tends to do.</Text>1327 </NumberedItem> 1328 <NumberedItem> 1329 <Text id="050 6">Now edit this file <i>extra.dm</i> using WordPad or Notepad. Search for the string <i>[c=garish]</i> and remove this string wherever it appears. Lines starting with <i>#</i> are comment lines; you don't have to remove the string from these (though it won't do any harm). There are 11 other occurrences of <i>[c=garish]</i>: you must remove them all.</Text>1323 <Text id="0505">Go to the folder <Path>C:\Program Files\Greenstone\collect\garish\macros</Path>. Copy the file <i>extra.dm</i>. Now go to your collection folder <Path>C:\Program Files\Greenstone\collect\tudor</Path> and create a new folder in there called <i>macros</i>. Paste <i>extra.dm</i> into that new folder. The overall effect is that you have created a new file <Path>C:\Program Files\Greenstone\collect\tudor\macros\extra.dm</Path>.</Text> 1324 </NumberedItem> 1325 <NumberedItem> 1326 <Text id="0505a">This macro file uses a CSS style file and some images which you will also need to copy from the garish collection. Go to the folder <Path>C:\Program Files\Greenstone\collect\garish\images</Path>. Select the three files <i>style.css</i>, <i>horzline.gif</i> and <i>bg_blue.gif</i>. <b>Copy</b> these files and paste them into the <Path>C:\Program Files\Greenstone\collect\tudor\images</Path> folder.</Text> 1330 1327 </NumberedItem> 1331 1328 <NumberedItem> 1332 1329 <Text id="0507">Go to the <b>Create </b>panel and click <<b>Preview</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> 1333 1330 </NumberedItem> 1334 <Comment>1335 <Text id="0508">A small but important enhancement to Greenstone has been made since the garish collection was written. Instead of using the [c=garish] macro argument to restrict the macros to apply to a certain collection, you can now put collection-specific macros in the macros directory of the collection, in a file called extra.dm. In fact, this is what you have just done. </Text>1336 </Comment>1337 1331 <Heading> 1338 1332 <Text id="0512">General macros</Text> … … 1354 1348 </NumberedItem> 1355 1349 <Comment> 1356 <Text id="0518">To learn howmore about macros, read <i>Customizing the Greenstone User Interface</i>, an illustrated guide to customizing the user interface, by Allison Zhang of the Washington Research Library Consortium, available at <Link>http://www.wrlc.org/dcpc/UserInterface/interface.htm</Link>.</Text>1350 <Text id="0518">To learn more about macros, read <i>Customizing the Greenstone User Interface</i>, an illustrated guide to customizing the user interface, by Allison Zhang of the Washington Research Library Consortium, available at <Link>http://www.wrlc.org/dcpc/UserInterface/interface.htm</Link>.</Text> 1357 1351 </Comment> 1358 1352 </Content> … … 1366 1360 <Content> 1367 1361 <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. </Text>1362 <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> 1369 1363 </NumberedItem> 1370 1364 <NumberedItem> … … 1381 1375 </NumberedItem> 1382 1376 <NumberedItem> 1383 <Text id="0526">Add an <b>AZCompactList</b> classifier for the <b>Subject</b> metadata. Select this item from the relevant menu of the <b>Browsing Classifiers </b>section of the <b>Design</b> panel and click <b><Add Classifier></b>. In the popup window, select <b>ex.Subject </b>as the metadata item , activate the <b>mingroup</b> option and set its field to <b>1</b>.</Text>1384 <Comment> 1385 <Text id="0527"><b>AZCompactList</b> is like <b>AZList,</b> 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. Setting <b>mingroup</b> to 1 means that the bookshelf appears even when there is just one item, and is done here to provide a more uniform display.</Text>1377 <Text id="0526">Add an <b>AZCompactList</b> classifier for the <b>Subject</b> metadata. Select this item from the relevant menu of the <b>Browsing Classifiers </b>section of the <b>Design</b> panel and click <b><Add Classifier></b>. In the popup window, select <b>ex.Subject </b>as the metadata item.</Text> 1378 <Comment> 1379 <Text id="0527"><b>AZCompactList</b> is like <b>AZList,</b> 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> 1386 1380 </Comment> 1387 1381 </NumberedItem> … … 1454 1448 </NumberedItem> 1455 1449 <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 "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 belowthat this is possible but tricky.)</Text>1450 <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 1451 </NumberedItem> 1458 1452 <NumberedItem> … … 1480 1474 <Text id="0554">Copy the files provided in</Text> 1481 1475 <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 the<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>1476 <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 1477 </NumberedItem> 1484 1478 <NumberedItem> … … 1610 1604 </Bullet> 1611 1605 <Bullet> 1612 <Text id="0601">Activate <b>mingroup</b> and set it to 1. This gives a uniform appearance by creating a bookshelf for every title.</Text>1613 </Bullet>1614 <Bullet>1615 1606 <Text id="0602">Finish by pressing <<b>OK</b>>.</Text> 1616 1607 </Bullet> … … 1641 1632 </NumberedItem> 1642 1633 <NumberedItem> 1643 <Text id="0611">To suppress the dummy documents, change the <b>VList</b> format statement in the <b> Design</b> panel again by adding the two highlighted lines, and the close curly bracket:</Text>1634 <Text id="0611">To suppress the dummy documents, change the <b>VList</b> format statement in the <b>Format Features</b> section of the <b>Design</b> panel again by adding the two highlighted lines, and the close curly bracket:</Text> 1644 1635 <Format><td valign=top><br/> 1645 1636 {If}{[dc.Format] eq 'Audio',<br/> … … 1652 1643 </NumberedItem> 1653 1644 <NumberedItem> 1654 <Text id="0612"> Add a <b>Phind</b> browsing classifier that sources its phrases from <i>Title</i> and <i>text</i> (the default setting).</Text>1645 <Text id="0612">In the <b>Browsing Classifiers</b> section on the <b>Design</b> panel, add a <b>Phind</b> classifier. Leave the settings at their defaults: this generates a phrase browsing classifier that sources its phrases from <i>Title</i> and <i>text</i>.</Text> 1655 1646 </NumberedItem> 1656 1647 <NumberedItem> … … 1688 1679 <BulletList> 1689 1680 <Bullet> 1690 <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> All Previous Values</b> list. All files extracted from the Zip file inherit its settings.</Text>1681 <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> 1691 1682 </Bullet> 1692 1683 </BulletList> … … 1811 1802 </NumberedItem> 1812 1803 <NumberedItem> 1813 <Text id="0660">If you want to you can reverse the most recent change you made by commenting out the three new lines added (add #) and uncommenting the original three(delete # character). Remember to save the file. To undo all the customized changes made, delete the content of the <i>macros</i> and <i>images</i> folders.</Text>1804 <Text id="0660">If you want to you can reverse the most recent change you made by commenting out the new lines added (add #) and uncommenting the original lines (delete # character). Remember to save the file. To undo all the customized changes made, delete the content of the <i>macros</i> and <i>images</i> folders.</Text> 1814 1805 </NumberedItem> 1815 1806 <Heading> … … 1820 1811 <BulletList> 1821 1812 <Bullet> 1822 <Text id="0663">Close the current collection .</Text>1823 </Bullet> 1824 <Bullet> 1825 <Text id="0664">Start a new collection called <i>advbeat_large .</i></Text>1813 <Text id="0663">Close the current collection (<Menu>File-->Close</Menu>).</Text> 1814 </Bullet> 1815 <Bullet> 1816 <Text id="0664">Start a new collection called <i>advbeat_large</i> (<Menu>File-->New</Menu>).</Text> 1826 1817 </Bullet> 1827 1818 <Bullet> … … 1868 1859 </NumberedItem> 1869 1860 <NumberedItem> 1870 <Text id="0680">Some of the files you have just dragged in are text files that contain the text extracted from page images. We want these to be processed by <b>PagedImgPlug</b>, not <b>TEXTPlug</b>. Switch to the <b>Design</b> panel and delete <b>TEXTPlug</b>. While you are at it, you could tidy things up by deleting <b>HTMLPlug</b>, <b>EMAILPlug</b>, <b>PDFPlug</b>, <b>RTFPlug</b>, <b>WordPlug</b>, and <b>PSPlug</b> as well, since they will not be used.</Text>1861 <Text id="0680">Some of the files you have just dragged in are text files that contain the text extracted from page images. We want these to be processed by <b>PagedImgPlug</b>, not <b>TEXTPlug</b>. Switch to the <b>Design</b> panel and delete <b>TEXTPlug</b>. While you are at it, you could tidy things up by deleting <b>HTMLPlug</b>, <b>EMAILPlug</b>, <b>PDFPlug</b>, <b>RTFPlug</b>, <b>WordPlug</b>, <b>PSPlug</b>, <b>ISISPlug</b> and <b>NULPlug</b> as well, since they will not be used.</Text> 1871 1862 </NumberedItem> 1872 1863 <NumberedItem> … … 1909 1900 </Heading> 1910 1901 <Comment> 1911 <Text id="0695">When you reach a newspaper, only its associated text is displayed. When either of the Te Waka o Te Iwi newspapers is accessed, the document view presents the message This document has no text. No scanned image information (screen-view resolution or otherwise) is shown, even though it has been computed and stored with the document. This can be fixed by a format statement that modifies the default behaviour for DocumentText.</Text>1912 </Comment> 1913 <NumberedItem> 1914 <Text id="0696">Staying within the <b>Format Features</b> section of the <b>Design </b>panel, under "Choose Feature" select <b>DocumentText</b>. Its HTML format string is empty, triggering the default behaviour of displaying the document's plain text, or, if there is none,"This document has no text". Change this to:</Text>1902 <Text id="0695">When you reach a newspaper, only its associated text is displayed. When either of the Te Waka o Te Iwi newspapers is accessed, the document view presents the message "This document has no text". No scanned image information (screen-view resolution or otherwise) is shown, even though it has been computed and stored with the document. This can be fixed by a format statement that modifies the default behaviour for DocumentText.</Text> 1903 </Comment> 1904 <NumberedItem> 1905 <Text id="0696">Staying within the <b>Format Features</b> section of the <b>Design </b>panel, under "Choose Feature" select <b>DocumentText</b>. The default format string displays the document's plain text, which, if there is none, is set to "This document has no text". Change this to:</Text> 1915 1906 <Format> 1916 1907 <center><br/> … … 1963 1954 </NumberedItem> 1964 1955 <Comment> 1965 <Text id="0708">When files are copied across like this, the Librarian Interface studies each one and uses its filename extension to check whether the collection contains a corresponding plug-in. Up until now, the answer has always been yes, so all file transfers have proceeded without interruption. This time, however, no plug-in in the list is capable of processing the OAI file records that are copied across (they have the file extension .oai).</Text>1956 <Text id="0708">When files are copied across like this, the Librarian Interface studies each one and uses its filename extension to check whether the collection contains a corresponding plug-in. No plug-in in the list is capable of processing the OAI file records that are copied across (they have the file extension .oai), so the Librarian Interface prompts you to add the appropriate plug-in.</Text> 1966 1957 </Comment> 1967 1958 <Comment> … … 2182 2173 </NumberedItem> 2183 2174 <NumberedItem> 2184 <Text id="0779">Staying within the <b>Design</b> panel, select <b>Browsing Classifiers</b> and <b>delete</b> both <b>AZList</b> classifiers (<i>ex.Title </i>and <i>ex.Source</i>). Add an <b>AZList</b> classifier for <b>dc.Title</b> and an <b>AZCompactList</b> classifier for <b>dc.Contributor</b>. Check the <b>mingroup</b> box in this classifier and set its field to 1<b>.</b></Text>2175 <Text id="0779">Staying within the <b>Design</b> panel, select <b>Browsing Classifiers</b> and <b>delete</b> both <b>AZList</b> classifiers (<i>ex.Title </i>and <i>ex.Source</i>). Add an <b>AZList</b> classifier for <b>dc.Title</b> and an <b>AZCompactList</b> classifier for <b>dc.Contributor</b>.</Text> 2185 2176 </NumberedItem> 2186 2177 <NumberedItem> … … 2192 2183 <Text id="0782">Also, let's add a format statement for the classifier based on <b>dc.Contributor</b> metadata. In the <b>Choose Feature </b>menu (under <b>Format Features </b>on the <b>Design </b>panel), select the item that says:</Text> 2193 2184 <Indent> 2194 CL2: AZCompactList -metadata dc.Contributor -mingroup 12185 CL2: AZCompactList -metadata dc.Contributor 2195 2186 </Indent> 2196 2187 </NumberedItem> 2197 2188 <NumberedItem> 2198 <Text id="0783">Leave <b>VList</b> inthe <b>Affected Component</b> and edit the text in the <b>HTML Format String</b> box so that it looks like:</Text>2189 <Text id="0783">Leave <b>VList</b> as the <b>Affected Component</b> and edit the text in the <b>HTML Format String</b> box so that it looks like:</Text> 2199 2190 <Format> 2200 2191 <td valign=top>[link][icon][/link]</td><br/>
Note:
See TracChangeset
for help on using the changeset viewer.
