Changeset 29718 for other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/HASHeaa2/9d2e0811.dir/doc.xml
- Timestamp:
- 2015-02-05T16:42:41+13:00 (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/HASHeaa2/9d2e0811.dir/doc.xml
r29404 r29718 9 9 <Metadata name="GENERATOR">wvWare/wvWare version 1.2.4</Metadata> 10 10 <Metadata name="Title">Greenstone: A Comprehensive Open-Source</Metadata> 11 <Metadata name="URL">http://Scratch/ak19/gs2-svn-22Oct2014/collect/Word-PDF-Basic/tmp/14 14468443_2/word03.html</Metadata>12 <Metadata name="UTF8URL">http://Scratch/ak19/gs2-svn-22Oct2014/collect/Word-PDF-Basic/tmp/14 14468443_2/word03.html</Metadata>11 <Metadata name="URL">http://Scratch/ak19/gs2-svn-22Oct2014/collect/Word-PDF-Basic/tmp/1423107672_3/word03.html</Metadata> 12 <Metadata name="UTF8URL">http://Scratch/ak19/gs2-svn-22Oct2014/collect/Word-PDF-Basic/tmp/1423107672_3/word03.html</Metadata> 13 13 <Metadata name="gsdlsourcefilename">import/word03.doc</Metadata> 14 <Metadata name="gsdlconvertedfilename">tmp/14 14468443_2/word03.html</Metadata>14 <Metadata name="gsdlconvertedfilename">tmp/1423107672_3/word03.html</Metadata> 15 15 <Metadata name="OrigSource">word03.html</Metadata> 16 16 <Metadata name="Source">word03.doc</Metadata> … … 29 29 <Metadata name="dc.Title">Greenstone: A comprehensive open-source digital library software system - doc</Metadata> 30 30 <Metadata name="Identifier">HASHeaa29d2e081149673150f3</Metadata> 31 <Metadata name="lastmodified">14 14468441</Metadata>32 <Metadata name="lastmodifieddate">201 41028</Metadata>33 <Metadata name="oailastmodified">14 14468444</Metadata>34 <Metadata name="oailastmodifieddate">201 41028</Metadata>31 <Metadata name="lastmodified">1423107619</Metadata> 32 <Metadata name="lastmodifieddate">20150205</Metadata> 33 <Metadata name="oailastmodified">1423107673</Metadata> 34 <Metadata name="oailastmodifieddate">20150205</Metadata> 35 35 <Metadata name="assocfilepath">HASHeaa2/9d2e0811.dir</Metadata> 36 36 <Metadata name="gsdlassocfile">word030.png:image/png:</Metadata> … … 130 130 </table> 131 131 132 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">133 134 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">132 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 133 134 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 135 135 <b></b> 136 136 </p></div> … … 138 138 139 139 140 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">141 142 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">140 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 141 142 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 143 143 <b></b> 144 144 </p></div> … … 158 158 159 159 160 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">161 162 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">160 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 161 162 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 163 163 This paper describes the Greenstone digital library software, a comprehensive, open-source system for the construction and presentation of information collections. Collections built with Greenstone offer effective full-text searching and metadata-based browsing facilities that are attractive and easy to use. Moreover, they are easily maintainable and can be augmented and rebuilt entirely automatically. The system is extensible: software &ldquo;plugins&rdquo; accommodate different document and metadata types. 164 164 </p></div> … … 174 174 175 175 176 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">177 178 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">176 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 177 178 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 179 179 Notwithstanding intense research activity in the digital library field during the second half of the 1990s, comprehensive software systems for creating digital libraries are not widely available. In fact, the usual solution when creating a digital library is also the most obvious&mdash;just put it on the Web. But consider how much effort is involved in constructing a Web site for a digital library. To be effective it needs to be visually attractive and ergonomically easy to use, incorporate convenient and powerful searching capabilities, and offer rich and natural browsing facilities. Above all it must be easy to maintain and augment, which presents a significant challenge if any manual organization is involved. 180 180 </p></div> … … 182 182 183 183 184 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">185 186 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">184 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 185 186 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 187 187 The alternative is to automate these activities through software tools. But the broad scope of digital library requirements makes this a daunting prospect. Ideally the software should incorporate facilities ranging from multilingual information retrieval to distributed computing protocols, from interoperability to search engine technology, from metadata standards to multiformat document parsing, from multimedia to multiple operating systems, from Web browsers to plug-and-play DVDs. 188 188 </p></div> … … 190 190 191 191 192 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">193 194 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">192 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 193 194 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 195 195 The Greenstone Digital Library Software from the New Zealand Digital Library (NZDL) project tackles this issue by providing a new way of organizing information and making it available over the Internet. A <i>collection</i> of information comprises several (typically several thousand, or several million) <i>documents</i>, and a uniform interface is provided to all documents in a collection. A library may include many different collections, each organized differently&mdash;though there is a strong family resemblance in how collections are presented. 196 196 </p></div> … … 198 198 199 199 200 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">201 202 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">200 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 201 202 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 203 203 Making information available using this system is far more than &ldquo;just putting it on the Web.&rdquo; The collection becomes maintainable, searchable, and browsable. Each collection, prior to presentation, undergoes a &ldquo;building&rdquo; process that, once established, is completely automatic. This process creates all the structures that are used at run-time for accessing the collection. Searching is based on various indexes, while browsing is based on various metadata; support structures for both are created during the building operation. When new material appears it can be fully incorporated into the collection by rebuilding. 204 204 </p></div> … … 206 206 207 207 208 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">209 210 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">208 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 209 210 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 211 211 To address the exceptionally broad demands of digital libraries, the system is public and extensible. It is issued under the Gnu public license and, in the spirit of open-source software, users are invited to contribute modifications and enhancements. Only through an international cooperative effort will digital library software become sufficiently comprehensive to meet the world's needs. Currently the Greenstone software is used at sites in Canada, Germany, New Zealand, Romania, UK, and the US, and collections range from newspaper articles to technical documents, from educational journals to oral history, from visual art to folksongs. The software has been used for collections in many different languages, and for CD-ROMs that have been published by the United Nations and other humanitarian agencies in Belgium, France, Japan, and the US for distribution in developing countries (Humanity Libraries, 1998; PAHO, 1999; UNESCO, 1999; UNU, 1998). Further details can be obtained from <i>www.nzdl.org</i>. 212 212 </p></div> … … 230 230 231 231 232 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">233 234 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">232 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 233 234 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 235 235 This paper sets the scene with a brief discussion of what a digital library is. We then give an overview of the facilities offered by Greenstone and show how end users find information in collections. Next we describe the files and directories involved in a collection, and then discuss the processes of updating existing collections and creating new ones, including extending the software to provide new facilities. We conclude with an overview of related work. 236 236 </p></div> … … 246 246 247 247 248 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">249 250 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">248 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 249 250 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 251 251 Ten definitions of the term &ldquo;digital library&rdquo; have been culled from the literature by Fox (1998), and their spirit is captured in the following brief characterization: 252 252 </p></div> … … 262 262 263 263 264 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">265 266 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">264 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 265 266 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 267 267 (Akscyn and Witten, 1998). Lesk (1998) views digital libraries as &ldquo;organized collections of digital information,&rdquo; and wisely recommends that they articulate the principles governing what is included and how the collection is organized. 268 268 </p></div> … … 270 270 271 271 272 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">273 274 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">272 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 273 274 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 275 275 Digital libraries are generally distinguished from the World-Wide Web, the essential difference being in selection and organization. But they are not generally distinguished from a web <i>site</i>: indeed, virtually all extant digital libraries manifest themselves as a web site. Hence the obvious question: to make a digital library, why not just put the information on the Web? 276 276 </p></div> … … 278 278 279 279 280 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">281 282 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">280 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 281 282 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 283 283 But we make a distinction between a digital library and a web site that lies at the heart of our software design: one should easily be able to add new material to a library without having to integrate it manually or edit its content in any way. Once added, new material should immediately become a first-class component of the library. And what permits it to be integrated into existing searching and browsing structures without any manual intervention is <i>metadata</i>. This provides sufficient focus to the concept of &ldquo;digital library&rdquo; to support the development of a construction kit. 284 284 </p></div> … … 294 294 295 295 296 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">297 298 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">296 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 297 298 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 299 299 Information collections built by Greenstone combine extensive full-text search facilities with browsing indexes based on different metadata types. There are several ways for users to find information, although they differ between collections depending on the metadata available and the collection design. Typically you can <i>search for particular words</i> that appear in the text, or within a section of a document, or within a title or section heading. You can <i>browse documents by title</i>: just click on the displayed book icon to read it. You can <i>browse documents by subject</i>. Subjects are represented by bookshelves: just click on a shelf to see the books. Where appropriate, documents come complete with a table of contents (constructed automatically): you can click on a chapter or subsection to open it, expand the full table of contents, or expand the full document. 300 300 </p></div> … … 302 302 303 303 304 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">305 306 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">304 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 305 306 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 307 307 An example of searching is shown in Figure 1 where documents in the Global Help Project's Humanity Development Library (HDL) are being searched for chapters matching the word <i>butterfly</i>. In Figure 2 the same collection is being browsed by subject: by clicking on the bookshelf icons the user has discovered an item under Section 16, Animal Husbandry. Pursuing an interest in butterfly farming, the user selects a book by clicking on its book icon. In Figure 3 the front cover of the book is displayed as a graphic on the left, and the automatically constructed table of contents appears at the start of the document. The current focus, <i>Introduction and Summary</i>, is shown in bold in the table of contents with its text starting further down the page. 308 308 </p></div> … … 310 310 311 311 312 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">313 314 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">312 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 313 314 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 315 315 In accordance with Lesk's advice, a statement of purpose and coverage accompanies each collection, along with an explanation of how it is organized (Figure 1 shows the start of this). A distinction is made between <i>searching</i> and <i>browsing</i>. Searching is full-text, and&mdash;depending on the collection's design&mdash;the user can choose between indexes built from different parts of the documents, or from different metadata. Some collections have an index of full documents, an index of sections, an index of paragraphs, an index of titles, and an index of section headings, each of which can be searched for particular words or phrases. Browsing involves data structures created from metadata that the user can examine: lists of authors, lists of titles, lists of dates, hierarchical classification structures, and so on. Data structures for both browsing and searching are built according to instructions in a configuration file, which controls both building and serving the collection. Sample configuration files are discussed below. 316 316 </p></div> … … 318 318 319 319 320 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">321 322 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">320 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 321 322 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 323 323 324 324 </p></div> … … 342 342 343 343 344 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">345 346 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">344 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 345 346 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 347 347 Rich browsing facilities can be provided by manually linking parts of documents together and building explicit indexes and tables of contents. However, manually-created linking becomes difficult to maintain, and often falls into disrepair when a collection expands. The Greenstone software takes a different tack: it facilitates <i>maintainability</i> by creating all searching and browsing structures automatically from the documents themselves. No links are inserted by hand. This means that when new documents in the same format become available, they can be added automatically. Indeed, for some collections this is done by processes that wake up regularly, scout for new material, and rebuild the indexes&mdash;all without manual intervention. 348 348 </p></div> … … 350 350 351 351 352 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">353 354 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">352 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 353 354 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 355 355 Collections comprise many documents: thousands, tens of thousands, or even millions. Each document may be hierarchically organized into <i>sections</i> (subsections, sub-subsections, and so on). Each section comprises one or more <i>paragraphs</i>. Metadata such as author, title, date, keywords, and so on, may be associated with documents, or with individual sections of documents. This is the raw material for indexes. It must either be provided explicitly for each document and section (for example, in an accompanying spreadsheet) or be derivable automatically from the source documents. Metadata is converted to Dublin Core and stored with the document for internal use. 356 356 </p></div> … … 358 358 359 359 360 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">361 362 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">360 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 361 362 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 363 363 In order to accommodate different kinds of source documents, the software is organized so that &ldquo;plugins&rdquo; can be written for new document types. Plugins exist for plain text documents, HTML documents, email documents, and bibliographic formats. Word documents are handled by saving them as HTML; PostScript ones by applying a preprocessor (Nevill-Manning <i>et al</i>., 1998). Specially written plugins also exist for proprietary formats such as that used by the BBC archives department. A collection may have source documents in different forms: it is just a matter of specifying all the necessary plugins. In order to build browsing indexes from metadata, an analogous scheme of &ldquo;classifiers&rdquo; is used: classifiers create indexes of various kinds based on metadata. Source documents are brought into the Greenstone system through a process called <i>importing</i>, which uses the plugins and classifiers specified in the collection configuration file. 364 364 </p></div> … … 366 366 367 367 368 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">369 370 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">368 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 369 370 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 371 371 The international Unicode character set is used throughout, so documents&mdash;and interfaces&mdash;can be written in any language. Collections have so far been produced in English, French, Spanish, German, Maori, Chinese, and Arabic. The NZDL Web site provides numerous examples. Collections can contain text, pictures, and even audio and video clips; a text-only version of the interface is also provided to accommodate visually impaired users. Compression technology is used to ensure best use of storage (Witten <i>et al</i>., 1999). Most non-textual material is either linked to textual documents or accompanied by textual descriptions (such as photo captions) to allow full-text searching and browsing. However, the architecture permits the implementation of plugins and classifiers even for non-textual data. 372 372 </p></div> … … 374 374 375 375 376 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">377 378 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">376 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 377 378 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 379 379 The system includes an &ldquo;administrative&rdquo; function whereby specified users can examine the composition of all collections, protect documents so that they can only be accessed by registered users on presentation of a password, and so on. Logs of user activity are kept that record all queries made to every Greenstone collection (though this facility can be disabled). 380 380 </p></div> … … 382 382 383 383 384 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">385 386 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">384 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 385 386 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 387 387 Although primarily designed for Internet access over the World-Wide Web, collections can be made available, in precisely the same form, on CD-ROM. In either case they are accessed through any Web browser. Greenstone CD-ROMs operate on a standalone PC under Windows 3.X, 95, 98, and NT, and the interaction is identical to accessing the collection on the Web&mdash;except that response is faster and more predictable. The requirement to operate on early Windows systems is one that plagues the software design, but is crucial for many users&mdash;particularly those in underdeveloped countries seeking access to humanitarian aid collections. If the PC is connected to a network (intranet or Internet), a custom-built Web server provided on each CD makes exactly the same information available to others through their standard Web browser. The use of compression ensures that the greatest possible volume of information can be packed on to a CD-ROM. 388 388 </p></div> … … 390 390 391 391 392 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">393 394 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">392 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 393 394 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 395 395 The collection-serving software operates under Unix and Windows NT, and works with standard Web servers. 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, even as part of the same collection (McNab and Witten, 1998). Existing 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. 396 396 </p></div> … … 422 422 423 423 424 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">425 426 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">424 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 425 426 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 427 427 Greenstone digital library systems generally include several separate collections. A home page allows you to select a collection; in addition, each collection has its own &ldquo;about&rdquo; page that gives you information about how the collection is organized and the principles governing what is included. 428 428 </p></div> … … 430 430 431 431 432 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">433 434 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">432 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 433 434 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 435 435 All icons in the screenshots of Figures 1-4 are clickable. Those icons at the top of the page return to the home page, provide help text, and allow you to set user interface and searching preferences. The navigation bar underneath gives access to the searching and browsing facilities, which differ from one collection to another. 436 436 </p></div> … … 438 438 439 439 440 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">441 442 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">440 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 441 442 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 443 443 Each of the five buttons provides a different way to find information. You can <i>search for particular words</i> that appear in the text from the &ldquo;search&rdquo; page (or from the &ldquo;about&rdquo; page of Figure 1). This collection contains indexes of chapters, section titles, and entire books. The default search interface is a simple one, suitable for casual users; advanced searching&mdash;which allows full Boolean expressions, phrase searching, case and stemming control&mdash;can be enabled from the <i>Preferences</i> page. 444 444 </p></div> … … 446 446 447 447 448 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">449 450 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">448 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 449 450 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 451 451 This collection has four browsable metadata indexes. You can <i>access publications by subject</i> by clicking the <i>subjects</i> button, which brings up a list of subjects, represented by bookshelves (Figure 2). You can <i>access publications by title</i> by clicking <i>titles a-z</i> (Figure 4), which brings up a list of books in alphabetic order. You can <i>access publications by organization</i> (i.e. Dublin Core &ldquo;publisher&rdquo;), bringing up a list of organizations. You can <i>access publications by &ldquo;how to&rdquo; listing</i>, yielding a list of hints defined by the collection's editors. We use the Dublin Core as a base and extend it in an <i>ad hoc</i> manner to accommodate the individual requirements of collection designers. 452 452 </p></div> … … 462 462 463 463 464 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">465 466 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">464 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 465 466 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 467 467 When a new collection is created or material is added to an existing one, the original source documents are first brought into the system through a process known as &ldquo;importing.&rdquo; This involves converting documents into a simple HTML-like format known as GML (for &ldquo;Greenstone Markup Language&rdquo;), which includes any metadata associated with the document. Documents are assumed to be in the Unicode UTF-8 code (of which the ASCII characters form a subset). 468 468 </p></div> … … 478 478 479 479 480 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">481 482 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">480 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 481 482 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 483 483 There is a separate directory for each collection, which contains five subdirectories: the original raw material (<i>import</i>), the GML files created from this (<i>archives</i>), the final collection as it is served to users (<i>index</i>), a directory for use during the building process (<i>building</i>), and one for any supporting files (<i>etc</i>)&mdash;including the configuration file that controls the collection creation procedure. Additional files might be required: for example, building a hierarchy of classifications requires a data file of sub-classifications. 484 484 </p></div> … … 494 494 495 495 496 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">497 498 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">496 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 497 498 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 499 499 In order to identify documents internally, a unique object identifier or OID is assigned to each original source document when it is imported (formed by hashing the content, to overcome file duplication effects caused by mirroring) and stored as metadata within that document. It is important that OIDs persist throughout the index-building process&mdash;so that a user's search history is unaffected by rebuilding the collection. OIDs are assigned by hashing the contents of the original source document. 500 500 </p></div> … … 502 502 503 503 504 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">505 506 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">504 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 505 506 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 507 507 Once imported, each document is stored in its own subdirectory of <i>archives</i>, along with any associated files&mdash;for example, images. To ensure compatibility with Windows 3.0, only eight characters are used in directory and file names, which causes annoying but essentially trivial complications. 508 508 </p></div> … … 518 518 519 519 520 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">521 522 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">520 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 521 522 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 523 523 The GML format imposes a limited amount of structure on documents. Documents are divided into paragraphs. They can be split hierarchically into sections and subsections. OIDs are extended to identify these components by appending numbers, separated by periods, to a document's OID. When a book is read, its section hierarchy is visible as the table of contents (Figure 3). Chapters, sections, subsections, and pages are all implemented simply as &ldquo;sections&rdquo; within the document. In some collections documents do not have a hierarchical subsection structure, but are split into pages to permit browsing within a retrieved document. 524 524 </p></div> … … 526 526 527 527 528 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">529 530 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">528 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 529 530 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 531 531 The document structure is used for searchable indexes. There are three levels of index: <i>documents</i>, <i>sections</i>, and <i>paragraphs</i>, corresponding to the distinctions that GML makes&mdash;the hierarchical structure is flattened for the purposes of creating these indexes. Indexes can be of text, or metadata, or any combination. Thus you can create a searchable index of section titles, and/or authors, and/or document descriptions, as well as the document text. 532 532 </p></div> … … 558 558 559 559 560 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">561 562 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">560 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 561 562 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 563 563 Updating an existing collection with new files in the same format is easy. For example, the raw material for the HDL is supplied in the form of HTML files marked up with &lt;&lt;TOC&gt;&gt; tags to split books into sections and subsections, and &lt;&lt;I&gt;&gt; tags to indicate where an image is to be inserted. For each book in the library there is a directory that contains a single HTML file representing the book, and separate files containing the associated images. An accompanying spreadsheet file contains the classification hierarchy; this is converted to a simple file format (using Excel's <i>Save As</i> command). 564 564 </p></div> … … 566 566 567 567 568 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">569 570 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">568 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 569 570 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 571 571 Since the collection exists, its directory is already set up with subdirectories <i>import</i>, <i>archives</i>, <i>building</i>, <i>index</i>, and <i>etc</i>, and the <i>etc</i> directory will contain a suitable collection configuration file. 572 572 </p></div> … … 582 582 583 583 584 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">585 586 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">584 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 585 586 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 587 587 To update a collection, the new raw material is placed in the <i>import</i> directory, in whatever form it is available. Then the <i>import</i> process is invoked, which converts the files into GML using the specified plugins. Old material for which GML files have previously been created is not re-imported. Then the <i>build</i> process is invoked to build the requisite indexes for the collection. Finally, the contents of the <i>building</i> directory are moved into the <i>index</i> directory, and the new version of the collection automatically becomes live. 588 588 </p></div> … … 590 590 591 591 592 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">593 594 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">592 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 593 594 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 595 595 This procedure may seem cumbersome. But all the steps are necessary for efficient operation with large collections. The <i>import</i> process could be performed on the fly during the building operation&mdash;but because building indexes is a multipass operation, the often lengthy importing would be repeated several times. The <i>build</i> process can take considerable time&mdash;a day or two, for very large collections. Consequently, the results are placed in the <i>building</i> directory so that, if the collection already exists, it will continue to be served to users in its old form throughout the building operation. 596 596 </p></div> … … 598 598 599 599 600 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">601 602 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">600 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 601 602 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 603 603 Active users of the collection will not be disturbed when the new version becomes live&mdash;they will probably not even notice. The persistent OIDs ensure that interactions remain coherent&mdash;users who are examining the results of a query or browse operation will still retrieve the expected documents&mdash;and if a search is actually in progress when the change takes place the program detects the resulting file-structure inconsistency and automatically and transparently re-executes the query, this time on the new version of the collection. 604 604 </p></div> … … 614 614 615 615 616 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">617 618 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">616 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 617 618 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 619 619 The original material in the <i>import</i> directory may be in any format, and plugins are required to process each format type. The plugins that a collection uses must be specified in the collection configuration file. The <i>import</i> program reads the list of plugins and passes each document to each plugin in order until it finds one that can process it. When updating an existing collection, all plugins necessary to process new material should already have been specified in the configuration file. 620 620 </p></div> … … 622 622 623 623 624 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">625 626 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">624 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 625 626 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 627 627 The building step creates the indexes for both searching and browsing. The MG software is generally used to do the searching (Witten <i>et al.</i>, 1999), and the <i>mgbuild</i> module is automatically invoked to create each of the indexes that is required. For example, the Humanity Development Library has three indexes, one for entire books, one for chapters, and one for section titles. Subdirectories of the <i>index</i> directory are created for each of these indexes. 628 628 </p></div> … … 1632 1632 1633 1633 1634 <p><div name="paragraph" align=" left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">1635 1636 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">1634 <p><div name="paragraph" align="justify" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 1635 1636 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 1637 1637 MG also compresses the text of the collection; and the image files are linked into the <i>index</i> subdirectory. Now none of the material in the <i>import</i> and <i>archives</i> directories is needed to run the collection and can be removed from the file system (though they would be needed if the collection were rebuilt). 1638 1638 </p></div> … … 1640 1640 1641 1641 1642 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">1643 1644 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">1642 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 1643 1644 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 1645 1645 Associated with each collection is a database stored in GDBM (Gnu database manager) format. This contains an entry for each document, giving its OID, its internal MG document number, and metadata such as title. Information for each of the browsing indexes, which appear as buttons on the Greenstone search/browse bar, is also extracted during the building process and stored in the database. A &ldquo;classifier&rdquo; program is required for each browsing index to extract the appropriate information from GML documents. Like plugins, classifiers are written on an <i>ad hoc</i> basis for the particular information required, and where possible reused from one collection to another. 1646 1646 </p></div> … … 1648 1648 1649 1649 1650 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">1651 1652 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">1650 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 1651 1652 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 1653 1653 The building program creates the indexes based on whatever appears in the <i>archives</i> directory. The first plugin specified by all collections is one that processes GML files, and so if <i>archives</i> contains imported files they will be processed correctly. If it contains material in the original format, that will be converted using the appropriate plugin. Thus the import process is optional. 1654 1654 </p></div> … … 1656 1656 1657 1657 1658 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">1659 1660 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">1658 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 1659 1660 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 1661 1661 GML is designed to be fast and easy to parse, an important requirement when millions of documents are to be processed. Something as simple as requiring tags to be lower-case, for example, yields a substantial speed-up. In certain circumstances, however, it might be preferable to use a standardized format such as XML. This is straightforward to implement_just write an XML plugin_although we have not done so ourselves. Given the transitory nature of the imported data, to date, we have found GML a satisfactory and beneficial format. 1662 1662 </p></div> … … 1672 1672 1673 1673 1674 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">1675 1676 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">1674 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 1675 1676 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 1677 1677 Building new collections from scratch is only slightly different from updating an existing collection. The key new requirement is creating a collection configuration file, and a software utility is provided to help. Two pieces of information are required for this: the name of the directory that the collection will use (into which the source data and other files will eventually be placed), and a contact e-mail address for use if any problems are encountered by the software once the collection is up and running. The utility creates files and directories within the newly-named directory to support a generic collection of plain text documents. With suitable data placed in the <i>import</i> directory, building the collection at this point will yield a document-level searchable index of all the text and a browsable list of &ldquo;titles&rdquo; (defined in this case to be the document filenames). 1678 1678 </p></div> … … 1680 1680 1681 1681 1682 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">1683 1684 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">1682 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 1683 1684 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 1685 1685 To enhance the functionality and presentation&mdash; something anything but the most trivial collection will require&mdash;the configuration file must be edited. For a collection sourced from documents in an already supported data format, presented in a similar fashion to an existing collection, the amount of editing is minimal. Importing new data formats and browsing metadata in ways not currently supported are more complex activities that require programming skills. 1686 1686 </p></div> … … 1712 1712 1713 1713 1714 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">1715 1716 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">1714 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 1715 1716 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 1717 1717 Figure 5b shows simple alterations to the generic configuration file in Figure 5a that was generated by the new-collection utility. <i>TEXTPlug</i> is replaced with <i>EMAILPlug</i> (line 7) which reads email files and extracts metadata (<i>From</i>, <i>To</i>, <i>Date</i>, <i>Subject</i>) from them. A classifier for dates is added (line 10) to make the collection browsable chronologically. The default presentation of search results is overridden (line 17) to display both the title of the message (i.e. Dublin Core <i>Title</i>) and its sender (i.e. Dublin Core <i>Author</i>). Elements in square brackets, such as <i>[Title]</i>, are replaced by the metadata associated with a particular document. The built-in term <i>[icon]</i> produces a suitable image that represents the document (such as a book icon or page icon), and the <i>[link]&hellip;[/link]</i> construct forms a hyperlink to the complete document. Anything else in the format statement, which in this case is solely table-cell tags in HTML, is passed through to the page being displayed. 1718 1718 </p></div> … … 1720 1720 1721 1721 1722 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">1723 1724 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">1722 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 1723 1724 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 1725 1725 As this example shows, creating a new collection that stays within the bounds of the library's established capabilities falls within the capability of many computer users&mdash;for instance, computer-trained librarians. Extending Greenstone to handle new document formats and browse metadata in new ways is more challenging. 1726 1726 </p></div> … … 1736 1736 1737 1737 1738 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">1739 1740 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">1738 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 1739 1740 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 1741 1741 Extensibility is obtained through plugins and classifiers. 1742 1742 </p></div> … … 1744 1744 1745 1745 1746 <p><div name="paragraph" align=" left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">1747 1748 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">1746 <p><div name="paragraph" align="justify" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 1747 1748 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 1749 1749 These are modules of code that can be slotted into the system to enhance its capabilities. Plugins parse documents, extracting the text and metadata to be indexed. Classifiers control how metadata is brought together to form browsable data structures. Both are specified in an object-oriented framework using inheritance to minimize the amount of code written. 1750 1750 </p></div> … … 1752 1752 1753 1753 1754 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">1755 1756 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">1754 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 1755 1756 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 1757 1757 A plugin must specify three things: what file formats it can handle, how they should be parsed, and whether the plugin is recursive. File formats are normally determined using regular expression matching on the filename. For example, the HTML plugin accepts all files that end in <i>.htm</i>, .<i>html</i>, <i>.HTM</i>, or <i>.HTML</i>. (It is quite possible, however, to write plugins that &ldquo;look inside&rdquo; the file as well.) For other files, the plugin returns <i>undefined</i> and the file is passed to the next plugin in the collection's configuration file (e.g. Figure 5 line 7). If it can, the plugin parses the file and returns the number of documents processed. This involves extracting text and metadata and adding it to the library's content through calls to <i>add text</i> and <i>add metadata</i>. 1758 1758 </p></div> … … 1760 1760 1761 1761 1762 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">1763 1764 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">1762 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 1763 1764 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 1765 1765 Some plugins (&ldquo;recursive&rdquo; ones) add extra files into the stream of data processed during the building phase by artificially reactivating the list of plugins. This is how directory hierarchies are traversed. 1766 1766 </p></div> … … 1768 1768 1769 1769 1770 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">1771 1772 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">1770 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 1771 1772 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 1773 1773 Plugins are small modules of code that are easy to write. We monitored the time it took to develop a new one that was different to any we had produced so far. We chose to make as an example a collection of HTML bookmark files, the motivation being to produce a convenient way of searching and browsing one's bookmarked Web pages. Figure 6 shows a user searching for bookmarked pages about <i>music</i>. The new plugin took under an hour to write, and was 160 lines long (ignoring blank lines and comments)&mdash;about the average length of existing plugins. 1774 1774 </p></div> … … 1776 1776 1777 1777 1778 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">1779 1780 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">1778 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 1779 1780 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 1781 1781 Classifiers are more general than plugins because they work on GML-format data. For example, any plugin that generates date metadata in accordance with the Dublin core can request the collection to be browsable chronologically by specifying the <i>DateList</i> classifier in the collection's configuration file (Figure 7). Classifiers are more elaborate than most plugins, but new ones are seldom required. The average length of existing classifiers is 230 lines. 1782 1782 </p></div> … … 1784 1784 1785 1785 1786 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">1787 1788 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">1786 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 1787 1788 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 1789 1789 Classifiers must specify three things: an initialization routine, how individual documents are classified, and the final browsable data structure. Initialization takes care of any options specified in the configuration file (such as <i>metadata=Title </i>on line 9 of Figure 5b). Classifying individual documents is an iterative process: for each one, a call to <i>document-classify</i> is made. On presentation of the document's OID, the necessary metadata is located and used to control where the document is added to the browsable data structure being constructed. 1790 1790 </p></div> … … 1792 1792 1793 1793 1794 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">1795 1796 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">1794 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 1795 1796 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 1797 1797 Once all documents have been added, a request is made for the completed data structure. Some classifiers return the data structure directly; others transform the data structure before it is returned. For example, the <i>AZList</i> classifier divides the alphabetically sorted list of metadata into separate pages of about the same size and returns the alphabetic ranges for each one (Figure 4). 1798 1798 </p></div> … … 1824 1824 1825 1825 1826 <p><div name="Plain Text" align=" left" style="margin: 2.08mm 0.24mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">1827 1828 <p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">1826 <p><div name="Plain Text" align="justify" style="margin: 2.08mm 0.24mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 1827 1828 <p style="text-indent: 0.00mm; text-align: justify; line-height: 4.166667mm; color: Black; background-color: White; "> 1829 1829 Two projects that provide substantial open source digital library software are Dienst (Lagoze and Fielding, 1998) and Harvest (Bowman <i>et al.</i>, 1994). The origins of Dienst (<i>www.cs.cornell.edu/cdlrg</i>) stretch back to 1992. The term has come to represent three entities: a conceptual architecture for distributed digital libraries; an open protocol for service communication; and a software system that implements the protocol. To date, five sample digital libraries have been built using this technology. They manifest themselves in two forms: technical reports and primary source documents. 1830 1830 </p></div> … … 1832 1832 1833 1833 1834 <p><div name="Plain Text" align=" left" style="margin: 2.08mm 0.24mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">1835 1836 <p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">1834 <p><div name="Plain Text" align="justify" style="margin: 2.08mm 0.24mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 1835 1836 <p style="text-indent: 0.00mm; text-align: justify; line-height: 4.166667mm; color: Black; background-color: White; "> 1837 1837 Best known is NCSTRL, the Networked Computer Science Technical Reference Library project (<i>www.ncstrl.org</i>). This collection facilitates searching by title, author and abstract, and browsing by year and author, across a distributed network of document repositories. Documents can (where supported) be delivered in various formats such as PostScript, a thumbnail overview of the pages, and a GIF image of a particular page. 1838 1838 </p></div> … … 1840 1840 1841 1841 1842 <p><div name="Plain Text" align=" left" style="margin: 2.08mm 0.24mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">1843 1844 <p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">1842 <p><div name="Plain Text" align="justify" style="margin: 2.08mm 0.24mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 1843 1844 <p style="text-indent: 0.00mm; text-align: justify; line-height: 4.166667mm; color: Black; background-color: White; "> 1845 1845 The <i>Making of America</i> resource is an example of a collection based around primary sources_in this case American social history, 1830â1900. It has a different &ldquo;look and feel&rdquo; to NCSTRL, being strongly oriented toward browsing rather than searching. A user navigates their way through a hierarchical structure of hyperlinks to reach a book of interest. The book itself is a series of scanned images: delivery options include going directly to a page number, next and previous page buttons, and displaying a particular page at different resolutions. A text version of the page is also available upon which a searching option is also provided. 1846 1846 </p></div> … … 1848 1848 1849 1849 1850 <p><div name="Plain Text" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">1851 1852 <p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">1850 <p><div name="Plain Text" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 1851 1852 <p style="text-indent: 0.00mm; text-align: justify; line-height: 4.166667mm; color: Black; background-color: White; "> 1853 1853 Started in 1994, Harvest is also a long-running research project. It provides an efficient means of gathering source data from the Internet and distributing indexing information over the Internet. This is accomplished through five components: <i>gatherer</i>, <i>broker</i>, <i>indexer</i>, <i>replicator</i> and <i>cache</i>. The first three are central to creating, updating and searching a collection; the last two help to improve performance over the Internet through transparent mirroring and caching techniques. 1854 1854 </p></div> … … 1856 1856 1857 1857 1858 <p><div name="Plain Text" align=" left" style="margin: 2.08mm 0.24mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">1859 1860 <p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">1858 <p><div name="Plain Text" align="justify" style="margin: 2.08mm 0.24mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 1859 1860 <p style="text-indent: 0.00mm; text-align: justify; line-height: 4.166667mm; color: Black; background-color: White; "> 1861 1861 The system is configurable and customizable. While searching is most commonly implemented using Glimpse (<i>glimpse.cs.arizona.edu</i>), in principle any search engine that supports incremental updates and Boolean combinations of attribute-based queries can be used. It is possible to control what type of documents are gathered during creation and updating, and how the query interface looks and is laid out. 1862 1862 </p></div> … … 1864 1864 1865 1865 1866 <p><div name="Plain Text" align=" left" style="margin: 2.08mm 0.24mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">1867 1868 <p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">1866 <p><div name="Plain Text" align="justify" style="margin: 2.08mm 0.24mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 1867 1868 <p style="text-indent: 0.00mm; text-align: justify; line-height: 4.166667mm; color: Black; background-color: White; "> 1869 1869 Sample collections cited by the developers include 21,000 computer science technical reports and 7,000 home pages. Other examples include a sizable collection of agriculture-related electronic journals and magazines called &ldquo;tomato-juice&rdquo; (accessed through <i>hegel.lib.ncsu.edu</i>) and a full-text index of library-related electronic serials (<i>sunsite.berkeley.edu/IndexMorganagus</i>). Harvest is also often used to index Web sites (for example <i>www.middlebury.edu</i>). 1870 1870 </p></div> … … 1872 1872 1873 1873 1874 <p><div name="Plain Text" align=" left" style="margin: 2.08mm 0.24mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">1875 1876 <p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">1874 <p><div name="Plain Text" align="justify" style="margin: 2.08mm 0.24mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 1875 1876 <p style="text-indent: 0.00mm; text-align: justify; line-height: 4.166667mm; color: Black; background-color: White; "> 1877 1877 Comparing Greenstone with Dienst and Harvest, there are both similarities and differences. All provide substantial digital library systems, hence common themes recur, but they are driven by projects with different aims. Harvest, for instance, was not conceived as a digital library project at all, but by virtue of its selective document gathering process it can be classed (and is used) as one. While it provides sophisticated search options, it lacks the complementary service of browsing. Furthermore it adds no structure or order to the documents collected, relying on whatever structures are present in the site that they were gathered from. A proven strength of the design is its flexibility through configuration and customization_an element also present in Greenstone. 1878 1878 </p></div> … … 1880 1880 1881 1881 1882 <p><div name="Plain Text" align=" left" style="margin: 2.08mm 0.24mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">1883 1884 <p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">1882 <p><div name="Plain Text" align="justify" style="margin: 2.08mm 0.24mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 1883 1884 <p style="text-indent: 0.00mm; text-align: justify; line-height: 4.166667mm; color: Black; background-color: White; "> 1885 1885 Dienst_best exemplified through the NCSTRL work_supports searching and browsing, like Greenstone. Both use open protocols. Differences include a high reliance in Dienst on user-supplied information when a document is added, and a smaller range of document types supported&mdash;although Dienst does include a document model that should, over time, allow this to expand with relative ease. 1886 1886 </p></div> … … 1888 1888 1889 1889 1890 <p><div name="Plain Text" align=" left" style="margin: 2.08mm 0.24mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">1891 1892 <p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">1890 <p><div name="Plain Text" align="justify" style="margin: 2.08mm 0.24mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 1891 1892 <p style="text-indent: 0.00mm; text-align: justify; line-height: 4.166667mm; color: Black; background-color: White; "> 1893 1893 There are also commercial systems that provide similar digital library services to those described. However, since corporate culture instills proprietary attitudes there is little opportunity for advancement through a shared collaborative effort. Consequently they are not reviewed here. 1894 1894 </p></div> … … 1904 1904 1905 1905 1906 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">1907 1908 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">1906 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 1907 1908 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 1909 1909 Greenstone is a comprehensive software system for creating digital library collections. It builds data structures for searching and browsing from the material provided, rather than relying on any hand-crafting. The process is controlled by a configuration file, and once a collection exists new material can be added completely automatically. Browsing is based on Dublin Core metadata. 1910 1910 </p></div> … … 1912 1912 1913 1913 1914 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">1915 1916 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">1914 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 1915 1916 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 1917 1917 New collections can be developed easily, particularly if they resemble existing ones. Extensibility is achieved through software &ldquo;plugins&rdquo; that can be written to accommodate documents, and metadata, in different formats. Standard plugins exist for many document types; new ones are easily written. Browsing is controlled by &ldquo;classifiers&rdquo; that process metadata into browsing structures (by date, alphabetical, hierarchical, etc). 1918 1918 </p></div> … … 1920 1920 1921 1921 1922 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">1923 1924 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">1922 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 1923 1924 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 1925 1925 However, the most powerful support for extensibility is achieved not by technical means but by making the source code freely available under the Gnu public license. Only through an international cooperative effort will digital library software become sufficiently comprehensive to meet the world's needs with the richness and flexibility that users deserve. 1926 1926 </p></div> … … 1936 1936 1937 1937 1938 <p><div name="paragraph" align=" left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">1939 1940 <p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">1938 <p><div name="paragraph" align="justify" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 1939 1940 <p style="text-indent: 0.00mm; text-align: justify; line-height: 3.819444mm; color: Black; background-color: White; "> 1941 1941 We gratefully acknowledge all those who have worked on the Greenstone software, and all members of the New Zealand Digital Library project for their enthusiasm and ideas. 1942 1942 </p></div> … … 1953 1953 1954 1954 <ol type="1"> 1955 <li value="1"><p><div name="References" align=" left" style="margin: 1.04mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">1956 1957 <p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">1955 <li value="1"><p><div name="References" align="justify" style="margin: 1.04mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 1956 1957 <p style="text-indent: -6.25mm; text-align: justify; line-height: 4.166667mm; color: Black; background-color: White; "> 1958 1958 Akscyn, R.M. and Witten, I.H. (1998) &ldquo;Report on First Summit on International Cooperation on Digital Libraries.&rdquo; ks.com/idla-wp-oct98. 1959 1959 </p></div></li> … … 1961 1961 1962 1962 1963 <li value="2"><p><div name="References" align=" left" style="margin: 1.04mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">1964 1965 <p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">1963 <li value="2"><p><div name="References" align="justify" style="margin: 1.04mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 1964 1965 <p style="text-indent: -6.25mm; text-align: justify; line-height: 4.166667mm; color: Black; background-color: White; "> 1966 1966 Bowman, C.M., Danzig, P.B., Manber, U., and Schwartz, M.F. &ldquo;Scalable Internet resource discovery: Research problems and approaches&rdquo; <i>Communications of the ACM,</i> Vol. 37, No. 8, pp. 98â107, 1994. 1967 1967 </p></div></li> … … 2113 2113 2114 2114 2115 <p><div name="Header" align=" left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">2116 2117 <p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">2115 <p><div name="Header" align="justify" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 2116 2117 <p style="text-indent: 0.00mm; text-align: justify; line-height: 4.166667mm; color: Black; background-color: White; "> 2118 2118 <span style="text-transform:lowercase"></span> 2119 2119 </p></div> … … 2129 2129 2130 2130 2131 <p><div name="Footer" align=" left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">2132 2133 <p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">2131 <p><div name="Footer" align="justify" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; "> 2132 2133 <p style="text-indent: 0.00mm; text-align: justify; line-height: 4.166667mm; color: Black; background-color: White; "> 2134 2134 <span style="text-transform:lowercase"></span> 2135 2135 </p></div>
Note:
See TracChangeset
for help on using the changeset viewer.
