Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Enhanced-PDF/archives/HASH019c.dir/doc.xml
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Enhanced-PDF/archives/HASH019c.dir/doc.xml	(revision 37429)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Enhanced-PDF/archives/HASH019c.dir/doc.xml	(revision 37429)
@@ -0,0 +1,672 @@
+<?xml version="1.0" encoding="utf-8" standalone="no"?>
+<!DOCTYPE Archive SYSTEM "http://greenstone.org/dtd/Archive/1.0/Archive.dtd">
+<Archive>
+<Section>
+  <Description>
+    <Metadata name="gsdldoctype">indexed_doc</Metadata>
+    <Metadata name="Language">en</Metadata>
+    <Metadata name="Encoding">utf8</Metadata>
+    <Metadata name="URL">http://Scratch/ak19/gs2-diffcol-26Jul2021/collect/Enhanced-PDF/tmp/1678158430_1/pdf03.html</Metadata>
+    <Metadata name="UTF8URL">http://Scratch/ak19/gs2-diffcol-26Jul2021/collect/Enhanced-PDF/tmp/1678158430_1/pdf03.html</Metadata>
+    <Metadata name="Title">Applications for Bibliometric Research in the Emerging Digital Libraries Sally Jo Cunningham...</Metadata>
+    <Metadata name="gsdlsourcefilename">import/pdf03.pdf</Metadata>
+    <Metadata name="gsdlsourcefilerenamemethod">url</Metadata>
+    <Metadata name="gsdlconvertedfilename">tmp/1678158430_1/pdf03.html</Metadata>
+    <Metadata name="OrigSource">pdf03.html</Metadata>
+    <Metadata name="Source">pdf03.pdf</Metadata>
+    <Metadata name="SourceFile">pdf03.pdf</Metadata>
+    <Metadata name="Plugin">PDFv1Plugin</Metadata>
+    <Metadata name="FileSize">35935</Metadata>
+    <Metadata name="FilenameRoot">pdf03</Metadata>
+    <Metadata name="FileFormat">PDF</Metadata>
+    <Metadata name="srcicon">_iconpdf_</Metadata>
+    <Metadata name="srclink_file">doc.pdf</Metadata>
+    <Metadata name="srclinkFile">doc.pdf</Metadata>
+    <Metadata name="NumPages">17</Metadata>
+    <Metadata name="gsdlthistype">Paged</Metadata>
+    <Metadata name="ex.ExifTool.ExifToolVersion">12.19</Metadata>
+    <Metadata name="ex.File.Directory">/Scratch/ak19/gs2-diffcol-26Jul2021/collect/Enhanced-PDF/import</Metadata>
+    <Metadata name="ex.File.FileAccessDate">2023:03:07 16:07:08+13:00</Metadata>
+    <Metadata name="ex.File.FileInodeChangeDate">2023:03:07 16:07:07+13:00</Metadata>
+    <Metadata name="ex.File.FileModifyDate">2023:03:07 16:07:07+13:00</Metadata>
+    <Metadata name="ex.File.FileName">pdf03.pdf</Metadata>
+    <Metadata name="ex.File.FilePermissions">100664</Metadata>
+    <Metadata name="ex.File.FileSize">35935</Metadata>
+    <Metadata name="ex.File.FileType">PDF</Metadata>
+    <Metadata name="ex.File.FileTypeExtension">PDF</Metadata>
+    <Metadata name="ex.File.MIMEType">application/pdf</Metadata>
+    <Metadata name="ex.PDF.Author">Bronwyn</Metadata>
+    <Metadata name="ex.PDF.CreateDate">1999:09:27 16:05:06</Metadata>
+    <Metadata name="ex.PDF.Creator">Microsoft Word</Metadata>
+    <Metadata name="ex.PDF.Linearized">false</Metadata>
+    <Metadata name="ex.PDF.PDFVersion">1.1</Metadata>
+    <Metadata name="ex.PDF.PageCount">17</Metadata>
+    <Metadata name="ex.PDF.Producer">Acrobat PDFWriter 2.0 for Macintosh</Metadata>
+    <Metadata name="ex.PDF.Title">biblio_for_dl_scientometrics.do</Metadata>
+    <Metadata name="Identifier">HASH019c5dca7f5bb781460a6b9c</Metadata>
+    <Metadata name="lastmodified">1678158427</Metadata>
+    <Metadata name="lastmodifieddate">20230307</Metadata>
+    <Metadata name="oailastmodified">1678158430</Metadata>
+    <Metadata name="oailastmodifieddate">20230307</Metadata>
+    <Metadata name="assocfilepath">HASH019c.dir</Metadata>
+    <Metadata name="gsdlassocfile">doc.pdf:application/pdf:</Metadata>
+  </Description>
+  <Content>
+
+ 
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+</Content>
+<Section>
+  <Description>
+    <Metadata name="Title">1</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+&lt;b&gt;Applications for Bibliometric Research&lt;/b&gt;&lt;br&gt;
+&lt;b&gt;in the Emerging Digital Libraries&lt;/b&gt;&lt;br&gt;
+Sally Jo Cunningham&lt;br&gt;
+Department of Computer Science&lt;br&gt;
+University of Waikato&lt;br&gt;
+Hamilton, New Zealand&lt;br&gt;
+email:  sallyjo@waikato.ac.nz&lt;br&gt;
+&lt;b&gt;Abstract:&lt;/b&gt;  Large numbers of research documents have recently become available on&lt;br&gt;
+the Internet through  âdigital librariesâ, and these collections are seeing high levels of&lt;br&gt;
+use  by  their  related  research  communities.  A  secondary    use  for  these  document&lt;br&gt;
+repositories and indexes is as a platform for bibliometric research.  We examine the&lt;br&gt;
+extent to which the new digital libraries support conventional bibliometric analysis, and&lt;br&gt;
+discuss  shortcomings  in  their  current  forms.    Interestingly,  these  electronic  text&lt;br&gt;
+archives also provide opportunities for new types of studies:  generally the full text of&lt;br&gt;
+documents are available for analysis, giving a finer grain of insight than abstract-only&lt;br&gt;
+online databases;  these repositories often contain technical reports or pre-prints, the&lt;br&gt;
+âgrey  literatureâ  that  has  been  previously  unavailable  for  analysis;  and  document&lt;br&gt;
+âusageâ  can  be  measured  directly  by  recording  user  accesses,  rather  than  studied&lt;br&gt;
+indirectly through document references.&lt;br&gt;
+&lt;b&gt;1.  Introduction&lt;/b&gt;&lt;br&gt;
+In recent years a number of &amp;quot;digital libraries&amp;quot; have become available through the&lt;br&gt;
+Internet.  While the technology promises in the future to support large, heterogenous&lt;br&gt;
+collections, at present the most widely used of the academically-focussed digital&lt;br&gt;
+libraries are generally repositories of one or two types of document (typically technical&lt;br&gt;
+reports, journal articles, pre-prints, or conference proceedings), grouped by discipline.&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">2</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+A distinguishing characteristic of these digital libraries is that the full text of documents&lt;br&gt;
+are often available for retrieval, as well as bibliographic records.The sciences are&lt;br&gt;
+represented much more heavily in the present crop of digital libraries than the social&lt;br&gt;
+sciences, arts, or humanities. They are maintained by professional societies,&lt;br&gt;
+universities, research laboratories, and even private individuals.  Access is generally&lt;br&gt;
+free, both to search and to download documents.&lt;br&gt;
+The emergence of these subject-specific digital libraries is particularly important&lt;br&gt;
+given the pattern of access to materials presently employed by research scientists.&lt;br&gt;
+Informal exchanges of preprints, reprints, and photocopies of papers passed on by&lt;br&gt;
+colleagues currently are major venues for the transmission of scientific information&lt;br&gt;
+between researchers in the sciences.  In one study, the dependence on these sources&lt;br&gt;
+ranges from 12% (for chemistry)  to 39% (for mathematics) of all papers cited in&lt;br&gt;
+researchers' own publications [11]. A qualitative study of study of how computer&lt;br&gt;
+scientists locate and retrieve documents (computing is one of the domains considered&lt;br&gt;
+later in this paper) indicates that for that field, technical reports and research documents&lt;br&gt;
+found in various locations on the Internet are a preferred source of information [6].&lt;br&gt;
+Many of the digital library systems discussed in this paper are repositories for just this&lt;br&gt;
+type of literature.  The documents tend to be of high quality:  primarily  technical&lt;br&gt;
+reports or working papers from research institutions (both academic and commercial),&lt;br&gt;
+as well as advance copies of work accepted for publication in conventional paper&lt;br&gt;
+journals. Moreover, these digital libraries are also coming to include refereed work&lt;br&gt;
+published digitally (in electronic journals).  Anecdotal evidence suggests that in their&lt;br&gt;
+fields, these digital libraries are coming to be the resource of choice for locating cutting&lt;br&gt;
+edge work.&lt;br&gt;
+For specialized subjects such as high energy physics, this dependence on&lt;br&gt;
+informal or extra-library dissemination can be much higher. Ginsparg ([9], [10])&lt;br&gt;
+reports that fields in physics have traditionally relied heavily on preprint exchanges, and&lt;br&gt;
+the digital repositories of physics preprints begun in 1991 (the PHYSICS E-PRINT&lt;br&gt;
+ARCHIVES) have to a large extent supplanted conventional publishing and physical&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">3</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+paper mailing of technical reports.  By providing ready access to information sources&lt;br&gt;
+that are already preferentially utilized by scientists, the digital libraries show potential to&lt;br&gt;
+increase access to information that until recently was expensive or difficult to acquire in&lt;br&gt;
+paper form.  Indeed, in some fields (most notably physics) this process has already&lt;br&gt;
+begun, as researchers in less developed countries report access to ongoing research&lt;br&gt;
+through the Internet repositories that their local libraries could not afford to acquire&lt;br&gt;
+through conventional journal subscriptions ([9], [10]).&lt;br&gt;
+The primary use for new bibliographic resources is, of course, for the contents&lt;br&gt;
+of the documents involved.  A secondary use for emerging resources is as a basis for&lt;br&gt;
+bibliometric analysis of the subject field.  With the conventionally published scientific&lt;br&gt;
+literature, the sheer difficulty of accumulating statistics discouraged bibliometric&lt;br&gt;
+research until the advent of large bibliographic databases in the 1960's. Computerized&lt;br&gt;
+bibliographic databases sparked a significant increase in the number of large-scale&lt;br&gt;
+bibliographic studies, as significant portions of the collection and analysis of data could&lt;br&gt;
+be automated ([12], [13]).  The availability of CD-ROM versions of bibliographic&lt;br&gt;
+databases has been of particular importance, since they provide a cheaper alternative to&lt;br&gt;
+the online commercial databases [3].&lt;br&gt;
+These computerized bibliographic resources have drawbacks, however.  The&lt;br&gt;
+greatest is that the full text of documents are rarely available, and even abstracts are not&lt;br&gt;
+always present.  This obviously limits the types of bibliometric research that can be&lt;br&gt;
+conducted &lt;i&gt;solely&lt;/i&gt; through these databases.  In addition, these databases are generally&lt;br&gt;
+limited to formally published documents (those appearing in selected books, journals,&lt;br&gt;
+and conference proceedings).  The &amp;quot;grey literature&amp;quot; of technical reports, pre-prints, and&lt;br&gt;
+other works not formally published are largely ignored, and it is this absence of easy&lt;br&gt;
+access to these documents that has hampered the analysis of these important forms of&lt;br&gt;
+scientific communication.&lt;br&gt;
+The digital libraries currently in existence complement the online and CD-ROM&lt;br&gt;
+bibliographic databases.  They are best suited for examinations of the &amp;quot;physical&amp;quot;&lt;br&gt;
+characteristics of documents (for example, document length), analysis based on&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">4</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+bibliographic information that can be automatically extracted from the document text or&lt;br&gt;
+the sometimes unevenly formatted bibliographic records (such as obsolescence&lt;br&gt;
+studies),  and usage studies (geographic or institutional origin of users, date/time of&lt;br&gt;
+access, individual patterns of document retrieval, etc.).  Because  references are present&lt;br&gt;
+in the document file but not identified by field, co-citation and bibliographic coupling&lt;br&gt;
+research is not well-supported, and conducting these studies requires considerable&lt;br&gt;
+effort on the part of the researcher.&lt;br&gt;
+The variety of bibliographic repositories in the available digital libraries in itself&lt;br&gt;
+has great potential in conducting bibliometric research.  Sigogneau et al [15] present a&lt;br&gt;
+case study illustrating the ways in which the strengths of different databases can be&lt;br&gt;
+played off each other; they conduct a fine-grained analysis of the emergence of research&lt;br&gt;
+fronts in molecular and cellular biology, and demonstrate that the observations gleaned&lt;br&gt;
+from two complementary bibliographic databases provide greater insight into their&lt;br&gt;
+problem. Similarly, it appears that  the types of bibliographic data that can be gleaned&lt;br&gt;
+from the relatively unstructured digital libraries can be profitably combined with data&lt;br&gt;
+from online databases, CD-ROMS, and other more conventional bibliographic&lt;br&gt;
+resources.&lt;br&gt;
+This paper is organized as follows:  Section 2 discusses the types of indexing&lt;br&gt;
+and searching available with current digital libraries; Section 3 gives examples of&lt;br&gt;
+conventional bibliometric techniques applied to Internet-accessible archives; Section 4&lt;br&gt;
+discusses opportunities to directly measure usage of documents and to detect&lt;br&gt;
+information-seeking patterns in researchers; and Section 5 presents our conclusions.&lt;br&gt;
+&lt;b&gt;2.  Indexing and searching in current digital libraries&lt;/b&gt;&lt;br&gt;
+At present, the types of indexing fields for most academically-oriented digital&lt;br&gt;
+library systems are limited.  Many schemes index on user-supplied document&lt;br&gt;
+descriptions, abstracts, or similar document surrogates (for example, the PHYSICS E-&lt;br&gt;
+PRINT ARCHIVE [10], a collection of physics pre-prints and technical reports). As will&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">5</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+be discussed below, the quality of this user-provided data can be highly variable, and&lt;br&gt;
+may unfavorably impact the usefulness of the index for searching. Alternatively, a&lt;br&gt;
+designated site librarian may maintain a catalog (eg, the WATERS [14] system, now&lt;br&gt;
+subsumed by NCSTRL (http://www.ncstrl.org/), both primarily collections of&lt;br&gt;
+computer science technical reports);  in this case the quality of the bibliographic&lt;br&gt;
+information may be expedited to be higher, but fewer sites will be likely to support&lt;br&gt;
+such a librarian and therefore fewer documents are likely to be included in the digital&lt;br&gt;
+library. In a âharvestingâ system such as the computer science technical report&lt;br&gt;
+collections supported by HARVEST  [2] or the NEW ZEALAND DIGITAL LIBRARY&lt;br&gt;
+computer science technical report collection ([16], [17]), documents are indexed from&lt;br&gt;
+passive repositories (that may not even be aware that their documents are being&lt;br&gt;
+included in the digital library). Harvesting systems therefore cannot rely on the&lt;br&gt;
+presence of bibliographic data of any sort.&lt;br&gt;
+Because of the relative paucity of high-quality bibliographic data available to&lt;br&gt;
+many of the current academically- or research-focussed digital library collections, their&lt;br&gt;
+search interfaces tend to be more primitive than those ordinarily found in online&lt;br&gt;
+bibliographic databases or library catalogs.  Systems such as NCSTRL can support&lt;br&gt;
+author, title, and subject searching, but  this more sophisticated search functionality&lt;br&gt;
+comes at the expense of requiring participating repositories to use specific software.  As&lt;br&gt;
+a consequence, these latter systems may provide access to a small number of sites than&lt;br&gt;
+harvesting systems. Harvesters may access a broader range of providers, but at the&lt;br&gt;
+penalty of being limited to unfielded, keyword searches over the raw text of the&lt;br&gt;
+document or document surrogate.&lt;br&gt;
+Specifically, the indexing in existing digital libraries has a variety of shortcomings for&lt;br&gt;
+bibliometric applications:&lt;br&gt;
+â¢&lt;br&gt;
+&lt;i&gt;lack of fielded indexing:&lt;/i&gt;   As noted above, some large and widely used digital&lt;br&gt;
+libraries (such as the computer science technical report collection of the  NEW&lt;br&gt;
+ZEALAND DIGITAL LIBRARY) may lack formal cataloging entirely, and rely on&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">6</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+keyword searching over the raw document text. Obviously this  makes  field-&lt;br&gt;
+dependent analysis more difficult (for example, locating documents produced by&lt;br&gt;
+specific authors), and in the worst case my require a manual examination of all&lt;br&gt;
+files in the collection in order to reliably identify a desired document subset.&lt;br&gt;
+However, keyword search techniques that approximate fielded searching results&lt;br&gt;
+may suffice:  for example in the  NEW ZEALAND DIGITAL LIBRARY computer&lt;br&gt;
+science technical report collection,  limiting the keyword search for âJohnsonâ&lt;br&gt;
+to a search of first pages only is likely to retrieve documents written by Johnson&lt;br&gt;
+(since for the  majority  of  computer  science  technical  reports,  the  first  page&lt;br&gt;
+contains little more than author, title, date, and institution details).&lt;br&gt;
+A more principled  approach to extracting bibliographic information is embodied&lt;br&gt;
+in  the  CiteSeer  tool  [1].  This  software  parses  raw,  unfielded  academic&lt;br&gt;
+documents and attempts to identify such indexing information as author, title,&lt;br&gt;
+reference list, etc. Obviously such a tool cannot attain 100% accuracy over a&lt;br&gt;
+heterogenous document collection, but in practice it appears useful in that it can&lt;br&gt;
+make a good first pass in processing a set of documents, providing an initial set&lt;br&gt;
+of parsed documents for analysis. The remaining (presumably much smaller) set&lt;br&gt;
+of unparsable documents can then be dealt with manually.&lt;br&gt;
+â¢&lt;br&gt;
+&lt;i&gt;lack of consistency in field formatting:&lt;/i&gt;  Current digital libraries usually acquire&lt;br&gt;
+bibliographic  information  from  either  the  authors  of  submitted  articles  or&lt;br&gt;
+automatic extraction routines (retrieving bibliographic details from catalog files&lt;br&gt;
+that may or may not be in a given document site, and that may or may not be in&lt;br&gt;
+an  easily  parsable  form).  Neither  of  these  methods  produce  records  with&lt;br&gt;
+standard  formatting,  which  causes  problems  with  automated  bibliometric&lt;br&gt;
+analysis.   Consider the following examples selected from entries in the hep-th&lt;br&gt;
+(high energy physics) collection of the PHYSICS E-PRINT ARCHIVES:&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">7</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+(i)&lt;br&gt;
+Authors: A. Yu. Alekseev, V. Schomerus&lt;br&gt;
+(ii)&lt;br&gt;
+Authors: Adel Bilal and Ian. I. Kogan&lt;br&gt;
+(iii)&lt;br&gt;
+Authors: Paul S. Aspinwall and David R. Morrison (with an appendix &lt;br&gt;
+by Mark Gross)&lt;br&gt;
+(iv)&lt;br&gt;
+Authors: A. H. Chamseddine and Herbi Dreiner (ETH-Zurich)&lt;br&gt;
+In this case, typical for existing digital libraries, there is no standardized format&lt;br&gt;
+for authors' names (here, appearing with full names, initials plus last name, and&lt;br&gt;
+a mixture of  the  two);  no  standard  convention  for  separating  author  names&lt;br&gt;
+(here, either a comma or &amp;quot;and&amp;quot; are  used);  and  parenthetical  information  can&lt;br&gt;
+include a variety of information such as the name of an associate author or the&lt;br&gt;
+institutional affiliations of an author.  Manual processing or specially  crafted&lt;br&gt;
+software would be required to reformat these fields for analysis.&lt;br&gt;
+â¢&lt;br&gt;
+&lt;i&gt;duplicate entries: &lt;/i&gt; Digital libraries that draw documents from a variety of sources&lt;br&gt;
+may  inadvertently  contain  duplicate  items.    Unfortunately,  the  irregular&lt;br&gt;
+formatting of the bibliographic information makes it difficult to  automatically&lt;br&gt;
+detect these duplicates.&lt;br&gt;
+â¢&lt;br&gt;
+&lt;i&gt;implicit field tagging:&lt;/i&gt;  In some repositories, items are not explicitly tagged with&lt;br&gt;
+certain  types  of  information  â  most  commonly  the  document's  date  of&lt;br&gt;
+publication or production.  Instead, the date is implicit in the document's title&lt;br&gt;
+(eg, its numeration in a technical report series) or in the location of the document&lt;br&gt;
+in the file structure of the repository  (eg,  separate  directories  exist  for  each&lt;br&gt;
+year).  A second common piece of  implicit  data  is  the  authorsâ  institutional&lt;br&gt;
+affiliations.  This may be contained in the document itself (typically on a cover&lt;br&gt;
+page),  or  may  be  implicit  in  the  documentâs  location  (for  example,  a&lt;br&gt;
+corporationâs technical reports are stored in its ftp repository).  Again, in these&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">8</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+cases  special  processing  is  required  to  append  this  field  information  to  a&lt;br&gt;
+document record for bibliometric analysis.  &lt;br&gt;
+â¢&lt;br&gt;
+&lt;i&gt;extraction of document text:&lt;/i&gt;  Few of  the  documents  stored  in  the  research-&lt;br&gt;
+oriented digital libraries discussed in this paper are straight ascii text; instead,&lt;br&gt;
+documents may appear in a variety of file formats, such as LaTeX, PostScript,&lt;br&gt;
+PDF, etc.  If the contents of the documents are to be automatically processed&lt;br&gt;
+(for  example,  to  count  the  words  in  a  document,  or  to  extract  reference&lt;br&gt;
+publication dates for an obsolescence study), then the text must be extracted.&lt;br&gt;
+Utilities are available to convert most common document formats to ascii.&lt;br&gt;
+It is likely that many of these problems will be addressed as the Internet-based&lt;br&gt;
+document indexing systems mature.  Even minor changes can greatly increase the&lt;br&gt;
+useability of a bibliographic database for bibliometric research.  For example, the&lt;br&gt;
+addition of an explicit date tag to many online databases in 1975 sparked new&lt;br&gt;
+applications in time series research [3].&lt;br&gt;
+&lt;b&gt;3.  Opportunities for applications of bibliometric techniques&lt;/b&gt;&lt;br&gt;
+One type of bibliometric research concentrates on quantifying fundamental,&lt;br&gt;
+structural details about a subject literature:  how many items are published, how many&lt;br&gt;
+authors are publishing, over what time period documents are likely to be used, etc.&lt;br&gt;
+More complex studies analyze the relationships between documents, such as how&lt;br&gt;
+documents cluster into subjects.  The following examples give a flavour of the&lt;br&gt;
+bibliometric research that is possible using the emerging digital libraries:&lt;br&gt;
+&lt;i&gt;examining the âphysicalâ characteristics of archived documents&lt;/i&gt;&lt;br&gt;
+One relatively straightforward type of bibliometric study characterizes the&lt;br&gt;
+formats of different literatures.   For example, Figure 1 presents a the range of the size&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">9</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+of computer science technical reports as measured by their length in pages.   Of the&lt;br&gt;
+45,720 documents in the CSTR collection as of April 1998, nearly 1600 did not contain&lt;br&gt;
+page divisions in their files (and hence are excluded from analysis). Note that the&lt;br&gt;
+number of pages in the shorter documents (&amp;lt;50 pages) falls into an approximately&lt;br&gt;
+normal distribution (slightly skewed to the left), while presumably the longer&lt;br&gt;
+documents represent Mastersâ and Doctoral theses. A surprising number of documents&lt;br&gt;
+are very short (between one and 5 pages); these may represent the type of condensed&lt;br&gt;
+results frequently found in the âtechnical notesâ, âshort papersâ, and âposter sessionsâ&lt;br&gt;
+of computing conferences and journals. The average number of pages per document,&lt;br&gt;
+27.5, appears to be slightly longer than the common upper bound for a computing&lt;br&gt;
+journal article, although this observation must be confirmed by a similar study of the&lt;br&gt;
+lengths of formally published computing articles.&lt;br&gt;
+This type of analysis is of particular interest for technical reports, since they&lt;br&gt;
+have not been studied in the same detail as formally published papers.  A comparison of&lt;br&gt;
+the physical characteristics of the formal and informal literature could provide&lt;br&gt;
+supporting evidence for common beliefs about the relationship between the two types&lt;br&gt;
+of documents. For example,  do publishing constraints force journal and proceedings&lt;br&gt;
+articles to be shorter than technical reports, and therefore presumably omit technical&lt;br&gt;
+details of findings?  Do technical reports contain more/less extensive reference sections?&lt;br&gt;
+If reference sections of technical reports are longer than those of published articles, then&lt;br&gt;
+citation links are being ommitted in published works; if technical reports contain fewer&lt;br&gt;
+references, then this may confirm earlier indications that computer scientists tend to&lt;br&gt;
+âresearch firstâ and do literature surveys later [6].&lt;br&gt;
+Figure 1.  Range of sizes of CS technical reports, measured by number of pages&lt;br&gt;
+&lt;i&gt;obsolescence studies.&lt;/i&gt;&lt;br&gt;
+A document is considered obsolete when it is no longer referenced by the&lt;br&gt;
+current literature. Typically, documents receive their greatest number and frequency of&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">10</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+citations immediately after publication, and the frequency of citation falls rapidly as time&lt;br&gt;
+passes. One technique for estimating the obsolescence rate of a body of  literatureâ the&lt;br&gt;
+&lt;i&gt;synchronous&lt;/i&gt; method â  is to find the median date in the references of the documents.&lt;br&gt;
+This median date is subtracted from the year of publication for the documents, yielding&lt;br&gt;
+the &lt;i&gt;median citation age&lt;/i&gt;.  As would be expected, this median varies between the&lt;br&gt;
+disciplines.  Typically the social sciences and arts have a higher median citation age&lt;br&gt;
+than the âhardâ sciences and engineering, indicating that documents obsolesce more&lt;br&gt;
+quickly for the latter fields.&lt;br&gt;
+As noted in Section 2, references are not generally explicitly tagged in existing&lt;br&gt;
+digital repositories.  However, reference dates can usually be extracted from the&lt;br&gt;
+document text by first locating the reference section (usually delimited by a &amp;quot;references&amp;quot;&lt;br&gt;
+or &amp;quot;bibliography&amp;quot; section heading), and then extracting all numbers in the appropriate&lt;br&gt;
+ranges for dates  for the field under study.&lt;br&gt;
+To illustrate this process, 188 technical reports were sampled from Internet-&lt;br&gt;
+accessible repositories1 and used as source documents for a synchronous obsolescence&lt;br&gt;
+study.  Conveniently, the repositories chosen organize technical reports into sub-&lt;br&gt;
+directories by their date of publication.  The reference dates for each technical report&lt;br&gt;
+were automatically extracted by software that scanned the documentâs file for numbers&lt;br&gt;
+of the form 19XX, since previous studies indicate that few if any computing reports&lt;br&gt;
+reference documents published in previous centuries [5].  Table 1 presents the median&lt;br&gt;
+citation age calculated for these documents, broken down by repository and the year of&lt;br&gt;
+publication for the source documents from which the reference dates were extracted:&lt;br&gt;
+Table 1.  Median citation ages for technical report repositories&lt;br&gt;
+The median citation age ranges between 2 and 4 years, which is consistent with&lt;br&gt;
+previous examinations of computing and information systems literature ([5], [4]).&lt;br&gt;
+When graphed, the distribution of reference dates show the exponential curve typically&lt;br&gt;
+found in obsolescence studies, including the final droop due to an âimmediacy effectâ&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">11</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+as fewer very new documents are available for citation [7].  These types of results&lt;br&gt;
+provide confirmation that references used in computer science technical reports (the pre-&lt;br&gt;
+eminent âgrey literatureâ of  the computing field) conforms to the same patterns as&lt;br&gt;
+references found in the formally published literature.&lt;br&gt;
+&lt;i&gt;co-citation and bibliographic coupling studies&lt;/i&gt;&lt;br&gt;
+The rate at which documents cite each other (co-citation) or cite the same&lt;br&gt;
+documents (bibliographic coupling) can be used to produce &amp;quot;maps&amp;quot; of a subject&lt;br&gt;
+literature.  These techniques rely on analysis of the references of documents, and these&lt;br&gt;
+references must be in a common format.  While digital libraries contain full text of&lt;br&gt;
+documents, their references are not standardized, and indeed are not  even tagged as&lt;br&gt;
+such.  To perform these studies the references must be manually extracted and&lt;br&gt;
+processedâa tedious process that is only worthwhile for documents (such as technical&lt;br&gt;
+reports) that are not included in existing citation databases such as the Science Citation&lt;br&gt;
+Index and Social Science Citation Index.&lt;br&gt;
+&lt;i&gt;detecting cycles or regularities in the rate of production of research&lt;/i&gt;&lt;br&gt;
+Analysis of trends in the production of technical reports can give indications&lt;br&gt;
+about working conditions that affect research; for example, is more research produced&lt;br&gt;
+over the summer, when the teaching load is lighter?  or is research steadily produced&lt;br&gt;
+throughout the year?&lt;br&gt;
+Figure 2.  Distribution of the number of documents submitted to hep-th, 1992-1994&lt;br&gt;
+Figures 2 and 3 present statistics on document accumulation in the hep-th (high&lt;br&gt;
+energy physics) e-print server, a part of the PHYSICS E-PRINT ARCHIVE.  This system&lt;br&gt;
+is one of the oldest formal pre-print archives, and has become the primary means for&lt;br&gt;
+information dissemination in its field.  Examination of these figures reveals several&lt;br&gt;
+trends.  Clearly the absolute number of documents deposited in the repository has&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">12</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+tended to increase over the time period.  For all three years, research production has its&lt;br&gt;
+lowest point in January and February, increases through May and June, then decreases&lt;br&gt;
+until August and September.  At that point the rate of production steps up, reaching a&lt;br&gt;
+yearly peak in November and December.  This pattern is less clear for 1992, which&lt;br&gt;
+might be expected as the archive was established in mid-1991.&lt;br&gt;
+Figure 3.  Distribution of the percentage of documents submitted to hep-th, 1992-1994&lt;br&gt;
+&lt;b&gt;4.  Analysis of usage data&lt;/b&gt;&lt;br&gt;
+The emerging Internet-based digital libraries will permit research on scientific&lt;br&gt;
+information collection and use at a much finer grain than is possible with current paper&lt;br&gt;
+libraries or online bibliographic databases.  Current bibliometric or scientometric&lt;br&gt;
+research of this type must measure information use indirectly â for example,  through&lt;br&gt;
+examination of the list of references appended to published articles.  However, it is well&lt;br&gt;
+known that authors do not necessarily include in the reference list all documents that&lt;br&gt;
+could have been cited, and conversely that not all references listed may have been&lt;br&gt;
+actually âusedâ in performing the research; citation behavior can be affected by a&lt;br&gt;
+number of motivating factors (Garfield lists &lt;i&gt;15&lt;/i&gt; possible reasons in [8]).&lt;br&gt;
+Digital library transaction logs provide a powerful tool for direct analysis of&lt;br&gt;
+document âusageâ: since  digital libraries contain the actual document (rather than only a&lt;br&gt;
+document surrogate), the relative amount of âuseâ that a digital libraryâs clients make of&lt;br&gt;
+a given document sees can be estimated from the number of times the document file is&lt;br&gt;
+downloaded (and, presumably, the document is read). Note that file downloading is a&lt;br&gt;
+much stronger statement on the part of the user than, for example, having a&lt;br&gt;
+bibliographic record appear in the query result set for a conventional bibliographic&lt;br&gt;
+system; the user downloads only &lt;i&gt;after&lt;/i&gt; the document has been found potentially relevant&lt;br&gt;
+through examination of its document surrogate. Additionally,  downloading is&lt;br&gt;
+frequently time-consuming  and sometimes costly (depending on local pricing for&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">13</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+Internet access). Downloaded documents are therefore highly likely at least to be&lt;br&gt;
+scanned, if not read closely.  The transaction logs for a digital library can provide a&lt;br&gt;
+global picture of the use of documents in the collection, since all user interactions with&lt;br&gt;
+the library can be automatically logged  for analysis. By contrast, it is of course&lt;br&gt;
+impossible to track usage of print bibliographies, and very difficult to monitor usage of&lt;br&gt;
+bibliographic data available on CD-ROM across more than one or two sites.&lt;br&gt;
+Furthermore, analysis of search requests by geographic location, institution,&lt;br&gt;
+and sometimes even individual user are also possible.  As an example, Table 2 presents&lt;br&gt;
+a portion of the summary of usage statistics (broken down by domain code) for queries&lt;br&gt;
+to the computer science technical collection of the NEW ZEALAND DIGITAL LIBRARY.&lt;br&gt;
+Examination of the data indicates that the heaviest use of the collection comes from&lt;br&gt;
+North America, Europe (particularly Germany and Finland), as well as the local New&lt;br&gt;
+Zealand community and nearby Australia.  As expected for such a collection, a large&lt;br&gt;
+proportion of users are from educational (.edu) institutions; surprisingly, however, a&lt;br&gt;
+similar number of queries come from commercial (.com) organizations, indicating&lt;br&gt;
+perhaps that the documents are seeing use in commercial research and development&lt;br&gt;
+units.&lt;br&gt;
+Table 2. Accesses to the NEW ZEALAND DIGITAL LIBRARY CS collection  by Domain&lt;br&gt;Code&lt;br&gt;
+Of course, usage levels can also be further broken down by IP number&lt;br&gt;
+(indicating  institutions), and systems requiring users to register may also be able to&lt;br&gt;
+analyze usage on an individual basis. Since the query strings themselves are also&lt;br&gt;
+recorded in the transaction logs, this domain/institution/individual activity could also be&lt;br&gt;
+linked to specific subjects through the query terms.  Summaries of this type could be&lt;br&gt;
+invaluable for studies of geographic diffusion and distribution of research topics.&lt;br&gt;
+Transaction log analysis can also indicate time-related  patterns in the&lt;br&gt;
+information seeking behavior of digital library users.   As a sample of this type of&lt;br&gt;
+analysis,  Paul Ginsparg notes a seven day periodicity in the number of search requests&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">14</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+made to the PHYSICS E-PRINT archives (Figure 4, reproduced from [9]).  From this he&lt;br&gt;
+adduces that many physicists do not yet have weekend access to the Internet (an&lt;br&gt;
+alternative, slightly more cynical hypothesis is that even high energy theoretical&lt;br&gt;
+physicists take the weekend off).&lt;br&gt;
+Figure 4.  Summary of search requests to the physics pre-print archives&lt;br&gt;
+&lt;b&gt;5.  Conclusion&lt;/b&gt;&lt;br&gt;
+This study suggests opportunities for conducting bibliometric research on the&lt;br&gt;
+evolving digital libraries.  These repositories are suitable platforms for conventional&lt;br&gt;
+bibliometric techniques (such as obsolescence studies, quantification of physical&lt;br&gt;
+characteristics of documents comprising a subject literature, time analysis, etc.).  The&lt;br&gt;
+ability to directly monitor access to documents in digital libraries also enables&lt;br&gt;
+researchers to explicitly quantify document usage, as well as to implicitly measure&lt;br&gt;
+usage through citations.  Additional facilities could aid in the performance of&lt;br&gt;
+bibliographic experiments, such as: improved tagging of document fields; provision of&lt;br&gt;
+utilities to strip out titles, authors, etc. from common document formats; and the ability&lt;br&gt;
+to easily eliminate duplicate entries from downloaded library subsets.  Unfortunately,&lt;br&gt;
+the most useful of these additional facilities â those associated with a higher degree of&lt;br&gt;
+cataloging â run counter to the underlying philosophy of many digital libraries:  to&lt;br&gt;
+avoid, if possible,  manual processing and formal cataloging of documents.   While&lt;br&gt;
+adherence to this principle can limit the accuracy of fielded searching (or indeed,&lt;br&gt;
+preclude it altogether), it can also avoid the cataloging bottleneck and permit digital&lt;br&gt;
+libraries to provide access to larger numbers of documents.&lt;br&gt;
+The digital libraries complement the information currently available through&lt;br&gt;
+paper, online, and CD-ROM bibliographic resources.  While these latter databases&lt;br&gt;
+generally have the advantage of standardized formatting of bibliographic fields, the&lt;br&gt;
+digital libraries are freely accessible, often contain &amp;quot;grey literature&amp;quot; that is otherwise&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">15</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+unavailable for analysis, and generally make the full text of documents available.  The&lt;br&gt;
+insights gained from analysis of digital libraries will add to the store of &amp;quot;information&lt;br&gt;
+about information&amp;quot; that we have gained from older types of bibliographic repositories.&lt;br&gt;
+&lt;b&gt;References&lt;/b&gt;&lt;br&gt;
+[1] Bollacker, K.D., S. Lawrence, and C.L.Giles, CiteSeer: An Autonomous Web&lt;br&gt;
+Agent for Automatic  Retrieval  and  Identification  of  Interesting  Publications,&lt;br&gt;
+&lt;i&gt;Proceedings of the Second International Conference  on  Autonomous  Agents&lt;/i&gt;&lt;br&gt;
+(Minneapolis/St. Paul, May 9-13), 1998.&lt;br&gt;
+[2] Bowman, C.M., P.B. Danzig, U. Manber,  and M.F. Schwartz,  Scalable Internet&lt;br&gt;
+resource discovery:  Research problems and approaches,  &lt;i&gt;Communications of&lt;/i&gt;&lt;br&gt;
+&lt;i&gt;the ACM 37(8)&lt;/i&gt;  (1994)  98-107.&lt;br&gt;
+[3] Burton, Hilary D. , Use of a virtual information system for bibliometric analysis,&lt;br&gt;
+&lt;i&gt;Informaton Processing &amp;amp; Management 24(1)&lt;/i&gt;  (1988) 39-44.&lt;br&gt;
+[4] Cunningham, S.J., An empirical investigation of the obsolescence rate for&lt;br&gt;
+information systems literature, &lt;i&gt;Library and Information Science&lt;/i&gt;&lt;br&gt;
+&lt;i&gt;Research&lt;/i&gt;., 1996, http://library.fgcu.edu/iclc/lisrissu.htm&lt;br&gt;
+ [5]  Cunningham,  S.J.,  and  D.  Bocock,    Obsolescence  of  computing  literature.&lt;br&gt;
+&lt;i&gt;Scientometrics&lt;/i&gt;  &lt;i&gt;34(2) &lt;/i&gt; (1995), pp. 255-262.&lt;br&gt;
+ [6] Cunningham, S.J. and Lynn Silipigni Connaway, Information searching&lt;br&gt;
+preferences and practices of computer science researchers, &lt;i&gt;Proceedings of&lt;/i&gt;&lt;br&gt;
+&lt;i&gt;OZCHI '96&lt;/i&gt; (1996)  294-299.&lt;br&gt;
+[7] de Solla Price, D.J.,  Citation measures of hard science, soft science, technology,&lt;br&gt;
+and nonscience.  In: C.E. Nelson  and  D.K.  Pollock  (eds),  &lt;i&gt;Communication&lt;/i&gt;&lt;br&gt;
+&lt;i&gt;among scientists and engineers&lt;/i&gt;  (Heath Lexington, 1970).&lt;br&gt;
+[8]  Garfield, E., &lt;i&gt;Citation Indexing:  Its theory and application in Science, Technology&lt;/i&gt;&lt;br&gt;
+&lt;i&gt;and Humanities (&lt;/i&gt;Wiley, 1979).&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">16</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+[9]  Ginsparg, P.  After dinner remarks:  14 Oct â94 APS meeting at LANL, 1994&lt;br&gt;
+(&amp;lt;URL: http://xxx.lanl.gov/blurb&amp;gt; ).&lt;br&gt;
+[10] Ginsparg, P., First steps towards electronic research communication, &lt;i&gt;Computers&lt;/i&gt;&lt;br&gt;
+&lt;i&gt;in Physics 8(4)&lt;/i&gt; (1994)  390-401.  &lt;br&gt;
+[11] Hallmark,  J., Scientists' access and retrieval of references cited in their recent&lt;br&gt;
+journal articles, &lt;i&gt; College and Research Libraries 55(3)&lt;/i&gt;  (1994) 199-210.&lt;br&gt;
+[12] Hawkins, D.T. , Unconventional uses of on-line information retrieval systems:&lt;br&gt;
+on-line bibliometric studies,  &lt;i&gt;Journal of the American Society for Information&lt;/i&gt;&lt;br&gt;
+&lt;i&gt;Science 28&lt;/i&gt;  (1977)  13-18.&lt;br&gt;
+[13] McGhee, P.E. , P.R. Skinner, K. Roberto,  N.J. Ridenour,  and S.M. Larson,&lt;br&gt;
+Using online databases to study current research trends:  an online bibliometric&lt;br&gt;
+study, &lt;i&gt;Library and Information Science Research 9&lt;/i&gt;  (1987)   285-291.&lt;br&gt;
+[14] Maly, K., E.A. Fox,  J.C. French,  and A.L. Selman,  Wide area technical report&lt;br&gt;
+server    (&lt;i&gt;Technical    Report  ,  &lt;/i&gt;  Dept.  of  Computer  Science,  Old  Dominion&lt;br&gt;
+University, &lt;br&gt;
+1994. &lt;br&gt;
+Also &lt;br&gt;
+available &lt;br&gt;
+at &lt;br&gt;
+ &lt;br&gt;
+ &lt;br&gt;
+&amp;lt;URL:&lt;br&gt;
+http://www.cs.odu.edu/WATERS/WATERS-paper.ps&amp;gt; ).&lt;br&gt;
+[15] Sigogneau, M.J. , S. Bain, J.P. Courtial, and H. Feillet,  Scientific innovation in&lt;br&gt;
+bibliographical databases:  a comparative study of the Science Citation Index&lt;br&gt;
+and the Pascal database,  &lt;i&gt;Scientometrics 22(1)&lt;/i&gt;   (1991)  65-82.&lt;br&gt;
+[16] Witten, I.H., S.J. Cunningham, M. Vallabh,  and T.C. Bell,  A New Zealand&lt;br&gt;
+digital library for computer science research,  &lt;i&gt;Proceedings of Digital Libraries&lt;/i&gt;&lt;br&gt;
+&lt;i&gt;'95&lt;/i&gt; (1995) 25-30.&lt;br&gt;
+[17]  Witten, I.H., C. Nevill-Manning, and S.J. Cunningham, A public library based&lt;br&gt;
+on full-text retrieval, &lt;i&gt;Communications of the ACM&lt;/i&gt; 41(4), 1998, p. 71&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">17</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+                                    &lt;br&gt;
+1Documents were randomly sampled from the DEC&lt;br&gt;
+(ftp://crl.dec.com/pub/DEC/CRL/tech-reports/), Sony&lt;br&gt;
+(ftp://ftp.csl.sony.co.jp/CSL/CSL-Papers), and Ohio (ftp://archive.cis.ohio-&lt;br&gt;
+state.edu/pub/tech-report/) technical report repositories&lt;br&gt;
+&lt;hr&gt;
+
+
+</Content>
+</Section>
+</Section>
+</Archive>
Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Enhanced-PDF/archives/HASH1a9c.dir/doc.xml
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Enhanced-PDF/archives/HASH1a9c.dir/doc.xml	(revision 37429)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Enhanced-PDF/archives/HASH1a9c.dir/doc.xml	(revision 37429)
@@ -0,0 +1,811 @@
+<?xml version="1.0" encoding="utf-8" standalone="no"?>
+<!DOCTYPE Archive SYSTEM "http://greenstone.org/dtd/Archive/1.0/Archive.dtd">
+<Archive>
+<Section>
+  <Description>
+    <Metadata name="gsdldoctype">indexed_doc</Metadata>
+    <Metadata name="Language">en</Metadata>
+    <Metadata name="Encoding">utf8</Metadata>
+    <Metadata name="URL">http://Scratch/ak19/gs2-diffcol-26Jul2021/collect/Enhanced-PDF/tmp/1678158430/pdf01.html</Metadata>
+    <Metadata name="UTF8URL">http://Scratch/ak19/gs2-diffcol-26Jul2021/collect/Enhanced-PDF/tmp/1678158430/pdf01.html</Metadata>
+    <Metadata name="Title">Greenstone: A Comprehensive Open-Source Digital Library Software System Ian H. Witten,* Rodger J....</Metadata>
+    <Metadata name="gsdlsourcefilename">import/pdf01.pdf</Metadata>
+    <Metadata name="gsdlsourcefilerenamemethod">url</Metadata>
+    <Metadata name="gsdlconvertedfilename">tmp/1678158430/pdf01.html</Metadata>
+    <Metadata name="OrigSource">pdf01.html</Metadata>
+    <Metadata name="Source">pdf01.pdf</Metadata>
+    <Metadata name="SourceFile">pdf01.pdf</Metadata>
+    <Metadata name="Plugin">PDFv1Plugin</Metadata>
+    <Metadata name="FileSize">269487</Metadata>
+    <Metadata name="FilenameRoot">pdf01</Metadata>
+    <Metadata name="FileFormat">PDF</Metadata>
+    <Metadata name="srcicon">_iconpdf_</Metadata>
+    <Metadata name="srclink_file">doc.pdf</Metadata>
+    <Metadata name="srclinkFile">doc.pdf</Metadata>
+    <Metadata name="NumPages">9</Metadata>
+    <Metadata name="gsdlthistype">Paged</Metadata>
+    <Metadata name="ex.ExifTool.ExifToolVersion">12.19</Metadata>
+    <Metadata name="ex.File.Directory">/Scratch/ak19/gs2-diffcol-26Jul2021/collect/Enhanced-PDF/import</Metadata>
+    <Metadata name="ex.File.FileAccessDate">2023:03:07 16:07:07+13:00</Metadata>
+    <Metadata name="ex.File.FileInodeChangeDate">2023:03:07 16:07:07+13:00</Metadata>
+    <Metadata name="ex.File.FileModifyDate">2023:03:07 16:07:07+13:00</Metadata>
+    <Metadata name="ex.File.FileName">pdf01.pdf</Metadata>
+    <Metadata name="ex.File.FilePermissions">100664</Metadata>
+    <Metadata name="ex.File.FileSize">269487</Metadata>
+    <Metadata name="ex.File.FileType">PDF</Metadata>
+    <Metadata name="ex.File.FileTypeExtension">PDF</Metadata>
+    <Metadata name="ex.File.MIMEType">application/pdf</Metadata>
+    <Metadata name="ex.PDF.Author">Bronwyn</Metadata>
+    <Metadata name="ex.PDF.CreateDate">2000:03:02 15:21:24</Metadata>
+    <Metadata name="ex.PDF.Creator">Microsoft Word</Metadata>
+    <Metadata name="ex.PDF.Linearized">false</Metadata>
+    <Metadata name="ex.PDF.PDFVersion">1.2</Metadata>
+    <Metadata name="ex.PDF.PageCount">9</Metadata>
+    <Metadata name="ex.PDF.Producer">Acrobat PDFWriter 4.0 for Power Macintosh</Metadata>
+    <Metadata name="Identifier">HASH1a9cea0f239f754007681b</Metadata>
+    <Metadata name="lastmodified">1678158427</Metadata>
+    <Metadata name="lastmodifieddate">20230307</Metadata>
+    <Metadata name="oailastmodified">1678158430</Metadata>
+    <Metadata name="oailastmodifieddate">20230307</Metadata>
+    <Metadata name="assocfilepath">HASH1a9c.dir</Metadata>
+    <Metadata name="gsdlassocfile">pdf01-2_1.jpg:image/jpeg:</Metadata>
+    <Metadata name="gsdlassocfile">pdf01-3_1.jpg:image/jpeg:</Metadata>
+    <Metadata name="gsdlassocfile">pdf01-4_1.jpg:image/jpeg:</Metadata>
+    <Metadata name="gsdlassocfile">pdf01-5_1.jpg:image/jpeg:</Metadata>
+    <Metadata name="gsdlassocfile">pdf01-7_1.jpg:image/jpeg:</Metadata>
+    <Metadata name="gsdlassocfile">pdf01-8_1.jpg:image/jpeg:</Metadata>
+    <Metadata name="gsdlassocfile">doc.pdf:application/pdf:</Metadata>
+  </Description>
+  <Content>
+
+ 
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+</Content>
+<Section>
+  <Description>
+    <Metadata name="Title">1</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+&lt;b&gt;Greenstone:  A Comprehensive Open-Source&lt;/b&gt;&lt;br&gt;
+&lt;b&gt;Digital Library Software System&lt;/b&gt;&lt;br&gt;
+&lt;i&gt;Ian H. Witten,* Rodger J. McNab,â  Stefan J. Boddie,* David Bainbridge*&lt;/i&gt;&lt;br&gt;
+* Dept of Computer Science&lt;br&gt;
+â  Digilib Systems&lt;br&gt;
+University of Waikato, New Zealand&lt;br&gt;
+Hamilton, New Zealand&lt;br&gt;
+E-mail:  {ihw, sjboddie, davidb}@cs.waikato.ac.nz&lt;br&gt;
+E-mail:  rodger@digilibs.com&lt;br&gt;
+&lt;b&gt;ABSTRACT&lt;/b&gt;&lt;br&gt;
+multilingual information retrieval to distributed computing&lt;br&gt;protocols, from interoperability to search engine&lt;br&gt;
+This paper describes the Greenstone digital library&lt;br&gt;
+technology, from metadata standards to multiformat&lt;br&gt;
+software, a comprehensive, open-source system for the&lt;br&gt;
+document parsing, from multimedia to multiple operating&lt;br&gt;
+construction and presentation of information collections.&lt;br&gt;
+systems, from Web browsers to plug-and-play DVDs.&lt;br&gt;
+Collections built with Greenstone offer effective full-text&lt;br&gt;searching and metadata-based browsing facilities that are&lt;br&gt;
+The Greenstone Digital Library Software from the New&lt;br&gt;
+attractive and easy to use. Moreover, they are easily&lt;br&gt;
+Zealand Digital Library (NZDL) project tackles this issue&lt;br&gt;
+maintainable and can be augmented and rebuilt entirely&lt;br&gt;
+by providing a new way of organizing information and&lt;br&gt;
+automatically. The system is extensible: software&lt;br&gt;
+making it available over the Internet. A &lt;i&gt;collection&lt;/i&gt; of&lt;br&gt;
+âpluginsâ accommodate different document and metadata&lt;br&gt;
+information comprises several (typically several thousand,&lt;br&gt;
+types.&lt;br&gt;
+or several million) &lt;i&gt;documents&lt;/i&gt;, and a uniform interface is&lt;br&gt;provided to all documents in a collection. A library may&lt;br&gt;
+&lt;b&gt;INTRODUCTION&lt;/b&gt;&lt;br&gt;
+include many different collections, each organized&lt;br&gt;differentlyâthough there is a strong family resemblance in&lt;br&gt;
+Notwithstanding intense research activity in the digital&lt;br&gt;
+how collections are presented.&lt;br&gt;
+library field during the second half of the 1990s,&lt;br&gt;comprehensive software systems for creating digital&lt;br&gt;
+Making information available using this system is far more&lt;br&gt;
+libraries are not widely available. In fact, the usual solution&lt;br&gt;
+than âjust putting it on the Web.â The collection becomes&lt;br&gt;
+when creating a digital library is also the most&lt;br&gt;
+maintainable, searchable, and browsable. Each collection,&lt;br&gt;
+obviousâjust put it on the Web. But consider how much&lt;br&gt;
+prior to presentation, undergoes a âbuildingâ process that,&lt;br&gt;
+effort is involved in constructing a Web site for a digital&lt;br&gt;
+once established, is completely automatic. This process&lt;br&gt;
+library. To be effective it needs to be visually attractive&lt;br&gt;
+creates all the structures that are used at run-time for&lt;br&gt;
+and ergonomically easy to use, incorporate convenient and&lt;br&gt;
+accessing the collection. Searching is based on various&lt;br&gt;
+powerful searching capabilities, and offer rich and natural&lt;br&gt;
+indexes, while browsing is based on various metadata;&lt;br&gt;
+browsing facilities. Above all it must be easy to maintain&lt;br&gt;
+support structures for both are created during the building&lt;br&gt;
+and augment, which presents a significant challenge if any&lt;br&gt;
+operation. When new material appears it can be fully&lt;br&gt;
+manual organization is involved.&lt;br&gt;
+incorporated into the collection by rebuilding.&lt;br&gt;
+The alternative is to automate these activities through&lt;br&gt;
+To address the exceptionally broad demands of digital&lt;br&gt;
+software tools. But the broad scope of digital library&lt;br&gt;
+libraries, the system is public and extensible. It is issued&lt;br&gt;
+requirements makes this a daunting prospect. Ideally the&lt;br&gt;
+under the Gnu public license and, in the spirit of open-&lt;br&gt;
+software should incorporate facilities ranging from&lt;br&gt;
+source software, users are invited to contribute&lt;br&gt;modifications and enhancements. Only through an&lt;br&gt;international cooperative effort will digital library software&lt;br&gt;become sufficiently comprehensive to meet the worldâs&lt;br&gt;needs. Currently the Greenstone software is used at sites in&lt;br&gt;Canada, Germany, New Zealand, Romania, UK, and the&lt;br&gt;US, and collections range from newspaper articles to&lt;br&gt;technical documents, from educational journals to oral&lt;br&gt;history, from visual art to folksongs. The software has&lt;br&gt;been used for collections in many different languages, and&lt;br&gt;for CD-ROMs that have been published by the United&lt;br&gt;Nations and other humanitarian agencies in Belgium,&lt;br&gt;France, Japan, and the US for distribution in developing&lt;br&gt;countries (Humanity Libraries, 1998; PAHO, 1999;&lt;br&gt;UNESCO, 1999; UNU, 1998). Further details can be&lt;br&gt;obtained from &lt;i&gt;www.nzdl.org&lt;/i&gt;.&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">2</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+&lt;IMG src=&quot;_httpdocimg_/pdf01-2_1.jpg&quot;&gt;&lt;br&gt;
+become a first-class component of the library. And what&lt;br&gt;permits it to be integrated into existing searching and&lt;br&gt;browsing structures without any manual intervention is&lt;br&gt;&lt;i&gt;metadata&lt;/i&gt;. This provides sufficient focus to the concept of&lt;br&gt;âdigital libraryâ to support the development of a&lt;br&gt;construction kit.&lt;br&gt;
+&lt;b&gt;OVERVIEW OF GREENSTONE&lt;/b&gt;&lt;br&gt;
+ &lt;br&gt;Information collections built by Greenstone combine&lt;br&gt;extensive full-text search facilities with browsing indexes&lt;br&gt;based on different metadata types. There are several ways&lt;br&gt;for users to find information, although they differ between&lt;br&gt;collections depending on the metadata available and the&lt;br&gt;collection design. Typically you can &lt;i&gt;search for particular&lt;br&gt;words&lt;/i&gt; that appear in the text, or within a section of a&lt;br&gt;document, or within a title or section heading. You can&lt;br&gt;&lt;i&gt;browse documents by title&lt;/i&gt;: just click on the displayed book&lt;br&gt;icon to read it. You can &lt;i&gt;browse documents by subject&lt;/i&gt;.&lt;br&gt;Subjects are represented by bookshelves: just click on a&lt;br&gt;shelf to see the books. Where appropriate, documents&lt;br&gt;
+&lt;b&gt;Figure 1: Searching the HDL collection&lt;/b&gt;&lt;br&gt;
+come complete with a table of contents (constructed&lt;br&gt;automatically): you can click on a chapter or subsection to&lt;br&gt;
+This paper sets the scene with a brief discussion of what a&lt;br&gt;
+open it, expand the full table of contents, or expand the full&lt;br&gt;
+digital library is. We then give an overview of the facilities&lt;br&gt;
+document.&lt;br&gt;
+offered by Greenstone and show how end users find&lt;br&gt;information in collections. Next we describe the files and&lt;br&gt;
+ &lt;br&gt;An example of searching is shown in Figure 1 where&lt;br&gt;
+directories involved in a collection, and then discuss the&lt;br&gt;
+documents in the Global Help Projectâs Humanity&lt;br&gt;
+processes of updating existing collections and creating new&lt;br&gt;
+Development Library (HDL) are being searched for&lt;br&gt;
+ones, including extending the software to provide new&lt;br&gt;
+chapters matching the word &lt;i&gt;butterfly&lt;/i&gt;. In Figure 2 the same&lt;br&gt;
+facilities. We conclude with an overview of related work.&lt;br&gt;
+collection is being browsed by subject: by clicking on the&lt;br&gt;bookshelf icons the user has discovered an item under&lt;br&gt;
+&lt;b&gt;WHAT IS A DIGITAL LIBRARY?&lt;/b&gt;&lt;br&gt;
+Section 16, Animal Husbandry. Pursuing an interest in&lt;br&gt;butterfly farming, the user selects a book by clicking on its&lt;br&gt;
+ &lt;br&gt;Ten definitions of the term âdigital libraryâ have been&lt;br&gt;
+book icon. In Figure 3 the front cover of the book is&lt;br&gt;
+culled from the literature by Fox (1998), and their spirit is&lt;br&gt;
+displayed as a graphic on the left, and the automatically&lt;br&gt;
+captured in the following brief characterization:&lt;br&gt;
+constructed table of contents appears at the start of the&lt;br&gt;
+ &lt;br&gt;
+document. The current focus, &lt;i&gt;Introduction and Summary&lt;/i&gt;,&lt;br&gt;
+&lt;i&gt;A collection of digital objects, including text,&lt;/i&gt;&lt;br&gt;
+is shown in bold in the table of contents with its text&lt;br&gt;
+&lt;i&gt;video, and audio, along with methods for access&lt;/i&gt;&lt;br&gt;
+starting further down the page.&lt;br&gt;
+&lt;i&gt;and retrieval, and for selection, organization&lt;br&gt;and maintenance of the collection&lt;/i&gt;&lt;br&gt;
+ &lt;br&gt;In accordance with Leskâs advice, a statement of purpose&lt;br&gt;
+ &lt;br&gt;
+and coverage accompanies each collection, along with an&lt;br&gt;
+(Akscyn and Witten, 1998). Lesk (1998) views digital&lt;br&gt;
+explanation of how it is organized (Figure 1 shows the&lt;br&gt;
+libraries as âorganized collections of digital information,â&lt;br&gt;
+start of this). A distinction is made between &lt;i&gt;searching&lt;/i&gt; and&lt;br&gt;
+and wisely recommends that they articulate the principles&lt;br&gt;
+&lt;i&gt;browsing&lt;/i&gt;. Searching is full-text, andâdepending on the&lt;br&gt;
+governing what is included and how the collection is&lt;br&gt;
+collectionâs designâthe user can choose between indexes&lt;br&gt;
+organized.&lt;br&gt;
+built from different parts of the documents, or from&lt;br&gt;
+ &lt;br&gt;Digital libraries are generally distinguished from the&lt;br&gt;
+different metadata. Some collections have an index of full&lt;br&gt;
+World-Wide Web, the essential difference being in&lt;br&gt;
+documents, an index of sections, an index of paragraphs,&lt;br&gt;
+selection and organization. But they are not generally&lt;br&gt;
+an index of titles, and an index of section headings, each of&lt;br&gt;
+distinguished from a web &lt;i&gt;site&lt;/i&gt;: indeed, virtually all extant&lt;br&gt;
+which can be searched for particular words or phrases.&lt;br&gt;
+digital libraries manifest themselves as a web site. Hence&lt;br&gt;
+Browsing involves data structures created from metadata&lt;br&gt;
+the obvious question: to make a digital library, why not&lt;br&gt;
+that the user can examine: lists of authors, lists of titles,&lt;br&gt;
+just put the information on the Web?&lt;br&gt;
+lists of dates, hierarchical classification structures, and so&lt;br&gt;
+ &lt;br&gt;
+on. Data structures for both browsing and searching are&lt;br&gt;
+But we make a distinction between a digital library and a&lt;br&gt;
+built according to instructions in a configuration file,&lt;br&gt;
+web site that lies at the heart of our software design: one&lt;br&gt;
+which controls both building and serving the collection.&lt;br&gt;
+should easily be able to add new material to a library&lt;br&gt;
+Sample configuration files are discussed below.&lt;br&gt;
+without having to integrate it manually or edit its content&lt;br&gt;in any way. Once added, new material should immediately&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">3</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+&lt;IMG src=&quot;_httpdocimg_/pdf01-3_1.jpg&quot;&gt;&lt;br&gt;
+matter of specifying all the necessary plugins. In order to&lt;br&gt;build browsing indexes from metadata, an analogous&lt;br&gt;scheme of âclassifiersâ is used: classifiers create indexes&lt;br&gt;of various kinds based on metadata. Source documents are&lt;br&gt;brought into the Greenstone system through a process&lt;br&gt;called &lt;i&gt;importing&lt;/i&gt;, which uses the plugins and classifiers&lt;br&gt;specified in the collection configuration file.&lt;br&gt;
+ &lt;br&gt;The international Unicode character set is used throughout,&lt;br&gt;so documentsâand interfacesâcan be written in any&lt;br&gt;language. Collections have so far been produced in&lt;br&gt;English, French, Spanish, German, Maori, Chinese, and&lt;br&gt;Arabic. The NZDL Web site provides numerous examples.&lt;br&gt;Collections can contain text, pictures, and even audio and&lt;br&gt;video clips; a text-only version of the interface is also&lt;br&gt;provided to accommodate visually impaired users.&lt;br&gt;Compression technology is used to ensure best use of&lt;br&gt;storage (Witten &lt;i&gt;et al &lt;/i&gt;., 1999). Most non-textual material is&lt;br&gt;either linked to textual documents or accompanied by&lt;br&gt;textual descriptions (such as photo captions) to allow full-&lt;br&gt;text searching and browsing. However, the architecture&lt;br&gt;
+&lt;b&gt;Figure 2: Browsing the HDL collection by subject&lt;/b&gt;&lt;br&gt;
+permits the implementation of plugins and classifiers even&lt;br&gt;for non-textual data.&lt;br&gt;
+ &lt;br&gt;Rich browsing facilities can be provided by manually&lt;br&gt;
+ &lt;br&gt;
+linking parts of documents together and building explicit&lt;br&gt;
+The system includes an âadministrativeâ function whereby&lt;br&gt;
+indexes and tables of contents. However, manually-created&lt;br&gt;
+specified users can examine the composition of all&lt;br&gt;
+linking becomes difficult to maintain, and often falls into&lt;br&gt;
+collections, protect documents so that they can only be&lt;br&gt;
+disrepair when a collection expands. The Greenstone&lt;br&gt;
+accessed by registered users on presentation of a password,&lt;br&gt;
+software takes a different tack: it facilitates &lt;i&gt;maintainability&lt;/i&gt;&lt;br&gt;
+and so on. Logs of user activity are kept that record all&lt;br&gt;
+by creating all searching and browsing structures&lt;br&gt;
+queries made to every Greenstone collection (though this&lt;br&gt;
+automatically from the documents themselves. No links&lt;br&gt;
+facility can be disabled).&lt;br&gt;
+are inserted by hand. This means that when new&lt;br&gt;
+ &lt;br&gt;Although primarily designed for Internet access over the&lt;br&gt;
+documents in the same format become available, they can&lt;br&gt;
+World-Wide Web, collections can be made available, in&lt;br&gt;
+be added automatically. Indeed, for some collections this is&lt;br&gt;
+precisely the same form, on CD-ROM. In either case they&lt;br&gt;
+done by processes that wake up regularly, scout for new&lt;br&gt;
+are accessed through any Web browser. Greenstone CD-&lt;br&gt;
+material, and rebuild the indexesâall without manual&lt;br&gt;
+ROMs operate on a standalone PC under Windows 3.X,&lt;br&gt;
+intervention.&lt;br&gt;
+95, 98, and NT, and the interaction is identical to accessing&lt;br&gt;
+Collections comprise many documents: thousands, tens of&lt;br&gt;
+the collection on the Webâexcept that response is faster&lt;br&gt;
+thousands, or even millions. Each document may be&lt;br&gt;
+and more predictable. The requirement to operate on early&lt;br&gt;
+hierarchically organized into &lt;i&gt;sections&lt;/i&gt; (subsections, sub-&lt;br&gt;
+Windows systems is one that plagues the software design,&lt;br&gt;
+subsections, and so on). Each section comprises one or&lt;br&gt;
+but is crucial for many usersâparticularly those in&lt;br&gt;
+more &lt;i&gt;paragraphs&lt;/i&gt;. Metadata such as author, title, date,&lt;br&gt;
+underdeveloped countries seeking access to humanitarian&lt;br&gt;
+keywords, and so on, may be associated with documents,&lt;br&gt;
+aid collections. If the PC is connected to a network&lt;br&gt;
+or with individual sections of documents. This is the raw&lt;br&gt;
+(intranet or Internet), a custom-built Web server provided&lt;br&gt;
+material for indexes. It must either be provided explicitly&lt;br&gt;
+on each CD makes exactly the same information available&lt;br&gt;
+for each document and section (for example, in an&lt;br&gt;
+to others through their standard Web browser. The use of&lt;br&gt;
+accompanying spreadsheet) or be derivable automatically&lt;br&gt;
+compression ensures that the greatest possible volume of&lt;br&gt;
+from the source documents. Metadata is converted to&lt;br&gt;
+information can be packed on to a CD-ROM.&lt;br&gt;
+Dublin Core and stored with the document for internal use.&lt;br&gt;
+ &lt;br&gt;The collection-serving software operates under Unix and&lt;br&gt;
+ &lt;br&gt;In order to accommodate different kinds of source&lt;br&gt;
+Windows NT, and works with standard Web servers. A&lt;br&gt;
+documents, the software is organized so that âpluginsâ can&lt;br&gt;
+flexible process structure allows different collections to be&lt;br&gt;
+be written for new document types. Plugins exist for plain&lt;br&gt;
+served by different computers, yet be presented to the user&lt;br&gt;
+text documents, HTML documents, email documents, and&lt;br&gt;
+in the same way, on the same Web page, as part of the&lt;br&gt;
+bibliographic formats. Word documents are handled by&lt;br&gt;
+same digital library, even as part of the same collection&lt;br&gt;
+saving them as HTML; PostScript ones by applying a&lt;br&gt;
+(McNab and Witten, 1998). Existing collections can be&lt;br&gt;
+preprocessor (Nevill-Manning &lt;i&gt;et al&lt;/i&gt;., 1998). Specially&lt;br&gt;
+updated and new ones brought on-line at any time, without&lt;br&gt;
+written plugins also exist for proprietary formats such as&lt;br&gt;
+bringing the system down; the process responsible for the&lt;br&gt;
+that used by the BBC archives department. A collection&lt;br&gt;
+user interface will notice (through periodic polling) when&lt;br&gt;
+may have source documents in different forms: it is just a&lt;br&gt;
+new collections appear and add them to the list presented&lt;br&gt;to the user.&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">4</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+&lt;IMG src=&quot;_httpdocimg_/pdf01-4_1.jpg&quot;&gt;&lt;br&gt;
+&lt;b&gt;FILES IN A COLLECTION&lt;/b&gt;&lt;br&gt;
+ &lt;br&gt;When a new collection is created or material is added to an&lt;br&gt;existing one, the original source documents are first&lt;br&gt;brought into the system through a process known as&lt;br&gt;âimporting.â This involves converting documents into a&lt;br&gt;simple HTML-like format known as GML (for&lt;br&gt;âGreenstone Markup Languageâ), which includes any&lt;br&gt;metadata associated with the document. Documents are&lt;br&gt;assumed to be in the Unicode UTF-8 code (of which the&lt;br&gt;ASCII characters form a subset).&lt;br&gt;
+ &lt;br&gt;&lt;b&gt;Files and directories&lt;/b&gt;&lt;br&gt;
+ &lt;br&gt;There is a separate directory for each collection, which&lt;br&gt;contains five subdirectories: the original raw material&lt;br&gt;(&lt;i&gt;import&lt;/i&gt;), the GML files created from this (&lt;i&gt;archives&lt;/i&gt;), the&lt;br&gt;final collection as it is served to users (&lt;i&gt;index&lt;/i&gt;), a directory&lt;br&gt;for use during the building process (&lt;i&gt;building&lt;/i&gt;), and one for&lt;br&gt;any supporting files (&lt;i&gt;etc&lt;/i&gt;)âincluding the configuration file&lt;br&gt;
+&lt;b&gt;Figure 3: Reading a book in the HDL&lt;/b&gt;&lt;br&gt;
+that controls the collection creation procedure. Additional&lt;br&gt;files might be required: for example, building a hierarchy&lt;br&gt;of classifications requires a data file of sub-classifications.&lt;br&gt;
+&lt;b&gt;FINDING INFORMATION&lt;/b&gt;&lt;br&gt;
+ &lt;br&gt;Greenstone digital library systems generally include&lt;br&gt;
+ &lt;br&gt;
+several separate collections. A home page allows you to&lt;br&gt;
+&lt;b&gt;The imported documents&lt;/b&gt;&lt;br&gt;
+select a collection; in addition, each collection has its own&lt;br&gt;
+ &lt;br&gt;In order to identify documents internally, a unique object&lt;br&gt;
+âaboutâ page that gives you information about how the&lt;br&gt;
+identifier or OID is assigned to each original source&lt;br&gt;
+collection is organized and the principles governing what&lt;br&gt;
+document when it is imported (formed by hashing the&lt;br&gt;
+is included.&lt;br&gt;
+content, to overcome file duplication effects caused by&lt;br&gt;
+ &lt;br&gt;All icons in the screenshots of Figures 1â4 are clickable.&lt;br&gt;
+mirroring) and stored as metadata within that document. It&lt;br&gt;
+Those icons at the top of the page return to the home page,&lt;br&gt;
+is important that OIDs persist throughout the index-&lt;br&gt;
+provide help text, and allow you to set user interface and&lt;br&gt;
+building processâso that a userâs search history is&lt;br&gt;
+searching preferences. The navigation bar underneath&lt;br&gt;
+unaffected by rebuilding the collection. OIDs are assigned&lt;br&gt;
+gives access to the searching and browsing facilities,&lt;br&gt;
+by hashing the contents of the original source document.&lt;br&gt;
+which differ from one collection to another.&lt;br&gt;
+ &lt;br&gt;Once imported, each document is stored in its own&lt;br&gt;
+ &lt;br&gt;Each of the five buttons provides a different way to find&lt;br&gt;
+subdirectory of &lt;i&gt;archives&lt;/i&gt;, along with any associated&lt;br&gt;
+information. You can &lt;i&gt;search for particular words&lt;/i&gt; that&lt;br&gt;
+filesâfor example, images. To ensure compatibility with&lt;br&gt;
+appear in the text from the âsearchâ page (or from the&lt;br&gt;
+Windows 3.0, only eight characters are used in directory&lt;br&gt;
+âaboutâ page of Figure 1). This collection contains indexes&lt;br&gt;
+and file names, which causes annoying but essentially&lt;br&gt;
+of chapters, section titles, and entire books. The default&lt;br&gt;
+trivial complications.&lt;br&gt;
+search interface is a simple one, suitable for casual users;&lt;br&gt;advanced searchingâwhich allows full Boolean&lt;br&gt;
+ &lt;br&gt;&lt;b&gt;Inside the documents&lt;/b&gt;&lt;br&gt;
+expressions, phrase searching, case and stemming&lt;br&gt;controlâcan be enabled from the &lt;i&gt;Preferences&lt;/i&gt; page.&lt;br&gt;
+ &lt;br&gt;The GML format imposes a limited amount of structure on&lt;br&gt;
+ &lt;br&gt;
+documents. Documents are divided into paragraphs. They&lt;br&gt;
+This collection has four browsable metadata indexes. You&lt;br&gt;
+can be split hierarchically into sections and subsections.&lt;br&gt;
+can &lt;i&gt;access publications by subject&lt;/i&gt; by clicking the &lt;i&gt;subjects&lt;/i&gt;&lt;br&gt;
+OIDs are extended to identify these components by&lt;br&gt;
+button, which brings up a list of subjects, represented by&lt;br&gt;
+appending numbers, separated by periods, to a documentâs&lt;br&gt;
+bookshelves (Figure 2). You can &lt;i&gt;access publications by&lt;/i&gt;&lt;br&gt;
+OID. When a book is read, its section hierarchy is visible&lt;br&gt;
+&lt;i&gt;title&lt;/i&gt; by clicking &lt;i&gt;titles a-z&lt;/i&gt; (Figure 4), which brings up a list&lt;br&gt;
+as the table of contents (Figure 3). Chapters, sections,&lt;br&gt;
+of books in alphabetic order. You can &lt;i&gt;access publications&lt;/i&gt;&lt;br&gt;
+subsections, and pages are all implemented simply as&lt;br&gt;
+&lt;i&gt;by organization&lt;/i&gt; (i.e. Dublin Core âpublisherâ), bringing up&lt;br&gt;
+âsectionsâ within the document. In some collections&lt;br&gt;
+a list of organizations. You can &lt;i&gt;access publications by&lt;/i&gt;&lt;br&gt;
+documents do not have a hierarchical subsection structure,&lt;br&gt;
+&lt;i&gt;âhow toâ listing&lt;/i&gt;, yielding a list of hints defined by the&lt;br&gt;
+but are split into pages to permit browsing within a&lt;br&gt;
+collectionâs editors. We use the Dublin Core as a base and&lt;br&gt;
+retrieved document.&lt;br&gt;
+extend it in an &lt;i&gt;ad hoc&lt;/i&gt; manner to accommodate the&lt;br&gt;individual requirements of collection designers.&lt;br&gt;
+ &lt;br&gt;The document structure is used for searchable indexes.&lt;br&gt;There are three levels of index: &lt;i&gt;documents&lt;/i&gt;, &lt;i&gt;sections&lt;/i&gt;, and&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">5</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+&lt;IMG src=&quot;_httpdocimg_/pdf01-5_1.jpg&quot;&gt;&lt;br&gt;
+the &lt;i&gt;import&lt;/i&gt; process is invoked, which converts the files into&lt;br&gt;GML using the specified plugins. Old material for which&lt;br&gt;GML files have previously been created is not re-imported.&lt;br&gt;Then the &lt;i&gt;build&lt;/i&gt; process is invoked to build the requisite&lt;br&gt;indexes for the collection. Finally, the contents of the&lt;br&gt;&lt;i&gt;building&lt;/i&gt; directory are moved into the &lt;i&gt;index&lt;/i&gt; directory, and&lt;br&gt;the new version of the collection automatically becomes&lt;br&gt;live.&lt;br&gt;
+ &lt;br&gt;This procedure may seem cumbersome. But all the steps&lt;br&gt;are necessary for efficient operation with large collections.&lt;br&gt;The &lt;i&gt;import&lt;/i&gt; process could be performed on the fly during&lt;br&gt;the building operationâbut because building indexes is a&lt;br&gt;multipass operation, the often lengthy importing would be&lt;br&gt;repeated several times. The &lt;i&gt;build&lt;/i&gt; process can take&lt;br&gt;considerable timeâa day or two, for very large&lt;br&gt;collections. Consequently, the results are placed in the&lt;br&gt;&lt;i&gt;building&lt;/i&gt; directory so that, if the collection already exists, it&lt;br&gt;will continue to be served to users in its old form&lt;br&gt;throughout the building operation.&lt;br&gt;
+ &lt;br&gt;Active users of the collection will not be disturbed when&lt;br&gt;the new version becomes liveâthey will probably not&lt;br&gt;
+&lt;b&gt;Figure 4: Browsing titles in the HDL&lt;/b&gt;&lt;br&gt;
+even notice. The persistent OIDs ensure that interactions&lt;br&gt;remain coherentâusers who are examining the results of a&lt;br&gt;query or browse operation will still retrieve the expected&lt;br&gt;
+&lt;i&gt;paragraphs&lt;/i&gt;, corresponding to the distinctions that GML&lt;br&gt;
+documentsâand if a search is actually in progress when&lt;br&gt;
+makesâthe hierarchical structure is flattened for the&lt;br&gt;
+the change takes place the program detects the resulting&lt;br&gt;
+purposes of creating these indexes. Indexes can be of text,&lt;br&gt;
+file-structure inconsistency and automatically and&lt;br&gt;
+or metadata, or any combination. Thus you can create a&lt;br&gt;
+transparently re-executes the query, this time on the new&lt;br&gt;
+searchable index of section titles, and/or authors, and/or&lt;br&gt;
+version of the collection.&lt;br&gt;
+document descriptions, as well as the document text.&lt;br&gt;
+&lt;b&gt;UPDATING EXISTING COLLECTIONS&lt;/b&gt;&lt;br&gt;
+ &lt;br&gt;&lt;b&gt;How it works&lt;/b&gt;&lt;br&gt;
+ &lt;br&gt;Updating an existing collection with new files in the same&lt;br&gt;
+ &lt;br&gt;The original material in the &lt;i&gt;import&lt;/i&gt; directory may be in any&lt;br&gt;
+format is easy. For example, the raw material for the HDL&lt;br&gt;
+format, and plugins are required to process each format&lt;br&gt;
+is supplied in the form of HTML files marked up with&lt;br&gt;
+type. The plugins that a collection uses must be specified&lt;br&gt;
+&amp;lt;&amp;lt;TOC&amp;gt;&amp;gt; tags to split books into sections and&lt;br&gt;
+in the collection configuration file. The &lt;i&gt;import&lt;/i&gt; program&lt;br&gt;
+subsections, and &amp;lt;&amp;lt;I&amp;gt;&amp;gt; tags to indicate where an image is&lt;br&gt;
+reads the list of plugins and passes each document to each&lt;br&gt;
+to be inserted. For each book in the library there is a&lt;br&gt;
+plugin in order until it finds one that can process it. When&lt;br&gt;
+directory that contains a single HTML file representing the&lt;br&gt;
+updating an existing collection, all plugins necessary to&lt;br&gt;
+book, and separate files containing the associated images.&lt;br&gt;
+process new material should already have been specified in&lt;br&gt;
+An accompanying spreadsheet file contains the&lt;br&gt;
+the configuration file.&lt;br&gt;
+classification hierarchy; this is converted to a simple file&lt;br&gt;format (using Excelâs &lt;i&gt;Save As&lt;/i&gt; command).&lt;br&gt;
+ &lt;br&gt;The building step creates the indexes for both searching&lt;br&gt;and browsing. The MG software is generally used to do the&lt;br&gt;
+ &lt;br&gt;Since the collection exists, its directory is already set up&lt;br&gt;
+searching (Witten  &lt;i&gt;et al.&lt;/i&gt;, 1999), and the &lt;i&gt;mgbuild&lt;/i&gt; module is&lt;br&gt;
+with subdirectories &lt;i&gt;import&lt;/i&gt;, &lt;i&gt;archives&lt;/i&gt;, &lt;i&gt;building&lt;/i&gt;, &lt;i&gt;index&lt;/i&gt;, and&lt;br&gt;
+automatically invoked to create each of the indexes that is&lt;br&gt;
+&lt;i&gt;etc&lt;/i&gt;, and the &lt;i&gt;etc&lt;/i&gt; directory will contain a suitable collection&lt;br&gt;
+required. For example, the Humanity Development Library&lt;br&gt;
+configuration file.&lt;br&gt;
+has three indexes, one for entire books, one for chapters,&lt;br&gt;and one for section titles. Subdirectories of the &lt;i&gt;index&lt;/i&gt;&lt;br&gt;
+ &lt;br&gt;
+directory are created for each of these indexes.&lt;br&gt;
+&lt;b&gt;The updating procedure&lt;/b&gt;&lt;br&gt;
+ &lt;br&gt;To update a collection, the new raw material is placed in&lt;br&gt;the &lt;i&gt;import&lt;/i&gt; directory, in whatever form it is available. Then&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">6</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+creator&lt;br&gt;
+davidb@cs.waikato.ac.nz&lt;br&gt;
+1&lt;br&gt;
+maintainer&lt;br&gt;
+davidb@cs.waikato.ac.nz&lt;br&gt;
+2&lt;br&gt;
+public&lt;br&gt;
+True&lt;br&gt;
+3&lt;br&gt;4&lt;br&gt;
+indexes&lt;br&gt;
+document:text&lt;br&gt;
+5&lt;br&gt;
+defaultindex&lt;br&gt;
+document:text&lt;br&gt;
+6&lt;br&gt;
+plugins&lt;br&gt;
+GMLPlug TEXTPlug ArcPlug RecPlug&lt;br&gt;
+7&lt;br&gt;8&lt;br&gt;
+classify&lt;br&gt;
+AZList metadata=Title&lt;br&gt;
+9&lt;br&gt;10&lt;br&gt;
+collectionmeta&lt;br&gt;
+collectionname    &amp;quot;generic text collection&amp;quot;&lt;br&gt;
+11&lt;br&gt;
+(a)&lt;br&gt;
+collectionmeta&lt;br&gt;
+.document:text    &amp;quot;documents&amp;quot;&lt;br&gt;
+12&lt;br&gt;
+creator&lt;br&gt;
+davidb@cs.waikato.ac.nz&lt;br&gt;
+1&lt;br&gt;
+maintainer&lt;br&gt;
+davidb@cs.waikato.ac.nz&lt;br&gt;
+2&lt;br&gt;
+public&lt;br&gt;
+True&lt;br&gt;
+3&lt;br&gt;4&lt;br&gt;
+indexes&lt;br&gt;
+document:text document:From&lt;br&gt;
+5&lt;br&gt;
+defaultindex&lt;br&gt;
+document:text&lt;br&gt;
+6&lt;br&gt;
+plugins&lt;br&gt;
+GMLPlug EMAILPlug ArcPlug RecPlug&lt;br&gt;
+7&lt;br&gt;8&lt;br&gt;
+classify&lt;br&gt;
+AZList metadata=Title&lt;br&gt;
+9&lt;br&gt;
+classify&lt;br&gt;
+DateList&lt;br&gt;
+10&lt;br&gt;11&lt;br&gt;
+collectionmeta&lt;br&gt;
+collectionname    &amp;quot;Email messages&amp;quot;&lt;br&gt;
+12&lt;br&gt;
+collectionmeta&lt;br&gt;
+.document:text    &amp;quot;documents&amp;quot;&lt;br&gt;
+13&lt;br&gt;
+collectionmeta&lt;br&gt;
+.document:From    &amp;quot;email senders&amp;quot;&lt;br&gt;
+14&lt;br&gt;15&lt;br&gt;
+format&lt;br&gt;
+QueryResults \\\\&lt;br&gt;
+16&lt;br&gt;
+(b)&lt;br&gt;
+&amp;lt;td&amp;gt;[link][icon][/link]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[Title]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[Author]&amp;lt;/td&amp;gt;&lt;br&gt;
+17&lt;br&gt;
+&lt;b&gt;Figure 5: Collection configuration files (a) generic, (b) for an email collection&lt;/b&gt;&lt;br&gt;
+ &lt;br&gt;MG also compresses the text of the collection; and the&lt;br&gt;
+certain circumstances, however, it might be preferable to&lt;br&gt;
+image files are linked into the &lt;i&gt;index&lt;/i&gt; subdirectory. Now&lt;br&gt;
+use a standardized format such as XML. This is&lt;br&gt;
+none of the material in the &lt;i&gt;import&lt;/i&gt; and &lt;i&gt;archives&lt;/i&gt; directories&lt;br&gt;
+straightforward to implementï£§just write an XML&lt;br&gt;
+is needed to run the collection and can be removed from&lt;br&gt;
+pluginï£§although we have not done so ourselves. Given&lt;br&gt;
+the file system (though they would be needed if the&lt;br&gt;
+the transitory nature of the imported data, to date, we have&lt;br&gt;
+collection were rebuilt).&lt;br&gt;
+found GML a satisfactory and beneficial format.&lt;br&gt;
+ &lt;br&gt;Associated with each collection is a database stored in&lt;br&gt;
+&lt;b&gt;CREATING NEW COLLECTIONS&lt;/b&gt;&lt;br&gt;
+GDBM (Gnu database manager) format. This contains an&lt;br&gt;entry for each document, giving its OID, its internal MG&lt;br&gt;
+ &lt;br&gt;Building new collections from scratch is only slightly&lt;br&gt;
+document number, and metadata such as title. Information&lt;br&gt;
+different from updating an existing collection. The key&lt;br&gt;
+for each of the browsing indexes, which appear as buttons&lt;br&gt;
+new requirement is creating a collection configuration file,&lt;br&gt;
+on the Greenstone search/browse bar, is also extracted&lt;br&gt;
+and a software utility is provided to help. Two pieces of&lt;br&gt;
+during the building process and stored in the database. A&lt;br&gt;
+information are required for this: the name of the directory&lt;br&gt;
+âclassifierâ program is required for each browsing index to&lt;br&gt;
+that the collection will use (into which the source data and&lt;br&gt;
+extract the appropriate information from GML documents.&lt;br&gt;
+other files will eventually be placed), and a contact e-mail&lt;br&gt;
+Like plugins, classifiers are written on an &lt;i&gt;ad hoc&lt;/i&gt; basis for&lt;br&gt;
+address for use if any problems are encountered by the&lt;br&gt;
+the particular information required, and where possible&lt;br&gt;
+software once the collection is up and running. The utility&lt;br&gt;
+reused from one collection to another.&lt;br&gt;
+creates files and directories within the newly-named&lt;br&gt;
+ &lt;br&gt;
+directory to support a generic collection of plain text&lt;br&gt;
+The building program creates the indexes based on&lt;br&gt;
+documents. With suitable data placed in the &lt;i&gt;import&lt;/i&gt;&lt;br&gt;
+whatever appears in the &lt;i&gt;archives&lt;/i&gt; directory. The first plugin&lt;br&gt;
+directory, building the collection at this point will yield a&lt;br&gt;
+specified by all collections is one that processes GML&lt;br&gt;
+document-level searchable index of all the text and a&lt;br&gt;
+files, and so if &lt;i&gt;archives&lt;/i&gt; contains imported files they will be&lt;br&gt;
+browsable list of âtitlesâ (defined in this case to be the&lt;br&gt;
+processed correctly. If it contains material in the original&lt;br&gt;
+document filenames).&lt;br&gt;
+format, that will be converted using the appropriate plugin.&lt;br&gt;Thus the import process is optional.&lt;br&gt;
+ &lt;br&gt;To enhance the functionality and presentationâ something&lt;br&gt;
+ &lt;br&gt;
+anything but the most trivial collection will requireâthe&lt;br&gt;
+GML is designed to be fast and easy to parse, an important&lt;br&gt;
+configuration file must be edited. For a collection sourced&lt;br&gt;
+requirement when millions of documents are to be&lt;br&gt;
+from documents in an already supported data format,&lt;br&gt;
+processed. Something as simple as requiring tags to be&lt;br&gt;
+presented in a similar fashion to an existing collection, the&lt;br&gt;
+lower-case, for example, yields a substantial speed-up. In&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">7</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+&lt;IMG src=&quot;_httpdocimg_/pdf01-7_1.jpg&quot;&gt;&lt;br&gt;
+ &lt;br&gt;These are modules of code that can be slotted into the&lt;br&gt;system to enhance its capabilities. Plugins parse&lt;br&gt;documents, extracting the text and metadata to be indexed.&lt;br&gt;Classifiers control how metadata is brought together to&lt;br&gt;form browsable data structures. Both are specified in an&lt;br&gt;object-oriented framework using inheritance to minimize&lt;br&gt;the amount of code written.&lt;br&gt;
+ &lt;br&gt;A plugin must specify three things: what file formats it can&lt;br&gt;handle, how they should be parsed, and whether the plugin&lt;br&gt;is recursive. File formats are normally determined using&lt;br&gt;regular expression matching on the filename. For example,&lt;br&gt;the HTML plugin accepts all files that end in &lt;i&gt;.htm&lt;/i&gt;, . &lt;i&gt;html&lt;/i&gt;,&lt;br&gt;&lt;i&gt;.HTM&lt;/i&gt;, or &lt;i&gt;.HTML&lt;/i&gt;. (It is quite possible, however, to write&lt;br&gt;plugins that âlook insideâ the file as well.) For other files,&lt;br&gt;the plugin returns &lt;i&gt;undefined&lt;/i&gt; and the file is passed to the&lt;br&gt;next plugin in the collectionâs configuration file (e.g.&lt;br&gt;Figure 5 line 7). If it can, the plugin parses the file and&lt;br&gt;returns the number of documents processed. This involves&lt;br&gt;extracting text and metadata and adding it to the libraryâs&lt;br&gt;content through calls to &lt;i&gt;add text&lt;/i&gt; and &lt;i&gt;add metadata&lt;/i&gt;.&lt;br&gt;
+ &lt;br&gt;Some plugins (ârecursiveâ ones) add extra files into the&lt;br&gt;
+&lt;b&gt;Figure 6: Searching bookmarked Web pages&lt;/b&gt;&lt;br&gt;
+stream of data processed during the building phase by&lt;br&gt;artificially reactivating the list of plugins. This is how&lt;br&gt;directory hierarchies are traversed.&lt;br&gt;
+amount of editing is minimal. Importing new data formats&lt;br&gt;and browsing metadata in ways not currently supported are&lt;br&gt;
+ &lt;br&gt;Plugins are small modules of code that are easy to write.&lt;br&gt;
+more complex activities that require programming skills.&lt;br&gt;
+We monitored the time it took to develop a new one that&lt;br&gt;was different to any we had produced so far. We chose to&lt;br&gt;make as an example a collection of HTML bookmark files,&lt;br&gt;
+ &lt;br&gt;&lt;b&gt;Modifying the configuration file&lt;/b&gt;&lt;br&gt;
+the motivation being to produce a convenient way of&lt;br&gt;
+ &lt;br&gt;
+searching and browsing oneâs bookmarked Web pages.&lt;br&gt;
+Figure 5b shows simple alterations to the generic&lt;br&gt;
+Figure 6 shows a user searching for bookmarked pages&lt;br&gt;
+configuration file in Figure 5a that was generated by the&lt;br&gt;
+about &lt;i&gt;music&lt;/i&gt;. The new plugin took under an hour to write,&lt;br&gt;
+new-collection utility. &lt;i&gt;TEXTPlug&lt;/i&gt; is replaced with&lt;br&gt;
+and was 160 lines long (ignoring blank lines and&lt;br&gt;
+&lt;i&gt;EMAILPlug&lt;/i&gt; (line 7) which reads email files and extracts&lt;br&gt;
+comments)âabout the average length of existing plugins.&lt;br&gt;
+metadata (&lt;i&gt;From&lt;/i&gt;, &lt;i&gt;To&lt;/i&gt;, &lt;i&gt;Date&lt;/i&gt;, &lt;i&gt;Subject&lt;/i&gt;) from them. A classifier&lt;br&gt;for dates is added (line 10) to make the collection&lt;br&gt;
+ &lt;br&gt;Classifiers are more general than plugins because they&lt;br&gt;
+browsable chronologically. The default presentation of&lt;br&gt;
+work on GML-format data. For example, any plugin that&lt;br&gt;
+search results is overridden (line 17) to display both the&lt;br&gt;
+generates date metadata in accordance with the Dublin&lt;br&gt;
+title of the message (i.e. Dublin Core &lt;i&gt;Title&lt;/i&gt;) and its sender&lt;br&gt;
+core can request the collection to be browsable&lt;br&gt;
+(i.e. Dublin Core &lt;i&gt;Author&lt;/i&gt;). Elements in square brackets,&lt;br&gt;
+chronologically by specifying the &lt;i&gt;DateList&lt;/i&gt; classifier in the&lt;br&gt;
+such as &lt;i&gt;[Title]&lt;/i&gt;, are replaced by the metadata associated&lt;br&gt;
+collectionâs configuration file (Figure 7). Classifiers are&lt;br&gt;
+with a particular document. The built-in term &lt;i&gt;[icon]&lt;/i&gt;&lt;br&gt;
+more elaborate than most plugins, but new ones are seldom&lt;br&gt;
+produces a suitable image that represents the document&lt;br&gt;
+required. The average length of existing classifiers is 230&lt;br&gt;
+(such as a book icon or page icon), and the &lt;i&gt;[link]âŠ[/link]&lt;/i&gt;&lt;br&gt;
+lines.&lt;br&gt;
+construct forms a hyperlink to the complete document.&lt;br&gt;
+ &lt;br&gt;
+Anything else in the format statement, which in this case is&lt;br&gt;
+Classifiers must specify three things: an initialization&lt;br&gt;
+solely table-cell tags in HTML, is passed through to the&lt;br&gt;
+routine, how individual documents are classified, and the&lt;br&gt;
+page being displayed.&lt;br&gt;
+final browsable data structure. Initialization takes care of&lt;br&gt;any options specified in the configuration file (such as&lt;br&gt;
+As this example shows, creating a new collection that stays&lt;br&gt;
+&lt;i&gt;metadata=Title &lt;/i&gt;on line 9 of Figure 5b). Classifying&lt;br&gt;
+within the bounds of the libraryâs established capabilities&lt;br&gt;
+individual documents is an iterative process: for each one,&lt;br&gt;
+falls within the capability of many computer usersâfor&lt;br&gt;
+a call to &lt;i&gt;document-classify&lt;/i&gt; is made. On presentation of the&lt;br&gt;
+instance, computer-trained librarians. Extending&lt;br&gt;
+documentâs OID, the necessary metadata is located and&lt;br&gt;
+Greenstone to handle new document formats and browse&lt;br&gt;
+used to control where the document is added to the&lt;br&gt;
+metadata in new ways is more challenging.&lt;br&gt;
+browsable data structure being constructed.&lt;br&gt;
+ &lt;br&gt;Once all documents have been added, a request is made for&lt;br&gt;
+ &lt;br&gt;&lt;b&gt;Writing new plugins and classifiers&lt;/b&gt;&lt;br&gt;
+the completed data structure. Some classifiers return the&lt;br&gt;data structure directly; others transform the data structure&lt;br&gt;
+ &lt;br&gt;Extensibility  is  obtained through  plugins  and  classifiers.&lt;br&gt;
+before it is returned. For example, the &lt;i&gt;AZList&lt;/i&gt; classifier&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">8</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+&lt;IMG src=&quot;_httpdocimg_/pdf01-8_1.jpg&quot;&gt;&lt;br&gt;
+a page number, next and previous page buttons, and&lt;br&gt;displaying a particular page at different resolutions. A text&lt;br&gt;version of the page is also available upon which a&lt;br&gt;searching option is also provided.&lt;br&gt;
+Started in 1994, Harvest is also a long-running research&lt;br&gt;project. It provides an efficient means of gathering source&lt;br&gt;data from the Internet and distributing indexing&lt;br&gt;information over the Internet. This is accomplished&lt;br&gt;through five components: &lt;i&gt;gatherer&lt;/i&gt;, &lt;i&gt;broker&lt;/i&gt;, &lt;i&gt;indexer&lt;/i&gt;,&lt;br&gt;&lt;i&gt;replicator&lt;/i&gt; and &lt;i&gt;cache&lt;/i&gt;. The first three are central to creating,&lt;br&gt;updating and searching a collection; the last two help to&lt;br&gt;improve performance over the Internet through transparent&lt;br&gt;mirroring and caching techniques.&lt;br&gt;
+The system is configurable and customizable. While&lt;br&gt;searching is most commonly implemented using Glimpse&lt;br&gt;(&lt;i&gt;glimpse.cs.arizona.edu&lt;/i&gt;), in principle any search engine&lt;br&gt;that supports incremental updates and Boolean&lt;br&gt;combinations of attribute-based queries can be used. It is&lt;br&gt;possible to control what type of documents are gathered&lt;br&gt;during creation and updating, and how the query interface&lt;br&gt;
+&lt;b&gt;Figure 7: Browsing a newspaper collection by date&lt;/b&gt;&lt;br&gt;
+looks and is laid out.&lt;br&gt;
+Sample collections cited by the developers include 21,000&lt;br&gt;
+divides the alphabetically sorted list of metadata into&lt;br&gt;
+computer science technical reports and 7,000 home pages.&lt;br&gt;
+separate pages of about the same size and returns the&lt;br&gt;
+Other examples include a sizable collection of agriculture-&lt;br&gt;
+alphabetic ranges for each one (Figure 4).&lt;br&gt;
+related electronic journals and magazines called âtomato-&lt;br&gt;juiceâ (accessed through &lt;i&gt;hegel.lib.ncsu.edu&lt;/i&gt;) and a full-text&lt;br&gt;
+&lt;b&gt;OVERVIEW OF RELATED WORK&lt;/b&gt;&lt;br&gt;
+index of library-related electronic serials&lt;br&gt;
+Two projects that provide substantial open source digital&lt;br&gt;
+(&lt;i&gt;sunsite.berkeley.edu/IndexMorganagus&lt;/i&gt;). Harvest is also&lt;br&gt;
+library software are Dienst (Lagoze and Fielding, 1998)&lt;br&gt;
+often used to index Web sites (for example&lt;br&gt;
+and Harvest (Bowman &lt;i&gt;et al.&lt;/i&gt;, 1994). The origins of Dienst&lt;br&gt;
+&lt;i&gt;www.middlebury.edu&lt;/i&gt;).&lt;br&gt;
+(&lt;i&gt;www.cs.cornell.edu/cdlrg&lt;/i&gt;) stretch back to 1992. The term&lt;br&gt;
+Comparing Greenstone with Dienst and Harvest, there are&lt;br&gt;
+has come to represent three entities: a conceptual&lt;br&gt;
+both similarities and differences. All provide substantial&lt;br&gt;
+architecture for distributed digital libraries; an open&lt;br&gt;
+digital library systems, hence common themes recur, but&lt;br&gt;
+protocol for service communication; and a software&lt;br&gt;
+they are driven by projects with different aims. Harvest,&lt;br&gt;
+system that implements the protocol. To date, five sample&lt;br&gt;
+for instance, was not conceived as a digital library project&lt;br&gt;
+digital libraries have been built using this technology.&lt;br&gt;
+at all, but by virtue of its selective document gathering&lt;br&gt;
+They manifest themselves in two forms: technical reports&lt;br&gt;
+process it can be classed (and is used) as one. While it&lt;br&gt;
+and primary source documents.&lt;br&gt;
+provides sophisticated search options, it lacks the&lt;br&gt;
+Best known is NCSTRL, the Networked Computer&lt;br&gt;
+complementary service of browsing. Furthermore it adds&lt;br&gt;
+Science Technical Reference Library project&lt;br&gt;
+no structure or order to the documents collected, relying&lt;br&gt;
+(&lt;i&gt;www.ncstrl.org&lt;/i&gt;). This collection facilitates searching by&lt;br&gt;
+on whatever structures are present in the site that they&lt;br&gt;
+title, author and abstract, and browsing by year and author,&lt;br&gt;
+were gathered from. A proven strength of the design is its&lt;br&gt;
+across a distributed network of document repositories.&lt;br&gt;
+flexibility through configuration and customizationï£§an&lt;br&gt;
+Documents can (where supported) be delivered in various&lt;br&gt;
+element also present in Greenstone.&lt;br&gt;
+formats such as PostScript, a thumbnail overview of the&lt;br&gt;
+Dienstï£§best exemplified through the NCSTRL&lt;br&gt;
+pages, and a GIF image of a particular page.&lt;br&gt;
+workï£§supports searching and browsing, like Greenstone.&lt;br&gt;
+The &lt;i&gt;Making of America&lt;/i&gt; resource is an example of a&lt;br&gt;
+Both use open protocols. Differences include a high&lt;br&gt;
+collection based around primary sourcesï£§in this case&lt;br&gt;
+reliance in Dienst on user-supplied information when a&lt;br&gt;
+American social history, 1830â1900. It has a different&lt;br&gt;
+document is added, and a smaller range of document types&lt;br&gt;
+âlook and feelâ to NCSTRL, being strongly oriented&lt;br&gt;
+supportedâalthough Dienst does include a document&lt;br&gt;
+toward browsing rather than searching. A user navigates&lt;br&gt;
+model that should, over time, allow this to expand with&lt;br&gt;
+their way through a hierarchical structure of hyperlinks to&lt;br&gt;
+relative ease.&lt;br&gt;
+reach a book of interest. The book itself is a series of&lt;br&gt;
+There are also commercial systems that provide similar&lt;br&gt;
+scanned images: delivery options include going directly to&lt;br&gt;
+digital library services to those described. However, since&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">9</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+corporate culture instills proprietary attitudes there is little&lt;br&gt;
+&lt;b&gt;REFERENCES&lt;/b&gt;&lt;br&gt;
+opportunity for advancement through a shared&lt;br&gt;
+1.  Akscyn, R.M. and Witten, I.H. (1998) âReport on First&lt;br&gt;
+collaborative effort. Consequently they are not reviewed&lt;br&gt;
+Summit on International Cooperation on Digital&lt;br&gt;
+here.&lt;br&gt;
+Libraries.â ks.com/idla-wp-oct98.&lt;br&gt;
+2.  Bowman, C.M., Danzig, P.B., Manber, U., and&lt;br&gt;
+&lt;b&gt;CONCLUSIONS&lt;/b&gt;&lt;br&gt;
+Schwartz, M.F. âScalable Internet resource discovery:&lt;br&gt;
+Greenstone is a comprehensive software system for&lt;br&gt;
+Research problems and approachesâ &lt;i&gt;Communications&lt;/i&gt;&lt;br&gt;
+creating digital library collections. It builds data structures&lt;br&gt;
+&lt;i&gt;of the ACM,&lt;/i&gt; Vol. 37, No. 8, pp. 98â107, 1994.&lt;br&gt;
+for searching and browsing from the material provided,&lt;br&gt;
+3.  Fox, E. (1998) âDigital library definitions.â&lt;br&gt;
+rather than relying on any hand-crafting. The process is&lt;br&gt;
+ei.cs.vt.edu/~fox/dlib/def.html.&lt;br&gt;
+controlled by a configuration file, and once a collection&lt;br&gt;exists new material can be added completely&lt;br&gt;
+4.  Humanity Libraries (1998) &lt;i&gt;Humanity Development&lt;/i&gt;&lt;br&gt;
+automatically. Browsing is based on Dublin Core&lt;br&gt;
+&lt;i&gt;Library&lt;/i&gt;. CD-ROM produced by the Global Help&lt;br&gt;
+metadata.&lt;br&gt;
+Project, Antwerp, Belgium.&lt;br&gt;
+New collections can be developed easily, particularly if&lt;br&gt;
+5.  Lagoze, C. and Fielding, D âDefining Collections in&lt;br&gt;
+they resemble existing ones. Extensibility is achieved&lt;br&gt;
+Distributed Digital Librariesâ &lt;i&gt;D-Lib Magazine&lt;/i&gt;, Nov.&lt;br&gt;
+through software âpluginsâ that can be written to&lt;br&gt;
+1998.&lt;br&gt;
+accommodate documents, and metadata, in different&lt;br&gt;
+6.  PAHO (1999) &lt;i&gt;Virtual Disaster Library&lt;/i&gt;. CD-ROM&lt;br&gt;
+formats. Standard plugins exist for many document types;&lt;br&gt;
+produced by the Pan-American Health Organization,&lt;br&gt;
+new ones are easily written. Browsing is controlled by&lt;br&gt;
+Washington DC, USA.&lt;br&gt;
+âclassifiersâ that process metadata into browsing structures&lt;br&gt;
+7.  McNab, R.J., Witten, I.H. and Boddie, S.J. (1998) âA&lt;br&gt;
+(by date, alphabetical, hierarchical, etc).&lt;br&gt;
+distributed digital library architecture incorporating&lt;br&gt;
+However, the most powerful support for extensibility is&lt;br&gt;
+different index styles.â &lt;i&gt;Proc IEEE Advances in Digital&lt;/i&gt;&lt;br&gt;
+achieved not by technical means but by making the source&lt;br&gt;
+&lt;i&gt;Libraries&lt;/i&gt;, Santa Barbara, CA, pp. 36â45.&lt;br&gt;
+code freely available under the Gnu public license. Only&lt;br&gt;
+8.  Nevill-Manning, C.G., Reed, T., and Witten, I.H.&lt;br&gt;
+through an international cooperative effort will digital&lt;br&gt;
+(1998) âExtracting text from PostScriptâ&lt;br&gt;
+library software become sufficiently comprehensive to&lt;br&gt;
+&lt;i&gt;SoftwareâPractice and Experience&lt;/i&gt;, Vol. 28, No. 5, pp.&lt;br&gt;
+meet the worldâs needs with the richness and flexibility&lt;br&gt;
+481â491; April.&lt;br&gt;
+that users deserve.&lt;br&gt;
+9.  UNESCO (1999) &lt;i&gt;SAHEL point DOC: Anthologie du&lt;/i&gt;&lt;br&gt;
+&lt;b&gt;ACKNOWLEDGMENTS&lt;/b&gt;&lt;br&gt;
+&lt;i&gt;dÃ©veloppement au Sahel&lt;/i&gt;. CD-ROM produced by&lt;br&gt;UNESCO, Paris, France.&lt;br&gt;
+We gratefully acknowledge all those who have worked on&lt;br&gt;the Greenstone software, and all members of the New&lt;br&gt;
+10. UNU (1998) &lt;i&gt;Collection on critical global issues.&lt;/i&gt; CD-&lt;br&gt;
+Zealand Digital Library project for their enthusiasm and&lt;br&gt;
+ROM produced by the United Nations University&lt;br&gt;
+ideas.&lt;br&gt;
+Press, Tokyo, Japan.&lt;br&gt;
+11. Witten, I.H., Moffat, A. and Bell, T. (1999) &lt;i&gt;Managing&lt;/i&gt;&lt;br&gt;
+&lt;i&gt;Gigabytes: compressing and indexing documents and&lt;br&gt;images&lt;/i&gt;, Morgan Kaufmann, second edition.&lt;br&gt;
+&lt;hr&gt;
+
+
+</Content>
+</Section>
+</Section>
+</Archive>
Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Enhanced-PDF/archives/HASHbb6e.dir/doc.xml
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Enhanced-PDF/archives/HASHbb6e.dir/doc.xml	(revision 37429)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Enhanced-PDF/archives/HASHbb6e.dir/doc.xml	(revision 37429)
@@ -0,0 +1,804 @@
+<?xml version="1.0" encoding="utf-8" standalone="no"?>
+<!DOCTYPE Archive SYSTEM "http://greenstone.org/dtd/Archive/1.0/Archive.dtd">
+<Archive>
+<Section>
+  <Description>
+    <Metadata name="gsdldoctype">indexed_doc</Metadata>
+    <Metadata name="Language">en</Metadata>
+    <Metadata name="Encoding">utf8</Metadata>
+    <Metadata name="URL">http://Scratch/ak19/gs2-diffcol-26Jul2021/collect/Enhanced-PDF/tmp/1678158429_3/pdf06-weirdchars.html</Metadata>
+    <Metadata name="UTF8URL">http://Scratch/ak19/gs2-diffcol-26Jul2021/collect/Enhanced-PDF/tmp/1678158429_3/pdf06-weirdchars.html</Metadata>
+    <Metadata name="Title">!&amp;quot; # $ % %...</Metadata>
+    <Metadata name="gsdlsourcefilename">import/notext/pdf06-weirdchars.pdf</Metadata>
+    <Metadata name="gsdlsourcefilerenamemethod">url</Metadata>
+    <Metadata name="gsdlconvertedfilename">tmp/1678158429_3/pdf06-weirdchars.html</Metadata>
+    <Metadata name="OrigSource">pdf06-weirdchars.html</Metadata>
+    <Metadata name="Source">pdf06-weirdchars.pdf</Metadata>
+    <Metadata name="SourceFile">pdf06-weirdchars.pdf</Metadata>
+    <Metadata name="Plugin">PDFv1Plugin</Metadata>
+    <Metadata name="FileSize">846134</Metadata>
+    <Metadata name="FilenameRoot">pdf06-weirdchars</Metadata>
+    <Metadata name="FileFormat">PDF</Metadata>
+    <Metadata name="srcicon">_iconpdf_</Metadata>
+    <Metadata name="srclink_file">doc.pdf</Metadata>
+    <Metadata name="srclinkFile">doc.pdf</Metadata>
+    <Metadata name="NumPages">12</Metadata>
+    <Metadata name="gsdlthistype">Paged</Metadata>
+    <Metadata name="ex.ExifTool.ExifToolVersion">12.19</Metadata>
+    <Metadata name="ex.File.Directory">/Scratch/ak19/gs2-diffcol-26Jul2021/collect/Enhanced-PDF/import/notext</Metadata>
+    <Metadata name="ex.File.FileAccessDate">2023:03:07 16:07:09+13:00</Metadata>
+    <Metadata name="ex.File.FileInodeChangeDate">2023:03:07 16:07:07+13:00</Metadata>
+    <Metadata name="ex.File.FileModifyDate">2023:03:07 16:07:07+13:00</Metadata>
+    <Metadata name="ex.File.FileName">pdf06-weirdchars.pdf</Metadata>
+    <Metadata name="ex.File.FilePermissions">100664</Metadata>
+    <Metadata name="ex.File.FileSize">846134</Metadata>
+    <Metadata name="ex.File.FileType">PDF</Metadata>
+    <Metadata name="ex.File.FileTypeExtension">PDF</Metadata>
+    <Metadata name="ex.File.MIMEType">application/pdf</Metadata>
+    <Metadata name="ex.PDF.Author">rg</Metadata>
+    <Metadata name="ex.PDF.CreateDate">10/7/2002 16:9:30</Metadata>
+    <Metadata name="ex.PDF.Creator">Pscript.dll Version 5.0</Metadata>
+    <Metadata name="ex.PDF.Linearized">false</Metadata>
+    <Metadata name="ex.PDF.PDFVersion">1.2</Metadata>
+    <Metadata name="ex.PDF.PageCount">12</Metadata>
+    <Metadata name="ex.PDF.Producer">AFPL Ghostscript 7.04</Metadata>
+    <Metadata name="ex.PDF.Title">metsreportfinal.doc</Metadata>
+    <Metadata name="Identifier">HASHbb6e0c8f087c9c5b2e301a</Metadata>
+    <Metadata name="lastmodified">1678158427</Metadata>
+    <Metadata name="lastmodifieddate">20230307</Metadata>
+    <Metadata name="oailastmodified">1678158430</Metadata>
+    <Metadata name="oailastmodifieddate">20230307</Metadata>
+    <Metadata name="assocfilepath">HASHbb6e.dir</Metadata>
+    <Metadata name="gsdlassocfile">doc.pdf:application/pdf:</Metadata>
+  </Description>
+  <Content>
+
+ 
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+</Content>
+<Section>
+  <Description>
+    <Metadata name="Title">1</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+ &lt;br&gt;
+!&amp;quot;&lt;br&gt;
+# $&lt;br&gt;
+% &lt;br&gt;
+%&lt;br&gt;
+$&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">2</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+&lt;b&gt;Â© JISC 2002&lt;/b&gt;&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">3</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+! &amp;amp; $&lt;br&gt;
+&amp;amp;&lt;br&gt;
+%&lt;br&gt;
+ &lt;br&gt;
+!&lt;br&gt;
+&amp;quot;# $&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+'&lt;br&gt;
+(&lt;br&gt;
+ &lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+)&lt;br&gt;
+*&lt;br&gt;
++&lt;br&gt;
+&amp;quot;# $ # % &amp;amp;&lt;br&gt;
+,&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+,&lt;br&gt;
+&amp;quot;# $&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+-&lt;br&gt;
+.&lt;br&gt;
+)&lt;br&gt;
+&amp;quot;# $&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+&amp;quot;# $,&lt;br&gt;
+)&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+&amp;quot;# $&lt;br&gt;
+# % &amp;amp;  &lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+/&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+) %&lt;br&gt;
+#&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+$&lt;br&gt;
+0&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+#&lt;br&gt;
+1&lt;br&gt;
+1&lt;br&gt;
+&amp;quot;# $1&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">4</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+'&lt;br&gt;
+&amp;amp;&lt;br&gt;
+/&lt;br&gt;
+)&lt;br&gt;
+2&lt;br&gt;
+2&lt;br&gt;
+)&lt;br&gt;
+3&lt;br&gt;
+4&lt;br&gt;
+/&lt;br&gt;
+0&lt;br&gt;
+5&lt;br&gt;
+56&lt;br&gt;
+4&lt;br&gt;
+4&lt;br&gt;
+)&lt;br&gt;
+ &lt;br&gt;
+7&lt;br&gt;
+,&lt;br&gt;
+0%/) &amp;amp;&lt;br&gt;
+8&lt;br&gt;
+)&lt;br&gt;
+ &lt;br&gt;
+89&lt;br&gt;
+# ) 0&lt;br&gt;
+# ) 0,&lt;br&gt;
+:&lt;br&gt;
+2&lt;br&gt;
+,&lt;br&gt;
+# ) 0&lt;br&gt;
+2&lt;br&gt;
+(&lt;br&gt;
+) )&lt;br&gt;
+%&lt;br&gt;
+&amp;quot;&lt;br&gt;
+&amp;amp;&lt;br&gt;
+3 # $&lt;br&gt;
+;&lt;br&gt;
+2&lt;br&gt;
+)&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+/&lt;br&gt;
+$&lt;br&gt;
+&amp;lt;&lt;br&gt;
+6&lt;br&gt;
+,&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">5</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+2&lt;br&gt;
+ &lt;br&gt;
+# ) 0&lt;br&gt;
+,&lt;br&gt;
+=&lt;br&gt;
+,&lt;br&gt;
+2&lt;br&gt;
+ &lt;br&gt;
+2&lt;br&gt;
+'&lt;br&gt;
+2&lt;br&gt;
+# ) 0&lt;br&gt;
+(&lt;br&gt;
+'&lt;br&gt;
+2&lt;br&gt;
+(&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+,&lt;br&gt;
+2&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+'&lt;br&gt;
+(&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+/&lt;br&gt;
+$&lt;br&gt;
+&amp;lt;&lt;br&gt;
+)&lt;br&gt;
+'&lt;br&gt;
+(&lt;br&gt;
+'&lt;br&gt;
+(&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+&amp;quot;# $&lt;br&gt;
+&amp;quot;# $&lt;br&gt;
+&amp;gt;&lt;br&gt;
+)&amp;amp;0  &lt;br&gt;
+;&lt;br&gt;
+&amp;quot;# $&lt;br&gt;
+/ /&lt;br&gt;
+&amp;quot;#$&lt;br&gt;
+'&lt;br&gt;
+(!&lt;br&gt;
+&amp;quot;#$&lt;br&gt;
+&amp;quot;# $&lt;br&gt;
+&amp;quot;# $&lt;br&gt;
+ &lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+) # % &amp;amp;&lt;br&gt;
+,&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+'&lt;br&gt;
+(&lt;br&gt;
+&amp;lt;&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">6</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+)&lt;br&gt;
+,&lt;br&gt;
+&amp;lt;structMap TYPE=&amp;quot;PHYSICAL&amp;quot;&amp;gt;&lt;br&gt;
+&amp;lt;div ID=&amp;quot;title1.div.1&amp;quot;&lt;br&gt;
+LABEL=&amp;quot;Chapter 1&amp;quot;&amp;gt;&lt;br&gt;
+&amp;lt;div ID=&amp;quot;title.1.div.1.1&amp;quot; LABEL=&amp;quot;Section 1&amp;quot;&amp;gt;&lt;br&gt;
+&amp;lt;fptr FILEID=&amp;quot;title1.image.1&amp;quot;/&amp;gt;&lt;br&gt;
+&amp;lt;fptr FILEID=&amp;quot;title1.image.2&amp;quot;/&amp;gt;&lt;br&gt;
+&amp;lt;/div&amp;gt;&lt;br&gt;
+&amp;lt;div ID=&amp;quot;title.1.div.1.2&amp;quot; LABEL=&amp;quot;Section 2&amp;quot;&amp;gt;&lt;br&gt;
+&amp;lt;fptr FILEID=&amp;quot;title1.image.3&amp;quot;/&amp;gt;&lt;br&gt;
+&amp;lt;/div&amp;gt;&lt;br&gt;
+&amp;lt;/div&amp;gt;&lt;br&gt;
+&amp;lt;div ID=&amp;quot;title1.div.2&amp;quot;&lt;br&gt;
+LABEL=&amp;quot;Chapter 2&amp;quot;&amp;gt;&lt;br&gt;
+[Contents of Chapter 2 omitted]&lt;br&gt;
+&amp;lt;/div&amp;gt;&lt;br&gt;
+&amp;lt;/structMap&amp;gt;&lt;br&gt;
+!&lt;br&gt;
+&amp;lt; $% /&lt;br&gt;
+?&lt;br&gt;
+@'&lt;br&gt;
+(&lt;br&gt;
+&amp;quot;# $,&lt;br&gt;
+ &lt;br&gt;
+&amp;quot;&amp;amp;$ '&lt;br&gt;
+&amp;quot;# $&lt;br&gt;
+(&lt;br&gt;
+%&lt;br&gt;
+,&lt;br&gt;
+&amp;lt;file ID=&amp;quot;FILE003&amp;quot; MIMETYPE=&amp;quot;image/jpeg&amp;quot;&amp;gt;&lt;br&gt;
+&amp;lt;Flocat LOCTYPE=&amp;quot;URL&amp;quot;&amp;gt;&lt;br&gt;
+http://dlib.nyu.edu/tamwag/beame.jpg&lt;br&gt;
+&amp;lt;/FLocat&amp;gt;&lt;br&gt;
+&amp;lt;/file&amp;gt;&lt;br&gt;
+; $&lt;br&gt;
+&amp;lt;Flocat&amp;gt;&lt;br&gt;
+element, while its ID, by which it is referenced from the structural map, is declared by the ID attribute of the&lt;br&gt;&amp;lt;file&amp;gt; element itself. Different manifestations of the same image, sound file or other digital file (for&lt;br&gt;instance, thumbnails, archival copies, or delivery versions in the case of still images) may be grouped&lt;br&gt;together in surrounding &amp;lt;fileGrp&amp;gt; elements, and so referenced together if necessary.&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">7</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+/&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+&amp;lt;dmdSec&amp;gt; %&lt;br&gt;
+&amp;lt;dmdSec&amp;gt; is labelled with a unique ID to allow it to be referenced from within&lt;br&gt;
+the structural map. # % &amp;amp;&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+ &lt;br&gt;
+?&lt;br&gt;
+@&lt;br&gt;
+%)/&lt;br&gt;
+&amp;lt;dmdSec ID=&amp;quot;dmd001&amp;quot;&amp;gt;&lt;br&gt;
+&amp;lt;mdRef LOCTYPE=&amp;quot;URN&amp;quot; MIMETYPE=&amp;quot;application/xml&amp;quot; MDTYPE=&amp;quot;EAD&amp;quot;&lt;br&gt;
+LABEL=&amp;quot;Berol Collection Finding Aid&amp;quot;&amp;gt;urn:x-nyu:fales1735&amp;lt;/mdRef&amp;gt;&lt;br&gt;
+&amp;lt;/dmdSec&amp;gt;&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+&amp;lt;mdWrap&amp;gt;&lt;br&gt;
+&amp;lt;dmdSec ID=&amp;quot;dmd002&amp;quot;&amp;gt;&lt;br&gt;
+&amp;lt;mdWrap MIMETYPE=&amp;quot;text/xml&amp;quot; MDTYPE=&amp;quot;DC&amp;quot; LABEL=&amp;quot;Dublin&lt;br&gt;
+Core&lt;br&gt;
+Metadata&amp;quot;&amp;gt;&lt;br&gt;
+&amp;lt;dc:title&amp;gt;Alice's Adventures&lt;br&gt;
+in Wonderland&amp;lt;/dc:title&amp;gt;&lt;br&gt;
+&amp;lt;dc:creator&amp;gt;Lewis Carroll&amp;lt;/dc:creator&amp;gt;&lt;br&gt;
+&amp;lt;dc:date&amp;gt;between 1872 and&lt;br&gt;
+1890&amp;lt;/dc:date&amp;gt;&lt;br&gt;
+&amp;lt;dc:publisher&amp;gt;McCloughlin&lt;br&gt;
+Brothers&amp;lt;/dc:publisher&amp;gt;&lt;br&gt;
+&amp;lt;dc:type&amp;gt;text&amp;lt;/dc:type&amp;gt;&lt;br&gt;
+&amp;lt;/mdWrap&amp;gt;&lt;br&gt;
+&amp;lt;/dmdSec&amp;gt;&lt;br&gt;
+/&lt;br&gt;
+0&lt;br&gt;
+ &lt;br&gt;
+?&lt;br&gt;
+!&lt;br&gt;
+@&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+&amp;quot;# $&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+0&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+# ) 0&lt;br&gt;
+)&lt;br&gt;
+&amp;lt;amdSec&amp;gt;&lt;br&gt;
+ /&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+&amp;lt;mdWrap&amp;gt;&lt;br&gt;
+)&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+A &amp;amp;4&lt;br&gt;
+#&lt;br&gt;
+/&lt;br&gt;
+&amp;amp;&lt;br&gt;
+ &lt;br&gt;
+&amp;amp;&lt;br&gt;
+B&lt;br&gt;
+)&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">8</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+*&lt;br&gt;
+&amp;quot;&lt;br&gt;
+/&lt;br&gt;
+#&lt;br&gt;
+2&lt;br&gt;
+0&lt;br&gt;
+2&lt;br&gt;
+4&lt;br&gt;
+# ) 0&lt;br&gt;
+2&lt;br&gt;
+ &lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+&amp;quot;# $&lt;br&gt;
+&amp;quot;# $,&lt;br&gt;
++&lt;br&gt;
+&amp;quot;# $&lt;br&gt;
+/ /&lt;br&gt;
+)&lt;br&gt;
+/ /&lt;br&gt;
+,&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+&amp;quot;# $&lt;br&gt;
+'&lt;br&gt;
+%)/&lt;br&gt;
+% (&lt;br&gt;
+ &lt;br&gt;
+2&lt;br&gt;
+,&lt;br&gt;
+/ /  &lt;br&gt;
+,&lt;br&gt;
+'&lt;br&gt;
+(&lt;br&gt;
+&amp;quot;# $&lt;br&gt;
+ &lt;br&gt;
+ &lt;br&gt;
+,&lt;br&gt;
+2&lt;br&gt;
+2&lt;br&gt;
+4&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+ &lt;br&gt;
+# ) 0&lt;br&gt;
+)&lt;br&gt;
+,)&lt;br&gt;
+0&lt;br&gt;
+'))0 7(&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+# ) 0&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+&amp;quot;# $&lt;br&gt;
+'&lt;br&gt;
+/&lt;br&gt;
+0&lt;br&gt;
+(&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+,&lt;br&gt;
+&amp;quot;# $&lt;br&gt;
+;&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+))0 7&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">9</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+!&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+# ) 0&lt;br&gt;
+&amp;amp;&lt;br&gt;
+) # % &amp;amp;&lt;br&gt;
+&amp;quot;# $&lt;br&gt;
+,&lt;br&gt;
+&amp;quot;# $,&lt;br&gt;
+&amp;quot;# $,&lt;br&gt;
+2&lt;br&gt;
+&amp;quot;# $&lt;br&gt;
+'&lt;br&gt;
+/ /&lt;br&gt;
+(&lt;br&gt;
+&amp;quot;&amp;amp;$&lt;br&gt;
+'&lt;br&gt;
+C # $()&lt;br&gt;
+&amp;quot;# $&lt;br&gt;
+,&lt;br&gt;
+D&lt;br&gt;
+C&lt;br&gt;
+&amp;quot;# $,&lt;br&gt;
+,&lt;br&gt;
+&amp;quot;# $,&lt;br&gt;
+&amp;quot;#&lt;br&gt;
+E&lt;br&gt;
+&amp;quot;# $,&lt;br&gt;
+'89(&lt;br&gt;
+,&lt;br&gt;
+&amp;quot;# $&lt;br&gt;
+59&lt;br&gt;
+&amp;quot;# $&lt;br&gt;
+&amp;quot;&lt;br&gt;
+55&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+&amp;quot;# $&lt;br&gt;
+&amp;quot;# $&lt;br&gt;
+&amp;lt;&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+!&lt;br&gt;
+,!&lt;br&gt;
+!&lt;br&gt;
+&amp;amp;&lt;br&gt;
+57&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+&amp;quot;&amp;amp;$&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+A&lt;br&gt;
+F&lt;br&gt;
+;&lt;br&gt;
+,&lt;br&gt;
+# % &amp;amp;58 4&lt;br&gt;
+/ /&lt;br&gt;
+# % &amp;amp;'&lt;br&gt;
+0&lt;br&gt;
+/&lt;br&gt;
+$&lt;br&gt;
+*&lt;br&gt;
+# 4)7/ /&lt;br&gt;
+# % &amp;amp;5:(&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+4&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+1&lt;br&gt;
+C&lt;br&gt;
+;&lt;br&gt;
+*# % &amp;amp;G&lt;br&gt;
+56&lt;br&gt;
+/&lt;br&gt;
+$&lt;br&gt;
+ &lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+A&lt;br&gt;
+,&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
++&amp;amp;&lt;br&gt;
+$ ) *&lt;br&gt;
+,&lt;br&gt;
+-&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+C&lt;br&gt;
+&amp;lt;&lt;br&gt;
+%&lt;br&gt;
+)&lt;br&gt;
+4&lt;br&gt;
+;&lt;br&gt;
+*/&lt;br&gt;
+$&lt;br&gt;
+5&amp;gt;&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
++&lt;br&gt;
+$&lt;br&gt;
+A&lt;br&gt;
+$&lt;br&gt;
+!&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+%&lt;br&gt;
+,&lt;br&gt;
+# % &amp;amp;,&lt;br&gt;
+&amp;amp;&lt;br&gt;
+0&lt;br&gt;
+*&lt;br&gt;
+%&lt;br&gt;
+&amp;lt;&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+&amp;quot;# $ &amp;lt;&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">10</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+# % &amp;amp;1&lt;br&gt;
+.&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+)&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+#&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+4&lt;br&gt;
+/&lt;br&gt;
+$&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+)&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+$&lt;br&gt;
+0&lt;br&gt;
+*&lt;br&gt;
+/&lt;br&gt;
+)&lt;br&gt;
+,3&lt;br&gt;
+H&lt;br&gt;
+H&lt;br&gt;
+H&lt;br&gt;
+5B&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+)&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+,&lt;br&gt;
++&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+)&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+H&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+,&lt;br&gt;
+,&lt;br&gt;
+ &lt;br&gt;
+# % &amp;amp;&lt;br&gt;
+,&lt;br&gt;
+ &lt;br&gt;
+2&lt;br&gt;
+/&lt;br&gt;
+)&lt;br&gt;
+,3&lt;br&gt;
+H&lt;br&gt;
+H&lt;br&gt;
+H&lt;br&gt;
+!&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">11</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+)&lt;br&gt;
+%&lt;br&gt;
+)&lt;br&gt;
+,)&lt;br&gt;
+0&lt;br&gt;
+,&lt;br&gt;
+)&lt;br&gt;
+&amp;amp;&lt;br&gt;
+0&lt;br&gt;
+ &lt;br&gt;
+ &lt;br&gt;
+=&lt;br&gt;
+&amp;quot;#$&lt;br&gt;
+I.HCF&amp;amp; 0)$.&lt;br&gt;
+/&lt;br&gt;
+/&lt;br&gt;
+56&lt;br&gt;
+%&lt;br&gt;
+)&lt;br&gt;
+/&lt;br&gt;
+&amp;quot;#$&lt;br&gt;
+&amp;quot;#$&lt;br&gt;
+?&lt;br&gt;
+@ ?J @ &lt;br&gt;
+?&lt;br&gt;
+# @&lt;br&gt;
+?J&lt;br&gt;
+# @&lt;br&gt;
+!&lt;br&gt;
+#)&lt;br&gt;
+0&lt;br&gt;
+#&lt;br&gt;
+%&lt;br&gt;
+&amp;amp;&lt;br&gt;
+&amp;quot;&lt;br&gt;
+#&lt;br&gt;
+)&lt;br&gt;
+  &lt;br&gt;
+/ /&lt;br&gt;
+#% &amp;amp;&lt;br&gt;
+#&lt;br&gt;
+&amp;quot; A&lt;br&gt;
+ &lt;br&gt;
+&amp;amp;&lt;br&gt;
+4&lt;br&gt;
+!&lt;br&gt;
+'&lt;br&gt;
+, ,&lt;br&gt;
+(&lt;br&gt;
+%&lt;br&gt;
+ &lt;br&gt;
+&amp;quot;#$&lt;br&gt;
+$ % ;&lt;br&gt;
+$&lt;br&gt;
+-&lt;br&gt;
+.&lt;br&gt;
+'&lt;br&gt;
+J&lt;br&gt;
+J&lt;br&gt;
+J&lt;br&gt;
+(&lt;br&gt;
+&amp;amp;&lt;br&gt;
+% 3&lt;br&gt;
+#&lt;br&gt;
+$&lt;br&gt;
+' % &amp;quot;&lt;br&gt;
+#&lt;br&gt;
+$&lt;br&gt;
+'&lt;br&gt;
+%&lt;br&gt;
+&amp;quot;#$,&lt;br&gt;
+'&lt;br&gt;
+/ /&lt;br&gt;
+(&lt;br&gt;
+' %&lt;br&gt;
+&amp;quot;&lt;br&gt;
+&amp;amp;&lt;br&gt;
+$&lt;br&gt;
+=&lt;br&gt;
+&amp;quot;# $&lt;br&gt;
+&lt;hr&gt;
+</Content>
+</Section>
+<Section>
+  <Description>
+    <Metadata name="Title">12</Metadata>
+  </Description>
+  <Content>&lt;br /&gt;
+&amp;quot;&lt;br&gt;
+5&lt;br&gt;
+J&lt;br&gt;
+J&lt;br&gt;
+7&lt;br&gt;
+J&lt;br&gt;
+J&lt;br&gt;
+8&lt;br&gt;
+J&lt;br&gt;
+J&lt;br&gt;
+J&lt;br&gt;
+:&lt;br&gt;
+J&lt;br&gt;
+J&lt;br&gt;
+J&lt;br&gt;
+J&lt;br&gt;
+6&lt;br&gt;
+J&lt;br&gt;
+J&lt;br&gt;
+J&lt;br&gt;
+&amp;gt; 0&lt;br&gt;
+G&lt;br&gt;
+!&lt;br&gt;
+/&lt;br&gt;
+ &lt;br&gt;
+! 0&lt;br&gt;
+$&lt;br&gt;
+ &lt;br&gt;
+5EEB' &amp;amp;+A 5DDB88:6:D(&lt;br&gt;
+&amp;amp;K# $J&amp;quot;# $&lt;br&gt;
+B&lt;br&gt;
+JJ&lt;br&gt;
+J&lt;br&gt;
+J&lt;br&gt;
+J&lt;br&gt;
+D &amp;amp;&lt;br&gt;
+JJ&lt;br&gt;
+,&lt;br&gt;
+J&lt;br&gt;
+J&lt;br&gt;
+&amp;amp;!&lt;br&gt;
+&amp;quot;# $&lt;br&gt;
+E&lt;br&gt;
+JJ&lt;br&gt;
+2&lt;br&gt;
+59&lt;br&gt;
+JJ&lt;br&gt;
+J J&lt;br&gt;
+55&lt;br&gt;
+JJ&lt;br&gt;
+J&lt;br&gt;
+7,J&lt;br&gt;
+57&lt;br&gt;
+JJ&lt;br&gt;
+J&lt;br&gt;
+58&lt;br&gt;
+JJ&lt;br&gt;
+J&lt;br&gt;
+J&lt;br&gt;
+5:&lt;br&gt;
+JJ&lt;br&gt;
+J&lt;br&gt;
+J&lt;br&gt;
+7&lt;br&gt;
+J&lt;br&gt;
+56&lt;br&gt;
+JJ&lt;br&gt;
+J&lt;br&gt;
+J&lt;br&gt;
+5&amp;gt;&lt;br&gt;
+JJ&lt;br&gt;
+J&lt;br&gt;
+L&lt;br&gt;
+JJ&lt;br&gt;
+J J&lt;br&gt;
+J&lt;br&gt;
+J&lt;br&gt;
+&lt;hr&gt;
+
+
+</Content>
+</Section>
+</Section>
+</Archive>
Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Enhanced-PDF/archives/rss-items.rdf
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Enhanced-PDF/archives/rss-items.rdf	(revision 37429)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Enhanced-PDF/archives/rss-items.rdf	(revision 37429)
@@ -0,0 +1,12 @@
+<item>
+   <title>Untitled</title>
+   <link>_httpdomainHtmlsafe__httpcollection_/document/HASHbb6e0c8f087c9c5b2e301a</link>
+</item>
+<item>
+   <title>Untitled</title>
+   <link>_httpdomainHtmlsafe__httpcollection_/document/HASH1a9cea0f239f754007681b</link>
+</item>
+<item>
+   <title>Untitled</title>
+   <link>_httpdomainHtmlsafe__httpcollection_/document/HASH019c5dca7f5bb781460a6b9c</link>
+</item>
Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Enhanced-PDF/index/build.cfg
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Enhanced-PDF/index/build.cfg	(revision 37429)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Enhanced-PDF/index/build.cfg	(revision 37429)
@@ -0,0 +1,16 @@
+builddate	1678158431
+buildtype	mgpp
+earliestdatestamp	1678158427
+indexfieldmap	text->TX	dc.Title,ex.dc.Title,Title->TI	Source->SO
+indexfields	text	dc.Title,ex.dc.Title,Title	Source
+indexlevels	Doc	Sec
+indexmap	text;dc.Title,ex.dc.Title,Title;Source;->idx
+indexstem	Enhanced-PDF
+infodbtype	gdbm
+levelmap	document->Doc	section->Sec
+maxnumeric	4
+numbytes	85978
+numdocs	3
+numsections	41
+stemindexes	7
+textlevel	Sec
Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Enhanced-PDF/index/rss-items.rdf
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Enhanced-PDF/index/rss-items.rdf	(revision 37429)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Enhanced-PDF/index/rss-items.rdf	(revision 37429)
@@ -0,0 +1,12 @@
+<item>
+   <title>Untitled</title>
+   <link>_httpdomainHtmlsafe__httpcollection_/document/HASHbb6e0c8f087c9c5b2e301a</link>
+</item>
+<item>
+   <title>Untitled</title>
+   <link>_httpdomainHtmlsafe__httpcollection_/document/HASH1a9cea0f239f754007681b</link>
+</item>
+<item>
+   <title>Untitled</title>
+   <link>_httpdomainHtmlsafe__httpcollection_/document/HASH019c5dca7f5bb781460a6b9c</link>
+</item>
