source: trunk/gsdl-documentation/manuals/xml-source/en/User_en.xml@ 14099

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE Manual [
    <!ENTITY chap_gli SYSTEM "help-en.xml">
]>

<Manual id="User" lang="en">
<Heading>
<Text id="1">GREENSTONE DIGITAL LIBRARY</Text>
</Heading>
<Title>
<Text id="2">USER'S GUIDE</Text>
</Title>
<Author>
<Text id="3">Ian H. Witten, Stefan Boddie and John Thompson</Text>
</Author>
<Affiliation>
<Text id="4">Department of Computer Science <br/>University of Waikato, New Zealand</Text>
</Affiliation>
<SupplementaryText>
<Text id="manual_index">Back to manual index</Text>
<Text id="top_index">Back to top index</Text>
</SupplementaryText>
<Text id="5">Greenstone is a suite of software for building and distributing digital library collections. It provides a new way of organizing information and publishing it on the Internet or on CD-ROM. Greenstone is produced by the New Zealand Digital Library Project at the University of Waikato, and developed and distributed in cooperation with UNESCO and the Human Info NGO. It is open-source software, available from <i>http://greenstone.org</i> under the terms of the Gnu General Public License.</Text>
<Comment>
<Text id="6">We want to ensure that this software works well for you. Please report any problems to <i>[email protected]</i></Text>
</Comment>
<Version>
<Text id="7">Greenstone gsdl-2.70</Text>
</Version>
<Date>
<Text id="8">March 2006</Text>
</Date>
<Section id="about_this_manual">
<Title>
<Text id="9">About this manual</Text>
</Title>
<Content>
<Text id="10">This manual provides a comprehensive description of how to use the Greenstone software for accessing and building digital library collections.</Text>
<Text id="11">Section <CrossRef target="Chapter" ref="overview_of_greenstone"/> gives an overview of the capabilities of the software. Section <CrossRef target="Chapter" ref="using_greenstone_collections"/> explains how to use Greenstone collections. The interface is self-explanatory—the best way to learn is by doingand this section comprises the on-line help information for a typical collection. Section <CrossRef target="Chapter" ref="making_greenstone_collections"/> explains how to build your own library collections using the Greenstone Librarian Interface. Section <CrossRef target="Chapter" ref="administration"/> introduces the administration facility that allows the system administrator to monitor what is going on and control who can build collections.</Text>
<Text id="12">Appendices list the features of the Greenstone software, and give a glossary of terms used throughout the Greenstone documentation.</Text>
</Content>
</Section>
<Section id="companion_documents">
<Title>
<Text id="13">Companion documents</Text>
</Title>
<Content>
<Text id="14">The complete set of Greenstone documents includes four volumes:</Text>
<BulletList>
<Bullet>
<Text id="15">Greenstone Digital Library Installer's Guide</Text>
</Bullet>
<Bullet>
<Text id="16">Greenstone Digital Library User's Guide <i>(this document)</i></Text>
</Bullet>
<Bullet>
<Text id="17">Greenstone Digital Library Developer's Guide</Text>
</Bullet>
<Bullet>
<Text id="18">Greenstone Digital Library: From Paper to Collection</Text>
</Bullet>
</BulletList>
</Content>
</Section>
<Section id="copyright">
<Title>
<Text id="copyright-title">Copyright</Text>
</Title>
<Content>
<Text id="right-text-1">Copyright 2002 2003 2004 2005 2006 2007 by the <Link url="http://www.nzdl.org">New Zealand Digital Library Project</Link> at <Link url="http://www.waikato.ac.nz">the University of Waikato</Link>, New Zealand.</Text>
<Text id="right-text-2">Permission is granted to copy, distribute and/or modify this document under the terms of the <Link url="http://www.gnu.org/licenses/fdl.html">GNU Free Documentation License</Link>, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled <Link url="http://greenstonewiki.cs.waikato.ac.nz/wiki/gsdoc/GNUFDL.html">“GNU Free Documentation License.”</Link></Text>
</Content>
</Section>
<Section id="acknowledgements">
<Title>
<Text id="19">Acknowledgements</Text>
</Title>
<Content>
<Text id="20">The Greenstone software is a collaborative effort between manypeople. Rodger McNab and Stefan Boddie are the principal architects andimplementors. Contributions have been made by David Bainbridge, GeorgeBuchanan, Hong Chen, Michael Dewsnip, Katherine Don, Elke Duncker, Carl Gutwin, Geoff Holmes, Dana McKay, JohnMcPherson, Craig Nevill-Manning, Dynal Patel, Gordon Paynter, Bernhard Pfahringer, ToddReed, Bill Rogers, John Thompson, and Stuart Yeates. Other members of the New ZealandDigital Library project provided advice and inspiration in the design ofthe system: Mark Apperley, Sally Jo Cunningham, Matt Jones, Steve Jones, Te TakaKeegan, Michel Loots, Malika Mahoui, Gary Marsden, Dave Nichols and Lloyd Smith. We would also like toacknowledge all those who have contributed to the GNU-licensed packagesincluded in this distribution: MG, GDBM, PDFTOHTML, PERL, WGET, WVWARE and XLHTML.</Text>
</Content>
</Section>
<Chapter id="overview_of_greenstone">
<Title>
<Text id="21">Overview of Greenstone</Text>
</Title>
<Content>
<Text id="22">Greenstone is a comprehensive system for constructing and presenting collections of thousands or millions of documents, including text, images, audio and video.</Text>
<Section id="collections">
<Title>
<Text id="23">Collections</Text>
</Title>
<Content>
<Text id="24">A typical digital library built with Greenstone will contain many collections, individually organized—though they bear a strong family resemblance. Easily maintained, collections can be augmented and rebuilt automatically.</Text>
<Text id="25">There are several ways to find information in most Greenstone collections. For example, you can <i>search for particular words</i> that appear in the text, or within a section of a document. You can <i>browse documents by title</i>: just click on a book to read it. You can <i>browse documents by subject</i>. Subjects are represented by bookshelves: just click on a bookshelf to look at the books. Where appropriate, documents come complete with a table of contents: you can click on a chapter or subsection to open it, expand the full table of contents, or expand the full document into your browser window (useful for printing). The New Zealand Digital Library website (<i>nzdl.org</i>) provides numerous example collections.</Text>
<Text id="26">On the front page of each collection is a statement of its purpose and coverage, and an explanation of how the collection is organized. Most collections can be accessed by both <i>searching</i> and <i>browsing</i>. When searching, the Greenstone software looks through the entire text of all documents in the collection (this is called “full-text search”). In most collections the user can choose between indexes built from different parts of the documents. Some collections have an index of full documents, an index of paragraphs, and an index of titles, each of which can be searched for particular words or phrases. Using these you can find all documents that contain a particular set of words (the words may be scattered far and wide throughout the document), or all paragraphs that contain the set of words (which must all appear in the same paragraph), or all documents whose titles contain the words (the words must all appear in the document's title). There might be other indexes, perhaps an index of sections, and an index of section headings. Browsing involves lists that the user can examine: lists of authors, lists of titles, lists of dates, hierarchical classification structures, and so on. Different collections offer different browsing facilities.</Text>
</Content>
</Section>
<Section id="finding_information">
<Title>
<Text id="27">Finding information</Text>
</Title>
<Content>
<Text id="28">Greenstone constructs full-text indexes from the document text—that is, indexes that enable searching on any words in the full text of the document. Indexes can be searched for particular words, combinations of words, or phrases, and results are ordered according to how relevant they are to the query.</Text>
<Text id="29">In most collections, descriptive data such as author, title, date, keywords, and so on, is associated with each document. This information is called <i>metadata</i>. Many document collections also contain full-text indexes of certain kinds of metadata. For example, many collections have a searchable index of document titles.</Text>
<Text id="30">Users can browse interactively around lists, and hierarchical structures, that are generated from the metadata that is associated with each document in the collection. Metadata forms the raw material for browsing. It must be provided explicitly or be derivable automatically from the documents themselves. Different collections offer different searching and browsing facilities. Indexes for both searching and browsing are constructed during a “building” process, according to information in a collection configuration file.</Text>
<Text id="31">Greenstone creates all index structures automatically from the documents and suppporting files: nothing is done manually. If new documents in the same format become available, they can be merged into the collection automatically. Indeed, for many collections this is done by processes that awake regularly, scout for new material, and rebuild the indexes—all without manual intervention.</Text>
</Content>
</Section>
<Section id="document_formats">
<Title>
<Text id="32">Document formats</Text>
</Title>
<Content>
<Text id="33">Source documents come in a variety of formats, and are converted into a standard XML form for indexing by “plugins.” Plugins distributed with Greenstone process plain text, HTML, WORD and PDF documents, and Usenet and E-mail messages. New ones can be written for different document types (to do this you need to study the <i>Greenstone Digital Library Developer's Guide</i>). To build browsing structures from metadata, an analogous scheme of “classifiers” is used. These create browsing indexes of various kinds: scrollable lists, alphabetic selectors, dates, and arbitrary hierarchies. Again, Greenstone programmers can create new browsing structures.</Text>
</Content>
</Section>
<Section id="multimedia_and_multilingual_documents">
<Title>
<Text id="34">Multimedia and multilingual documents</Text>
</Title>
<Content>
<Text id="35">Collections can contain text, pictures, audio and video. Non-textual material is either linked into the textual documents or accompanied by textual descriptions (such as figure captions) to allow full-text searching and browsing.</Text>
<Text id="36">Unicode, which is a standard scheme for representing the character sets used in the world's languages, is used throughout Greenstone. This allows any language to be processed and displayed in a consistent manner. Collections have been built containing Arabic, Chinese, English, French, M 0Å
 1ori and Spanish. Multilingual collections embody automatic language recognition, and the interface is available in all the above languages (and more).</Text>
</Content>
</Section>
<Section id="distributing_greenstone">
<Title>
<Text id="37">Distributing Greenstone</Text>
</Title>
<Content>
<Text id="38">Collections are accessed over the Internet or published, in precisely the same form, on a self-installing Windows CD-ROM. Compression is used to compact the text and indexes. A Corba protocol supports distributed collections and graphical query interfaces.</Text>
<Text id="39">The New Zealand Digital Library (<i>nzdl.org</i>) provides many example collections, including historical documents, humanitarian and development information, technical reports and bibliographies, literary works, and magazines.</Text>
<Text id="40">Being open source, Greenstone is readily extensible, and benefits from the inclusion of Gnu-licensed modules for full-text retrieval, database management, and text extraction from proprietary document formats. Only through international cooperative efforts will digital library software become sufficiently comprehensive to meet the world's needs with the richness and flexibility that users deserve.</Text>
</Content>
</Section>
</Content>
</Chapter>
<Chapter id="using_greenstone_collections">
<Title>
<Text id="41">Using Greenstone Collections</Text>
</Title>
<Content>
<Text id="42">The Greenstone software is designed to be easy to use. Web-based and CD-ROM collections have interfaces that are identical. Installing the Greenstone software from CD-ROM on any Windows or Linux computer is very easy indeed; a standard installation setup program is used in conjunction with pre-compiled binaries. A collection can be used locally on the computer where it is installed; also, if this computer is connected to a network, the software automatically and transparently allows all other computers on the network to access the same collection.</Text>
<Text id="43">The next section describes how to install a Greenstone CD-ROM. Then we look at the searching and browsing facilities offered by a typical Greenstone collection, the “Demo” collection that is supplied with the Greenstone software. Other collections offer similar facilities; if you can use one, you can use them all. The following section explains how to customize the interface for your own requirements using the Preferences page.</Text>
<Section id="using_a_greenstone_cd-rom">
<Title>
<Text id="44">Using a Greenstone CD-ROM</Text>
</Title>
<Content>
<Text id="45">The Greenstone digital library software itself comes on a CD-ROM, and you or your system manager have probably installed it on your system, following the instructions in the <i>Greenstone Digital Library Installer's Guide.</i> If so, Greenstone is already installed on your computer and you should skip the rest of this section.</Text>
<Text id="46">Some Greenstone collections come on a self-contained Greenstone CD-ROM that includes enough of the software to run just that collection. To use it, simply put it into the CD-ROM drive on any Windows PC. Most likely (if “autorun” is enabled on your PC), a window will appear inviting you to install the Greenstone software. If not, find the CD-ROM disk drive (on current Windows systems you can get this by clicking on the <i>My Computer</i> icon on the desktop) and double-click it, then the <i>Setup.exe</i> file inside it. The Greenstone <i>Setup</i> program will be entered, which guides you through the setup procedure. Most people respond <i>yes</i> to all the questions.</Text>
<Text id="47">When the installation procedure has finished, you'll find the library in the <i>Programs</i> submenu of the Windows <i>Start</i> menu, under the name of the collection (for example, “Development Library” or “United Nations University”).</Text>
<Text id="48">Once the software has been installed, the library will be entered automatically every time you re-insert the CD-ROM if autorun is enabled.</Text>
</Content>
</Section>
<Section id="finding_information_1">
<Title>
<Text id="49">Finding information</Text>
</Title>
<Content>
<Text id="50">The easiest way to learn how to use a Greenstone collection is to try it out. Don't worry—you can't break anything. Click liberally: most images that appear on the screen are clickable. If you hold the mouse stationary over an image, most browsers will soon pop up a message that tells you what will happen if you click.</Text>
<Text id="51">Experiment! Choose common words like “the” and “and” to search for—that should evoke some responses, and nothing will break.</Text>
<Text id="52">Greenstone digital library systems usually comprise several separate collections—for example, computer science technical reports, literary works, internet FAQs, magazines. There will be a home page for the digital library system which allows you to access any publicly-accessible collection; in addition, each collection has its own “about” page that gives you information about how the collection is organized and the principles governing what is included in it. To get back to the “about” page at any time, just click on the “collection” icon that appears at the top left side of all searching and browsing pages.</Text>
<Text id="53">Figure <CrossRef target="Figure" ref="using_the_demo_collection"/> shows a screenshot of the “Demo” collection supplied with the Greenstone software, which is a very small subset of the Development Library collection; we will use it as an example to describe the different ways of finding information. (If you can't find the Demo collection, use the Development Library instead; it looks just the same.) First, almost all icons are clickable. Several icons appear at the top of almost every page; Table <CrossRef target="Table" ref="what_the_icons_at_the_top_of_each_page_mean"/> shows you what they mean.</Text>
<Figure id="using_the_demo_collection">
<Title>
<Text id="54">Using the Demo collection</Text>
</Title>
<File width="397" height="286" url="images/User_Fig_1.png"/>
</Figure>
<Table id="what_the_icons_at_the_top_of_each_page_mean">
<Title>
<Text id="55">What the icons at the top of each page mean</Text>
</Title>
<TableContent>
<tr>
<th width="132">
<File width="68" height="32" url="images/User_Icon_1.png"/>
</th>
<th width="397">
<Text id="56">This takes you to the “about” page</Text>
</th>
</tr>
<tr>
<th width="132">
<File width="36" height="16" url="images/User_Icon_2.png"/>
</th>
<th width="397">
<Text id="57">This takes you to the Digital Library's home page, from which you can select another collection</Text>
</th>
</tr>
<tr>
<th width="132">
<File width="29" height="16" url="images/User_Icon_3.png"/>
</th>
<th width="397">
<Text id="58">This provides help text similar to what you are reading now</Text>
</th>
</tr>
<tr>
<th width="132">
<File width="70" height="16" url="images/User_Icon_4.png"/>
</th>
<th width="397">
<Text id="59">This allows you to set some user interface and searching options that will then be used henceforth</Text>
</th>
</tr>
</TableContent>
</Table>
<Text id="60">The “<i>search 
 subjects 
 titles a-z 
 organization 
 how to</i>” bar underneath gives access to the searching and browsing facilities. The leftmost button is for searching, and the ones to the right of it—four, in this collection—evoke different browsing facilities. These last four may differ from one collection to another.</Text>
<Subsection id="how_to_find_information">
<Title>
<Text id="61">How to find information</Text>
</Title>
<Content>
<Text id="62">Table <CrossRef target="Table" ref="table_icons_on_the_search_browse_bar"/> shows the five ways to find information in the Demo collection.</Text>
<Table id="table_icons_on_the_search_browse_bar">
<Title>
<Text id="63">What the icons on the search/browse bar mean</Text>
</Title>
<TableContent>
<tr>
<th width="123">
<File width="61" height="11" url="images/User_Icon_5.png"/>
</th>
<th width="407">
<Text id="64">Search for particular words</Text>
</th>
</tr>
<tr>
<th width="123">
<File width="58" height="11" url="images/User_Icon_6.png"/>
</th>
<th width="407">
<Text id="65">Access publications by subject</Text>
</th>
</tr>
<tr>
<th width="123">
<File width="58" height="11" url="images/User_Icon_7.png"/>
</th>
<th width="407">
<Text id="66">Access publications by title</Text>
</th>
</tr>
<tr>
<th width="123">
<File width="71" height="11" url="images/User_Icon_8.png"/>
</th>
<th width="407">
<Text id="67">Access publications by organization</Text>
</th>
</tr>
<tr>
<th width="123">
<File width="58" height="11" url="images/User_Icon_9.png"/>
</th>
<th width="407">
<Text id="68">Access publications by “how to” listing</Text>
</th>
</tr>
</TableContent>
</Table>
<Text id="69">You can <i>search for particular words</i> that appear in the text from the “search” page. (This is just like the “about” page shown in Figure <CrossRef target="Figure" ref="using_the_demo_collection"/>, except that it doesn't contain the <i>about this collection</i> text.) The search page can be reached from other pages by pressing the <i>search</i> button. You can <i>access publications by subject</i> by pressing the <i>subjects</i> button. This brings up a list of subjects, represented by bookshelves that can be further expanded by clicking on them. You can <i>access publications by title</i> by pressing the <i>titles a-z</i> button. This brings up a list of books in alphabetic order. You can <i>access publications by organization</i> by pressing the <i>organization</i> button. This brings up a list of organizations. You can <i>access publications by how to listing</i> by pressing the <i>how to</i> button. This brings up a list of “how to” hints. All these buttons are visible in Figure <CrossRef target="Figure" ref="using_the_demo_collection"/>.</Text>
</Content>
</Subsection>
<Subsection id="how_to_read_the_documents">
<Title>
<Text id="70">How to read the documents</Text>
</Title>
<Content>
<Text id="71">In the Demo collection, you can tell when you have arrived at an individual book because there is a photograph of its front cover (Figure <CrossRef target="Figure" ref="a_book_in_the_demo_collection"/>). Beside the photograph is a table of contents: the entry in bold face marks where you are, in this case <i>Introduction and Summary</i> —Section 1 of the chosen book. This table is expandable: click on the folders to open them or close them. Click on the open book at the top to close it.</Text>
<Text id="72">Underneath is the text of the current section (“The international demand for tropical butterflies 
” in the example, beginning at the very bottom of the illustration). When you have read through it, there are arrows at the end to take you on to the next section or back to the previous one.</Text>
<Text id="73">Below the photograph are four buttons. Click on <i>detach</i> to make a new browser window for this book. (This is useful if you want to compare books, or read two at once.) If you have reached this book through a search, the search terms will be highlighted: the <i>no highlighting</i> button turns this off. Click on <i>expand text</i> to expand out the whole text of the current section, or book. Click on <i>expand contents</i> to expand out the whole table of contents so that you can see the titles of all chapters and subsections.</Text>
<Text id="74">In some collections, the documents do not have this kind of hierarchical structure. In this case, no table of contents is displayed when you get to an individual document—just the document text. In some cases, the document is split into pages, and you can read sequentially or jump about from one page to another.</Text>
<Figure id="a_book_in_the_demo_collection">
<Title>
<Text id="75">A book in the Demo collection</Text>
</Title>
<File width="397" height="476" url="images/User_Fig_2.png"/>
</Figure>
</Content>
</Subsection>
<Subsection id="what_the_icons_mean">
<Title>
<Text id="76">What the icons mean</Text>
</Title>
<Content>
<Text id="77">When you are browsing around the collection, you will encounter the items shown in Table <CrossRef target="Table" ref="table_icons_that_you_will_encounter_when_browsing"/>.</Text>
</Content>
</Subsection>
<Subsection id="how_to_search_for_particular_words">
<Title>
<Text id="78">How to search for particular words</Text>
</Title>
<Content>
<Text id="79">From the search page, follow these simple steps to make a query:</Text>
<BulletList>
<Bullet>
<Text id="80">Specify what units you want to search: in the Demo collection you can search section titles or the full text of the books.</Text>
</Bullet>
<Bullet>
<Text id="81">Say whether you want to search for all or just some of the words</Text>
</Bullet>
<Bullet>
<Text id="82">Type in the words you want to search for into the query box</Text>
</Bullet>
<Bullet>
<Text id="83">Click the <i>Begin Search</i> button</Text>
</Bullet>
</BulletList>
<Text id="84">When you make a query, the titles of up to twenty matching documents will be shown. There is a button at the end to take you on to the next twenty. From there you will find buttons to take you on to the third twenty or back to the first twenty, and so on. However, for efficiency reasons a maximum of 100 is imposed on the number of documents returned. You can change these numbers by clicking the <i>preferences</i> button at the top of the page.</Text>
<Table id="table_icons_that_you_will_encounter_when_browsing">
<Title>
<Text id="85">Icons that you will encounter when browsing</Text>
</Title>
<TableContent>
<tr>
<th width="123">
<File width="19" height="12" url="images/User_Icon_10.png"/>
</th>
<th width="407">
<Text id="86">Click on a book icon to read the corresponding book</Text>
</th>
</tr>
<tr>
<th width="123">
<File width="22" height="17" url="images/User_Icon_11.png"/>
</th>
<th width="407">
<Text id="87">Click on a bookshelf icon to look at books on that subject</Text>
</th>
</tr>
<tr>
<th width="123">
<File width="25" height="16" url="images/User_Icon_12.png"/>
</th>
<th width="407">
<Text id="88">View this document</Text>
</th>
</tr>
<tr>
<th width="123">
<File width="25" height="16" url="images/User_Icon_13.png"/>
</th>
<th width="407">
<Text id="89">Open this folder and view contents</Text>
</th>
</tr>
<tr>
<th width="123">
<File width="29" height="25" url="images/User_Icon_14.png"/>
</th>
<th width="407">
<Text id="90">Click on this icon to close the book</Text>
</th>
</tr>
<tr>
<th width="123">
<File width="25" height="17" url="images/User_Icon_15.png"/>
</th>
<th width="407">
<Text id="91">Click on this icon to close the folder</Text>
</th>
</tr>
<tr>
<th width="123">
<File width="32" height="17" url="images/User_Icon_16.gif"/>
</th>
<th width="407">
<Text id="92">Click on the arrow to go on to the next section ...</Text>
</th>
</tr>
<tr>
<th width="123">
<File width="32" height="17" url="images/User_Icon_17.gif"/>
</th>
<th width="407">
<Text id="93">... or back to the previous section</Text>
</th>
</tr>
<tr>
<th width="123">
<File width="49" height="31" url="images/User_Icon_18.png"/>
</th>
<th width="407">
<Text id="94">Open this page in a new window</Text>
</th>
</tr>
<tr>
<th width="123">
<File width="61" height="32" url="images/User_Icon_19.png"/>
</th>
<th width="407">
<Text id="95">Expand table of contents</Text>
</th>
</tr>
<tr>
<th width="123">
<File width="48" height="32" url="images/User_Icon_20.png"/>
</th>
<th width="407">
<Text id="96">Display all text</Text>
</th>
</tr>
<tr>
<th width="123">
<File width="55" height="31" url="images/User_Icon_21.png"/>
</th>
<th width="407">
<Text id="97">Highlight search terms</Text>
</th>
</tr>
</TableContent>
</Table>
<Text id="98">Click the title of any document, or the little icon beside it, to open it. The icon may show a book, or a folder, or a page: it will be a book icon if you are searching books; otherwise if you are searching sections it will be a folder or page icon depending on whether or not the section found has subsections.</Text>
<Part id="search_terms">
<Title>
<Text id="99"><b><i>Search terms</i></b></Text>
</Title>
<Content>
<Text id="100">Whatever you type into the query box is interpreted as a list of words called “search terms.” Each search term contains nothing but alphabetic characters and digits. Terms are separated by white space. If any other characters such as punctuation appear, they serve to separate terms just as though they were spaces. And then they are ignored. You can't search for words that include punctuation.</Text>
<Text id="101">For example, the query</Text>
<Text type="code" id="102">Agro-forestry in the Pacific Islands: Systems for Sustainability (1993)</Text>
<Text id="103">will be treated the same as</Text>
<Text type="code" id="104">Agro forestry in the Pacific Islands Systems for Sustainability 1993</Text>
</Content>
</Part>
<Part id="query_type">
<Title>
<Text id="105"><b><i>Query type</i></b></Text>
</Title>
<Content>
<Text id="106">There are two different kinds of query.</Text>
<BulletList>
<Bullet>
<Text id="107">Queries for all the words. These look for documents (or chapters, or titles) that contain all the words you have specified. Documents that satisfy the query are displayed.</Text>
</Bullet>
<Bullet>
<Text id="108">Queries for some of the words. Just list some terms that are likely to appear in the documents you are looking for. Documents are displayed in order of how closely they match the query. When determining the degree of match,</Text>
<BulletList>
<Bullet>
<Text id="109">the more search terms a document contains, the closer it matches;</Text>
</Bullet>
<Bullet>
<Text id="110">rare terms are more important than common ones;</Text>
</Bullet>
<Bullet>
<Text id="111">short documents match better than long ones.</Text>
</Bullet>
</BulletList>
</Bullet>
</BulletList>
</Content>
</Part>
<Text id="112">Use as many search terms as you like—a whole sentence, or even a whole paragraph. If you specify only one term, it doesn't much matter whether you use an <i>all</i> or a <i>some</i> query, except that in the second case the results will be sorted by the search term's frequency of occurrence.</Text>
</Content>
</Subsection>
<Subsection id="scope_of_queries">
<Title>
<Text id="113">Scope of queries</Text>
</Title>
<Content>
<Text id="114">In most collections you can choose different indexes to search. For example, there might be author or title indexes. Or there might be chapter or paragraph indexes. Generally, the full matching document is returned regardless of which index you search.</Text>
<Text id="115">If documents are books, they will be opened at the appropriate place.</Text>
</Content>
</Subsection>
<Subsection id="advanced_search_features">
<Title>
<Text id="116">Advanced search features</Text>
</Title>
<Content>
<Text id="117">While the above is enough to meet most searching needs, some more advanced search features are provided. These are activated from the Preferences page, which is reached by clicking the <i>preferences</i> button at the top of the page—see Section <CrossRef target="Section" ref="changing_the_preferences"/> below. After changing your preferences, do not click your browser's <i>Back</i> button—that would undo the changes. Instead, click any of the buttons on the search/browse bar.</Text>
<Part id="case_sensitivity_and_stemming">
<Title>
<Text id="118"><i><b>Case sensitivity and stemming</b></i></Text>
</Title>
<Content>
<Text id="119">When you specify search terms, you can choose whether upper and lower case must match between the query and the document: this is called “case sensitivity.” You can also choose whether to ignore word endings or not: this is called “stemming.”</Text>
<Text id="120">Under <i>Search options</i> on the Preferences page you will see a pair of buttons labeled <i>ignore case differences</i> and <i>upper/lower case must match</i>; these control the case sensitivity of your queries. Below is a pair of buttons labeled <i>ignore word endings</i> and <i>whole word must match</i>: these control stemming.</Text>
<Text id="121">For example, if the buttons <i>ignore case differences</i> and <i>ignore word endings</i> are selected, the query</Text>
<Text type="code" id="122">African building</Text>
<Text id="123">will be treated the same as</Text>
<Text type="code" id="124">africa builds</Text>
<Text id="125">because the uppercase letter in “African” will be transformed to lowercase, and the suffixes “n” and “ing” will be removed from “African” and “building” respectively (also, “s” would be removed from “builds”).</Text>
<Text id="126">Generally case differences and word endings should be ignored unless you are querying for particular names or acronyms.</Text>
</Content>
</Part>
<Part id="phrase_searching">
<Title>
<Text id="127"><b><i>Phrase searching</i></b></Text>
</Title>
<Content>
<Text id="128">If your query includes a phrase in quotation marks, only documents containing that phrase, exactly as typed, will be returned.</Text>
<Text id="129">If you want to use phrase searching, you need to learn a little about how it works. Phrases are processed by a post-retrieval scan. First the query is issued in the normal way—all the words in the phrase are included as search terms—and then the documents returned are scanned to eliminate those in which that phrase does not appear.</Text>
<Text id="130">During the post-retrieval scan, phrases are checked just as they are, including any punctuation. For example, the query</Text>
<Text type="code" id="131">what's a “post-retrieval scan?”</Text>
<Text id="132">will first retrieve all documents that match all of the words</Text>
<CodeLine>what s a post retrieval scan</CodeLine>
<Text id="133">and then the documents returned will be checked for the phrase</Text>
<Text type="code" id="134">post-retrieval scan?</Text>
<Text id="135">Phrase matches are case-insensitive if <i>ignore case differences</i> is set on the Preferences page.</Text>
</Content>
</Part>
<Part id="advanced_query_mode">
<Title>
<Text id="136"><b><i>Advanced query mode</i></b></Text>
</Title>
<Content>
<Text id="137">In <i>advanced query mode</i>, which can be selected on the Preferences page, the queries for <i>all</i> of the words, described above, are actually Boolean queries. They consist of a list of terms joined by logical operators &amp; (and), | (or), and ! (not). Absent operatorsbetween search terms are interpreted as &amp; (and): thus a query without any operators returns documents that match <i>all</i> the terms.</Text>
<Text id="138">If the words AND, OR, and NOT appear in your query they are treated as ordinary search terms, not operators. For operators you must use &amp;, |, and !. In addition, parentheses can be used for grouping.</Text>
</Content>
</Part>
<Part id="using_search_history">
<Title>
<Text id="139"><b><i>Using search history</i></b></Text>
</Title>
<Content>
<Text id="140">When you switch on the “search history” feature on the Preferences page you will be shown your last few searches, along with a summary of how many results they generated. Click the button beside one of the previous searches to copy the text into the search box. This makes it easy to repeat slightly modified versions of previous queries.</Text>
</Content>
</Part>
</Content>
</Subsection>
</Content>
</Section>
<Section id="changing_the_preferences">
<Title>
<Text id="141">Changing the preferences</Text>
</Title>
<Content>
<Figure id="the_preferences_page">
<Title>
<Text id="142">The Preferences page</Text>
</Title>
<File width="394" height="439" url="images/User_Fig_3.png"/>
</Figure>
<Text id="143">When you click the <i>preferences</i> button at the top of the page you will be able to change some features of the interface to suit your own requirements. The preferences depend on the collection; an example is shown in Figure <CrossRef target="Figure" ref="the_preferences_page"/>. When you adjust your search preferences, you should press the <i>set preferences</i> button shown in Figure <CrossRef target="Figure" ref="the_preferences_page"/>. After setting preferences, do not use your browser's “back” button—that would unset them! Instead, click one of the buttons on the access bar near the top of the page.</Text>
<Subsection id="collection_preferences">
<Title>
<Text id="144">Collection preferences</Text>
</Title>
<Content>
<Text id="145">Some collections comprise several subcollections, which can be searched independently or together, as one unit. If so, you can select which subcollections to include in your searches on the Preferences page.</Text>
</Content>
</Subsection>
<Subsection id="language_preferences">
<Title>
<Text id="146">Language preferences</Text>
</Title>
<Content>
<Text id="147">Each collection has a default presentation language, but you can switch to a different language if you like. You can also alter the encoding scheme used by Greenstone for output to the browser—the software chooses sensible defaults, but with some browsers better visual results can be used by switching to a different encoding scheme. All collections allow you to switch from the standard graphical interface format to a textual one. This is particularly useful for visually impaired users who use large screen fonts or speech synthesizers for output.</Text>
</Content>
</Subsection>
<Subsection id="presentation_preferences">
<Title>
<Text id="148">Presentation preferences</Text>
</Title>
<Content>
<Text id="149">Depending on the collection, there may be other options you can set that control the presentation. Collections of web pages allow you to suppress the Greenstone navigation bar at the top of each document page, so that once you have done a search you land at the exact web page that matches without any Greenstone header. To do another search you will have to use your browser's “back” button. These collections also allow you to suppress Greenstone's warning message when you click a link that takes you out of the digital library collection and on to the web itself. And in some web collections you can control whether the links on the “Search Results” page take you straight to the actual URL in question, rather than to the digital library's copy of the page.</Text>
</Content>
</Subsection>
<Subsection id="search_preferences">
<Title>
<Text id="150">Search preferences</Text>
</Title>
<Content>
<Text id="151">Under <i>Search preferences</i> in Figure <CrossRef target="Figure" ref="the_preferences_page"/>, the first pair of buttons allows you to get a large query box, so that you can easily do paragraph-sized searching. In Greenstone, it is surprisingly quick to search for large amounts of text. The next two pairs of buttons control the kind of text matching in the searches that you make. The first set (labeled “case differences”) controls whether upper and lower case must match. The second (“word endings”) controls whether to ignore word endings or not.</Text>
<Text id="152">Using the next button pair you can switch to the “advanced” query mode described above, which allows you to specify more precise queries by combining terms using AND (&amp;), OR (|), and NOT (!). You can turn the search history feature, described above, on and off. Finally, you can control the number of hits returned, and the number presented on each screenful, through the last entry in Figure <CrossRef target="Figure" ref="the_preferences_page"/>.</Text>
</Content>
</Subsection>
</Content>
</Section>
</Content>
</Chapter>
<Chapter id="making_greenstone_collections">
<Title>
<Text id="153">Making Greenstone Collections</Text>
</Title>
<Content>
<Text id="154">The simplest way to build new collections is to use Greenstone's “librarian” interface (GLI). This allows you to collect sets of documents, import or assign metadata, and build them into a Greenstone collection. It supports five basic activities, which can be interleaved but are nominally undertaken in this order:</Text>
<NumberedList>
<NumberedItem>
<Text id="155">Copy documents from the computer's file space, including existing collections, into the new collection. Any existing metadata remains “attached” to these documents. Documents may also be gathered from the web through a built-in mirroring facility.</Text>
</NumberedItem>
<NumberedItem>
<Text id="156">Enrich the documents by adding further metadata to individual documents or groups of documents.</Text>
</NumberedItem>
<NumberedItem>
<Text id="157">Design the collection by determining its appearance and the access facilities that it will support.</Text>
</NumberedItem>
<NumberedItem>
<Text id="158">Build the collection using Greenstone.</Text>
</NumberedItem>
<NumberedItem>
<Text id="159">Preview the newly created collection, which will have been installed on your Greenstone home page as one of the regular collections.</Text>
</NumberedItem>
</NumberedList>
<Text id="160">The librarian interface allows you to add what people call “external” metadata to documents, metadata that pertains to the document as a whole. But documents often need to be structured into sections and subsections, and “internal” metadata might be associated with each part. In Greenstone, source documents can be tagged with this information, and we explain this in Section <CrossRef target="Section" ref="tagging_document_files"/>.</Text>
<Text id="161">Finally, an alternative way of building collections is provided by the Collector, which helps you create new collections, modify or add to existing ones, or delete collections. It predates the librarian interface, and for most practical purposes the librarian interface should be used instead of the Collector. It is described in Section <CrossRef target="Section" ref="the_collector"/>.</Text>
<Text id="162">To harness the full power of Greenstone to build advanced collections, you will also need to read Chapter <CrossRef external="Develop" lang="en" target="Chapter" ref="getting_the_most_out_of_your_documents"/> of the <i>Developer's Guide</i>.</Text>
<Section id="the_librarian_interface">
<Title>
<Text id="163">The librarian's interface</Text>
</Title>
<Content>
<Text id="164">To convey the operation of Greenstone's librarian interface, we work through a simple example. Figures <CrossRef target="Figure" ref="starting_a_new_collection"/> to <CrossRef target="Figure" ref="previewing_the_newly_built_collection"/> are screen snapshots at various points during the interaction. This example uses documents in the Development Library Subset (DLS) collection, which is distributed with Greenstone. For expository purposes, the walkthrough takes the form of a single pass through the steps listed above. A more realistic pattern of use, however, is for users to switch back and forth through the various stages as the task proceeds.</Text>
<Text id="165">The librarian interface can be run in one of four modes: Librarian Assistant, Librarian, Library Systems Specialist, and Expert. Modes control the level of detail within the interface, and can be changed through 'Preferences' in the 'File' menu. The walkthrough in this section assumes that the librarian interface is operating in the default mode, Librarian.</Text>
<Subsection id="getting_started">
<Title>
<Text id="166">Getting started</Text>
</Title>
<Content>
<Text id="167">Launch the librarian interface under Windows by selecting <i>Greenstone Digital Library</i> from the <i>Programs</i> section of the <i>Start</i> menu and choosing <i>Librarian Interface</i>. If you are using Unix, instead type</Text>
<CodeLine>cd ~/gsdl</CodeLine>
<CodeLine>cd gli</CodeLine>
<CodeLine>./gli.sh</CodeLine>
<Text id="168">where <i>~/gsdl</i> is the directory containing your Greenstone system. To begin, you must either open an existing collection or start a new one. Figure <CrossRef target="Figure" ref="starting_a_new_collection"/> shows the user in the process of starting a new collection. She has selected <i>New</i> from the file menu and begun to fill out general information about the collection—its title, the E-mail address of the person responsible for it, and a brief description of the content—in the popup window. The collection title is a short phrase used throughout the digital library to identify the collection's content: existing collections have names like <i>Food and Nutrition Library</i>, <i>World Environmental Library</i>, and so on. When you type the title, the system assigns a unique mnemonic identifier, the collection “name”, for internal use (you can change it if you like). The E-mail address specifies the first point of contact for any problems encountered with the collection.</Text>
<Text id="169">The brief description is a statement describing the principles that govern what is included in the collection. It appears under the heading <i>About this collection</i> on the collection's initial page.</Text>
<Figure id="starting_a_new_collection">
<Title>
<Text id="170">Starting a new collection</Text>
</Title>
<File width="407" height="317" url="images/User_Fig_4.png"/>
</Figure>
<Figure id="exploring_the_local_file_space">
<Title>
<Text id="171">Exploring the local file space</Text>
</Title>
<File width="407" height="318" url="images/User_Fig_5.png"/>
</Figure>
<Text id="172">At this point, the user decides whether to base the new collection on the same structure as an existing collection, or to build an entirely new kind of collection. In Figure <CrossRef target="Figure" ref="starting_a_new_collection"/> she has chosen to base it on the <i>Development Library Subset</i> collection. This implies that the “DLS” metadata set which is used in this collection will be used for the new collection. (In fact, this metadata set has been used to build several Greenstone collections that share a common structure and organization but with different content, including the <i>Development Library Subset</i> and <i>Demo</i> collections delivered as samples with Greenstone.)</Text>
<Text id="173">The DLS metadata set contains these items:</Text>
<BulletList>
<Bullet>
<Text id="174">Title</Text>
</Bullet>
<Bullet>
<Text id="175">Subject</Text>
</Bullet>
<Bullet>
<Text id="176">Language</Text>
</Bullet>
<Bullet>
<Text id="177">Organization</Text>
</Bullet>
<Bullet>
<Text id="178">Keyword (i.e.”Howto”).</Text>
</Bullet>
</BulletList>
<Text id="179">(There is, in addition, a metadata item called <i>AZList</i> which is used to determine which bucket of the alphabetic list contains the document's title, with values like “A-B” or “C-D-E”. This is used to give precise control over thedivisions in the list. For most other collections it is absent, and Greenstone assigns the buckets itself.)</Text>
<Text id="180">If, instead, the user had chosen “New Collection” at this point, she would have been asked to select what metadata sets should be used in the new collection. Three standard sets are pre-supplied: Dublin Core, the DLS metadata set mentioned above, and a set that comprises metadata elements extracted automatically by Greenstone from the documents in the collection. The user can also create new metadata sets using a popup panel activated through the “metadata” menu.</Text>
<Text id="181">Several different metadata sets can be associated with the same collection; the system keeps them distinct (so that, for example, documents can have both a Dublin Core <i>Title</i> and a DLS <i>Title</i>). The different sets are clearly distinguished in the interface. Behind the scenes, metadata sets are represented in XML.</Text>
</Content>
</Subsection>
<Subsection id="assembling_the_source_material">
<Title>
<Text id="182">Assembling the source material</Text>
</Title>
<Content>
<Text id="183">After clicking the <i>OK</i> button on the “new collection” popup, the remaining parts of the interface, which were grayed out before, become active. The <i>Gather</i> panel, selected by the eponymous tab near the top of Figure <CrossRef target="Figure" ref="starting_a_new_collection"/>, is displayed initially. This allows the user to explore the local file space and existing collections, gathering up selected documents for the new collection. The panel is divided into two sections, the left for browsing existing structures and the right for the documents in the collection.</Text>
<Text id="184">Operations available at this stage include:</Text>
<BulletList>
<Bullet>
<Text id="185">Navigating the existing file structure hierarchy, and the one being created, in the usual way.</Text>
</Bullet>
<Bullet>
<Text id="186">Dragging and dropping files into the new collection.</Text>
</Bullet>
<Bullet>
<Text id="187">Multiple selection of files.</Text>
</Bullet>
<Bullet>
<Text id="188">Dragging and dropping entire sub-hierarchies.</Text>
</Bullet>
<Bullet>
<Text id="189">Deleting documents from the nascent collection.</Text>
</Bullet>
<Bullet>
<Text id="190">Creating new sub-hierarchies within the collection.</Text>
</Bullet>
<Bullet>
<Text id="191">Filtering the files that are visible, in both the local file system and the collection, based on predetermined groups or on standard file matching terms.</Text>
</Bullet>
<Bullet>
<Text id="192">Invoking the appropriate program to display the contents of a selected file, by double-clicking it.</Text>
</Bullet>
</BulletList>
<Text id="193">Care is taken to deal appropriately with name clashes when files of the same name in different parts of the computer's directory structure are copied into the same folder of the collection.</Text>
<Text id="194">In Figure <CrossRef target="Figure" ref="exploring_the_local_file_space"/> the user is using the interactive file tree display to explore the local file system. At this stage, the collection on the right is empty; the user populates it by dragging and dropping files of interest from the left to the right panel. Such files are “copied” rather than “moved”: so as not to disturb the original file system. The usual techniques for multiple selection, dragging and dropping, structuring the new collection by creating subdirectories (“folders”), and deleting files from it by moving them to a trashcan, are all available.</Text>
<Text id="195">Existing collections are represented by a subdirectory on the left called “Greenstone Collections,” which can be opened and explored like any other directory. However, the documents therein differ from ordinary files because they already have metadata attached, and this is preserved when they are moved into the new collection. Conflicts may arise because their metadata may have been assigned using a different metadata set from the one in use for the new collection, and the user must resolve these. In Figure <CrossRef target="Figure" ref="importing_existing_metadata"/> the user has selected some documents from an existing collection and dragged them into the new one. The popup window explains that the metadata element <i>Organization</i> cannot be automatically imported, and asks the user to either select a metadata set and press <i>Add</i> to add the metadata element to that set<FootnoteRef id="1"/>, or choose a metadata set, then an element, and press <i>Merge</i> to effectively rename the old metadata element to the new one by merging the two. Metadata in subsequent documents from the same collection will automatically be handled in the same way.</Text>
<Text id="196">When large file sets are selected, dragged, and dropped into the new collection, the copying operation may take some time—particularly if metadata conversion is involved. To indicate progress, the interface shows which file is being copied and what percentage of files has been processed.</Text>
<Text id="197">Special facilities are provided for dealing with large file sets. For example, the user can choose to filter the file tree to show only certain files, using a dropdown menu of file types displayed underneath the trees. In Figure <CrossRef target="Figure" ref="filtering_the_file_trees"/>, only the HTM and HTML files are being shown (and only these files will be copied by drag and drop).</Text>
</Content>
</Subsection>
<Subsection id="enriching_the_documents">
<Title>
<Text id="198">Enriching the documents</Text>
</Title>
<Content>
<Text id="199">The next phase in collection building is to enrich the documents by adding metadata. The <i>Enrich</i> tab brings up a new panel of information (Figure <CrossRef target="Figure" ref="assigning_metadata_using_enrich_view"/>), which shows the document tree representing the collection on the left and on the right allows metadata to be added to individual documents, or groups of documents.</Text>
<Text id="200">Documents that are copied during the first step come with any applicable metadata attached. If a document is part of a Greenstone collection, previously defined metadata is carried over to the new collection. Of course, this new collection may have a different metadata set, or perhaps just a subset of the defined metadata, and only metadata that pertains to the new collection's set is carried over. Resolution of such conflicts may require user intervention via a supplementary dialog (Figure <CrossRef target="Figure" ref="importing_existing_metadata"/>). Any choices made are remembered for subsequent file copies.</Text>
<Text id="201">The <i>Enrich</i> panel allows metadata values to be assigned to documents in the collection. For example, new values can be added to the set of existing values for an element. If the element's values have a hierarchical structure, the hierarchy can be extended in the same way.</Text>
<Figure id="importing_existing_metadata">
<Title>
<Text id="202">Importing existing metadata</Text>
</Title>
<File width="407" height="317" url="images/User_Fig_6.png"/>
</Figure>
<Figure id="filtering_the_file_trees">
<Title>
<Text id="203">Filtering the file trees</Text>
</Title>
<File width="407" height="318" url="images/User_Fig_7.png"/>
</Figure>
<Figure id="assigning_metadata_using_enrich_view">
<Title>
<Text id="204">Assigning metadata using <i>Enrich</i> view</Text>
</Title>
<File width="407" height="318" url="images/User_Fig_8.png"/>
</Figure>
<Figure id="viewing_all_metadata_for_selected_files">
<Title>
<Text id="205">Viewing all metadata for selected files</Text>
</Title>
<File width="407" height="317" url="images/User_Fig_9.png"/>
</Figure>
<Text id="206">Metadata values can also be assigned to folders, in just the same way. Documents in these folders for which this metadata is unspecified inherit the metadata values. However, they can subsequently be overridden by supplying different ones for the document itself.</Text>
<Text id="207">Operations at this stage include:</Text>
<BulletList>
<Bullet>
<Text id="208">Assigning new and existing metadata values to documents.</Text>
</Bullet>
<Bullet>
<Text id="209">Assigning metadata to an individual document.</Text>
</Bullet>
<Bullet>
<Text id="210">Assigning metadata to a folder (this is inherited by all documentsin the folder, including those in nested folders).</Text>
</Bullet>
<Bullet>
<Text id="211">Assigning hierarchical metadata, whose structure can be dynamically updated if required.</Text>
</Bullet>
<Bullet>
<Text id="212">Editing or updating assigned metadata.</Text>
</Bullet>
<Bullet>
<Text id="213">Reviewing the metadata assigned to a selection of files and directories.</Text>
</Bullet>
</BulletList>
<Text id="214">For our walkthrough example, in Figure <CrossRef target="Figure" ref="assigning_metadata_using_enrich_view"/> the user has selected the folder <i>ec121e</i> and assigned “EC Courier” as its <i>Organization</i> metadata. The buttons for updating and removing metadata become active depending on what selections have been made.</Text>
<Text id="215">During the enrichment phase, or indeed at any other time, the user can choose to view all the metadata that has been assigned to documents in the collection. This is done by selecting a set of documents and choosing <i>Assigned Metadata</i> from the metadata sets menu, which brings up a popup window like that in Figure <CrossRef target="Figure" ref="viewing_all_metadata_for_selected_files"/> that shows the metadata in spreadsheet form. For large collections it is useful to be able to view the metadata associated with certain document types only, and if the user has specified a file filter as mentioned above, only the selected documents are shown in the metadata display.</Text>
<Text id="216">The panel in Figure <CrossRef target="Figure" ref="editing_the_metadata_set"/> allows the user to edit metadata sets. Here, the user is looking at the <i>Subject</i> element of the DLS set. The values of this element form a hierarchy, and the user is examining, and perhaps changing, the list of values assigned to it. The same panel also allows you to change the “profile” for mapping elements of one metadata set to another. This profile is created when importing documents from collections that have pre-assigned metadata.</Text>
<Figure id="editing_the_metadata_set">
<Title>
<Text id="217">Editing the metadata set</Text>
</Title>
<File width="407" height="317" url="images/User_Fig_10.png"/>
</Figure>
<Figure id="designing_the_collection">
<Title>
<Text id="218">Designing the collection</Text>
</Title>
<File width="407" height="318" url="images/User_Fig_11.png"/>
</Figure>
<Figure id="specifying_which_plug-ins_to_use">
<Title>
<Text id="219">Specifying which plug-ins to use</Text>
</Title>
<File width="407" height="318" url="images/User_Fig_12.png"/>
</Figure>
<Figure id="configuring_arguments_to_a_plug-in">
<Title>
<Text id="220">Configuring arguments to a plug-in</Text>
</Title>
<File width="407" height="317" url="images/User_Fig_13.png"/>
</Figure>
</Content>
</Subsection>
<Subsection id="designing_the_collection_1">
<Title>
<Text id="221">Designing the collection</Text>
</Title>
<Content>
<Text id="222">The <i>Design</i> panel (Figures <CrossRef target="Figure" ref="designing_the_collection"/>—<CrossRef target="Figure" ref="configuring_arguments_to_a_plug-in"/>) allows one to specify the structure, organization, and presentation of the collection being created. As noted earlier, the result of this process is recorded in a “collection configuration file,” which is Greenstone's way of expressing the facilities that a collection requires. This step involves a series of separate interaction screens, each dealing with one aspect of the collection design. In effect, it serves as a graphical equivalent to the usual process of editing the configuration file manually.</Text>
<Text id="223">Operations include:</Text>
<BulletList>
<Bullet>
<Text id="224">Reviewing and editing collection-level metadata such as title, author and public availability of the collection.</Text>
</Bullet>
<Bullet>
<Text id="225">Defining what full-text indexes are to be built.</Text>
</Bullet>
<Bullet>
<Text id="226">Creating sub-collections and having indexes built for them.</Text>
</Bullet>
<Bullet>
<Text id="227">Adding or removing support for predefined interface languages.</Text>
</Bullet>
<Bullet>
<Text id="228">Constructing a list of plug-ins to be used, and their arguments.</Text>
</Bullet>
<Bullet>
<Text id="229">Presenting the list to the user for review and modification.</Text>
</Bullet>
<Bullet>
<Text id="230">Configuring individual plug-ins.</Text>
</Bullet>
<Bullet>
<Text id="231">Constructing a list of “classifiers,” their arguments, assignment and configuration.</Text>
</Bullet>
<Bullet>
<Text id="232">Assigning formatting strings to various controls within the collection, thus altering its appearance.</Text>
</Bullet>
<Bullet>
<Text id="233">Reviewing the metadata sets, and their elements, used in the collection.</Text>
</Bullet>
</BulletList>
<Text id="234">In Figure <CrossRef target="Figure" ref="designing_the_collection"/> the user has clicked the <i>Design</i> tab and is reviewing the general information about the collection, entered when the new collection was created. On the left are listed the various facets that the user can configure: General, Document Plug-ins, Search Types, Search Indexes, Partition Indexes, Cross-Collection Search, Browsing Classifiers, Format Features, Translate Text, Metadata Sets. Appearance and functionality varies between these. For example, clicking the <i>Plug-in</i> button brings up the screen shown in Figure <CrossRef target="Figure" ref="specifying_which_plug-ins_to_use"/>, which allows you to add, remove or configure plug-ins, and change the order in which the plug-ins are applied to documents.</Text>
<Text id="235">Plug-ins and classifiers have many different arguments or “options” that the user can supply. The dialog box in Figure <CrossRef target="Figure" ref="configuring_arguments_to_a_plug-in"/> shows the user specifying arguments to some of the plug-ins. The grayed-out fields become active when the user adds the option by clicking the tick-box beside it. Because Greenstone is a continually growing open-source system, the number of options tends to increase as developers add new facilities. To help cope with this, Greenstone has a “plug-in information” utility program that lists the options available for each plug-in, and the librarian interface automatically invokes this to determine what options to show. This allows the interactive user interface to automatically keep pace with developments in the software.</Text>
<Figure id="getting_ready_to_create_new_collection">
<Title>
<Text id="236">Getting ready to create new collection</Text>
</Title>
<File width="407" height="318" url="images/User_Fig_14.png"/>
</Figure>
<Figure id="previewing_the_newly_built_collection">
<Title>
<Text id="237">Previewing the newly built collection</Text>
</Title>
<File width="407" height="291" url="images/User_Fig_15.png"/>
</Figure>
</Content>
</Subsection>
<Subsection id="building_the_collection">
<Title>
<Text id="238">Building the collection</Text>
</Title>
<Content>
<Text id="239">The <i>Create</i> panel (Figure <CrossRef target="Figure" ref="getting_ready_to_create_new_collection"/>) is used to construct a collection based on the documents and assigned metadata. The brunt of this work is borne by the Greenstone code itself. The user controls this external process through a series of separate interaction screens, each dealing with the arguments provided to a certain stage of the creation process.</Text>
<Text id="240">The user observes the building process though a window that shows not only the text output generated by Greenstone's importing and index-building scripts, but also progress bars that indicate the overall degree of completion of each script.</Text>
<Text id="241">Figure <CrossRef target="Figure" ref="getting_ready_to_create_new_collection"/> shows the <i>Create</i> view. At the top are shown some options that can be applied during the creation process. The user selects appropriate values for the options. This figure illustrates a popup “tool tip” that is available throughout the interface to explain the function of each argument.</Text>
<Text id="242">When satisfied with the arguments, the user clicks <i>Build Collection</i>. Greenstone continually prints text that indicates progress, and this is shown along with a more informative progress bar.</Text>
</Content>
</Subsection>
<Subsection id="previewing">
<Title>
<Text id="243">Previewing</Text>
</Title>
<Content>
<Text id="244">The <i>Preview Collection</i> button (Figure <CrossRef target="Figure" ref="getting_ready_to_create_new_collection"/>) is used to view the collection that has been built. Clicking this button launches a web browser showing the home page of the collection (Figure <CrossRef target="Figure" ref="previewing_the_newly_built_collection"/>). In practice, previewing often shows up deficiencies in the collection design, or in the individual metadata values, and the user frequently returns to earlier stages to correct these. This button becomes active once the collection has been created. The newly created collection will also have been installed on your Greenstone home page as one of the regular collections.</Text>
</Content>
</Subsection>
<Subsection id="help">
<Title>
<Text id="245">Help</Text>
</Title>
<Content>
<Text id="246">On-line help is always available, and is invoked using the <i>Help</i> item at the right of the main menu bar at the top of each of the Figures. This opens up a hierarchically structured file of help text, and account is taken of the user's current context to highlight the section that is appropriate to the present stage of the interaction. Furthermore, as noted above, whenever the mouse is held still over any interactive object a small window pops up to give a textual “tool tip,” as illustrated near the bottom of Figure <CrossRef target="Figure" ref="getting_ready_to_create_new_collection"/>.</Text>
</Content>
</Subsection>
</Content>
</Section>
<Section id="librarian_interface_user_guide">
<Title>
<Text id="247">Librarian Interface user guide</Text>
</Title>
<Content>
&chap_gli;
</Content>
</Section>
<Section id="tagging_document_files">
<Title>
<Text id="453">Tagging document files</Text>
</Title>
<Content>
<Text id="454">Source documents often need to be structured into sections and subsections, and this information needs to be communicated to Greenstone so that it can preserve the hierarchical structure. Also, metadata - typically the title - might be associated with each section and subsection.</Text>
<Text id="455">The source documents from an OCR process are typically a set of word processor files, including images. If these are represented as MicrosoftWord files, they can be input into Greenstone using the Word plugin. Alternatively, they can be converted to HTML and input using the HTML plugin.</Text>
<Text id="456">In either case, the hierarchical structure of a document may be indicated by inserting tags in the text as follows:</Text>
<CodeLine>&lt;!--</CodeLine>
<CodeLine>&lt;Section&gt;</CodeLine>
<CodeLine>&lt;Description&gt;</CodeLine>
<Text type="code" id="457">&lt;Metadata name="Title"&gt;Realizing human rights for poor people: Strategies for achieving the international development targets&lt;/Metadata&gt;</Text>
<CodeLine>&lt;/Description&gt;</CodeLine>
<CodeLine>--&gt;</CodeLine>
<Text id="458"><i>(text of section goes here)</i></Text>
<CodeLine>&lt;!--</CodeLine>
<CodeLine>&lt;/Section&gt;</CodeLine>
<CodeLine>--&gt;</CodeLine>
<Text id="459">The &lt;!-- ... --&gt; markers are used because they indicate comments in HTML; thus these section tags will not affect document formatting. You must include these markers around your section tags, even if the document you are working with is not HTML (e.g. if it's a Microsoft Word file).</Text>
<Text id="460">In the Description part (between the &lt;Description&gt; and &lt;/Description&gt; tags) other kinds of metadata can be specified, but this is not done for the style of collections we are describing here.</Text>
<Text id="461">It is important to remember that you are creating a hierarchical table of contents when you insert section tags into your document. This means that sections can be nested within other sections. In fact, all sections must be nested within a single enclosing section that encompasses the entire document.</Text>
<Text id="462">The following example demonstrates a document with two chapters, the second of which contains two subsections. For real examples of sourcedocuments tagged in this way, look at the source documents for the Demo or DLS collections.</Text>
<CodeLine>&lt;!--</CodeLine>
<CodeLine>&lt;Section&gt;</CodeLine>
<CodeLine>&lt;Description&gt;</CodeLine>
<CodeLine>&lt;Metadata name="Title"&gt;My Document&lt;/Metadata&gt;</CodeLine>
<CodeLine>&lt;/Description&gt;</CodeLine>
<CodeLine>&lt;Section&gt;</CodeLine>
<CodeLine>&lt;Description&gt;</CodeLine>
<CodeLine>&lt;Metadata name="Title"&gt;Chapter 1&lt;/Metadata&gt;</CodeLine>
<CodeLine>&lt;/Description&gt;</CodeLine>
<CodeLine>--&gt;</CodeLine>
<Text type="code" id="463">(text of chapter 1 goes here)</Text>
<CodeLine>&lt;!--</CodeLine>
<CodeLine>&lt;/Section&gt;</CodeLine>
<CodeLine>&lt;Section&gt;</CodeLine>
<CodeLine>&lt;Description&gt;</CodeLine>
<CodeLine>&lt;Metadata name="Title"&gt;Chapter 2&lt;/Metadata&gt;</CodeLine>
<CodeLine>&lt;/Description&gt;</CodeLine>
<CodeLine>&lt;Section&gt;</CodeLine>
<CodeLine>&lt;Description&gt;</CodeLine>
<CodeLine>&lt;Metadata name="Title"&gt;Subsection 1&lt;/Metadata&gt;</CodeLine>
<CodeLine>&lt;/Description&gt;</CodeLine>
<CodeLine>--&gt;</CodeLine>
<Text type="code" id="464">(text of sub-section 1 goes here)</Text>
<CodeLine>&lt;!--</CodeLine>
<CodeLine>&lt;/Section&gt;</CodeLine>
<CodeLine>&lt;Section&gt;</CodeLine>
<CodeLine>&lt;Description&gt;</CodeLine>
<CodeLine>&lt;Metadata name="Title"&gt;Subsection 2&lt;/Metadata&gt;</CodeLine>
<CodeLine>&lt;/Description&gt;</CodeLine>
<CodeLine>--&gt;</CodeLine>
<Text type="code" id="465">(text of sub-section 2 goes here)</Text>
<CodeLine>&lt;!--</CodeLine>
<CodeLine>&lt;/Section&gt;</CodeLine>
<CodeLine>&lt;/Section&gt;</CodeLine>
<CodeLine>&lt;/Section&gt;</CodeLine>
<CodeLine>--&gt;</CodeLine>
<Text id="466">Note that metadata assigned from within a section tag in a source document takes precedence over that assigned to the document as a whole. This means that you should not explicitly specify Title metadata for the top-level section within a source document unless you want it to override the title you gave it when specifying metadata. In the above example, unless you want to override the document's existing title you should omit the line that reads:</Text>
<CodeLine>&lt;Metadata name="Title"&gt;My Document&lt;/Metadata&gt;</CodeLine>
</Content>
</Section>
<Section id="the_collector">
<Title>
<Text id="467">The Collector</Text>
</Title>
<Content>
<Text id="468">The Collector is a facility that helps you create new collections, modify or add to existing ones, or delete collections. To do this you will be guided through a sequence of web pages which request the information that is needed. The sequence is self-explanatory: this section takes you through it. As an alternative to using the Collector, you can also build collections from the command line—the first few pages of the Developer's Guide give a detailed walk-through of how to do this. The Collector predates the librarian interface described in Section <CrossRef target="Section" ref="the_librarian_interface"/>, and for most practical purposes the librarian interface should be used instead of the Collector.</Text>
<Text id="469">Building and distributing information collections carries responsibilities that you should reflect on before you begin. There are legal issues of copyright: being able to access documents doesn't mean you can necessarily give them to others. There are social issues: collections should respect the customs of the community out of which the documents arise. And there are ethical issues: some things simply should not be made available to others. The pen is mightier than the sword!—be sensitive to the power of information and use it wisely.</Text>
<Text id="470">To access the Collector, click the appropriate link on the digital library home page.</Text>
<Text id="471">In Greenstone, the structure of a particular collection is determined when the collection is set up. This includes such things as the format of the source documents, how they should be displayed on the screen, the source of metadata, what browsing facilities should be provided, what full-text search indexes should be provided, and how the search results should be displayed. Once the collection is in place, it is easy to add new documents to it—so long as they have the same format as the existing documents, and the same type of metadata is provided, in exactly the same way.</Text>
<Text id="472">The Collector has the following basic functions:</Text>
<NumberedList>
<NumberedItem>
<Text id="473">create a new collection with the same structure as an existing one;</Text>
</NumberedItem>
<NumberedItem>
<Text id="474">create a new collection with a different structure from existing ones;</Text>
</NumberedItem>
<NumberedItem>
<Text id="475">add new material to an existing collection;</Text>
</NumberedItem>
<NumberedItem>
<Text id="476">modify the structure of an existing collection;</Text>
</NumberedItem>
<NumberedItem>
<Text id="477">delete a collection; and</Text>
</NumberedItem>
<NumberedItem>
<Text id="478">write an existing collection to a self-contained, self-installing cd-rom.</Text>
</NumberedItem>
</NumberedList>
<Text id="479">Figure <CrossRef target="Figure" ref="using_the_collector_to_build_a_new_collection"/> shows the Collector being used to create a new collection, in this case from a set of html files stored locally. You must first decide whether to work with an existing collection or build a new one. The former case covers options 1 and 2 above; the latter covers options 3—6. In Figure <CrossRef target="Figure" ref="using_the_collector_to_build_a_new_collection"/>, the user opts to create a new collection.</Text>
<Figure id="using_the_collector_to_build_a_new_collection">
<Title>
<Text id="480">Using the Collector to build a new collection (continued on next pages)</Text>
<SubTitle>
<Text id="481">(a)</Text>
</SubTitle>
</Title>
<File width="369" height="440" url="images/User_Fig_16a.png"/>
</Figure>
<Subsection id="logging_in">
<Title>
<Text id="482">Logging in</Text>
</Title>
<Content>
<Text id="483">Either way it is necessary to log in before proceeding. Note that in general, people use their web browser to access the collection-building facility on a remote computer, and build the collection on that server. Of course, we cannot allow arbitrary people to build collections (for reasons of propriety if nothing else), so Greenstone contains a security system which forces people who want to build collections to log in first. This allows a central system to offer a service to those wishing to build information collections and use that server to make them available to others. Alternatively, if you are running Greenstone on your own computer you can build collections locally, but it is still necessary to log in because other people who use the Greenstone system on your computer should not be allowed to build collections without prior permission.</Text>
</Content>
</Subsection>
<Subsection id="dialog_structure">
<Title>
<Text id="484">Dialog structure</Text>
</Title>
<Content>
<Figure id="using_the_collector_to_build_a_new_collection_1">
<Title>
<Text id="485">Using the Collector to build a new collection (Continued)</Text>
<SubTitle>
<Text id="486">(b)</Text>
</SubTitle>
</Title>
<File width="369" height="435" url="images/User_Fig_16b.png"/>
</Figure>
<Text id="487">Upon completion of login, the page in Figure <CrossRef target="Figure" ref="using_the_collector_to_build_a_new_collection_1"/> appears. This shows the sequence of steps that are involved in collection building. They are:</Text>
<NumberedList>
<NumberedItem>
<Text id="488">Collection information</Text>
</NumberedItem>
<NumberedItem>
<Text id="489">Source data</Text>
</NumberedItem>
<NumberedItem>
<Text id="490">Configuring the collection</Text>
</NumberedItem>
<NumberedItem>
<Text id="491">Building the collection</Text>
</NumberedItem>
<NumberedItem>
<Text id="492">Viewing the collection.</Text>
</NumberedItem>
</NumberedList>
<Text id="493">The first step is to specify the collection's name and associated information. The second is to say where the source data is to come from. The third is to adjust the configuration options, a step that becomes more useful as you gain experience with Greenstone. The fourth step is where all the (computer's) work is done. During the “building” process the system makes all the indexes and gathers together any other information that is required to make the collection operate. The fifth step is to view the collection that has been created.</Text>
<Text id="494">These five steps are displayed as a linear sequence of gray buttons at the bottom of the screen in Figure <CrossRef target="Figure" ref="using_the_collector_to_build_a_new_collection_1"/>, and at the bottom of all other pages generated by the Collector. This display helps users keep track of where they are in the process. The button that should be clicked to continue the sequence is shown in green (<i>collection information</i> in Figure <CrossRef target="Figure" ref="using_the_collector_to_build_a_new_collection_1"/>). The gray buttons (all the others, in Figure <CrossRef target="Figure" ref="using_the_collector_to_build_a_new_collection_1"/>) are inactive. The buttons change to yellow as you proceed through the sequence, and the user can return to an earlier step by clicking the corresponding yellow button in the diagram. This display is modeled after the “wizards” that are widely used in commercial software to guide users through the steps involved in installing new software.</Text>
</Content>
</Subsection>
<Subsection id="collection_information">
<Title>
<Text id="495">Collection information</Text>
</Title>
<Content>
<Figure id="using_the_collector_to_build_a_new_collection_2">
<Title>
<Text id="496">Using the Collector to build a new collection (Continued)</Text>
<SubTitle>
<Text id="497">(c)</Text>
</SubTitle>
</Title>
<File width="369" height="504" url="images/User_Fig_16c.png"/>
</Figure>
<Text id="498">The next step in the sequence, collection information, is shown in Figure <CrossRef target="Figure" ref="using_the_collector_to_build_a_new_collection_2"/>. When creating a new collection, it is necessary to enter some information about it:</Text>
<BulletList>
<Bullet>
<Text id="499">title,</Text>
</Bullet>
<Bullet>
<Text id="500">contact E-mail address, and</Text>
</Bullet>
<Bullet>
<Text id="501">brief description.</Text>
</Bullet>
</BulletList>
<Text id="502">The collection title is a short phrase used through the digital library to identify the content of the collection. Example titles include <i>Food and Nutrition Library</i>, <i>World Environmental Library</i>, <i>Development Library</i>, and so on. The E-mail address specifies the first point of contact for any problems encountered with the collection. If the Greenstone software detects a problem, a diagnostic report may be sent to this address. Finally, the brief description is a statement describing the principles that govern what is included in the collection. It appears under the heading <i>About this collection</i> on the first page when the collection is presented.</Text>
<Text id="503">The user's current position in the collection-building sequence is indicated by an arrow that appears in the display at the bottom of each screen—in this case, as Figure <CrossRef target="Figure" ref="using_the_collector_to_build_a_new_collection_2"/> shows, the collection information stage. The user proceeds to Figure <CrossRef target="Figure" ref="using_the_collector_to_build_a_new_collection_3"/> by clicking the green source data button.</Text>
</Content>
</Subsection>
<Subsection id="source_data">
<Title>
<Text id="504">Source data</Text>
</Title>
<Content>
<Figure id="using_the_collector_to_build_a_new_collection_3">
<Title>
<Text id="505">Using the Collector to build a new collection (Continued)</Text>
<SubTitle>
<Text id="506">(d)</Text>
</SubTitle>
</Title>
<File width="368" height="532" url="images/User_Fig_16d.png"/>
</Figure>
<Text id="507">Figure <CrossRef target="Figure" ref="using_the_collector_to_build_a_new_collection_3"/> is the point where the user specifies the source text that comprises the collection. You may either base your collection on a default structure that is provided, or on the structure of an existing collection.</Text>
<Text id="508">If you opt for the default structure, the new collection may contain html documents (files ending in <i>.htm, .html</i>), or plain text documents (files ending in <i>.txt, .text</i>), Microsoft Word documents (files ending in <i>.doc</i>), PDF documents (files ending in <i>.pdf</i>) or E-mail documents (files ending in <i>.email</i>). More information about the different document formats that can be accommodated is given in the section on “Document formats” below.</Text>
<Text id="509">If you base your new collection on an existing one, the files in the new collection must be exactly the same type as those used to build the existing one. Note that some collections use non-standard input file formats, while others use metadata specified in auxiliary files. If your new input lacks this information, some browsing facilities may not work properly. For example, if you clone the Demo collection you may find that the <i>subjects</i>, <i>organization</i>, and <i>how to</i> buttons don't work.</Text>
<Text id="510">Boxes are provided to indicate where the source documents are located: up to three separate input sources can be specified in Figure <CrossRef target="Figure" ref="using_the_collector_to_build_a_new_collection_3"/>. If you need more, just click the button marked “more sources.”</Text>
<Text id="511">There are three kinds of specification:</Text>
<BulletList>
<Bullet>
<Text id="512">a directory name on the Greenstone server system (beginning with “file://”)</Text>
</Bullet>
<Bullet>
<Text id="513">an address beginning with “http://” for files to be downloaded from the web</Text>
</Bullet>
<Bullet>
<Text id="514">an address beginning with “ftp://” for files to be downloaded using anonymous FTP.</Text>
</Bullet>
</BulletList>
<Text id="515">If you use <i>file://</i> or <i>ftp://</i> to specify a file, that file will be downloaded.</Text>
<Text id="516">If you use <i>http://</i> it depends on whether the URL gives you a normal web page in your browser, or a list of files. If a page, that page will be downloaded—and so will all pages it links to, and all pages they link to, etc.—provided they reside on the same site, below the URL.</Text>
<Text id="517">If you use <i>file://</i> or <i>ftp://</i> to specify a folder or directory, or give a <i>http://</i> URL that leads to a list of files, everything in the folder and all its subfolders will be included in the collection.</Text>
<Text id="518">You can specify sources of more than one type.</Text>
<Text id="519">In this case (Figure <CrossRef target="Figure" ref="using_the_collector_to_build_a_new_collection_3"/>) the new collection will contain documents taken from a local file system as well as a remote web site, which will be mirrored during the building process.</Text>
<Text id="520">When you click the <i>configure collection</i> button to proceed to the next stage of building, the Collector checks that all the sources of input you specified can be reached. This might take a few seconds, or even a few minutes if you have specified several sources. If one or more of the input sources you specified is unavailable, you will be presented with a page like that in Figure <CrossRef target="Figure" ref="using_the_collector_to_build_a_new_collection_4"/>, where the unavailable sources are marked (both of them in this case).</Text>
<Figure id="using_the_collector_to_build_a_new_collection_4">
<Title>
<Text id="521">Using the Collector to build a new collection (Continued)</Text>
<SubTitle>
<Text id="522">(e)</Text>
</SubTitle>
</Title>
<File width="368" height="531" url="images/User_Fig_16e.png"/>
</Figure>
<Text id="523">Sources might be unavailable because</Text>
<BulletList>
<Bullet>
<Text id="524">the file, FTP site or URL does not exist;</Text>
</Bullet>
<Bullet>
<Text id="525">you need to dial up your ISP first;</Text>
</Bullet>
<Bullet>
<Text id="526">you are trying to access a URL from behind a firewall.</Text>
</Bullet>
</BulletList>
<Text id="527">The last case is potentially the most mysterious. It occurs if you normally have to present a username and password to access the Internet Sometimes it happens that you can see the page from your Web browser if you enter the URL, but the Collector claims that it is unavailable. The explanation is that the page in your browser may be coming from a locally cached copy. Unfortunately, locally cached copies are invisible to the Collector. In this case we recommend that you download the pages using your browser first.</Text>
</Content>
</Subsection>
<Subsection id="configuring_the_collection">
<Title>
<Text id="528">Configuring the collection</Text>
</Title>
<Content>
<Figure id="using_the_collector_to_build_a_new_collection_5">
<Title>
<Text id="529">Using the Collector to build a new collection (Continued)</Text>
<SubTitle>
<Text id="530">(f)</Text>
</SubTitle>
</Title>
<File width="369" height="467" url="images/User_Fig_16f.png"/>
</Figure>
<Text id="531">Figure <CrossRef target="Figure" ref="using_the_collector_to_build_a_new_collection_5"/> shows the next stage. The construction and presentation of all collections is controlled by specifications in a special collection configuration file (see below). Advanced users may use this page to alter the configuration settings. Most, however, will proceed directly to the final stage. Indeed, in Figure <CrossRef target="Figure" ref="using_the_collector_to_build_a_new_collection_3"/> both the <i>configure collection</i> and the <i>build collection</i> buttons are displayed in green, signifying that step 3 can be bypassed completely.</Text>
<Text id="532">In our example the user has made a small modification to the default configuration file by including the <i>file_is_url</i> flag with the html plugin. This flag causes URL metadata to be inserted in each document, based on the filename convention that is adopted by the mirroring package. This metadata is used in the collection to allow readers to refer to the original source material, rather than to a local copy.</Text>
</Content>
</Subsection>
<Subsection id="building_the_collection_1">
<Title>
<Text id="533">Building the collection</Text>
</Title>
<Content>
<Figure id="using_the_collector_to_build_a_new_collection_6">
<Title>
<Text id="534">Using the Collector to build a new collection (Continued)</Text>
<SubTitle>
<Text id="535">(g)</Text>
</SubTitle>
</Title>
<File width="369" height="304" url="images/User_Fig_16g.png"/>
</Figure>
<Text id="536">Figure <CrossRef target="Figure" ref="using_the_collector_to_build_a_new_collection_6"/> shows the “building” stage. Up until now, the responses to the dialog have merely been recorded in a temporary file. The building stage is where the action takes place.</Text>
<Text id="537">During building, indexes for both browsing and searching are constructed according to instructions in the collection configuration file. The building process takes some time: minutes to hours, depending on the size of the collection and the speed of your computer. Some very large collections take a day or more to build.</Text>
<Text id="538">When you reach this stage in the interaction, a status line at the bottom of the web page gives feedback on how the operation is progressing, updated every five seconds. The message visible in Figure <CrossRef target="Figure" ref="using_the_collector_to_build_a_new_collection_5"/> indicates that when the snapshot was taken, Title metadata was being extracted from an input file.</Text>
<Text id="539">Warnings are written if input files or URLs are requested that do not exist, or exist but there is no plugin that can process them, or the plugin cannot find an associated file, such as an image file embedded in a html document. The intention is that you will monitor progress by keeping this window open in your browser. If any errors cause the process to terminate, they are recorded in this status area.</Text>
<Text id="540">You can stop the building process at any time by clicking on the <i>stop building</i> button in Figure <CrossRef target="Figure" ref="using_the_collector_to_build_a_new_collection_6"/>. If you leave the web page (and have not cancelled the building process with the <i>stop building</i> button), the building operation will continue, and the new collection will be installed when the operation completes.</Text>
</Content>
</Subsection>
<Subsection id="viewing_the_collection">
<Title>
<Text id="541">Viewing the collection</Text>
</Title>
<Content>
<Text id="542">When the collection is built and installed, the sequence of buttons visible at the bottom of Figures <CrossRef target="Figure" ref="using_the_collector_to_build_a_new_collection_1"/>—<CrossRef target="Figure" ref="using_the_collector_to_build_a_new_collection_5"/> appears at the bottom of Figure <CrossRef target="Figure" ref="using_the_collector_to_build_a_new_collection_6"/>, with the View collection button active. This takes the user directly to the newly built collection.</Text>
<Text id="543">Finally, there is a facility for E-mail to be sent to the collection's contact E-mail address, and to the system's administrator, whenever a collection is created (or modified.) This allows those responsible to check when changes occur, and monitor what is happening on the system. The facility is disabled by default but can be enabled by editing the <i>main.cfg</i> configuration file (see the <i>Greenstone Digital Library Developer's Guide</i>, Section <CrossRef target="Chapter" external="Develop" lang="en" ref="configuring_your_greenstone_site"/>).</Text>
</Content>
</Subsection>
<Subsection id="working_with_existing_collections">
<Title>
<Text id="544">Working with existing collections</Text>
</Title>
<Content>
<Text id="545">When you enter the Collector you have to specify whether you want to create an entirely new collection or work with an existing one, adding data to it or deleting it. By creating all searching and browsing structures automatically from the documents themselves Greenstone makes it easy to add new information to existing collections. Because no links are inserted by hand, when new documents in the same format become available they can be merged into the collection automatically.</Text>
<Text id="546">To work with an existing collection, you first select the collection from a list that is provided. Some collections are “write protected” and cannot be altered: these ones don't appear in the selection list. With the collection, you can</Text>
<BulletList>
<Bullet>
<Text id="547">Add more data and rebuild the collection</Text>
</Bullet>
<Bullet>
<Text id="548">Edit the collection configuration file</Text>
</Bullet>
<Bullet>
<Text id="549">Delete the collection entirely</Text>
</Bullet>
<Bullet>
<Text id="550">Export the collection to CD-ROM.</Text>
</Bullet>
</BulletList>
<Part id="add_new_data">
<Title>
<Text id="551">Add new data</Text>
</Title>
<Content>
<Text id="552">The files that you specify will be added to the collection. Make sure that you do not re-specify files that are already in the collection—otherwise two copies will be included. Files are identified by their full pathname, web pages by their absolute web address. You specify directories and files just as you do when building a new collection.</Text>
<Text id="553">If you add data to a collection and for some reason the building process fails, the old version of the collection remains unchanged.</Text>
</Content>
</Part>
<Part id="edit_configuration_file">
<Title>
<Text id="554">Edit configuration file</Text>
</Title>
<Content>
<Text id="555">Advanced users can edit the collection configuration file, just as they can when a new collection is built.</Text>
</Content>
</Part>
<Part id="delete_the_collection">
<Title>
<Text id="556">Delete the collection</Text>
</Title>
<Content>
<Text id="557">You will be asked to confirm whether you really want to delete the collection. Once deleted, Greenstone can not bring the collection back!</Text>
</Content>
</Part>
<Part id="export_the_collection">
<Title>
<Text id="558">Export the collection</Text>
</Title>
<Content>
<Text id="559">You can export the collection in a form that allows it to be written to a self-contained, self-installing Greenstone CD-ROM for Windows. Because commercial software that creates self-installing CD-ROMs is expensive, this facility includes a homegrown installer module.</Text>
<Text id="560">When you export the collection, the dialogue informs you of the directory name in which the result has been placed. The entire contents of the directory should be written on to CD-ROM using a standard CD-writing utility.</Text>
<Text id="561">The immense variety of different possible Windows configurations has made it difficult for us to test and debug the Greenstone installer under all possible conditions. Although the installer produces CD-ROMs that operate on most Windows systems, it is still under development. If you experience problems and you possess a commercial installation package (e.g. InstallShield), you can use it to create CD-ROMs from the information that Greenstone provides. The above-mentioned export directory contains four files that relate to the installation process, and three subdirectories that contain the complete collection and software. Remove the four files and use InstallShield to make a CD-ROM image that installs these directories and creates a shortcut to the program <i>gsdl\server.exe</i>.</Text>
</Content>
</Part>
</Content>
</Subsection>
<Subsection id="document_formats_1">
<Title>
<Text id="562">Document formats</Text>
</Title>
<Content>
<Text id="563">When building collections, Greenstone processes each different format of source document by seeking a “plugin” that can deal with that particular format. Plugins are specified in the collection configuration file. Greenstone generally uses the filename to determine document formats—for example, <i>foo.txt</i> is processed as a text file, <i>foo.html</i> as html, and <i>foo.doc</i> as a Word file.</Text>
<Text id="564">Here is a summary of the plugins that are available for widely-used document formats. More detail about these plugins, and additional plugins for less commonly-used formats, can be found in the <i>Greenstone Digital Library Developer's Guide</i>.</Text>
<Part id="textplug">
<Title>
<Text id="565">TEXTPlug (*.txt, *.text)</Text>
</Title>
<Content>
<Text id="566">TEXTPlug interprets a plain text file as a simple document. It adds <i>title</i> metadata based on the first line of the file.</Text>
</Content>
</Part>
<Part id="htmlplug">
<Title>
<Text id="567">HTMLPlug (*.htm, *.html; also .shtml, .shm, .asp, .php, .cgi)</Text>
</Title>
<Content>
<Text id="568">HTMLPlug processes html files. It extracts <i>title</i> metadata based on the &lt;title&gt; tag; other metadata expressed using html's metatag syntax can be extracted too. There are many options available with this plugin, documented in the <i>Greenstone Digital Library Developer's Guide</i>.</Text>
</Content>
</Part>
<Part id="wordplug">
<Title>
<Text id="569">WORDPlug (*.doc)</Text>
</Title>
<Content>
<Text id="570">WORDPlug imports Microsoft Word documents. There are many different variants on the Word format—and even Microsoft programs frequently make conversion errors. Greenstone uses independent programs to convert Word files to html. For some older Word formats the system resorts to a simple extraction algorithm that finds all text strings in the input file.</Text>
</Content>
</Part>
<Part id="pdfplug">
<Title>
<Text id="571">PDFPlug (*.pdf)</Text>
</Title>
<Content>
<Text id="572">PDFPlug imports documents in PDF Adobe's Portable Document Format. Like WORDPlug, it uses an independent program, in this case <i>pdftohtml</i>, to convert PDF files to html.</Text>
<Text id="573">As with WORDPlug, by default collections will display the html equivalent of the file when the user clicks the <i>document</i> icon; however, the format strings in the collection configuration file can be adjusted to give the user access to the original PDF file instead, and we recommend that you do this. Again, just replace the <i>&lt;link&gt; 
 &lt;/link&gt;</i> tags by <i>&lt;srclink&gt; 
 &lt;/srclink&gt;</i> ones.</Text>
<Text id="574">The <i>pdftohtml</i> program fails on some PDF files. What happens is that the conversion process takes an exceptionally long time, and often an error message relating to the conversion process appears on the screen. If this occurs, the only solution that we can offer is to remove the offending document from the collection. Also, PDFPlug cannot handle encrypted PDF files.</Text>
</Content>
</Part>
<Part id="psplug">
<Title>
<Text id="575">PSPlug (*.ps)</Text>
</Title>
<Content>
<Text id="576">PSPlug imports documents in PostScript. It works best if a standard Linux program, called <i>ps2ascii</i>, is already installed on your computer. This is available on most Linux installations, but not on Windows. If this program is not available, PSPlug resorts to a simple text extraction algorithm.</Text>
</Content>
</Part>
<Part id="emailplug">
<Title>
<Text id="577">EMAILPlug (*.email)</Text>
</Title>
<Content>
<Text id="578">EMAILPlug imports files containing E-mail, and deals with common E-mail formats such as are used by the Netscape, Eudora, and Unix mail readers. Each source document is examined to see if it contains an E-mail, or several E-mails joined together in one file, and if so its contents are processed. The plugin extracts <i>Subject</i>, <i>To</i>, <i>From</i>, and <i>Date</i> metadata. However, this plugin does not yet handle MIME-encoded E-mails properly—although legible, they often look rather strange.</Text>
</Content>
</Part>
<Part id="zipplug">
<Title>
<Text id="579">ZIPPlug (.gz, .z, .tgz, .taz, .bz, .zip, .tar)</Text>
</Title>
<Content>
<Text id="580">ZIPPlug plugin handles the following compressed and/or archived input formats : gzip (.<i>gz</i>, .<i>z</i>, .<i>tgz</i>, .<i>taz</i>) , bzip (.<i>bz</i>) , zip (.<i>zip</i>, .<i>jar</i>) , and tar (.<i>tar</i>). It relies on the programs <i>gunzip</i>, <i>bunzip</i>, <i>unzip</i>, and <i>tar</i>, which are standard Linux utilities. ZIPPlug is disabled on Windows computers.</Text>
</Content>
</Part>
</Content>
</Subsection>
</Content>
</Section>
</Content>
</Chapter>
<Chapter id="administration">
<Title>
<Text id="581">Administration</Text>
</Title>
<Content>
<Text id="582">An “administrative” facility is included with every Greenstone installation.To access this facility, click the appropriate link on the front page.</Text>
<Text id="583">The entry page, shown in Figure <CrossRef target="Figure" ref="greenstone_administration_facility"/>, gives information about each of the collections offered by the system. Note that <i>all</i> collections are included—for there may be “private” ones that do not appear on the Greenstone home page. With each is given its short name, full name, whether it is publicly displayed, and whether or not it is running. Clicking a particular collection's abbreviation (the first column of links in Figure <CrossRef target="Figure" ref="greenstone_administration_facility"/>) brings up information about that collection, gathered from its collection configuration file and from other internal structures created for that collection. If the collection is both public and running, clicking the collection's full name (the second link) takes you to the collection itself.</Text>
<Text id="584">A collection named <i>wohiex</i>, for <i>Women's History Excerpt</i>, is visible near the bottom of Figure <CrossRef target="Figure" ref="greenstone_administration_facility"/>. Figure <CrossRef target="Figure" ref="information_about_the_womens_history_excerpt_collection"/> shows the information that is displayed when this link is clicked. The first section gives some information from the configuration file, and the size of the collection (about 1000 documents, about a million words, over 6 Mb). The next sections contain internal information related to the communication protocol through which collections are accessed. For example, the filter options for “QueryFilter” show the options and possible values that can be used when querying the collection.</Text>
<Text id="585">The administrative facility also presents configuration information about the installation and allows it to be modified. It facilitates examination of the error logs that record internal errors, and the user logs that record usage. It enables a specified user (or users) to authorize others to build collections and add new material to existing ones. All these facilities are accessed interactively from the menu items at the left-hand side of Figure <CrossRef target="Figure" ref="greenstone_administration_facility"/>.</Text>
<Figure id="greenstone_administration_facility">
<Title>
<Text id="586">Greenstone Administration facility</Text>
</Title>
<File width="335" height="699" url="images/User_Fig_17.png"/>
</Figure>
<Figure id="information_about_the_womens_history_excerpt_collection">
<Title>
<Text id="587">Information about the <i>Women's History Excerpt</i> collection</Text>
</Title>
<File width="331" height="699" url="images/User_Fig_18.png"/>
</Figure>
<Section id="configuration_files">
<Title>
<Text id="588">Configuration files</Text>
</Title>
<Content>
<Text id="589">There are two configuration files that control Greenstone's operation, the site configuration file <i>gsdlsite.cfg</i> and the main configuration file <i>main.cfg</i>.</Text>
<Text id="590">The <i>gsdlsite.cfg</i> file is used to configure the Greenstone software for the site where it is installed. It is designed for keeping configuration options that are particular to a given site. Examples include the name of the directory where the Greenstone software is kept, the http address of the Greenstone system, and whether the <i>fastcgi</i> facility is being used.The entries in this file are described in the <i>Greenstone Digital Library Installation Guide</i>.</Text>
<Text id="591">The <i>main.cfg</i> file contains information that is common to the interface of all collections served by a Greenstone site. It includes the E-mail address of the system maintainer, whether the status and collector pages are enabled, whether logs of user activity are kept, and whether Internet “cookies” are used to identify users.</Text>
</Content>
</Section>
<Section id="logs">
<Title>
<Text id="592">Logs</Text>
</Title>
<Content>
<Text id="593">Three kinds of logs can be examined: usage logs, error logs and initialization logs. The last two are only really of interest to people maintaining the software.</Text>
<Text id="594">All user activity—every page that each user visits—can be recorded by the Greenstone software, though no personal names are included in the logs. Logging, disabled by default, is enabled by including the lines</Text>
<CodeLine>logcgiargs true</CodeLine>
<CodeLine>usecookies true</CodeLine>
<Text id="595">in the main system configuration file. Both options are false by default, so that no logging is done unless they are set. It is the <i>logcgiargs</i> line that actually turns logging on and off. By activating <i>usecookies</i> a unique identification code is assigned to each user, which enables individual user's interactions to be traced through the log file.</Text>
<Text id="596">Each line in the user log records a page visited—even the pages generated to inspect the log files! It contains (a) the IP address of the user's computer, (b) a timestamp in square brackets, (c) the CGI arguments in parentheses, and (d) the name of the user's browser (Netscape is called “Mozilla”). Here is a sample line, split and annotated for ease of reading:</Text>
<CodeLine>/fast-cgi-bin/niupepalibrary</CodeLine>
<CodeLine>(a) its-www1.massey.ac.nz</CodeLine>
<CodeLine>(b) [ Thu Dec07 23:47:00 NZDT2000]</CodeLine>
<CodeLine>(c) (a=p, b=0, bcp=, beu=, c=niupepa, cc=, ccp=0, ccs=0, cl=, cm=, cq2=, d=, e=, er=, f=0, fc=1, gc=0, gg=text, gt=0, h=, h2=, hl=1, hp=, il=l, j=, j2=, k=1, ky=, l=en, m=50, n=, n2=, o=20, p=home, pw=, q=, q2=, r=1, s=0, sp=frameset, t=1, ua=, uan=, ug=, uma=listusers, umc=, umnpw1=, umnpw2=, umpw=, umug=, umun=, umus=, un=, us=invalid, v=0, w=w, x=0, z=130.123.128.4-950647871)</CodeLine>
<CodeLine>(d) “Mozilla/4.08 [en] (Win95; I ;Nav)”</CodeLine>
<Text id="597">The last CGI argument, “z”, is an identification code or “cookie” generated by the user's browser: it comprises the user's IP number followed by the timestamp when they first accessed the digital library.</Text>
<Text id="598">The log file <i>usage.txt</i> is placed in the <i>etc</i> directoryin the Greenstone file structure (see the <i>Greenstone Digital Library Developer's Guide</i>).When logging is enabled, every action by every user is logged. However, only the last 100 entries in the log file are displayed by the <i>usage log</i> link in Figure <CrossRef target="Figure" ref="greenstone_administration_facility"/>.</Text>
</Content>
</Section>
<Section id="user_management">
<Title>
<Text id="599">User management</Text>
</Title>
<Content>
<Text id="600">Greenstone incorporates an authentication scheme which can be used to control access to certain facilities. At the moment this is only used to restrict the people who are allowed to enter the Collectorand certain administration functions. If, for a particular collection, it were necessary to authenticate users before returning information to them, this is possible too—for example, documents could be protected on an individual basis so that they can only be accessed by registered users on presentation of a password. However, no current collections use this facility). Authentication is done by requesting a user name and password, as illustrated in Figure <CrossRef target="Figure" ref="using_the_collector_to_build_a_new_collection"/>.</Text>
<Text id="601">From the administration page users can be listed, new ones added, and old ones deleted. The ability to do this is of course also protected: only users who have administrative privileges can add new users. It is also possible for each user to belong to different “groups”. At present, the only extant groups are “administrator” and “colbuilder”. Members of the first group can add and remove users, and change their groups. Members of the second can access the facilities described above to build new collections and alter (and delete) existing ones.</Text>
<Text id="602">When Greenstone is installed, there is one user called <i>admin</i> who belongs to both groups. The password for this user is set during the installation process. This user can create new names and passwords for users who belong just to the <i>colbuilder</i> group, which is the recommended way of giving other users the ability to build collections. User information is recorded in two databases that are placed in the Greenstone file structure (see the <i>Greenstone Digital Library Developer's Guide</i>).</Text>
</Content>
</Section>
<Section id="technical_information">
<Title>
<Text id="603">Technical information</Text>
</Title>
<Content>
<Text id="604">The links under the <i>Technical information</i> heading show further information on the installation.The <i>general</i> link gives access to technical information, including the directories where things are stored.The <i>protocols</i> menu item gives, for each possible protocol type, information about each of the collections supported by that protocol.</Text>
<Text id="605">Finally, user interface code (called the “receptionist”) uses <i>actions</i> to communicate the wishes of the user. These actions correspond to the CGI argument labeled <i>a</i>. For example, if <i>a=status</i> the receptionist invokes the <i>status</i> action (which displays the status page). A menu item gives access to lists of all actions supported by the system, and another leads to the arguments that these actions take.</Text>
</Content>
</Section>
</Content>
</Chapter>
<Chapter id="appendix_a_software_features">
<Title>
<Text id="606">Appendix A Software features</Text>
</Title>
<Content>
<Table class="hidden" id="table_appendixa">
<Title/>
<TableContent>
<tr>
<th width="132">
<Text id="607"><i>Accessible via web browser</i></Text>
</th>
<th width="397">
<Text id="608">Collections are accessed through a standard web browser (Netscape or Internet Explorer) and combine easy-to-use browsing with powerful search facilities.</Text>
</th>
</tr>
<tr>
<th width="132">
<Text id="609"><i>Full-text and fielded search</i></Text>
</th>
<th width="397">
<Text id="610">The user can search the full text of the documents, or choose between indexes built from different parts of the documents. For example, some collections have an index of full documents, an index of sections, an index of titles, and an index of authors, each of which can be searched for particular words or phrases. Results can be ranked by relevance or sorted by a metadata element.</Text>
</th>
</tr>
<tr>
<th width="132">
<Text id="611"><i>Flexible browsing facilities</i></Text>
</th>
<th width="397">
<Text id="612">The user can browse lists of authors, lists of titles, lists of dates, classification structures, and so on. Different collections may offer different browsing facilities and even within a collection, a broad variety of browsing interfaces are available. Browsing and searching interfaces are constructed during the building process, according to collection configuration information.</Text>
</th>
</tr>
<tr>
<th width="132">
<Text id="613"><i>Creates access structures automatically</i></Text>
</th>
<th width="397">
<Text id="614">The Greenstone software creates information collections that are very easy to maintain. All searching and browsing structures are built directly from the documents themselves. No links are inserted by hand, but existing links in originals are maintained. This means that if new documents in the same format become available, they can be merged into the collection automatically. Indeed, for some collections this is done by processes that wake up regularly, scout for new material, and rebuild the indexes—all without manual intervention.</Text>
</th>
</tr>
<tr>
<th width="132">
<Text id="615"><i>Makes use of available metadata</i></Text>
</th>
<th width="397">
<Text id="616">Metadata, which is descriptive information such as author, title, date, keywords, and so on, may be associated with each document, or with individual sections within documents. Metadata is used as the raw material for browsing indexes. It must be either provided explicitly or derivable automatically from the source documents. The Dublin Core metadata scheme is used for most electronic documents, however, provision is made for other schemes.</Text>
</th>
</tr>
<tr>
<th width="132">
<Text id="617"><i>Plugins extend the system's capabilities</i></Text>
</th>
<th width="397">
<Text id="618">In order to accommodate different kinds of source documents, the software is organized in such a way that “plugins” can be written for new document types. Plugins currently exist for plain text, html, Word, PDF, PostScript, E-mail, some proprietary formats, and for recursively traversing directory structures and compressed archives containing such documents. A collection may have source documents in different forms. In order to build browsing indexes from metadata, an analogous scheme of “classifiers” is used: classifiers create browsing indexes of various kinds based on metadata.</Text>
</th>
</tr>
<tr>
<th width="132">
<Text id="619"><i>Designed for multi-gigabyte collections</i></Text>
</th>
<th width="397">
<Text id="620">Collections can contain millions of documents, making the Greenstone system suitable for collections up to several gigabytes.</Text>
</th>
</tr>
<tr>
<th width="132">
<Text id="621"><i>Documents can be in any language</i></Text>
</th>
<th width="397">
<Text id="622">Unicode is used throughout the software, allowing any language to be processed in a consistent manner. To date, collections have been built containing French, Spanish, Maori, Chinese, Arabic and English. On-the-fly conversion is used to convert from Unicode to an alphabet supported by the user's web browser.</Text>
</th>
</tr>
<tr>
<th width="132">
<Text id="623"><i>User interface available in multiple languages</i></Text>
</th>
<th width="397">
<Text id="624">The interface can be presented in multiple languages. Currently, the interface is available in Arabic, Chinese, Dutch, English, French, German, Maori, Portuguese, and Spanish. New languages can be added easily.</Text>
</th>
</tr>
<tr>
<th width="132">
<Text id="625"><i>Collections can contain text, pictures, audio, and video</i></Text>
</th>
<th width="397">
<Text id="626">Greenstone collections can contain text, pictures, audio and video clips. Most non-textual material is either linked in to the textual documents or accompanied by textual descriptions (such as figure captions) to allow full-text searching and browsing. However, the architecture permits implementation of plugins and classifiers even for non-textual data.</Text>
</th>
</tr>
<tr>
<th width="132">
<Text id="627"><i>Uses advanced compression techniques</i></Text>
</th>
<th width="397">
<Text id="628">Compression techniques are used to reduce the size of the indexes and text. Reducing the size of the indexes via compression has the added advantage of increasing the speed of text retrieval.</Text>
</th>
</tr>
<tr>
<th width="132">
<Text id="629"><i>Administrative function provided</i></Text>
</th>
<th width="397">
<Text id="630">An “administrative” function enables specified users to authorize new users to build collections, protect documents so that they can only be accessed by registered users on presentation of a password, examine the composition of all collections, and so on. Logs of user activity can record all queries made to every Greenstone collection.</Text>
</th>
</tr>
<tr>
<th width="132">
<Text id="631"><i>New collections appear dynamically</i></Text>
</th>
<th width="397">
<Text id="632">Collections can be updated and new ones brought on-line at any time, without bringing the system down; the process responsible for the user interface will notice (through periodic polling) when new collections appear and add them to the list presented to the user.</Text>
</th>
</tr>
<tr>
<th width="132">
<Text id="633"><i>Collections can be published on the Internet or on CD-ROM</i></Text>
</th>
<th width="397">
<Text id="634">The software can be used to serve collections over the World-Wide Web. Greenstone collections can be made available, in precisely the same form, on CD-ROM. The user interface is through a standard web browser (Netscape is provided on each disk), and the interaction is identical to accessing the collection on the web—except that response times are more predictable. The CD-ROMs run under all versions of the Windows operating system.</Text>
</th>
</tr>
<tr>
<th width="132">
<Text id="635"><i>Collections can be distributed amongst different computers</i></Text>
</th>
<th width="397">
<Text id="636">A flexible process structure allows different collections to be served by different computers, yet be presented to the user in the same way, on the same web page, as part of the same digital library.</Text>
</th>
</tr>
<tr>
<th width="132">
<Text id="637"><i>Operates on both Windows and Unix</i></Text>
</th>
<th width="397">
<Text id="638">Greenstone runs under both Windows (3.1/3.11, 95/98/Me, NT/2000) and Unix (Linux and SunOS). Any of these systems can be used as a webserver. Collections cannot be built on low-end Windows systems (3.1/3.11), but pre-built collections can be transferred to them.</Text>
</th>
</tr>
<tr>
<th width="132">
<Text id="639"><i>What you get with Greenstone</i></Text>
</th>
<th width="397">
<Text id="640">The Greenstone Digital Library is open-source software, available from the New Zealand Digital Library (<i>nzdl.org</i>) under the terms of the Gnu General Public License. The software includes everything described above: web serving, CD-ROM creation, collection building, multi-lingual capability, plugins and classifiers for a variety of different source document types. It includes an autoinstall feature to allow easy installation on both Windows and Unix. In the spirit of open-source software, users are encouraged to contribute modifications and enhancements.</Text>
</th>
</tr>
</TableContent>
</Table>
</Content>
</Chapter>
<Chapter id="appendix_b_glossary_of_terms">
<Title>
<Text id="641">Appendix B Glossary of terms</Text>
</Title>
<Content>
<Table id="appendixb" class="hidden">
<Title/>
<TableContent>
<tr>
<th width="123">
<Text id="642"><b>Term</b></Text>
</th>
<th width="406">
<Text id="643"><b>Meaning</b></Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="644"><i>autoconf</i></Text>
</th>
<th width="406">
<Text id="645">Unix program used to configure the Greenstone software installation package to suit your system</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="646"><i>Autorun</i></Text>
</th>
<th width="406">
<Text id="647">Windows feature that starts a program automatically whenever a CD-ROM is inserted</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="648">Boolean query</Text>
</th>
<th width="406">
<Text id="649">Query to an information retrieval system that may contain AND, OR, NOT</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="650">Browsing</Text>
</th>
<th width="406">
<Text id="651">Accessing a collection by scanning an organized list of metadata values associated with the documents (such as author, title, date, keywords)</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="652"><i>buildcol.pl</i></Text>
</th>
<th width="406">
<Text id="653">Greenstone program used to build collections</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="654">Building</Text>
</th>
<th width="406">
<Text id="655">Process of creating the indexing and browsing structures that are used to access a collection</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="656">C++</Text>
</th>
<th width="406">
<Text id="657">Programming language in which the majority of the Greenstone software is written</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="658">Casefolding</Text>
</th>
<th width="406">
<Text id="659">Making uppercase and lowercase words look the same, for searching purposes</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="660">CGI</Text>
</th>
<th width="406">
<Text id="661">Common Gateway Interface, a scheme that allows users to activate programs on the host computer by clicking on web pages</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="662">CGI script</Text>
</th>
<th width="406">
<Text id="663">Code associated with a button, menu, or link on a web page that specifies what the host computer is to do when it is clicked</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="664"><i>cgi-bin</i></Text>
</th>
<th width="406">
<Text id="665">Directory in which CGI scripts are stored</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="666">Classifier</Text>
</th>
<th width="406">
<Text id="667">Greenstone code module that examines document metadata to form an index for browsing</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="668">Collection</Text>
</th>
<th width="406">
<Text id="669">Set of documents that are brought together under a uniform searching and browsing interface</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="670">Collection configuration file</Text>
</th>
<th width="406">
<Text id="671">File that specifies how a collection is to be imported and built, what indexes and language interfaces are to be provided, etc.</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="672">Collection server</Text>
</th>
<th width="406">
<Text id="673">Program responsible for providing access to a collection when it is being used</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="674">Configuration file</Text>
</th>
<th width="406">
<Text id="675">See collection configuration file, main configuration file, site configuration file</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="676">CVS</Text>
</th>
<th width="406">
<Text id="677">Concurrent Versioning System, a scheme for maintaining source code used throughout Greenstone</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="678"><i>db2txt</i></Text>
</th>
<th width="406">
<Text id="679">Greenstone tool for viewing a GDBM database as text (see GDBM)</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="680">Demo collection</Text>
</th>
<th width="406">
<Text id="681">A subset of the Humanities Development Library, distributed with the Greenstone software and used for illustration in this tutorial</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="682">Digital library</Text>
</th>
<th width="406">
<Text id="683">Collection of digital objects (text, audio, video), along with methods for access and retrieval, and for selection, organization, and maintenance</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="684">DL</Text>
</th>
<th width="406">
<Text id="685">Development Library, A Greenstone collection of humanitarian information for developing countries</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="686">Document</Text>
</th>
<th width="406">
<Text id="687">Basic unit from which digital library collections are constructed; it may include text, graphics, sound, video, etc.</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="688">Dublin core</Text>
</th>
<th width="406">
<Text id="689">A standard way of describing metadata</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="690">Fast CGI</Text>
</th>
<th width="406">
<Text id="691">Facility that allows CGI scripts to remain continuously active so that they do not have to be restarted from scratch every time they are invoked</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="692">Filter program</Text>
</th>
<th width="406">
<Text id="693">That part of a Greenstone collection server that implements querying and browsing operations</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="694">Format string</Text>
</th>
<th width="406">
<Text id="695">A string that specifies how documents and other listings are to be displayed in Greenstone</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="696">GB-encoding</Text>
</th>
<th width="406">
<Text id="697">Standard way of encoding the Chinese language</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="698">GDBM</Text>
</th>
<th width="406">
<Text id="699">Gnu DataBase Manager, a program used within the Greenstone software to store metadata for each document</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="700">GIMP</Text>
</th>
<th width="406">
<Text id="701">Gnu Image-Manipulation Program used (on Unix) to create icons in Greenstone</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="702">GML</Text>
</th>
<th width="406">
<Text id="703">Greenstone Markup Language, an XML-compliant format used for storing documents internally</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="704">Gnu license</Text>
</th>
<th width="406">
<Text id="705">Software license that permits users to copy and distribute computer programs freely, and modify them—so long as all modifications are made publicly available</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="706">Greenstone</Text>
</th>
<th width="406">
<Text id="707">The name of this digital library software</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="708">GSDL</Text>
</th>
<th width="406">
<Text id="709">Abbreviation for Greenstone Digital Library</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="710"><i>%GSDLHOME%</i></Text>
</th>
<th width="406">
<Text id="711">Operating system variable that represents the top-level directory in which all Greenstone programs and collections are stored (<i>$GSDLHOME</i> on Unix systems)</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="712"><i>%GSDLOS%</i></Text>
</th>
<th width="406">
<Text id="713">Operating system variable that represents the operating system currently being used (<i>$GSDLOS</i> on Unix systems)</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="714"><i>hashfile</i></Text>
</th>
<th width="406">
<Text id="715">Greenstone program used at import or build time to generate the OID of each document</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="716">HTML</Text>
</th>
<th width="406">
<Text id="717">HyperText Markup Language, the language in which web documents are written</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="718"><i>import.pl</i></Text>
</th>
<th width="406">
<Text id="719">Greenstone program used to import documents</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="720">Importing</Text>
</th>
<th width="406">
<Text id="721">Process of bringing collections of documents into the Greenstone system</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="722">Index</Text>
</th>
<th width="406">
<Text id="723">Information structure that is used for searching or browsing a collection</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="724">InstallShield</Text>
</th>
<th width="406">
<Text id="725">Windows program, used by Greenstone CD-ROMs, that allows a system to be installed from a CD-ROM</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="726">Main configuration file</Text>
</th>
<th width="406">
<Text id="727">File that contains specifications common to all collections served by this site</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="728">Metadata</Text>
</th>
<th width="406">
<Text id="729">Descriptive data such as author, title, date, keywords, and so on, that is associated with a document (or document collection)</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="730">MG</Text>
</th>
<th width="406">
<Text id="731">Managing Gigabytes, a program used by the Greenstone system for full-text indexing, that incorporates compression techniques (see Witten, I.H., Moffat, A. and Bell, T. <i>Managing Gigabytes: compressing and indexing documents and images</i>, Morgan Kaufmann, second edition, 1999)</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="732"><i>mgbuild</i></Text>
</th>
<th width="406">
<Text id="733">MG program for building a compressed full-text index</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="734"><i>mgquery</i></Text>
</th>
<th width="406">
<Text id="735">MG program for querying a compressed full-text index</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="736"><i>mkcol.pl</i></Text>
</th>
<th width="406">
<Text id="737">Greenstone program that creates and initializes the directory structure for a new collection</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="738">New Zealand <br/>Digital Library Project</Text>
</th>
<th width="406">
<Text id="739">Research project in the Computer Science Department at the University of Waikato, New Zealand, that created the Greenstone software (<i>nzdl.org</i>)</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="740">OID</Text>
</th>
<th width="406">
<Text id="741">Object Identifier, a unique identification code associated with a document</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="742">Perl</Text>
</th>
<th width="406">
<Text id="743">Programming language used for many of the text-processing operations that occur during the building process</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="744">Ping</Text>
</th>
<th width="406">
<Text id="745">Message sent to a system to determine whether it is running or not</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="746">Plugin</Text>
</th>
<th width="406">
<Text id="747">Code module for handling documents of different formats, used during the importing and building processes</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="748">Protocol</Text>
</th>
<th width="406">
<Text id="749">Set of conventions by which a Greenstone receptionist communicates with a collection server</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="750">Ranked query</Text>
</th>
<th width="406">
<Text id="751">Natural-language query to an information retrieval system, for which the documents that match the query are sorted in order of relevance</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="752">Receptionist</Text>
</th>
<th width="406">
<Text id="753">Program that organizes the Greenstone user interface</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="754">RTF</Text>
</th>
<th width="406">
<Text id="755">Rich Text Format, a standard format for interchange of text documents</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="756">Searching</Text>
</th>
<th width="406">
<Text id="757">Accessing a collection through a full-text search of its contents (or parts of contents, such as section titles)</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="758">Server</Text>
</th>
<th width="406">
<Text id="759">See Collection server and Web server</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="760"><i>setup.bat, setup.sh, setup.csh</i></Text>
</th>
<th width="406">
<Text id="761">Script used to set up your environment to recognize the Greenstone software</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="762">Site configuration file</Text>
</th>
<th width="406">
<Text id="763">File that contains specifications used to configure the Greenstone software for the site on which it is installed</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="764">Stemming</Text>
</th>
<th width="406">
<Text id="765">Stripping endings off a query term to make it more general</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="766">STL</Text>
</th>
<th width="406">
<Text id="767">Standard template library, a widely-available library of C++ code developed by Silicon Graphics</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="768">txt2db</Text>
</th>
<th width="406">
<Text id="769">Greenstone program used at build time to create the GDBM database</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="770">Unicode</Text>
</th>
<th width="406">
<Text id="771">Standard scheme for representing the character sets used in the world's languages</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="772">UNU</Text>
</th>
<th width="406">
<Text id="773">The United Nations University; also used to refer to a Greenstone collection created for that organization</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="774">Web server</Text>
</th>
<th width="406">
<Text id="775">Standard program that computers use to make information accessible over the World Wide Web</Text>
</th>
</tr>
<tr>
<th width="123">
<Text id="776">XML</Text>
</th>
<th width="406">
<Text id="777">A standard format for structured documents and data on the web (the Greenstone Markup Language is an XML-compliant format)</Text>
</th>
</tr>
</TableContent>
</Table>
</Content>
</Chapter>
<FootnoteList>
<Footnote id="1">
<Text id="778">This option is disabled if an element of the same name already exists.</Text>
</Footnote>
</FootnoteList>
</Manual>