Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/HASH015936f5.dir/doc.xml
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/HASH015936f5.dir/doc.xml (revision 27727)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/HASH015936f5.dir/doc.xml (revision 27727)
@@ -0,0 +1,618 @@
+
+
+
+
+
+ indexed_doc
+ en
+ utf8
+ Clustering with finite data from semi-parametric mixture distributions
+ import/cluster.ps
+ tmp/1372402380/cluster.text
+ cluster.text
+ cluster.ps
+ cluster.ps
+ PostScriptPlugin
+ 94721
+ cluster
+ PS
+ _iconps_
+ doc.ps
+ doc.ps
+ Yong Wang
+ Ian H. Witten
+ HASH015936f516ed4b1d7b050af9
+ 1372400870
+ 20130628
+ 1372402380
+ 20130628
+ HASH015936f5.dir
+ doc.ps:application/postscript:
+
+ <pre>
+
+
+Clustering with finite data from semi-parametric mixture distributions
+
+Yong Wang Ian H. Witten Computer Science Department Computer Science Department
+University of Waikato, New Zealand University of Waikato, New Zealand
+
+Email: yongwang@cs.waikato.ac.nz Email: ihw@cs.waikato.ac.nz
+
+Abstract Existing clustering methods for the semi-parametric mixture distribution
+perform well as the volume of data increases. However, they all suffer from
+a serious drawback in finite-data situations: small outlying groups of data
+points can be completely ignored in the clusters that are produced, no matter
+how far away they lie from the major clusters. This can result in unbounded
+loss if the loss function is sensitive to the distance between clusters.
+
+This paper proposes a new distance-based clustering method that overcomes
+the problem by avoiding global constraints. Experimental results illustrate
+its superiority to existing methods when small clusters are present in finite
+data sets; they also suggest that it is more accurate and stable than other
+methods even when there are no small clusters.
+
+1 Introduction A common practical problem is to fit an underlying statistical
+distribution to a sample. In some applications, this involves estimating
+the parameters of a single distribution function--e.g. the mean and variance
+of a normal distribution. In others, an appropriate mixture of elementary
+distributions must be found--e.g. a set of normal distributions, each with
+its own mean and variance. Among many kinds of mixture distribution, one
+in particular is attracting increasing research attention because it has
+many practical applications: the semiparametric mixture distribution.
+
+A semi-parametric mixture distribution is one whose cumulative distribution
+function (CDF) has the form
+
+FG(x) = Z
+
+\\Theta F (x; `) dG(`); (1)
+
+where ` 2 \\Theta , the parameter space, and x 2 X , the sample space. This
+gives the CDF of the mixture distribution FG(x) in terms of two more elementary
+distributions: the component distribution F (x; `), which is given, and the
+mixing distribution G(`), which is unknown. The former has a single unknown
+parameter `, while the latter gives a CDF for `. For example, F (x; `) might
+be the normal distribution with mean ` and unit variance, where ` is a random
+variable distributed according to G(`).
+
+The problem that we will address is the estimation of G(`) from sampled data
+that are independent and identically distributed according to the unknown
+distribution FG(x). Once G(`) has been obtained, it is a straightforward
+matter to obtain the mixture distribution.
+
+The CDF G(`) can be either continuous or discrete. In the latter case, G(`)
+is composed of a number of mass points, say, `1; : : : ; `k with masses w1;
+: : : ; wk respectively, satisfying Pki=1 wi = 1. Then (1) can be re-written
+as
+
+FG(x) =
+
+kX
+
+i=1
+
+wiF (x; `i); (2)
+
+each mass point providing a component, or cluster, in the mixture with the
+corresponding weight. If the number of components k is finite and known a
+priori, the mixture distribution is called finite; otherwise it is treated
+as countably infinite. The qualifier "countably" is necessary to distinguish
+this case from the situation with continuous G(`), which is also infinite.
+
+We will focus on the estimation of arbitrary mixing distributions, i.e.,
+G(`) is any general probability distribution--finite, countably infinite
+or continuous. A few methods for tackling this problem can be found in the
+literature. However, as we shall see, they all suffer from a serious drawback
+in finite-data situations: small outlying groups of data points can be completely
+ignored in the clusters that are produced.
+
+This phenomenon seems to have been overlooked, presumably for three reasons:
+small amounts of data may be assumed to represent a small loss; a few data
+points
+
+1
+
+can easily be dismissed as outliers; and in the limit the problem evaporates
+because most estimators possess the property of strong consistency--which
+means that, almost surely, they converge weakly to any given G(`) as the
+sample size approaches infinity. However, often these reasons are inappropriate:
+the loss function may be sensitive to the distance between clusters; the
+small number of outlying data points may actually represent small clusters;
+and any practical clustering situation will necessarily involve finite data.
+
+This paper proposes a new method, based on the idea of local fitting, that
+successfully solves the problem. The experimental results presented below
+illustrate its superiority to existing methods when small clusters are present
+in finite data sets. Moreover, they also suggest that it is more accurate
+and stable than other methods even when there are no small clusters. Existing
+clustering methods for semi-parametric mixture distributions are briefly
+reviewed in the next section. Section 3 identifies a common problem from
+which these current methods suffer. Then we present the new solution, and
+in Section 5 we describe experiments that illustrate the problem that has
+been identified and show how the new method overcomes it.
+
+2 Clustering methods The general problem of inferring mixture models is treated
+extensively and in considerable depth in books by Titterington et al. (1985),
+McLachlan and Basford (1988) and Lindsay (1995). For semi-parametric mixture
+distributions there are three basic approaches: minimum distance, maximum
+likelihood, and Bayesian. We briefly introduce the first approach, which
+is the one adopted in the paper, review the other two to show why they are
+not suitable for arbitrary mixtures, and then return to the chosen approach
+and review the minimum distance estimators for arbitrary semi-parametric
+mixture distributions that have been described in the literature.
+
+The idea of the minimum distance method is to define some measure of the
+goodness of the clustering and optimize this by suitable choice of a mixing
+distribution Gn(`) for a sample of size n. We generally want the estimator
+to be strongly consistent as n ! 1, in the sense defined above, for arbitrary
+mixing distributions. We also generally want to take advantage of the special
+structure of semi-parametric mixtures to come up with an efficient algorithmic
+solution.
+
+The maximum likelihood approach maximizes the likelihood (or equivalently
+the log-likelihood) of the data by suitable choice of Gn(`). It can in fact
+be viewed as
+
+a minimum distance method that uses the Kullback- Leibler distance (Titterington
+et al., 1985). This approach has been widely used for estimating finite mixtures,
+particularly when the number of clusters is fairly small, and it is generally
+accepted that it is more accurate than other methods. However, it has not
+been used to estimate arbitrary semi-parametric mixtures, presumably because
+of its high computational cost. Its speed drops dramatically as the number
+of parameters that must be determined increases, which makes it computationally
+infeasible for arbitrary mixtures, since each data point might represent
+a component of the final distribution with its own parameters.
+
+Bayesian methods assume prior knowledge, often given by some kind of heuristic,
+to determine a suitable a priori probability density function. They are often
+used to determine the number of components in the final distribution--particularly
+when outliers are present. Like the maximum likelihood approach they are
+computationally expensive, for they use the same computational techniques.
+
+We now review existing minimum distance estimators for arbitrary semi-parametric
+mixture distributions. We begin with some notation. Let x1; : : : ; xn be
+a sample chosen according to the mixture distribution, and suppose (without
+loss of generality) that the sequence is ordered so that x1 ^ x2 ^ : : :
+^ xn. Let Gn(`) be a discrete estimator of the underlying mixing distribution
+with a set of support points at f`nj; j = 1; : : :; kng. Each `nj provides
+a component of the final clustering with
+
+weight wnj * 0, where Pk
+
+n
+
+j=1 wnj = 1. Given the sup-port points, obtaining G
+
+n(`) is equivalent to computing the weight vector wn = (wn1; wn2; : : :;
+wnk
+
+n)0. Denoteby F
+
+Gn(x) the estimated mixture CDF with respect to Gn(`).
+
+Two minimum distance estimators were proposed in the late 1960s. Choi and
+Bulgren (1968) used
+
+1 n
+
+nX
+
+i=1
+
+[FG
+
+n(xi) \\Gamma i=n]
+
+2 (3)
+
+as the distance measure. Minimizing this quantity with respect to Gn yields
+a strongly consistent estimator. A slight improvement is obtained by using
+the Cram'er-von Mises statistic
+
+1 n
+
+nX
+
+i=1
+
+[FG
+
+n(xi) \\Gamma (i \\Gamma 1=2)=n]
+
+2 + 1=(12n2); (4)
+
+which essentially replaces i=n in (3) with (i \\Gamma 12 )=n without affecting
+the asymptotic result. As might be expected, this reduces the bias for small-sample
+cases, as
+
+was demonstrated empirically by Macdonald (1971) in a note on Choi and Bulgren's
+paper.
+
+At about the same time, Deely and Kruse (1968) used the sup-norm associated
+with the Kolmogorov-Smirnov test. The minimization is over
+
+sup 1^i^nfjF
+
+Gn(xi) \\Gamma (i \\Gamma 1)=nj; jFGn(xi) \\Gamma i=njg; (5)
+
+and this leads to a linear programming problem. Deely and Kruse also established
+the strong consistency of their estimator Gn. Ten years later, this approach
+was extended by Blum and Susarla (1977) by using any sequence ffng of functions
+which satisfies sup jfn\\Gamma fGj ! 0 a.s. as n ! 1. Each fn can, for example,
+be obtained by a kernel-based density estimator. Blum and Susarla approximated
+the function fn by the overall mixture pdf fG
+
+n , and established the strong consistency of the esti-mator G
+
+n under weak conditions.
+
+For reason of simplicity and generality, we will denote the approximation
+between two mathematical entities of the same type by ,=, which implies the
+minimization with respect to an estimator of a distance measure between the
+entities on either side. The types of entity involved in this paper include
+vector, function and measure, and we use the same symbol ,= for each.
+
+In the work reviewed above, two kinds of estimator are used: CDF-based (Choi
+and Bulgren, Macdonald, and Deely and Kruse) and pdf-based (Blum and Susarla).
+CDF-based estimators involve approximating an empirical distribution with
+an estimated one FG
+
+n. We writethis as
+
+FG
+
+n ,= Fn; (6)
+
+where Fn is the Kolmogorov empirical CDF--or indeed any empirical CDF that
+converges to it. Pdf-based estimators involve the approximation between probability
+density functions:
+
+fG
+
+n ,= fn; (7)
+
+where fG
+
+n is the estimated mixture pdf and fn is theempirical pdf described above.
+
+The entities involved in (6) and (7) are functions. When the approximation
+is computed, however, it is computed between vectors that represent the functions.
+These vectors contain the function values at a particular set of points,
+which we call "fitting points." In the work reviewed above, the fitting points
+are chosen to be the data points themselves.
+
+3 The problem of minority clusters
+
+Although they perform well asymptotically, all the minimum distance methods
+described above suffer from the finite-sample problem discussed earlier:
+they can neglect small groups of outlying data points no matter how far they
+lie from the dominant data points. The underlying reason is that the objective
+function to be minimized is defined globally rather than locally. A global
+approach means that the value of the estimated probability density function
+at a particular place will be influenced by all data points, no matter how
+far away they are. This can cause small groups of data points to be ignored
+even if they are a long way from the dominant part of the data sample. From
+a probabilistic point of view, however, there is no reason to subsume distant
+groups within the major clusters just because they are relatively small.
+
+The ultimate effect of suppressing distant minority clusters depends on how
+the clustering is applied. If the application's loss function depends on
+the distance between clusters, the result may prove disastrous because there
+is no limit to how far away these outlying groups may be. One might argue
+that small groups of points can easily be explained away as outliers, because
+the effect will become less important as the number of data points increases--and
+it will disappear in the limit of infinite data. However, in a finite-data
+situation--and all practical applications necessarily involve finite data--the
+"outliers" may equally well represent small minority clusters. Furthermore,
+outlying data points are not really treated as outliers by these methods--whether
+or not they are discarded is merely an artifact of the global fitting calculation.
+When clustering, the final mixture distribution should take all data points
+into account--including outlying clusters if any exist. If practical applications
+demand that small outlying clusters are suppressed, this should be done in
+a separate stage.
+
+In distance-based clustering, each data point has a farreaching effect because
+of two global constraints. One is the use of the cumulative distribution
+function; the other is the normalization constraint Pk
+
+n
+
+j=1 wnj = 1. Theseconstraints may sacrifice a small number of data points--
+
+at any distance--for a better overall fit to the data as a whole. Choi and
+Bulgren (1968), the Cramer-von Mises statistic (Macdonald, 1971), and Deely
+and Kruse (1968) all enforce both the CDF and the normalization constraints.
+Blum and Susarla (1977) drop the CDF, but still enforce the normalization
+constraint. The result is that these clustering methods are only appropriate
+for finite mixtures without small clusters, where the risk of suppressing
+clusters is low.
+
+This paper addresses the general problem of arbitrary mixtures. Of course,
+the minority cluster problem exists for all types of mixture--including finite
+mixtures. Even here, the maximum likelihood and Bayesian approaches do not
+solve the problem, because they both introduce a global normalization constraint.
+
+4 Solving the minority cluster
+
+problem
+
+Now that the source of the problem has been identified, the solution is clear,
+at least in principle: drop both the approximation of CDFs, as Blum and Susarla
+(1977) do, and the normalization constraint--no matter how seductive it may
+seem.
+
+Let G0n be a discrete function with masses fwnjg at f`njg; note that we do
+not require the wnj to sum to one. Since the new method operates in terms
+of measures rather than distribution functions, the notion of approximation
+is altered to use intervals rather than points. Using the formulation described
+in Section 2, we have
+
+PG0
+
+n ,= Pn; (8)
+
+where PG0
+
+n is the estimated measure and Pn is the em-pirical measure. The intervals
+over which the approximation takes place are called "fitting intervals."
+Since (8) is not subject to the normalization constraint, G0n is not a CDF
+and PG0
+
+n is not a probability measure. How-ever, G0
+
+n can be easily converted into a CDF estimatorby normalizing it after equation
+(8) has been solved.
+
+To define the estimation procedure fully, we need to determine (a) the set
+of support points, (b) the set of fitting intervals, (c) the empirical measure,
+and (d) the distance measure. Here we discuss these in an intuitive manner;
+Wang and Witten (1999) show how to determine them in a way that guarantees
+a strongly consistent estimator.
+
+Support points. The support points are usually suggested by the data points
+in the sample. For example, if the component distribution F (x; `) is the
+normal distribution with mean ` and unit variance, each data point can be
+taken as a support point. In fact, the support points are more accurately
+described as potential support points, because their associated weights may
+become zero after solving (8)--and, in practice, many often do.
+
+Fitting intervals. The fitting intervals are also suggested by the data points.
+In the normal distribution example, each data point xi can provide one interval,
+such as [xi \\Gamma 3oe; xi], or two, such as [xi \\Gamma 3oe; xi] and [xi;
+xi + 3oe], or more. There is no problem if the fitting
+
+intervals overlap. Their length should not be so large that points can exert
+an influence on the clustering at an unduly remote place, nor so small that
+the empirical measure is inaccurate. The experiments reported below use intervals
+of a few standard deviations around each data point, and, as we will see,
+this works well.
+
+Empirical measure. The empirical measure can be the probability measure determined
+by the Kolmogorov empirical CDF, or any measure that converges to it. The
+fitting intervals discussed above can be open, closed, or semi-open. This
+will affect the empirical measure if data points are used as interval boundaries,
+although it does not change the values of the estimated measure because the
+corresponding distribution is continuous. In smallsample situations, bias
+can be reduced by careful attention to this detail--as Macdonald (1971) discusses
+with respect to Choi and Bulgren's (1968) method.
+
+Distance measure. The choice of distance measure determines what kind of
+mathematical programming problem must be solved. For example, a quadratic
+distance will give rise to a least squares problem under linear constraints,
+whereas the sup-norm gives rise to a linear programming problem that can
+be solved using the simplex method. These two measures have efficient solutions
+that are globally optimal.
+
+It is worth pointing out that abandoning the global constraints associated
+with both CDFs and normalization can brings with it a computational advantage.
+In vector form, we write PG0
+
+n = AG
+
+0 nwn, where wn is the(unnormalized) weight vector and each element of the
+
+matrix AG0
+
+n is the probability value of a component dis-tribution over an fitting interval.
+Then, provided the
+
+support points corresponding to w0n and w00n lie outside each others' sphere
+of influence as determined by the component distributions F (x; `), the estimation
+procedure becomes`
+
+A0G0
+
+n 00 A00
+
+G0n ' `
+
+w0n w00n ' ,= `
+
+P 0n P 00n ' ; (9)
+
+subject to w0n * 0 and w00n * 0. This is the same as combining the solutions
+of two sub-equations, A0nw0n ,= P 0n subject to w0n * 0, and A00nw00n ,=
+P 00n subject to w00n * 0. If the relevant support points continue to lie
+outside each others' sphere of influence, the sub-equations can be further
+partitioned. This implies that when data points are sufficiently far apart,
+the mixing distribution G can be estimated by grouping data points in different
+regions. Moreover, the solution in each region can be normalized separately
+before they are combined, which yields a better estimation of the mixing
+distribution.
+
+If the normalization constraint Pk
+
+n
+
+j=1 wnj = 1 is re-tained when estimating the mixing distribution, the es
+timation procedure becomes
+
+PG
+
+n ,= Pn: (10)
+
+where the estimator Gn is a discrete CDF on \\Theta . This constraint is necessary
+for the left-hand side of (10) to be a probability measure. Although he did
+not develop an operational estimation scheme, Barbe (1998) suggested exploiting
+the fact that the empirical probability measure is approximated by the estimated
+probability measure--but he retained the normalization constraint. As noted
+above, relaxing the constraint has the effect of loosening the throttling
+effect of large clusters on small groups of outliers, and our experimental
+results show that the resulting estimator suffers from the drawback noted
+earlier.
+
+Both estimators, Gn obtained from (10) and G0n from (8), have been shown
+to be strongly consistent under weak conditions similar to those used by
+others (Wang & Witten, 1999). Of course, the weak convergence of G0n is in
+the sense of general functions, not CDFs. The strong consistency of G0n immediately
+implies the strong consistency of the CDF estimator obtained by normalizing
+G0n.
+
+5 Experimental validation We have conducted experiments to illustrate the
+failure of existing methods to detect small outlying clusters, and the improvement
+achieved by the new scheme. The results also suggest that the new method
+is more accurate and stable than the others.
+
+When comparing clustering methods, it is not always easy to evaluate the
+clusters obtained. To finesse this problem we consider simple artificial
+situations in which the proper outcome is clear. Some practical applications
+of clusters do provide objective evaluation functions; however, these are
+beyond the scope of this paper.
+
+The methods used are Choi and Bulgren (1968) (denoted choi), Macdonald's
+application of the Cram'er-von Mises statistic (cram'er), the new method
+with the normalization constraint (test), and the new method without that
+constraint (new). In each case, equations involving non-negativity and/or
+linear equality constraints are solved as quadratic programming problems
+using the elegant and efficient procedures nnls and lsei provided by Lawson
+and Hanson (1974). All four methods have the same computational time complexity.
+
+We set the sample size n to 100 throughout the experiments. The data points
+are artificially generated from a mixture of two clusters: n1 points from
+N (0; 1) and n2 points from N (100; 1). The values of n1 and n2 are in the
+ratios 99 : 1, 97 : 3, 93 : 7, 80 : 20 and 50 : 50.
+
+Every data point is taken as a potential support point in all four methods:
+thus the number of potential components in the clustering is 100. For test
+and new, fitting intervals need to be determined. In the experiments, each
+data point xi provides the two fitting intervals [xi \\Gamma 3; xi] and [xi;
+xi + 3]. Any data point located on the boundary of an interval is counted
+as half a point when determining the empirical measure over that interval.
+
+These choices are admittedly crude, and further improvements in the accuracy
+and speed of test and new are possible that take advantage of the flexibility
+provided by (10) and (8). For example, accuracy will likely increase with
+more--and more carefully chosen-- support points and fitting intervals. The
+fact that it performs well even with crudely chosen support points and fitting
+intervals testifies to the robustness of the method.
+
+Our primary interest in this experiment is the weights of the clusters that
+are found. To cast the results in terms of the underlying models, we use
+the cluster weights to estimate values for n1 and n2. Of course, the results
+often do not contain exactly two clusters--but because the underlying cluster
+centres, 0 and 100, are well separated compared to their standard deviation
+of 1, it is highly unlikely that any data points from one cluster will fall
+anywhere near the other. Thus we use a threshold of 50 to divide the clusters
+into two groups: those near 0 and those near 100. The final cluster weights
+are normalized, and the weights for the first group are summed to obtain
+an estimate ^n1 of n1, while those for the second group are summed to give
+an estimate ^n2 of n2.
+
+Table 1 shows results for each of the four methods. Each cell represents
+one hundred separate experimental runs. Three figures are recorded. At the
+top is the number of times the method failed to detect the smaller cluster,
+that is, the number of times ^n2 = 0. In the middle are the average values
+for ^n1 and ^n2. At the bottom is the standard deviation of ^n1 and ^n2 (which
+are equal). These three figures can be thought of as measures of reliability,
+accuracy and stability respectively.
+
+The top figures in Table 1 show clearly that only new is always reliable
+in the sense that it never fails to detect the smaller cluster. The other
+methods fail mostly when n2 = 1; their failure rate gradually decreases as
+n2 grows. The center figures show that, under all conditions, new gives a
+more accurate estimate of the correct values of n1 and n2 than the other
+methods. As expected, cram'er shows a noticeable improvement over choi, but
+it is very minor. The test method has lower failure rates and produces estimates
+that are more accurate and far more stable (indicated by the bottom fign1
+= 99 n1 = 97 n1 = 93 n1 = 80 n1 = 50
+
+n2 = 1 n2 = 3 n2 = 7 n2 = 20 n2 = 50 choi Failures 86 42 4 0 0
+
+^n1=^n2 99.9/0.1 99.2/0.8 95.8/4.2 82.0/18.0 50.6/49.4 SD(^n1) 0.36 0.98
+1.71 1.77 1.30 cram'er Failures 80 31 1 0 0
+
+^n1=^n2 99.8/0.2 98.6/1.4 95.1/4.9 81.6/18.4 49.7/50.3 SD(^n1) 0.50 1.13
+1.89 1.80 1.31 test Failures 52 5 0 0 0
+
+^n1=^n2 99.8/0.2 98.2/1.8 94.1/5.9 80.8/19.2 50.1/49.9 SD(^n1) 0.32 0.83
+0.87 0.78 0.55 new Failures 0 0 0 0 0
+
+^n1=^n2 99.0/1.0 96.9/3.1 92.8/7.2 79.9/20.1 50.1/49.9 SD(^n1) 0.01 0.16
+0.19 0.34 0.41
+
+Table 1: Experimental results for detecting small clusters ures) than those
+for choi and cram'er--presumably because it is less constrained. Of the four
+methods, new is clearly and consistently the winner in terms of all three
+measures: reliability, accuracy and stability.
+
+The results of the new method can be further improved. If the decomposed
+form (9) is used instead of (8), and the solutions of the sub-equations are
+normalized before combining them--which is feasible because the two underlying
+clusters are so distant from each other--the correct values are obtained
+for ^n1 and ^n2 in virtually every trial.
+
+6 Conclusions We have identified a shortcoming of existing clustering methods
+for arbitrary semi-parametric mixture distributions: they fail to detect
+very small clusters reliably. This is a significant weakness when the minority
+clusters are far from the dominant ones and the loss function takes account
+of the distance of misclustered points.
+
+We have described a new clustering method for arbitrary semi-parametric mixture
+distributions, and shown experimentally that it overcomes the problem. Furthermore,
+the experiments suggest that the new estimator is more accurate and more
+stable than existing ones.
+
+References Barbe, P. (1998). Statistical analysis of mixtures and
+
+the empirical probability measure. Acta Applicandae Mathematicae, 50(3),
+253-340.
+
+Blum, J. R. & Susarla, V. (1977). Estimation of a mixing
+
+distribution function. Ann. Probab, 5, 200-209.
+
+Choi, K. & Bulgren, W. B. (1968). An estimation procedure for mixtures of
+distributions. J. R. Statist. Soc. B, 30, 444-460.
+
+Deely, J. J. & Kruse, R. L. (1968). Construction of sequences estimating
+the mixing distribution. Ann. Math. Statist., 39, 286-288.
+
+Lawson, C. L. & Hanson, R. J. (1974). Solving Least
+
+Squares Problems. Prentice-Hall, Inc.
+
+Lindsay, B. G. (1995). Mixture models: theory, geometry,
+
+and applications, Volume 5 of NSF-CBMS Regional Conference Series in Probability
+and Statistics. Institute for Mathematical Statistics: Hayward, CA.
+
+Macdonald, P. D. M. (1971). Comment on a paper by
+
+Choi and Bulgren. J. R. Statist. Soc. B, 33, 326- 329.
+
+McLachlan, G. & Basford, K. (1988). Mixture Models:
+
+Inference and Applications to Clustering. Marcel Dekker, New York.
+
+Titterington, D. M., Smith, A. F. M. & Makov, U. E.
+
+(1985). Statistical Analysis of Finite Mixture Distributions. John Wiley
+& Sons.
+
+Wang, Y. & Witten, I. H. (1999). The estimation of mixing distributions by
+approximating empirical measures. Technical Report (in preparation), Dept.
+of Computer Science, University of Waikato, New Zealand.
+</pre>
+
+
Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/HASH019c5dca.dir/doc.xml
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/HASH019c5dca.dir/doc.xml (revision 27727)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/HASH019c5dca.dir/doc.xml (revision 27727)
@@ -0,0 +1,516 @@
+
+
+
+
+
+ indexed_doc
+ en
+ utf8
+ Bronwyn
+ biblio_for_dl_scientometrics.do
+ http://research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402381/pdf03.html
+ http://research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402381/pdf03.html
+ import/pdf03.pdf
+ tmp/1372402381/pdf03.html
+ pdf03.html
+ pdf03.pdf
+ pdf03.pdf
+ PDFPlugin
+ 35935
+ pdf03
+ PDF
+ _iconpdf_
+ doc.pdf
+ doc.pdf
+ 17
+ Acrobat PDFWriter 2.0 for Macintosh
+ 1.1
+ Applications for Bibliometric Research in the Emerging Digital Libraries
+ 644
+ pdf03.pdf
+ /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/import
+ Microsoft Word
+ 35935
+ 2013:06:28 18:27:50+12:00
+ Sally Jo Cunningham
+ 17
+ Bronwyn
+ PDF
+ false
+ 1999:09:27 16:05:06
+ biblio_for_dl_scientometrics.do
+ 8.57
+ application/pdf
+ HASH019c5dca7f5bb781460a6b9c
+ 1372400870
+ 20130628
+ 1372402381
+ 20130628
+ HASH019c5dca.dir
+ doc.pdf:application/pdf:
+
+
+<A name=1></a><b>Applications for Bibliometric Research</b><br>
+<b>in the Emerging Digital Libraries</b><br>
+Sally Jo Cunningham<br>
+Department of Computer Science<br>
+University of Waikato<br>
+Hamilton, New Zealand<br>
+email: sallyjo@waikato.ac.nz<br>
+<b>Abstract:</b> Large numbers of research documents have recently become available on<br>
+the Internet through âdigital librariesâ, and these collections are seeing high levels of<br>
+use by their related research communities. A secondary use for these document<br>
+repositories and indexes is as a platform for bibliometric research. We examine the<br>
+extent to which the new digital libraries support conventional bibliometric analysis, and<br>
+discuss shortcomings in their current forms. Interestingly, these electronic text<br>
+archives also provide opportunities for new types of studies: generally the full text of<br>
+documents are available for analysis, giving a finer grain of insight than abstract-only<br>
+online databases; these repositories often contain technical reports or pre-prints, the<br>
+âgrey literatureâ that has been previously unavailable for analysis; and document<br>
+âusageâ can be measured directly by recording user accesses, rather than studied<br>
+indirectly through document references.<br>
+<b>1. Introduction</b><br>
+In recent years a number of "digital libraries" have become available through the<br>
+Internet. While the technology promises in the future to support large, heterogenous<br>
+collections, at present the most widely used of the academically-focussed digital<br>
+libraries are generally repositories of one or two types of document (typically technical<br>
+reports, journal articles, pre-prints, or conference proceedings), grouped by discipline.<br>
+<hr>
+<A name=2></a>A distinguishing characteristic of these digital libraries is that the full text of documents<br>
+are often available for retrieval, as well as bibliographic records.The sciences are<br>
+represented much more heavily in the present crop of digital libraries than the social<br>
+sciences, arts, or humanities. They are maintained by professional societies,<br>
+universities, research laboratories, and even private individuals. Access is generally<br>
+free, both to search and to download documents.<br>
+The emergence of these subject-specific digital libraries is particularly important<br>
+given the pattern of access to materials presently employed by research scientists.<br>
+Informal exchanges of preprints, reprints, and photocopies of papers passed on by<br>
+colleagues currently are major venues for the transmission of scientific information<br>
+between researchers in the sciences. In one study, the dependence on these sources<br>
+ranges from 12% (for chemistry) to 39% (for mathematics) of all papers cited in<br>
+researchers' own publications [11]. A qualitative study of study of how computer<br>
+scientists locate and retrieve documents (computing is one of the domains considered<br>
+later in this paper) indicates that for that field, technical reports and research documents<br>
+found in various locations on the Internet are a preferred source of information [6].<br>
+Many of the digital library systems discussed in this paper are repositories for just this<br>
+type of literature. The documents tend to be of high quality: primarily technical<br>
+reports or working papers from research institutions (both academic and commercial),<br>
+as well as advance copies of work accepted for publication in conventional paper<br>
+journals. Moreover, these digital libraries are also coming to include refereed work<br>
+published digitally (in electronic journals). Anecdotal evidence suggests that in their<br>
+fields, these digital libraries are coming to be the resource of choice for locating cutting<br>
+edge work.<br>
+For specialized subjects such as high energy physics, this dependence on<br>
+informal or extra-library dissemination can be much higher. Ginsparg ([9], [10])<br>
+reports that fields in physics have traditionally relied heavily on preprint exchanges, and<br>
+the digital repositories of physics preprints begun in 1991 (the PHYSICS E-PRINT<br>
+ARCHIVES) have to a large extent supplanted conventional publishing and physical<br>
+<hr>
+<A name=3></a>paper mailing of technical reports. By providing ready access to information sources<br>
+that are already preferentially utilized by scientists, the digital libraries show potential to<br>
+increase access to information that until recently was expensive or difficult to acquire in<br>
+paper form. Indeed, in some fields (most notably physics) this process has already<br>
+begun, as researchers in less developed countries report access to ongoing research<br>
+through the Internet repositories that their local libraries could not afford to acquire<br>
+through conventional journal subscriptions ([9], [10]).<br>
+The primary use for new bibliographic resources is, of course, for the contents<br>
+of the documents involved. A secondary use for emerging resources is as a basis for<br>
+bibliometric analysis of the subject field. With the conventionally published scientific<br>
+literature, the sheer difficulty of accumulating statistics discouraged bibliometric<br>
+research until the advent of large bibliographic databases in the 1960's. Computerized<br>
+bibliographic databases sparked a significant increase in the number of large-scale<br>
+bibliographic studies, as significant portions of the collection and analysis of data could<br>
+be automated ([12], [13]). The availability of CD-ROM versions of bibliographic<br>
+databases has been of particular importance, since they provide a cheaper alternative to<br>
+the online commercial databases [3].<br>
+These computerized bibliographic resources have drawbacks, however. The<br>
+greatest is that the full text of documents are rarely available, and even abstracts are not<br>
+always present. This obviously limits the types of bibliometric research that can be<br>
+conducted <i>solely</i> through these databases. In addition, these databases are generally<br>
+limited to formally published documents (those appearing in selected books, journals,<br>
+and conference proceedings). The "grey literature" of technical reports, pre-prints, and<br>
+other works not formally published are largely ignored, and it is this absence of easy<br>
+access to these documents that has hampered the analysis of these important forms of<br>
+scientific communication.<br>
+The digital libraries currently in existence complement the online and CD-ROM<br>
+bibliographic databases. They are best suited for examinations of the "physical"<br>
+characteristics of documents (for example, document length), analysis based on<br>
+<hr>
+<A name=4></a>bibliographic information that can be automatically extracted from the document text or<br>
+the sometimes unevenly formatted bibliographic records (such as obsolescence<br>
+studies), and usage studies (geographic or institutional origin of users, date/time of<br>
+access, individual patterns of document retrieval, etc.). Because references are present<br>
+in the document file but not identified by field, co-citation and bibliographic coupling<br>
+research is not well-supported, and conducting these studies requires considerable<br>
+effort on the part of the researcher.<br>
+The variety of bibliographic repositories in the available digital libraries in itself<br>
+has great potential in conducting bibliometric research. Sigogneau et al [15] present a<br>
+case study illustrating the ways in which the strengths of different databases can be<br>
+played off each other; they conduct a fine-grained analysis of the emergence of research<br>
+fronts in molecular and cellular biology, and demonstrate that the observations gleaned<br>
+from two complementary bibliographic databases provide greater insight into their<br>
+problem. Similarly, it appears that the types of bibliographic data that can be gleaned<br>
+from the relatively unstructured digital libraries can be profitably combined with data<br>
+from online databases, CD-ROMS, and other more conventional bibliographic<br>
+resources.<br>
+This paper is organized as follows: Section 2 discusses the types of indexing<br>
+and searching available with current digital libraries; Section 3 gives examples of<br>
+conventional bibliometric techniques applied to Internet-accessible archives; Section 4<br>
+discusses opportunities to directly measure usage of documents and to detect<br>
+information-seeking patterns in researchers; and Section 5 presents our conclusions.<br>
+<b>2. Indexing and searching in current digital libraries</b><br>
+At present, the types of indexing fields for most academically-oriented digital<br>
+library systems are limited. Many schemes index on user-supplied document<br>
+descriptions, abstracts, or similar document surrogates (for example, the PHYSICS E-<br>
+PRINT ARCHIVE [10], a collection of physics pre-prints and technical reports). As will<br>
+<hr>
+<A name=5></a>be discussed below, the quality of this user-provided data can be highly variable, and<br>
+may unfavorably impact the usefulness of the index for searching. Alternatively, a<br>
+designated site librarian may maintain a catalog (eg, the WATERS [14] system, now<br>
+subsumed by NCSTRL (http://www.ncstrl.org/), both primarily collections of<br>
+computer science technical reports); in this case the quality of the bibliographic<br>
+information may be expedited to be higher, but fewer sites will be likely to support<br>
+such a librarian and therefore fewer documents are likely to be included in the digital<br>
+library. In a âharvestingâ system such as the computer science technical report<br>
+collections supported by HARVEST [2] or the NEW ZEALAND DIGITAL LIBRARY<br>
+computer science technical report collection ([16], [17]), documents are indexed from<br>
+passive repositories (that may not even be aware that their documents are being<br>
+included in the digital library). Harvesting systems therefore cannot rely on the<br>
+presence of bibliographic data of any sort.<br>
+Because of the relative paucity of high-quality bibliographic data available to<br>
+many of the current academically- or research-focussed digital library collections, their<br>
+search interfaces tend to be more primitive than those ordinarily found in online<br>
+bibliographic databases or library catalogs. Systems such as NCSTRL can support<br>
+author, title, and subject searching, but this more sophisticated search functionality<br>
+comes at the expense of requiring participating repositories to use specific software. As<br>
+a consequence, these latter systems may provide access to a small number of sites than<br>
+harvesting systems. Harvesters may access a broader range of providers, but at the<br>
+penalty of being limited to unfielded, keyword searches over the raw text of the<br>
+document or document surrogate.<br>
+Specifically, the indexing in existing digital libraries has a variety of shortcomings for<br>
+bibliometric applications:<br>
+â¢<br>
+<i>lack of fielded indexing:</i> As noted above, some large and widely used digital<br>
+libraries (such as the computer science technical report collection of the NEW<br>
+ZEALAND DIGITAL LIBRARY) may lack formal cataloging entirely, and rely on<br>
+<hr>
+<A name=6></a>keyword searching over the raw document text. Obviously this makes field-<br>
+dependent analysis more difficult (for example, locating documents produced by<br>
+specific authors), and in the worst case my require a manual examination of all<br>
+files in the collection in order to reliably identify a desired document subset.<br>
+However, keyword search techniques that approximate fielded searching results<br>
+may suffice: for example in the NEW ZEALAND DIGITAL LIBRARY computer<br>
+science technical report collection, limiting the keyword search for âJohnsonâ<br>
+to a search of first pages only is likely to retrieve documents written by Johnson<br>
+(since for the majority of computer science technical reports, the first page<br>
+contains little more than author, title, date, and institution details).<br>
+A more principled approach to extracting bibliographic information is embodied<br>
+in the CiteSeer tool [1]. This software parses raw, unfielded academic<br>
+documents and attempts to identify such indexing information as author, title,<br>
+reference list, etc. Obviously such a tool cannot attain 100% accuracy over a<br>
+heterogenous document collection, but in practice it appears useful in that it can<br>
+make a good first pass in processing a set of documents, providing an initial set<br>
+of parsed documents for analysis. The remaining (presumably much smaller) set<br>
+of unparsable documents can then be dealt with manually.<br>
+â¢<br>
+<i>lack of consistency in field formatting:</i> Current digital libraries usually acquire<br>
+bibliographic information from either the authors of submitted articles or<br>
+automatic extraction routines (retrieving bibliographic details from catalog files<br>
+that may or may not be in a given document site, and that may or may not be in<br>
+an easily parsable form). Neither of these methods produce records with<br>
+standard formatting, which causes problems with automated bibliometric<br>
+analysis. Consider the following examples selected from entries in the hep-th<br>
+(high energy physics) collection of the PHYSICS E-PRINT ARCHIVES:<br>
+<hr>
+<A name=7></a>(i)<br>
+Authors: A. Yu. Alekseev, V. Schomerus<br>
+(ii)<br>
+Authors: Adel Bilal and Ian. I. Kogan<br>
+(iii)<br>
+Authors: Paul S. Aspinwall and David R. Morrison (with an appendix <br>
+by Mark Gross)<br>
+(iv)<br>
+Authors: A. H. Chamseddine and Herbi Dreiner (ETH-Zurich)<br>
+In this case, typical for existing digital libraries, there is no standardized format<br>
+for authors' names (here, appearing with full names, initials plus last name, and<br>
+a mixture of the two); no standard convention for separating author names<br>
+(here, either a comma or "and" are used); and parenthetical information can<br>
+include a variety of information such as the name of an associate author or the<br>
+institutional affiliations of an author. Manual processing or specially crafted<br>
+software would be required to reformat these fields for analysis.<br>
+â¢<br>
+<i>duplicate entries: </i> Digital libraries that draw documents from a variety of sources<br>
+may inadvertently contain duplicate items. Unfortunately, the irregular<br>
+formatting of the bibliographic information makes it difficult to automatically<br>
+detect these duplicates.<br>
+â¢<br>
+<i>implicit field tagging:</i> In some repositories, items are not explicitly tagged with<br>
+certain types of information â most commonly the document's date of<br>
+publication or production. Instead, the date is implicit in the document's title<br>
+(eg, its numeration in a technical report series) or in the location of the document<br>
+in the file structure of the repository (eg, separate directories exist for each<br>
+year). A second common piece of implicit data is the authorsâ institutional<br>
+affiliations. This may be contained in the document itself (typically on a cover<br>
+page), or may be implicit in the documentâs location (for example, a<br>
+corporationâs technical reports are stored in its ftp repository). Again, in these<br>
+<hr>
+<A name=8></a>cases special processing is required to append this field information to a<br>
+document record for bibliometric analysis. <br>
+â¢<br>
+<i>extraction of document text:</i> Few of the documents stored in the research-<br>
+oriented digital libraries discussed in this paper are straight ascii text; instead,<br>
+documents may appear in a variety of file formats, such as LaTeX, PostScript,<br>
+PDF, etc. If the contents of the documents are to be automatically processed<br>
+(for example, to count the words in a document, or to extract reference<br>
+publication dates for an obsolescence study), then the text must be extracted.<br>
+Utilities are available to convert most common document formats to ascii.<br>
+It is likely that many of these problems will be addressed as the Internet-based<br>
+document indexing systems mature. Even minor changes can greatly increase the<br>
+useability of a bibliographic database for bibliometric research. For example, the<br>
+addition of an explicit date tag to many online databases in 1975 sparked new<br>
+applications in time series research [3].<br>
+<b>3. Opportunities for applications of bibliometric techniques</b><br>
+One type of bibliometric research concentrates on quantifying fundamental,<br>
+structural details about a subject literature: how many items are published, how many<br>
+authors are publishing, over what time period documents are likely to be used, etc.<br>
+More complex studies analyze the relationships between documents, such as how<br>
+documents cluster into subjects. The following examples give a flavour of the<br>
+bibliometric research that is possible using the emerging digital libraries:<br>
+<i>examining the âphysicalâ characteristics of archived documents</i><br>
+One relatively straightforward type of bibliometric study characterizes the<br>
+formats of different literatures. For example, Figure 1 presents a the range of the size<br>
+<hr>
+<A name=9></a>of computer science technical reports as measured by their length in pages. Of the<br>
+45,720 documents in the CSTR collection as of April 1998, nearly 1600 did not contain<br>
+page divisions in their files (and hence are excluded from analysis). Note that the<br>
+number of pages in the shorter documents (<50 pages) falls into an approximately<br>
+normal distribution (slightly skewed to the left), while presumably the longer<br>
+documents represent Mastersâ and Doctoral theses. A surprising number of documents<br>
+are very short (between one and 5 pages); these may represent the type of condensed<br>
+results frequently found in the âtechnical notesâ, âshort papersâ, and âposter sessionsâ<br>
+of computing conferences and journals. The average number of pages per document,<br>
+27.5, appears to be slightly longer than the common upper bound for a computing<br>
+journal article, although this observation must be confirmed by a similar study of the<br>
+lengths of formally published computing articles.<br>
+This type of analysis is of particular interest for technical reports, since they<br>
+have not been studied in the same detail as formally published papers. A comparison of<br>
+the physical characteristics of the formal and informal literature could provide<br>
+supporting evidence for common beliefs about the relationship between the two types<br>
+of documents. For example, do publishing constraints force journal and proceedings<br>
+articles to be shorter than technical reports, and therefore presumably omit technical<br>
+details of findings? Do technical reports contain more/less extensive reference sections?<br>
+If reference sections of technical reports are longer than those of published articles, then<br>
+citation links are being ommitted in published works; if technical reports contain fewer<br>
+references, then this may confirm earlier indications that computer scientists tend to<br>
+âresearch firstâ and do literature surveys later [6].<br>
+Figure 1. Range of sizes of CS technical reports, measured by number of pages<br>
+<i>obsolescence studies.</i><br>
+A document is considered obsolete when it is no longer referenced by the<br>
+current literature. Typically, documents receive their greatest number and frequency of<br>
+<hr>
+<A name=10></a>citations immediately after publication, and the frequency of citation falls rapidly as time<br>
+passes. One technique for estimating the obsolescence rate of a body of literatureâ the<br>
+<i>synchronous</i> method â is to find the median date in the references of the documents.<br>
+This median date is subtracted from the year of publication for the documents, yielding<br>
+the <i>median citation age</i>. As would be expected, this median varies between the<br>
+disciplines. Typically the social sciences and arts have a higher median citation age<br>
+than the âhardâ sciences and engineering, indicating that documents obsolesce more<br>
+quickly for the latter fields.<br>
+As noted in Section 2, references are not generally explicitly tagged in existing<br>
+digital repositories. However, reference dates can usually be extracted from the<br>
+document text by first locating the reference section (usually delimited by a "references"<br>
+or "bibliography" section heading), and then extracting all numbers in the appropriate<br>
+ranges for dates for the field under study.<br>
+To illustrate this process, 188 technical reports were sampled from Internet-<br>
+accessible repositories1 and used as source documents for a synchronous obsolescence<br>
+study. Conveniently, the repositories chosen organize technical reports into sub-<br>
+directories by their date of publication. The reference dates for each technical report<br>
+were automatically extracted by software that scanned the documentâs file for numbers<br>
+of the form 19XX, since previous studies indicate that few if any computing reports<br>
+reference documents published in previous centuries [5]. Table 1 presents the median<br>
+citation age calculated for these documents, broken down by repository and the year of<br>
+publication for the source documents from which the reference dates were extracted:<br>
+Table 1. Median citation ages for technical report repositories<br>
+The median citation age ranges between 2 and 4 years, which is consistent with<br>
+previous examinations of computing and information systems literature ([5], [4]).<br>
+When graphed, the distribution of reference dates show the exponential curve typically<br>
+found in obsolescence studies, including the final droop due to an âimmediacy effectâ<br>
+<hr>
+<A name=11></a>as fewer very new documents are available for citation [7]. These types of results<br>
+provide confirmation that references used in computer science technical reports (the pre-<br>
+eminent âgrey literatureâ of the computing field) conforms to the same patterns as<br>
+references found in the formally published literature.<br>
+<i>co-citation and bibliographic coupling studies</i><br>
+The rate at which documents cite each other (co-citation) or cite the same<br>
+documents (bibliographic coupling) can be used to produce "maps" of a subject<br>
+literature. These techniques rely on analysis of the references of documents, and these<br>
+references must be in a common format. While digital libraries contain full text of<br>
+documents, their references are not standardized, and indeed are not even tagged as<br>
+such. To perform these studies the references must be manually extracted and<br>
+processedâa tedious process that is only worthwhile for documents (such as technical<br>
+reports) that are not included in existing citation databases such as the Science Citation<br>
+Index and Social Science Citation Index.<br>
+<i>detecting cycles or regularities in the rate of production of research</i><br>
+Analysis of trends in the production of technical reports can give indications<br>
+about working conditions that affect research; for example, is more research produced<br>
+over the summer, when the teaching load is lighter? or is research steadily produced<br>
+throughout the year?<br>
+Figure 2. Distribution of the number of documents submitted to hep-th, 1992-1994<br>
+Figures 2 and 3 present statistics on document accumulation in the hep-th (high<br>
+energy physics) e-print server, a part of the PHYSICS E-PRINT ARCHIVE. This system<br>
+is one of the oldest formal pre-print archives, and has become the primary means for<br>
+information dissemination in its field. Examination of these figures reveals several<br>
+trends. Clearly the absolute number of documents deposited in the repository has<br>
+<hr>
+<A name=12></a>tended to increase over the time period. For all three years, research production has its<br>
+lowest point in January and February, increases through May and June, then decreases<br>
+until August and September. At that point the rate of production steps up, reaching a<br>
+yearly peak in November and December. This pattern is less clear for 1992, which<br>
+might be expected as the archive was established in mid-1991.<br>
+Figure 3. Distribution of the percentage of documents submitted to hep-th, 1992-1994<br>
+<b>4. Analysis of usage data</b><br>
+The emerging Internet-based digital libraries will permit research on scientific<br>
+information collection and use at a much finer grain than is possible with current paper<br>
+libraries or online bibliographic databases. Current bibliometric or scientometric<br>
+research of this type must measure information use indirectly â for example, through<br>
+examination of the list of references appended to published articles. However, it is well<br>
+known that authors do not necessarily include in the reference list all documents that<br>
+could have been cited, and conversely that not all references listed may have been<br>
+actually âusedâ in performing the research; citation behavior can be affected by a<br>
+number of motivating factors (Garfield lists <i>15</i> possible reasons in [8]).<br>
+Digital library transaction logs provide a powerful tool for direct analysis of<br>
+document âusageâ: since digital libraries contain the actual document (rather than only a<br>
+document surrogate), the relative amount of âuseâ that a digital libraryâs clients make of<br>
+a given document sees can be estimated from the number of times the document file is<br>
+downloaded (and, presumably, the document is read). Note that file downloading is a<br>
+much stronger statement on the part of the user than, for example, having a<br>
+bibliographic record appear in the query result set for a conventional bibliographic<br>
+system; the user downloads only <i>after</i> the document has been found potentially relevant<br>
+through examination of its document surrogate. Additionally, downloading is<br>
+frequently time-consuming and sometimes costly (depending on local pricing for<br>
+<hr>
+<A name=13></a>Internet access). Downloaded documents are therefore highly likely at least to be<br>
+scanned, if not read closely. The transaction logs for a digital library can provide a<br>
+global picture of the use of documents in the collection, since all user interactions with<br>
+the library can be automatically logged for analysis. By contrast, it is of course<br>
+impossible to track usage of print bibliographies, and very difficult to monitor usage of<br>
+bibliographic data available on CD-ROM across more than one or two sites.<br>
+Furthermore, analysis of search requests by geographic location, institution,<br>
+and sometimes even individual user are also possible. As an example, Table 2 presents<br>
+a portion of the summary of usage statistics (broken down by domain code) for queries<br>
+to the computer science technical collection of the NEW ZEALAND DIGITAL LIBRARY.<br>
+Examination of the data indicates that the heaviest use of the collection comes from<br>
+North America, Europe (particularly Germany and Finland), as well as the local New<br>
+Zealand community and nearby Australia. As expected for such a collection, a large<br>
+proportion of users are from educational (.edu) institutions; surprisingly, however, a<br>
+similar number of queries come from commercial (.com) organizations, indicating<br>
+perhaps that the documents are seeing use in commercial research and development<br>
+units.<br>
+Table 2. Accesses to the NEW ZEALAND DIGITAL LIBRARY CS collection by Domain<br>Code<br>
+Of course, usage levels can also be further broken down by IP number<br>
+(indicating institutions), and systems requiring users to register may also be able to<br>
+analyze usage on an individual basis. Since the query strings themselves are also<br>
+recorded in the transaction logs, this domain/institution/individual activity could also be<br>
+linked to specific subjects through the query terms. Summaries of this type could be<br>
+invaluable for studies of geographic diffusion and distribution of research topics.<br>
+Transaction log analysis can also indicate time-related patterns in the<br>
+information seeking behavior of digital library users. As a sample of this type of<br>
+analysis, Paul Ginsparg notes a seven day periodicity in the number of search requests<br>
+<hr>
+<A name=14></a>made to the PHYSICS E-PRINT archives (Figure 4, reproduced from [9]). From this he<br>
+adduces that many physicists do not yet have weekend access to the Internet (an<br>
+alternative, slightly more cynical hypothesis is that even high energy theoretical<br>
+physicists take the weekend off).<br>
+Figure 4. Summary of search requests to the physics pre-print archives<br>
+<b>5. Conclusion</b><br>
+This study suggests opportunities for conducting bibliometric research on the<br>
+evolving digital libraries. These repositories are suitable platforms for conventional<br>
+bibliometric techniques (such as obsolescence studies, quantification of physical<br>
+characteristics of documents comprising a subject literature, time analysis, etc.). The<br>
+ability to directly monitor access to documents in digital libraries also enables<br>
+researchers to explicitly quantify document usage, as well as to implicitly measure<br>
+usage through citations. Additional facilities could aid in the performance of<br>
+bibliographic experiments, such as: improved tagging of document fields; provision of<br>
+utilities to strip out titles, authors, etc. from common document formats; and the ability<br>
+to easily eliminate duplicate entries from downloaded library subsets. Unfortunately,<br>
+the most useful of these additional facilities â those associated with a higher degree of<br>
+cataloging â run counter to the underlying philosophy of many digital libraries: to<br>
+avoid, if possible, manual processing and formal cataloging of documents. While<br>
+adherence to this principle can limit the accuracy of fielded searching (or indeed,<br>
+preclude it altogether), it can also avoid the cataloging bottleneck and permit digital<br>
+libraries to provide access to larger numbers of documents.<br>
+The digital libraries complement the information currently available through<br>
+paper, online, and CD-ROM bibliographic resources. While these latter databases<br>
+generally have the advantage of standardized formatting of bibliographic fields, the<br>
+digital libraries are freely accessible, often contain "grey literature" that is otherwise<br>
+<hr>
+<A name=15></a>unavailable for analysis, and generally make the full text of documents available. The<br>
+insights gained from analysis of digital libraries will add to the store of "information<br>
+about information" that we have gained from older types of bibliographic repositories.<br>
+<b>References</b><br>
+[1] Bollacker, K.D., S. Lawrence, and C.L.Giles, CiteSeer: An Autonomous Web<br>
+Agent for Automatic Retrieval and Identification of Interesting Publications,<br>
+<i>Proceedings of the Second International Conference on Autonomous Agents</i><br>
+(Minneapolis/St. Paul, May 9-13), 1998.<br>
+[2] Bowman, C.M., P.B. Danzig, U. Manber, and M.F. Schwartz, Scalable Internet<br>
+resource discovery: Research problems and approaches, <i>Communications of</i><br>
+<i>the ACM 37(8)</i> (1994) 98-107.<br>
+[3] Burton, Hilary D. , Use of a virtual information system for bibliometric analysis,<br>
+<i>Informaton Processing & Management 24(1)</i> (1988) 39-44.<br>
+[4] Cunningham, S.J., An empirical investigation of the obsolescence rate for<br>
+information systems literature, <i>Library and Information Science</i><br>
+<i>Research</i>., 1996, http://library.fgcu.edu/iclc/lisrissu.htm<br>
+ [5] Cunningham, S.J., and D. Bocock, Obsolescence of computing literature.<br>
+<i>Scientometrics</i> <i>34(2) </i> (1995), pp. 255-262.<br>
+ [6] Cunningham, S.J. and Lynn Silipigni Connaway, Information searching<br>
+preferences and practices of computer science researchers, <i>Proceedings of</i><br>
+<i>OZCHI '96</i> (1996) 294-299.<br>
+[7] de Solla Price, D.J., Citation measures of hard science, soft science, technology,<br>
+and nonscience. In: C.E. Nelson and D.K. Pollock (eds), <i>Communication</i><br>
+<i>among scientists and engineers</i> (Heath Lexington, 1970).<br>
+[8] Garfield, E., <i>Citation Indexing: Its theory and application in Science, Technology</i><br>
+<i>and Humanities (</i>Wiley, 1979).<br>
+<hr>
+<A name=16></a>[9] Ginsparg, P. After dinner remarks: 14 Oct â94 APS meeting at LANL, 1994<br>
+(<URL: http://xxx.lanl.gov/blurb> ).<br>
+[10] Ginsparg, P., First steps towards electronic research communication, <i>Computers</i><br>
+<i>in Physics 8(4)</i> (1994) 390-401. <br>
+[11] Hallmark, J., Scientists' access and retrieval of references cited in their recent<br>
+journal articles, <i> College and Research Libraries 55(3)</i> (1994) 199-210.<br>
+[12] Hawkins, D.T. , Unconventional uses of on-line information retrieval systems:<br>
+on-line bibliometric studies, <i>Journal of the American Society for Information</i><br>
+<i>Science 28</i> (1977) 13-18.<br>
+[13] McGhee, P.E. , P.R. Skinner, K. Roberto, N.J. Ridenour, and S.M. Larson,<br>
+Using online databases to study current research trends: an online bibliometric<br>
+study, <i>Library and Information Science Research 9</i> (1987) 285-291.<br>
+[14] Maly, K., E.A. Fox, J.C. French, and A.L. Selman, Wide area technical report<br>
+server (<i>Technical Report , </i> Dept. of Computer Science, Old Dominion<br>
+University, <br>
+1994. <br>
+Also <br>
+available <br>
+at <br>
+ <br>
+ <br>
+<URL:<br>
+http://www.cs.odu.edu/WATERS/WATERS-paper.ps> ).<br>
+[15] Sigogneau, M.J. , S. Bain, J.P. Courtial, and H. Feillet, Scientific innovation in<br>
+bibliographical databases: a comparative study of the Science Citation Index<br>
+and the Pascal database, <i>Scientometrics 22(1)</i> (1991) 65-82.<br>
+[16] Witten, I.H., S.J. Cunningham, M. Vallabh, and T.C. Bell, A New Zealand<br>
+digital library for computer science research, <i>Proceedings of Digital Libraries</i><br>
+<i>'95</i> (1995) 25-30.<br>
+[17] Witten, I.H., C. Nevill-Manning, and S.J. Cunningham, A public library based<br>
+on full-text retrieval, <i>Communications of the ACM</i> 41(4), 1998, p. 71<br>
+<hr>
+<A name=17></a> <br>
+1Documents were randomly sampled from the DEC<br>
+(ftp://crl.dec.com/pub/DEC/CRL/tech-reports/), Sony<br>
+(ftp://ftp.csl.sony.co.jp/CSL/CSL-Papers), and Ohio (ftp://archive.cis.ohio-<br>
+state.edu/pub/tech-report/) technical report repositories<br>
+<hr>
+
+
+
+
+
Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/HASH07915444.dir/doc.xml
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/HASH07915444.dir/doc.xml (revision 27727)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/HASH07915444.dir/doc.xml (revision 27727)
@@ -0,0 +1,471 @@
+
+
+
+
+
+ indexed_doc
+ en
+ utf8
+ Authorship patterns in Information Systems
+ http://research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402381/rtf01.html
+ http://research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402381/rtf01.html
+ import/rtf01.rtf
+ tmp/1372402381/rtf01.html
+ rtf01.html
+ rtf01.rtf
+ rtf01.rtf
+ RTFPlugin
+ 144917
+ rtf01
+ RTF
+ _iconrtf_
+ doc.rtf
+ doc.rtf
+ Sally Jo Cunningham
+ Stuart M. Dillon
+ HASH079154443e2ecce7bb4208
+ 1372400870
+ 20130628
+ 1372402381
+ 20130628
+ HASH07915444.dir
+ doc.rtf:application/rtf:
+
+ <b>Authorship patterns in Information
+Systems</b><p>
+<b></b><p>
+Sally Jo Cunningham and Stuart M. Dillon<p>
+Department of Computer Science<p>
+University of Waikato<p>
+Hamilton, New Zealand<p>
+email: sallyjo@waikato.ac.nz<p>
+<p>
+<b>Abstract:</b> This paper examines the patterns of multiple authorship in
+five information systems journals. Specifically, we determine the distribution
+of the number of authors per paper in this field, the proportion of male and
+female authors, gender composition of research teams, and the incidence of
+collaborative relationships spanning institutional affiliations and across
+different geographic regions.<p>
+<p>
+<b>1. Introduction</b><p>
+<b></b><p>
+In his seminal work <i>Little Science, Big Science</i> [16], Derek J. De Solla
+Price drew attention to the 20th century trend of increasing team work in
+scientific research and co-authorship in publicationÂmaking a
+tongue-in-cheek prediction that "by 1980 the single author paper will be
+extinct", and that scientific collaboration would continue to increase so that
+scholarly publications would "move steadily toward an infinity of authors per
+paper" (p. 89). <p>
+<p>
+Since 1963, Price's conjectures have been measured and, to a large extent,
+verified, for a number of domains in the social sciences, arts, and physical
+sciences. Characteristics of collaboration in research have been examined in a
+number of ways: for example, through bibliographic analysis of readily
+quantifiable variables such as the rate of co-authorship and mean number of
+co-authors per document (for an overview of this type of research, see [10]);
+through studies of the social organizations that support collaboration in
+particular and research in general (such as the ground-breaking work of Crane
+[6]); and by ethnographic descriptions of the patterns of behavior employed by
+researchers in finding collaborators, organizing the research tasks, and
+composing the written documentation of the work (for example, the examination
+of the philosophy research process presented in [19]).<p>
+<p>
+This paper examines authorship patterns in the field of Information Systems
+(IS). IS is a relatively young discipline, an interdisciplinary field at the
+conjunction of computer science, management, and the social sciences. It
+concerns itself primarily managerial, and "people" issues that support
+information management (primarily in an organizational context), and to a
+lesser extent with hardware and software issues. Perhaps because it is an
+emerging, interdisciplinary field, IS has been the focus of few
+bibliometric/scientometric studies. The present work uses bibliometric
+techniques to examine the extent of collaborative authorship in the field, the
+geographic distribution of co-authors, and gender patterns in publication and
+collaboration.<p>
+<p>
+<b>2. Methodology</b><p>
+<b></b><p>
+The journals and time periods examined for this study are listed in Table 1.
+Journal articles, rather than books or technical reports, were chosen for
+analysis because the journal is the primary source of information in IS, making
+up the bulk of documents cited [7]. Five journals were selected for study,
+based on the criteria that they well known internationally, cover a relatively
+broad set of topics in the IS field, have author information available, and
+are published in the English language. It should be noted, however, that the
+journals selected tend to the management end of IS.<p>
+<p>
+
+
+<pre>
+Journal title abbreviation years
+Journal of Systems Management JSM 1989-1995
+Information Systems Research ISR 1990-1995
+Strategic Information Systems SIS 1991-1995
+Management Information Systems Quarterly MISQ 1989-1995
+Decision Support Systems DSS 1989-1995
+
+</pre>
+<p>
+Table 1. Journals analyzed in this study<p>
+<p>
+The following definitions and guidelines were used in gathering data from the
+five journals:<p>
+<p>
+·author: All individuals identified as authors in the heading of the
+paper were included, and counted equally. Some journal volumes apparently
+enforced an alphabetic name ordering on authors, while other journalsÂor
+even other volumes of the same journalÂdid not; for this reason we did not
+attempt to record the rank orderings of authors. Only personal (rather than
+corporate) authors were included in this study.<p>
+<p>
+·article: All refereed papers from each issue of each journal were
+considered for inclusion in the study. All other articles (book reviews,
+editorials, letters to the editor, reports of conferences, etc.) were excluded.
+While all refereed articles were included in the examination of co-authorship
+rates, some of these papers were omitted from the remainder of the study
+because the gender and/or the affiliation of one or more authors could not be
+determined.<p>
+<p>
+·gender: Where possible, the gender of an author was determined from
+the author's biography or picture. If this information was not available or
+was inconclusive, the gender was inferred from the author's personal name(s).
+If any doubt remained for any co-author of an article (that is, if the author
+was listed only by initials or had an ambiguous personal name), then that
+article was omitted from the study of author gender.<p>
+<p>
+·institution: For co-authored articles, we noted whether or not all
+authors were affiliated with the same institution (generally a university or
+company). A single institution could have more than one physical location.<p>
+<p>
+·geographic area: Co-authored articles were examined to determine
+whether all authors' institutions are from the same geographic region. This
+somewhat subjective category was defined as follows: for highly populated and
+physically large countries such as the United States, authors were considered
+to be from the same region if their institution were located in the same or
+adjacent states; for lightly populated or physically compact countries (such as
+New Zealand or the Netherlands, respectively), the entire country was
+considered to be a single geographic region.<p>
+<p>
+<b>3. Results</b><p>
+<b></b><p>
+This section discusses the amount of collaboration in publishing, the
+geographic/institutional spread of co-author affiliation, and the gender of
+authors in the IS literature.<p>
+<p>
+<i>degree of collaborative authorship</i><p>
+<i></i><p>
+Tables 2Â4 summarize authorship collaboration in IS. Approximately 38% of
+the articles have a single author; the majority of he papers are co-authored,
+with two or three authors (Table 2). The maximum number of authors for a single
+paper was six, found in a vanishingly small minority of the articles (less than
+0.5%). Viewed strictly in terms of the percentage of co-authored papers (Table
+3), it is readily apparent that co-authorship is the norm for all journals,
+over the entire period of study. The journal with the smallest degree of
+co-authorship, the <i>Journal of Systems Management</i> (JSM), saw its
+percentage of collaboratively written articles rise from approximately
+one-third to one-half; the remainder of the journals have a co-authorship rate
+ranging from 40% to 100%. The percentage of co-authored papers has risen
+slightly between 1989 and 1995 in four of the five journalsÂperhaps
+reflecting the trend to increased co-authorship reported in other fields, as
+the subjects matured [3].<p>
+<p>
+
+
+<pre>
+number of number of percentage
+authors articles
+1 368 37.74%
+2 391 40.10%
+3 171 17.54%
+4 37 3.80%
+5 4 0.41%
+6 4 0.41%
+Total 975 100.00%
+
+</pre>
+<p>
+Table 2. Distribution of number of co-authors per paper<p>
+
+
+<pre>
+ JSM ISR SIS MISQ DSS average
+1989 36% 68% 73% 59%
+1990 29% 75% 68% 57% 57%
+1991 39% 92% 60% 77% 71% 68%
+1992 41% 100% 40% 81% 68% 66%
+1993 48% 92% 63% 89% 70% 72%
+1994 46% 90% 67% 82% 70% 71%
+1995 54% 87% 58% 87% 79% 75%
+
+</pre>
+<p>
+Table 3. Percentage of co-authored articles<p>
+<p>
+
+
+<pre>
+ Mean Variance Std dev std error Number of
+ articles
+JSM 1.50 .466 .682 .039 308
+ISR 2.175 .604 .777 .079 97
+SIS 1.739 .655 .809 .086 88
+MISQ 2.251 .954 .977 .075 171
+DSS 2.071 .866 .931 .053 311
+Total 1.903 .799 .894 .029 975
+
+</pre>
+<p>
+Table 4a. Mean number of co-authors per paper<p>
+<p>
+<IMG SRC="_httpdocimg_/rtf011.gif"><p>
+Table 4b. T-test of mean number of co-authors<p>
+<p>
+The mean number of authors per article ranged from 1.5 (for the Journal of
+Systems Management) to 2.175 (for Information Systems Research), with an
+overall mean of 1.903 (Table 4a). As was noted when considering the
+distribution of numbers of co-authors in Table 2, while collaboration is the
+norm, the size of the research team in IS is relatively small. Differences in
+mean between the journals was generally not statisticaly significant, with the
+exception of ISR/DSS and ISR/MISQ (Table 4b).<p>
+<p>
+<i>institutional affiliation and geographic region</i><p>
+<i></i><p>
+Table 5 presents the institutional and geographical commonalities found amongst
+co-authors. As noted in Section 2, at this point we use a subset of the
+articles examined in this study: those papers for which we could identify the
+institutional affiliation and gender of all authors. For nearly half of the
+co-authored articles of this subsetÂ46%Âall authors for an article
+are either affiliated with the same institution <i>or</i> are resident in the
+same geographic region. Just over half of the multiply authored papers, then,
+involve a collaboration across significant distances. For nearly one-third
+(32%) of the co-authored papers, all authors are affiliated with the same
+institutionÂagain, indicating a significant degree of collaboration across
+institutional boundaries. The collaborative relationships of working groups
+are thus surprisingly dispersed, suggesting that IS is a field with a healthy
+"invisible college". <p>
+
+
+<pre>
+ JSM ISR SIS MISQ DSS average
+ 1989- 1990- 1991- 1989- 1989-
+ 1994 1994 1994 1994 1994
+Co-authored articles 147 71 80 35 62 128 133 514 861
+occurrences out of 364 40% 89% 56% 166 77% 189 70% 60%
+percentage
+co-authors from same 95 15 20 48 61 239
+institution OR same 147 65% 71 21% 35 58% 128 38% 133 46% 514 46%
+geographical area
+occurrences out of
+percentage
+co-authors from same 34 1 5 11 23 74
+area, different 147 23% 71 1% 35 14% 128 9% 133 17% 514 14%
+institutions
+occurrences out of
+percentage
+
+</pre>
+<p>
+Table 5. Percentage of co-authors from the same institution or geographical
+area<p>
+<p>
+<i>gender of authors</i><p>
+<i></i><p>
+Gender was recorded for <i>all</i> authors for whom it was explicitly stated or
+could be inferred; this could be determined for 861 papers, with 1021 authors.
+As no attempt was made to maintain a list of names, it is unknown how many
+unique individuals are represented in that total. Approximately four-fifths of
+the authors were male (Table 6), with male authors being in the majority for
+each journal. <p>
+<p>
+
+
+<pre>
+Gender Number Percentage
+male 804 78.7%
+female 217 21.3%
+
+</pre>
+<p>
+Table 6. Gender of authors<p>
+<p>
+The preponderance of male authors appears to mirror the under-representation of
+women in the Management/IS disciplines of academia, in which opportunities for
+publication and research are more likely than in commercial enterprises ([12],
+[21]). IS departments are generally located within the business or management
+faculty in universities, where women tend to be over-represented as
+instructors, lecturers, contract researchers, and other untenured staff
+positions. In the mid-eighties in the US, for example, women held 52% of the
+instructor and lower teaching positions and 36% of the assistant professorships
+in business schools, but accounted for only 6% of the full [2]. These lower
+level positions provide fewer opportunities for research funding, and generally
+involve a higher teaching load (with proportionally less time for research).<p>
+<p>
+Next, we examine the question of whether or not males and female have the same
+patterns of collaboration and co-authorship (Table 7). The percentage of male
+authors who published a single-authored paper is 37.31% ([343 male single
+authors] / [804 male authors]); the percentage of female authors who published
+solo is 18.89% ([41 single author females] / [217 female authors]). The
+percentage of male authors involved in male-only co-authored papers is 42.66%
+([343 / 804]), while the percentage of female authors who published in
+female-only groups is 6.91% (15/217). Clearly, then, a female author is more
+likely to co-publish than a male author, and more likely to publish in mixed
+gender research teams.<p>
+
+
+<pre>
+ single multiple single multiple multiple
+ male author authors, female authors, authors, male
+ male only author female only and female
+number 300 343 41 15 161
+percentage 34.9% 39.9% 4.8% 1.7% 18.7%
+
+</pre>
+<p>
+Table 7. Gender composition of publishing teams<p>
+<p>
+<b>4. Conclusions</b><p>
+<b></b><p>
+The high proportion of multiply-authored papers is characteristic of the
+physical and life sciences rather than the social sciences. In the "hard"
+sciences the percentage of co-authored articles is reported to range from
+two-thirds and up ([5], [13]), with nearly universal co-authorship in fields
+for which research is based on complex, expensive instruments/equipment ([14],
+as reported in [9]). By way of contrast, the proportion of single-authored
+papers is much higher in the humanities and social sciences: in philosophy, for
+example, collaboration is so unusual that some researchers find it difficult to
+imagine how a joint project could be produced [19]. Even in these disciplines,
+however, sub-fields may vary in their degree of collaboration, often reflecting
+equipment or team needs outside the norm for that discipline (for example,
+biophysical and archaeological anthropology show higher degrees of
+collaboration than sociocultural and linguistic anthropology [4]). IS, then,
+seems to fit more into the multiply-authored norm of the physical or
+experimental sciences than the humanities/social sciences.<p>
+<p>
+This point is slightly muddied, however, when comparing the mean number of
+authors in IS with the mean of other fields (Table 8). IS articles tend to
+have a smaller average number of co-authors than the "hard" sciences, even
+though the rate of co-authorship is high. Two hypotheses present themselves:
+that the experimental team needed to support IS research is smaller than the
+team size necessary for managing the instruments for the physical sciences;
+and/or that the support personnel for IS research may not be acknowledged with
+authorship, as seems to be the case in some of the sciences.<p>
+<p>
+
+
+<pre>
+Discipline authors/paper year(s) of study Reference
+Library science 1.17 1989-90 [17]
+Counseling 1.45 1971-1982 [8]
+Anthropology 1.79 1983 [4]
+Applied, physical, 2.13 1978-1980 [20]
+analytical chemistry
+Chemical engineering 2.13 [22]
+Biomedicine (basic 2.21 1961-1978 [18]
+life sciences)
+Biomedicine 2.25 1961-1978 [18]
+(preclinical basic
+research)
+Biochemistry 2.41 1978-1980 [20]
+Biomedicine 2.71 1961-1978 [18]
+(clinical research)
+Biochemistry 2.72 [22]
+Chemistry 2.82 1974-1975 [11]
+Schistosomiasis 2.92 1972-1986 [15]
+Political Science 3.54 1974-1975 [11]
+Biology 3.97 1974-1975 [11]
+Psychology 4.58 1974-1975 [11]
+Astronomy & 7.4 1974 [1]
+astrophysics
+
+</pre>
+<p>
+Table 8. Average number of authors for a variety of fields<p>
+<p>
+The degree of collaboration in IS that crosses institutional and geographic
+boundaries is significant, and warrants further attentionÂin particular,
+to investigate the communication techniques that support co-authorship.
+Traditionally, collaboration occurs through face-to-face meetings, telephone,
+and postal correspondence; it is likely that email and other Internet-based
+communication modes also see significant use, given the naturally high degree
+of computer literacy in this field.<p>
+<p>
+<b>References</b><p>
+<b></b><p>
+[1]Abt, H. A. (1984) "Citations to single and multiauthored papers<i>,"
+Publications of the Astronomical Society of the Pacific</i> 96, 746-749.<p>
+<p>
+[2]Aisenberg, N., and Harrington, M. (1988) <i>Women of Academe</i>,
+University of Massachusetts Press.<p>
+<p>
+[3]Beaver, D. de B., and Rosen, R. (1979) "Studies in scientific collaboration
+Part III: Professionalization and the natural history of modern scientific
+co-authorship," <i>Scientometrics </i>1(3), 231-245.<p>
+<p>
+[4]Choi, J.M. (1988) "An analysis of authorship in anthropology journals, 1963
+& 1983<i>," Behavioral & Social Sciences Librarian</i> 6(3/4), 85-94.<p>
+<p>
+[5]Clarke, B.L. (1964) "Multiple authorship trends in scientific papers,'
+<i>Science</i> 143, 882-884.<p>
+<p>
+[6]Crane, D. (1972) <i>Invisible colleges: Diffusion of Knowledge in
+Scientific communities</i>, University of Chicago Press.<p>
+<p>
+[7]Cunningham, S.J. (1996) "An empirical investigation of the obsolescence
+rate for information systems literature." <i>Working Paper Series 95/16</i>,
+Dept. of Computer Science, University of Waikato, Hamilton, New Zealand. To
+appear in <i>Library and Information Science Research</i>..<p>
+<p>
+[8]Gladding, S. (1984) "Multiple authorship in the <i>Personnel and Guidance
+Journal</i>: a 12-year study), <i>Personnel and Guidance Journal</i>, June,
+628-630.<p>
+<p>
+[9]Gordon, M.D. (1979) "A critical reassessment of inferred relations between
+multiple authorship, scientific collaboration, the production of papers and
+their acceptance for publication," <i>Scientometrics</i> 2(3), 193-201.<p>
+<p>
+[10]Harsanyi, M.A. (1993) "Multiple authors, multiple
+problemsÂBibliometrics and the study of scholarly collaboration: a
+literature review," <i>LISR</i> 15, 325-354.<p>
+<p>
+[11]Heffner, A.G. (1981) "Funded research, multiple authorship and
+subauthorship collaboration in four disciplines," <i>Scientometrics</i> 3,
+231-.<p>
+<p>
+[12]McKeen, C.A., and Bujaki, M.L. (1994) "Taking women into account", <i>CA
+Magazine, 127</i> <i>(2)</i>, pp. 29-35.<p>
+<p>
+[13]Meadows, A.J. (1974) <i>Communication in Science</i>. London:
+Butterworths.<p>
+<p>
+[14]Meadows, A.J., and O'Connor, J.G. (1971) "A survey in depth of a selected
+information field (astronomy and astrophysics). Astronomy Department,
+University of Leicester.<p>
+<p>
+[15]Pao, M.L. (1992) "Global and local collaborators: a study of scientific
+collaboration," <i>Information Processing & Management</i> 28(1), 99-109.<p>
+<p>
+[16]Price, Derek J. de Solla. (1963) <i>Little science, big science</i>. New
+York: Columbia University Press.<p>
+<p>
+[17]Raptis, P. (1992) "Authorship characteristics in five international
+library science journals," <i>Libri </i>42(1), 35-52.<p>
+<p>
+[18]Satyanarayana, K. and Ratnakar, K.V. (1989) "Authorship patterns in life
+sciences, preclinical basic and clinical research papers,"
+<i>Scientometrics</i> 17(3-4), 363-371.<p>
+<p>
+[19]Sievert, D., and Sievert, ME. (1989) "Philosophical Research: report
+from the field," <i>Proceedings of the Humanists at Work symposium</i> (April,
+Chicago, ILL, USA). Published by the University of Illinois at Chicago.<p>
+<p>
+[20]Stefaniak, B. (1982) "Individual and multiple authorship of papers in
+chemistry and physics," <i>Scientometrics </i>4(4), 331-337.<p>
+<p>
+[21]Still, L.V. (1993) <i>Where to from here? The managerial woman in
+transition</i>, Business and Professional Publishing.<p>
+<p>
+[22]Subrahmanyam, K., and Stephens, E.M. (1982) "Research collaboration and
+funding in biochemistry and chemical engineering," <i>International Forum on
+Information and Documentation</i> 7, 26-.<p>
+
+
+
Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/HASH1a9cea0f.dir/doc.xml
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/HASH1a9cea0f.dir/doc.xml (revision 27727)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/HASH1a9cea0f.dir/doc.xml (revision 27727)
@@ -0,0 +1,730 @@
+
+
+
+
+
+ indexed_doc
+ en
+ utf8
+ Bronwyn
+ Greenstone: A Comprehensive Open-Source Digital Library Software...
+ http://research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402380/pdf01.html
+ http://research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402380/pdf01.html
+ import/pdf01.pdf
+ tmp/1372402380/pdf01.html
+ pdf01.html
+ pdf01.pdf
+ pdf01.pdf
+ PDFPlugin
+ 269487
+ pdf01
+ PDF
+ _iconpdf_
+ doc.pdf
+ doc.pdf
+ 9
+ Acrobat PDFWriter 4.0 for Power Macintosh
+ 1.2
+ Greenstone: A comprehensive open-source digital library software system
+ 644
+ pdf01.pdf
+ /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/import
+ Microsoft Word
+ 269487
+ 2013:06:28 18:27:50+12:00
+ Ian H. Witten
+ Rodger J. McNab
+ Stefan J. Boddie
+ David Bainbridge
+ Bronwyn
+ 9
+ PDF
+ 2000:03:02 15:21:24
+ false
+ 8.57
+ application/pdf
+ HASH1a9cea0f239f754007681b
+ 1372400870
+ 20130628
+ 1372402381
+ 20130628
+ HASH1a9cea0f.dir
+ pdf01-2_1.jpg:image/jpeg:
+ pdf01-3_1.jpg:image/jpeg:
+ pdf01-4_1.jpg:image/jpeg:
+ pdf01-5_1.jpg:image/jpeg:
+ pdf01-7_1.jpg:image/jpeg:
+ pdf01-8_1.jpg:image/jpeg:
+ doc.pdf:application/pdf:
+
+
+<A name=1></a><b>Greenstone: A Comprehensive Open-Source</b><br>
+<b>Digital Library Software System</b><br>
+<i>Ian H. Witten,* Rodger J. McNab,â Stefan J. Boddie,* David Bainbridge*</i><br>
+* Dept of Computer Science<br>
+â Digilib Systems<br>
+University of Waikato, New Zealand<br>
+Hamilton, New Zealand<br>
+E-mail: {ihw, sjboddie, davidb}@cs.waikato.ac.nz<br>
+E-mail: rodger@digilibs.com<br>
+<b>ABSTRACT</b><br>
+multilingual information retrieval to distributed computing<br>protocols, from interoperability to search engine<br>
+This paper describes the Greenstone digital library<br>
+technology, from metadata standards to multiformat<br>
+software, a comprehensive, open-source system for the<br>
+document parsing, from multimedia to multiple operating<br>
+construction and presentation of information collections.<br>
+systems, from Web browsers to plug-and-play DVDs.<br>
+Collections built with Greenstone offer effective full-text<br>searching and metadata-based browsing facilities that are<br>
+The Greenstone Digital Library Software from the New<br>
+attractive and easy to use. Moreover, they are easily<br>
+Zealand Digital Library (NZDL) project tackles this issue<br>
+maintainable and can be augmented and rebuilt entirely<br>
+by providing a new way of organizing information and<br>
+automatically. The system is extensible: software<br>
+making it available over the Internet. A <i>collection</i> of<br>
+âpluginsâ accommodate different document and metadata<br>
+information comprises several (typically several thousand,<br>
+types.<br>
+or several million) <i>documents</i>, and a uniform interface is<br>provided to all documents in a collection. A library may<br>
+<b>INTRODUCTION</b><br>
+include many different collections, each organized<br>differentlyâthough there is a strong family resemblance in<br>
+Notwithstanding intense research activity in the digital<br>
+how collections are presented.<br>
+library field during the second half of the 1990s,<br>comprehensive software systems for creating digital<br>
+Making information available using this system is far more<br>
+libraries are not widely available. In fact, the usual solution<br>
+than âjust putting it on the Web.â The collection becomes<br>
+when creating a digital library is also the most<br>
+maintainable, searchable, and browsable. Each collection,<br>
+obviousâjust put it on the Web. But consider how much<br>
+prior to presentation, undergoes a âbuildingâ process that,<br>
+effort is involved in constructing a Web site for a digital<br>
+once established, is completely automatic. This process<br>
+library. To be effective it needs to be visually attractive<br>
+creates all the structures that are used at run-time for<br>
+and ergonomically easy to use, incorporate convenient and<br>
+accessing the collection. Searching is based on various<br>
+powerful searching capabilities, and offer rich and natural<br>
+indexes, while browsing is based on various metadata;<br>
+browsing facilities. Above all it must be easy to maintain<br>
+support structures for both are created during the building<br>
+and augment, which presents a significant challenge if any<br>
+operation. When new material appears it can be fully<br>
+manual organization is involved.<br>
+incorporated into the collection by rebuilding.<br>
+The alternative is to automate these activities through<br>
+To address the exceptionally broad demands of digital<br>
+software tools. But the broad scope of digital library<br>
+libraries, the system is public and extensible. It is issued<br>
+requirements makes this a daunting prospect. Ideally the<br>
+under the Gnu public license and, in the spirit of open-<br>
+software should incorporate facilities ranging from<br>
+source software, users are invited to contribute<br>modifications and enhancements. Only through an<br>international cooperative effort will digital library software<br>become sufficiently comprehensive to meet the worldâs<br>needs. Currently the Greenstone software is used at sites in<br>Canada, Germany, New Zealand, Romania, UK, and the<br>US, and collections range from newspaper articles to<br>technical documents, from educational journals to oral<br>history, from visual art to folksongs. The software has<br>been used for collections in many different languages, and<br>for CD-ROMs that have been published by the United<br>Nations and other humanitarian agencies in Belgium,<br>France, Japan, and the US for distribution in developing<br>countries (Humanity Libraries, 1998; PAHO, 1999;<br>UNESCO, 1999; UNU, 1998). Further details can be<br>obtained from <i>www.nzdl.org</i>.<br>
+<hr>
+<A name=2></a><IMG src="_httpdocimg_/pdf01-2_1.jpg"><br>
+become a first-class component of the library. And what<br>permits it to be integrated into existing searching and<br>browsing structures without any manual intervention is<br><i>metadata</i>. This provides sufficient focus to the concept of<br>âdigital libraryâ to support the development of a<br>construction kit.<br>
+<b>OVERVIEW OF GREENSTONE</b><br>
+ <br>Information collections built by Greenstone combine<br>extensive full-text search facilities with browsing indexes<br>based on different metadata types. There are several ways<br>for users to find information, although they differ between<br>collections depending on the metadata available and the<br>collection design. Typically you can <i>search for particular<br>words</i> that appear in the text, or within a section of a<br>document, or within a title or section heading. You can<br><i>browse documents by title</i>: just click on the displayed book<br>icon to read it. You can <i>browse documents by subject</i>.<br>Subjects are represented by bookshelves: just click on a<br>shelf to see the books. Where appropriate, documents<br>
+<b>Figure 1: Searching the HDL collection</b><br>
+come complete with a table of contents (constructed<br>automatically): you can click on a chapter or subsection to<br>
+This paper sets the scene with a brief discussion of what a<br>
+open it, expand the full table of contents, or expand the full<br>
+digital library is. We then give an overview of the facilities<br>
+document.<br>
+offered by Greenstone and show how end users find<br>information in collections. Next we describe the files and<br>
+ <br>An example of searching is shown in Figure 1 where<br>
+directories involved in a collection, and then discuss the<br>
+documents in the Global Help Projectâs Humanity<br>
+processes of updating existing collections and creating new<br>
+Development Library (HDL) are being searched for<br>
+ones, including extending the software to provide new<br>
+chapters matching the word <i>butterfly</i>. In Figure 2 the same<br>
+facilities. We conclude with an overview of related work.<br>
+collection is being browsed by subject: by clicking on the<br>bookshelf icons the user has discovered an item under<br>
+<b>WHAT IS A DIGITAL LIBRARY?</b><br>
+Section 16, Animal Husbandry. Pursuing an interest in<br>butterfly farming, the user selects a book by clicking on its<br>
+ <br>Ten definitions of the term âdigital libraryâ have been<br>
+book icon. In Figure 3 the front cover of the book is<br>
+culled from the literature by Fox (1998), and their spirit is<br>
+displayed as a graphic on the left, and the automatically<br>
+captured in the following brief characterization:<br>
+constructed table of contents appears at the start of the<br>
+ <br>
+document. The current focus, <i>Introduction and Summary</i>,<br>
+<i>A collection of digital objects, including text,</i><br>
+is shown in bold in the table of contents with its text<br>
+<i>video, and audio, along with methods for access</i><br>
+starting further down the page.<br>
+<i>and retrieval, and for selection, organization<br>and maintenance of the collection</i><br>
+ <br>In accordance with Leskâs advice, a statement of purpose<br>
+ <br>
+and coverage accompanies each collection, along with an<br>
+(Akscyn and Witten, 1998). Lesk (1998) views digital<br>
+explanation of how it is organized (Figure 1 shows the<br>
+libraries as âorganized collections of digital information,â<br>
+start of this). A distinction is made between <i>searching</i> and<br>
+and wisely recommends that they articulate the principles<br>
+<i>browsing</i>. Searching is full-text, andâdepending on the<br>
+governing what is included and how the collection is<br>
+collectionâs designâthe user can choose between indexes<br>
+organized.<br>
+built from different parts of the documents, or from<br>
+ <br>Digital libraries are generally distinguished from the<br>
+different metadata. Some collections have an index of full<br>
+World-Wide Web, the essential difference being in<br>
+documents, an index of sections, an index of paragraphs,<br>
+selection and organization. But they are not generally<br>
+an index of titles, and an index of section headings, each of<br>
+distinguished from a web <i>site</i>: indeed, virtually all extant<br>
+which can be searched for particular words or phrases.<br>
+digital libraries manifest themselves as a web site. Hence<br>
+Browsing involves data structures created from metadata<br>
+the obvious question: to make a digital library, why not<br>
+that the user can examine: lists of authors, lists of titles,<br>
+just put the information on the Web?<br>
+lists of dates, hierarchical classification structures, and so<br>
+ <br>
+on. Data structures for both browsing and searching are<br>
+But we make a distinction between a digital library and a<br>
+built according to instructions in a configuration file,<br>
+web site that lies at the heart of our software design: one<br>
+which controls both building and serving the collection.<br>
+should easily be able to add new material to a library<br>
+Sample configuration files are discussed below.<br>
+without having to integrate it manually or edit its content<br>in any way. Once added, new material should immediately<br>
+<hr>
+<A name=3></a><IMG src="_httpdocimg_/pdf01-3_1.jpg"><br>
+matter of specifying all the necessary plugins. In order to<br>build browsing indexes from metadata, an analogous<br>scheme of âclassifiersâ is used: classifiers create indexes<br>of various kinds based on metadata. Source documents are<br>brought into the Greenstone system through a process<br>called <i>importing</i>, which uses the plugins and classifiers<br>specified in the collection configuration file.<br>
+ <br>The international Unicode character set is used throughout,<br>so documentsâand interfacesâcan be written in any<br>language. Collections have so far been produced in<br>English, French, Spanish, German, Maori, Chinese, and<br>Arabic. The NZDL Web site provides numerous examples.<br>Collections can contain text, pictures, and even audio and<br>video clips; a text-only version of the interface is also<br>provided to accommodate visually impaired users.<br>Compression technology is used to ensure best use of<br>storage (Witten <i>et al </i>., 1999). Most non-textual material is<br>either linked to textual documents or accompanied by<br>textual descriptions (such as photo captions) to allow full-<br>text searching and browsing. However, the architecture<br>
+<b>Figure 2: Browsing the HDL collection by subject</b><br>
+permits the implementation of plugins and classifiers even<br>for non-textual data.<br>
+ <br>Rich browsing facilities can be provided by manually<br>
+ <br>
+linking parts of documents together and building explicit<br>
+The system includes an âadministrativeâ function whereby<br>
+indexes and tables of contents. However, manually-created<br>
+specified users can examine the composition of all<br>
+linking becomes difficult to maintain, and often falls into<br>
+collections, protect documents so that they can only be<br>
+disrepair when a collection expands. The Greenstone<br>
+accessed by registered users on presentation of a password,<br>
+software takes a different tack: it facilitates <i>maintainability</i><br>
+and so on. Logs of user activity are kept that record all<br>
+by creating all searching and browsing structures<br>
+queries made to every Greenstone collection (though this<br>
+automatically from the documents themselves. No links<br>
+facility can be disabled).<br>
+are inserted by hand. This means that when new<br>
+ <br>Although primarily designed for Internet access over the<br>
+documents in the same format become available, they can<br>
+World-Wide Web, collections can be made available, in<br>
+be added automatically. Indeed, for some collections this is<br>
+precisely the same form, on CD-ROM. In either case they<br>
+done by processes that wake up regularly, scout for new<br>
+are accessed through any Web browser. Greenstone CD-<br>
+material, and rebuild the indexesâall without manual<br>
+ROMs operate on a standalone PC under Windows 3.X,<br>
+intervention.<br>
+95, 98, and NT, and the interaction is identical to accessing<br>
+Collections comprise many documents: thousands, tens of<br>
+the collection on the Webâexcept that response is faster<br>
+thousands, or even millions. Each document may be<br>
+and more predictable. The requirement to operate on early<br>
+hierarchically organized into <i>sections</i> (subsections, sub-<br>
+Windows systems is one that plagues the software design,<br>
+subsections, and so on). Each section comprises one or<br>
+but is crucial for many usersâparticularly those in<br>
+more <i>paragraphs</i>. Metadata such as author, title, date,<br>
+underdeveloped countries seeking access to humanitarian<br>
+keywords, and so on, may be associated with documents,<br>
+aid collections. If the PC is connected to a network<br>
+or with individual sections of documents. This is the raw<br>
+(intranet or Internet), a custom-built Web server provided<br>
+material for indexes. It must either be provided explicitly<br>
+on each CD makes exactly the same information available<br>
+for each document and section (for example, in an<br>
+to others through their standard Web browser. The use of<br>
+accompanying spreadsheet) or be derivable automatically<br>
+compression ensures that the greatest possible volume of<br>
+from the source documents. Metadata is converted to<br>
+information can be packed on to a CD-ROM.<br>
+Dublin Core and stored with the document for internal use.<br>
+ <br>The collection-serving software operates under Unix and<br>
+ <br>In order to accommodate different kinds of source<br>
+Windows NT, and works with standard Web servers. A<br>
+documents, the software is organized so that âpluginsâ can<br>
+flexible process structure allows different collections to be<br>
+be written for new document types. Plugins exist for plain<br>
+served by different computers, yet be presented to the user<br>
+text documents, HTML documents, email documents, and<br>
+in the same way, on the same Web page, as part of the<br>
+bibliographic formats. Word documents are handled by<br>
+same digital library, even as part of the same collection<br>
+saving them as HTML; PostScript ones by applying a<br>
+(McNab and Witten, 1998). Existing collections can be<br>
+preprocessor (Nevill-Manning <i>et al</i>., 1998). Specially<br>
+updated and new ones brought on-line at any time, without<br>
+written plugins also exist for proprietary formats such as<br>
+bringing the system down; the process responsible for the<br>
+that used by the BBC archives department. A collection<br>
+user interface will notice (through periodic polling) when<br>
+may have source documents in different forms: it is just a<br>
+new collections appear and add them to the list presented<br>to the user.<br>
+<hr>
+<A name=4></a><IMG src="_httpdocimg_/pdf01-4_1.jpg"><br>
+<b>FILES IN A COLLECTION</b><br>
+ <br>When a new collection is created or material is added to an<br>existing one, the original source documents are first<br>brought into the system through a process known as<br>âimporting.â This involves converting documents into a<br>simple HTML-like format known as GML (for<br>âGreenstone Markup Languageâ), which includes any<br>metadata associated with the document. Documents are<br>assumed to be in the Unicode UTF-8 code (of which the<br>ASCII characters form a subset).<br>
+ <br><b>Files and directories</b><br>
+ <br>There is a separate directory for each collection, which<br>contains five subdirectories: the original raw material<br>(<i>import</i>), the GML files created from this (<i>archives</i>), the<br>final collection as it is served to users (<i>index</i>), a directory<br>for use during the building process (<i>building</i>), and one for<br>any supporting files (<i>etc</i>)âincluding the configuration file<br>
+<b>Figure 3: Reading a book in the HDL</b><br>
+that controls the collection creation procedure. Additional<br>files might be required: for example, building a hierarchy<br>of classifications requires a data file of sub-classifications.<br>
+<b>FINDING INFORMATION</b><br>
+ <br>Greenstone digital library systems generally include<br>
+ <br>
+several separate collections. A home page allows you to<br>
+<b>The imported documents</b><br>
+select a collection; in addition, each collection has its own<br>
+ <br>In order to identify documents internally, a unique object<br>
+âaboutâ page that gives you information about how the<br>
+identifier or OID is assigned to each original source<br>
+collection is organized and the principles governing what<br>
+document when it is imported (formed by hashing the<br>
+is included.<br>
+content, to overcome file duplication effects caused by<br>
+ <br>All icons in the screenshots of Figures 1â4 are clickable.<br>
+mirroring) and stored as metadata within that document. It<br>
+Those icons at the top of the page return to the home page,<br>
+is important that OIDs persist throughout the index-<br>
+provide help text, and allow you to set user interface and<br>
+building processâso that a userâs search history is<br>
+searching preferences. The navigation bar underneath<br>
+unaffected by rebuilding the collection. OIDs are assigned<br>
+gives access to the searching and browsing facilities,<br>
+by hashing the contents of the original source document.<br>
+which differ from one collection to another.<br>
+ <br>Once imported, each document is stored in its own<br>
+ <br>Each of the five buttons provides a different way to find<br>
+subdirectory of <i>archives</i>, along with any associated<br>
+information. You can <i>search for particular words</i> that<br>
+filesâfor example, images. To ensure compatibility with<br>
+appear in the text from the âsearchâ page (or from the<br>
+Windows 3.0, only eight characters are used in directory<br>
+âaboutâ page of Figure 1). This collection contains indexes<br>
+and file names, which causes annoying but essentially<br>
+of chapters, section titles, and entire books. The default<br>
+trivial complications.<br>
+search interface is a simple one, suitable for casual users;<br>advanced searchingâwhich allows full Boolean<br>
+ <br><b>Inside the documents</b><br>
+expressions, phrase searching, case and stemming<br>controlâcan be enabled from the <i>Preferences</i> page.<br>
+ <br>The GML format imposes a limited amount of structure on<br>
+ <br>
+documents. Documents are divided into paragraphs. They<br>
+This collection has four browsable metadata indexes. You<br>
+can be split hierarchically into sections and subsections.<br>
+can <i>access publications by subject</i> by clicking the <i>subjects</i><br>
+OIDs are extended to identify these components by<br>
+button, which brings up a list of subjects, represented by<br>
+appending numbers, separated by periods, to a documentâs<br>
+bookshelves (Figure 2). You can <i>access publications by</i><br>
+OID. When a book is read, its section hierarchy is visible<br>
+<i>title</i> by clicking <i>titles a-z</i> (Figure 4), which brings up a list<br>
+as the table of contents (Figure 3). Chapters, sections,<br>
+of books in alphabetic order. You can <i>access publications</i><br>
+subsections, and pages are all implemented simply as<br>
+<i>by organization</i> (i.e. Dublin Core âpublisherâ), bringing up<br>
+âsectionsâ within the document. In some collections<br>
+a list of organizations. You can <i>access publications by</i><br>
+documents do not have a hierarchical subsection structure,<br>
+<i>âhow toâ listing</i>, yielding a list of hints defined by the<br>
+but are split into pages to permit browsing within a<br>
+collectionâs editors. We use the Dublin Core as a base and<br>
+retrieved document.<br>
+extend it in an <i>ad hoc</i> manner to accommodate the<br>individual requirements of collection designers.<br>
+ <br>The document structure is used for searchable indexes.<br>There are three levels of index: <i>documents</i>, <i>sections</i>, and<br>
+<hr>
+<A name=5></a><IMG src="_httpdocimg_/pdf01-5_1.jpg"><br>
+the <i>import</i> process is invoked, which converts the files into<br>GML using the specified plugins. Old material for which<br>GML files have previously been created is not re-imported.<br>Then the <i>build</i> process is invoked to build the requisite<br>indexes for the collection. Finally, the contents of the<br><i>building</i> directory are moved into the <i>index</i> directory, and<br>the new version of the collection automatically becomes<br>live.<br>
+ <br>This procedure may seem cumbersome. But all the steps<br>are necessary for efficient operation with large collections.<br>The <i>import</i> process could be performed on the fly during<br>the building operationâbut because building indexes is a<br>multipass operation, the often lengthy importing would be<br>repeated several times. The <i>build</i> process can take<br>considerable timeâa day or two, for very large<br>collections. Consequently, the results are placed in the<br><i>building</i> directory so that, if the collection already exists, it<br>will continue to be served to users in its old form<br>throughout the building operation.<br>
+ <br>Active users of the collection will not be disturbed when<br>the new version becomes liveâthey will probably not<br>
+<b>Figure 4: Browsing titles in the HDL</b><br>
+even notice. The persistent OIDs ensure that interactions<br>remain coherentâusers who are examining the results of a<br>query or browse operation will still retrieve the expected<br>
+<i>paragraphs</i>, corresponding to the distinctions that GML<br>
+documentsâand if a search is actually in progress when<br>
+makesâthe hierarchical structure is flattened for the<br>
+the change takes place the program detects the resulting<br>
+purposes of creating these indexes. Indexes can be of text,<br>
+file-structure inconsistency and automatically and<br>
+or metadata, or any combination. Thus you can create a<br>
+transparently re-executes the query, this time on the new<br>
+searchable index of section titles, and/or authors, and/or<br>
+version of the collection.<br>
+document descriptions, as well as the document text.<br>
+<b>UPDATING EXISTING COLLECTIONS</b><br>
+ <br><b>How it works</b><br>
+ <br>Updating an existing collection with new files in the same<br>
+ <br>The original material in the <i>import</i> directory may be in any<br>
+format is easy. For example, the raw material for the HDL<br>
+format, and plugins are required to process each format<br>
+is supplied in the form of HTML files marked up with<br>
+type. The plugins that a collection uses must be specified<br>
+<<TOC>> tags to split books into sections and<br>
+in the collection configuration file. The <i>import</i> program<br>
+subsections, and <<I>> tags to indicate where an image is<br>
+reads the list of plugins and passes each document to each<br>
+to be inserted. For each book in the library there is a<br>
+plugin in order until it finds one that can process it. When<br>
+directory that contains a single HTML file representing the<br>
+updating an existing collection, all plugins necessary to<br>
+book, and separate files containing the associated images.<br>
+process new material should already have been specified in<br>
+An accompanying spreadsheet file contains the<br>
+the configuration file.<br>
+classification hierarchy; this is converted to a simple file<br>format (using Excelâs <i>Save As</i> command).<br>
+ <br>The building step creates the indexes for both searching<br>and browsing. The MG software is generally used to do the<br>
+ <br>Since the collection exists, its directory is already set up<br>
+searching (Witten <i>et al.</i>, 1999), and the <i>mgbuild</i> module is<br>
+with subdirectories <i>import</i>, <i>archives</i>, <i>building</i>, <i>index</i>, and<br>
+automatically invoked to create each of the indexes that is<br>
+<i>etc</i>, and the <i>etc</i> directory will contain a suitable collection<br>
+required. For example, the Humanity Development Library<br>
+configuration file.<br>
+has three indexes, one for entire books, one for chapters,<br>and one for section titles. Subdirectories of the <i>index</i><br>
+ <br>
+directory are created for each of these indexes.<br>
+<b>The updating procedure</b><br>
+ <br>To update a collection, the new raw material is placed in<br>the <i>import</i> directory, in whatever form it is available. Then<br>
+<hr>
+<A name=6></a>creator<br>
+davidb@cs.waikato.ac.nz<br>
+1<br>
+maintainer<br>
+davidb@cs.waikato.ac.nz<br>
+2<br>
+public<br>
+True<br>
+3<br>4<br>
+indexes<br>
+document:text<br>
+5<br>
+defaultindex<br>
+document:text<br>
+6<br>
+plugins<br>
+GMLPlug TEXTPlug ArcPlug RecPlug<br>
+7<br>8<br>
+classify<br>
+AZList metadata=Title<br>
+9<br>10<br>
+collectionmeta<br>
+collectionname "generic text collection"<br>
+11<br>
+(a)<br>
+collectionmeta<br>
+.document:text "documents"<br>
+12<br>
+creator<br>
+davidb@cs.waikato.ac.nz<br>
+1<br>
+maintainer<br>
+davidb@cs.waikato.ac.nz<br>
+2<br>
+public<br>
+True<br>
+3<br>4<br>
+indexes<br>
+document:text document:From<br>
+5<br>
+defaultindex<br>
+document:text<br>
+6<br>
+plugins<br>
+GMLPlug EMAILPlug ArcPlug RecPlug<br>
+7<br>8<br>
+classify<br>
+AZList metadata=Title<br>
+9<br>
+classify<br>
+DateList<br>
+10<br>11<br>
+collectionmeta<br>
+collectionname "Email messages"<br>
+12<br>
+collectionmeta<br>
+.document:text "documents"<br>
+13<br>
+collectionmeta<br>
+.document:From "email senders"<br>
+14<br>15<br>
+format<br>
+QueryResults \\\\<br>
+16<br>
+(b)<br>
+<td>[link][icon][/link]</td><td>[Title]</td><td>[Author]</td><br>
+17<br>
+<b>Figure 5: Collection configuration files (a) generic, (b) for an email collection</b><br>
+ <br>MG also compresses the text of the collection; and the<br>
+certain circumstances, however, it might be preferable to<br>
+image files are linked into the <i>index</i> subdirectory. Now<br>
+use a standardized format such as XML. This is<br>
+none of the material in the <i>import</i> and <i>archives</i> directories<br>
+straightforward to implementjust write an XML<br>
+is needed to run the collection and can be removed from<br>
+pluginalthough we have not done so ourselves. Given<br>
+the file system (though they would be needed if the<br>
+the transitory nature of the imported data, to date, we have<br>
+collection were rebuilt).<br>
+found GML a satisfactory and beneficial format.<br>
+ <br>Associated with each collection is a database stored in<br>
+<b>CREATING NEW COLLECTIONS</b><br>
+GDBM (Gnu database manager) format. This contains an<br>entry for each document, giving its OID, its internal MG<br>
+ <br>Building new collections from scratch is only slightly<br>
+document number, and metadata such as title. Information<br>
+different from updating an existing collection. The key<br>
+for each of the browsing indexes, which appear as buttons<br>
+new requirement is creating a collection configuration file,<br>
+on the Greenstone search/browse bar, is also extracted<br>
+and a software utility is provided to help. Two pieces of<br>
+during the building process and stored in the database. A<br>
+information are required for this: the name of the directory<br>
+âclassifierâ program is required for each browsing index to<br>
+that the collection will use (into which the source data and<br>
+extract the appropriate information from GML documents.<br>
+other files will eventually be placed), and a contact e-mail<br>
+Like plugins, classifiers are written on an <i>ad hoc</i> basis for<br>
+address for use if any problems are encountered by the<br>
+the particular information required, and where possible<br>
+software once the collection is up and running. The utility<br>
+reused from one collection to another.<br>
+creates files and directories within the newly-named<br>
+ <br>
+directory to support a generic collection of plain text<br>
+The building program creates the indexes based on<br>
+documents. With suitable data placed in the <i>import</i><br>
+whatever appears in the <i>archives</i> directory. The first plugin<br>
+directory, building the collection at this point will yield a<br>
+specified by all collections is one that processes GML<br>
+document-level searchable index of all the text and a<br>
+files, and so if <i>archives</i> contains imported files they will be<br>
+browsable list of âtitlesâ (defined in this case to be the<br>
+processed correctly. If it contains material in the original<br>
+document filenames).<br>
+format, that will be converted using the appropriate plugin.<br>Thus the import process is optional.<br>
+ <br>To enhance the functionality and presentationâ something<br>
+ <br>
+anything but the most trivial collection will requireâthe<br>
+GML is designed to be fast and easy to parse, an important<br>
+configuration file must be edited. For a collection sourced<br>
+requirement when millions of documents are to be<br>
+from documents in an already supported data format,<br>
+processed. Something as simple as requiring tags to be<br>
+presented in a similar fashion to an existing collection, the<br>
+lower-case, for example, yields a substantial speed-up. In<br>
+<hr>
+<A name=7></a><IMG src="_httpdocimg_/pdf01-7_1.jpg"><br>
+ <br>These are modules of code that can be slotted into the<br>system to enhance its capabilities. Plugins parse<br>documents, extracting the text and metadata to be indexed.<br>Classifiers control how metadata is brought together to<br>form browsable data structures. Both are specified in an<br>object-oriented framework using inheritance to minimize<br>the amount of code written.<br>
+ <br>A plugin must specify three things: what file formats it can<br>handle, how they should be parsed, and whether the plugin<br>is recursive. File formats are normally determined using<br>regular expression matching on the filename. For example,<br>the HTML plugin accepts all files that end in <i>.htm</i>, . <i>html</i>,<br><i>.HTM</i>, or <i>.HTML</i>. (It is quite possible, however, to write<br>plugins that âlook insideâ the file as well.) For other files,<br>the plugin returns <i>undefined</i> and the file is passed to the<br>next plugin in the collectionâs configuration file (e.g.<br>Figure 5 line 7). If it can, the plugin parses the file and<br>returns the number of documents processed. This involves<br>extracting text and metadata and adding it to the libraryâs<br>content through calls to <i>add text</i> and <i>add metadata</i>.<br>
+ <br>Some plugins (ârecursiveâ ones) add extra files into the<br>
+<b>Figure 6: Searching bookmarked Web pages</b><br>
+stream of data processed during the building phase by<br>artificially reactivating the list of plugins. This is how<br>directory hierarchies are traversed.<br>
+amount of editing is minimal. Importing new data formats<br>and browsing metadata in ways not currently supported are<br>
+ <br>Plugins are small modules of code that are easy to write.<br>
+more complex activities that require programming skills.<br>
+We monitored the time it took to develop a new one that<br>was different to any we had produced so far. We chose to<br>make as an example a collection of HTML bookmark files,<br>
+ <br><b>Modifying the configuration file</b><br>
+the motivation being to produce a convenient way of<br>
+ <br>
+searching and browsing oneâs bookmarked Web pages.<br>
+Figure 5b shows simple alterations to the generic<br>
+Figure 6 shows a user searching for bookmarked pages<br>
+configuration file in Figure 5a that was generated by the<br>
+about <i>music</i>. The new plugin took under an hour to write,<br>
+new-collection utility. <i>TEXTPlug</i> is replaced with<br>
+and was 160 lines long (ignoring blank lines and<br>
+<i>EMAILPlug</i> (line 7) which reads email files and extracts<br>
+comments)âabout the average length of existing plugins.<br>
+metadata (<i>From</i>, <i>To</i>, <i>Date</i>, <i>Subject</i>) from them. A classifier<br>for dates is added (line 10) to make the collection<br>
+ <br>Classifiers are more general than plugins because they<br>
+browsable chronologically. The default presentation of<br>
+work on GML-format data. For example, any plugin that<br>
+search results is overridden (line 17) to display both the<br>
+generates date metadata in accordance with the Dublin<br>
+title of the message (i.e. Dublin Core <i>Title</i>) and its sender<br>
+core can request the collection to be browsable<br>
+(i.e. Dublin Core <i>Author</i>). Elements in square brackets,<br>
+chronologically by specifying the <i>DateList</i> classifier in the<br>
+such as <i>[Title]</i>, are replaced by the metadata associated<br>
+collectionâs configuration file (Figure 7). Classifiers are<br>
+with a particular document. The built-in term <i>[icon]</i><br>
+more elaborate than most plugins, but new ones are seldom<br>
+produces a suitable image that represents the document<br>
+required. The average length of existing classifiers is 230<br>
+(such as a book icon or page icon), and the <i>[link]âŠ[/link]</i><br>
+lines.<br>
+construct forms a hyperlink to the complete document.<br>
+ <br>
+Anything else in the format statement, which in this case is<br>
+Classifiers must specify three things: an initialization<br>
+solely table-cell tags in HTML, is passed through to the<br>
+routine, how individual documents are classified, and the<br>
+page being displayed.<br>
+final browsable data structure. Initialization takes care of<br>any options specified in the configuration file (such as<br>
+As this example shows, creating a new collection that stays<br>
+<i>metadata=Title </i>on line 9 of Figure 5b). Classifying<br>
+within the bounds of the libraryâs established capabilities<br>
+individual documents is an iterative process: for each one,<br>
+falls within the capability of many computer usersâfor<br>
+a call to <i>document-classify</i> is made. On presentation of the<br>
+instance, computer-trained librarians. Extending<br>
+documentâs OID, the necessary metadata is located and<br>
+Greenstone to handle new document formats and browse<br>
+used to control where the document is added to the<br>
+metadata in new ways is more challenging.<br>
+browsable data structure being constructed.<br>
+ <br>Once all documents have been added, a request is made for<br>
+ <br><b>Writing new plugins and classifiers</b><br>
+the completed data structure. Some classifiers return the<br>data structure directly; others transform the data structure<br>
+ <br>Extensibility is obtained through plugins and classifiers.<br>
+before it is returned. For example, the <i>AZList</i> classifier<br>
+<hr>
+<A name=8></a><IMG src="_httpdocimg_/pdf01-8_1.jpg"><br>
+a page number, next and previous page buttons, and<br>displaying a particular page at different resolutions. A text<br>version of the page is also available upon which a<br>searching option is also provided.<br>
+Started in 1994, Harvest is also a long-running research<br>project. It provides an efficient means of gathering source<br>data from the Internet and distributing indexing<br>information over the Internet. This is accomplished<br>through five components: <i>gatherer</i>, <i>broker</i>, <i>indexer</i>,<br><i>replicator</i> and <i>cache</i>. The first three are central to creating,<br>updating and searching a collection; the last two help to<br>improve performance over the Internet through transparent<br>mirroring and caching techniques.<br>
+The system is configurable and customizable. While<br>searching is most commonly implemented using Glimpse<br>(<i>glimpse.cs.arizona.edu</i>), in principle any search engine<br>that supports incremental updates and Boolean<br>combinations of attribute-based queries can be used. It is<br>possible to control what type of documents are gathered<br>during creation and updating, and how the query interface<br>
+<b>Figure 7: Browsing a newspaper collection by date</b><br>
+looks and is laid out.<br>
+Sample collections cited by the developers include 21,000<br>
+divides the alphabetically sorted list of metadata into<br>
+computer science technical reports and 7,000 home pages.<br>
+separate pages of about the same size and returns the<br>
+Other examples include a sizable collection of agriculture-<br>
+alphabetic ranges for each one (Figure 4).<br>
+related electronic journals and magazines called âtomato-<br>juiceâ (accessed through <i>hegel.lib.ncsu.edu</i>) and a full-text<br>
+<b>OVERVIEW OF RELATED WORK</b><br>
+index of library-related electronic serials<br>
+Two projects that provide substantial open source digital<br>
+(<i>sunsite.berkeley.edu/IndexMorganagus</i>). Harvest is also<br>
+library software are Dienst (Lagoze and Fielding, 1998)<br>
+often used to index Web sites (for example<br>
+and Harvest (Bowman <i>et al.</i>, 1994). The origins of Dienst<br>
+<i>www.middlebury.edu</i>).<br>
+(<i>www.cs.cornell.edu/cdlrg</i>) stretch back to 1992. The term<br>
+Comparing Greenstone with Dienst and Harvest, there are<br>
+has come to represent three entities: a conceptual<br>
+both similarities and differences. All provide substantial<br>
+architecture for distributed digital libraries; an open<br>
+digital library systems, hence common themes recur, but<br>
+protocol for service communication; and a software<br>
+they are driven by projects with different aims. Harvest,<br>
+system that implements the protocol. To date, five sample<br>
+for instance, was not conceived as a digital library project<br>
+digital libraries have been built using this technology.<br>
+at all, but by virtue of its selective document gathering<br>
+They manifest themselves in two forms: technical reports<br>
+process it can be classed (and is used) as one. While it<br>
+and primary source documents.<br>
+provides sophisticated search options, it lacks the<br>
+Best known is NCSTRL, the Networked Computer<br>
+complementary service of browsing. Furthermore it adds<br>
+Science Technical Reference Library project<br>
+no structure or order to the documents collected, relying<br>
+(<i>www.ncstrl.org</i>). This collection facilitates searching by<br>
+on whatever structures are present in the site that they<br>
+title, author and abstract, and browsing by year and author,<br>
+were gathered from. A proven strength of the design is its<br>
+across a distributed network of document repositories.<br>
+flexibility through configuration and customizationan<br>
+Documents can (where supported) be delivered in various<br>
+element also present in Greenstone.<br>
+formats such as PostScript, a thumbnail overview of the<br>
+Dienstbest exemplified through the NCSTRL<br>
+pages, and a GIF image of a particular page.<br>
+worksupports searching and browsing, like Greenstone.<br>
+The <i>Making of America</i> resource is an example of a<br>
+Both use open protocols. Differences include a high<br>
+collection based around primary sourcesin this case<br>
+reliance in Dienst on user-supplied information when a<br>
+American social history, 1830â1900. It has a different<br>
+document is added, and a smaller range of document types<br>
+âlook and feelâ to NCSTRL, being strongly oriented<br>
+supportedâalthough Dienst does include a document<br>
+toward browsing rather than searching. A user navigates<br>
+model that should, over time, allow this to expand with<br>
+their way through a hierarchical structure of hyperlinks to<br>
+relative ease.<br>
+reach a book of interest. The book itself is a series of<br>
+There are also commercial systems that provide similar<br>
+scanned images: delivery options include going directly to<br>
+digital library services to those described. However, since<br>
+<hr>
+<A name=9></a>corporate culture instills proprietary attitudes there is little<br>
+<b>REFERENCES</b><br>
+opportunity for advancement through a shared<br>
+1. Akscyn, R.M. and Witten, I.H. (1998) âReport on First<br>
+collaborative effort. Consequently they are not reviewed<br>
+Summit on International Cooperation on Digital<br>
+here.<br>
+Libraries.â ks.com/idla-wp-oct98.<br>
+2. Bowman, C.M., Danzig, P.B., Manber, U., and<br>
+<b>CONCLUSIONS</b><br>
+Schwartz, M.F. âScalable Internet resource discovery:<br>
+Greenstone is a comprehensive software system for<br>
+Research problems and approachesâ <i>Communications</i><br>
+creating digital library collections. It builds data structures<br>
+<i>of the ACM,</i> Vol. 37, No. 8, pp. 98â107, 1994.<br>
+for searching and browsing from the material provided,<br>
+3. Fox, E. (1998) âDigital library definitions.â<br>
+rather than relying on any hand-crafting. The process is<br>
+ei.cs.vt.edu/~fox/dlib/def.html.<br>
+controlled by a configuration file, and once a collection<br>exists new material can be added completely<br>
+4. Humanity Libraries (1998) <i>Humanity Development</i><br>
+automatically. Browsing is based on Dublin Core<br>
+<i>Library</i>. CD-ROM produced by the Global Help<br>
+metadata.<br>
+Project, Antwerp, Belgium.<br>
+New collections can be developed easily, particularly if<br>
+5. Lagoze, C. and Fielding, D âDefining Collections in<br>
+they resemble existing ones. Extensibility is achieved<br>
+Distributed Digital Librariesâ <i>D-Lib Magazine</i>, Nov.<br>
+through software âpluginsâ that can be written to<br>
+1998.<br>
+accommodate documents, and metadata, in different<br>
+6. PAHO (1999) <i>Virtual Disaster Library</i>. CD-ROM<br>
+formats. Standard plugins exist for many document types;<br>
+produced by the Pan-American Health Organization,<br>
+new ones are easily written. Browsing is controlled by<br>
+Washington DC, USA.<br>
+âclassifiersâ that process metadata into browsing structures<br>
+7. McNab, R.J., Witten, I.H. and Boddie, S.J. (1998) âA<br>
+(by date, alphabetical, hierarchical, etc).<br>
+distributed digital library architecture incorporating<br>
+However, the most powerful support for extensibility is<br>
+different index styles.â <i>Proc IEEE Advances in Digital</i><br>
+achieved not by technical means but by making the source<br>
+<i>Libraries</i>, Santa Barbara, CA, pp. 36â45.<br>
+code freely available under the Gnu public license. Only<br>
+8. Nevill-Manning, C.G., Reed, T., and Witten, I.H.<br>
+through an international cooperative effort will digital<br>
+(1998) âExtracting text from PostScriptâ<br>
+library software become sufficiently comprehensive to<br>
+<i>SoftwareâPractice and Experience</i>, Vol. 28, No. 5, pp.<br>
+meet the worldâs needs with the richness and flexibility<br>
+481â491; April.<br>
+that users deserve.<br>
+9. UNESCO (1999) <i>SAHEL point DOC: Anthologie du</i><br>
+<b>ACKNOWLEDGMENTS</b><br>
+<i>développement au Sahel</i>. CD-ROM produced by<br>UNESCO, Paris, France.<br>
+We gratefully acknowledge all those who have worked on<br>the Greenstone software, and all members of the New<br>
+10. UNU (1998) <i>Collection on critical global issues.</i> CD-<br>
+Zealand Digital Library project for their enthusiasm and<br>
+ROM produced by the United Nations University<br>
+ideas.<br>
+Press, Tokyo, Japan.<br>
+11. Witten, I.H., Moffat, A. and Bell, T. (1999) <i>Managing</i><br>
+<i>Gigabytes: compressing and indexing documents and<br>images</i>, Morgan Kaufmann, second edition.<br>
+<hr>
+
+
+
+
+
Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/HASH8bbe6da0.dir/doc.xml
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/HASH8bbe6da0.dir/doc.xml (revision 27727)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/HASH8bbe6da0.dir/doc.xml (revision 27727)
@@ -0,0 +1,90 @@
+
+
+
+
+
+ indexed_doc
+ en
+ utf8
+ Bronwyn; page: 1 of 1 1 Using language models for generic entity extraction
+ import/langmodl.ps
+ tmp/1372402380/langmodl.text
+ langmodl.text
+ langmodl.ps
+ langmodl.ps
+ PostScriptPlugin
+ 16751
+ langmodl
+ PS
+ _iconps_
+ doc.ps
+ doc.ps
+ Ian H. Witten
+ Zane Bray
+ Malika Mahoui
+ W.J. Teahan
+ HASH8bbe6da0374b413b1b355c
+ 1372400870
+ 20130628
+ 1372402380
+ 20130628
+ HASH8bbe6da0.dir
+ doc.ps:application/postscript:
+
+ <pre>
+Bronwyn; page: 1 of 1 1 Using language models for generic entity extraction
+Ian H. Witten, Zane Bray, Malika Mahoui, W.J. Teahan Computer ScienceUniversity
+of WaikatoHamilton, New Zealandihw@cs.waikato.ac.nz AbstractThis paper describes
+the use of statisticallanguage modeling techniques, such as arecommonly used
+for text compression, to extractmeaningful, low-level, information about
+thelocation of semantic tokens, or \\322entities,\\323 in text.We begin by
+marking up several different tokentypes in training documents\\321for example,people\\325s
+names, dates and time periods, phonenumbers, and sums of money. We form alanguage
+model for each token type and examinehow accurately it identifies new tokens.
+We thenapply a search algorithm to insert tokenboundaries in a way that maximizes
+compressionof the entire test document. The technique can beapplied to hierarchically-defined
+tokens, leadingto a kind of \\322soft parsing\\323 that will, we believe,be
+able to identify structured items such asreferences and tables in html or
+plain text, basedon nothing more than a few marked-up examplesin training
+documents. 1. INTRODUCTIONText mining is about looking for patterns in
+text, and maybe defined as the process of analyzing text to extractinformation
+that is useful for particular purposes.Compared with the kind of data stored
+in databases, textis unstructured, amorphous, and difficult to deal with.Nevertheless,
+in modern Western culture, text is the mostcommon vehicle for the formal
+exchange of information.The motivation for trying to extract information
+from it iscompelling\\321even if success is only partial.Text mining is possible
+because you do not have tounderstand text in order to extract useful information
+fromit. Here are four examples. First, if only names could beidentified,
+links could be inserted automatically to otherplaces that mention the same
+name\\321links that are\\322dynamically evaluated\\323 by calling upon a search
+engineto bind them at click time. Second, actions can beassociated with different
+types of data, using eitherexplicit programming or programming-by-demonstrationtechniques.
+A day/time specification appearing anywherewithin one\\325s email could be
+associated with diary actionssuch as updating a personal organizer or creating
+anautomatic reminder, and each mention of a day/time in thetext could raise
+a popup menu of calendar-based actions.Third, text could be mined for data
+in tabular format,allowing databases to be created from formatted tablessuch
+as stock-market information on Web pages. Fourth,an agent could monitor incoming
+newswire stories forcompany names and collect documents that mentionthem\\321an
+automated press clipping service.In all these examples, the key problem is
+to recognizedifferent types of target fragments, which we will calltokens
+or \\322entities\\323. This is really a kind of languagerecognition problem:
+we have a text made up of differentsublanguages {for personal names, company
+names, dates,table entries, and so on} and seek to determine whichparts are
+expressed in which language.The information extraction research community
+{of whichwe were, until recently, unaware} has studied these tasksand reported
+results at annual Message UnderstandingConferences {MUC}. For example, \\322named
+entities\\323 aredefined as proper names and quantities of interest,including
+personal, organization, and location names, aswell as dates, times, percentages,
+and monetary amounts{Chinchor, 1999}.The standard approach to this problem
+is manual:tokenizers and grammars are hand-designed for theparticular data
+being extracted. Looking at currentcommercial state-of-the-art text mining
+software, forexample, IBM\\325s Intelligent Miner for Text {Tkach, 1997}uses
+specific recognition modules carefully programmedfor the different data types,
+while Apple\\325s data detectors{Nardi et al., 1998} uses language grammars.
+The TextTokenization Tool of Grover et al. {1999} is anotherexample, and
+a demonstration version is available on theWeb. The challenge for machine
+learning is to use
+</pre>
+
+
Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/HASHeaa2992e.dir/doc.xml
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/HASHeaa2992e.dir/doc.xml (revision 27727)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/HASHeaa2992e.dir/doc.xml (revision 27727)
@@ -0,0 +1,4289 @@
+
+
+
+
+
+ indexed_doc
+ en
+ utf8
+ wvWare/wvWare version 1.2.4
+ 1997-00 Listing of Working Papers
+ http://research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402381/word01.html
+ http://research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402381/word01.html
+ import/word01.doc
+ tmp/1372402381/word01.html
+ word01.html
+ word01.doc
+ word01.doc
+ WordPlugin
+ 110080
+ word01
+ Word
+ _icondoc_
+ doc.doc
+ doc.doc
+ HASHeaa2992e081949673150f3
+ 1372400870
+ 20130628
+ 1372402382
+ 20130628
+ HASHeaa2992e.dir
+ doc.doc:application/msword:
+
+
+
+<!--Section Begins--><br>
+
+
+
+<p><div name="Title" align="center" style="margin: 0.00mm -0.12mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>1997-00 Listing of Working Papers </b>
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+2000/1
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Using compression to identify acronyms in text
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Stuart Yeates, David Bainbridge, Ian H. Witten
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Text mining is about looking for patterns in natural language text, and may be defined as the process of analyzing text to extract information from it for particular purposes. In previous work, we claimed that compression is a key technology for text mining, and backed this up with a study that showed how particular kinds of lexical tokens—names, dates, locations, <i>etc.</i>—can be identified and located in running text, using compression models to provide the leverage necessary to distinguish different token types (Witten <i>et al.</i>, 1999)
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+2000/2
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Text categorization using compression models
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Eibe Frank, Chang Chui, Ian H. Witten
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Text categorization, or the assignment of natural language texts to predefined categories based on their content, is of growing importance as the volume of information available on the internet continues to overwhelm us. The use of predefined categories implies a “supervised learning” approach to categorization, where already-classified articles - which effectively define the categories - are used as “training data” to build a model that can be used for classifying new articles that comprise the “test data”. This contrasts with “unsupervised” learning, where there is no training data and clusters of like documents are sought amongst the test articles. With supervised learning, meaningful labels (such as keyphrases) are attached to the training documents, and appropriate labels can be assigned automatically to test documents depending on which category they fall into.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+2000/3
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Reserved for Sally Jo
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+2000/4
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Interactive machine learning—letting users build classifiers
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Malcolm Ware, Eibe Frank, Geoffrey Holmes, Mark Hall, Ian H. Witten
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+According to standard procedure, building a classifier is a fully automated process that follows data preparation by a domain expert. In contrast, <I>interactive</I>machine learning engages users in actually generating the classifier themselves. This offers a natural way of integrating background knowledge into the modeling stage—so long as interactive tools can be designed that support efficient and effective communication. This paper shows that appropriate techniques can empower users to create models that compete with classifiers built by state-of-the-art learning algorithms. It demonstrates that users—even users who are not domain experts—can often construct good classifiers, without any help from a learning algorithm, using a simple two-dimensional visual interface. Experiments demonstrate that, not surprisingly, success hinges on the domain: if a few attributes can support good predictions, users generate accurate classifiers, whereas domains with many high-order attribute interactions favor standard machine learning techniques. The future challenge is to achieve a symbiosis between human user and machine learning algorithm.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+2000/5
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+KEA: Practical automatic keyphrase extraction
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Ian H. Witten, Gordon W. Paynter, Eibe Frank, Carl Gutwin, Craig G. Nevill-Manning
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Keyphrases provide semantic metadata that summarize and characterize documents. This paper describes Kea, an algorithm for automatically extracting keyphrases from text. Kea identifies candidate keyphrases using lexical methods, calculates feature values for each candidate, and uses a machine learning algorithm to predict which candidates are good keyphrases. The machine learning scheme first builds a prediction model using training documents with known keyphrases, and then uses the model to find keyphrases in new documents. We use a large test corpus to evaluate Kea's effectiveness in terms of how many author-assigned keyphrases are correctly identified. The system is simple, robust, and publicly available.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+2000/6
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<i>Ό</i>-Charts and Z: hows, whys and wherefores
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Greg Reeve, Steve Reeves
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+In this paper we show, by a series of examples, how the <i>Ό</i>-chart formalism can be translated into Z. We give reasons for why this is an interesting and sensible thing to do and what it might be used for.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+2000/7
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+One dimensional non-uniform rational B-splines for animation control
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Abdelaziz Mahoui
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Most 3D animation packages use graphical representations called motion graphs to represent the variation in time of the motion parameters. Many use two-dimensional B-splines as animation curves because of their power to represent free-form curves. In this project, we investigate the possibility of using One-dimensional Non-Uniform Rational B-Spline (NURBS) curves for the interactive construction of animation control curves. One-dimensional NURBS curves present the potential of solving some problems encountered in motion graphs when two-dimensional B-splines are used. The study focuses on the properties of One-dimensional NURBS mathematical model. It also investigates the algorithms and shape modification tools devised for two-dimensional curves and their port to the One-dimensional NURBS model. It also looks at the issues related to the user interface used to interactively modify the shape of the curves.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+2000/8
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Correlation-based feature selection of discrete and numeric class machine learning
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Mark A. Hall
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Algorithms for feature selection fall into two broad categories: <I>wrappers</I>that use the learning algorithm itself to evaluate the usefulness of features and <I>filters</I>that evaluate features according to heuristics based on general characteristics of the data. For application to large databases, filters have proven to be more practical than wrappers because they are much faster. However, most existing filter algorithms only work with discrete classification problems. This paper describes a fast, correlation-based filter algorithm that can be applied to continuous and discrete problems. The algorithm often out-performs the well-known ReliefF attribute estimator when used as a preprocessing step for naïve Bayes, instance-based learning, decision trees, locally weighted regression, and model trees. It performs more feature selection than ReliefF does-reducing the data dimensionality by fifty percent in most cases. Also, decision and model trees built from the prepocessed data are often significantly smaller.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+2000/9
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+A development environment for predictive modelling in foods
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+G. Holmes, M.A. Hall
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+WEKA (Waikato Environment for Knowledge Analysis) is a comprehensive suite of Java class libraries that implement many state-of-the-art machine learning/data mining algorithms. Non-programmers interact with the software via a user interface component called the Knowledge Explorer.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Applications constructed from the WEKA class libraries can be run on any computer with a web browsing capability, allowing users to apply machine learning techniques to their own data regardless of computer platform. This paper describes the user interface component of the WEKA system in reference to previous applications in the predictive modeling of foods.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+2000/10
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Benchmarking attribute selection techniques for data mining
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Mark A. Hall, Geoffrey Holmes
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Data engineering is generally considered to be a central issue in the development of data mining applications. The success of many learning schemes, in their attempts to construct models of data, hinges on the reliable identification of a small set of highly predictive attributes. The inclusion of irrelevant, redundant and noisy attributes in the model building process phase can result in poor predictive performance and increased computation.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Attribute selection generally involves a combination of search and attribute utility estimation plus evaluation with respect to specific learning schemes. This leads to a large number of possible permutations and has led to a situation where very few benchmark studies have been conducted.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+This paper presents a benchmark comparison of several attribute selection methods. All the methods produce an attribute ranking, a useful devise of isolating the individual merit of an attribute. Attribute selection is achieved by cross-validating the rankings with respect to a learning scheme to find the best attributes. Results are reported for a selection of standard data sets and two learning schemes C4.5 and naïve Bayes.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+2000/11
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Steve Reeves, Greg Reeve
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+2000/12
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Malika Mahoui, Sally Jo Cunningham
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Transaction logs are invaluable sources of fine-grained information about users' search behavior. This paper compares the searching behavior of users across two WWW-accessible digital libraries: the New Zealand Digital Library's Computer Science Technical Reports collection (CSTR), and the Karlsruhe Computer Science Bibliographies (CSBIB) collection. Since the two collections are designed to support the same type of users-researchers/students in computer science a comparative log analysis is likely to uncover common searching preferences for that user group. The two collections differ in their content, however; the CSTR indexes a full text collection, while the CSBIB is primarily a bibliographic database. Differences in searching behavior between the two systems may indicate the effect of differing search facilities and content type.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+99/1
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Lexical attraction for text compression
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Joscha Bach, Ian H. Witten
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+New methods of acquiring structural information in text documents may support better compression by identifying an appropriate prediction context for each symbol. The method of “lexical attraction” infers syntactic dependency structures from statistical analysis of large corpora. We describe the generation of a lexical attraction model, discuss its application to text compression, and explore its potential to outperform fixed-context models such as word-level PPM. Perhaps the most exciting aspect of this work is the prospect of using compression as a metric for structure discovery in text.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+99/2
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Generating rule sets from model trees
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Geoffrey Holmes, Mark Hall, Eibe Frank
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Knowledge discovered in a database must be represented in a form that is easy to understand. Small, easy to interpret nuggets of knowledge from data are one requirement and the ability to induce them from a variety of data sources is a second. The literature is abound with classification algorithms, and in recent years with algorithms for time sequence analysis, but relatively little has been published on extracting meaningful information from problems involving continuous classes (regression).
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Model trees-decision trees with linear models at the leaf nodes-have recently emerged as an accurate method for numeric prediction that produces understandable models. However, it is well known that decision lists-ordered sets of If-Then rules-have the potential to be more compact and therefore more understandable than their tree counterparts.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+In this paper we present an algorithm for inducing simple, yet accurate rule sets from model trees. The algorithm works by repeatedly building model trees and selecting the best rule at each iteration. It produces rule sets that are, on the whole, as accurate but smaller than the model tree constructed from the entire dataset. Experimental results for various heuristics which attempt to find a compromise between rule accuracy and rule coverage are reported. We also show empirically that our method produces more accurate and smaller rule sets than the commercial state-of-the-art rule learning system Cubist.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+99/3
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+A diagnostic tool for tree based supervised classification learning algorithms
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Leonard Trigg, Geoffrey Holmes
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The process of developing applications of machine learning and data mining that employ supervised classification algorithms includes the important step of knowledge verification. Interpretable output is presented to a user so that they can verify that the knowledge contained in the output makes sense for the given application. As the development of an application is an iterative process it is quite likely that a user would wish to compare models constructed at various times or stages.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+One crucial stage where comparison of models is important is when the accuracy of a model is being estimated, typically using some form of cross-validation. This stage is used to establish an estimate of how well a model will perform on unseen data. This is vital information to present to a user, but it is also important to show the degree of variation between models obtained from the entire dataset and models obtained during cross-validation. In this way it can be verified that the cross-validation models are at least structurally aligned with the model garnered from the entire dataset.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+This paper presents a diagnostic tool for the comparison of tree-based supervised classification models. The method is adapted from work on approximate tree matching and applied to decision trees. The tool is described together with experimental results on standard datasets.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+99/4
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Feature selection for discrete and numeric class machine learning
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Mark A. Hall
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Algorithms for feature selection fall into two broad categories: <I>wrappers</I>use the learning algorithm itself to evaluate the usefulness of features, while <I>filters</I>evaluate features according to heuristics based on general characteristics of the data. For application to large databases, filters have proven to be more practical than wrappers because they are much faster. However, most existing filter algorithms only work with discrete classification problems.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+This paper describes a fast, correlation-based filter algorithm that can be applied to continuous and discrete problems. Experiments using the new method as a preprocessing step for naïve Bayes, instance-based learning, decision trees, locally weighted regression, and model trees show it to be an effective feature selector- it reduces the data in dimensionality by more than sixty percent in most cases without negatively affecting accuracy. Also, decision and model trees built from the pre-processed data are often significantly smaller.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+99/5
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Browsing tree structures
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Mark Apperley, Robert Spence, Stephen Hodge, Michael Chester
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Graphic representations of tree structures are notoriously difficult to create, display, and interpret, particularly when the volume of information they contain, and hence the number of nodes, is large. The problem of interactively browsing information held in tree structures is examined, and the implementation of an innovative tree browser described. This browser is based on distortion-oriented display techniques and intuitive direct manipulation interaction. The tree layout is automatically generated, but the location and extent of detail shown is controlled by the user. It is suggested that these techniques could be extended to the browsing of more general networks.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+99/6
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Facilitating multiple copy/past operations
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Mark Apperley, Jay Baker, Dale Fletcher, Bill Rogers
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Copy and paste, or cut and paste, using a clipboard or paste buffer has long been the principle facility provided to users for transferring data between and within GUI applications. We argue that this mechanism can be clumsy in circumstances where several pieces of information must be moved systematically. In two situations - extraction of data fields from unstructured data found in a directed search process, and reorganisation of computer program source text - we present alternative, more natural, user interface facilities to make the task less onerous, and to provide improved visual feedback during the operation.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+For the data extraction task we introduce the Stretchable Selection Tool, a semi-transparent overlay augmenting the mouse pointer to automate paste operations and provide information to prompt the user. We describe a prototype implementation that functions in a collaborative software environment, allowing users to cooperate on a multiple copy/paste operation. For text reorganisation, we present an extension to Emacs, providing similar functionality, but without the collaborative features.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+99/7
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Automating iterative tasks with programming by demonstration: a user evaluation
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Gordon W. Paynter, Ian H. Witten
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Computer users often face iterative tasks that cannot be automated using the tools and aggregation techniques provided by their application program: they end up performing the iteration by hand, repeating user interface actions over and over again. We have implemented an agent, called Familiar, that can be taught to perform iterative tasks using programming by demonstration (PBD). Unlike other PBD systems, it is domain independent and works with unmodified, widely-used, applications in a popular operating system. In a formal evaluation, we found that users quickly learned to use the agent to automate iterative tasks. Generally, the participants preferred to use multiple selection where possible, but could and did use PBD in situations involving iteration over many commands, or when other techniques were unavailable.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+99/8
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+A survey of software requirements specification practices in the New Zealand software industry
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Lindsay Groves, Ray Nickson, Greg Reeve, Steve Reeves, Mark Utting
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+We report on the software development techniques used in the New Zealand software industry, paying particular attention to requirements gathering. We surveyed a selection of software companies with a general questionnaire and then conducted in-depth interviews with four companies. Our results show a wide variety in the kinds of companies undertaking software development, employing a wide range of software development techniques. Although our data are not sufficiently detailed to draw statistically significant conclusions, it appears that larger software development groups typically have more well-defined software development processes, spend proportionally more time on requirements gathering, and follow more rigorous testing regimes.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+99/9
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The LRU*WWW proxy cache document replacement algorithm
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Chung-yi Chang, Tony McGregor, Geoffrey Holmes
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Obtaining good performance from WWW proxy caches is critically dependent on the document replacement policy used by the proxy. This paper validates the work of other authors by reproducing their studies of proxy cache document replacement algorithms. From this basis a cross-trace study is mounted. This demonstrates that the performance of most document replacement algorithms is dependent on the type of workload that they are presented with. Finally we propose a new algorithm, LRU*, that consistently performs well across all our traces.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+99/10
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Reduced-error pruning with significance tests
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Eibe Frank, Ian H. Witten
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+When building classification models, it is common practice to prune them to counter spurious effects of the training data: this often improves performance and reduces model size. "Reduced-error pruning" is a fast pruning procedure for decision trees that is known to produce small and accurate trees. Apart from the data from which the tree is grown, it uses an independent "pruning" set, and pruning decisions are based on the model's error rate on this fresh data. Recently it has been observed that reduced-error pruning overfits the pruning data, producing unnecessarily large decision trees. This paper investigates whether standard statistical significance tests can be used to counter this phenomenon.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The problem of overfitting to the pruning set highlights the need for significance testing. We investigate two classes of test, "parametric" and "non-parametric." The standard chi-squared statistic can be used both in a parametric test and as the basis for a non-parametric permutation test. In both cases it is necessary to select the significance level at which pruning is applied. We show empirically that both versions of the chi-squared test perform equally well if their significance levels are adjusted appropriately. Using a collection of standard datasets, we show that significance testing improves on standard reduced error pruning if the significance level is tailored to the particular dataset at hand using cross-validation, yielding consistently smaller trees that perform at least as well and sometimes better.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+99/11
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Weka: Practical machine learning tools and techniques with Java implementations
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Ian H. Witten, Eibe Frank, Len Trigg, Mark Hall, Geoffrey Holmes, Sally Jo Cunningham
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The Waikato Environment for Knowledge Analysis (Weka) is a comprehensive suite of Java class libraries that implement many state-of-the-art machine learning and data mining algorithms. Weka is freely available on the World-Wide Web and accompanies a new text on data mining [1] which documents and fully explains all the algorithms it contains. Applications written using the Weka class libraries can be run on any computer with a Web browsing capability; this allows users to apply machine learning techniques to their own data regardless of computer platform.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+99/12
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Pace Regression
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Yong Wang, Ian H. Witten
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+This paper articulates a new method of linear regression, “pace regression”, that addresses many drawbacks of standard regression reported in the literature—particularly the subset selection problem. Pace regression improves on classical ordinary least squares (OLS) regression by evaluating the effect of each variable and using a clustering analysis to improve the statistical basis for estimating their contribution to the overall regression. As well as outperforming OLS, it also outperforms—in a remarkably general sense—other linear modeling techniques in the literature, including subset selection procedures, which seek a reduction in dimensionality that falls out as a natural byproduct of pace regression. The paper defines six procedures that share the fundamental idea of pace regression, all of which are theoretically justified in terms of asymptotic performance. Experiments confirm the performance improvement over other techniques.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+99/13
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+A compression-based algorithm for Chinese word segmentation
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+W.J. Teahan, Yingying Wen, Rodger McNab, Ian H. Witten
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The Chinese language is written without using spaces or other word delimiters. Although a text may be thought of as a corresponding sequence of words, there is considerable ambiguity in the placement of boundaries. Interpreting a text as a sequence of words is beneficial for some information retrieval and storage tasks: for example, full-text search, word-based compression, and keyphrase extraction.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+We describe a scheme that infers appropriate positions for word boundaries using an adaptive language model that is standard in text compression. It is trained on a corpus of pre-segmented text, and when applied to new text, interpolates word boundaries so as to maximize the compression obtained. This simple and general method performs well with respect to specialized schemes for Chinese language segmentation.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+99/14
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Clustering with finite data from semi-parametric mixture distributions
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Yong Wang, Ian H. Witten
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Existing clustering methods for the semi-parametric mixture distribution perform well as the volume of data increases. However, they all suffer from a serious drawback in finite-data situations: small outlying groups of data points can be completely ignored in the clusters that are produced, no matter how far away they lie from the major clusters. This can result in unbounded loss if the loss function is sensitive to the distance between clusters.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+This paper proposes a new distance-based clustering method that overcomes the problem by avoiding global constraints. Experimental results illustrate its superiority to existing methods when small clusters are present in finite data sets; they also suggest that it is more accurate and stable than other methods even when there are no small clusters.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+99/15
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+99/16
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The Niupepa Collection: Opening the blinds on a window to the past
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Te Taka Keegan, Sally Jo Cunningham, Mark Apperley
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+This paper describes the building of a digital library collection of historic newspapers. The newspapers (<i>Niupepa</i> in Maori), which were published in New Zealand during the period 1842 to 1933, form a unique historical record of the Maori language, and of events from an historical perspective. Images of these newspapers have been converted to digital form, electronic text extracted from these, and the collection is now being made available over the Internet as a part of the New Zealand Digital Library (NZDL) project at the University of Waikato.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+98/1
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Boosting trees for cost-sensitive classifications
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Kai Ming Ting, Zijian Zheng
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+This paper explores two boosting techniques for cost-sensitive tree classification in the situation where misclassification costs change very often. Ideally, one would like to have only one induction, and use the induced model for different misclassification costs. Thus, it demands robustness of the induced model against cost changes. Combining multiple trees gives robust predictions against this change. We demonstrate that ordinary boosting combined with the minimum expected cost criterion to select the prediction class is a good solution under this situation. We also introduce a variant of the ordinary boosting procedure which utilizes the cost information during training. We show that the proposed technique performs better than the ordinary boosting in terms of misclassification cost. However, this technique requires to induce a set of new trees every time the cost changes. Our empirical investigation also reveals some interesting behavior of boosting decision trees for cost-sensitive classification.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+98/2
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Generating accurate rule sets without global optimization
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Eibe Frank, Ian H. Witten
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The two dominant schemes for rule-learning, C4.5 and RIPPER, both operate in two stages. First they induce an initial rule set and then they refine it using a rather complex optimization stage that discards (C4.5) or adjusts (RIPPER) individual rules to make them work better together. In contrast, this paper shows how good rule sets can be learned one rule at a time, without any need for global optimization. We present an algorithm for inferring rules by repeatedly generating partial decision trees, thus combining the two major paradigms for rule generation-creating rules from decision trees and the separate-and-conquer rule-learning technique. The algorithm is straightforward and elegant: despite this, experiments on standard datasets show that it produces rule sets that are as accurate as and of similar size to those generated by C4.5, and more accurate than RIPPER's. Moreover, it operates efficiently, and because it avoids postprocessing, does not suffer the extremely slow performance on pathological example sets for which the C4.5 method has been criticized.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+98/3
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+VQuery: a graphical user interface for Boolean query Specification and dynamic result preview
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Steve Jones
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Textual query languages based on Boolean logic are common amongst the search facilities of on-line information repositories. However, there is evidence to suggest that the syntactic and semantic demands of such languages lead to user errors and adversely affect the time that it takes users to form queries. Additionally, users are faced with user interfaces to these repositories which are unresponsive and uninformative, and consequently fail to support effective query refinement. We suggest that graphical query languages, particularly Venn-like diagrams, provide a natural medium for Boolean query specification which overcomes the problems of textual query languages. Also, dynamic result previews can be seamlessly integrated with graphical query specification to increase the effectiveness of query refinements. We describe VQuery, a query interface to the New Zealand Digital Library which exploits querying by Venn diagrams and integrated query result previews.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+98/4
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Revising <I>Z</I>: semantics and logic
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Martin C. Henson, Steve Reeves
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+We introduce a simple specification logic <I>Z</I>c comprising a logic and semantics (in <I>ZF</I> set theory). We then provide an interpretation for (a rational reconstruction of) the specification language <I>Z</I> within <I>Z</I>c. As a result we obtain a sound logic for <I>Z</I>, including the schema calculus. A consequence of our formalisation is a critique of a number of concepts used in <I>Z</I>. We demonstrate that the complications and confusions which these concepts introduce can be avoided without compromising expressibility.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+98/5
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+A logic for the schema calculus
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Martin C. Henson, Steve Reeves
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+In this paper we introduce and investigate a logic for the schema calculus of <I>Z</I>. The schema calculus is arguably the reason for <I>Z</I>'s popularity but so far no true calculus (a sound system of rules for reasoning about schema expressions) has been given. Presentations thus far have either failed to provide a calculus (e.g. the draft standard [3]) or have fallen back on informal descriptions at a syntactic level (most text books e.g. [7[). Once the calculus is established we introduce a derived equational logic which enables us to formalise properly the informal notations of schema expression equality to be found in the literature.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+98/6
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+New foundations for <I>Z</I>
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Martin C. Henson, Steve Reeves
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+We provide a constructive and intensional interpretation for the specification language <I>Z</I> in a theory of operations and kinds <I>T</I>. The motivation is to facilitate the development of an integrated approach to program construction. We illustrate the new foundations for <I>Z</I> with examples.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+98/7
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Predicting apple bruising relationships using machine learning
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+G. Holmes, S.J. Cunningham, B.T. Dela Rue, A.F. Bollen
+</p></div>
+
+
+
+<p><div name="Body Text" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Many models have been used to describe the influence of internal or external factors on apple bruising. Few of these have addressed the application of derived relationships to the evaluation of commercial operations. From an industry perspective, a model must enable fruit to be rejected on the basis of a commercially significant bruise and must also accurately quantify the effects of various combinations of input features (such as cultivar, maturity, size, and so on) on bruise prediction. Input features must in turn have characteristics which are measurable commercially; for example, the measure of force should be impact energy rather than energy absorbed. Further, as the commercial criteria for acceptable damage levels change, the model should be versatile enough to regenerate new bruise thresholds from existing data.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Machine learning is a burgeoning technology with a vast range of potential applications particularly in agriculture where large amounts of data can be readily collected [1]. The main advantage of using a machine learning method in an application is that the models built for prediction can be viewed and understood by the owner of the data who is in a position to determine the usefulness of the model, an essential component in a commercial environment.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+98/8
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+An evaluation of passage-level indexing strategies for a technical report archive
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Michael Williams
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Past research has shown that using evidence from document passages rather than complete documents is an effective way of improving the precision of full-text database searches. However, passage-level indexing has yet to be widely adopted for commercial or online databases.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+This paper reports on experiments designed to test the efficacy of passage-level indexing with a particular collection of a full-text online database, the New Zealand Digital Library. Discourse passages and word-window passages are used for the indexing process. Both ranked and Boolean searching are used to test the resulting indexes.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Overlapping window passages are shown to offer the best retrieval performance with both ranked and Boolean queries. Modifications may be necessary to the term weighting methodology in order to ensure optimal ranked query performance.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+98/9
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Managing multiple collections, multiple languages, and multiple media in a distributed digital library
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Ian H. Witten, Rodger McNab, Steve Jones, Sally Jo Cunningham, David Bainbridge, Mark Apperley
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Managing the organizational and software complexity of a comprehensive digital library presents a significant challenge. Different library collections each have their own distinctive features. Different presentation languages have structural implications such as left-to-right writing order and text-only interfaces for the visually impaired. Different media involve different file formats, and-more importantly-radically different search strategies are required for non-textual media. In a distributed library, new collections can appear asynchronously on servers in different parts of the world. And as searching interfaces mature from the command-line era exemplified by current Web search engines into the age of reactive visual interfaces, experimental new interfaces must be developed, supported, and tested. This paper describes our experience, gained from operating a substantial digital library service over several years, in solving these problems by designing an appropriate software architecture.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+98/10
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Experiences with a weighted decision tree learner
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+John G. Cleary, Leonard E. Trigg
+</p></div>
+
+
+
+<p><div name="Body Text" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Machine learning algorithms for inferring decision trees typically choose a single “best” tree to describe the training data. Recent research has shown that classification performance can be significantly improved by voting predictions of multiple, independently produced decision trees. This paper describes an algorithm, OB1, that makes a weighted sum over many possible models. We describe one instance of OB1, that includes <I>all</I> possible decision trees as well as naïve Bayesian models. OB1 is compared with a number of other decision tree and instance based learning alogrithms on some of the data sets from the UCI repository. Both an information gain and an accuracy measure are used for the comparison. On the information gain measure OB1 performs significantly better than all the other algorithms. On the accuracy measure it is significantly better than all the algorithms except naïve Bayes which performs comparably to OB1.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+98/11
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+An entropy gain measure of numeric prediction performance
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Leonard Trigg
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Categorical classifier performance is typically evaluated with respect to error rate, expressed as a percentage of test instances that were not correctly classified. When a classifier produces multiple classifications for a test instance, the prediction is counted as incorrect (even if the correct class was one of the predictions). Although commonly used in the literature, error rate is a coarse measure of classifier performance, as it is based only on a single prediction offered for a test instance. Since many classifiers can produce a class distribution as a prediction, we should use this to provide a better measure of how much information the classifier is extracting from the domain.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Numeric classifiers are a relatively new development in machine learning, and as such there is no single performance measure that has become standard. Typically these machine learning schemes predict a single real number for each test instance, and the error between the predicted and actual value is used to calculate a myriad of performance measures such as correlation coefficient, root mean squared error, mean absolute error, relative absolute error, and root relative squared error. With so many performance measures it is difficult to establish an overall performance evaluation.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The next section describes a performance measure for machine learning schemes that attempts to overcome the problems with current measures. In addition, the same evaluation measure is used for categorical and numeric classifier.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+98/12
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Proceedings of CBISE '98 CaiSE*98 Workshop on Component Based Information Systems Engineering
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Edited by John Grundy
+</p></div>
+
+
+
+<p><div name="Body Text" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Component-based information systems development is an area of research and practice of increasing importance. Information Systems developers have realised that traditional approaches to IS engineering produce monolithic, difficult to maintain, difficult to reuse systems. In contrast, the use of software components, which embody data, functionality and well-specified and understood interfaces, makes interoperable, distributed and highly reusable IS components feasible. Component-based approaches to IS engineering can be used at strategic and organisational levels, to model business processes and whole IS architectures, in development methods which utilise component-based models during analysis and design, and in system implementation. Reusable components can allow end users to compose and configure their own Information Systems, possibly from a range of suppliers, and to more tightly couple their organisational workflows with their IS support.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+This workshop proceedings contains a range of papers addressing one or more of the above issues relating to the use of component models for IS development. All of these papers were refereed by at least two members of an international workshop committee comprising industry and academic researchers and users of component technologies. Strategic uses of components are addressed in the first three papers, while the following three address uses of components for systems design and workflow management. Systems development using components, and the provision of environments for component management are addressed in the following group of five papers. The last three papers in this proceedings address component management and analysis techniques.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+All of these papers provide new insights into the many varied uses of component technology for IS engineering. I hope you find them as interesting and useful as I have when collating this proceedings and organising the workshop.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+98/13
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+An analysis of usage of a digital library
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Steve Jones, Sally Jo Cunningham, Rodger McNab
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+As experimental digital library testbeds gain wider acceptance and develop significant user bases, it becomes important to investigate the ways in which users interact with the systems in practice. Transaction logs are one source of usage information, and the information on user behaviour can be culled from them both automatically (through calculation of summary statistics) and manually (by examining query strings for semantic clues on search motivations and searching strategy). We conduct a transaction log analysis on user activity in the Computer Science Technical Reports Collection of the New Zealand Digital Library, and report insights gained and identify resulting search interface design issues.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+98/14
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Measuring ATM traffic: final report for New Zealand Telecom
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+John Cleary, Ian Graham, Murray Pearson, Tony McGregor
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The report describes the development of a low-cost ATM monitoring system, hosted by a standard PC. The monitor can be used remotely returning information on ATM traffic flows to a central site. The monitor is interfaces to a GPS timing receiver, which provides an absolute time accuracy of better than 1 usec. By monitoring the same traffic flow at different points in a network it is possible to measure cell delay and delay variation in real time, and with existing traffic. The monitoring system characterises cells by a CRC calculated over the cell payload, thus special measurement cells are not required. Delays in both local area and wide-area networks have been measured using this system. It is possible to measure delay in a network that is not end-to-end ATM, as long as some cells remain identical at the entry and exit points. Examples are given of traffic and delay measurements in both wide and local area network systems, including delays measured over the Internet from Canada to New Zealand.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+98/15
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Despite its simplicity, the naïve Bayes learning scheme performs well on most classification tasks, and is often significantly more accurate than more sophisticated methods. Although the probability estimates that it produces can be inaccurate, it often assigns maximum probability to the correct class. This suggests that its good performance might be restricted to situations where the output is categorical. It is therefore interesting to see how it performs in domains where the predicted value is numeric, because in this case, predictions are more sensitive to inaccurate probability estimates.<P>
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+This paper shows how to apply the naïve Bayes methodology to numeric prediction (i.e. regression) tasks, and compares it to linear regression, instance-based learning, and a method that produces “model trees”-decision trees with linear regression functions at the leaves. Although we exhibit an artificial dataset for which naïve Bayes is the method of choice, on real-world datasets it is almost uniformly worse than model trees. The comparison with linear regression depends on the error measure: for one measure naïve Bayes performs similarly, for another it is worse. Compared to instance-based learning, it performs similarly with respect to both measures. These results indicate that the simplistic statistical assumption that naïve Bayes makes is indeed more restrictive for regression than for classification.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+98/16
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Link as you type: using key phrases for automated dynamic link generation
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Steve Jones
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+When documents are collected together from diverse sources they are unlikely to contain useful hypertext links to support browsing amongst them. For large collections of thousands of documents it is prohibitively resource intensive to manually insert links into each document. Users of such collections may wish to relate documents within them to text that they are themselves generating. This process, often involving keyword searching, distracts from the authoring process and results in material related to query terms but not necessarily to the author's document. Query terms that are effective in one collection might not be so in another. We have developed Phrasier, a system that integrates authoring (of text and hyperlinks), browsing, querying and reading in support of information retrieval activities. Phrasier exploits key phrases which are automatically extracted from documents in a collection, and uses them as link anchors and to identify candidate destinations for hyperlinks. This system suggests links into existing collections for purposes of authoring and retrieval of related information, creates links between documents in a collection and provides supportive document and link overviews.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+98/17
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Melody based tune retrieval over the World Wide Web
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+David Bainbridge, Rodger J. McNab, Lloyd A. Smith
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+In this paper we describe the steps taken to develop a Web-based version of an existing stand-alone, single-user digital library application for melodical searching of a collection of music. For the three key components: input, searching, and output, we assess the suitability of various Web-based strategies that deal with the now distributed software architecture and explain the decisions we made. The resulting melody indexing service, known as MELDEX, has been in operation for one year, and the feed-back we have received has been favorable.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+98/18
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Making oral history accessible over the World Wide Web
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+David Bainbridge, Sally Jo Cunningham
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+We describe a multimedia, WWW-based oral history collection constructed from off-the-shelf or publicly available software. The source materials for the collection include audio tapes of interviews and summary transcripts of each interview, as well as photographs illustrating episodes mentioned in the tapes. Sections of the transcripts are manually matched to associated segments of the tapes, and the tapes are digitized. Users search a full-text retrieval system based on the text transcripts to retrieve relevant transcript sections and their associated audio recordings and photographs. It is also possible to search for photos by matching text queries against text descriptions of the photos in the collection, where the located photos link back to their respective interview transcript and audio recordings.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>1997</b>
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+97/1
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+A dynamic and flexible representation of social relationships in CSCW
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Steve Jones, Steve Marsh
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+CSCW system designers lack effective support in addressing the social issues and interpersonal relationships which are linked with the use of CSCW systems. We present a formal description of trust to support CSCW system designers in considering the social aspects of group work, embedding those considerations in systems and analysing computer supported group processes.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+We argue that trust is a critical aspect in group work, and describe what we consider to be the building blocks of trust. We then present a formal notation for the building blocks, their use in reasoning about social interactions and how they are amended over time.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+We then consider how the formalism may be used in practice, and present some insights from initial analysis of the behaviour of the formalism. This is followed by a description of possible amendments and extensions to the formalism. We conclude that it is possible to formalise a notion of trust and to model the formalisation by a computational mechanism.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+97/2
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Design issues for World Wide Web navigation visualisation tools
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Andy Cockburn, Steve Jones
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The World Wide Web (WWW) is a successful hypermedia information space used by millions of people, yet it suffers from many deficiencies and problems in support for navigation around its vast information space. In this paper we identify the origins of these navigation problems, namely WWW browser design, WWW page design, and WWW page description languages. Regardless of their origins, these problems are eventually represented to the user at the browser's user interface. To help overcome these problems, many tools are being developed which allow users to visualise WWW subspaces. We identify five key issues in the design and functionality of these visualisation systems: characteristics of the visual representation, the scope of the subspace representation, the mechanisms for generating the visualisation, the degree of browser independence, and the navigation support facilities. We provide a critical review of the diverse range of WWW visualisation tools with respect to these issues.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+97/3
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Stacked generalization: when does it work?
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Kai Ming Ting, Ian H. Witten
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Stacked generalization is a general method of using a high-level model to combine lower-level models to achieve greater predictive accuracy. In this paper we address two crucial issues which have been considered to be a 'black art' in classification tasks ever since the introduction of stacked generalization in 1992 by Wolpert: the type of generalizer that is suitable to derive the higher-level model, and the kind of attributes that should be used as its input.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+We demonstrate the effectiveness of stacked generalization for combining three different types of learning algorithms, and also for combining models of the same type derived from a single learning algorithm in a multiple-data-batches scenario. We also compare the performance of stacked generalization with published results arcing and bagging.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+97/4
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Browsing in digital libraries: a phrase-based approach
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Craig Nevill-Manning, Ian H. Witten, Gordon W. Paynter
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+A key question for digital libraries is this: how should one go about becoming familiar with a digital collection, as opposed to a physical one? Digital collections generally present an appearance which is extremely opaque-a screen, typically a Web page, with no indication of what, or how much, lies beyond: whether a carefully-selected collection or a morass of worthless ephemera; whether half a dozen documents or many millions. At least physical collections occupy physical space, present a physical appearance, and exhibit tangible physical organization. When standing on the threshold of a large library one gains a sense of presence and permanence that reflects the care taken in building and maintaining the collection inside. No-one could confuse it with a dung-heap! Yet in the digital world the difference is not so palpable.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+97/5
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+A graphical notation for the design of information visualisations
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Matthew C. Humphrey
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Visualisations are coherent, graphical expressions of complex information that enhance people's ability to communicate and reason about that information. Yet despite the importance of visualisations in helping people to understand and solve a wide variety of problems, there is a dearth of formal tools and methods for discussing, describing and designing them. Although simple visualisations, such as bar charts and scatterplots, are easily produced by modern interactive software, novel visualisations of multivariate, multirelational data must be expressed in a programming language. The Relational Visualisation Notation is a new, graphical language for designing such highly expressive visualisations that does not use programming constructs. Instead, the notation is based on relational algebra, which is widely used in database query languages, and it is supported by a suite of direct manipulation tools. This article presents the notation and examines the designs of some interesting visualisations.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+97/6
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Applications of machine learning in information retrieval
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Sally Jo Cunningham, James Littin, Ian H. Witten
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Information retrieval systems provide access to collections of thousands, or millions, of documents, from which, by providing an appropriate description, users can recover any one. Typically, users iteratively refine the descriptions they provide to satisfy their needs, and retrieval systems can utilize user feedback on selected documents to indicate the accuracy of the description at any stage. The style of description required from the user, and the way it is employed to search the document database, are consequences of the indexing method used for the collection. The index may take different forms, from storing keywords with links to individual documents, to clustering documents under related topics.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+97/7
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Computer concepts without computers: a first course in computer science
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Geoffrey Holmes, Tony C. Smith, William J. Rogers
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+While some institutions seek to make CS1 curricula more enjoyable by incorporating specialised educational software [1] or by setting more enjoyable programming assignments [2], we have joined the growing number of Computer Science departments that seek to improve the quality of the CS1 experience by focusing student attention away from the computer monitor [3,4]. Sophisticated computing concepts usually reserved for senior level courses are presented in a <I>popular science</I> manner, and given equal time alongside the essential introductory programming material. By exposing students to a broad range of specific computational problems we endeavour to make the introductory course more interesting and enjoyable, and instil in students a sense of vision for areas they might specialise in as computing majors.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+97/8
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+A sight-singing tutor
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Lloyd A. Smith, Rodger J. McNab
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+This paper describes a computer program designed to aid its users in learning to sight-sing. Sight-singing-the ability to sing music from a score without prior study-is an important skill for musicians and holds a central place in most university music curricula. Its importance to vocalists is obvious; it is also an important skill for instrumentalists and conductors because it develops the aural imagination necessary to judge how the music should sound, when played (Benward and Carr 1991). Furthermore, it is an important skill for amateur musicians, who can save a great deal of rehearsal time through an ability to sing music at sight.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+97/9
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Stacking bagged and dagged models
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Kai Ming Ting, I.H. Witten
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+In this paper, we investigate the method of <i>stacked generalization</i> in combining models derived from different subsets of a training dataset by a single learning algorithm, as well as different algorithms. The simplest way to combine predictions from competing models is majority vote, and the effect of the sampling regime used to generate training subsets has already been studied in this context-when bootstrap samples are used the method is called <i>bagging</i>, and for disjoint samples we call it <i>dagging</i>. This paper extends these studies to stacked generalization, where a learning algorithm is employed to combine the models. This yields new methods dubbed <i>bag-stacking</i> and <i>dag-stacking</i>.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+We demonstrate that bag-stacking and dag-stacking can be effective for classification tasks even when the training samples cover just a small fraction of the full dataset. In contrast to earlier bagging results, we show that bagging and bag-stacking work for stable as well as unstable learning algorithms, as do dagging and dag-stacking. We find that bag-stacking (dag-stacking) almost always has higher predictive accuracy than bagging (dagging), and we also show that bag-stacking models derived using two different algorithms is more effective than bagging.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+97/10
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Extracting text from Postscript
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Craig Nevill-Manning, Todd Reed, Ian H. Witten
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+We show how to extract plain text from PostScript files. A textual scan is inadequate because PostScript interpreters can generate characters on the page that do not appear in the source file. Furthermore, word and line breaks are implicit in the graphical rendition, and must be inferred from the positioning of word fragments. We present a robust technique for extracting text and recognizing words and paragraphs. The method uses a standard PostScript interpreter but redefines several PostScript operators, and simple heuristics are employed to locate word and line breaks. The scheme has been used to create a full-text index, and plain-text versions, of 40,000 technical reports (34 Gbyte of PostScript). Other text-extraction systems are reviewed: none offer the same combination of robustness and simplicity.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+97/11
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Gathering and indexing rich fragments of the World Wide Web
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Geoffrey Holmes, William J Rogers
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+While the World Wide Web (WWW) is an attractive option as a resource for teaching and research it does have some undesirable features. The cost of allowing students unlimited access can be high-both in money and time; students may become addicted to 'surfing' the web-exploring purely for entertainment-and jeopardise their studies. Students are likely to discover undesirable material because large scale search engines index sites regardless of their merit. Finally, the explosive growth of WWW usage means that servers and networks are often overloaded, to the extent that a student may gain a very negative view of the technology.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+We have developed a piece of software which attempts to address these issues by capturing rich fragments of the WWW onto local storage media. It is possible to put a collection onto CD ROM, providing portability and inexpensive storage. This enables the presentation of the WWW to distance learning students, who do not have internet access. The software interfaces to standard, commonly available web browsers, acting as a proxy server to the files stored on the local media, and provides a search engine giving full text searching capability within the collection.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+97/12
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Using model trees for classification
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Eibe Frank, Yong Wang, Stuart Inglis, Geoffrey Holmes, Ian H. Witten
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Model trees, which are a type of decision tree with linear regression functions at the leaves, form the basis of a recent successful technique for predicting continuous numeric values. They can be applied to classification problems by employing a standard method of transforming a classification problem into a problem of function approximation. Surprisingly, using this simple transformation the model tree inducer M5', based on Quinlan's M5, generates more accurate classifiers than the state-of-the-art decision tree learner C5.0, particularly when most of the attributes are numeric.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+97/13
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Discovering inter-attribute relationships
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Geoffrey Holmes
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+It is important to discover relationships between attributes being used to predict a class attribute in supervised learning situations for two reasons. First, any such relationship will be potentially interesting to the provider of a dataset in its own right. Second, it would simplify a learning algorithm's search space, and the related irrelevant feature and subset selection problem, if the relationships were removed from datasets ahead of learning. An algorithm to discover such relationships is presented in this paper. The algorithm is described and a surprising number of inter-attribute relationships are discovered in datasets from the University of California at Irvine (UCI) repository.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+97/14
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Learning from batched data: model combination vs data combination
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Kai Ming Ting, Boon Toh Low, Ian H. Witten
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+When presented with multiple batches of data, one can either combine them into a single batch before applying a machine learning procedure or learn from each batch independently and combine the resulting models. The former procedure, data combination, is straightforward; this paper investigates the latter, model combination. Given an appropriate combination method, one might expect model combination to prove superior when the data in each batch was obtained under somewhat different conditions or when different learning algorithms were used on the batches. Empirical results show that model combination often outperforms data combination even when the batches are drawn randomly from a single source of data and the same learning method is used on each. Moreover, this is not just an artifact of one particular method of combining models: it occurs with several different combination methods.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+We relate this phenomenon to the learning curve of the classifiers being used. Early in the learning process when the learning curve is steep there is much to gain from data combination, but later when it becomes shallow there is less to gain and model combination achieves a greater reduction in variance and hence a lower error rate.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The practical implication of these results is that one should consider using model combination rather than data combination, especially when multiple batches of data for the same task are readily available. It is often superior even when the batches are drawn randomly from a single sample, and we expect its advantage to increase if genuine statistical differences between the batches exist.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+97/15
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Information seeking retrieval, reading and storing behaviour of library users
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Turner K.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+In the interest of digital libraries, it is advisable that designers be aware of the potential behaviour of the users of such a system. There are two distinct parts under investigation, the interaction between traditional libraries involving the seeking and retrieval of relevant material, and the reading and storage behaviours ensuing. Through this analysis, the findings could be incorporated into digital library facilities. There has been copious amounts of research on information seeking leading to the development of behavioural models to describe the process. Often research on the information seeking practices of individuals is based on the task and field of study. The information seeking model, presented by Ellis et al. (1993), characterises the format of this study where it is used to compare various research on the information seeking practices of groups of people (from academics to professionals). It is found that, although researchers do make use of library facilities, they tend to rely heavily on their own collections and primarily use the library as a source for previously identified information, browsing and interloan. It was found that there are significant differences in user behaviour between the groups analysed. When looking at the reading and storage of material it was hard to draw conclusions, due to the lack of substantial research and information on the topic. However, through the use of reading strategies, a general idea on how readers behave can be developed. Designers of digital libraries can benefit from the guidelines presented here to better understand their audience.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+97/16
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Proceeding of the INTERACT97 Combined Workshop on CSCW in HCI-Worldwide
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Matthias Rauterberg, Lars Oestreicher, John Grundy
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+This is the proceedings for the INTERACT97 combined workshop on “CSCW in HCI-worldwide”. The position papers in this proceedings are those selected from topics relating to HCI community development worldwide and to CSCW issues. Originally these were to be two separate INTERACT workshops, but were combined to ensure sufficient participation for a combined workshop to run.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The combined workshop has been split into two separate sessions to run in the morning of July 15<sup>th</sup>, Sydney, Australia. One to discuss the issues relating to the position papers focusing on general CSCW systems, the other to the development of HCI communities in a worldwide context. The CSCW session uses as a case study a proposed groupware tool for facilitating the development of an HCI database with a worldwide geographical distribution. The HCI community session focuses on developing the content for such a database, in order for it to foster the continued development of HCI communities. The afternoon session of the combined workshop involves a joint discussion of the case study groupware tool, in terms of its content and likely groupware facilities.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The position papers have been grouped into those focusing on HCI communities and hence content issues for a groupware database, and those focusing on CSCW and groupware issues, and hence likely groupware support in the proposed HCI database/collaboration tools. We hope that you find the position papers in this proceedings offer a wide range of interesting reports of HCI community development worldwide, leading CSCW system research, and that a groupware tool supporting aspects of a worldwide HCI database can draw upon the varied work reported.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+97/17
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Internationalising a spreadsheet for Pacific Basin languages
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Robert Barbour, Alvin Yeo
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+As people trade and engage in commerce, an economically dominant culture tends to migrate language into other recently contacted cultures. Information technology (IT) can accelerate enculturation and promote the expansion of western hegemony in IT. Equally, IT can present a culturally appropriate interface to the user that promotes the preservation of culture and language with very little additional effort. In this paper a spreadsheet is internationalised to accept languages from the Latin-1 character set such as English, Maori and Bahasa Melayu (Malaysia's national language). A technique that allows a non-programmer to add a new language to the spreadsheet is described. The technique could also be used to internationalise other software at the point of design by following the steps we outline.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+97/18
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Localising a spreadsheet: an Iban example
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Alvin Yeo, Robert Barbour
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Presently, there is little localisation of software to smaller cultures if it is not economically viable. We believe software should also be localised to the languages of small cultures in order to sustain and preserve these small cultures. As an example, we localised a spreadsheet from English to Iban. The process in which we carried out the localisation can be used as a framework for the localisation of software to languages of small ethnic minorities. Some problems faced during the localisation process are also discussed.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+97/19
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Strategies of internationalisation and localisation: a postmodernist/s perspective
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Alvin Yeo, Robert Barbour
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Many software companies today are developing software not only for local consumption but for the rest of the world. We introduce the concepts of internationalisation and localisation and discuss some techniques using these processes. An examination of postmodern critique with respect to the software industry is also reported. In addition, we also feature our proposed internationalisation technique that was inspired by taking into account the researches of postmodern philosophers and mathematicians. As illustrated in our prototype, the technique empowers non-programmers to localise their own software. Further development of the technique and its implications on user interfaces and the future of software internationalisation and localisation are discussed.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+97/20
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Language use in software
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Alvin Yeo, Robert Barbour
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Many of the popular software we use today are in English. Very few software applications are available in minority languages. Besides economic goals, we justify why software should be made available to smaller cultures. Furthermore, there is evidence that people learn and progress faster in software in their mother tongue (Griffiths et at, 1994) (Krock, 1996). We hypothesise that experienced users of English spreadsheet can easily migrate to a spreadsheet in their native tongue i.e. Bahasa Melayu (Malaysia's national language). Observations made in the study suggest that the native speakers of Bahasa Melayu had difficulties with the Bahasa Melayu interface. The subjects' main difficulty was their unfamiliarity with computing terminology in Bahasa Melayu. We present possible strategies to increase the use of Bahasa Melayu in IT. These strategies may also be used to promote the use of other minority languages in IT.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+97/21
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Usability testing: a Malaysian study
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Alvin Yeo, Robert Barbour, Mark Apperley
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+An exploratory study of software assessment techniques is conducted in Malaysia. Subjects in the study comprised staff members of a Malaysian university with a high Information Technology (IT) presence. The subjects assessed a spreadsheet tool with a Bahasa Melayu (Malaysia's national language) interface. Software evaluation techniques used include the think aloud method, interviews and the System Usability Scale. The responses in the various techniques used are reported and initial results indicate idiosyncratic behaviour of Malaysian subjects. The implications of the findings are also discussed.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+97/22
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Inducing cost-sensitive trees via instance-weighting
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Kai Ming Ting
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+We introduce an instance-weighting method to induce cost-sensitive trees in this paper. It is a generalization of the standard tree induction process where only the initial instance weights determine the type of tree (i.e., minimum error trees or minimum cost trees) to be induced. We demonstrate that it can be easily adopted to an existing tree learning algorithm.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Previous research gave insufficient evidence to support the fact that the greedy divide-and-conquer algorithm can effectively induce a truly cost-sensitive tree directly from the training data. We provide this empirical evidence in this paper. The algorithm employing the instance-weighting method is found to be comparable to or better than both C4.5 and C5 in terms of total misclassification costs, tree size and the number of high cost errors. The instance-weighting method is also simpler and more effective in implementation than a method based on altered priors.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+97/23
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Fast convergence with a greedy tag-phrase dictionary
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Ross Peeters, Tony C. Smith
+</p></div>
+
+
+
+<p><div name="Body Text" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The best general-purpose compression schemes make their gains by estimating a probability distribution over all possible next symbols given the context established by some number of previous symbols. Such context models typically obtain good compression results for plain text by taking advantage of regularities in character sequences. Frequent words and syllables can be incorporated into the model quickly and thereafter used for reasonably accurate prediction. However, the precise context in which frequent patterns emerge is often extremely varied, and each new word or phrase immediately introduces new contexts which can adversely affect the compression rate
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+A great deal of the structural regularity in a natural language is given rather more by properties of its grammar than by the orthographic transcription of its phonology. This implies that access to a grammatical abstraction might lead to good compression. While grammatical models have been used successfully for compressing computer programs [4], grammar-based compression of plain text has received little attention, primarily because of the difficulties associated with constructing a suitable natural language grammar. But even without a precise formulation of the syntax of a language, there is a linguistic abstraction which is easily accessed and which demonstrates a high degree of regularity which can be exploited for compression purposes-namely, lexical categories.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+97/24
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Tag based models of English text
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+W. J. Teahan, John G. Cleary
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The problem of compressing English text is important both because of the ubiquity of English as a target for compression and because of the light that compression can shed on the structure of English. English text is examined in conjunction with additional information about the parts of speech of each word in the text (these are referred to as “tags”). It is shown that the tags plus the text can be compressed more than the text alone. Essentially the tags can be compressed for nothing or even a small net saving in size. A comparison is made of a number of different ways of integrating compression of tags and text using an escape mechanism similar to PPM. These are also compared with standard word based and character based compression programs. The result is that the tag character and word based schemes always outperform the character based schemes. Overall, the tag based schemes outperform the word based schemes. We conclude by conjecturing that tags chosen for compression rather than linguistic purposes would perform even better.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+97/25
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Musical image compression
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+David Bainbridge, Stuart Inglis
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Optical music recognition aims to convert the vast repositories of sheet music in the world into an on-line digital format [Bai97]. In the near future it will be possible to assimilate music into digital libraries and users will be able to perform searches based on a sung melody in addition to typical text-based searching [MSW+96]. An important requirement for such a system is the ability to reproduce the original score as accurately as possible. Due to the huge amount of sheet music available, the efficient storage of musical images is an important topic of study.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+This paper investigates whether the “knowledge” extracted from the optical music recognition (OMR) process can be exploited to gain higher compression than the JBIG international standard for bi-level image compression. We present a hybrid approach where the primitive shapes of music extracted by the optical music recognition process-note heads, note stems, staff lines and so forth-are fed into a graphical symbol based compression scheme originally designed for images containing mainly printed text. Using this hybrid approach the average compression rate for a single page is improved by 3.5% over JBIG. When multiple pages with similar typography are processed in sequence, the file size is decreased by 4-8%.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Section 2 presents the relevant background to both optical music recognition and textual image compression. Section 3 describes the experiments performed on 66 test images, outlining the combinations of parameters that were examined to give the best results. The initial results and refinements are presented in Section 4, and we conclude in the last section by summarizing the findings of this work.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+97/26
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Correcting English text using PPM models
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+W. J. Teahan, S. Inglis, J. G. Cleary, G. Holmes
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+An essential component of many applications in natural language processing is a language modeler able to correct errors in the text being processed. For optical character recognition (OCR), poor scanning quality or extraneous pixels in the image may cause one or more characters to be mis-recognized; while for spelling correction, two characters may be transposed, or a character may be inadvertently inserted or missed out.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+This paper describes a method for correcting English text using a PPM model. A method that segments words in English text is introduced and is shown to be a significant improvement over previously used methods. A similar technique is also applied as a post-processing stage after pages have been recognized by a state-of-the-art commercial OCR system. We show that the accuracy of the OCR system can be increased from 95.9% to 96.6%, a decrease of about 10 errors per page.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+97/27
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Constraints on parallelism beyond 10 instructions per cycle
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+John G. Cleary, Richard H. Littin, J. A. David McWha, Murray W. Pearson
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The problem of extracting Instruction Level Parallelism at levels of 10 instructions per clock and higher is considered. Two different architectures which use speculation on memory accesses to achieve this level of performance are reviewed. It is pointed out that while this form of speculation gives high potential parallelism it is necessary to retain execution state so that incorrect speculation can be detected and subsequently squashed. Simulation results show that the space to store such state is a critical resource in obtaining good speedup. To make good use of the space it is essential that state be stored efficiently and that it be retired as soon as possible. A number of techniques for extracting the best usage from the available state storage are introduced.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+97/28
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Effects of re-ordered memory operations on parallelism
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Richard H. Littin, John G. Cleary
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The performance effect of permitting different memory operations to be re-ordered is examined. The available parallelism is computed using a machine code simulator. A range of possible restrictions on the re-ordering of memory operations is considered: from the purely sequential case where no re-ordering is permitted; to the completely permissive one where memory operations may occur in any order so that the parallelism is restricted only by data dependencies. A general conclusion is drawn that to reliably obtain parallelism beyond 10 instructions per clock will require an ability to re-order all memory instructions. A brief description of a feasible architecture capable of this is given.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 0.00mm -0.14mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+97/29
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+OZCHI'96 Industry Session: Sixth Australian Conference on Human-Computer Interaction
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Edited by Chris Phillips, Janis McKauge
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The idea for a specific industry session at OZCHI was first mooted at the 1995 conference in Wollongong, during questions following a session of short papers which happened (serendipitously) to be presented by people from industry. An animated discussion took place, most of which was about how OZCHI could be made more relevant to people in industry, be it working as usability consultants, or working within organisations either as usability professionals or as `champions of the cause'. The discussion raised more questions than answers, about the format of such as session, about the challenges of attracting industry participation, and about the best way of publishing the results. Although no real solutions were arrived at, it was enough to place an industry session on the agenda for OZCHI'96.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+97/30
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Adaptive models of English text
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+W. J. Teahan, John G. Cleary
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+High quality models of English text with performance approaching that of humans is important for many applications including spelling correction, speech recognition, OCR, and encryption. A number of different statistical models of English are compared with each other and with previous estimates from human subjects. It is concluded that the best current models are word based with part of speech tags. Given sufficient training text, they are able to attain performance comparable to humans.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+97/31
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+A graphical user interface for Boolean query specification
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Steve Jones, Shona McInnes
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+On-line information repositories commonly provide keyword search facilities via textual query languages based on Boolean logic. However, there is evidence to suggest that the syntactical demands of such languages can lead to user errors and adversely affect the time that it takes users to form queries. Users also face difficulties because of the conflict in semantics between AND and OR when used in Boolean logic and English language. We suggest that graphical query languages, in particular Venn-like diagrams, can alleviate the problems that users experience when forming Boolean expressions with textual languages. We describe Vquery, a Venn-diagram based user interface to the New Zealand Digital Library (NZDL). The design of Vquery has been partly motivated by analysis of NZDL usage. We found that few queries contain more than three terms, use of the intersection operator dominates and that query refinement is common. A study of the utility of Venn diagrams for query specification indicates that with little or no training users can interpret and form Venn-like diagrams which accurately correspond to Boolean expressions. The utility of Vquery is considered and directions for future work are proposed.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+<!--Section Ends-->
+
+
+
+<!--
+<hr>
+<address>
+<a href="_httpextlink_&rl=0&href=http:%2f%2fwvware.sourceforge.net"><img
+src="_httpdocimg_/wvSmall.gif" height=31 width=47
+align=left border=0 alt="wvWare"></a>
+<a href="_httpextlink_&rl=0&href=http:%2f%2fvalidator.w3.org%2fcheck%2freferer"><img
+src="_httpdocimg_/vh40.gif" height=31 width=88
+align=right border=0 alt="Valid HTML 4.0!"></a>
+Document created with <a href="_httpextlink_&rl=0&href=http:%2f%2fwvware.sourceforge.net">wvWare/wvWare version 1.2.4</a><br>
+</address>
+-->
+
+
+
+
+
Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/HASHeaa29d2e.dir/doc.xml
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/HASHeaa29d2e.dir/doc.xml (revision 27727)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/HASHeaa29d2e.dir/doc.xml (revision 27727)
@@ -0,0 +1,2213 @@
+
+
+
+
+
+ indexed_doc
+ en
+ utf8
+ wvWare/wvWare version 1.2.4
+ Greenstone: A Comprehensive Open-Source
+ http://research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402382/word03.html
+ http://research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402382/word03.html
+ import/word03.doc
+ tmp/1372402382/word03.html
+ word03.html
+ word03.doc
+ word03.doc
+ WordPlugin
+ 414720
+ word03
+ Word
+ _icondoc_
+ doc.doc
+ doc.doc
+ Ian H. Witten
+ Rodger J. McNab
+ Stefan J. Boddie
+ David Bainbridge
+ Greenstone: A comprehensive open-source digital library software system
+ HASHeaa29d2e081149673150f3
+ 1372400870
+ 20130628
+ 1372402382
+ 20130628
+ HASHeaa29d2e.dir
+ word030.png:image/png:
+ word031.png:image/png:
+ word032.png:image/png:
+ word033.png:image/png:
+ word034.png:image/png:
+ word035.png:image/png:
+ doc.doc:application/msword:
+
+
+
+<!--Section Begins--><br>
+
+
+
+<p><div name="Heading 1" align="center" style="margin: 4.17mm 0.50mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b><span style="text-transform:uppercase">Greenstone: A Comprehensive Open-Source Digital Library Software System</span></b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="center" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 3.819444mm; color: Black; background-color: White; ">
+<b></b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="center" style="margin: 1.74mm 0.00mm 1.39mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<i>Ian H. Witten,</i><i><sup>*</sup></i><i> Rodger J. McNab,</i><i><sup>†</sup></i><i> Stefan J. Boddie,</i><i><sup>*</sup></i><i> David Bainbridge</i><i><sup>*</sup></i><i> </i><i><sup></sup></i>
+</p></div>
+
+
+<table width="98.51%" border="1" cols="2" rows="1">
+<tr><td bgcolor="White" width="46.57%" rowspan="1" colspan="1"><p><div name="Normal" align="center" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<sup>*</sup> Dept of Computer Science
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+University of Waikato, New Zealand
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+E-mail: {ihw, sjboddie, davidb}@cs.waikato.ac.nz
+</p></div></td>
+
+
+
+<td bgcolor="White" width="53.43%" rowspan="1" colspan="1"><p><div name="Normal" align="center" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<sup>† </sup>Digilib Systems
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+Hamilton, New Zealand
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+E-mail: rodger@digilibs.com
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<sup></sup>
+</p></div></td>
+
+</tr>
+
+</table>
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+<b></b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+<b></b>
+</p></div>
+
+<!--Section Ends-->
+
+<!--Section Begins--><br>
+
+
+
+<p><div name="Heading 1" align="left" style="margin: 0.00mm 0.49mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b><span style="text-transform:uppercase">Abstract</span></b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+This paper describes the Greenstone digital library software, a comprehensive, open-source system for the construction and presentation of information collections. Collections built with Greenstone offer effective full-text searching and metadata-based browsing facilities that are attractive and easy to use. Moreover, they are easily maintainable and can be augmented and rebuilt entirely automatically. The system is extensible: software “plugins” accommodate different document and metadata types.
+</p></div>
+
+
+
+<p><div name="Heading 1" align="left" style="margin: 4.17mm 0.50mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b><span style="text-transform:uppercase">Introduction</span></b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+Notwithstanding intense research activity in the digital library field during the second half of the 1990s, comprehensive software systems for creating digital libraries are not widely available. In fact, the usual solution when creating a digital library is also the most obvious—just put it on the Web. But consider how much effort is involved in constructing a Web site for a digital library. To be effective it needs to be visually attractive and ergonomically easy to use, incorporate convenient and powerful searching capabilities, and offer rich and natural browsing facilities. Above all it must be easy to maintain and augment, which presents a significant challenge if any manual organization is involved.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+The alternative is to automate these activities through software tools. But the broad scope of digital library requirements makes this a daunting prospect. Ideally the software should incorporate facilities ranging from multilingual information retrieval to distributed computing protocols, from interoperability to search engine technology, from metadata standards to multiformat document parsing, from multimedia to multiple operating systems, from Web browsers to plug-and-play DVDs.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+The Greenstone Digital Library Software from the New Zealand Digital Library (NZDL) project tackles this issue by providing a new way of organizing information and making it available over the Internet. A <i>collection</i> of information comprises several (typically several thousand, or several million) <i>documents</i>, and a uniform interface is provided to all documents in a collection. A library may include many different collections, each organized differently—though there is a strong family resemblance in how collections are presented.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+Making information available using this system is far more than “just putting it on the Web.” The collection becomes maintainable, searchable, and browsable. Each collection, prior to presentation, undergoes a “building” process that, once established, is completely automatic. This process creates all the structures that are used at run-time for accessing the collection. Searching is based on various indexes, while browsing is based on various metadata; support structures for both are created during the building operation. When new material appears it can be fully incorporated into the collection by rebuilding.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+To address the exceptionally broad demands of digital libraries, the system is public and extensible. It is issued under the Gnu public license and, in the spirit of open-source software, users are invited to contribute modifications and enhancements. Only through an international cooperative effort will digital library software become sufficiently comprehensive to meet the world's needs. Currently the Greenstone software is used at sites in Canada, Germany, New Zealand, Romania, UK, and the US, and collections range from newspaper articles to technical documents, from educational journals to oral history, from visual art to folksongs. The software has been used for collections in many different languages, and for CD-ROMs that have been published by the United Nations and other humanitarian agencies in Belgium, France, Japan, and the US for distribution in developing countries (Humanity Libraries, 1998; PAHO, 1999; UNESCO, 1999; UNU, 1998). Further details can be obtained from <i>www.nzdl.org</i>.
+</p></div>
+
+
+
+<p><div name="Caption" align="center" style="margin: 2.08mm 2.74mm 0.00mm 17.26mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -17.26mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<img width="740" height="658" alt="0x01 graphic" src="_httpdocimg_/word030.png"><br>
+</p></div>
+
+
+
+<p><div name="Caption" align="center" style="margin: 2.08mm 2.74mm 0.00mm 17.26mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -17.26mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>Figure </b><b></b><b></b><b></b><b>1</b><b></b><b>: Searching the HDL collection</b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+This paper sets the scene with a brief discussion of what a digital library is. We then give an overview of the facilities offered by Greenstone and show how end users find information in collections. Next we describe the files and directories involved in a collection, and then discuss the processes of updating existing collections and creating new ones, including extending the software to provide new facilities. We conclude with an overview of related work.
+</p></div>
+
+
+
+<p><div name="Heading 1" align="left" style="margin: 4.17mm 0.50mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b><span style="text-transform:uppercase">What is a digital library?</span></b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+Ten definitions of the term “digital library” have been culled from the literature by Fox (1998), and their spirit is captured in the following brief characterization:
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 7.55mm 0.00mm 7.81mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+<i>A collection of digital objects, including text, video, and audio, along with methods for access and retrieval, and for selection, organization and maintenance of the collection</i>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+(Akscyn and Witten, 1998). Lesk (1998) views digital libraries as “organized collections of digital information,” and wisely recommends that they articulate the principles governing what is included and how the collection is organized.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+Digital libraries are generally distinguished from the World-Wide Web, the essential difference being in selection and organization. But they are not generally distinguished from a web <i>site</i>: indeed, virtually all extant digital libraries manifest themselves as a web site. Hence the obvious question: to make a digital library, why not just put the information on the Web?
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+But we make a distinction between a digital library and a web site that lies at the heart of our software design: one should easily be able to add new material to a library without having to integrate it manually or edit its content in any way. Once added, new material should immediately become a first-class component of the library. And what permits it to be integrated into existing searching and browsing structures without any manual intervention is <i>metadata</i>. This provides sufficient focus to the concept of “digital library” to support the development of a construction kit.
+</p></div>
+
+
+
+<p><div name="Heading 1" align="left" style="margin: 4.17mm 0.50mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b><span style="text-transform:uppercase">Overview of Greenstone</span></b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+Information collections built by Greenstone combine extensive full-text search facilities with browsing indexes based on different metadata types. There are several ways for users to find information, although they differ between collections depending on the metadata available and the collection design. Typically you can <i>search for particular words</i> that appear in the text, or within a section of a document, or within a title or section heading. You can <i>browse documents by title</i>: just click on the displayed book icon to read it. You can <i>browse documents by subject</i>. Subjects are represented by bookshelves: just click on a shelf to see the books. Where appropriate, documents come complete with a table of contents (constructed automatically): you can click on a chapter or subsection to open it, expand the full table of contents, or expand the full document.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+An example of searching is shown in Figure 1 where documents in the Global Help Project's Humanity Development Library (HDL) are being searched for chapters matching the word <i>butterfly</i>. In Figure 2 the same collection is being browsed by subject: by clicking on the bookshelf icons the user has discovered an item under Section 16, Animal Husbandry. Pursuing an interest in butterfly farming, the user selects a book by clicking on its book icon. In Figure 3 the front cover of the book is displayed as a graphic on the left, and the automatically constructed table of contents appears at the start of the document. The current focus, <i>Introduction and Summary</i>, is shown in bold in the table of contents with its text starting further down the page.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+In accordance with Lesk's advice, a statement of purpose and coverage accompanies each collection, along with an explanation of how it is organized (Figure 1 shows the start of this). A distinction is made between <i>searching</i> and <i>browsing</i>. Searching is full-text, and—depending on the collection's design—the user can choose between indexes built from different parts of the documents, or from different metadata. Some collections have an index of full documents, an index of sections, an index of paragraphs, an index of titles, and an index of section headings, each of which can be searched for particular words or phrases. Browsing involves data structures created from metadata that the user can examine: lists of authors, lists of titles, lists of dates, hierarchical classification structures, and so on. Data structures for both browsing and searching are built according to instructions in a configuration file, which controls both building and serving the collection. Sample configuration files are discussed below.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<img width="740" height="658" alt="0x01 graphic" src="_httpdocimg_/word031.png"><br><b></b>
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>Figure </b><b></b><b></b><b></b><b>2</b><b></b><b>: Browsing the HDL collection by subject</b><b></b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+Rich browsing facilities can be provided by manually linking parts of documents together and building explicit indexes and tables of contents. However, manually-created linking becomes difficult to maintain, and often falls into disrepair when a collection expands. The Greenstone software takes a different tack: it facilitates <i>maintainability</i> by creating all searching and browsing structures automatically from the documents themselves. No links are inserted by hand. This means that when new documents in the same format become available, they can be added automatically. Indeed, for some collections this is done by processes that wake up regularly, scout for new material, and rebuild the indexes—all without manual intervention.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+Collections comprise many documents: thousands, tens of thousands, or even millions. Each document may be hierarchically organized into <i>sections</i> (subsections, sub-subsections, and so on). Each section comprises one or more <i>paragraphs</i>. Metadata such as author, title, date, keywords, and so on, may be associated with documents, or with individual sections of documents. This is the raw material for indexes. It must either be provided explicitly for each document and section (for example, in an accompanying spreadsheet) or be derivable automatically from the source documents. Metadata is converted to Dublin Core and stored with the document for internal use.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+In order to accommodate different kinds of source documents, the software is organized so that “plugins” can be written for new document types. Plugins exist for plain text documents, HTML documents, email documents, and bibliographic formats. Word documents are handled by saving them as HTML; PostScript ones by applying a preprocessor (Nevill-Manning <i>et al</i>., 1998). Specially written plugins also exist for proprietary formats such as that used by the BBC archives department. A collection may have source documents in different forms: it is just a matter of specifying all the necessary plugins. In order to build browsing indexes from metadata, an analogous scheme of “classifiers” is used: classifiers create indexes of various kinds based on metadata. Source documents are brought into the Greenstone system through a process called <i>importing</i>, which uses the plugins and classifiers specified in the collection configuration file.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+The international Unicode character set is used throughout, so documents—and interfaces—can be written in any language. Collections have so far been produced in English, French, Spanish, German, Maori, Chinese, and Arabic. The NZDL Web site provides numerous examples. Collections can contain text, pictures, and even audio and video clips; a text-only version of the interface is also provided to accommodate visually impaired users. Compression technology is used to ensure best use of storage (Witten <i>et al</i>., 1999). Most non-textual material is either linked to textual documents or accompanied by textual descriptions (such as photo captions) to allow full-text searching and browsing. However, the architecture permits the implementation of plugins and classifiers even for non-textual data.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+The system includes an “administrative” function whereby specified users can examine the composition of all collections, protect documents so that they can only be accessed by registered users on presentation of a password, and so on. Logs of user activity are kept that record all queries made to every Greenstone collection (though this facility can be disabled).
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+Although primarily designed for Internet access over the World-Wide Web, collections can be made available, in precisely the same form, on CD-ROM. In either case they are accessed through any Web browser. Greenstone CD-ROMs operate on a standalone PC under Windows 3.X, 95, 98, and NT, and the interaction is identical to accessing the collection on the Web—except that response is faster and more predictable. The requirement to operate on early Windows systems is one that plagues the software design, but is crucial for many users—particularly those in underdeveloped countries seeking access to humanitarian aid collections. If the PC is connected to a network (intranet or Internet), a custom-built Web server provided on each CD makes exactly the same information available to others through their standard Web browser. The use of compression ensures that the greatest possible volume of information can be packed on to a CD-ROM.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+The collection-serving software operates under Unix and Windows NT, and works with standard Web servers. A flexible process structure allows different collections to be served by different computers, yet be presented to the user in the same way, on the same Web page, as part of the same digital library, even as part of the same collection (McNab and Witten, 1998). Existing collections can be updated and new ones brought on-line at any time, without bringing the system down; the process responsible for the user interface will notice (through periodic polling) when new collections appear and add them to the list presented to the user.
+</p></div>
+
+
+
+<p><div name="Heading 1" align="center" style="margin: 4.17mm 0.50mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b><span style="text-transform:uppercase"><img width="760" height="662" alt="0x01 graphic" src="_httpdocimg_/word032.png"><br></span></b><b><span style="text-transform:uppercase"></span></b>
+</p></div>
+
+
+
+<p><div name="Caption" align="center" style="margin: 2.08mm 2.74mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>Figure </b><b></b><b></b><b></b><b>3</b><b></b><b>: Reading a book in the HDL</b><b></b>
+</p></div>
+
+
+
+<p><div name="Heading 1" align="left" style="margin: 4.17mm 0.50mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b><span style="text-transform:uppercase">Finding information </span></b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+Greenstone digital library systems generally include several separate collections. A home page allows you to select a collection; in addition, each collection has its own “about” page that gives you information about how the collection is organized and the principles governing what is included.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+All icons in the screenshots of Figures 1-4 are clickable. Those icons at the top of the page return to the home page, provide help text, and allow you to set user interface and searching preferences. The navigation bar underneath gives access to the searching and browsing facilities, which differ from one collection to another.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+Each of the five buttons provides a different way to find information. You can <i>search for particular words</i> that appear in the text from the “search” page (or from the “about” page of Figure 1). This collection contains indexes of chapters, section titles, and entire books. The default search interface is a simple one, suitable for casual users; advanced searching—which allows full Boolean expressions, phrase searching, case and stemming control—can be enabled from the <i>Preferences</i> page.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+This collection has four browsable metadata indexes. You can <i>access publications by subject</i> by clicking the <i>subjects</i> button, which brings up a list of subjects, represented by bookshelves (Figure 2). You can <i>access publications by title</i> by clicking <i>titles a-z</i> (Figure 4), which brings up a list of books in alphabetic order. You can <i>access publications by organization</i> (i.e. Dublin Core “publisher”), bringing up a list of organizations. You can <i>access publications by “how to” listing</i>, yielding a list of hints defined by the collection's editors. We use the Dublin Core as a base and extend it in an <i>ad hoc</i> manner to accommodate the individual requirements of collection designers.
+</p></div>
+
+
+
+<p><div name="Heading 1" align="left" style="margin: 4.17mm 0.50mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b><span style="text-transform:uppercase">Files in a collection</span></b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+When a new collection is created or material is added to an existing one, the original source documents are first brought into the system through a process known as “importing.” This involves converting documents into a simple HTML-like format known as GML (for “Greenstone Markup Language”), which includes any metadata associated with the document. Documents are assumed to be in the Unicode UTF-8 code (of which the ASCII characters form a subset).
+</p></div>
+
+
+
+<p><div name="Heading 2" align="left" style="margin: 6.94mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>Files and directories</b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+There is a separate directory for each collection, which contains five subdirectories: the original raw material (<i>import</i>), the GML files created from this (<i>archives</i>), the final collection as it is served to users (<i>index</i>), a directory for use during the building process (<i>building</i>), and one for any supporting files (<i>etc</i>)—including the configuration file that controls the collection creation procedure. Additional files might be required: for example, building a hierarchy of classifications requires a data file of sub-classifications.
+</p></div>
+
+
+
+<p><div name="Heading 2" align="left" style="margin: 6.94mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>The imported documents</b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+In order to identify documents internally, a unique object identifier or OID is assigned to each original source document when it is imported (formed by hashing the content, to overcome file duplication effects caused by mirroring) and stored as metadata within that document. It is important that OIDs persist throughout the index-building process—so that a user's search history is unaffected by rebuilding the collection. OIDs are assigned by hashing the contents of the original source document.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+Once imported, each document is stored in its own subdirectory of <i>archives</i>, along with any associated files—for example, images. To ensure compatibility with Windows 3.0, only eight characters are used in directory and file names, which causes annoying but essentially trivial complications.
+</p></div>
+
+
+
+<p><div name="Heading 2" align="left" style="margin: 6.94mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>Inside the documents</b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+The GML format imposes a limited amount of structure on documents. Documents are divided into paragraphs. They can be split hierarchically into sections and subsections. OIDs are extended to identify these components by appending numbers, separated by periods, to a document's OID. When a book is read, its section hierarchy is visible as the table of contents (Figure 3). Chapters, sections, subsections, and pages are all implemented simply as “sections” within the document. In some collections documents do not have a hierarchical subsection structure, but are split into pages to permit browsing within a retrieved document.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+The document structure is used for searchable indexes. There are three levels of index: <i>documents</i>, <i>sections</i>, and <i>paragraphs</i>, corresponding to the distinctions that GML makes—the hierarchical structure is flattened for the purposes of creating these indexes. Indexes can be of text, or metadata, or any combination. Thus you can create a searchable index of section titles, and/or authors, and/or document descriptions, as well as the document text.
+</p></div>
+
+
+
+<p><div name="Caption" align="center" style="margin: 2.08mm 2.74mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<img width="698" height="698" alt="0x01 graphic" src="_httpdocimg_/word033.png"><br>
+</p></div>
+
+
+
+<p><div name="Caption" align="center" style="margin: 2.08mm 2.74mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>Figure 4</b><b>: Browsing titles in the HDL</b><b></b>
+</p></div>
+
+
+
+<p><div name="Heading 1" align="left" style="margin: 4.17mm 0.50mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b><span style="text-transform:uppercase">Updating existing collections</span></b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+Updating an existing collection with new files in the same format is easy. For example, the raw material for the HDL is supplied in the form of HTML files marked up with <<TOC>> tags to split books into sections and subsections, and <<I>> tags to indicate where an image is to be inserted. For each book in the library there is a directory that contains a single HTML file representing the book, and separate files containing the associated images. An accompanying spreadsheet file contains the classification hierarchy; this is converted to a simple file format (using Excel's <i>Save As</i> command).
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+Since the collection exists, its directory is already set up with subdirectories <i>import</i>, <i>archives</i>, <i>building</i>, <i>index</i>, and <i>etc</i>, and the <i>etc</i> directory will contain a suitable collection configuration file.
+</p></div>
+
+
+
+<p><div name="Heading 2" align="left" style="margin: 6.94mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>The updating procedure</b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+To update a collection, the new raw material is placed in the <i>import</i> directory, in whatever form it is available. Then the <i>import</i> process is invoked, which converts the files into GML using the specified plugins. Old material for which GML files have previously been created is not re-imported. Then the <i>build</i> process is invoked to build the requisite indexes for the collection. Finally, the contents of the <i>building</i> directory are moved into the <i>index</i> directory, and the new version of the collection automatically becomes live.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+This procedure may seem cumbersome. But all the steps are necessary for efficient operation with large collections. The <i>import</i> process could be performed on the fly during the building operation—but because building indexes is a multipass operation, the often lengthy importing would be repeated several times. The <i>build</i> process can take considerable time—a day or two, for very large collections. Consequently, the results are placed in the <i>building</i> directory so that, if the collection already exists, it will continue to be served to users in its old form throughout the building operation.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+Active users of the collection will not be disturbed when the new version becomes live—they will probably not even notice. The persistent OIDs ensure that interactions remain coherent—users who are examining the results of a query or browse operation will still retrieve the expected documents—and if a search is actually in progress when the change takes place the program detects the resulting file-structure inconsistency and automatically and transparently re-executes the query, this time on the new version of the collection.
+</p></div>
+
+
+
+<p><div name="Heading 2" align="left" style="margin: 6.94mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>How it works</b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+The original material in the <i>import</i> directory may be in any format, and plugins are required to process each format type. The plugins that a collection uses must be specified in the collection configuration file. The <i>import</i> program reads the list of plugins and passes each document to each plugin in order until it finds one that can process it. When updating an existing collection, all plugins necessary to process new material should already have been specified in the configuration file.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+The building step creates the indexes for both searching and browsing. The MG software is generally used to do the searching (Witten <i>et al.</i>, 1999), and the <i>mgbuild</i> module is automatically invoked to create each of the indexes that is required. For example, the Humanity Development Library has three indexes, one for entire books, one for chapters, and one for section titles. Subdirectories of the <i>index</i> directory are created for each of these indexes.
+</p></div>
+
+
+<table width="92.93%25" border="1" cols="4" rows="12">
+<tr><td bgcolor="White" width="6.36%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="19.69%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+creator
+</p></div></td>
+
+
+
+<td bgcolor="White" width="64.87%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+davidb@cs.waikato.ac.nz
+</p></div></td>
+
+
+
+<td bgcolor="White" width="9.08%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+1
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="6.36%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="19.69%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+maintainer
+</p></div></td>
+
+
+
+<td bgcolor="White" width="64.87%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+davidb@cs.waikato.ac.nz
+</p></div></td>
+
+
+
+<td bgcolor="White" width="9.08%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+2
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="6.36%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="19.69%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+public
+</p></div></td>
+
+
+
+<td bgcolor="White" width="64.87%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+True
+</p></div></td>
+
+
+
+<td bgcolor="White" width="9.08%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+3
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="6.36%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="19.69%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="64.87%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="9.08%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+4
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="6.36%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="19.69%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+indexes
+</p></div></td>
+
+
+
+<td bgcolor="White" width="64.87%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+document:text
+</p></div></td>
+
+
+
+<td bgcolor="White" width="9.08%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+5
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="6.36%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="19.69%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+defaultindex
+</p></div></td>
+
+
+
+<td bgcolor="White" width="64.87%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+document:text
+</p></div></td>
+
+
+
+<td bgcolor="White" width="9.08%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+6
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="6.36%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="19.69%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+plugins
+</p></div></td>
+
+
+
+<td bgcolor="White" width="64.87%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+GMLPlug TEXTPlug ArcPlug RecPlug
+</p></div></td>
+
+
+
+<td bgcolor="White" width="9.08%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+7
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="6.36%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="19.69%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="64.87%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="9.08%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+8
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="6.36%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="19.69%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+classify
+</p></div></td>
+
+
+
+<td bgcolor="White" width="64.87%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+AZList metadata=Title
+</p></div></td>
+
+
+
+<td bgcolor="White" width="9.08%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+9
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="6.36%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="19.69%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="64.87%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="9.08%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+10
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="6.36%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="19.69%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+collectionmeta
+</p></div></td>
+
+
+
+<td bgcolor="White" width="64.87%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+collectionname "generic text collection"
+</p></div></td>
+
+
+
+<td bgcolor="White" width="9.08%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+11
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="6.36%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+(a)
+</p></div></td>
+
+
+
+<td bgcolor="White" width="19.69%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+collectionmeta
+</p></div></td>
+
+
+
+<td bgcolor="White" width="64.87%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+.document:text "documents"
+</p></div></td>
+
+
+
+<td bgcolor="White" width="9.08%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+12
+</p></div></td>
+
+</tr>
+
+</table>
+
+<p><div name="label" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+<table width="92.93%25" border="1" cols="4" rows="17">
+<tr><td bgcolor="White" width="6.36%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="19.69%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+creator
+</p></div></td>
+
+
+
+<td bgcolor="White" width="64.87%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+davidb@cs.waikato.ac.nz
+</p></div></td>
+
+
+
+<td bgcolor="White" width="9.08%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+1
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="6.36%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="19.69%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+maintainer
+</p></div></td>
+
+
+
+<td bgcolor="White" width="64.87%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+davidb@cs.waikato.ac.nz
+</p></div></td>
+
+
+
+<td bgcolor="White" width="9.08%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+2
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="6.36%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="19.69%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+public
+</p></div></td>
+
+
+
+<td bgcolor="White" width="64.87%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+True
+</p></div></td>
+
+
+
+<td bgcolor="White" width="9.08%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+3
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="6.36%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="19.69%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="64.87%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="9.08%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+4
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="6.36%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="19.69%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+indexes
+</p></div></td>
+
+
+
+<td bgcolor="White" width="64.87%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+document:text document:From
+</p></div></td>
+
+
+
+<td bgcolor="White" width="9.08%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+5
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="6.36%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="19.69%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+defaultindex
+</p></div></td>
+
+
+
+<td bgcolor="White" width="64.87%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+document:text
+</p></div></td>
+
+
+
+<td bgcolor="White" width="9.08%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+6
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="6.36%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="19.69%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+plugins
+</p></div></td>
+
+
+
+<td bgcolor="White" width="64.87%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+GMLPlug EMAILPlug ArcPlug RecPlug
+</p></div></td>
+
+
+
+<td bgcolor="White" width="9.08%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+7
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="6.36%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="19.69%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="64.87%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="9.08%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+8
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="6.36%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="19.69%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+classify
+</p></div></td>
+
+
+
+<td bgcolor="White" width="64.87%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+AZList metadata=Title
+</p></div></td>
+
+
+
+<td bgcolor="White" width="9.08%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+9
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="6.36%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="19.69%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+classify
+</p></div></td>
+
+
+
+<td bgcolor="White" width="64.87%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+DateList
+</p></div></td>
+
+
+
+<td bgcolor="White" width="9.08%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+10
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="6.36%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="19.69%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="64.87%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="9.08%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+11
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="6.36%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="19.69%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+collectionmeta
+</p></div></td>
+
+
+
+<td bgcolor="White" width="64.87%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+collectionname "Email messages"
+</p></div></td>
+
+
+
+<td bgcolor="White" width="9.08%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+12
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="6.36%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="19.69%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+collectionmeta
+</p></div></td>
+
+
+
+<td bgcolor="White" width="64.87%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+.document:text "documents"
+</p></div></td>
+
+
+
+<td bgcolor="White" width="9.08%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+13
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="6.36%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="19.69%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+collectionmeta
+</p></div></td>
+
+
+
+<td bgcolor="White" width="64.87%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+.document:From "email senders"
+</p></div></td>
+
+
+
+<td bgcolor="White" width="9.08%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+14
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="6.36%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="19.69%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="64.87%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="9.08%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+15
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="6.36%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="19.69%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+format
+</p></div></td>
+
+
+
+<td bgcolor="White" width="64.87%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+QueryResults /
+</p></div></td>
+
+
+
+<td bgcolor="White" width="9.08%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+16
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="6.36%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+(b)
+</p></div></td>
+
+
+
+<td bgcolor="White" width="19.69%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="64.87%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<td>[link][icon][/link]</td><td>[Title]</td><td>[Author]</td>
+</p></div></td>
+
+
+
+<td bgcolor="White" width="9.08%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+17
+</p></div></td>
+
+</tr>
+
+</table>
+
+<p><div name="label" align="center" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>Figure 5: Collection configuration files (a) generic, (b) for an email collection</b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+MG also compresses the text of the collection; and the image files are linked into the <i>index</i> subdirectory. Now none of the material in the <i>import</i> and <i>archives</i> directories is needed to run the collection and can be removed from the file system (though they would be needed if the collection were rebuilt).
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+Associated with each collection is a database stored in GDBM (Gnu database manager) format. This contains an entry for each document, giving its OID, its internal MG document number, and metadata such as title. Information for each of the browsing indexes, which appear as buttons on the Greenstone search/browse bar, is also extracted during the building process and stored in the database. A “classifier” program is required for each browsing index to extract the appropriate information from GML documents. Like plugins, classifiers are written on an <i>ad hoc</i> basis for the particular information required, and where possible reused from one collection to another.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+The building program creates the indexes based on whatever appears in the <i>archives</i> directory. The first plugin specified by all collections is one that processes GML files, and so if <i>archives</i> contains imported files they will be processed correctly. If it contains material in the original format, that will be converted using the appropriate plugin. Thus the import process is optional.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+GML is designed to be fast and easy to parse, an important requirement when millions of documents are to be processed. Something as simple as requiring tags to be lower-case, for example, yields a substantial speed-up. In certain circumstances, however, it might be preferable to use a standardized format such as XML. This is straightforward to implement_just write an XML plugin_although we have not done so ourselves. Given the transitory nature of the imported data, to date, we have found GML a satisfactory and beneficial format.
+</p></div>
+
+
+
+<p><div name="Heading 1" align="left" style="margin: 4.17mm 0.50mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b><span style="text-transform:uppercase">Creating new collections</span></b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+Building new collections from scratch is only slightly different from updating an existing collection. The key new requirement is creating a collection configuration file, and a software utility is provided to help. Two pieces of information are required for this: the name of the directory that the collection will use (into which the source data and other files will eventually be placed), and a contact e-mail address for use if any problems are encountered by the software once the collection is up and running. The utility creates files and directories within the newly-named directory to support a generic collection of plain text documents. With suitable data placed in the <i>import</i> directory, building the collection at this point will yield a document-level searchable index of all the text and a browsable list of “titles” (defined in this case to be the document filenames).
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+To enhance the functionality and presentation— something anything but the most trivial collection will require—the configuration file must be edited. For a collection sourced from documents in an already supported data format, presented in a similar fashion to an existing collection, the amount of editing is minimal. Importing new data formats and browsing metadata in ways not currently supported are more complex activities that require programming skills.
+</p></div>
+
+
+
+<p><div name="Caption" align="center" style="margin: 2.08mm 2.74mm 0.00mm 17.26mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -17.26mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<img width="698" height="698" alt="0x01 graphic" src="_httpdocimg_/word034.png"><br>
+</p></div>
+
+
+
+<p><div name="Caption" align="center" style="margin: 2.08mm 2.74mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>Figure 6</b><b>: Searching bookmarked Web pages</b><b><i></i></b>
+</p></div>
+
+
+
+<p><div name="Heading 2" align="left" style="margin: 6.94mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>Modifying the configuration file</b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+Figure 5b shows simple alterations to the generic configuration file in Figure 5a that was generated by the new-collection utility. <i>TEXTPlug</i> is replaced with <i>EMAILPlug</i> (line 7) which reads email files and extracts metadata (<i>From</i>, <i>To</i>, <i>Date</i>, <i>Subject</i>) from them. A classifier for dates is added (line 10) to make the collection browsable chronologically. The default presentation of search results is overridden (line 17) to display both the title of the message (i.e. Dublin Core <i>Title</i>) and its sender (i.e. Dublin Core <i>Author</i>). Elements in square brackets, such as <i>[Title]</i>, are replaced by the metadata associated with a particular document. The built-in term <i>[icon]</i> produces a suitable image that represents the document (such as a book icon or page icon), and the <i>[link]…[/link]</i> construct forms a hyperlink to the complete document. Anything else in the format statement, which in this case is solely table-cell tags in HTML, is passed through to the page being displayed.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+As this example shows, creating a new collection that stays within the bounds of the library's established capabilities falls within the capability of many computer users—for instance, computer-trained librarians. Extending Greenstone to handle new document formats and browse metadata in new ways is more challenging.
+</p></div>
+
+
+
+<p><div name="Heading 2" align="left" style="margin: 6.94mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>Writing new plugins and classifiers</b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+Extensibility is obtained through plugins and classifiers.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+These are modules of code that can be slotted into the system to enhance its capabilities. Plugins parse documents, extracting the text and metadata to be indexed. Classifiers control how metadata is brought together to form browsable data structures. Both are specified in an object-oriented framework using inheritance to minimize the amount of code written.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+A plugin must specify three things: what file formats it can handle, how they should be parsed, and whether the plugin is recursive. File formats are normally determined using regular expression matching on the filename. For example, the HTML plugin accepts all files that end in <i>.htm</i>, .<i>html</i>, <i>.HTM</i>, or <i>.HTML</i>. (It is quite possible, however, to write plugins that “look inside” the file as well.) For other files, the plugin returns <i>undefined</i> and the file is passed to the next plugin in the collection's configuration file (e.g. Figure 5 line 7). If it can, the plugin parses the file and returns the number of documents processed. This involves extracting text and metadata and adding it to the library's content through calls to <i>add text</i> and <i>add metadata</i>.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+Some plugins (“recursive” ones) add extra files into the stream of data processed during the building phase by artificially reactivating the list of plugins. This is how directory hierarchies are traversed.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+Plugins are small modules of code that are easy to write. We monitored the time it took to develop a new one that was different to any we had produced so far. We chose to make as an example a collection of HTML bookmark files, the motivation being to produce a convenient way of searching and browsing one's bookmarked Web pages. Figure 6 shows a user searching for bookmarked pages about <i>music</i>. The new plugin took under an hour to write, and was 160 lines long (ignoring blank lines and comments)—about the average length of existing plugins.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+Classifiers are more general than plugins because they work on GML-format data. For example, any plugin that generates date metadata in accordance with the Dublin core can request the collection to be browsable chronologically by specifying the <i>DateList</i> classifier in the collection's configuration file (Figure 7). Classifiers are more elaborate than most plugins, but new ones are seldom required. The average length of existing classifiers is 230 lines.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+Classifiers must specify three things: an initialization routine, how individual documents are classified, and the final browsable data structure. Initialization takes care of any options specified in the configuration file (such as <i>metadata=Title </i>on line 9 of Figure 5b). Classifying individual documents is an iterative process: for each one, a call to <i>document-classify</i> is made. On presentation of the document's OID, the necessary metadata is located and used to control where the document is added to the browsable data structure being constructed.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+Once all documents have been added, a request is made for the completed data structure. Some classifiers return the data structure directly; others transform the data structure before it is returned. For example, the <i>AZList</i> classifier divides the alphabetically sorted list of metadata into separate pages of about the same size and returns the alphabetic ranges for each one (Figure 4).
+</p></div>
+
+
+
+<p><div name="Caption" align="center" style="margin: 2.08mm 2.74mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<img width="698" height="698" alt="0x01 graphic" src="_httpdocimg_/word035.png"><br>
+</p></div>
+
+
+
+<p><div name="Caption" align="center" style="margin: 2.08mm 2.74mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>Figure 7</b><b>: Browsing a newspaper collection by date</b><b></b>
+</p></div>
+
+
+
+<p><div name="Heading 1" align="left" style="margin: 4.17mm 0.50mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b><span style="text-transform:uppercase">Overview of related work</span></b>
+</p></div>
+
+
+
+<p><div name="Plain Text" align="left" style="margin: 2.08mm 0.24mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Two projects that provide substantial open source digital library software are Dienst (Lagoze and Fielding, 1998) and Harvest (Bowman <i>et al.</i>, 1994). The origins of Dienst (<i>www.cs.cornell.edu/cdlrg</i>) stretch back to 1992. The term has come to represent three entities: a conceptual architecture for distributed digital libraries; an open protocol for service communication; and a software system that implements the protocol. To date, five sample digital libraries have been built using this technology. They manifest themselves in two forms: technical reports and primary source documents.
+</p></div>
+
+
+
+<p><div name="Plain Text" align="left" style="margin: 2.08mm 0.24mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Best known is NCSTRL, the Networked Computer Science Technical Reference Library project (<i>www.ncstrl.org</i>). This collection facilitates searching by title, author and abstract, and browsing by year and author, across a distributed network of document repositories. Documents can (where supported) be delivered in various formats such as PostScript, a thumbnail overview of the pages, and a GIF image of a particular page.
+</p></div>
+
+
+
+<p><div name="Plain Text" align="left" style="margin: 2.08mm 0.24mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The <i>Making of America</i> resource is an example of a collection based around primary sources_in this case American social history, 1830â1900. It has a different “look and feel” to NCSTRL, being strongly oriented toward browsing rather than searching. A user navigates their way through a hierarchical structure of hyperlinks to reach a book of interest. The book itself is a series of scanned images: delivery options include going directly to a page number, next and previous page buttons, and displaying a particular page at different resolutions. A text version of the page is also available upon which a searching option is also provided.
+</p></div>
+
+
+
+<p><div name="Plain Text" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Started in 1994, Harvest is also a long-running research project. It provides an efficient means of gathering source data from the Internet and distributing indexing information over the Internet. This is accomplished through five components: <i>gatherer</i>, <i>broker</i>, <i>indexer</i>, <i>replicator</i> and <i>cache</i>. The first three are central to creating, updating and searching a collection; the last two help to improve performance over the Internet through transparent mirroring and caching techniques.
+</p></div>
+
+
+
+<p><div name="Plain Text" align="left" style="margin: 2.08mm 0.24mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The system is configurable and customizable. While searching is most commonly implemented using Glimpse (<i>glimpse.cs.arizona.edu</i>), in principle any search engine that supports incremental updates and Boolean combinations of attribute-based queries can be used. It is possible to control what type of documents are gathered during creation and updating, and how the query interface looks and is laid out.
+</p></div>
+
+
+
+<p><div name="Plain Text" align="left" style="margin: 2.08mm 0.24mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Sample collections cited by the developers include 21,000 computer science technical reports and 7,000 home pages. Other examples include a sizable collection of agriculture-related electronic journals and magazines called “tomato-juice” (accessed through <i>hegel.lib.ncsu.edu</i>) and a full-text index of library-related electronic serials (<i>sunsite.berkeley.edu/IndexMorganagus</i>). Harvest is also often used to index Web sites (for example <i>www.middlebury.edu</i>).
+</p></div>
+
+
+
+<p><div name="Plain Text" align="left" style="margin: 2.08mm 0.24mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Comparing Greenstone with Dienst and Harvest, there are both similarities and differences. All provide substantial digital library systems, hence common themes recur, but they are driven by projects with different aims. Harvest, for instance, was not conceived as a digital library project at all, but by virtue of its selective document gathering process it can be classed (and is used) as one. While it provides sophisticated search options, it lacks the complementary service of browsing. Furthermore it adds no structure or order to the documents collected, relying on whatever structures are present in the site that they were gathered from. A proven strength of the design is its flexibility through configuration and customization_an element also present in Greenstone.
+</p></div>
+
+
+
+<p><div name="Plain Text" align="left" style="margin: 2.08mm 0.24mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Dienst_best exemplified through the NCSTRL work_supports searching and browsing, like Greenstone. Both use open protocols. Differences include a high reliance in Dienst on user-supplied information when a document is added, and a smaller range of document types supported—although Dienst does include a document model that should, over time, allow this to expand with relative ease.
+</p></div>
+
+
+
+<p><div name="Plain Text" align="left" style="margin: 2.08mm 0.24mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+There are also commercial systems that provide similar digital library services to those described. However, since corporate culture instills proprietary attitudes there is little opportunity for advancement through a shared collaborative effort. Consequently they are not reviewed here.
+</p></div>
+
+
+
+<p><div name="Heading 1" align="left" style="margin: 4.17mm 0.50mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b><span style="text-transform:uppercase">Conclusions</span></b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+Greenstone is a comprehensive software system for creating digital library collections. It builds data structures for searching and browsing from the material provided, rather than relying on any hand-crafting. The process is controlled by a configuration file, and once a collection exists new material can be added completely automatically. Browsing is based on Dublin Core metadata.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+New collections can be developed easily, particularly if they resemble existing ones. Extensibility is achieved through software “plugins” that can be written to accommodate documents, and metadata, in different formats. Standard plugins exist for many document types; new ones are easily written. Browsing is controlled by “classifiers” that process metadata into browsing structures (by date, alphabetical, hierarchical, etc).
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+However, the most powerful support for extensibility is achieved not by technical means but by making the source code freely available under the Gnu public license. Only through an international cooperative effort will digital library software become sufficiently comprehensive to meet the world's needs with the richness and flexibility that users deserve.
+</p></div>
+
+
+
+<p><div name="Heading 1" align="left" style="margin: 4.17mm 0.50mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b><span style="text-transform:uppercase">Acknowledgments</span></b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 3.819444mm; color: Black; background-color: White; ">
+We gratefully acknowledge all those who have worked on the Greenstone software, and all members of the New Zealand Digital Library project for their enthusiasm and ideas.
+</p></div>
+
+
+
+<p><div name="Heading 1" align="left" style="margin: 0.00mm 0.49mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b><span style="text-transform:uppercase">References</span></b>
+</p></div>
+
+
+
+<ol type="1">
+<li value="1"><p><div name="References" align="left" style="margin: 1.04mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Akscyn, R.M. and Witten, I.H. (1998) “Report on First Summit on International Cooperation on Digital Libraries.” ks.com/idla-wp-oct98.
+</p></div></li>
+
+
+
+<li value="2"><p><div name="References" align="left" style="margin: 1.04mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Bowman, C.M., Danzig, P.B., Manber, U., and Schwartz, M.F. “Scalable Internet resource discovery: Research problems and approaches” <i>Communications of the ACM,</i> Vol. 37, No. 8, pp. 98â107, 1994.
+</p></div></li>
+
+
+
+<li value="3"><p><div name="References" align="left" style="margin: 1.04mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Fox, E. (1998) “Digital library definitions.” ei.cs.vt.edu/~fox/dlib/def.html.
+</p></div></li>
+
+
+
+<li value="4"><p><div name="References" align="left" style="margin: 1.04mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Humanity Libraries (1998) <i>Humanity Development Library</i>. CD-ROM produced by the Global Help Project, Antwerp, Belgium.
+</p></div></li>
+
+
+
+<li value="5"><p><div name="References" align="left" style="margin: 1.04mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Lagoze, C. and Fielding, D “Defining Collections in Distributed Digital Libraries” <i>D-Lib Magazine</i>, Nov. 1998.
+</p></div></li>
+
+
+
+<li value="6"><p><div name="References" align="left" style="margin: 1.04mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+PAHO (1999) <i>Virtual Disaster Library</i>. CD-ROM produced by the Pan-American Health Organization, Washington DC, USA.
+</p></div></li>
+
+
+
+<li value="7"><p><div name="References" align="left" style="margin: 1.04mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+McNab, R.J., Witten, I.H. and Boddie, S.J. (1998) “A distributed digital library architecture incorporating different index styles.” <i>Proc IEEE Advances in Digital Libraries</i>, Santa Barbara, CA, pp. 36-45.
+</p></div></li>
+
+
+
+<li value="8"><p><div name="References" align="left" style="margin: 1.04mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Nevill-Manning, C.G., Reed, T., and Witten, I.H. (1998) “Extracting text from PostScript” <i>Software—Practice and Experience</i>, Vol. 28, No. 5, pp. 481-491; April.
+</p></div></li>
+
+
+
+<li value="9"><p><div name="References" align="left" style="margin: 1.04mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+UNESCO (1999) <i>SAHEL point DOC: Anthologie du développement au Sahel</i>. CD-ROM produced by UNESCO, Paris, France.
+</p></div></li>
+
+
+
+<li value="10"><p><div name="References" align="left" style="margin: 1.04mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+UNU (1998) <i>Collection on critical global issues.</i> CD-ROM produced by the United Nations University Press, Tokyo, Japan.
+</p></div></li>
+
+
+
+<li value="11"><p><div name="References" align="left" style="margin: 1.04mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Witten, I.H., Moffat, A. and Bell, T. (1999) <i>Managing Gigabytes: compressing and indexing documents and images</i>, Morgan Kaufmann, second edition.
+</p></div></li>
+
+
+
+</ol><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Header" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<span style="text-transform:lowercase"></span>
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Footer" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<span style="text-transform:lowercase"></span>
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Caption" align="center" style="margin: 2.08mm 2.74mm 0.00mm 17.26mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -17.26mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Caption" align="center" style="margin: 2.08mm 2.74mm 0.00mm 17.26mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -17.26mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Caption" align="center" style="margin: 2.08mm 2.74mm 0.00mm 17.26mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -17.26mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+<!--Section Ends-->
+
+
+
+<!--
+<hr>
+<address>
+<a href="_httpextlink_&rl=0&href=http:%2f%2fwvware.sourceforge.net"><img
+src="_httpdocimg_/wvSmall.gif" height=31 width=47
+align=left border=0 alt="wvWare"></a>
+<a href="_httpextlink_&rl=0&href=http:%2f%2fvalidator.w3.org%2fcheck%2freferer"><img
+src="_httpdocimg_/vh40.gif" height=31 width=88
+align=right border=0 alt="Valid HTML 4.0!"></a>
+Document created with <a href="_httpextlink_&rl=0&href=http:%2f%2fwvware.sourceforge.net">wvWare/wvWare version 1.2.4</a><br>
+</address>
+-->
+
+
+
+
+
Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/HASHeaa2a12e.dir/doc.xml
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/HASHeaa2a12e.dir/doc.xml (revision 27727)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/HASHeaa2a12e.dir/doc.xml (revision 27727)
@@ -0,0 +1,5438 @@
+
+
+
+
+
+ indexed_doc
+ en
+ utf8
+ wvWare/wvWare version 1.2.4
+ How to build your own digital library with Greenstone
+ http://research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402382/word05.html
+ http://research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402382/word05.html
+ import/word05.doc
+ tmp/1372402382/word05.html
+ word05.html
+ word05.doc
+ word05.doc
+ WordPlugin
+ 488960
+ word05
+ Word
+ _icondoc_
+ doc.doc
+ doc.doc
+ Ian H. Witten
+ Stefan J. Boddie
+ GREENSTONE DIGITAL LIBRARY INSTALLERâS GUIDE
+ HASHeaa2a12e080949673150f3
+ 1372400870
+ 20130628
+ 1372402383
+ 20130628
+ HASHeaa2a12e.dir
+ word050.wmf:unknown:
+ word051.png:image/png:
+ word052.png:image/png:
+ word053.jpg:image/jpeg:
+ word054.jpg:image/jpeg:
+ word055.jpg:image/jpeg:
+ word056.jpg:image/jpeg:
+ word057.jpg:image/jpeg:
+ word058.jpg:image/jpeg:
+ word059.jpg:image/jpeg:
+ doc.doc:application/msword:
+
+
+
+<!--Section Begins--><br>
+
+
+
+<p><div name="paragraph" align="right" style="margin: 0.00mm 0.00mm 8.33mm 39.06mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="DarkGray"><b><img alt="0x08 graphic" src=""><br></b></font><font color="DarkGray"><b>GREENSTONE DIGITAL LIBRARY</b></font><font color="DarkGray"><b> </b></font><b>INSTALLER'S GUIDE</b><font color="Black"><b></b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="right" style="margin: 0.00mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b></b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="right" style="margin: 0.00mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b></b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="right" style="margin: 0.00mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b></b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="right" style="margin: 0.00mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>Ian H. Witten and Stefan Boddie</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="right" style="margin: 0.00mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b></b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="right" style="margin: 0.00mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><i>Department of Computer Science<br>University of Waikato, New Zealand</i></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 0.00mm 0.00mm 0.00mm 34.50mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Greenstone is a suite of software for building and distributing digital library collections. It provides a new way of organizing information and publishing it on the Internet or on CD-ROM. Greenstone is produced by the New Zealand Digital Library Project at the University of Waikato, and developed and distributed in cooperation with UNESCO and the Human Info NGO. It is open-source software, available from <i>http://greenstone.org</i> under the terms of the G<span style="text-transform:lowercase">nu</span> General Public License.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 4.17mm 0.00mm 0.00mm 51.68mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="right" style="margin: 6.94mm 0.00mm 0.00mm 49.22mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black">We want to ensure that this software works well for you. Please report any problems to </font><font color="Black"><i>greenstone@cs.waikato.ac.nz</i></font>
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+<!--Section Ends-->
+
+<!--Section Begins--><br>
+
+
+
+<p><div name="SectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 7.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -7.38mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>About this manual</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+This document explains how to install Greenstone so that you can run it on your own computer. It also describes how to obtain associated software that is freely available—the Apache Webserver and Perl. We have striven to make the installation procedure as simple as it possibly can be.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The software runs on different platforms, and in different configurations. Consequently there are many issues that affect (or might affect) the installation procedure. Section 1 mentions some questions that you will need to consider before installing Greenstone. Section 2 details the installation procedure for all the different versions; you need only read the part that relates to your operating system. Section 3 describes the demonstration digital library collections that are included in the distribution. Section 4 explains how to set up common webservers, Apache and Microsoft PWS/IIS, to work with Greenstone. Section 5 describes various Greenstone configuration options, and Section 6 shows how to make a personalized home page for your digital library installation. Finally, an Appendix lists pieces of associated software and how to obtain them.
+</p></div>
+
+
+
+<p><div name="Plain Text" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>Companion documents</b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The complete set of Greenstone documents include five volumes:
+</p></div>
+
+
+
+<ul>
+<li value="1"><p><div name="bulleted list" align="left" style="margin: 2.08mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Greenstone Digital Library Installer's Guide <i>(this document)</i>
+</p></div></li>
+
+
+
+<li value="2"><p><div name="bulleted list" align="left" style="margin: 0.00mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Greenstone Digital Library User's Guide
+</p></div></li>
+
+
+
+<li value="3"><p><div name="bulleted list" align="left" style="margin: 0.00mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Greenstone Digital Library Developer's Guide
+</p></div></li>
+
+
+
+<li value="4"><p><div name="bulleted list" align="left" style="margin: 0.00mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Greenstone Digital Library: From Paper to Collection
+</p></div></li>
+
+
+
+<li value="5"><p><div name="bulleted list" align="left" style="margin: 0.00mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Greenstone Digital Library: Using the Organizer
+</p></div></li>
+
+
+
+</ul><p><div name="Plain Text" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b><b>Acknowledgements</b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The Greenstone software is a collaborative effort between many people. Rodger McNab and Stefan Boddie are the principal architects and implementors. Contributions have been made by David Bainbridge, George Buchanan, Hong Chen, Michael Dewsnip, Katherine Don, Elke Duncker, Carl Gutwin, Geoff Holmes, Dana McKay, John McPherson, Craig Nevill-Manning, Dynal Patel, Gordon Paynter, Bernhard Pfahringer, Todd Reed, Bill Rogers, John Thompson, and Stuart Yeates. Other members of the New Zealand Digital Library project provided advice and inspiration in the design of the system: Mark Apperley, Sally Jo Cunningham, Matt Jones, Steve Jones, Te Taka Keegan, Michel Loots, Malika Mahoui, Gary Marsden, Dave Nichols and Lloyd Smith. We would also like to acknowledge all those who have contributed to the GNU-licensed packages included in this distribution: <font color="Black"><span style="text-transform:lowercase">MG, GDBM, PDFTOHTML, </span></font><font color="Black"><span style="text-transform:lowercase">PERL, </span></font><font color="Black"><span style="text-transform:lowercase">WGET, WVWARE </span></font>and<font color="Black"><span style="text-transform:lowercase"> XLHTML.</span></font><font color="Black"><span style="text-transform:lowercase"></span></font>
+</p></div>
+
+
+
+<p><div name="TOA" align="right" style="margin: 12.50mm 0.00mm 12.50mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<span style="text-transform:uppercase"></span><span style="text-transform:uppercase">Contents</span>
+</p></div>
+
+
+
+<p><div name="TOC 2" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b><b></b><b></b><b>About this manual</b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b>
+</p></div>
+
+
+
+<p><div name="TOC 1" align="left" style="margin: 6.25mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b>
+</p></div>
+
+
+
+<p><div name="TOC 1" align="left" style="margin: 6.25mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b>
+</p></div>
+
+
+
+<p><div name="TOC 2" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b>
+</p></div>
+
+
+
+<p><div name="TOC 3" align="left" style="margin: 0.00mm 0.00mm 0.00mm 9.84mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="TOC 3" align="left" style="margin: 0.00mm 0.00mm 0.00mm 9.84mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="TOC 3" align="left" style="margin: 0.00mm 0.00mm 0.00mm 9.84mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="TOC 3" align="left" style="margin: 0.00mm 0.00mm 0.00mm 9.84mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="TOC 2" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b>
+</p></div>
+
+
+
+<p><div name="TOC 3" align="left" style="margin: 0.00mm 0.00mm 0.00mm 9.84mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="TOC 3" align="left" style="margin: 0.00mm 0.00mm 0.00mm 9.84mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="TOC 3" align="left" style="margin: 0.00mm 0.00mm 0.00mm 9.84mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="TOC 3" align="left" style="margin: 0.00mm 0.00mm 0.00mm 9.84mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="TOC 2" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b>
+</p></div>
+
+
+
+<p><div name="TOC 3" align="left" style="margin: 0.00mm 0.00mm 0.00mm 9.84mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="TOC 3" align="left" style="margin: 0.00mm 0.00mm 0.00mm 9.84mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="TOC 3" align="left" style="margin: 0.00mm 0.00mm 0.00mm 9.84mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="TOC 3" align="left" style="margin: 0.00mm 0.00mm 0.00mm 9.84mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="TOC 2" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b>
+</p></div>
+
+
+
+<p><div name="TOC 3" align="left" style="margin: 0.00mm 0.00mm 0.00mm 9.84mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="TOC 3" align="left" style="margin: 0.00mm 0.00mm 0.00mm 9.84mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="TOC 3" align="left" style="margin: 0.00mm 0.00mm 0.00mm 9.84mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="TOC 3" align="left" style="margin: 0.00mm 0.00mm 0.00mm 9.84mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="TOC 2" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b>
+</p></div>
+
+
+
+<p><div name="TOC 3" align="left" style="margin: 0.00mm 0.00mm 0.00mm 9.84mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="TOC 2" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b>
+</p></div>
+
+
+
+<p><div name="TOC 1" align="left" style="margin: 6.25mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b>
+</p></div>
+
+
+
+<p><div name="TOC 1" align="left" style="margin: 6.25mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b>
+</p></div>
+
+
+
+<p><div name="TOC 2" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b>
+</p></div>
+
+
+
+<p><div name="TOC 3" align="left" style="margin: 0.00mm 0.00mm 0.00mm 9.84mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="TOC 3" align="left" style="margin: 0.00mm 0.00mm 0.00mm 9.84mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="TOC 3" align="left" style="margin: 0.00mm 0.00mm 0.00mm 9.84mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="TOC 2" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b>
+</p></div>
+
+
+
+<p><div name="TOC 1" align="left" style="margin: 6.25mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b>
+</p></div>
+
+
+
+<p><div name="TOC 2" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b>
+</p></div>
+
+
+
+<p><div name="TOC 2" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b>
+</p></div>
+
+
+
+<p><div name="TOC 1" align="left" style="margin: 6.25mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b>
+</p></div>
+
+
+
+<p><div name="TOC 2" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b>
+</p></div>
+
+
+
+<p><div name="TOC 2" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b>
+</p></div>
+
+
+
+<p><div name="TOC 2" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b>
+</p></div>
+
+
+
+<p><div name="TOC 1" align="left" style="margin: 6.25mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b><b><span style="text-transform:uppercase"></span></b>
+</p></div>
+
+
+
+<p><div name="TOC 2" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b>
+</p></div>
+
+
+
+<p><div name="TOC 2" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b>
+</p></div>
+
+
+
+<p><div name="TOC 2" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b><span style="text-transform:uppercase"></span></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b>
+</p></div>
+
+
+
+<p><div name="TOC 2" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b>
+</p></div>
+
+
+
+<p><div name="TOC 2" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b>
+</p></div>
+
+
+
+<p><div name="TOC 2" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b><b></b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Heading 1" align="right" style="margin: 12.50mm 0.00mm 12.50mm 43.75mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b></b></font>
+</p></div>
+
+<!--Section Ends-->
+
+<!--Section Begins--><br>
+
+
+
+<p><div name="ChapterTitle" align="right" style="margin: 12.50mm 0.00mm 12.50mm 43.75mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>1<br>Versions of Greenstone</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The Greenstone software runs on different platforms, and in different configurations, as summarized in Figure 1.
+</p></div>
+
+
+
+<p><div name="Normal" align="right" style="margin: 0.00mm 0.00mm 0.00mm -9.84mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: White; background-color: White; ">
+<img width="576" height="19" alt="0x01 graphic" src="_httpdocimg_/word050.wmf"><br>
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style="margin: 2.08mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<img alt="0x08 graphic" src=""><br>Figure 1 The different options for Windows and Unix versions of Greenstone
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+There are many issues that affect (or might affect) the installation procedure. Before reading on, you should consider these questions:
+</p></div>
+
+
+
+<ul>
+<li value="6"><p><div name="bulleted list" align="left" style="margin: 2.08mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Are you using Windows or Unix?
+</p></div></li>
+
+
+
+<li value="7"><p><div name="bulleted list" align="left" style="margin: 0.00mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+If Windows, are you using Windows 3.1/3.11 or a more recent version? Although you can view collections on 3.1/3.11 machines, and serve other computers on the same network, you cannot build new collections. The full Greenstone software runs on 95/98/Me, and NT/2000.
+</p></div></li>
+
+
+
+<li value="8"><p><div name="bulleted list" align="left" style="margin: 0.00mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+If Unix, are you using Linux or another version of Unix? For Linux, a binary version of the complete system is provided which is easy to install. For other types of Unix you will have to install the source code and compile it. This may require you to install some additional software on your machine.
+</p></div></li>
+
+
+
+<li value="9"><p><div name="bulleted list" align="left" style="margin: 0.00mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+If Windows NT/2000 or Unix, can you log in as the system “administrator” or “root”? This may be required to configure a webserver appropriately for Greenstone.
+</p></div></li>
+
+
+
+<li value="10"><p><div name="bulleted list" align="left" style="margin: 0.00mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Do you want the source code? If you are using Windows or Linux, you can just install binaries. But you may want the source code as well—it's in the Greenstone distribution.
+</p></div></li>
+
+
+
+<li value="11"><p><div name="bulleted list" align="left" style="margin: 0.00mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Do you want to build new digital library collections? If so, you need to have Perl, which is freely available for both Windows and Unix.
+</p></div></li>
+
+
+
+<li value="12"><p><div name="bulleted list" align="left" style="margin: 0.00mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Is your computer running a webserver? The Greenstone software comes with a Windows webserver. However, if you are already running a Web server, you may want to stay with it. For Unix, you need to run a webserver.
+</p></div></li>
+
+
+
+<li value="13"><p><div name="bulleted list" align="left" style="margin: 0.00mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Do you know how to reconfigure your webserver? If you don't use the Greenstone webserver, you will have to reconfigure your existing one slightly to recognize the Greenstone software.
+</p></div></li>
+
+
+
+</ul><p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="ChapterTitle" align="right" style="margin: 12.50mm 0.00mm 12.50mm 43.75mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b></b></font>
+</p></div>
+
+<!--Section Ends-->
+
+<!--Section Begins--><br>
+
+
+
+<p><div name="ChapterTitle" align="right" style="margin: 12.50mm 0.00mm 12.50mm 43.75mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>2<br>The Installation Procedure</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Versions of Greenstone are available for both Windows and Unix, as binaries and in source code form. The Greenstone user interface uses a Web browser: Netscape Navigator or Internet Explorer (version 4.0 or greater in both cases) are both suitable. In case you don't already have a Web browser, Windows versions of Netscape are provided on the CD-ROM.
+</p></div>
+
+
+
+<p><div name="SectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 7.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -7.38mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>2.1Windows</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+If you are a Unix user, please skip ahead to Section 2.2. For Windows users, if you want just a simple, straightforward installation, go through the following “simple installation” procedure. The Greenstone system occupies about 40 Mb of disk space.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+If you choose anything other than the default setup, you will have to decide whether you want to install the binary code or the source code. If in doubt, choose the binary code. The installation procedure is the same for both. The following sections tell you more about the options you will be presented with.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+When you've finished installation you should skip ahead to Section 2.3.
+</p></div>
+
+
+
+<p><div name="SubsectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>Simple installation</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+To install the Windows version from the CD-ROM, insert the disk into the drive (e.g. into <i>D:</i>). If the installation procedure does not start automatically after about 20 seconds, click on the <i>Start</i> menu, select <i>Run</i> and type <i>D:/setup.exe</i>, where “<i>D</i>” is the letter that identifies your CD-ROM drive. For Windows 3.1, select <i>Run</i> from the “File manager” and type <i>D:/Windows/win3.1/setup.exe</i>.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+For the simplest installation, just accept the default at each point by clicking the <i>Next</i> button. That's all you need to do! Greenstone is installed in the directory <i>C:/Program Files/gsdl</i>.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Once installation is complete, to start your Greenstone system click on the <i>Start</i> button, open the <i>Program </i>menu, and select <i>Greenstone Digital Library</i>. This brings up a dialogue box: just click <i>Enter Library. </i>This automatically starts your Internet browser and loads the Greenstone Digital Library home page, which should look something like the example in Figure 2. You enter the Greenstone Demo collection by clicking on its icon.
+</p></div>
+
+
+<table width="100.00%25" border="1" cols="2" rows="2">
+<tr><td bgcolor="White" width="26.01%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Figure 2<br>Your Greenstone home page
+</p></div></td>
+
+
+
+<td bgcolor="White" width="73.99%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<img width="669" height="555" alt="0x01 graphic" src="_httpdocimg_/word051.png"><br>
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="26.01%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="73.99%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+</tr>
+
+</table>
+
+<p><div name="SubsectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>Windows binaries</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+There are two separate Windows binary programs on the CD-ROM: the <i>Local Library</i> and the <i>Web Library</i>. The default installation described above selects the Local Library version. We strongly recommend that you use this version. The Web Library, which is much harder to set up, is only necessary if you already run a web server and want to use it for Greenstone. Despite its modest name, the Local Library offers a complete, self-contained, web-serving capability.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>Local Library.</b> This enables any Windows computer to serve pre-built Greenstone collections. The Greenstone Demo collection will automatically be installed; you can also install the other collections on the CD-ROM (Section 3). The Local Library software is the same as that used on CD-ROMs produced by the Greenstone system.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The Local Library is intended for use on standalone computers or computers that do not already have webserver software. It contains a small built-in webserver so that other computers on the same network can also access the library. (However, the webserver has limited configurability.)
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The Local Library software automatically determines whether your computer has network software installed or is connected to a network. It operates correctly under any combinations of these conditions. However, there are two possible problems that may be encountered. Greenstone may
+</p></div>
+
+
+
+<ul>
+<li value="14"><p><div name="bulleted list" align="left" style="margin: 2.08mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+cause an unwanted telephone dialup operation;
+</p></div></li>
+
+
+
+<li value="15"><p><div name="bulleted list" align="left" style="margin: 0.00mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+fail to run because network software is installed, but installed incorrectly.
+</p></div></li>
+
+
+
+</ul><p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+A restricted version of the Local Library is supplied which is intended for use in these situations. The restricted version only works with Netscape (not Internet Explorer). When you invoke the Local Library version of Greenstone, the dialogue box contains a button that allows you to use the restricted version instead. Unless the above problems arise, you should always use the standard version.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>Web Library</b>. This enables any computer with an existing webserver to serve pre-built Greenstone collections. As with the Local Library above, the Greenstone Demo collection will automatically be installed. You can also install the other collections on the CD-ROM (see Section 3).
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The Web Library differs from the Local Library because it is intended for computers that already have webserver software.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+To run the Web Library, you also need
+</p></div>
+
+
+
+<ul>
+<li value="16"><p><div name="bulleted list" align="left" style="margin: 2.08mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Webserver software. One possibility is Apache (see Appendix).
+</p></div></li>
+
+
+
+<li value="17"><p><div name="bulleted list" align="left" style="margin: 2.08mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>The Collector</b>. This component, which is included in both the Local Library and the Web Library, allows you to build collections containing material of your choice. (You will not be able to use the Collector on a Windows 3.1/3.11 machine.)
+</p></div></li>
+
+
+
+</ul><p><div name="SubsectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>Windows webserver configuration (Web Library version only)</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+An advantage of the Local Library version of Greenstone is that it runs “out of the box” and does not require any special configuration. For the Web Library version, however, you will have to make some adjustments to your webserver setup.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+If you already have a webserver, some small changes have to be made to its configuration to make your Greenstone installation operate. The install script explains what these are for the Apache webserver—see Section 4.2 for instructions for configuring the PWS and IIS webservers. You may need help from a system administrator to reconfigure an existing webserver—they should be able to understand the instructions printed by the install script.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+If you do not already have a webserver, you will have to install one. (See the Appendix for information on the Apache webserver.) Then you will have to configure it appropriately. Section 4 gives a detailed account of the parts of a webserver installation that affect Greenstone, and how they need to be altered. It comes down to including half a dozen or so lines in a configuration file.
+</p></div>
+
+
+
+<p><div name="SubsectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>Windows source</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The Greenstone source code occupies 50 Mb of disk space, but to compile it you will need about 90 Mb. To compile the source on Windows you need
+</p></div>
+
+
+
+<ul>
+<li value="18"><p><div name="bulleted list" align="left" style="margin: 2.08mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The Microsoft Visual C++ compiler. (We are currently sorting out some minor problems in compiling Greenstone with various Windows ports of GNU GCC.)
+</p></div></li>
+
+
+
+</ul><p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+(You do not need GDBM, the Gnu database manager, because it is included in the Greenstone source distribution.)
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+It is unlikely that you will be able to compile Greenstone on a Windows 3.1/3.11 machine.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+In the event that you recompile Greenstone and wish to use the recompiled version to create CD-ROMs, you should note that code produced by recent versions of the Visual C++ compiler does not run under Windows 3.1/3.11, although there is no problem with later Windows systems (95, 98, Me, NT, 2000). If you want your CD-ROMs to operate on early Windows machines, you will need a different version of the compiler. Moreover, Greenstone uses STL, the C++ standard template library, and although these compilers sometimes come with STL, the provided version does not always work properly. Hence to recompile Greenstone in such a way that it produces CD-ROMs that work on early versions of Windows, you need
+</p></div>
+
+
+
+<ul>
+<li value="19"><p><div name="bulleted list" align="left" style="margin: 2.08mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The Microsoft Visual C++ compiler, Version 4.0 or 4.2.
+</p></div></li>
+
+
+
+<li value="20"><p><div name="bulleted list" align="left" style="margin: 0.00mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+An external version of STL, the C++ standard template library. STL is packaged with Greenstone for use with these compiler versions.
+</p></div></li>
+
+
+
+</ul><p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Note that the Windows installation procedure does not attempt to compile Greenstone for you if you choose to install the source code. For platform- and compiler-specific instructions on compiling Greenstone, see the <i>Install.txt </i>document which is placed in the top-level Greenstone directory (<i>C:/Program Files/gsdl</i> by default) during the installation procedure.
+</p></div>
+
+
+
+<p><div name="SectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 7.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -7.38mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>2.2Unix</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+This section is written for Unix users. (Windows users should skip ahead to Section 2.3.) You need to choose whether to install the binary code or the source code. The binary code occupies about 50 Mb of disk space; the source code requires about 160 Mb to compile.
+</p></div>
+
+
+
+<p><div name="SubsectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>Unix binaries</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The binary code requires an Intel x86-based Linux distribution which includes ELF binary support. Distributions that meet these requirements include:
+</p></div>
+
+
+
+<ul>
+<li value="21"><p><div name="bulleted list" align="left" style="margin: 2.08mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+RedHat 5.1
+</p></div></li>
+
+
+
+<li value="22"><p><div name="bulleted list" align="left" style="margin: 0.00mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+SuSE Linux 6.1
+</p></div></li>
+
+
+
+<li value="23"><p><div name="bulleted list" align="left" style="margin: 0.00mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Debian 2.1
+</p></div></li>
+
+
+
+<li value="24"><p><div name="bulleted list" align="left" style="margin: 0.00mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Slackware 4.0
+</p></div></li>
+
+
+
+</ul><p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+More recent versions of these distributions should also work.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+You will need a webserver: we recommend Apache. We also strongly recommend you to install your webserver <i>before</i> installing Greenstone—this will make it much easier to answer the questions that are asked during the Greenstone installation procedure. If you want to build new digital library collections, you will also need Perl if this is not already on your system. To check, open a terminal window, type <i>perl -v</i>, and see if a message appears specifying, amongst other things, the version number. For most versions of Linux, Perl is installed by default. The Appendix gives information on how to obtain Apache and Perl.
+</p></div>
+
+
+
+<p><div name="SubsectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>Unix source</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The source code is the same for Unix as for Windows. It has been compiled and tested on Linux, Solaris, and Macintosh OS/X; it should be a fairly routine matter to port it to other flavors of Unix.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+To compile the Greenstone source code on Unix, you need
+</p></div>
+
+
+
+<ul>
+<li value="25"><p><div name="bulleted list" align="left" style="margin: 2.08mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+GCC, the Gnu C++ compiler.
+</p></div></li>
+
+
+
+<li value="26"><p><div name="bulleted list" align="left" style="margin: 0.00mm 0.00mm 0.00mm 6.25mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+GDBM, the Gnu database manager.
+</p></div></li>
+
+
+
+</ul><p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+To run the Greenstone software, you also need a Web server and Perl, as described above under <i>Unix binaries</i>.
+</p></div>
+
+
+
+<p><div name="SubsectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>Unix installation</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+To install the Unix version from the CD-ROM, insert the disk into the drive, and type
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 66.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -27.08mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+mount /cdrommount the CD-ROM device (this command may differ from one system to another; for example on OS/X you <i>cd</i> to the <i>/Volumes</i> directory and then to the appropriate subdirectory for the CD-ROM)
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 0.00mm 0.00mm 0.00mm 66.44mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -27.07mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+cd /cdromchange directory to the CD-ROM's top level
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 0.00mm 0.00mm 0.00mm 66.44mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -27.07mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+cd Unixchange directory to where the Unix install script resides
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 0.00mm 0.00mm 0.00mm 66.44mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -27.07mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+sh Install.shbegin the installation process (an explicit <i>sh</i> is used because many installations forbid you to execute programs directly from CD-ROM)
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The final command begins an interactive dialogue which requests the information that is needed to install Greenstone on your system, and gives detailed feedback on what is happening.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The installation procedure begins by asking you which directory to install Greenstone into. The first file placed there is the “uninstall” program that cleans up any partial installation, should you encounter problems or terminate the installation prematurely. Next you choose whether you want to install binaries or source code. You are then asked some questions about your webserver setup. You need to have a valid cgi executable directory (normally called “cgi-bin” on Unix systems); you can either create a new one or use your existing one. If you create a new one, you will need to enter this information in your webserver's configuration file. In either case you need to enter the web address of the cgi directory. The installation dialogue will guide you through all these choices. It is important to set the file permissions correctly on certain directories, and you are prompted for the necessary information. Finally, you are prompted for a password for the “administrator” user <i>admin</i>.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+By default, all Greenstone software is installed in the directory <i>/usr/local/gsdl</i> if it is the root user who is doing the installation, and into the directory ~<i>/gsdl</i> otherwise (where “~” is the user's home directory).
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Installing the binaries takes just a few minutes, enough time for you to answer the appropriate questions. If you install the source code, the installation script will compile it, which takes from ten minutes to an hour or so, depending on the speed of your processor.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+To uninstall the software, type
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 66.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -27.08mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+cd ~/gsdlor <i>/usr/local/gsdl</i> if it was the root user who installed Greenstone
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 0.00mm 0.00mm 0.00mm 66.44mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -27.07mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+sh Uninstall.sh
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+During the installation procedure you will be asked whether you want to install any Greenstone collections. The Greenstone Demo collection is installed automatically; other collections on the CD-ROM are described in Section 3.
+</p></div>
+
+
+
+<p><div name="SubsectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>Unix webserver configuration</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+If you already have a webserver, some small changes will have to be made to its configuration to make your Greenstone installation operate. The install script explains what these are. You will probably need help from your system administrator to reconfigure the webserver—he or she should be able to understand the instructions output by the install script. For your convenience, the output of the install script is written to a file called INSTALL_RECORD in the directory into which you installed Greenstone.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+If you do not already have a webserver, you will have to install one. The Appendix gives information on Apache. Then you will have to configure it appropriately. Section 4 gives a detailed account of the parts of an Apache webserver installation that affect Greenstone, and how they need to be altered. It comes down to including half a dozen or so lines in a configuration file.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+You do not need to be the Unix “root” user to go through the installation procedure above. When it comes to configuring an existing Apache server, however, you may need “root” privileges—it all depends on how Apache is set up. If you install Apache yourself, you can do it as a user without “root” privileges. If you need to work your way around an uncooperative system administrator, you can always install a second Apache webserver on your computer—even if one exists already.
+</p></div>
+
+
+
+<p><div name="SectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 7.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -7.38mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>2.3How to find Greenstone</b></font>
+</p></div>
+
+
+
+<p><div name="SubsectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>Local library (Windows only)</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+If you are using the Local Library, simply run the <i>Greenstone</i> program from the <i>Start</i> menu. This automatically opens a dialog box that starts your Internet browser and loads the Greenstone Digital Library home page. The Greenstone Demo collection should be accessible from this page. The dialog box contais a<i> File</i> menu item that allows you to change the default browser used by Greenstone. It doesn't matter whether you use Netscape or Internet Explorer, except that if you are running on Windows 2000, we recommend that you use Internet Explorer.
+</p></div>
+
+
+
+<p><div name="SubsectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>Web library (Windows and Unix)</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+If you are using the Web Library, once you have installed the software and configured the webserver, use this URL to enter your Greenstone system:
+</p></div>
+
+
+
+<p><div name="bulleted list" align="left" style="margin: 2.08mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -2.47mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<i>http://localhost/gsdl/cgi-bin/library</i>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The Greenstone Demo collection should be accessible from this page.
+</p></div>
+
+
+
+<p><div name="SubsectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>The Collector</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+A link to the Collector is provided on the digital library home page.
+</p></div>
+
+
+
+<p><div name="SubsectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>Administration</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+A link to the Administration pages is provided on the digital library home page. The “administrator” user is called <i>admin</i>, with a password that you specified during the installation process. The administrator is authorized to add new users, and to build collections.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="SectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 7.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -7.38mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>2.4The Greenstone Librarian Interface (GLI)</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The Greenstone Librarian Interface (GLI) is a tool to assist you with building digital libraries using Greenstone. It gives you access to Greenstone's collection-building functionality from an easy-to-use “point and click” interface.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+GLI is installed automatically with all distributions of Greenstone. It is placed in the subdirectory <i>gli</i> of the top-level Greenstone directory (<i>C:/Program Files/gsdl/gli</i> by default). Note that it runs in conjunction with Greenstone and will not work properly unless it is placed in a subdirectory of your Greenstone installation. If you have downloaded one of the Greenstone distributions, this will be the case.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+To use the GLI, your computer needs to have the Java Runtime Environment. If it doesn't, the installer will offer to install a version that is included on the CD-ROM. On Unix, you will also need to ensure that Perl is installed (for Windows, Perl is already included in the Greenstone software). Please report any problems you have running or using the Librarian Interface to <font color="Blue"><u>greenstone@cs.waikato.ac.nz</u></font>.
+</p></div>
+
+
+
+<p><div name="SubsectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>Running under Windows </b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+To run GLI under Windows, browse to the <i>gli</i> folder in your Greenstone installation (e.g. using Windows Explorer), and double-click on the file called <i>gli.bat</i>. This file checks that Greenstone, the Java Runtime Environment, and Perl are all installed, and starts the Greenstone Librarian Interface.
+</p></div>
+
+
+
+<p><div name="SubsectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>Running under Unix </b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+To run GLI under Unix, change to the <i>gli </i>directory in your Greenstone installation, then run the <i>gli.sh</i> script. This script checks that Greenstone, the Java Runtime Environment, and Perl are all installed and on your search path, and starts the Greenstone Librarian Interface.
+</p></div>
+
+
+
+<p><div name="SubsectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>Getting help</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The Greenstone Librarian Interface has extensive on-line help facilities. You get help by clicking the <i>Help</i> button at the top right of the screen. This opens up the text to a section that relates to what you are doing—which of the GLI panels you are on. You can click around the help text to learn what you need to know. Use it.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 0.00mm 0.00mm 0.00mm 34.50mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="SubsectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>Compiling the Greenstone Librarian Interface</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+If you have downloaded the Greenstone source distribution, you will have the Java source code of the Librarian Interface. To compile it, your computer needs to have a <font color="Black">Java Development Kit</font>. The Appendix gives information on how to obtain this. To compile the source code, run the <i>makegli.bat</i> (Windows) or <i>makegli.sh</i> (Unix) files. Once compiled, you can run GLI as described above.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="SectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 7.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -7.38mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>2.5Testing and troubleshooting</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+To test Greenstone, point your Web browser at the Greenstone home page and explore the Demo collection and any other collections that you have installed. Don't worry—you can't break anything. Click liberally: most images that appear on the screen are clickable. If you hold the mouse stationary over an image, most browsers will soon pop up a message that tells you what will happen if you click. Experiment! Choose common words like “the” and “and” to search for—that should evoke some responses, and nothing will break. For more information, see the <i>Greenstone Digital Library User's Guide</i>.<i></i>
+</p></div>
+
+
+
+<p><div name="SubsectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>Troubleshooting </b></font>
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+<table width="100.00%25" border="1" cols="3" rows="5">
+<tr><td bgcolor="White" width="25.01%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b>
+</p></div></td>
+
+
+
+<td bgcolor="White" width="28.57%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>Problem</b>
+</p></div></td>
+
+
+
+<td bgcolor="White" width="46.42%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>Try this</b>
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="25.01%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<span style="text-transform:lowercase">Local Library (Windows only)</span>
+</p></div></td>
+
+
+
+<td bgcolor="White" width="28.57%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+When I start Greenstone my computer asks me to dial up my Internet Service Provider.
+</p></div></td>
+
+
+
+<td bgcolor="White" width="46.42%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Push the <i>Cancel</i> button in the dialog box. This usually solves the problem.
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="25.01%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="28.57%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+When I start Greenstone my computer <i>still</i> asks me to dial up my Internet Service Provider.
+</p></div></td>
+
+
+
+<td bgcolor="White" width="46.42%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Choose the “Restricted version” when you run Greenstone. This version only works with Netscape.
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="25.01%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="28.57%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+When I point my browser at the digital library, it can't find that page.
+</p></div></td>
+
+
+
+<td bgcolor="White" width="46.42%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Check your Internet Proxy settings and turn proxies off (use <i>Edit preferences</i> on Netscape or <i>Internet options</i> on Explorer).
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="25.01%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="28.57%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The Collector seems to be working very slowly!
+</p></div></td>
+
+
+
+<td bgcolor="White" width="46.42%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Are you using Netscape under Windows 2000? If so, try using Internet Explorer instead—on Windows 2000 (only) there seems to be some incompatibility with Netscape.
+</p></div></td>
+
+</tr>
+
+</table>
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+<table width="100.00%25" border="1" cols="3" rows="8">
+<tr><td bgcolor="White" width="25.01%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b>
+</p></div></td>
+
+
+
+<td bgcolor="White" width="28.57%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>Problem</b>
+</p></div></td>
+
+
+
+<td bgcolor="White" width="46.42%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>Try this</b>
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="25.01%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<span style="text-transform:lowercase">Web Library (Windows and Unix)</span>
+</p></div></td>
+
+
+
+<td bgcolor="White" width="28.57%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+When I start Apache, it quits immediately.
+</p></div></td>
+
+
+
+<td bgcolor="White" width="46.42%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Add a <i>ServerName localhost</i> directive to the Apache configuration file (see Section 4.1).
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="25.01%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="28.57%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+When I point my browser at the digital library, it displays garbage—a binary file.
+</p></div></td>
+
+
+
+<td bgcolor="White" width="46.42%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Check the <i>ScriptAlias</i> directive in the Apache configuration file, making sure it comes before the <i>Alias</i> directive (see Sections 4.2 and 4.3).
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="25.01%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<span style="text-transform:lowercase"></span>
+</p></div></td>
+
+
+
+<td bgcolor="White" width="28.57%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+I get the Greenstone home page (Figure 2), but the Demo collection icon does not appear.
+</p></div></td>
+
+
+
+<td bgcolor="White" width="46.42%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Run the program <i>library</i> (in the cgi-bin directory) from the DOS (or shell) prompt to generate debugging information that will help you locate the problem.
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="25.01%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<span style="text-transform:lowercase">Both versions</span>
+</p></div></td>
+
+
+
+<td bgcolor="White" width="28.57%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+When I point my browser at the digital library, it can't find that page.
+</p></div></td>
+
+
+
+<td bgcolor="White" width="46.42%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Try using 127.0.0.1 in place of <i>localhost</i>. This reserved IP number is defined to be a “loopback” to your local computer.
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="25.01%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<span style="text-transform:lowercase"></span>
+</p></div></td>
+
+
+
+<td bgcolor="White" width="28.57%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+My browser complains that it can't find <i>main.cfg</i><i>.</i>
+</p></div></td>
+
+
+
+<td bgcolor="White" width="46.42%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Check that the Greenstone files exist and are world-readable. If you are using the Web library, try running the <i>library</i> program from the command line. If it runs OK, the problem is with file permissions (see Section 5.1). If not, the <i>gsdlhome</i> variable is probably set incorrectly in the <i>gsdlsite.cfg</i> configuration file (see Section 5.2).
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="25.01%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="28.57%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+I'm having trouble using the Collector.
+</p></div></td>
+
+
+
+<td bgcolor="White" width="46.42%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Read the <i>Greenstone Digital Library User's Guide</i>, Section 3.
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="25.01%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="28.57%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+I've added a new user but they can't seem to log in.
+</p></div></td>
+
+
+
+<td bgcolor="White" width="46.42%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Check that the directory <i>C:/Program Files/gsdl/etc</i> and all its contents are globally writeable (see Section 5.1).
+</p></div></td>
+
+</tr>
+
+</table>
+
+<p><div name="SectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 7.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -7.38mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>2.6To learn more</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+To learn more about the innards of your Greenstone installation, consult the <i>Greenstone Digital Library Developer's Guide</i>. It includes (for example) details of the directory structure that has been created, and information about how to configure your Greenstone site.
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+<!--Section Ends-->
+
+<!--Section Begins--><br>
+
+
+
+<p><div name="ChapterTitle" align="right" style="margin: 12.50mm 0.00mm 12.50mm 43.75mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>3<br>Greenstone Collections</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Several demonstration Greenstone collections are included on the CD-ROM. If you have Web access, many others can be downloaded, in either pre-built or unbuilt form, from the New Zealand Digital Library Project website (<i>nzdl.org</i>).
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The Greenstone Demo collection is a small subset of the Humanity Development Library (HDL), a polished collection. It illustrates that relatively rich browsing capabilities can be provided (so long as suitable metadata is available). It is included automatically when the software is installed.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 2.08mm 34.50mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Greenstone also comes with some well-documented example collections whose “about” page describes how they are constructed. They demonstrate various capabilities of Greenstone. The install dialogue will ask you whether you want to include them in your Greenstone installation; the approximate amount of disk space needed for each collection is shown below.
+</p></div>
+
+
+<table width="100.00%25" border="1" cols="3" rows="12">
+<tr><td bgcolor="White" width="24.25%25" rowspan="1" colspan="1"><p><div name="paragraph" align="right" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<i>demo</i>
+</p></div></td>
+
+
+
+<td bgcolor="White" width="24.25%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Greenstone Demo<br>(7Â Mb)
+</p></div></td>
+
+
+
+<td bgcolor="White" width="51.50%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+A small subset of the HDL. If you clone this collection, the full facilities will only appear if your new files provide appropriate metadata information.
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="24.25%25" rowspan="1" colspan="1"><p><div name="Normal" align="right" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<i>dls-e</i>
+</p></div></td>
+
+
+
+<td bgcolor="White" width="24.25%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Development Library Subset collection <br>(150 Mb)
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="51.50%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Like the Greenstone Demo, this is a subset of the HDL—but much larger. It contains 250 publications—books, reports and magazines—in various areas of human development (the full HDL contains 1,230 publications). It has the same structure as the Greenstone Demo. It's fairly complex, and if you're just starting out you might prefer to look at some other collections first (e.g. <i>MSWord and PDF demonstration</i>, the <i>Greenstone Archives</i>, or the <i>Simple image collection</i>).
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="24.25%25" rowspan="1" colspan="1"><p><div name="paragraph" align="right" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<i>wrdpdf-e</i>
+</p></div></td>
+
+
+
+<td bgcolor="White" width="24.25%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+MSWord and PDF demonstration <br>(4 Mb)
+</p></div></td>
+
+
+
+<td bgcolor="White" width="51.50%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+This contains a few documents in PDF, MSWord, RTF, and Postscript formats, demonstrating the ability to build collections from documents in different formats. The collection configuration file is very simple.
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="24.25%25" rowspan="1" colspan="1"><p><div name="Normal" align="right" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<i>gsarch-e </i>
+</p></div></td>
+
+
+
+<td bgcolor="White" width="24.25%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Greenstone Archives collection <br>(5 Mb)
+</p></div></td>
+
+
+
+<td bgcolor="White" width="51.50%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+A collection of email messages from the Greenstone mailing list archives, this uses the Email plugin, which parses files in email formats. The collection configuration file is very simple.
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="24.25%25" rowspan="1" colspan="1"><p><div name="Normal" align="right" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<i>cltbib-e</i>
+</p></div></td>
+
+
+
+<td bgcolor="White" width="24.25%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Bibliography collection <br>(7 Mb)
+</p></div></td>
+
+
+
+<td bgcolor="White" width="51.50%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+With about 4,000 bibliography entries, this collection incorporates a form-based search interface that allows fielded searching. It is fairly complex.
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="24.25%25" rowspan="1" colspan="1"><p><div name="Normal" align="right" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<i>cltext-e</i>
+</p></div></td>
+
+
+
+<td bgcolor="White" width="24.25%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Bibliography supplement <br>(1 Mb)
+</p></div></td>
+
+
+
+<td bgcolor="White" width="51.50%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+This tiny collection of 10 bibliography entries illustrates the "supercollection" facility which searches several collections together, seamlessly. It operates together with the <i>Bibliography</i> collection, and its configuration file is almost the same.
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="24.25%25" rowspan="1" colspan="1"><p><div name="paragraph" align="right" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<i>MARC-e</i>
+</p></div></td>
+
+
+
+<td bgcolor="White" width="24.25%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+MARC example <br>(1 Mb)
+</p></div></td>
+
+
+
+<td bgcolor="White" width="51.50%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Based on some MARC records from the Library of Congress, this is a simple collection (and does not allow form-based searching).
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="24.25%25" rowspan="1" colspan="1"><p><div name="Normal" align="right" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<i>oai-e</i>
+</p></div></td>
+
+
+
+<td bgcolor="White" width="24.25%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+OAI demo collection <br>(18 Mb)
+</p></div></td>
+
+
+
+<td bgcolor="White" width="51.50%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Using the Open Archive Protocol and the <i>Import-From</i> feature, this retrieves metadata from an archive and builds a collection from the records. In this case they are images, so both the OAI and Image plugins are used.
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="24.25%25" rowspan="1" colspan="1"><p><div name="paragraph" align="right" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<i>image-e</i>
+</p></div></td>
+
+
+
+<td bgcolor="White" width="24.25%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Simple image collection <br>(1 Mb)
+</p></div></td>
+
+
+
+<td bgcolor="White" width="51.50%25" rowspan="1" colspan="1"><p><div name="figure" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+This very basic image collection contains no text and no explicit metadata—which makes it rather unrealistic. The configuration file is about as simple as you can get.
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="24.25%25" rowspan="1" colspan="1"><p><div name="paragraph" align="right" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<i>authen-e</i>
+</p></div></td>
+
+
+
+<td bgcolor="White" width="24.25%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Formatting and authentication demo <br>(8 Mb)
+</p></div></td>
+
+
+
+<td bgcolor="White" width="51.50%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+With the same material as the original Greenstone demo collection, this shows off two independent features: non-standard document formatting, and controlled access to the documents via user authentication.
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="24.25%25" rowspan="1" colspan="1"><p><div name="paragraph" align="right" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<i>garish</i>
+</p></div></td>
+
+
+
+<td bgcolor="White" width="24.25%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Garish version of demo collection <br>(8 Mb)
+</p></div></td>
+
+
+
+<td bgcolor="White" width="51.50%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+This collection also contains the same material as the Greenstone demo. Its appearance has been altered to show how the pages generated can be set out differently. It relies on a non-standard macro file that is supplied with Greenstone.
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="24.25%25" rowspan="1" colspan="1"><p><div name="paragraph" align="right" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<i>isis-e</i><i></i>
+</p></div></td>
+
+
+
+<td bgcolor="White" width="24.25%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+CDS/ISIS example (1 Mb)
+</p></div></td>
+
+
+
+<td bgcolor="White" width="51.50%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+This collection is built from a CDS/ISIS database of about 150 bibliography entries. It uses the ISISPlug plugin, which reads the standard ISIS .mst and .fdt files and converts them to Greenstone metadata.
+</p></div></td>
+
+</tr>
+
+</table>
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="ChapterTitle" align="right" style="margin: 12.50mm 0.00mm 12.50mm 43.75mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b></b></font>
+</p></div>
+
+<!--Section Ends-->
+
+<!--Section Begins--><br>
+
+
+
+<p><div name="ChapterTitle" align="right" style="margin: 12.50mm 0.00mm 12.50mm 43.75mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>4<br>Setting up the Webserver</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+In this section we describe how to set up your webserver to work with Greenstone. Note that all this is unnecessary when using the Windows Local Library, because this software works “out of the box” and does not require a webserver.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+We discuss both the Apache webserver, which is freely available for both Windows and Unix (see the Appendix for details) and Microsoft's Personal Web Server (PWS) and Internet Information Services (IIS) webserver. PWS is the standard Microsoft server for Windows 95/98; IIS is the standard webserver for Windows 2000 and the forthcoming Windows XP; Windows NT can use either. The Apache description applies equally to the Windows Web Library and Unix versions (though we use Windows-style terminology and pathnames); the PWS/IIS section applies only to the Windows Web Library.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Once you have installed your webserver, the next step is to install Greenstone. We will assume that during the install procedure you have taken the default action for each stage by clicking on the <i>Next</i> button. The result is that the directory <i>C:/Program Files/gsdl</i> is created and the Web Library binary is stored there, along with some supporting files.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+All webservers use the special URL “localhost” to denote the computer that the webserver is running on. Thus when you install a webserver, you can get at your <span style="text-transform:lowercase">html</span> documents by typing the URL <i>http://localhost</i> into a browser. If your computer has a domain name set up, this is used instead of localhost to identify your computer from remote sites. Thus on the New Zealand Digital Library's computer, <i>http://nzdl.org</i> and <i>http://localhost</i> are equivalent. If you type <i>http://nzdl.org</i> on your computer you will get the New Zealand Digital Library webserver, whereas if you type <i>http://localhost</i> you will get your own computer's webserver.
+</p></div>
+
+
+
+<p><div name="SectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 7.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -7.38mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>4.1The Apache web server</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The Apache webserver is usually installed in <i>C:/Program Files/Apache Group/Apache</i> and is configured so that the cgi-bin directory is in the subdirectory <i>/cgi-bin</i> and the document root is the subdirectory <i>/htdocs</i>. It is reconfigured by editing the configuration file <i>C:/Program Files/Apache Group/Apache/conf/httpd.conf</i>. This is a text file: it's quite easy to read it to see how things are set up.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Depending on how your computer's networking software is set up, you may have to add this line to Apache's <i>httpd.conf</i> configuration file:
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 2.08mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+ServerName localhost
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+If this line is not included, the system attempts to find your server's name. However, there are bugs in some versions of Windows that cause this to fail. In this case, Apache will exit immediately when you start it up. It does display an error message, but it is immediately erased and you probably can't read it.
+</p></div>
+
+
+
+<p><div name="SubsectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>Setting up the Greenstone cgi-bin directory</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Cgi-bin is a directory from which the webserver treats documents as executable programs. Apache's <i>ScriptAlias</i> directive is used to create a cgi-bin directory. Note that this directive can make any directory a cgi executable directory—it doesn't have to be called “cgi-bin”! Conversely, a directory called “cgi-bin” isn't special unless <i>ScriptAlias</i> has been applied to it.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+When installed, Apache has a cgi-bin directory of <i>C:/Program Files/Apache Group/Apache/cgi-bin</i>. This means that if presented with the URL <i>http://localhost/cgi-bin/hello</i>, the webserver will attempt to execute a file called <i>hello</i> from within the above directory.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+There is one Greenstone program, which is called “library.exe”, that needs to be executed by the webserver; it in turn reads a file called the Greenstone site configuration file, or “gsdlsite.cfg”, which needs to be located in the same directory.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The best way of arranging this is to use Apache's <i>ScriptAlias</i> directive to create a new cgi-bin directory. Here's the excerpt from Apache's <i>httpd.conf</i> configuration file that adds <i>C:/Program Files/gsdl/cgi-bin</i> as an additional cgi-bin directory:
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 2.08mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+ScriptAlias /gsdl/cgi-bin/ "C:/Program Files/gsdl/cgi-bin/"
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<Directory C:/Program Files/gsdl/cgi-bin>
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+ Options None
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+ AllowOverride None
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+</Directory>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+(It's a curious fact that Apache configuration files use forward slashes in place of standard Windows backslashes.)
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+This means that any URLs of the form <i>http://localhost/gsdl/cgi-bin</i> ... will be sought in the directory <i>C:/Program Files/gsdl/cgi-bin</i>, and executed by the web server. For example, if presented with the URL <i>http://localhost/gsdl/cgi-bin/hello</i>, the web server will attempt to retrieve the file <i>C:/Program Files/gsdl/cgi-bin/hello</i> and execute it. However, the URL <i>http://localhost/cgi-bin/hello</i> looks in Apache's regular <i>cgi-bin</i> directory for the file <i>C:/Program Files/Apache Group/Apache/</i><i>cgi-bin</i><i>/hello</i> and executes it, just as it did before.
+</p></div>
+
+
+
+<p><div name="SubsectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>The document root directory</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The document root directory is the root of your webserver's directory structure. When installed, Apache has a document root <i>of C:/Program Files/Apache Group/Apache/htdocs</i>. This means that if presented with the URL <i>http://localhost/hello.html</i>, the webserver will attempt to retrieve a file called <i>hello.html</i> from within the above directory.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Several files within Greenstone need to be read by the webserver. The simplest way to arrange this is to use the <i>Alias</i> directive, which is just like <i>ScriptAlias</i> except that it applies to ordinary web pages, not cgi scripts. Insert these lines into your Apache configuration file, after the <i>ScriptAlias</i> directive, to add <i>C:/Program Files/gsdl</i> as an additional place to look for documents.
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 2.08mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Alias /gsdl/ "C:/Program Files/gsdl/"
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<Directory C:/Program Files/gsdl>
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+ Options Indexes MultiViews FollowSymLinks
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+ AllowOverride None
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+ Order allow,deny
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+ Allow from all
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+</Directory>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+This means that any URLs that match the first argument of Alias (gsdl) are sought as files in the place corresponding to the second argument. In other words, URLs of the form <i>http://localhost/gsdl/</i> ... will be sought as files in the directory <i>C:/Program Files/gsdl</i>. For example, if presented with the URL <i>http://localhost/gsdl/hello.html</i>, the webserver will attempt to retrieve the file <i>C:/Program Files/gsdl/hello.html</i>. However, the URL <i>http://localhost/hello.html</i> looks in the regular <i>htdocs</i> directory for the file <i>C:/Program Files/Apache Group/Apache/htdocs/hello.html</i>, just as it did before.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Be sure to add the <i>Alias</i> directive after the <i>ScriptAlias</i> directive. Instructing Apache to alias <i>/gsdl </i>before<i> /gsdl/cgi-bin</i> would match the URL <i>/gsdl/cgi-bin/library</i> against the Alias directive rather than the ScriptAlias, and it would be interpreted as a request for a document rather than the result of executing a program. The outcome would be to “display” the binary program file as a page in the Web browser, instead of executing it.
+</p></div>
+
+
+
+<p><div name="SubsectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>Security</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+You should be aware that if the web library version of Greenstone is set up as instructed above, anyone will be allowed to download any file in the <i>gsdl</i> directory structure. This includes the index files and source documents of any collections you make, the user database, usage logs, etc.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+If you are concerned about this, you can easily tighten up your webserver configuration to improve security. For the Apache webserver, put these lines into the configuration file instead of those given in the previous subsection:
+</p></div>
+
+
+
+<p><div name="code line" align="left" style="margin: 2.08mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Alias /gsdl/ "C:/Program Files/gsdl/"
+</p></div>
+
+
+
+<p><div name="code line" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<Directory "C:/Program Files/gsdl">
+</p></div>
+
+
+
+<p><div name="code line" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+ Order allow,deny
+</p></div>
+
+
+
+<p><div name="code line" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+ Deny from all
+</p></div>
+
+
+
+<p><div name="code line" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+ <FilesMatch
+</p></div>
+
+
+
+<p><div name="code line" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+"/.(gif|jpe?g|png|css|mov|mpeg|ps|pdf|doc|rtf|jar|class)$">
+</p></div>
+
+
+
+<p><div name="code line" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+ Order allow,deny
+</p></div>
+
+
+
+<p><div name="code line" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+ Allow from all
+</p></div>
+
+
+
+<p><div name="code line" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+ </FilesMatch>
+</p></div>
+
+
+
+<p><div name="code line" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+</Directory>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+This means that only files whose extensions match the regular expression in the <i>FilesMatch</i> line may be downloaded.
+</p></div>
+
+
+
+<p><div name="SectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 7.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -7.38mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>4.2The PWS and IIS webservers</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Although neither PWS nor IIS is installed by default on current Windows systems, they can easily be installed using the “Add/Remove programs” control panel. If they are not already on your Windows distribution CD-ROM you will have to download them from the Microsoft web site (<i>www.microsoft.com</i>).
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The setup procedure for Greenstone is identical for both PWS and IIS. Invoke the Personal Web Manager and perform the following actions.
+</p></div>
+
+
+
+<ol type="1">
+<li value="1"><p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 41.84mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -7.38mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Select <i>Advanced</i> to get the <i>Advanced Options</i> screen.
+</p></div></li>
+
+
+
+<li value="2"><p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 41.84mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -7.38mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Select <i>Home</i> and click <i>Add</i>. Fill out the fields as follows:
+</p></div></li>
+
+
+
+</ol><p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 49.22mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<i>Directory</i> field:<i>C:/Program Files/gsdl</i>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 0.00mm 0.00mm 0.00mm 49.22mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<i>Alias</i> field:<i>gsdl</i>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 0.00mm 0.00mm 0.00mm 49.22mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Access permissions:<i>Read</i>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 0.00mm 0.00mm 0.00mm 49.22mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Application permissions:<i>None</i>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 0.00mm 0.00mm 0.00mm 49.22mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Click <i>OK</i>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 41.84mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+This makes Greenstone files accessible to the webserver.
+</p></div>
+
+
+
+<ol type="1">
+<li value="3"><p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 41.84mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -7.38mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Back in <i>Advanced Options</i>, select <i>gsdl</i> and click <i>Add</i>. Fill out the fields as follows:
+</p></div></li>
+
+
+
+</ol><p><div name="paragraph" align="left" style="margin: 2.08mm 0.00mm 0.00mm 49.22mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<i>Directory</i> field:<i>C:/Program Files/gsdl</i><i>/cgi-bin</i>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 0.00mm 0.00mm 0.00mm 49.22mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<i>Alias</i> field:<i>cgi-bin</i>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 0.00mm 0.00mm 0.00mm 49.22mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Access permissions:<i>None</i>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 0.00mm 0.00mm 0.00mm 49.22mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Application permissions:<i>Execute</i>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 0.00mm 0.00mm 0.00mm 49.22mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Click <i>OK</i>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 41.84mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+This allows the Greenstone program <i>library.exe</i> to be executed by the webserver.
+</p></div>
+
+
+
+<ol type="1">
+<li value="4"><p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 41.84mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -7.38mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Go to the URL <i>http://localhost/gsdl/cgi-bin/library.exe</i>.
+</p></div></li>
+
+
+
+</ol><p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 41.84mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Note: you need to specify the <i>.exe</i> file extension with PWS and IIS.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 41.84mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 41.84mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+<!--Section Ends-->
+
+<!--Section Begins--><br>
+
+
+
+<p><div name="ChapterTitle" align="right" style="margin: 12.50mm 0.00mm 12.50mm 43.75mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>5<br>Configuring your Site</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+For Greenstone to work properly, access permissions for certain files must be set up appropriately. Also, there is a configuration file associated with each Greenstone site. The install procedure creates a generic configuration file based on your installation choices; however its contents can be tailored to cope with different situations. This section explains both of these issues.
+</p></div>
+
+
+
+<p><div name="SectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 7.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -7.38mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>5.1File permissions</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+This section is irrelevant for Windows 95/98, because these systems don't identify the owners of files.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+On Windows NT, 2000 and Unix systems, cgi scripts don't run as normal users, because users can't be identified over the Web. Instead, they run as the user who started up the webserver program (on Windows systems), or as a special user (commonly called <i>nobody </i>on Unix systems). Because of this, all files and directories within <i>C:/Program Files/gsdl</i> need to be globally readable (or at least readable by the cgi-script user, perhaps “<i>nobody</i>”). To test whether file permissions are set up correctly, run the program <i>library.exe</i> from the command line. If the files are in the right places but the permissions are set incorrectly, it will run from the command line—that is, when <i>you</i> execute it—but not from a browser—that is, when the “<i>nobody</i>” user executes it. Another test is to log in as another user to see if the file permissions are specific to your original user account.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+To work through a Web browser, all the Greenstone directories must be globally readable. Also, the <i>C:/Program Files/gsdl/etc</i> directory and all its contents must be globally <i>writable</i>. This is the directory into which the library program writes the usage log, error and initialization logs, and various user databases. If you're reluctant to make this directory globally writable, you can set permissions so that just the files <i>errout.txt</i>, <i>initout.txt</i>, <i>key.db</i>, <i>users.db</i>, <i>history.db</i> and <i>usage.txt</i> are writable by the cgi user.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+If file permissions are not set up correctly for <i>C:/Program Files/gsdl/etc</i>, you may find that user authentication and search history do not work, and that no usage log (<i>usage.txt</i>) is generated.
+</p></div>
+
+
+
+<p><div name="SectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 7.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -7.38mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>5.2The gsdlsite.cfg configuration file</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The install procedure creates a generic Greenstone site configuration file based on your installation choices. For our installation this file is <i>C:/Program Files/gsdl/cgi-bin/gsdlsite.cfg</i> and its content is:
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 2.08mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+# Site configuration file for Greenstone.
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+# Lines begining with
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+# are comments.
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+# This file should be placed in the same directory as your library
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+# executable file. it should be edited to suit your site.
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+# points to the GSDLHOME directory
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+gsdlhome “C:/Program Files/gsdl”
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+# this is the http address of GSDLHOME
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+# if your webservers DocumentRoot is set to $GSDLHOME
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+# then httpprefix can be commented out
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+httpprefix /gsdl
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+# this is the http address of the directory which
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+# contains the images for the interface.
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+httpimg /gsdl/images
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+# should contain the http address of this cgi script. This
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+# is not needed if the http server sets the environment variable
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+# SCRIPT_NAME
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+#gwcgi /cgi-bin/library
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+# maxrequests is the most requests a fastcgi process
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+# will serve before it exits. This can be set to a
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+# low figure (like 1) while debugging and then set
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+# to a high figure (like 10000) when everything is
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+# working well.
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+#maxrequests 10000
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+You can customise your installation by editing this file, although you will probably not need to do so.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The <i>gsdlhome</i> line simply points to the <i>C:/Program Files/gsdl</i> directory.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<i>httpprefix</i> is the web address of the directory that Greenstone is installed in. We explained earlier how to create an alias so that URLs of the form <i>http://localhost/gsdl/</i> ... are sought in the <i>C:/Program Files/gsdl</i> directory. Putting a line <i>httpprefix /gsdl</i> into the <i>gsdlsite</i> configuration file establishes the same convention for the Greenstone software.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<i>httpimg</i> is the web address of the <i>C:/Program Files/gsdl/images</i> directory, which contains all the gif images used in the interface. In any standard Greenstone installation this will always be <i>httpprefix/images</i>, and the line in the file above is left untouched.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<i>gwcgi</i> is the web address of the library cgi program. This is not required by most webservers (including Apache), and should remain commented out. Don't uncomment it unless you're sure you need to, because that may introduce problems.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<i>maxrequests</i> is only used by versions of Greenstone that are compiled with the “fast-cgi” option on. The standard binary distribution does not include this option because not all webservers are configured to support it. Fastcgi speeds up cgi executions by keeping the main executable in memory between invocations of the software, rather than loading it in from disk each time a web page is requested from the Greenstone software. The trade-off is the amount of memory used, which can grow the longer the program remains in memory. Once <i>maxrequests</i> pages have been generated, the cgi program quits, thereby freeing any accumulated memory. To respond to the next request for a Web page, the cgi program is read in from disk again, and a new cycle of page requests is begun. Most installations use the standard cgi protocol, which means that <i>maxrequests</i> can be safely ignored.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+<!--Section Ends-->
+
+<!--Section Begins--><br>
+
+
+
+<p><div name="ChapterTitle" align="right" style="margin: 12.50mm 0.00mm 12.50mm 43.75mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>6<br>Personalizing your Installation</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Probably the first thing you will want to do once your Greenstone installation is up and running is personalize the home page. The file that generates the Greenstone home page is called <i>home.dm</i>, and is located in the <i>macros</i> subdirectory of the directory into which you installed Greenstone. (The default for Windows systems is <i>C:/Program Files/gsdl</i>.) This is a plain text file that you will have to edit to create a new home page. Instead of editing it, we recommend creating a new file, say <i>yourhome.dm</i>. This will be like <i>home.dm</i> but will define “package home”—which is the bit that does the actual work—in a different way.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+When you make a different home page, there must be some way of linking in to the digital library pages so that you can search and browse the collections on your system. The solution that Greenstone adopts is to use “macros”. That's why the home-page file is called “.dm” and not “.html”—it's a “macro” file rather than a regular <span style="text-transform:lowercase">html</span> file. But don't quail: the macro file basically contains just <span style="text-transform:lowercase">html</span>, sprinkled with a few mystical incantantations which are explained below. The macro language is a powerful facility, and only a small part of it is described below—see the <i>Greenstone Digital Library Developer's Guide</i> for more information.
+</p></div>
+
+
+
+<p><div name="SectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 7.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -7.38mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>6.1Example</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Figure 3 shows an example of a new digital library home page. Each of the “Click here” links takes you to the appropriate Greenstone facility. This page was generated by the file called <i>yourhome.dm</i> shown in Figure 4.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+You can use Figure 4 as a template for creating your own specialized Greenstone home page. Basically, it defines a macro called <i>content</i>. Inside the curly braces is ordinary <span style="text-transform:lowercase">html</span>. You could insert additional text, along with any <span style="text-transform:lowercase">html</span> formatting commands, to put the content that you <br>want to see on the page. The text is regular <span style="text-transform:lowercase">html</span>; if you want you can include hyperlinks and use all the other facilities that <span style="text-transform:lowercase">html</span> provides.
+</p></div>
+
+
+<table width="100.00%25" border="1" cols="2" rows="4">
+<tr><td bgcolor="White" width="26.01%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Figure 3<br>Your own Greenstone home page
+</p></div></td>
+
+
+
+<td bgcolor="White" width="73.99%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<img width="666" height="384" alt="0x01 graphic" src="_httpdocimg_/word052.png"><br>
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="26.01%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="73.99%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="26.01%25" rowspan="1" colspan="1"><p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Figure 4<br><i>yourhome.dm</i> used to create Figure 3
+</p></div></td>
+
+
+
+<td bgcolor="White" width="73.99%25" rowspan="1" colspan="1"><p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+package home
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+_content_ {
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<h2>Your own Greenstone home page</h2>
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<ul>
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<table>
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<tr valign=top><td>Search page for the demo collection<br></td>
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+ <td><a href="_httpquery_&c=demo">Click here</a></td></tr>
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<tr><td>"About" page for the demo collection</td>
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+ <td><a href="_httppageabout_&c=demo">Click here</a></td></tr>
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<tr><td>Preferences page for the demo collection</td>
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+ <td><a href="_httppagepref_&c=demo">Click here</a></td></tr>
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<tr><td>Home page</td>
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+ <td><a href="_httppagehome_">Click here</a></td></tr>
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<tr><td>Help page</td>
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+ <td><a href="_httppagehelp_">Click here</a></td></tr>
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<tr><td>Administration page</td>
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+ <td><a href="_httppagestatus_">Click here</a></td></tr>
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<tr><td>The Collector</td>
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+ <td><a href="_httppagecollector_">Click here</a></td></tr>
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+</table>
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+</ul>
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+}
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+# if you hate the squirly green bar down the left-hand side of the
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+# page, uncomment these lines:
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="
+border: thin none Black;
+
+ padding: 0.00mm 1.39mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+# _header_ {
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+# }
+</p></div></td>
+
+</tr>
+
+
+
+<tr><td bgcolor="White" width="26.01%25" rowspan="1" colspan="1"><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+
+
+<td bgcolor="White" width="73.99%25" rowspan="1" colspan="1"><p><div name="Preformatted" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div></td>
+
+</tr>
+
+</table>
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+To make your new home page link in with other digital library pages, you need to use an appropriate magic spell. In this macro language, magic spells are words flanked by underscores. You can see these in Figure 4. For example, <i>_httppagehome_</i> takes you to the home page, <i>_httppagehelp_</i> to the help page, and so on. In some cases you need to include a collection name. For example, <i>_httpquery_</i><i>&c=demo</i> specifies the search page for the demo collection; for other collections you should replace <i>demo</i> by the appropriate collection name.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The definition of the macro called <i>_content_ </i>is plain <span style="text-transform:lowercase">html</span>. Any standard <span style="text-transform:lowercase">html</span> code may be placed within a macro definition. However, the special characters `{`, `}', `/', and `_' must be escaped with a backslash to prevent them from being processed by the macro language interpreter.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Note that the <i>_content_ </i>macro definition does not contain any <span style="text-transform:lowercase">html</span> header or footer. If you want to change the header or footer of your home page, you should define <i>_header_</i> and/or <i>_footer_</i> macros, adding them to the <i>yourhome.dm</i> file in the form
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 2.08mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+_macroname_ {
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+ ...
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 0.00mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+}
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+For example, the squirly green bar down the left-hand side of Greenstone pages is defined in the <i>_header_ </i>macro, and making this macro null will remove it, as indicated at the end of Figure 4.
+</p></div>
+
+
+
+<p><div name="SectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 7.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -7.38mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>6.2How to make it work</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+You have to tell Greenstone about the new home page <i>yourhome.dm</i>. The system reads in the macro files that are specified in the main configuration file <i>main.cfg</i>, so if you create a new one you must include it there. Name clashes are handled sensibly: the most recent definition takes precedence.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Thus to make the Greenstone digital library software use the home page in Figure 3 instead of the default, first put the <i>yourhome.dm</i> file in Figure 4 into the <i>macros</i> directory. Then edit the <i>main.cfg </i>configuration file to replace <i>home.dm</i> with <i>yourhome.dm</i> in the list of macro files that are loaded at startup.
+</p></div>
+
+
+
+<p><div name="SectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 7.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -7.38mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>6.3Redirecting a URL to Greenstone</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+You may want to redirect a more convenient URL to your Greenstone cgi program. For example, on our system the URL <i>http://nzdl.org</i> (which is shorthand for <i>http://nzdl.org/index.html)</i> is redirected to <i>http://nzdl.org/cgi-bin/library</i>. The Apache webserver accomplishes this with the <i>Redirect</i> directive. Along with other directives, this goes into the <i>C:/Program Files/Apache Group/Apache/conf/httpd.conf</i> configuration file. To redirect the URL <i>http://www.yourserver.com</i> to <i>http://www.yourserver.com/cgi-bin/library</i>, put this line into <i>httpd.conf</i>:
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 2.08mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Redirect /index.html http://www.yourserver.com/cgi-bin/library
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Then you will reach your digital library system directly from the URL <i>http://www.yourserver.com</i>. Instead, if you wanted a URL like <i>http://www.yourserver.com/greenstone</i> to be redirected to <i>http://www.yourserver.com/cgi-bin/library</i>, include in the <i>httpd.conf</i> file
+</p></div>
+
+
+
+<p><div name="Preformatted" align="left" style="margin: 2.08mm 0.00mm 0.00mm 39.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Redirect /greenstone http://www.yourserver.com/cgi-bin/library
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+If your computer doesn't have a domain name (like the “www.yourserver.com” above), just replace <i>www.yourserver.com</i> by <i>localhost</i> in the lines above. So long as the browser is running on the same machine as the webserver—which it surely is if your computer doesn't have a domain name—this has the same effect as the above redirections.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Instead of putting redirect directives into the file <i>httpd.conf</i>, you can equally well put them into a file called <i>.htaccess</i> within your server's document root directory. In fact, doing so has two advantages. First, changes to <i>.htaccess</i> take effect immediately, whereas you have to restart the Apache webserver to see the effect of changes to <i>httpd.conf</i>. Second, on Unix systems you usually have to be logged in as the “root” user to edit <i>httpd.conf</i>, whereas you don't to edit <i>.htaccess</i>.
+</p></div>
+
+
+
+<p><div name="ChapterTitle" align="right" style="margin: 12.50mm 0.00mm 12.50mm 43.75mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b></b></font>
+</p></div>
+
+<!--Section Ends-->
+
+<!--Section Begins--><br>
+
+
+
+<p><div name="AppendixTitle" align="right" style="margin: 12.50mm 0.00mm 12.50mm 43.75mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>Appendix<br>Associated Software</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Here is how to obtain the software packages mentioned above.
+</p></div>
+
+
+
+<p><div name="SectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 7.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -7.38mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>A.1Apache Webserver</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+To run any version of Greenstone apart from the Windows Local Library version, you need an external webserver. Many installations, particularly larger ones, will already have a webserver. If you are using Linux, Apache may be on your installation disk but may not have been selected during the installation procedure. The Apache Webserver from <i>www.apache.org</i> is free, and easy to install.
+</p></div>
+
+
+
+<p><div name="SectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 7.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -7.38mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>A.2Perl</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+Greenstone uses the Perl language when building collections. For Windows, Perl is already included in the Greenstone software. Most Unix systems already have Perl installed, but if not, source code and binaries for a wide range of Unix platforms are freely available at <i>www.perl.com</i>. Perl version 5.0 or higher is needed.
+</p></div>
+
+
+
+<p><div name="SectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 7.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -7.38mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>A.3GCC</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+The Unix version of Greenstone compiles under the Gnu C++ compiler, GCC. Greenstone makes extensive use of the C++ standard template library (we've found it to be broken on some older versions of GCC; please tell us if you have STL problems). Note that this version of Greenstone does not compile under GCC 3.0.
+</p></div>
+
+
+
+<p><div name="SectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 7.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -7.38mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>A.4GDBM</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+All versions of Greenstone use the Gnu Database Manager, GDBM. It is supplied with all Windows versions of Greenstone and installed automatically during the installation procedure. Linux systems already have GDBM, so we do not provide it for Linux. Most other Unix systems have it, but if necessary you can download it from <i></i><i></i><i></i><i><a href="_httpextlink_&rl=0&href=http:%2f%2fwww.gnu.org"></i><font color="Blue"><i><u>www.gnu.org</u></i></font><i></a></i>.
+</p></div>
+
+
+
+<p><div name="SectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 7.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -7.38mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>A.5Java runtime environment</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+To use the Greenstone Librarian Interface, you need a suitable version of the Java Runtime Environment. If you don't already have this, a suitable version is included on the CD-ROM, or you can download the latest version from <font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u><a href="_httpextlink_&rl=0&href=http:%2f%2fjava.sun.com%2fj2se%2fdownloads.html"></u></font><font color="Blue"><u>http://java.sun.com/j2se/downloads.html</u></font><font color="Blue"><u></a></u></font>. Version 1.4.0 or higher is needed.
+</p></div>
+
+
+
+<p><div name="SectionHeading" align="left" style="margin: 4.17mm 0.00mm 0.00mm 7.38mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -7.38mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b>A.6Java compiler</b></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black">To compile the source code of the Greenstone Librarian Interface, you must first install a Java Development Kit. You can download the J2SE Software Development Kit from </font><font color="DarkGreen"><u></u></font><font color="DarkGreen"><u></u></font><font color="DarkGreen"><u></u></font><font color="DarkGreen"><u><a href="_httpextlink_&rl=0&href=http:%2f%2fjava.sun.com%2fj2se%2fdownloads.html"></u></font><font color="Blue"><u>http://java.sun.com/j2se/downloads.html</u></font><font color="DarkGreen"><u></a></u></font>. Version 1.4.0 or higher is needed.
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Header" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+ii APPENDIX B—GLOSSARY OF TERMS
+</p></div>
+
+
+
+<p><div name="Header" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Header" align="right" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+APPENDIX B—GLOSSARY OF TERMS iii
+</p></div>
+
+
+
+<p><div name="Header" align="right" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Header" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Footer" align="left" style="margin: 0.00mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>Greenstone gsdl-2.50</b><b>March</b><b> 2004</b>
+</p></div>
+
+
+
+<p><div name="Footer" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Header" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+iv CONTENTS
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Header" align="right" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+v
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Header" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<i>greenstone.org</i><img width="1491" height="77" alt="0x01 graphic" src="_httpdocimg_/word053.jpg"><br>
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Footer" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Header" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+2 VERSIONS OF GREENSTONE
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Header" align="right" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+2
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Header" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<i>greenstone.org</i><img width="1491" height="77" alt="0x01 graphic" src="_httpdocimg_/word054.jpg"><br>
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Header" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+12 INSTALLATION PROCEDURE
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Header" align="right" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+INSTALLATION PROCEDURE 13
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Header" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<i>greenstone.org</i><img width="1491" height="77" alt="0x01 graphic" src="_httpdocimg_/word055.jpg"><br>
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Header" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+16 GREENSTONE COLLECTIONS
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Header" align="right" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+GREENSTONE COLLECTIONS 15
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Header" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<i>greenstone.org</i><img width="1491" height="77" alt="0x01 graphic" src="_httpdocimg_/word056.jpg"><br>
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Header" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+22 SETTING UP THE WEBSERVER
+</p></div>
+
+
+
+<p><div name="Header" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Header" align="right" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+SETTING UP THE WEBSERVER 21
+</p></div>
+
+
+
+<p><div name="Header" align="right" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Header" align="left" style="margin: 0.00mm -4.91mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<i>greenstone.org</i><img width="1491" height="77" alt="0x01 graphic" src="_httpdocimg_/word057.jpg"><br>
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Header" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+26 CONFIGURING YOUR SITE
+</p></div>
+
+
+
+<p><div name="Header" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Header" align="right" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+CONFIGURING YOUR SITE 25
+</p></div>
+
+
+
+<p><div name="Header" align="right" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Header" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+30 PERSONALIZING YOUR INSTALLATION
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Header" align="right" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+PERSONALIZING YOUR INSTALLATION 29
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Header" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<i>greenstone.org</i><img width="1491" height="77" alt="0x01 graphic" src="_httpdocimg_/word058.jpg"><br>
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Header" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+32 ASSOCIATED SOFTWARE
+</p></div>
+
+
+
+<p><div name="Header" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Header" align="right" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+PERSONALIZING YOUR INSTALLATION 33
+</p></div>
+
+
+
+<p><div name="Header" align="right" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: right; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Header" align="left" style="margin: 0.00mm -4.91mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<i>greenstone.org</i><img width="1491" height="77" alt="0x01 graphic" src="_httpdocimg_/word059.jpg"><br>
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Caption" align="left" style="margin: 2.08mm 0.00mm 0.00mm 14.06mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -14.06mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Caption" align="left" style="margin: 2.08mm 0.00mm 0.00mm 14.06mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -14.06mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+Only “Administrators” can install software
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+NT/2000
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+3.x
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+Full version available
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+Full version available
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+Serves collections but no building
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+Binaries available for all versions
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+Windows
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+Windows or Unix?
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+Other
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+Sun Solaris or Macintosh OS/X
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+Linux
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 1.39mm 0.00mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+Untested
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+Source code tested
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+Source code tested, binaries available
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+Full version available
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+Full version available
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+Full version available
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+May need “root” login to install
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+Unix
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+95/98/Me
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style="margin: 4.17mm 0.00mm 0.00mm 34.46mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+<!--Section Ends-->
+
+
+
+<!--
+<hr>
+<address>
+<a href="_httpextlink_&rl=0&href=http:%2f%2fwvware.sourceforge.net"><img
+src="_httpdocimg_/wvSmall.gif" height=31 width=47
+align=left border=0 alt="wvWare"></a>
+<a href="_httpextlink_&rl=0&href=http:%2f%2fvalidator.w3.org%2fcheck%2freferer"><img
+src="_httpdocimg_/vh40.gif" height=31 width=88
+align=right border=0 alt="Valid HTML 4.0!"></a>
+Document created with <a href="_httpextlink_&rl=0&href=http:%2f%2fwvware.sourceforge.net">wvWare/wvWare version 1.2.4</a><br>
+</address>
+-->
+
+
+
+
+
Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/HASHeaa2a32e.dir/doc.xml
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/HASHeaa2a32e.dir/doc.xml (revision 27727)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/HASHeaa2a32e.dir/doc.xml (revision 27727)
@@ -0,0 +1,1106 @@
+
+
+
+
+
+ indexed_doc
+ en
+ utf8
+ wvWare/wvWare version 1.2.4
+ Evolving Tool Support for Digital Librarians
+ http://research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402383/word06.html
+ http://research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402383/word06.html
+ import/word06.doc
+ tmp/1372402383/word06.html
+ word06.html
+ word06.doc
+ word06.doc
+ WordPlugin
+ 65536
+ word06
+ Word
+ _icondoc_
+ doc.doc
+ doc.doc
+ Michael B. Twidale
+ David M. Nichols
+ COMPUTATIONAL SENSE: THE ROLE OF TECHNOLOGY IN THE EDUCATION OF DIGITAL LIBRARIANS
+ HASHeaa2a32e080549673150f3
+ 1372400870
+ 20130628
+ 1372402383
+ 20130628
+ HASHeaa2a32e.dir
+ doc.doc:application/msword:
+
+
+
+<!--Section Begins--><br>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+Working Paper Series
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+ISSN 1170-487X
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>COMPUTATIONAL SENSE: THE ROLE OF<br>TECHNOLOGY IN THE EDUCATION OF DIGITAL LIBRARIANS</b>
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b>
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b>
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b>
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b>
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b>
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>Michael B. Twidale and David M. Nichols</b>
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b>
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b>
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b>
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b>
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b>
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b>
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b>
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b>
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b>
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b>
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b>
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b>
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+Working Paper: 10/2006
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+October 2006
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 6.250000mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+© 2006 Michael B. Twidale and David M. Nichols
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+Department of Computer Science
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+The University of Waikato
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+Private Bag 3105
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+Hamilton, New Zealand
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>Table of Contents</b><b></b>
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="TOC 1" align="left" style="margin: 6.25mm 0.00mm 4.17mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b></b><b></b><b></b><font color="Blue"><u></u></font><font color="Blue"><u></u></font><b></b><font color="Blue"><u></u></font><font color="Blue"><b><u></u></b></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font><b></b><b></b><b></b><b></b><b></b><b></b><b></b><font color="Blue"><u></u></font><b></b>
+</p></div>
+
+
+
+<p><div name="TOC 1" align="left" style="margin: 6.25mm 0.00mm 4.17mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Blue"><u></u></font><font color="Blue"><u></u></font><b></b><font color="Blue"><u></u></font><font color="Blue"><b><u></u></b></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font><b></b><b></b><b></b><b></b><b></b><b></b><b></b><font color="Blue"><u></u></font><b></b>
+</p></div>
+
+
+
+<p><div name="TOC 1" align="left" style="margin: 6.25mm 0.00mm 4.17mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Blue"><u></u></font><font color="Blue"><u></u></font><b></b><font color="Blue"><u></u></font><font color="Blue"><b><u></u></b></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font><b></b><b></b><b></b><b></b><b></b><b></b><b></b><font color="Blue"><u></u></font><b></b>
+</p></div>
+
+
+
+<p><div name="TOC 3" align="left" style="margin: 6.25mm 0.00mm 4.17mm 8.33mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font>
+</p></div>
+
+
+
+<p><div name="TOC 3" align="left" style="margin: 6.25mm 0.00mm 4.17mm 8.33mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font>
+</p></div>
+
+
+
+<p><div name="TOC 3" align="left" style="margin: 6.25mm 0.00mm 4.17mm 8.33mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font>
+</p></div>
+
+
+
+<p><div name="TOC 3" align="left" style="margin: 6.25mm 0.00mm 4.17mm 8.33mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font>
+</p></div>
+
+
+
+<p><div name="TOC 3" align="left" style="margin: 6.25mm 0.00mm 4.17mm 8.33mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font>
+</p></div>
+
+
+
+<p><div name="TOC 3" align="left" style="margin: 6.25mm 0.00mm 4.17mm 8.33mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font>
+</p></div>
+
+
+
+<p><div name="TOC 1" align="left" style="margin: 6.25mm 0.00mm 4.17mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Blue"><u></u></font><font color="Blue"><u></u></font><b></b><font color="Blue"><u></u></font><font color="Blue"><b><u></u></b></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font><b></b><b></b><b></b><b></b><b></b><b></b><b></b><font color="Blue"><u></u></font><b></b>
+</p></div>
+
+
+
+<p><div name="TOC 1" align="left" style="margin: 6.25mm 0.00mm 4.17mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Blue"><u></u></font><font color="Blue"><u></u></font><b></b><font color="Blue"><u></u></font><font color="Blue"><b><u></u></b></font><font color="Blue"><u></u></font><font color="Blue"><u></u></font><b></b><b></b><b></b><b></b><b></b><b></b><b></b><font color="Blue"><u></u></font><b></b>
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 4.17mm -1.39mm 2.08mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 0.00mm -1.39mm 0.00mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>Computational Sense:<br> the role of technology in the education of digital librarians</b>
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 2.08mm 0.00mm 2.08mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>Michael B. Twidale</b><b><sup>1</sup></b><b> & David M. Nichols</b><b><sup>2</sup></b><b></b>
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b><sup>1</sup></b> Graduate School of Library and Information Science <br>University of Illinois at Urbana-Champaign, IL, USA
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 2.08mm 0.00mm 2.08mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+twidale@uiuc.edu
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b><sup>2</sup></b> Department of Computer Science, University of Waikato<br> Hamilton, New Zealand
+</p></div>
+
+
+
+<p><div name="Normal" align="center" style="margin: 2.08mm 0.00mm 2.08mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: center; line-height: 4.166667mm; color: Black; background-color: White; ">
+dmn@cs.waikato.ac.nz
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<ul>
+<li value="1"><p><div name="Heading 1" align="left" style="margin: 4.17mm 0.00mm 2.08mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b><span style="text-transform:uppercase">I</span></b></font><font color="Black"><b><span style="text-transform:uppercase">NTRODUCTION</span></b></font><font color="Black"><b><span style="text-transform:uppercase"></span></b></font>
+</p></div></li>
+
+
+
+</ul><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 9.84mm; text-align: left; line-height: 6.250000mm; color: Black; background-color: White; ">
+<font color="Black">The rapid progress of digital library technology from research to implementation has created a force for change in the curricula of library schools. The education of future librarians has always had to adapt to new technologies but the pace, complexity and implications of digital libraries pose considerable challenges. In this article we explore how we might successfully blend elements of computer science and library science to produce effective educational experiences for the digital librarians of tomorrow. We first outline the background to current digital librarian education and then propose the concept of </font><font color="Black"><i>computational sense</i></font><font color="Black"> as an appropriate meeting point for these two disciplines.</font>
+</p></div>
+
+
+
+<ul>
+<li value="2"><p><div name="Heading 1" align="left" style="margin: 4.17mm 0.00mm 2.08mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b><span style="text-transform:uppercase">DIGITAL LIBRARIANS</span></b></font>
+</p></div></li>
+
+
+
+</ul><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 9.84mm; text-align: left; line-height: 6.250000mm; color: Black; background-color: White; ">
+<font color="Black">There is an ongoing discussion on what it means to be a digital librarian (Coleman, 2005; Marion, 2001; Mostafa et al, 2006; </font><font color="Black">Pomerantz et al, 2006)</font><font color="Black">. It is similar to being a traditional librarian in terms of ethos and applicability of core guiding theories, including access, cataloguing, collection development and teaching people both search skills and general information literacy. It can be viewed as simply integrating one set of digital information resou</font><font color="Black">rces into a set of access servic</font><font color="Black">es provided around a pre-existing set of paper-based resources. However it also requires additional technical skills, extending the librarian's role into new areas. For example, DL creation can be more akin to publishing than collection development, involving aspects of editing, revision and aligning to data and metadata standards.</font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 9.84mm; text-align: left; line-height: 6.250000mm; color: Black; background-color: White; ">
+<font color="Black">The topic of digital librarianship is subject to rapid change (Pomerantz et al, 2006), as it is partially defined by the availability and functionality of appropriate software. The ease of building a digital library or an institutional repository has been radically changed over the past decade by the emergence of software such as Greenstone (W</font><font color="Black">itten & Bainbridge, 2003) and DS</font><font color="Black">pace (Tansley et al, 2005). For example, the courses presented in library schools are often based around similar material presented in tutorials at digital library conferences. Education based around digital library software inevitably brings with it techniques and concepts from computer science; especially as most of these courses combine theory and practice (Ma, Clegg, & O'Brien, 2006) Issues that can cause problems for library students vary from the basic (such as selecting the appropriate software version, downloading and installing) to advanced topics involving customization and extensibility (Nichols et al, 2006).</font>
+</p></div>
+
+
+
+<ul>
+<li value="3"><p><div name="Heading 1" align="left" style="margin: 4.17mm 0.00mm 2.08mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b><span style="text-transform:uppercase">COMPUTATIONAL SENSE</span></b></font>
+</p></div></li>
+
+
+
+</ul><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 6.250000mm; color: Black; background-color: White; ">
+<font color="Black">As libraries have become more computerised, librarians have had to learn more and more about computer systems, file formats and web servers. Over time, commodity software can hide away certain levels of complexity as a basic infrastructure is develop</font><font color="Black">ed</font><font color="Black">. But innovative computer applications will always require a degree of explicit support and tinkering. For example, the Greenstone software development team has, over several years, developed a variety of tools to abstract away from technical details to simplify the tasks of creating and maintaining digital collections. Despite this work the experiences of using digital library software can still be disconcerting for some students (Nichols et al, 2006). This state of affairs is more a reflection on the state-of-the-art in content management systems than a criticism of any particular software applications.</font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 6.250000mm; color: Black; background-color: White; ">
+<font color="Black">From the perspective of software developers the power of digital library software derives from the flexibility of computer programming languages. Indeed, the Greenstone digital library suite embeds programming language constructs into its customization features; providing considerable flexibility for collection design but at the expense of learnability (Nichols et al, 2005). A practical example is the nature of conditional statements in Greenstone macros, which:</font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 6.250000mm; color: Black; background-color: White; ">
+<font color="Black"></font>
+</p></div>
+
+
+
+<ul>
+<li value="1"><p><div name="paragraph" align="left" style="margin: 0.00mm 0.00mm 0.00mm 12.50mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 6.250000mm; color: Black; background-color: White; ">
+<font color="Black">have a unique syntax (rather than re-using an existing language such as JavaScript or PHP)</font>
+</p></div></li>
+
+
+
+<li value="2"><p><div name="paragraph" align="left" style="margin: 0.00mm 0.00mm 0.00mm 12.50mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 6.250000mm; color: Black; background-color: White; ">
+<font color="Black">have a different syntax to conditional statements in Greenstone formatting statements</font>
+</p></div></li>
+
+
+
+<li value="3"><p><div name="paragraph" align="left" style="margin: 0.00mm 0.00mm 0.00mm 12.50mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 6.250000mm; color: Black; background-color: White; ">
+<font color="Black">have no error checking at design time (such as the red underlining of spell checkers or Visual Studio)</font>
+</p></div></li>
+
+
+
+<li value="4"><p><div name="paragraph" align="left" style="margin: 0.00mm 0.00mm 0.00mm 12.50mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: -6.25mm; text-align: left; line-height: 6.250000mm; color: Black; background-color: White; ">
+<font color="Black">have no integrated documentation (such as found in modern programming development environments)</font>
+</p></div></li>
+
+
+
+</ul><p><div name="paragraph" align="left" style="margin: 0.00mm 0.00mm 0.00mm 12.50mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 6.250000mm; color: Black; background-color: White; ">
+<font color="Black"></font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 6.250000mm; color: Black; background-color: White; ">
+<font color="Black">At one level it is simple to say that these can be corrected through more software development. The larger question is whether this is the right direction for systems that are to be used in digital librarian education. The resulting system would be very similar to an IDE (Integrated Development Environment) of the sort regularly used by computer science students and programmers the world over. </font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 6.250000mm; color: Black; background-color: White; ">
+<font color="Black">This raises the question: should future librarians be forced to become programmers in order to graduate? We believe that digital librarians should not have to become programmers but that they </font><font color="Black"><i>do</i></font><font color="Black"> need to acquire a fluency with information technology beyond </font><font color="Black">that of </font><font color="Black">a traditional MLS degree. We coin the term </font><font color="Black"><i>computational sense</i></font><font color="Black"> to describe this level of fluency. It covers a range of issues that remain in flux and are clearly open for debate. We </font><font color="Black">outline a</font><font color="Black"> few of them below for illustration.</font>
+</p></div>
+
+
+
+<p><div name="Heading 2" align="left" style="margin: 4.17mm 0.00mm 2.08mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>Comfort and fluency with computational systems</b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 9.84mm; text-align: left; line-height: 6.250000mm; color: Black; background-color: White; ">
+<font color="Black">Of course a digital librarian should be comfortable in using the latest technologies available. However, although necessary we do not believe this is sufficient for librarians to be able to take active roles in exploiting the potential of a rapidly changing set of technologies.</font>
+</p></div>
+
+
+
+<p><div name="Heading 2" align="left" style="margin: 4.17mm 0.00mm 2.08mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>Metacognitive skills in learning about new computational resources</b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 6.250000mm; color: Black; background-color: White; ">
+<font color="Black">Possessing training in a technology is insufficient because technologies change so rapidly. New versions of applications contain new functionalities, new interfaces and hence new possibilities for how they might be used. New applications become available to complement or replace existing applications. Online resources and computational services can enhance or disrupt what users expect or want to be able to do with existing resources. Patrons' changing reactions to library catalogues in the light of their experiences with Amazon and Google are just one indicator of this. Consequently, practising librarians need to be able to learn about the latest versions, applications and new ways of combining applications quickly and maybe without formal training. This can be done, but probably requires the teaching of the metacognitive skills that can facilitate more efficient and effective learning both by individuals and communities within and across organisations.</font>
+</p></div>
+
+
+
+<p><div name="Heading 2" align="left" style="margin: 4.17mm 0.00mm 2.08mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>Fluency in incremental tailoring and combining of applications for evolving needs </b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 6.250000mm; color: Black; background-color: White; ">
+<font color="Black">Even if they do not directly program new digital library applications, librarians are likely to be involved directly or indirectly in the installation and use of those applications, which invariably involves tailoring work. Modern applications typically come with a host of options, and the defaults are often less than ideal. Making a resource useful and usable in a particular context typically involves a range of tailoring activities ranging from selecting between options, choosing modules to install, including or linking the application to the resources it will use or provide, integrating the software with other applications or provisions and `skinning' the interface to create an integrated, consistent and coherent look and feel for end users as part of a focus on usability. All these require varying levels of technical expertise. They also require the ability to interact productively with others, both stakeholders with far less technical skill, and also technical experts, lacking local knowledge of use-in-context. Although somewhat daunting-sounding this information intermediary role is one firmly within the bounds of the ethos of traditional librarianship (Erlich and Cash, 1994).</font>
+</p></div>
+
+
+
+<p><div name="Heading 2" align="left" style="margin: 4.17mm 0.00mm 2.08mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>A sense of applications as ongoing co-designed artefacts rather than technological givens</b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 6.250000mm; color: Black; background-color: White; ">
+<font color="Black">Computational sense </font><font color="Black">should include</font><font color="Black"> an understanding and an expectation that digital librarians be involved not just in the selection, analysis, and facilitation of learning and use of computational artefacts, but that they should also be involved in the </font><font color="Black"><i>design</i></font><font color="Black"> of those artefacts. At the very least it should empower digital librarians to take a more direct role in larger-scale design processes. Applications should not be taken as technological givens, to be coped with by them and in their information intermediary role in helping others to learn and use. Rather these applications need to be regarded as provisional, changing and amenable to change by librarians. In many existing cases this still might not actually be feasible, but we believe that it is worth considering what it would take to give more librarians the skills necessary to not merely critique inadequate systems but to get involved in actually improving them. Design does not necessarily require programming. As noted above, tailoring is one aspect of design, but there are others. As well as in-house design, there are various approaches to wider involvement in larger co-design processes, including participatory design (Kyng and Mathiassen, 1997) and the involvement of lead users (von Hippel, 2005) as well as open source software development. Modern systems are frequently in the process of near-continual re-design as new versions and modules are released, which at least raises the possibility of greater involvement by people with appropriate skills</font>
+</p></div>
+
+
+
+<p><div name="Heading 2" align="left" style="margin: 4.17mm 0.00mm 2.08mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>A sense of the feasibility of potential design options </b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 6.250000mm; color: Black; background-color: White; ">
+<font color="Black">To be fully involved in ongoing co-design, it is very helpful to have a good sense of what is feasible in current systems development and what is not. A qualitative sense of the relative costs of different design options is also helpful as the design space is collectively explored. Typically computer science students are expected to acquire these rich qualitative skills just by lots of practice. They are rarely explicitly taught. We speculate that it might be possible to teach these skills of judgement without requiring considerable practical programming experience. If so, it would allow digital librarians to engage in far more productive interactions both with vendors and systems development teams, as advocates for stakeholders and use-in-context as different functionalities and possibilities are uncovered. If you don't have a sense of what it is reasonable to ask for, you are inclined to select just from the options on offer. All design involves trade-offs and compromises, but when these are done in ignorance of whole categories of costs, benefits, and opportunities, truly innovative design possibilities are overlooked.</font>
+</p></div>
+
+
+
+<p><div name="Heading 2" align="left" style="margin: 4.17mm 0.00mm 2.08mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<b>Spreadsheets as a guiding metaphor</b>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 6.250000mm; color: Black; background-color: White; ">
+<font color="Black">To illustrate our vision, we use an example from an earlier round of technological innovation coinciding with the advent of the personal computer in the 1980s. Prior to that time, people who wanted to do mathematical calculations on computers (including scientists and financial experts) would have had to write a program in a language such as FORTRAN, or commission someone else to do it for them. This was for many daunting or </font><font color="Black">prohibitively </font><font color="Black">expensive in terms of money, opportunity cost or effort-risk-reward calculations. With the advent of the early spreadsheet programs on PCs, many people started using them because they were far easier to both learn and use than programming to achieve basic numerical calculations. Although intended for accounting calculations, the ease of learning and use encouraged innovation and appropriation by many others with needs to manipulate numbers. Nevertheless, spreadsheets were not completely trivial to use. One needed basic numeracy to be able to use them productively and not generate nonsense - what we might call a numerical sense. One just did not need to know how to program in FORTRAN. Ability to program certainly helped in avoiding certain classic errors, and was essential for more complex calculations that either the spreadsheet software of the day could not manage or where the programming of macros was needed. But programming ceased to be a </font><font color="Black">prerequisite</font><font color="Black"> and the skills of sophisticated spreadsheet use, planning, design and debugging could be taught to people who had not first learned to program. </font>
+</p></div>
+
+
+
+<p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 6.250000mm; color: Black; background-color: White; ">
+<font color="Black">In a similar manner, we believe that it is possible to extract some of the skills traditionally acquired (explicitly but more often implicitly) from long experience of programming, and teach these to librarians under the label of computational sense. In so doing we can widen the number of people able to productively engage with information technologies, just as spreadsheets widened the use of computers by numerate people far beyond the range of those willing to invest time in learning FORTRAN. This approach also challenges the developers of digital library software to produce tools as useful and useable as the spreadsheet.</font>
+</p></div>
+
+
+
+<ul>
+<li value="4"><p><div name="Heading 1" align="left" style="margin: 0.00mm 0.00mm 2.08mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b><span style="text-transform:uppercase">CONCLUSION</span></b></font>
+</p></div></li>
+
+
+
+</ul><p><div name="paragraph" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 9.84mm; text-align: left; line-height: 6.250000mm; color: Black; background-color: White; ">
+<font color="Black">Computational sense extends beyond the notion of programming to encompass an ability to understand the broader notions of the capabilities of software and the socio-technical issues of usability, system deployment and maintenance. In this article we have proposed some characteristics of computational sense and how they might influence the design of the curriculum for digital librarians. In doing so we don't claim to have a complete list but simply to contribute a new perspective to the ongoing debate on the nature of digital librarianship. </font>
+</p></div>
+
+
+
+<ul>
+<li value="5"><p><div name="Heading 1" align="left" style="margin: 4.17mm 0.00mm 2.08mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"><b><span style="text-transform:uppercase">R</span></b></font><font color="Black"><b><span style="text-transform:uppercase">EFERENCES</span></b></font><font color="Black"><b><span style="text-transform:uppercase"></span></b></font>
+</p></div></li>
+
+
+
+</ul><p><div name="Body Text First Indent" align="left" style="margin: 0.00mm 0.00mm 2.08mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 4.91mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black">Coleman, A. (2005) Interdisciplinarity, interactivity, and interoperability for educating the digerati. </font><font color="Black"><i>Education for Information</i></font><font color="Black"> 23(4) 233-243.</font>
+</p></div>
+
+
+
+<p><div name="Body Text First Indent" align="left" style="margin: 0.00mm 0.00mm 2.08mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 4.91mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black">Erlich, K. and Cash, D. (1994) Turning information into knowledge: information finding as a collaborative activity. </font><font color="Black"><i>Proceedings of Digital Libraries '94</i></font><font color="Black">. College Station, TX. 119-125.</font>
+</p></div>
+
+
+
+<p><div name="Body Text First Indent" align="left" style="margin: 0.00mm 0.00mm 2.08mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 4.91mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black">von Hippel, E. (2005) </font><font color="Black"><i>Democratizing Innovation.</i></font><font color="Black"> Cambridge, MA: MIT Press.. </font>
+</p></div>
+
+
+
+<p><div name="Body Text First Indent" align="left" style="margin: 0.00mm 0.00mm 2.08mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 4.91mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black">Kyng, M. and Mathiassen, L. (1997) (eds.) </font><font color="Black"><i>Computers and Design in Context</i></font><font color="Black">. Cambridge, MA.: MIT Press.</font>
+</p></div>
+
+
+
+<p><div name="Body Text First Indent" align="left" style="margin: 0.00mm 0.00mm 2.08mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 4.91mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black">Ma, Y., Clegg, W., and O'Brien, A. (2006) Digital library education: the current status. In </font><font color="Black"><i>Proceedings of the 6th ACM/IEEE-CS Joint Conference on Digital Libraries (JCDL'06)</i></font><font color="Black">. ACM Press, New York, NY, 165-174. </font>
+</p></div>
+
+
+
+<p><div name="Body Text First Indent" align="left" style="margin: 0.00mm 0.00mm 2.08mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 4.91mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black">Marion, L. (2001). Digital librarian, cybrarian, or librarian with specialized skills: Who will staff digital libraries? In H. Thompson (Ed.), </font><font color="Black"><i>Crossing the Divide: Proceedings of the Tenth National Conference of the Association of College and Research Libraries. </i></font><font color="Black">Chicago, IL: American Library Association. 143-149.</font>
+</p></div>
+
+
+
+<p><div name="Body Text First Indent" align="left" style="margin: 0.00mm 0.00mm 2.08mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 4.91mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black">Mostafa, J., Brancolini, K., Smith, L.C. and Mischo, W. (2005) Developing a digital library education program. </font><font color="Black"><i>Proceedings of the 5th ACM/IEEE-CS Joint Conference on Digital Libraries (JCDL'05)</i></font><font color="Black">, 427. ACM Press.</font>
+</p></div>
+
+
+
+<p><div name="Body Text First Indent" align="left" style="margin: 0.00mm 0.00mm 2.08mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 4.91mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black">Nichols, D. M., Bainbridge, D., Downie, J. S., and Twidale, M. B. (2006). Learning by building digital libraries. </font><font color="Black"><i>Proceedings of the 6th ACM/IEEE-CS Joint Conference on Digital Libraries (JCDL'06).</i></font><font color="Black"> ACM Press, New York, NY, 185-186 </font>
+</p></div>
+
+
+
+<p><div name="Body Text First Indent" align="left" style="margin: 0.00mm 0.00mm 2.08mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 4.91mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black">Nichols, D. M., Bainbridge, D., Marsden, G., Patel, D., Cunningham, S. J., Thompson, J., Boddie, S. J. and Witten, I. H. (2005) Evolving tool support for digital librarians. Theng, Y.-L. and Foo, S. (eds), In </font><font color="Black"><i>Design and Usability of Digital Libraries: Case Studies in the Asia Pacific</i></font><font color="Black">, 171-189. Information Science Publishing, London.</font>
+</p></div>
+
+
+
+<p><div name="Body Text First Indent" align="left" style="margin: 0.00mm 0.00mm 2.08mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 4.91mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black">Pomerantz, J., Wildemuth, B. M., Yang, S., and Fox, E. A. (2006) Curriculum development for digital libraries. </font><font color="Black"><i>Proceedings of the 6th ACM/IEEE-CS Joint Conference on Digital Libraries (JCDL'06).</i></font><font color="Black"> ACM Press, New York, NY, 175-184. </font>
+</p></div>
+
+
+
+<p><div name="Body Text First Indent" align="left" style="margin: 0.00mm 0.00mm 2.08mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 4.91mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black">Tansley, R., Smith, M. and Walker, J.H. (2005) The DSpace open source digital asset management system: challenges and opportunities. </font><font color="Black"><i>Proceedings of the 9th European Conference on Research and Advanced Technology for Digital Libraries (ECDL 2005)</i></font><font color="Black">. LNCS 3652. Springer.242-253.</font>
+</p></div>
+
+
+
+<p><div name="Body Text First Indent" align="left" style="margin: 0.00mm 0.00mm 2.08mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 4.91mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black">Witten, I.H. and Bainbridge, D. (2003). </font><font color="Black"><i>How to Build a Digital Library</i></font><font color="Black">. San Francisco, CA: Morgan Kaufmann.</font><font color="Black"></font>
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Normal" align="left" style=" padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 0.00mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+
+</p></div>
+
+
+
+<p><div name="Body Text First Indent" align="left" style="margin: 0.00mm 0.00mm 2.08mm 0.00mm; padding: 0.00mm 0.00mm 0.00mm 0.00mm; ">
+
+<p style="text-indent: 4.91mm; text-align: left; line-height: 4.166667mm; color: Black; background-color: White; ">
+<font color="Black"></font>
+</p></div>
+
+<!--Section Ends-->
+
+
+
+<!--
+<hr>
+<address>
+<a href="_httpextlink_&rl=0&href=http:%2f%2fwvware.sourceforge.net"><img
+src="_httpdocimg_/wvSmall.gif" height=31 width=47
+align=left border=0 alt="wvWare"></a>
+<a href="_httpextlink_&rl=0&href=http:%2f%2fvalidator.w3.org%2fcheck%2freferer"><img
+src="_httpdocimg_/vh40.gif" height=31 width=88
+align=right border=0 alt="Valid HTML 4.0!"></a>
+Document created with <a href="_httpextlink_&rl=0&href=http:%2f%2fwvware.sourceforge.net">wvWare/wvWare version 1.2.4</a><br>
+</address>
+-->
+
+
+
+
+
Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/earliestDatestamp
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/earliestDatestamp (revision 27727)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/earliestDatestamp (revision 27727)
@@ -0,0 +1,1 @@
+1372402379
Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/rss-items.rdf
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/rss-items.rdf (revision 27727)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/archives/rss-items.rdf (revision 27727)
@@ -0,0 +1,36 @@
+-
+
+ _httpdomain__httpcollection_/document/HASH015936f516ed4b1d7b050af9
+
+-
+
+ _httpdomain__httpcollection_/document/HASH8bbe6da0374b413b1b355c
+
+-
+ Greenstone: A comprehensive open-source digital library software system
+ _httpdomain__httpcollection_/document/HASH1a9cea0f239f754007681b
+
+-
+ Applications for Bibliometric Research in the Emerging Digital Libraries
+ _httpdomain__httpcollection_/document/HASH019c5dca7f5bb781460a6b9c
+
+-
+
+ _httpdomain__httpcollection_/document/HASH079154443e2ecce7bb4208
+
+-
+
+ _httpdomain__httpcollection_/document/HASHeaa2992e081949673150f3
+
+-
+ Greenstone: A comprehensive open-source digital library software system
+ _httpdomain__httpcollection_/document/HASHeaa29d2e081149673150f3
+
+-
+ GREENSTONE DIGITAL LIBRARY INSTALLERâS GUIDE
+ _httpdomain__httpcollection_/document/HASHeaa2a12e080949673150f3
+
+-
+ COMPUTATIONAL SENSE: THE ROLE OF TECHNOLOGY IN THE EDUCATION OF DIGITAL LIBRARIANS
+ _httpdomain__httpcollection_/document/HASHeaa2a32e080549673150f3
+
Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/etc/collect.bak
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/etc/collect.bak (revision 27727)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/etc/collect.bak (revision 27727)
@@ -0,0 +1,62 @@
+creator
+maintainer
+public true
+
+buildtype mgpp
+infodbtype gdbm
+
+indexes text dc.Title,ex.dc.Title,ex.Title dc.Creator
+defaultindex text
+
+levels document
+
+indexoptions accentfold casefold stem
+
+defaultlevel document
+
+# import options, needed for diffcol testing
+# especially in conjunction with -sort flag to ArchivesInfPlugin
+OIDtype hash_on_full_filename
+sortmeta OID
+
+plugin GreenstoneXMLPlugin
+plugin PDFPlugin
+plugin RTFPlugin
+plugin WordPlugin
+plugin PostScriptPlugin
+plugin ImagePlugin
+plugin EmbeddedMetadataPlugin
+plugin MetadataXMLPlugin
+plugin ArchivesInfPlugin -sort
+plugin DirectoryPlugin
+
+classify List -metadata dc.Title;ex.Title -partition_type_within_level approximate_size
+
+classify AZCompactList -metadata dc.Creator
+
+format VList "
[link][icon][/link] |
+[ex.srclink]{Or}{[ex.thumbicon],[ex.srcicon]}[ex./srclink] |
+[highlight]
+{Or}{[dc.Title],[exp.Title],[ex.Title],Untitled}
+[/highlight]{If}{[ex.Source], ([ex.Source])} | "
+
+format HList "[link][highlight][ex.Title][/highlight][/link]"
+
+format DocumentHeading "{Or}{[parent(Top):Title],[Title],untitled}
"
+
+format DocumentText "[Text]"
+
+format DocumentButtons "Detach|Highlight"
+
+format SearchTypes "plain,form"
+
+collectionmeta collectionname [l=en] "Word-PDF-Basic"
+collectionmeta .text [l=en] "_labeltext_"
+collectionmeta .dc.Title,ex.dc.Title,Title [l=en] "_labelTitle_"
+collectionmeta .document [l=en] "_textdocument_"
+collectionmeta .section [l=en] "_textsection_"
+collectionmeta .document:text [l=en] "_labeltext_"
+collectionmeta .document:dc.Title,Title,ex.dc.Title [l=en] "_labelTitle_"
+collectionmeta .document:Source [l=en] "_labelSource_"
+collectionmeta .document:dc.Title,Title [l=en] "_labelTitle_"
+collectionmeta .dc.Creator [l=en] "_labelCreator_"
Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/etc/collect.cfg
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/etc/collect.cfg (revision 27727)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/etc/collect.cfg (revision 27727)
@@ -0,0 +1,62 @@
+creator
+maintainer
+public true
+
+buildtype mgpp
+infodbtype gdbm
+
+indexes text dc.Title,ex.dc.Title,ex.Title dc.Creator
+defaultindex text
+
+levels document
+
+indexoptions accentfold casefold stem
+
+defaultlevel document
+
+# import options, needed for diffcol testing
+# especially in conjunction with -sort flag to ArchivesInfPlugin
+OIDtype hash_on_full_filename
+sortmeta OID
+
+plugin GreenstoneXMLPlugin
+plugin PDFPlugin
+plugin RTFPlugin
+plugin WordPlugin
+plugin PostScriptPlugin
+plugin ImagePlugin
+plugin EmbeddedMetadataPlugin
+plugin MetadataXMLPlugin
+plugin ArchivesInfPlugin -sort
+plugin DirectoryPlugin
+
+classify List -metadata dc.Title;ex.Title -partition_type_within_level approximate_size
+
+classify AZCompactList -metadata dc.Creator
+
+format VList "[link][icon][/link] |
+[ex.srclink]{Or}{[ex.thumbicon],[ex.srcicon]}[ex./srclink] |
+[highlight]
+{Or}{[dc.Title],[exp.Title],[ex.Title],Untitled}
+[/highlight]{If}{[ex.Source], ([ex.Source])} | "
+
+format HList "[link][highlight][ex.Title][/highlight][/link]"
+
+format DocumentHeading "{Or}{[parent(Top):Title],[Title],untitled}
"
+
+format DocumentText "[Text]"
+
+format DocumentButtons "Detach|Highlight"
+
+format SearchTypes "plain,form"
+
+collectionmeta collectionname [l=en] "Word-PDF-Basic"
+collectionmeta .text [l=en] "_labeltext_"
+collectionmeta .dc.Title,ex.dc.Title,Title [l=en] "_labelTitle_"
+collectionmeta .document [l=en] "_textdocument_"
+collectionmeta .section [l=en] "_textsection_"
+collectionmeta .document:text [l=en] "_labeltext_"
+collectionmeta .document:dc.Title,Title,ex.dc.Title [l=en] "_labelTitle_"
+collectionmeta .document:Source [l=en] "_labelSource_"
+collectionmeta .document:dc.Title,Title [l=en] "_labelTitle_"
+collectionmeta .dc.Creator [l=en] "_labelCreator_"
Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/gli.col
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/gli.col (revision 27727)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/gli.col (revision 27727)
@@ -0,0 +1,24 @@
+
+
+
+
+
+
+
+
+
+]>
+
+ false
+ true
+ true
+
+
+
+
+
+
+
Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/import/metadata.xml
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/import/metadata.xml (revision 27727)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/import/metadata.xml (revision 27727)
@@ -0,0 +1,70 @@
+
+
+
+
+ pdf01\.pdf
+
+ Greenstone: A comprehensive open-source digital library software system
+ Ian H. Witten
+ Rodger J. McNab
+ Stefan J. Boddie
+ David Bainbridge
+
+
+
+ word03\.doc
+
+ Greenstone: A comprehensive open-source digital library software system
+ Ian H. Witten
+ Rodger J. McNab
+ Stefan J. Boddie
+ David Bainbridge
+
+
+
+ pdf03\.pdf
+
+ Applications for Bibliometric Research in the Emerging Digital Libraries
+ Sally Jo Cunningham
+
+
+
+ word06\.doc
+
+ COMPUTATIONAL SENSE: THE ROLE OF TECHNOLOGY IN THE EDUCATION OF DIGITAL LIBRARIANS
+ Michael B. Twidale
+ David M. Nichols
+
+
+
+ word05\.doc
+
+ GREENSTONE DIGITAL LIBRARY INSTALLERâS GUIDE
+ Ian H. Witten
+ Stefan J. Boddie
+
+
+
+ rtf01\.rtf
+
+ Sally Jo Cunningham
+ Stuart M. Dillon
+
+
+
+ cluster\.ps
+
+ Yong Wang
+ Ian H. Witten
+
+
+
+ langmodl\.ps
+
+ Ian H. Witten
+ Zane Bray
+ Malika Mahoui
+ W.J. Teahan
+
+
+
Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/index/build.cfg
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/index/build.cfg (revision 27727)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/index/build.cfg (revision 27727)
@@ -0,0 +1,16 @@
+builddate 1372402385
+buildtype mgpp
+earliestdatestamp 1372402379
+indexfieldmap text->TX dc.Title,ex.dc.Title,Title->TI dc.Creator->CR
+indexfields text dc.Title,ex.dc.Title,Title dc.Creator
+indexlevels Doc
+indexmap text;dc.Title,ex.dc.Title,Title;dc.Creator;->idx
+indexstem wordpdfb
+infodbtype gdbm
+levelmap document->Doc
+maxnumeric 4
+numbytes 744955
+numdocs 9
+numsections 9
+stemindexes 7
+textlevel Sec
Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/index/rss-items.rdf
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/index/rss-items.rdf (revision 27727)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/index/rss-items.rdf (revision 27727)
@@ -0,0 +1,36 @@
+-
+
+ _httpdomain__httpcollection_/document/HASH015936f516ed4b1d7b050af9
+
+-
+
+ _httpdomain__httpcollection_/document/HASH8bbe6da0374b413b1b355c
+
+-
+ Greenstone: A comprehensive open-source digital library software system
+ _httpdomain__httpcollection_/document/HASH1a9cea0f239f754007681b
+
+-
+ Applications for Bibliometric Research in the Emerging Digital Libraries
+ _httpdomain__httpcollection_/document/HASH019c5dca7f5bb781460a6b9c
+
+-
+
+ _httpdomain__httpcollection_/document/HASH079154443e2ecce7bb4208
+
+-
+
+ _httpdomain__httpcollection_/document/HASHeaa2992e081949673150f3
+
+-
+ Greenstone: A comprehensive open-source digital library software system
+ _httpdomain__httpcollection_/document/HASHeaa29d2e081149673150f3
+
+-
+ GREENSTONE DIGITAL LIBRARY INSTALLERâS GUIDE
+ _httpdomain__httpcollection_/document/HASHeaa2a12e080949673150f3
+
+-
+ COMPUTATIONAL SENSE: THE ROLE OF TECHNOLOGY IN THE EDUCATION OF DIGITAL LIBRARIANS
+ _httpdomain__httpcollection_/document/HASHeaa2a32e080549673150f3
+
Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/log/build_log.1372400872243.txt
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/log/build_log.1372400872243.txt (revision 27727)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/log/build_log.1372400872243.txt (revision 27727)
@@ -0,0 +1,137 @@
+s
+Command: perl -S /research/ak19/GS286bin_26Jun2013/bin/script/full-import.pl -gli -language en -collectdir /research/ak19/GS286bin_26Jun2013/collect wordpdfb
+import.pl> Global file scan checking directory: /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/import
+import.pl> MetadataXMLPlugin: processing metadata.xml
+import.pl> EmbeddedMetadataPlugin: processing pdf01.pdf
+import.pl> Extracted 15 pieces of metadata from /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/import/pdf01.pdf EXIF block
+import.pl> EmbeddedMetadataPlugin: processing pdf03.pdf
+import.pl> Extracted 16 pieces of metadata from /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/import/pdf03.pdf EXIF block
+import.pl> Converting cluster.ps to text format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400873/err.log" -output text "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400873/cluster.ps"
+import.pl> TextPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400873/cluster.text
+import.pl> PostScriptPlugin: extracting PostScript metadata from "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/import/cluster.ps"
+import.pl> Converting langmodl.ps to text format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400873/err.log" -output text "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400873/langmodl.ps"
+import.pl> Warning: Error executing gs: couldn't run.
+import.pl> Stripping text from postscript
+import.pl> TextPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400873/langmodl.text
+import.pl> PostScriptPlugin: extracting PostScript metadata from "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/import/langmodl.ps"
+import.pl> Converting pdf01.pdf to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -pdf_zoom 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400874/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400874/pdf01.pdf"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400874/pdf01.html
+import.pl> Converting pdf03.pdf to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -pdf_zoom 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400874/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400874/pdf03.pdf"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400874/pdf03.html
+import.pl> Converting rtf01.rtf to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400874/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400874/rtf01.rtf"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400874/rtf01.html
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400874/rtf011.gif to rtf011.gif
+import.pl> Converting word01.doc to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400874/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400874/word01.doc"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400874/word01.html
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400874/wvSmall.gif to wvSmall.gif
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400874/vh40.gif to vh40.gif
+import.pl> Converting word03.doc to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400875/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400875/word03.doc"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400875/word03.html
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400875/wvSmall.gif to wvSmall.gif
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400875/vh40.gif to vh40.gif
+import.pl> Converting word05.doc to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400875/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400875/word05.doc"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400875/word05.html
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400875/wvSmall.gif to wvSmall.gif
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400875/vh40.gif to vh40.gif
+import.pl> Converting word06.doc to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400876/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400876/word06.doc"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400876/word06.html
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400876/wvSmall.gif to wvSmall.gif
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372400876/vh40.gif to vh40.gif
+import.pl> *********************************************
+import.pl> Import complete
+import.pl> *********************************************
+import.pl> * 9 documents were considered for processing
+import.pl> * 9 were processed and included in the collection
+import.pl> Command complete.
+import.pl> Extracting new metadata from archive files.
+import.pl> Archived metadata extraction complete.
+Command: perl -S /research/ak19/GS286bin_26Jun2013/bin/script/full-buildcol.pl -gli -language en -collectdir /research/ak19/GS286bin_26Jun2013/collect wordpdfb
+buildcol.pl> *** creating the compressed text
+buildcol.pl> collecting text statistics (mgpp_passes -T1)
+buildcol.pl> ArchivesInfPlugin: processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/archives/archiveinf-doc.gdb
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0f55374a.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH014d6653.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH1e8bdd2b.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH2ce671f3.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH017ebea0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH2a3afe7a.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0194429e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH01b5ae76.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHfe0860a0.dir/doc.xml
+buildcol.pl> Stats (Compressing text from text)
+buildcol.pl> Total bytes in collection: 744955
+buildcol.pl> Total bytes in text: 744964
+buildcol.pl> creating the compression dictionary
+buildcol.pl> compressing the text (mgpp_passes -T2)
+buildcol.pl> ArchivesInfPlugin: processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/archives/archiveinf-doc.gdb
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0f55374a.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH014d6653.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH1e8bdd2b.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH2ce671f3.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH017ebea0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH2a3afe7a.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0194429e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH01b5ae76.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHfe0860a0.dir/doc.xml
+buildcol.pl> Stats (Compressing text from text)
+buildcol.pl> Total bytes in collection: 744955
+buildcol.pl> Total bytes in text: 744964
+buildcol.pl> *** building index text;dc.Title,ex.dc.Title,Title;Source; in subdirectory idx
+buildcol.pl> creating index dictionary (mgpp_passes -I1)
+buildcol.pl> ArchivesInfPlugin: processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/archives/archiveinf-doc.gdb
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0f55374a.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH014d6653.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH1e8bdd2b.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH2ce671f3.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH017ebea0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH2a3afe7a.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0194429e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH01b5ae76.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHfe0860a0.dir/doc.xml
+buildcol.pl> Stats (Creating index text;dc.Title,ex.dc.Title,Title;Source;)
+buildcol.pl> Total bytes in collection: 744955
+buildcol.pl> Total bytes in text;dc.Title,ex.dc.Title,Title;Source;: 326938
+buildcol.pl> inverting the text (mgpp_passes -I2)
+buildcol.pl> ArchivesInfPlugin: processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/archives/archiveinf-doc.gdb
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0f55374a.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH014d6653.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH1e8bdd2b.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH2ce671f3.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH017ebea0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH2a3afe7a.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0194429e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH01b5ae76.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHfe0860a0.dir/doc.xml
+buildcol.pl> Stats (Creating index text;dc.Title,ex.dc.Title,Title;Source;)
+buildcol.pl> Total bytes in collection: 744955
+buildcol.pl> Total bytes in text;dc.Title,ex.dc.Title,Title;Source;: 326938
+buildcol.pl> create the weights file
+buildcol.pl> creating 'on-disk' stemmed dictionary
+buildcol.pl> creating stem indexes
+buildcol.pl> BuildDir: /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/building
+buildcol.pl> *** creating the info database and processing associated files
+buildcol.pl> ArchivesInfPlugin: processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/archives/archiveinf-doc.gdb
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0f55374a.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH014d6653.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH1e8bdd2b.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH2ce671f3.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH017ebea0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH2a3afe7a.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0194429e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH01b5ae76.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHfe0860a0.dir/doc.xml
+buildcol.pl> *** outputting information for classifier: CL1
+buildcol.pl> *** outputting information for classifier: CL2
+buildcol.pl> *** outputting information for classifier: oai
+buildcol.pl> *** creating auxiliary files
+buildcol.pl> Copying rss-items.rdf file from archives to building (eventually to index)
+buildcol.pl> Command complete.
Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/log/build_log.1372401612710.txt
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/log/build_log.1372401612710.txt (revision 27727)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/log/build_log.1372401612710.txt (revision 27727)
@@ -0,0 +1,140 @@
+s
+Command: perl -S /research/ak19/GS286bin_26Jun2013/bin/script/full-import.pl -gli -language en -collectdir /research/ak19/GS286bin_26Jun2013/collect wordpdfb
+import.pl> Removing current contents of the archives directory...
+import.pl> Removing contents of the collection "tmp" directory...
+import.pl> Global file scan checking directory: /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/import
+import.pl> MetadataXMLPlugin: processing metadata.xml
+import.pl> EmbeddedMetadataPlugin: processing pdf01.pdf
+import.pl> Extracted 15 pieces of metadata from /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/import/pdf01.pdf EXIF block
+import.pl> EmbeddedMetadataPlugin: processing pdf03.pdf
+import.pl> Extracted 16 pieces of metadata from /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/import/pdf03.pdf EXIF block
+import.pl> Converting cluster.ps to text format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401613/err.log" -output text "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401613/cluster.ps"
+import.pl> TextPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401613/cluster.text
+import.pl> PostScriptPlugin: extracting PostScript metadata from "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/import/cluster.ps"
+import.pl> Converting langmodl.ps to text format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401614/err.log" -output text "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401614/langmodl.ps"
+import.pl> Warning: Error executing gs: couldn't run.
+import.pl> Stripping text from postscript
+import.pl> TextPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401614/langmodl.text
+import.pl> PostScriptPlugin: extracting PostScript metadata from "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/import/langmodl.ps"
+import.pl> Converting pdf01.pdf to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -pdf_zoom 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401614/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401614/pdf01.pdf"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401614/pdf01.html
+import.pl> Converting pdf03.pdf to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -pdf_zoom 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401614/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401614/pdf03.pdf"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401614/pdf03.html
+import.pl> Converting rtf01.rtf to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401615/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401615/rtf01.rtf"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401615/rtf01.html
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401615/rtf011.gif to rtf011.gif
+import.pl> Converting word01.doc to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401615/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401615/word01.doc"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401615/word01.html
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401615/wvSmall.gif to wvSmall.gif
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401615/vh40.gif to vh40.gif
+import.pl> Converting word03.doc to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401615/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401615/word03.doc"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401615/word03.html
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401615/wvSmall.gif to wvSmall.gif
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401615/vh40.gif to vh40.gif
+import.pl> Converting word05.doc to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401616/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401616/word05.doc"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401616/word05.html
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401616/wvSmall.gif to wvSmall.gif
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401616/vh40.gif to vh40.gif
+import.pl> Wide character in print at /research/ak19/GS286bin_26Jun2013/perllib/plugouts/BasePlugout.pm line 899.
+import.pl> Converting word06.doc to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401617/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401617/word06.doc"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401617/word06.html
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401617/wvSmall.gif to wvSmall.gif
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401617/vh40.gif to vh40.gif
+import.pl> *********************************************
+import.pl> Import complete
+import.pl> *********************************************
+import.pl> * 9 documents were considered for processing
+import.pl> * 9 were processed and included in the collection
+import.pl> Command complete.
+import.pl> Extracting new metadata from archive files.
+import.pl> Archived metadata extraction complete.
+Command: perl -S /research/ak19/GS286bin_26Jun2013/bin/script/full-buildcol.pl -gli -language en -collectdir /research/ak19/GS286bin_26Jun2013/collect wordpdfb
+buildcol.pl> *** creating the compressed text
+buildcol.pl> collecting text statistics (mgpp_passes -T1)
+buildcol.pl> ArchivesInfPlugin: processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/archives/archiveinf-doc.gdb
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0f55374a.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH014d6653.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH1e8bdd2b.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH011178d4.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH017ebea0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0194429e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH01b5ae76.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHfe0860a0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHbc2ee015.dir/doc.xml
+buildcol.pl> Stats (Compressing text from text)
+buildcol.pl> Total bytes in collection: 744955
+buildcol.pl> Total bytes in text: 744964
+buildcol.pl> creating the compression dictionary
+buildcol.pl> compressing the text (mgpp_passes -T2)
+buildcol.pl> ArchivesInfPlugin: processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/archives/archiveinf-doc.gdb
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0f55374a.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH014d6653.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH1e8bdd2b.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH011178d4.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH017ebea0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0194429e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH01b5ae76.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHfe0860a0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHbc2ee015.dir/doc.xml
+buildcol.pl> Stats (Compressing text from text)
+buildcol.pl> Total bytes in collection: 744955
+buildcol.pl> Total bytes in text: 744964
+buildcol.pl> *** building index text;dc.Title,ex.dc.Title,Title;Source; in subdirectory idx
+buildcol.pl> creating index dictionary (mgpp_passes -I1)
+buildcol.pl> ArchivesInfPlugin: processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/archives/archiveinf-doc.gdb
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0f55374a.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH014d6653.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH1e8bdd2b.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH011178d4.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH017ebea0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0194429e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH01b5ae76.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHfe0860a0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHbc2ee015.dir/doc.xml
+buildcol.pl> Stats (Creating index text;dc.Title,ex.dc.Title,Title;Source;)
+buildcol.pl> Total bytes in collection: 744955
+buildcol.pl> Total bytes in text;dc.Title,ex.dc.Title,Title;Source;: 327283
+buildcol.pl> inverting the text (mgpp_passes -I2)
+buildcol.pl> ArchivesInfPlugin: processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/archives/archiveinf-doc.gdb
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0f55374a.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH014d6653.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH1e8bdd2b.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH011178d4.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH017ebea0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0194429e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH01b5ae76.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHfe0860a0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHbc2ee015.dir/doc.xml
+buildcol.pl> Stats (Creating index text;dc.Title,ex.dc.Title,Title;Source;)
+buildcol.pl> Total bytes in collection: 744955
+buildcol.pl> Total bytes in text;dc.Title,ex.dc.Title,Title;Source;: 327283
+buildcol.pl> create the weights file
+buildcol.pl> creating 'on-disk' stemmed dictionary
+buildcol.pl> creating stem indexes
+buildcol.pl> BuildDir: /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/building
+buildcol.pl> *** creating the info database and processing associated files
+buildcol.pl> ArchivesInfPlugin: processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/archives/archiveinf-doc.gdb
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0f55374a.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH014d6653.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH1e8bdd2b.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH011178d4.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH017ebea0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0194429e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH01b5ae76.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHfe0860a0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHbc2ee015.dir/doc.xml
+buildcol.pl> *** outputting information for classifier: CL1
+buildcol.pl> *** outputting information for classifier: CL2
+buildcol.pl> *** outputting information for classifier: oai
+buildcol.pl> *** creating auxiliary files
+buildcol.pl> Copying rss-items.rdf file from archives to building (eventually to index)
+buildcol.pl> Command complete.
Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/log/build_log.1372401998212.txt
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/log/build_log.1372401998212.txt (revision 27727)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/log/build_log.1372401998212.txt (revision 27727)
@@ -0,0 +1,140 @@
+s
+Command: perl -S /research/ak19/GS286bin_26Jun2013/bin/script/full-import.pl -gli -language en -collectdir /research/ak19/GS286bin_26Jun2013/collect wordpdfb
+import.pl> Removing current contents of the archives directory...
+import.pl> Removing contents of the collection "tmp" directory...
+import.pl> Global file scan checking directory: /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/import
+import.pl> MetadataXMLPlugin: processing metadata.xml
+import.pl> EmbeddedMetadataPlugin: processing pdf01.pdf
+import.pl> Extracted 15 pieces of metadata from /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/import/pdf01.pdf EXIF block
+import.pl> EmbeddedMetadataPlugin: processing pdf03.pdf
+import.pl> Extracted 16 pieces of metadata from /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/import/pdf03.pdf EXIF block
+import.pl> Converting cluster.ps to text format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401999/err.log" -output text "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401999/cluster.ps"
+import.pl> TextPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401999/cluster.text
+import.pl> PostScriptPlugin: extracting PostScript metadata from "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/import/cluster.ps"
+import.pl> Converting langmodl.ps to text format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401999/err.log" -output text "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401999/langmodl.ps"
+import.pl> Warning: Error executing gs: couldn't run.
+import.pl> Stripping text from postscript
+import.pl> TextPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401999/langmodl.text
+import.pl> PostScriptPlugin: extracting PostScript metadata from "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/import/langmodl.ps"
+import.pl> Converting pdf01.pdf to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -pdf_zoom 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401999/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401999/pdf01.pdf"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372401999/pdf01.html
+import.pl> Converting pdf03.pdf to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -pdf_zoom 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402000/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402000/pdf03.pdf"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402000/pdf03.html
+import.pl> Converting rtf01.rtf to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402000/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402000/rtf01.rtf"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402000/rtf01.html
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402000/rtf011.gif to rtf011.gif
+import.pl> Converting word01.doc to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402000/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402000/word01.doc"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402000/word01.html
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402000/wvSmall.gif to wvSmall.gif
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402000/vh40.gif to vh40.gif
+import.pl> Converting word03.doc to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402001/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402001/word03.doc"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402001/word03.html
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402001/wvSmall.gif to wvSmall.gif
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402001/vh40.gif to vh40.gif
+import.pl> Converting word05.doc to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402001/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402001/word05.doc"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402001/word05.html
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402001/wvSmall.gif to wvSmall.gif
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402001/vh40.gif to vh40.gif
+import.pl> Wide character in print at /research/ak19/GS286bin_26Jun2013/perllib/plugouts/BasePlugout.pm line 899.
+import.pl> Converting word06.doc to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402002/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402002/word06.doc"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402002/word06.html
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402002/wvSmall.gif to wvSmall.gif
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402002/vh40.gif to vh40.gif
+import.pl> *********************************************
+import.pl> Import complete
+import.pl> *********************************************
+import.pl> * 9 documents were considered for processing
+import.pl> * 9 were processed and included in the collection
+import.pl> Command complete.
+import.pl> Extracting new metadata from archive files.
+import.pl> Archived metadata extraction complete.
+Command: perl -S /research/ak19/GS286bin_26Jun2013/bin/script/full-buildcol.pl -gli -language en -collectdir /research/ak19/GS286bin_26Jun2013/collect wordpdfb
+buildcol.pl> *** creating the compressed text
+buildcol.pl> collecting text statistics (mgpp_passes -T1)
+buildcol.pl> ArchivesInfPlugin: processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/archives/archiveinf-doc.gdb
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0f55374a.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH014d6653.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH1e8bdd2b.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH017ebea0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH011a1dd4.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHbc2ee10f.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0194429e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH01b5ae76.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHfe0860a0.dir/doc.xml
+buildcol.pl> Stats (Compressing text from text)
+buildcol.pl> Total bytes in collection: 744955
+buildcol.pl> Total bytes in text: 744964
+buildcol.pl> creating the compression dictionary
+buildcol.pl> compressing the text (mgpp_passes -T2)
+buildcol.pl> ArchivesInfPlugin: processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/archives/archiveinf-doc.gdb
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0f55374a.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH014d6653.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH1e8bdd2b.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH017ebea0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH011a1dd4.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHbc2ee10f.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0194429e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH01b5ae76.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHfe0860a0.dir/doc.xml
+buildcol.pl> Stats (Compressing text from text)
+buildcol.pl> Total bytes in collection: 744955
+buildcol.pl> Total bytes in text: 744964
+buildcol.pl> *** building index text;dc.Title,ex.dc.Title,Title;dc.Creator; in subdirectory idx
+buildcol.pl> creating index dictionary (mgpp_passes -I1)
+buildcol.pl> ArchivesInfPlugin: processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/archives/archiveinf-doc.gdb
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0f55374a.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH014d6653.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH1e8bdd2b.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH017ebea0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH011a1dd4.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHbc2ee10f.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0194429e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH01b5ae76.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHfe0860a0.dir/doc.xml
+buildcol.pl> Stats (Creating index text;dc.Title,ex.dc.Title,Title;dc.Creator;)
+buildcol.pl> Total bytes in collection: 744955
+buildcol.pl> Total bytes in text;dc.Title,ex.dc.Title,Title;dc.Creator;: 327503
+buildcol.pl> inverting the text (mgpp_passes -I2)
+buildcol.pl> ArchivesInfPlugin: processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/archives/archiveinf-doc.gdb
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0f55374a.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH014d6653.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH1e8bdd2b.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH017ebea0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH011a1dd4.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHbc2ee10f.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0194429e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH01b5ae76.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHfe0860a0.dir/doc.xml
+buildcol.pl> Stats (Creating index text;dc.Title,ex.dc.Title,Title;dc.Creator;)
+buildcol.pl> Total bytes in collection: 744955
+buildcol.pl> Total bytes in text;dc.Title,ex.dc.Title,Title;dc.Creator;: 327503
+buildcol.pl> create the weights file
+buildcol.pl> creating 'on-disk' stemmed dictionary
+buildcol.pl> creating stem indexes
+buildcol.pl> BuildDir: /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/building
+buildcol.pl> *** creating the info database and processing associated files
+buildcol.pl> ArchivesInfPlugin: processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/archives/archiveinf-doc.gdb
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0f55374a.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH014d6653.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH1e8bdd2b.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH017ebea0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH011a1dd4.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHbc2ee10f.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0194429e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH01b5ae76.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHfe0860a0.dir/doc.xml
+buildcol.pl> *** outputting information for classifier: CL1
+buildcol.pl> *** outputting information for classifier: CL2
+buildcol.pl> *** outputting information for classifier: oai
+buildcol.pl> *** creating auxiliary files
+buildcol.pl> Copying rss-items.rdf file from archives to building (eventually to index)
+buildcol.pl> Command complete.
Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/log/build_log.1372402009444.txt
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/log/build_log.1372402009444.txt (revision 27727)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/log/build_log.1372402009444.txt (revision 27727)
@@ -0,0 +1,140 @@
+s
+Command: perl -S /research/ak19/GS286bin_26Jun2013/bin/script/full-import.pl -gli -language en -collectdir /research/ak19/GS286bin_26Jun2013/collect wordpdfb
+import.pl> Removing current contents of the archives directory...
+import.pl> Removing contents of the collection "tmp" directory...
+import.pl> Global file scan checking directory: /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/import
+import.pl> MetadataXMLPlugin: processing metadata.xml
+import.pl> EmbeddedMetadataPlugin: processing pdf01.pdf
+import.pl> Extracted 15 pieces of metadata from /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/import/pdf01.pdf EXIF block
+import.pl> EmbeddedMetadataPlugin: processing pdf03.pdf
+import.pl> Extracted 16 pieces of metadata from /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/import/pdf03.pdf EXIF block
+import.pl> Converting cluster.ps to text format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402010/err.log" -output text "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402010/cluster.ps"
+import.pl> TextPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402010/cluster.text
+import.pl> PostScriptPlugin: extracting PostScript metadata from "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/import/cluster.ps"
+import.pl> Converting langmodl.ps to text format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402011/err.log" -output text "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402011/langmodl.ps"
+import.pl> Warning: Error executing gs: couldn't run.
+import.pl> Stripping text from postscript
+import.pl> TextPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402011/langmodl.text
+import.pl> PostScriptPlugin: extracting PostScript metadata from "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/import/langmodl.ps"
+import.pl> Converting pdf01.pdf to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -pdf_zoom 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402011/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402011/pdf01.pdf"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402011/pdf01.html
+import.pl> Converting pdf03.pdf to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -pdf_zoom 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402011/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402011/pdf03.pdf"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402011/pdf03.html
+import.pl> Converting rtf01.rtf to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402011/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402011/rtf01.rtf"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402011/rtf01.html
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402011/rtf011.gif to rtf011.gif
+import.pl> Converting word01.doc to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402011/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402011/word01.doc"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402011/word01.html
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402011/wvSmall.gif to wvSmall.gif
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402011/vh40.gif to vh40.gif
+import.pl> Converting word03.doc to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402012/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402012/word03.doc"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402012/word03.html
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402012/wvSmall.gif to wvSmall.gif
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402012/vh40.gif to vh40.gif
+import.pl> Converting word05.doc to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402013/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402013/word05.doc"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402013/word05.html
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402013/wvSmall.gif to wvSmall.gif
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402013/vh40.gif to vh40.gif
+import.pl> Wide character in print at /research/ak19/GS286bin_26Jun2013/perllib/plugouts/BasePlugout.pm line 899.
+import.pl> Converting word06.doc to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402013/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402013/word06.doc"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402013/word06.html
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402013/wvSmall.gif to wvSmall.gif
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402013/vh40.gif to vh40.gif
+import.pl> *********************************************
+import.pl> Import complete
+import.pl> *********************************************
+import.pl> * 9 documents were considered for processing
+import.pl> * 9 were processed and included in the collection
+import.pl> Command complete.
+import.pl> Extracting new metadata from archive files.
+import.pl> Archived metadata extraction complete.
+Command: perl -S /research/ak19/GS286bin_26Jun2013/bin/script/full-buildcol.pl -gli -language en -collectdir /research/ak19/GS286bin_26Jun2013/collect wordpdfb
+buildcol.pl> *** creating the compressed text
+buildcol.pl> collecting text statistics (mgpp_passes -T1)
+buildcol.pl> ArchivesInfPlugin: processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/archives/archiveinf-doc.gdb
+buildcol.pl> GreenstoneXMLPlugin: processing HASHbc2ee10f.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0f55374a.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH014d6653.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH1e8bdd2b.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH017ebea0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0194429e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH01b5ae76.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHfe0860a0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH011115d4.dir/doc.xml
+buildcol.pl> Stats (Compressing text from text)
+buildcol.pl> Total bytes in collection: 744955
+buildcol.pl> Total bytes in text: 744964
+buildcol.pl> creating the compression dictionary
+buildcol.pl> compressing the text (mgpp_passes -T2)
+buildcol.pl> ArchivesInfPlugin: processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/archives/archiveinf-doc.gdb
+buildcol.pl> GreenstoneXMLPlugin: processing HASHbc2ee10f.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0f55374a.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH014d6653.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH1e8bdd2b.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH017ebea0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0194429e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH01b5ae76.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHfe0860a0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH011115d4.dir/doc.xml
+buildcol.pl> Stats (Compressing text from text)
+buildcol.pl> Total bytes in collection: 744955
+buildcol.pl> Total bytes in text: 744964
+buildcol.pl> *** building index text;dc.Title,ex.dc.Title,Title;dc.Creator; in subdirectory idx
+buildcol.pl> creating index dictionary (mgpp_passes -I1)
+buildcol.pl> ArchivesInfPlugin: processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/archives/archiveinf-doc.gdb
+buildcol.pl> GreenstoneXMLPlugin: processing HASHbc2ee10f.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0f55374a.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH014d6653.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH1e8bdd2b.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH017ebea0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0194429e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH01b5ae76.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHfe0860a0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH011115d4.dir/doc.xml
+buildcol.pl> Stats (Creating index text;dc.Title,ex.dc.Title,Title;dc.Creator;)
+buildcol.pl> Total bytes in collection: 744955
+buildcol.pl> Total bytes in text;dc.Title,ex.dc.Title,Title;dc.Creator;: 327503
+buildcol.pl> inverting the text (mgpp_passes -I2)
+buildcol.pl> ArchivesInfPlugin: processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/archives/archiveinf-doc.gdb
+buildcol.pl> GreenstoneXMLPlugin: processing HASHbc2ee10f.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0f55374a.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH014d6653.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH1e8bdd2b.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH017ebea0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0194429e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH01b5ae76.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHfe0860a0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH011115d4.dir/doc.xml
+buildcol.pl> Stats (Creating index text;dc.Title,ex.dc.Title,Title;dc.Creator;)
+buildcol.pl> Total bytes in collection: 744955
+buildcol.pl> Total bytes in text;dc.Title,ex.dc.Title,Title;dc.Creator;: 327503
+buildcol.pl> create the weights file
+buildcol.pl> creating 'on-disk' stemmed dictionary
+buildcol.pl> creating stem indexes
+buildcol.pl> BuildDir: /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/building
+buildcol.pl> *** creating the info database and processing associated files
+buildcol.pl> ArchivesInfPlugin: processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/archives/archiveinf-doc.gdb
+buildcol.pl> GreenstoneXMLPlugin: processing HASHbc2ee10f.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0f55374a.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH014d6653.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH1e8bdd2b.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH017ebea0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH0194429e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH01b5ae76.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHfe0860a0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH011115d4.dir/doc.xml
+buildcol.pl> *** outputting information for classifier: CL1
+buildcol.pl> *** outputting information for classifier: CL2
+buildcol.pl> *** outputting information for classifier: oai
+buildcol.pl> *** creating auxiliary files
+buildcol.pl> Copying rss-items.rdf file from archives to building (eventually to index)
+buildcol.pl> Command complete.
Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/log/build_log.1372402379223.txt
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/log/build_log.1372402379223.txt (revision 27727)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/log/build_log.1372402379223.txt (revision 27727)
@@ -0,0 +1,141 @@
+s
+Command: perl -S /research/ak19/GS286bin_26Jun2013/bin/script/full-import.pl -gli -language en -collectdir /research/ak19/GS286bin_26Jun2013/collect wordpdfb
+import.pl> Detected -sortmeta. To effect the stipulated sorting by metadata (or OID) remember this option should be paired with either the '-reversesort' or '-sort' option to ArchivesInfPlugin.
+import.pl> Removing current contents of the archives directory...
+import.pl> Removing contents of the collection "tmp" directory...
+import.pl> Global file scan checking directory: /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/import
+import.pl> MetadataXMLPlugin: processing metadata.xml
+import.pl> EmbeddedMetadataPlugin: processing pdf01.pdf
+import.pl> Extracted 15 pieces of metadata from /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/import/pdf01.pdf EXIF block
+import.pl> EmbeddedMetadataPlugin: processing pdf03.pdf
+import.pl> Extracted 16 pieces of metadata from /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/import/pdf03.pdf EXIF block
+import.pl> Converting cluster.ps to text format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402380/err.log" -output text "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402380/cluster.ps"
+import.pl> TextPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402380/cluster.text
+import.pl> PostScriptPlugin: extracting PostScript metadata from "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/import/cluster.ps"
+import.pl> Converting langmodl.ps to text format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402380/err.log" -output text "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402380/langmodl.ps"
+import.pl> Warning: Error executing gs: couldn't run.
+import.pl> Stripping text from postscript
+import.pl> TextPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402380/langmodl.text
+import.pl> PostScriptPlugin: extracting PostScript metadata from "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/import/langmodl.ps"
+import.pl> Converting pdf01.pdf to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -pdf_zoom 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402380/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402380/pdf01.pdf"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402380/pdf01.html
+import.pl> Converting pdf03.pdf to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -pdf_zoom 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402381/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402381/pdf03.pdf"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402381/pdf03.html
+import.pl> Converting rtf01.rtf to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402381/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402381/rtf01.rtf"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402381/rtf01.html
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402381/rtf011.gif to rtf011.gif
+import.pl> Converting word01.doc to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402381/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402381/word01.doc"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402381/word01.html
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402381/wvSmall.gif to wvSmall.gif
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402381/vh40.gif to vh40.gif
+import.pl> Converting word03.doc to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402382/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402382/word03.doc"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402382/word03.html
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402382/wvSmall.gif to wvSmall.gif
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402382/vh40.gif to vh40.gif
+import.pl> Converting word05.doc to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402382/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402382/word05.doc"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402382/word05.html
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402382/wvSmall.gif to wvSmall.gif
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402382/vh40.gif to vh40.gif
+import.pl> Wide character in print at /research/ak19/GS286bin_26Jun2013/perllib/plugouts/BasePlugout.pm line 899.
+import.pl> Converting word06.doc to html format
+import.pl> calling cmd "/usr/bin/perl" -S gsConvert.pl -verbose 2 -errlog "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402383/err.log" -output html "/research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402383/word06.doc"
+import.pl> HTMLPlugin processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402383/word06.html
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402383/wvSmall.gif to wvSmall.gif
+import.pl> BasePlugout::process couldn't copy the associated file /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/tmp/1372402383/vh40.gif to vh40.gif
+import.pl> *********************************************
+import.pl> Import complete
+import.pl> *********************************************
+import.pl> * 9 documents were considered for processing
+import.pl> * 9 were processed and included in the collection
+import.pl> Command complete.
+import.pl> Extracting new metadata from archive files.
+import.pl> Archived metadata extraction complete.
+Command: perl -S /research/ak19/GS286bin_26Jun2013/bin/script/full-buildcol.pl -gli -language en -collectdir /research/ak19/GS286bin_26Jun2013/collect wordpdfb
+buildcol.pl> *** creating the compressed text
+buildcol.pl> collecting text statistics (mgpp_passes -T1)
+buildcol.pl> ArchivesInfPlugin: processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/archives/archiveinf-doc.gdb
+buildcol.pl> GreenstoneXMLPlugin: processing HASH015936f5.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH019c5dca.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH07915444.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH1a9cea0f.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH8bbe6da0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHeaa2992e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHeaa29d2e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHeaa2a12e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHeaa2a32e.dir/doc.xml
+buildcol.pl> Stats (Compressing text from text)
+buildcol.pl> Total bytes in collection: 744955
+buildcol.pl> Total bytes in text: 744964
+buildcol.pl> creating the compression dictionary
+buildcol.pl> compressing the text (mgpp_passes -T2)
+buildcol.pl> ArchivesInfPlugin: processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/archives/archiveinf-doc.gdb
+buildcol.pl> GreenstoneXMLPlugin: processing HASH015936f5.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH019c5dca.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH07915444.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH1a9cea0f.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH8bbe6da0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHeaa2992e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHeaa29d2e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHeaa2a12e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHeaa2a32e.dir/doc.xml
+buildcol.pl> Stats (Compressing text from text)
+buildcol.pl> Total bytes in collection: 744955
+buildcol.pl> Total bytes in text: 744964
+buildcol.pl> *** building index text;dc.Title,ex.dc.Title,Title;dc.Creator; in subdirectory idx
+buildcol.pl> creating index dictionary (mgpp_passes -I1)
+buildcol.pl> ArchivesInfPlugin: processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/archives/archiveinf-doc.gdb
+buildcol.pl> GreenstoneXMLPlugin: processing HASH015936f5.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH019c5dca.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH07915444.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH1a9cea0f.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH8bbe6da0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHeaa2992e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHeaa29d2e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHeaa2a12e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHeaa2a32e.dir/doc.xml
+buildcol.pl> Stats (Creating index text;dc.Title,ex.dc.Title,Title;dc.Creator;)
+buildcol.pl> Total bytes in collection: 744955
+buildcol.pl> Total bytes in text;dc.Title,ex.dc.Title,Title;dc.Creator;: 327503
+buildcol.pl> inverting the text (mgpp_passes -I2)
+buildcol.pl> ArchivesInfPlugin: processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/archives/archiveinf-doc.gdb
+buildcol.pl> GreenstoneXMLPlugin: processing HASH015936f5.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH019c5dca.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH07915444.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH1a9cea0f.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH8bbe6da0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHeaa2992e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHeaa29d2e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHeaa2a12e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHeaa2a32e.dir/doc.xml
+buildcol.pl> Stats (Creating index text;dc.Title,ex.dc.Title,Title;dc.Creator;)
+buildcol.pl> Total bytes in collection: 744955
+buildcol.pl> Total bytes in text;dc.Title,ex.dc.Title,Title;dc.Creator;: 327503
+buildcol.pl> create the weights file
+buildcol.pl> creating 'on-disk' stemmed dictionary
+buildcol.pl> creating stem indexes
+buildcol.pl> BuildDir: /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/building
+buildcol.pl> *** creating the info database and processing associated files
+buildcol.pl> ArchivesInfPlugin: processing /research/ak19/GS286bin_26Jun2013/collect/wordpdfb/archives/archiveinf-doc.gdb
+buildcol.pl> GreenstoneXMLPlugin: processing HASH015936f5.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH019c5dca.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH07915444.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH1a9cea0f.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASH8bbe6da0.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHeaa2992e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHeaa29d2e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHeaa2a12e.dir/doc.xml
+buildcol.pl> GreenstoneXMLPlugin: processing HASHeaa2a32e.dir/doc.xml
+buildcol.pl> *** outputting information for classifier: CL1
+buildcol.pl> *** outputting information for classifier: CL2
+buildcol.pl> *** outputting information for classifier: oai
+buildcol.pl> *** creating auxiliary files
+buildcol.pl> Copying rss-items.rdf file from archives to building (eventually to index)
+buildcol.pl> Command complete.
Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/macros/extra.dm
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/macros/extra.dm (revision 27727)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/macros/extra.dm (revision 27727)
@@ -0,0 +1,17 @@
+# extra.dm file
+# You can add collection specific macros in here
+# Lines starting with a '#' are comments.
+# Remember to include the package declaration
+
+package Style
+
+# will be applied to all pages
+# add css style lines inside the style tags
+_collectionspecificstyle_ {
+
+}
+
+# add any javascript functions here
+_collectionspecificscript_ {
+}
Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/metadata/dublin.mds
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/metadata/dublin.mds (revision 27727)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/metadata/dublin.mds (revision 27727)
@@ -0,0 +1,1856 @@
+
+
+
+
+
+ Dublin Core Metadata Element Set, Version 1.1: Reference Description
+ This document is the reference description, version 1.1 of the Dublin Core Metadata Element Set. This document supersedes the Dublin Core Metadata Element Set, version 1.0. See the Dublin Core Home Page (http://dublincore.org) for further information about the workshops, reports, working group papers, projects, and new developments concerning the Dublin Core Metadata Element set
+
+
+
+ Dublin Core Huanga - Maori (He Tauira)
+
+
+
+
+ Eléments de métadonnées du Dublin Core, Version 1.1: Description de Réference
+ Ce document résume les derniÚres définitions des éléments demétadonnées du Dublin Core originellement définis dans le document[RFC2413]. Ces nouvelles définitions seront officiellement connues comme la Version 1.1. Elles utilisent un standard défini formellement pour la description d'éléments de métadonnées. Cette formalisation contribue à améliorer la cohérence avec d'autres communautés décrivant des métadonnées et à augmenter la précision, la portée et la cohérence interne de la définition des éléments du Dublin Core.
+
+
+
+
+ ÐÐ°Ð±ÐŸÑ ÑлеЌеМÑПв ЌеÑаЎаММÑÑ
+ Dublin Core (ÐÑблОМÑкПгП ÑÐŽÑа) ÐеÑÑÐžÑ 1.1: СпÑавПÑМПе ПпОÑаМОе
+ ÐаÑÑПÑÑОй ЎПкÑÐŒÐµÐœÑ ÐŸÐ±ÐŸÐ±ÑÐ°ÐµÑ ÐŸÐ±ÐœÐŸÐ²Ð»ÐµÐœÐœÑе ПпÑÐµÐŽÐµÐ»ÐµÐœÐžÑ ÑлеЌеМÑПв ЌеÑаЎаММÑÑ
+ Dublin Core (ÐÑблОМÑкПгП ÑÐŽÑа), пеÑвПМаÑалÑМП ПпÑеЎелеММÑÑ
+ в RFC2413 (ÐеÑаЎаММÑе Dublin Core ÐŽÐ»Ñ ÐœÐ°Ñ
+ÐŸÐ¶ÐŽÐµÐœÐžÑ ÑеÑÑÑÑПв). ÐÑО МПвÑе ПпÑÐµÐŽÐµÐ»ÐµÐœÐžÑ ÐŸÑОÑОалÑМП ОзвеÑÑÐœÑ ÐºÐ°Ðº ÐеÑÑÐžÑ 1.1.
+
+
+
+
+ Elementos del conjunto de metadatas de Dublin Core: Descripción de Referencia
+ Este documento corresponde a una traducción del original en lengua inglesa, con fecha 02/11/1997 que se encuentra en http://purl.org/metadata/dublin_core_elements. Este documento es una descripción de referencia de los elementos del conjunto de "Dublin Core". Para más información sobre reuniones de trabajo, documentos de trabajo, proyectos y nuevos desarrollos relacionados con el conjunto de elementos que aquà se describen consultar la "Home Page" de "Dublin Core" (http://purl.org/metadata/dublin_core). Los elementos poseen nombres descriptivos que pretenden transmitir un significado semántico a los mismos. Para promover una interoperabilidad global, una descripción del valor de algunos elementos prodrá ser asociada a vocabularios controlados. Se asume que otros vocabularios controlados serán desarrollados para asegurar esta interoperabilidad en dominios especÃficos. Cada elemento es opcional y puede repetirse. Además, los elementos pueden aparecer en cualquier orden. Aunque algunos entornos, como HTML, no diferencian entre mayúsculas y minúsculas, es recomendable escribir correctamente cada metadata según su definición para evitar conflictos con otros entornos, como XML (Extensible Markup Language) http://www.w3.org/TR/PR-xml
+
+
+
+
+ دؚÙÙÙ ÙÙر
+ ÙرØØš ØšÙÙ
+ Ù٠صÙØØ© د ØšÙÙÙ Ù٠ر ؚاÙعرؚ٠ÙÙ Ùذ٠اÙصÙØØ© ٠ؚاÙتعاÙÙ Ù
+ع اÙاخÙا٠اÙعرؚ Ù
+٠اÙÙ
+ÙØªØšØ§ØªØ Ø¯Ø§Ø± اÙÙØŽØ±Ø Ø§ÙØšØÙØ« اÙعÙÙ
+ÙØ© Ù Ùر؎ة عÙ
+ÙWorking Group On Multilingual Dublin Core (DC-International) Ø
+
+
+
+
+ éœæææ žå¿å
+æ°æ®å
+çŽ é1.1çïŒåèæè¿°
+ æ¬ææ¡£å
+³äºéœæææ žå¿å
+æ°æ®å
+çŽ é1.1çæ¬çåèæè¿°ãæ€æè¿°äžå·²ç»æ亀ç»ISOçšäºåœé
+æ祚çNISOå®æ¹æ åä¿æäžèŽã éœæææ žå¿å
+æ°æ®éæ¯äžç§è·šé¢åçä¿¡æ¯èµæºæè¿°æ åãè¿éçä¿¡æ¯èµæºè¢«å®ä¹äžºâä»»äœå
+·ææ è¯çäžè¥¿âãæ€å®ä¹æ¥èªäºTim Berners-Leeç人æèçInternet RFC2396 "Uniform Resource Identifiers (URI): Generic Syntax"æ件ãéœæææ žå¿å
+æ°æ®çåºçšé¢å没ææ ¹æ¬çéå¶ã
+
+
+
+
+ Soubor metadatovÃœch prvků Dublin Core, verze 1.1: referenÄnà popis
+ Tento dokument je ÄeskÃœm pÅekladem anglické verze referenÄnÃho popisu souboru metadatovÃœch prvků Dublin Core, verze 1.1 [DCEN1.1]. Tento dokument nahrazuje ÄeskÃœ pÅeklad souboru metadatovÃœch prvků Dublin Core, verze 1.0 [DCCS1.0]. DalÅ¡Ã informace o pracovnÃch semináÅÃch (workshopech), zprávách, studiÃch pracovnÃch skupin, projektech a dalÅ¡Ãm vÃœvoji souboru metadatovÃœch prvků Dublin Core najdete na domovské stránce Dublin Core (http://purl.org/dc)
+
+
+
+
+ Rapporten Dublin Core Simple Format
+ Dit document beschrijft welke Dublin Core metadata elementen er zijn en geeft een korte definitie van elk element. Voor uitgebreide uitleg en gebruik van de Dublin Core elementen wordt u verwezen naar de gebruikershandleiding. Deze vertaling geeft ook de keuzes aan voor standaarden (taalcodes, datum codes) die wij in DONOR verband gaan hanteren. In zoverre kan deze vertaling afwijken van het oorspronkelijke document "Description of Dublin Core Elements" http://purl.org/metadata/dublin_core_elements"
+
+
+
+
+
+
+
+
+
+
+ Collection de elementos de metadatos de Dublin Core, version 1.1: Description de referentia
+ Isto es un traduction de un Recommendation del Dublin Core Metadata Initiative. Le publication como un recommendation significa que le specificationes es stabile e su adoption es supportate per le communitate Dublin Core (http://purl.org/dc/).
+
+
+
+
+ à€¡à€¬à¥à€²à€¿à€š à€à¥à€° à€®à¥à€à€Ÿà€¡à¥à€à€Ÿ à€žà¥à€ à€à€µà¥à€€à¥à€€à¥ १.१ à€žà€à€Šà€°à¥à€ à€žà¥à€ªà€·à¥à€à¥à€à€°à€£ १.१ à€¡à€¬à¥à€²à€¿à€š à€à¥à€° à€®à¥à€à€Ÿà€¡à¥à€à€Ÿà€à€µà¥à€€à¥à€€à¥ १.१.
+ १.१ à€¡à€¬à¥à€²à€¿à€š à€à¥à€° à€®à¥à€à€Ÿà€¡à¥à€à€Ÿ à€¹à¥ à€µà¥à€à€µà¥à€à€³à¥à€¯à€Ÿ à€µà€¿à€·à€¯à€Ÿà€€à¥à€² à€®à€Ÿà€¹à¥à€€à¥ à€žà€Ÿà€ à¥à€¯à€Ÿà€à€µà€Šà¥à€Šà€²à€à¥ à€®à€Ÿà€¹à¥à€€à¥ à€Šà¥à€£à¥à€¯à€Ÿà€à¥ à€®à€Ÿà€šà€ à€à€¹à¥. à€¯à€Ÿà€€ à€®à€Ÿà€¹à¥à€€à¥à€žà€Ÿà€ à€Ÿ à€®à¥à€¹à€£à€à¥ à€à¥à€¯à€Ÿà€²à€Ÿ à€à€³à€ à€à€¹à¥ à€
+à€žà€Ÿ à€à€žà€€à¥. à€
+à€¶à€Ÿ à€ªà¥à€°à€à€Ÿà€°à€à¥ à€µà¥à€¯à€Ÿà€à¥à€¯à€Ÿ à€®à€Ÿà€¹à¥à€€à¥ à€à€Ÿà€³à¥à€¯à€µà€°à¥à€² à€. à€à€«.à€žà¥. ग़३९६URI: Generic Syntax -- Tim Berners Lee et al. à€¡à€¬à¥à€²à€¿à€š à€à¥à€° à€®à€Ÿà€šà€ à€à¥à€£à€€à¥à€¯à€Ÿà€¹à¥ à€ªà¥à€°à€à€Ÿà€°à€à¥à€¯à€Ÿ à€®à€Ÿà€¹à¥à€€à¥ à€žà€Ÿà€ à¥à€¯à€Ÿà€à€žà€Ÿà€ à¥ à€µà€Ÿà€ªà€°à€€à€Ÿ à€¯à¥à€€à¥. à€€à¥à€¯à€Ÿà€žà€Ÿà€ ॠà€à¥à€£à€€à€Ÿà€¹à¥ à€®à€à¥à€à€Ÿà€µ à€šà€Ÿà€¹à¥.
+
+
+
+
+ à®à®ªà¯à®³à®¿à®©à¯ à®à¯à®°à¯ à®®à¯à®€à®°à®µà¯ à®à®±à¯à®ªà¯à®ªà¯ à®à®£à®®à¯ ப஀ிபà¯à®ªà¯ 1.1: à®à¯à®±à®¿à®ªà¯à®ªà¯ விவரமà¯
+ à®à®šà¯à®€ à®à®µà®£à¯à®®à¯ à®à®ªà¯à®³à®¿à®©à¯ à®à¯à®°à¯ à®®à¯à®€à®°à®µà¯ à®à®±à¯à®ªà¯à®ªà¯ à®à®£à®®à¯ ப஀ிபà¯à®ªà¯ 1.1 à®à¯à®±à®¿à®ªà¯à®ªà¯ விவரமடà®à¯à®®à¯. à®à®šà¯à®€ à®à®µà®£à¯à®®à¯ à®à®ªà¯à®³à®¿à®©à¯ à®à¯à®°à¯ à®®à¯à®€à®°à®µà¯ à®à®±à¯à®ªà¯à®ªà¯ à®à®£à®®à¯ ப஀ிபà¯à®ªà¯ 1.0 வ௠à®à®°à®¿à®µà¯à®ªà¯à®ªà¯à®à®¿à®°à®€à¯. வரà¯à®à¯à®·à®Ÿà®ªà®ªà¯à®à¯à®à®³à¯, à®
+றிà®à¯à®à¯à®à®³à¯, à®à¯à®¯à®²à¯ à®à¯à®Žà¯ ஀டளà¯à®à®³à¯, ஀ிà®à¯à®à®ªà¯à®ªà®£à®¿à®à®³à¯, à®®à¯à®²à¯à®®à¯ à®à®ªà¯à®³à®¿à®©à¯ à®à¯à®°à¯ à®®à¯à®€à®°à®µà¯ à®à®±à¯à®ªà¯à®ªà¯ à®à®£à®®à¯ ப஀ிபà¯à®ªà¯ பà¯à®€à®¿à®¯ விரà¯à®€à¯à®€à®¿ பறà¯à®±à®¿ à®à¯à®à¯à®€à®²à¯ ஀à®à®µà®²à¯à®à¯à®à¯ à®à®ªà¯à®³à®¿à®©à¯ à®à¯à®°à¯ à®à®²à¯à®² பà®à¯à®à®€à¯à®€à®¿à®²à¯ படரà¯à®à¯à®à®µà¯à®®à¯ (http://dublincore.org)
+
+
+
+
+ Yếu tá» Siêu dữ liá»u Dublin Core, phiên bản 1.1: Tham chiếu
+
+
+
+
+
+ Title
+ A name given to the resource.
+ Typically, a Title will be a name by which the resource is formally known.
+
+
+
+ Taitara
+ Te ingoa ka tapaina tetahi rauemi.
+ Ko te tikanga, ko te Taitara te ingoa ka mohio whanuitia te ingoa.
+
+
+
+ Titre
+ Le nom donné à la ressource.
+ Typiquement, un titre sera le nom par lequel la ressource est officiellement connue.
+
+
+
+ ÐазваМОе
+ ÐÐŒÑ, ЎаММПе ÑеÑÑÑÑÑ.
+ ÐбÑÑМП МазваМОеЌ ÑвлÑеÑÑÑ ÐžÐŒÑ, пПЎ кПÑПÑÑÐŒ ÑеÑÑÑÑ ÐŸÑОÑОалÑМП ОзвеÑÑеМ.
+
+
+
+ TÃtulo
+ El nombre dado a un recurso, usualmente por el autor.
+
+
+
+ اÙعÙÙاÙ
+ Ùذا اÙاسÙ
+ Ùعط٠ÙÙÙ
+صدر, Ù
+Ù Ùؚ٠اÙÙ
+ؚدع ا٠اÙÙا؎ر
+
+
+
+ èµæºå
+ èµäºèµæºçå称ã
+ èµæºåäžè¬æèµæºå¯¹è±¡æ£åŒå
+¬åŒçå称ã
+
+
+
+ Název
+ Jméno dané zdroji.
+ Název bude typicky jméno, pod nÃmÅŸ je zdroj oficiálnÄ znám.
+
+
+
+ Titel
+ De naam van de Internetbron. Meestal gegeven door de auteur, maker of uitgever
+
+
+
+
+
+
+
+
+
+ Titulo
+ Un nomine date al ressource.
+ Typicamente se utiliza un nomine per le qual le ressource es formalmente cognite.
+
+
+
+ à€¶à¥à€°à¥à€·à€
+ à€ªà€°à¥à€¯à€Ÿà€¯à¥ à€¶à¥à€°à¥à€·à€
+ à€žà€à€à¥à€·à€¿à€ªà¥à€€ , à€à€Ÿà€·à€Ÿà€à€€à€°à¥à€€ à€¶à¥à€°à¥à€·à€
+
+
+
+ ஀லà¯à®ªà¯à®ªà¯
+ வள஀à¯à®€à®¿à®°à¯à®à¯à®à¯ à®à¯à®à¯à®€à¯à®€ பà¯à®¯à®°à¯.
+ ஀லà¯à®ªà¯à®ªà¯
+
+
+
+ Nhan Äá»
+ Tên Äược gán cho nguá»n tin
+
+
+
+ 1.1
+ Dublin Core Metadata Initiative
+ Optional
+ Character String
+ Unlimited
+
+
+
+
+ Creator
+ An entity primarily responsible for making the content of the resource.
+ Examples of a Creator include a person, an organisation, or a service. Typically, the name of a Creator should be used to indicate the entity.
+
+
+
+ Kaihanga
+ Te putahi, nana, na ratou ranei i matua oti ai te hanganga o te rauemi.
+ Ko te tangata, he putahitanga, he ratonga ranei etahi tauira Kaihanga. Ko te tikanga, ko te Kaihanga te ingoa ka whakamahia hei tohu i te putahi na ratou te hanganga.
+
+
+
+ Créateur
+ L'entité principalement responsable de la création du contenu de la ressource.
+ Exemples de Créateur incluent une personne, une organisation, ou un service. Typiquement, un nom du Créateur devrait être utilisé pour désigner cette entité.
+
+
+
+ СПзЎаÑелÑ
+ ÐОÑП, МеÑÑÑее пеÑвОÑÐœÑÑ ÐŸÑвеÑÑÑвеММПÑÑÑ Ð·Ð° ÑПзЎаМОе ÑПЎеÑÐ¶Ð°ÐœÐžÑ ÑеÑÑÑÑа.
+ ÐÑОЌеÑÑ Ð¡ÐŸÐ·ÐŽÐ°ÑÐµÐ»Ñ Ð²ÐºÐ»ÑÑаÑÑ Ð¿ÐµÑÑПМÑ, ПÑгаМОзаÑÐžÑ ÐžÐ»Ðž ÑлÑжбÑ. ÐбÑÑМП ÐžÐŒÑ Ð¡ÐŸÐ·ÐŽÐ°ÑÐµÐ»Ñ ÐžÑпПлÑзÑеÑÑÑ ÐŽÐ»Ñ ÐžÐœÐŽÐžÐºÐ°ÑОО ПбÑекÑа.
+
+
+
+ Autor o Creador
+ La persona u organización responsable de la creación del contenido intelectual del recurso. Por ejemplo, los autores en el caso de documentos escritos, artistas, fotografos e ilustradores en el caso de recursos visuales.
+
+
+
+ اÙÙاتؚ ا٠اÙÙ
+ؚدع
+ Ù٠اÙ؎خص ا٠اÙÙ
+؀سسة Ø£ÙÙا ع٠ÙØŽØŠ اÙÙ
+ØتÙ٠اÙÙÙر Ù ÙÙÙ
+صدر , عÙ٠سؚÙ٠اÙÙ
+ثا٠, اÙÙ
+Ø€ÙÙÙÙ ÙÙ ØاÙØ© اÙثا؊٠اÙÙ
+ÙتÙؚة , ٠اÙÙÙاÙÙÙ , اÙÙ
+صÙرÙÙ ÙÙ ØاÙØ© اÙÙ
+صادر اÙÙ
+ر؊ÙØ©
+
+
+
+ å建è
+
+ å建èµæºå
+容çäž»èŠèŽ£ä»»è
+ã
+ å建è
+çå®äŸå
+æ¬äžªäººïŒç»ç»ææ项æå¡ãäžè¬èèšïŒçšå建è
+çå称æ¥æ è¯è¿äžæ¡ç®ã
+
+
+
+ Tvůrce
+ Entita primárnÄ odpovÄdná za vytvoÅenà obsahu zdroje.
+ PÅÃklady Tvůrce zahrnujà osobu, organizaci nebo sluÅŸbu. K oznaÄenà entity se typicky pouÅŸÃvá jméno tvůrce.
+
+
+
+ Auteur of maker
+ De auteur, maker of organisatie die primair verantwoordelijk is voor de intellectuele inhoud van het werk. Bijvoorbeeld auteurs in geval van geschreven documenten, artiesten, fotografen of illustrators in geval van visuele bronnen.
+
+
+
+
+
+
+
+
+
+ Creator
+ Le entitate primarimente responsabile pro producer le contento del ressource.
+ Exemplos de creator include un persona, un organization, o un servicio. Typicamente se utiliza un nomine de creator pro indicar iste entitate.
+
+
+
+ à€šà€¿à€°à¥à€®à€Ÿà€€à€Ÿ, à€à€šà€
+ à€®à€Ÿà€¹à€¿à€€à¥à€žà€Ÿà€ à€Ÿ à€šà€¿à€°à¥à€®à€Ÿà€£ à€à€°à€£à€Ÿà€°à€Ÿ
+ à€à€Šà€Ÿ. à€²à¥à€à€, à€²à¥à€à€¿à€à€Ÿ, à€µà¥à€¯à€à¥à€€à¥, à€žà€à€žà¥à€¥à€Ÿ, à€žà€à€ªà€Ÿà€Šà€, à€žà€à€ªà€Ÿà€Šà€¿à€à€Ÿ
+
+
+
+ à®à®£à¯à®à®Ÿà®à¯à®à®¿à®¯à®µà®°à¯
+ à®à®°à¯ வள஀à¯à®€à®¿à®©à¯ à®à®³à¯à®³à®à®à¯à®à®€à¯à®€à¯ à®à¯à®¯à¯à®€à®€à®°à¯à®à¯à®à¯ à®®à¯à®à¯à®à®¿à®¯à®®à®Ÿà® பà¯à®±à¯à®ªà¯à®ªà¯à®³à¯à®³ பà¯à®°à¯à®³à¯.
+ à®à®°à¯ à®à®£à¯à®à®Ÿà®à¯à®à®¿à®¯à®µà®°à®¿à®©à¯ à®à®€à®Ÿà®à®°à®£à®®à¯: à®à®°à¯ சபரà¯, à®à®°à¯ à®à¯à®Žà¯, à®
+லà¯à®²à®€à¯ à®à®°à¯ à®à¯à®µà¯. à®à®°à¯ பà¯à®°à¯à®³à¯ à®à¯à®±à®¿à®ªà¯à®ªà®€à®°à¯à®à¯à®à¯ à®à®£à¯à®à®Ÿà®à¯à®à®¿à®¯à®µà®°à®¿à®©à¯ பà¯à®¯à®°à¯ à®à®ªà®¯à¯à®à®¿à®à¯à®à®µà¯à®£à¯à®à¯à®®à¯.
+
+
+
+ Tác giả
+ Pháp nhân chá»u trách nhiá»m chÃnh trong viá»c tạo ra ná»i dung của nguá»n tin
+ Pháp nhân trong tác giả có thá» là tên ngÆ°á»i, tên cÆ¡ quan, tá» chức chá»u trách nhiá»m vá» nÃŽi dung tà i liá»u
+
+
+ 1.1
+ Dublin Core Metadata Initiative
+ Optional
+ Character String
+ Unlimited
+
+
+
+
+ Subject and Keywords
+ The topic of the content of the resource.
+ Typically, a Subject will be expressed as keywords, key phrases or classification codes that describe a topic of the resource. Recommended best practice is to select a value from a controlled vocabulary or formal classification scheme.
+
+
+
+ Kaupapa
+ Te take/ nga take o te kaupapa, o te rauemi.
+ Ko te tikanga, ka whakaaturia te kaupapa o te rauemi e nga kupu matua, nga kimahi matua, nga tohu wehewehenga whakaahua ranei.
+
+
+
+ Sujet
+ Le sujet du contenu de la ressource.
+ Typiquement, le sujet sera décrit par un ensemble de mots-clefs ou de phrases ou un code de classification qui précisent le sujet de la ressource. L'utilisation de vocabulaires contrÎlés et de schémas formels de classification est encouragée.
+
+
+
+ ÐÑÐµÐŽÐŒÐµÑ Ðž клÑÑевÑе ÑлПва
+ ТеЌа ÑПЎеÑÐ¶Ð°ÐœÐžÑ ÑеÑÑÑÑа.
+ ÐбÑÑМП ÐÑÐµÐŽÐŒÐµÑ Ð²ÑÑажаеÑÑÑ Ñ Ð¿ÐŸÐŒÐŸÑÑÑ ÐºÐ»ÑÑевÑÑ
+ ÑлПв, клÑÑевÑÑ
+ ÑÑаз ОлО клаÑÑОÑОкаÑОПММÑÑ
+ кПЎПв, кПÑПÑÑе ПпОÑÑваÑÑ ÑÐµÐŒÑ ÑеÑÑÑÑа. ÐÐ»Ñ Ð¿ÑакÑОÑеÑкПгП ОÑпПлÑÐ·ÐŸÐ²Ð°ÐœÐžÑ ÑекПЌеМЎÑеÑÑÑ Ð²ÑбОÑаÑÑ Ð·ÐœÐ°ÑеМОе Оз кПМÑÑПлОÑÑеЌПгП ÑлПваÑÑ ÐžÐ»Ðž ÑПÑЌалÑМПй клаÑÑОÑОкаÑОПММПй ÑÑ
+еЌÑ.
+
+
+
+ Claves
+ Los tópicos del recurso. TÃpicamente, Subject expresará las claves o frases que describen el tÃtulo o el contenido del recurso. Se fomentará el uso de vocabularios controlados y de sistemas de clasificación formales. Se pueden ver ejemplos de vocabularios controlados en: Controlled vocabularies, thesauri and classification systems available in the WWW. DC Subject
+
+
+
+ اÙÙ
+ÙضÙع ٠اÙÙÙÙ
+ات اÙر؊ÙسÙØ©
+ ÙÙ Ù
+ÙضÙع اÙÙ
+صدر. ÙÙ
+ÙذجÙا Ùعؚر ع٠اÙÙ
+ÙضÙع ؚاستخداÙ
+Ù
+ÙØªØ§Ø Ø§ÙÙÙÙ
+ات ا٠جÙ
+٠اÙت٠تص٠Ù
+ÙضÙع ا٠Ù
+ØتÙ٠اÙÙ
+صدر , Ù ÙستØس٠استخداÙ
+ Ù
+Ùردات Ù
+خططة٠Ù
+ØÙÙ
+Ø© ÙادÙØ© تصÙÙÙ ØŽÙÙÙØ©
+
+
+
+ äž»é¢åå
+³é®è¯
+ èµæºå
+容çäž»é¢æè¿°ã
+ åŠæèŠæè¿°ç¹å®èµæºçæäžäž»é¢ïŒäžè¬éçšå
+³é®è¯ãå
+³é®åçè¯æåç±»å·ïŒæ奜䞻é¢åå
+³é®è¯ä»åæ§ è¯è¡šæè§èçåç±»äœç³»äžååŒã
+
+
+
+ PÅedmÄt a klÃÄová slova
+ Téma obsahu zdroje.
+ PÅedmÄt bude typicky vyjádÅen pomocà klÃÄovÃœch slov, klÃÄovÃœch frázà nebo klasifikaÄnÃch znaků popisujÃcÃch téma zdroje. DoporuÄuje se vybÃrat hodnotu prvku z ÅÃzeného slovnÃku nebo formálnÃho klasifikaÄnÃho schématu.
+
+
+
+ Onderwerp en trefwoorden
+ Het onderwerp van de Internetbron. Het onderwerp wordt beschreven in korte zinnen of door het gebruik van trefwoorden. Het gebruik van gecontroleerde trefwoorden of classificatie schema's wordt aanbevolen.
+
+
+
+
+
+
+
+
+
+ Subjecto e parolas-clave
+ Le topico del contento del ressource.
+ Typicamente le subjecto es expresse per medio de parolas-clave, phrases-clave, o codices de classification que describe le topico del ressource. Le melior practica recommendate es selectionar un valor a partir de un vocabulario controlate o un schema formal de classification.
+
+
+
+ à€µà€¿à€·à€¯
+ à€µà€¿à€·à€¯
+ à€®à€Ÿà€¹à€¿à€€à¥à€žà€Ÿà€ à€Ÿ, à€à¥à€à€Ÿà€šà€žà€Ÿà€§à€šà¥ à€¯à€Ÿà€€à¥à€² à€à€¶à€¯ à€žà¥à€ªà€·à¥à€ à€à€°à€£à€Ÿà€°à¥ à€¶à€¬à¥à€Š, à€µà€¿à€·à€¯à€Ÿà€à¥ à€µà€°à¥à€à¥à€à€°à€£ à€à€°à€€à€Ÿà€šà€Ÿ à€¶à€¬à¥à€Šà€žà€à€à¥à€°à€¹ à€
+à€¥à€µà€Ÿ à€¶à€¬à¥à€Š à€à¥à€·à€Ÿà€à€Ÿ à€µà€Ÿà€ªà€° à€à€°à€Ÿà€µà€Ÿ
+
+
+
+ விஷயமà¯à®®à¯ à®®à¯à®€à®©à¯à®®à¯à®à¯ à®à¯à®²à¯à®à®³à¯à®®à¯
+ வள஀à¯à®€à®¿à®©à¯ à®à®³à¯à®³à®à®à¯à®à®€à¯à®€à®¿à®©à¯ விஷயமà¯.
+ à®à®€à®Ÿà®à®°à®£à®®à®Ÿà®, à®à®°à¯ விஷய஀à¯à®€à¯ à®®à¯à®€à®©à¯à®®à¯à®à¯ à®à¯à®²à¯à®à®³à®Ÿà®à®µà¯, à®®à¯à®€à®©à¯à®®à¯à®à¯ à®à¯à®±à¯à®±à¯à®à®°à®Ÿà®à®µà¯ à®
+லà¯à®²à®€à¯ வà®à¯à®ªà¯à®ªà®à¯à®€à¯à®€à¯à®®à¯ à®à¯à®±à®¿à®®à¯à®±à¯à®à®³à®Ÿà®à®µà¯ வள஀à¯à®€à®¿à®©à¯ விஷய஀à¯à®€à¯ விவரிà®à¯à®à¯à®®à¯. à®à®°à¯ à®à®à¯à®à¯à®ªà¯à®ªà®à¯à® à®à¯à®²à¯ வள஀à¯à®€à®¿à®²à®¿à®°à¯à®šà¯à®€à¯ à®
+லà¯à®²à®€à¯ à®®à¯à®±à¯à®¯à®Ÿà®© வà®à¯à®ªà®à¯à®€à¯à®€à¯à®®à¯ ஀ிà®à¯à®à®€à¯à®€à®¿à®²à®¿à®°à¯à®šà¯à®€à¯ à®à®°à¯ ம஀ிபà¯à®ªà¯ ஀à¯à®°à¯à®šà¯à®€à¯à®à¯à®à¯à®à¯à®µà®€à¯ சடà®à¯à®à®³à¯ à®à®¿à®ªà®Ÿà®°à®à¯ à®à¯à®¯à¯à®µà®€à¯ à®®à¯à®²à¯à®€à®°à®®à¯ à®à¯à®¯à®²à¯.
+
+
+
+ Chủ Äá»
+ Chủ Äá» và /hoặc Äá» mục chÃnh của ná»i dung của nguá»n tin
+ Chủ Äá» Äược thá» hiá»n bằng từ khoá, cụm từ, kÃœ hiá»u phân loại, chá» sá» Äá» mục,...Vên sá» dụng từ vá»±ng có kiá»m soát
+
+
+ 1.1
+ Dublin Core Metadata Initiative
+ Optional
+ Character String
+ Unlimited
+
+
+
+
+ Description
+ An account of the content of the resource.
+ Description may include but is not limited to: an abstract, table of contents, reference to a graphical representation of content or a free-text account of the content.
+
+
+
+ Whakaaturanga
+ He whakaaturanga o nga kaupapa o te rauemi.
+ Ka uru atu, engari ehara noa ko: te whakarapopototanga korero, te ihirangi, te tohutanga o te kaupapa ma te whakaahua, te whakaaturanga kore kupu ranei, o te kauapapa.
+
+
+
+ Description
+ Une description du contenu de la ressource.
+ Une Description peut contenir, mais ce n'est pas limitatif: un résumé, une table des matiÚres, une référence à une représentation graphique du contenu, ou un texte libre sur le contenu.
+
+
+
+ ÐпОÑаМОе
+ СППбÑеМОе П ÑПЎеÑжаМОО ÑеÑÑÑÑа.
+ ÐпОÑаМОе ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ Ð¿ÑеЎÑÑавлеМП (пП МеПбÑ
+ПЎОЌПÑÑО) в вОЎе: ÑеÑеÑаÑа, ПглавлеМОÑ, ÑÑÑлкО Ма гÑаÑОÑеÑкПе пÑеЎÑÑавлеМОе ÑПЎеÑÐ¶Ð°ÐœÐžÑ ÐžÐ»Ðž пÑПÑÑПгП ÑекÑÑПвПгП ОзлПжеМОе ÑПЎеÑжаМОÑ.
+
+
+
+ Descripción
+ Una descripción textual del recurso, tal como un resumen en el caso de un documento o una descripción del contenido en el caso de un documento visual.
+
+
+
+ اÙÙصÙ
+ ÙÙ Ùص٠Ùص٠ÙÙ
+ØتÙ٠اÙÙ
+صدر, ÙÙضÙ
+ اÙÙ
+Ùخصات ÙÙ ØاÙØ© اÙÙثا؊٠Ù
+ث٠اÙا؎Ùاء اÙÙ
+ÙتÙؚة ا٠تÙصÙ٠اÙÙ
+ØتÙÙ ÙÙ ØاÙØ© اÙÙ
+صادر اÙÙ
+ر؊ÙØ©
+
+
+
+ 诎æ
+ èµæºå
+容ç解é
+ 诎æå¯ä»¥å
+æ¬äœäžéäºä»¥äžå
+容ïŒææãç®åœã对以åŸåœ¢æ¥æ瀺å
+容çèµæºèèšçæå诎æãæè
+äž äžªæå
+³èµæºå
+容çèªç±ææ¬æè¿°ã
+
+
+
+ Popis
+ VysvÄtlenà obsahu zdroje.
+ Popis můşe obsahovat (mimo jiné): abstrakt, obsah, odkaz na grafické nebo volné textové vyjádÅenà obsahu.
+
+
+
+ Omschrijving
+ Een omschrijving van de inhoud van de Internetbron. Abstracts of inhoudsomschrijvingen.
+
+
+
+
+
+
+
+
+
+ Description
+ Un description del contento del ressource.
+ Le description pote includer, ma non se limita a: summario, indice, referentia a un representation graphic del contento o un texto libere a proposito del contento.
+
+
+
+ à€µà€°à¥à€£à€š
+ à€®à€Ÿà€¹à€¿à€€à¥à€žà€Ÿà€ à¥à€¯à€Ÿà€à¥, à€à¥à€à€Ÿà€šà€žà€Ÿà€§à€šà€Ÿà€à¥à€µà€°à¥à€£à€š
+ à€®à€Ÿà€¹à€¿à€€à¥à€žà€Ÿà€ à¥à€¯à€Ÿà€à¥ à€šà€¿à€µà¥à€Šà€š, à€à€²à¥à€, à€à€¿à€€à¥à€°à€°à¥à€ª
+
+
+
+ விவரி஀à¯à®€à®²à¯
+ வள஀à¯à®€à®¿à®©à¯ à®à®³à¯à®³à®à®à¯à®à®€à¯à®€à¯ பறà¯à®±à®¿ விவரி஀à¯à®€à®²à¯
+ à®à®°à¯ à®à¯à®°à¯à®°à¯à®à¯à®à®®à¯, à®à®³à¯à®³à®à®à¯à®à®®à¯ பà®à¯à®à®¿à®¯à®²à¯, à®à®³à¯à®³à®à®à¯à®à®€à¯à®€à¯ வரவியலட஠à®à¯à®±à®¿à®ªà¯à®ªà¯à®à¯ à®à®à¯à®à®¿à®²à¯à®²à®Ÿà®€ à®à®°à¯à®¯à®¿à®©à¯ à®à®³à¯à®³à®à®à¯à®à®®à¯ விளà®à¯à®à®®à¯, à®à®µà¯à®à®³à¯à®®à¯ à®à®©à¯à®©à¯à®®à¯ à®®à¯à®²à¯à®®à¯ விவரி஀à¯à®€à®²à¯à®²à®¿à®²à¯ à®à¯à®°à¯à®€à¯à®€à¯à®à¯à®à¯à®³à¯à®³à®²à®Ÿà®®à¯.
+
+
+
+ MÎ tả
+ Má»t thÃŽng báo là m rõ ná»i dung của nguá»n tin
+ MÃŽ tả có thá» bao gá»m: tóm tắt ngắn gá»n. mục lục, ThÃŽng tin tham chiếu vá» bảng biá»i. vá» nguá»n tin
+
+
+ 1.1
+ Dublin Core Metadata Initiative
+ Optional
+ Character String
+ Unlimited
+
+
+
+
+ Publisher
+ An entity responsible for making the resource available.
+ Examples of a Publisher include a person, an organisation, or a service. Typically, the name of a Publisher should be used to indicate the entity.
+
+
+
+ Kaiwhakaputa
+ Te putahi nana i whakaputa te rauemi.
+ Ko te tangata, he putahitanga, he ratonga ranei etahi tauira Kaiwhakaputa. Ko te tikanga, ka whakamahia te ingoa o te Kaiwhakaputa hei tohu i te putahi.
+
+
+
+ Editeur
+ L'entité responsable de la diffusion de la ressource, dans sa forme actuelle, tels, un département universitaire, une entreprise.
+ Exemples d'Editeurs incluent une personne, une organisation, ou un service. Typiquement, le nom d'une maison d'édition devrait être utilisé ici.
+
+
+
+ ÐзЎаÑелÑ
+ ÐОÑП, ПÑвеÑÑÑвеММПе за ввПЎ ÑеÑÑÑÑа в ПбÑаÑеМОе.
+ ÐÑОЌеÑÑ ÐзЎаÑÐµÐ»Ñ Ð²ÐºÐ»ÑÑаÑÑ Ð¿ÐµÑÑПМÑ, ПÑгаМОзаÑÐžÑ ÐžÐ»Ðž ÑлÑжбÑ. ÐбÑÑМП ÐžÐŒÑ ÐзЎаÑÐµÐ»Ñ ÐžÑпПлÑзÑеÑÑÑ ÐŽÐ»Ñ ÐžÐœÐŽÐžÐºÐ°ÑОО ПбÑекÑа.
+
+
+
+ Editor
+ >La entidad responsable de hacer que el recurso se encuentre disponible en la red en su formato actual, por ejemplo la empresa editora, un departamento universitario u otro tipo de organización.
+
+
+
+ اÙÙا؎ر
+ Ù٠اÙÙÙ؊ة اÙÙ
+س؀ÙÙØ© ع٠صÙاعة اÙÙ
+صدر اÙÙ
+تÙÙر ÙÙ ØاÙت٠اÙØاضرة, Ù
+ث٠دار اÙÙ؎ر, ÙسÙ
+ جاÙ
+ع٠ا٠Ù
+؀سسة اعÙ
+اÙ
+
+
+
+ åºçè
+
+ 䜿èµæºæ䞺å¯ä»¥è·åŸå¹¶å¯çšç莣任è
+ã
+ åºçè
+çå®äŸå
+æ¬äžªäœïŒç»ç»ïŒææå¡ãäžè¬èèšïŒåºè¯¥çšåºçè
+çå称æ¥æ è¯è¿äžæ¡ç®ã
+
+
+
+ Vydavatel
+ Entita odpovÄdná za zpÅÃstupnÄnà zdroje.
+ PÅÃklady Vydavatele zahrnujà osobu, organizaci nebo sluÅŸbu. K oznaÄenà entity se typicky pouÅŸÃvá jméno vydavatele.
+
+
+
+ Uitgever
+ De entiteit die verantwoordelijk is voor het beschikbaarstellen van de Internetbron in de huidig vorm. Bijvoorbeeld een uitgeversbedrijf, een universiteitsafdeling.
+
+
+
+
+
+
+
+
+
+ Editor
+ Un entitate responsabile pro disponibilizar le ressource.
+ Exemplos de editor include un persona, un organization, o un servicio. Typicamente se utiliza un nomine de editor pro indicar le entitate.
+
+
+
+ à€ªà¥à€°à€à€Ÿà€¶à€
+ à€®à€Ÿà€¹à€¿à€€à¥à€žà€Ÿà€ à€Ÿ à€à€ªà€²à€¬à¥à€§ à€à€°à¥à€š à€Šà¥à€£à€Ÿà€°à€Ÿ
+ à€à€Šà€Ÿ.à€ à€ªà¥à€°à€à€Ÿà€¶à€ , à€ªà¥à€°à€à€Ÿà€¶à€š à€žà€à€žà¥à€¥à€Ÿ, à€žà¥à€µà€Ÿ à€®à€Ÿà€¹à€¿à€€à¥ à€à€Ÿà€ªà¥à€² à€°à¥à€ªà€Ÿà€€ à€
+à€¥à€µà€Ÿ à€à€à€à€°à€šà¥à€ à€µà€° à€à€ªà€²à€¬à¥à€§ à€à€°à¥à€š à€Šà¥à€£à€Ÿà€°à€Ÿ
+
+
+
+ பிரà®à¯à®°à®à®°à¯à®€à¯à®€à®Ÿ
+ வள஀à¯à®€à¯ à®à®¿à®à¯à®à¯à® à®à¯à®¯à¯à®€à®€à®°à¯à®à¯à®à¯ பà¯à®±à¯à®ªà¯à®ªà¯à®³à¯à®³ à®à®°à¯ பà¯à®°à¯à®³à¯.
+ à®à®€à®Ÿà®à®°à®£à®®à¯: à®à®°à¯ பிரà®à¯à®°à®à®°à¯à®€à¯à®€à®Ÿ à®à®©à¯à®±à®Ÿà®²à¯ à®à®°à¯ சபரà¯, à®à®°à¯ à®à¯à®Žà¯, à®
+லà¯à®²à¯à®€à¯ à®à®°à¯ à®à¯à®µà¯. à®
+சà¯à®€ பà¯à®°à¯à®³à¯ à®à¯à®±à®¿à®ªà¯à®ªà®¿à® பிரà®à¯à®°à®à®°à¯à®€à¯à®€à®Ÿà®µà®¿à®©à¯ பà¯à®¯à®°à¯ à®à®ªà®¯à¯à®à®ªà®à¯à®€à¯à®€à®µà¯à®®à¯.
+
+
+
+ Cơ quan xuất bản
+ Tá» chức chá»u trách nhiá»m là m cho nguá»n tin nà y có thá» truy xuất Äược
+ Ghi tên cá nhân, tá» chức cÆ¡ quan chá»u trách nhiá»m vá» xuất bản nguá»n tin
+
+
+ 1.1
+ Dublin Core Metadata Initiative
+ Optional
+ Character String
+ Unlimited
+
+
+
+
+ Contributor
+ An entity responsible for making contributions to the content of the resource.
+ Examples of a Contributor include a person, an organisation, or a service. Typically, the name of a Contributor should be used to indicate the entity.
+
+
+
+ Kaiwhakaaro
+ Te putahi nana, na ratou ranei nga whakakaupapatanga whakaaro o te rauemi.
+ Ko te tangata, he putahitanga, he ratonga ranei etahi tauira Kaiwhakaaro. Ko te tikanga ka whakamahia te ingoa o te Kaiwhakaaro hei tohu i te putahi.
+
+
+
+ Contributeur
+ Une entité qui a contribué à la création du contenu de la ressource.
+ Exemples de Contributeur incluent une personne, une organisation, ou un service. Typiquement, le nom d'un contributeur devrait être utilisé ici pour désigner l'entité.
+
+
+
+ СПОÑпПлМОÑелÑ
+ ÐОÑП, вМеÑÑее вклаЎ в ÑПзЎаМОе ÑПЎеÑÐ¶Ð°ÐœÐžÑ ÑеÑÑÑÑа.
+ ÐÑОЌеÑÑ Ð¡ÐŸÐžÑпПлМОÑÐµÐ»Ñ Ð²ÐºÐ»ÑÑаÑÑ Ð¿ÐµÑÑПМÑ, ПÑгаМОзаÑÐžÑ ÐžÐ»Ðž ÑлÑжбÑ. ÐбÑÑМП ÐžÐŒÑ Ð¡ÐŸÐžÑпПлМОÑÐµÐ»Ñ ÐžÑпПлÑзÑеÑÑÑ ÐŽÐ»Ñ ÐžÐœÐŽÐžÐºÐ°ÑОО ПбÑекÑа.
+
+
+
+ Otros Colaboradores
+ Una persona u organizacion que haya tenido una contribución intelectual significativa en la creación del recurso pero cuyas contribuciones son secundarias en comparación a las de las personas u organizaciones especificadas en el elementeo Creator (por ejemplo, editor, ilustrador y traductor).
+
+
+
+ اÙÙ
+ساÙÙ
+ اÙاخر
+ Ù٠اÙ؎خص ا٠اÙÙ
+؀سسة اÙغÙر Ù
+Ø°ÙÙر صراØØ© Ù٠عاÙ
+Ù " اÙÙ
+ؚدع " ٠اÙØ°Ù ÙدÙ
+ Ù
+ساÙÙ
+ات ÙÙرÙØ© ÙاÙ
+Ø© ÙÙÙ
+صدر, ÙÙÙ Ù
+ساÙÙ
+تÙتؚÙ٠ثاÙÙÙØ© Ù
+ÙارÙØ© Ù
+ع اÙ؎خص أ٠اÙÙ
+؀سسة اÙÙ
+Ø°ÙÙرة Ùصا Ù٠عاÙ
+Ù " اÙÙ
+ÙØŽØŠ " Ù
+Ø«Ùا٠Ù
+صØØ, اÙÙ
+ترجÙ
+, ا٠اÙÙ
+Ùسر
+
+
+
+ å
+¶ä»èŽ£ä»»è
+
+ 对èµæºçå
+容äœåºèŽ¡ç®çå
+¶ä»å®äœã
+ å
+¶ä»èŽ£ä»»è
+çå®äŸå¯å
+æ¬äžªäººãç»ç»ææ项æå¡ãäžè¬èèšïŒçšå
+¶ä»èŽ£ä»»è
+çååæ¥æ è¯è¿äžæ¡ç®ã
+
+
+
+ PÅispÄvatel
+ Entita, která pÅispÄla k vytvoÅenà obsahu zdroje.
+ PÅÃklady PÅispÄvatele zahrnujà osobu, organizaci nebo sluÅŸbu. K oznaÄenà entity se typicky pouÅŸÃvá jméno pÅispÄvatele.
+
+
+
+ Andere medewerkers
+ Een persoon of organisatie die een belangrijke bijdrage heeft geleverd, maar die secondair is aan de persoon of organisatie die bij "Creator" genoemd wordt. Gedacht kan worden aan editors, vertalers en illustrators.
+
+
+
+
+
+
+
+
+
+ Contribuente
+ Un entitate responsabile pro facer contributiones al contento del ressource.
+ Exemplos de contribuente include un persona, un organization, o un servicio. Typicamente se utiliza un nomine de contribuente pro indicar le entitate.
+
+
+
+ à€žà€¹à€¯à¥à€à€, à€žà€¹à€¯à¥à€à¥, à€žà€¹à€Ÿà€¯à¥à€¯à€
+ à€®à€Ÿà€¹à€¿à€€à¥à€žà€Ÿà€ à€Ÿ à€žà€à€à€²à¥à€€ à€à€°à€£à¥à¥à€Ÿà€ž à€®à€Šà€€ à€à€°à€£à€Ÿà€°à¥ à€µà¥à€¯à€à¥à€€à¥
+ à€à€Šà€Ÿ.à€ à€µà¥à€¯à€à¥à€€à¥, à€žà¥à€µà€Ÿ, à€žà€à€žà¥à€¥à€Ÿ
+
+
+
+ பà®à®à¯ à®à¯à®à¯à®€à¯à®€à®µà®°à¯
+ வள஀à¯à®€à®¿à®©à¯ à®à®³à¯à®³à®à®à¯à®à®€à¯à®€à®¿à®²à¯ பà®à®à¯ à®à¯à®à¯à®€à¯à®€à®°à¯à®à¯à®à¯ பà¯à®±à¯à®ªà¯à®ªà¯à®³à¯à®³ à®à®°à¯ பà¯à®°à¯à®³à¯.
+ à®à®€à®Ÿà®à®°à®£à®®à¯: à®à®°à¯ பà®à®à¯ à®à¯à®à¯à®€à¯à®€à®µà®°à¯ à®à®©à¯à®±à®Ÿà®²à¯ à®à®°à¯ சபரà¯, à®à®°à¯ à®à¯à®Žà¯, à®
+லà¯à®²à¯à®€à¯ à®à®°à¯ à®à¯à®µà¯. à®
+சà¯à®€ பà¯à®°à¯à®³à¯ à®à¯à®±à®¿à®ªà¯à®ªà®¿à® பà®à®à¯ à®à¯à®à¯à®€à¯à®€à®µà®°à¯ பà¯à®¯à®°à¯ à®à®ªà®¯à¯à®à®ªà®à¯à®€à¯à®€à®µà¯à®®à¯.
+
+
+
+ Äá»ng tác giả
+ Pháp nhân tham gia Äóng góp và o viá»c tạo ra ná»i dung của nguá»n tin
+ Pháp nhân trong Contributor có thá» là tác giả cá nhân hoặc cÆ¡ quan, tá» chức, dá»ch vụ (là tác giả táºp thá») có vai trò quan trá»ng, song là vai trò thứ yếu trong viá»c tạo ra ná»i dung. Những pháp nhân nà y khÃŽng Äược lá»±a chá»n ÄÆ°a và o yếu tá» Creator (tác giả)
+
+
+ 1.1
+ Dublin Core Metadata Initiative
+ Optional
+ Character String
+ Unlimited
+
+
+
+
+ Date
+ A date associated with an event in the life cycle of the resource.
+ Typically, Date will be associated with the creation or availability of the resource. Recommended best practice for encoding the date value is defined in a profile of ISO 8601 and follows the YYYY-MM-DD format.
+
+
+
+ Ra
+ He ra e whai panga ana ki te huringa ora o te rauemi.
+ Ko te tikanga, ka whai panga te ra ki te hanganga, te wateatanga ranei, o te rauemi. Ko te huarahi tino pai hei tohu i te uara o te ra (date value) kua whakaritea i roto i te whakaritenga IS0 8601 [W3CDTF], a, e whai atu ana ki te whakatakotoranga YYYY-MM-DD.
+
+
+
+ Date
+ Une date associée avec un événement dans le cycle de vie de la ressource.
+ Typiquement, une date sera associée à la création ou à la publication d'une ressource. Il est fortement recommandé d'encoder la valeur de la date en utilisant le format défini par l'ISO 8601 [W3CDTF] sous la forme AAAA-MM-JJ.
+
+
+
+ ÐаÑа
+ ÐаÑа, ÑвÑÐ·Ð°ÐœÐœÐ°Ñ Ñ ÑПбÑÑОеЌ в жОзМеММПЌ ÑОкле ÑеÑÑÑÑа.
+ ÐбÑÑМП ÐаÑа аÑÑПÑООÑÑеÑÑÑ Ñ ÑПзЎаМОеЌ ОлО ЎПÑÑÑпМПÑÑÑÑ ÑеÑÑÑÑа. Ðа пÑакÑОке ÑекПЌеМЎÑеÑÑÑ ÐŽÐ»Ñ ÐºÐŸÐŽÐžÑПвкО зМаÑÐµÐœÐžÑ ÐŽÐ°ÑÑ ÐžÑпПлÑзПваÑÑ ÐŸÐ¿ÑеЎелеМОе пÑПÑÐžÐ»Ñ ISO 8601 (ЀПÑЌаÑÑ ÐŽÐ°ÑÑ Ðž вÑеЌеМО W3C), кПÑПÑПе пПЎЎеÑÐ¶ÐžÐ²Ð°ÐµÑ ÑПÑÐŒÐ°Ñ ÐÐÐÐ-ÐÐ-ÐÐ.
+
+
+
+ Fecha
+ Una fecha en la que el recurso se puso a disposición del usuario en su forma actual. Esta fecha no ha de confundirse con la que pertenece al elemento Coverage, que serÃa asociada con el recurso sólo en la medida en que el contenido intelectual está de algún modo relacionado con esa fecha. Recomendamos la utiliazación de uno de los formatos definidos en el documento "Date and Time Formats", http://www.w3.org/TR/NOTE-datetime basado en la norma ISO 8601 que incluye, entre otras, fechas en el formato AAAA y AAAA-MM-DD. De esta forma la fecha 1994-11-05 corresponderÃa al 5 de Noviembre de 1994.
+
+
+
+ اÙتارخ
+ Ù٠اÙتارÙØ® اÙÙ
+تعÙÙ ØšÙÙت ÙØŽØŠ أ٠تÙÙر اÙÙ
+صدر . Ù Ùجؚ Ø£Ù Ùا ÙØ®ÙØ· Ùذا اÙتارÙØ® اÙعا؊د ÙعاÙ
+٠اÙتغطÙØ© , ٠اÙØ° Ù Ùجؚ Ø£Ù ÙÙØ٠ؚاÙÙ
+صدر ÙÙØ· Ù
+Ù ÙاØÙØ© اÙÙ
+ØتÙÙاÙÙÙر٠ÙÙÙÙÙ ÙÙعا Ù
+ا ÙÙ Ùذا اÙتارÙØ®. اÙصÙغة اÙÙ
+سثØسÙØ© ÙÙاØس٠اÙÙ
+تعار٠عÙÙ٠عÙد اÙتطؚÙÙ Ù٠اÙصÙغة اÙÙ
+عتÙ
+دة Ù٠ت؎ÙÙÙ (ISO 8601) صÙغة تارÙØ® اÙÙÙÙ
+ ٠اÙÙÙت ) اعتÙ
+ادا عÙÙ (ISO 8601) اÙÙ
+ÙاØ؞ة اÙÙÙÙØ© http://www.w3.org/TR/NOTE-datetime, W3C. ÙÙÙ Ùذا اÙÙس٠, Ù
+Ø«Ùا, تارÙØ® اÙÙÙÙ
+ 1994-11-04 ÙÙا؞ر ÙÙÙ
+ 5 ÙÙÙÙ
+ؚر 1994
+
+
+
+ æ¥æ
+ äžèµæºçåœåšæäžçäžäžªäºä»¶çžå
+³çæ¶éŽã
+ äžè¬èèšïŒæ¥æåºäžèµæºçå建æåºçæ¥æçžå
+³ã建议éçšçæ¥ææ ŒåŒåºç¬ŠåISO 8601 [W3CDTF]è§ èïŒå¹¶äœ¿çšYYYY-MM-DDçæ ŒåŒã
+
+
+
+ Datum
+ Datum spojené s urÄitou událostà bÄhem existence zdroje.
+ Datum bude typicky spojeno s vytvoÅenÃm nebo zpÅÃstupnÄnÃm zdroje. DoporuÄenÃœ postup pro kódovánà hodnoty data je definován v ISO 8601 [W3CDTF]: formát RRRR-MM-DD.
+
+
+
+ Datum
+ De datum van de totstandkoming of beschikbaarstelling van een Internetbron. Deze datum moet niet verward worden met de datum in "Coverage". De datum in "Coverage" geeft de tijdsperiode van de inhoud van de Internetbron aan. Voorgeschreven wordt de ISO 8601 standaard voor datum, zoals beschreven in W3C Technical Note http://www.w3.org/TR/NOTE-datetime. Hierin wordt het formaat YYYY-MM-DD beschreven. Het formaat YYYY-MM-DD wordt de voorgeschreven standaard. 3 September 1998 wordt in dit geval 1998-09-03.
+
+
+
+
+
+
+
+
+
+ Data
+ Un data associate a un evento in le cyclo vital del ressource.
+ Typicamente le data es associate al creation o disponibilization del ressource. Le practica recommendate pro codificar le valor del datas es definite in un profilo de ISO 8601 [W3CDTF] e seque le formato AAAA-MM-DD.
+
+
+
+ à€€à€Ÿà€°à¥à€, à€Šà€¿à€šà€Ÿà€à€
+ à€®à€Ÿà€¹à€¿à€€à¥à€žà€Ÿà€ à€Ÿ à€€à€¯à€Ÿà€° à€à¥à€²à¥à€¯à€Ÿà€à¥ à€€à€Ÿà€°à¥à€
+ à€€à€Ÿà€°à¥à€ à€²à€¿à€¹à¥à€£à¥à€¯à€Ÿà€à¥ à€žà¥à€µà€°à¥à€ª à€ à€µà€°à¥à€·. à€®à€¹à€¿à€šà€Ÿ. à€Šà€¿à€µà€ž १९५ॊ. ॊ४. ॊ४
+
+
+
+ ஀à¯à®€à®¿
+ வள஀à¯à®€à®¿à®©à¯ à®à®¯à¯à®³à¯ à®à¯à®Žà®±à¯à®à®¿à®¯à®¿à®²à¯ à®à¯à®°à¯à®šà¯à®€ à®à®°à¯ சிà®à®Žà¯à®µà®¿à®©à¯ ஀à¯à®€à®¿.
+ à®à®€à®Ÿà®à®°à®£à®®à¯: à®à®°à¯ வள஀à¯à®€à¯ à®à®£à¯à®à®Ÿà®à¯à®à®ªà¯à®ªà®à¯à® à®
+லà¯à®²à®€à¯ à®à®¿à®à¯à®à¯à®à®à¯à®à¯à®à®¿à®¯ ஀à¯à®€à®¿. ஀à¯à®€à®¿à®¯à®¿à®©à¯ ம஀ிபà¯à®ªà¯ à®à¯à®±à®¿à®¯à¯à®à¯ à®à®à¯à®à¯à®µà®€à®°à¯à®à¯à®à¯ ISO 8601 ல௠விவரிà®à¯à®à®ªà¯à®ªà®à¯à®à¯ YYYY-MM-DD வà®à®¿à®µà®®à¯ à®à¯à®£à¯à®à®€à¯ சடà®à¯à®à®³à¯ à®®à¯à®²à¯à®€à®°à®®à¯ à®à¯à®¯à®²à®Ÿà® à®à®¿à®ªà®Ÿà®°à®à¯ à®à¯à®¯à¯à®à®¿à®°à¯à®®à¯.
+
+
+
+ Thá»i gian
+ Thá»i gian liên quan Äến vòng Äá»i của nguá»n tin (tạo láºp, sá»a Äá»i, v.v..)
+ Ngà y tháng có thá» là thá»i gian liên quan Äến viá»c tạo ra, hiá»u ÄÃnh hoặc là m cho nguá»n tin tiếp cáºn Äược. Khuyến nghá» sá» dụng cách trình bà y thá»i gian theo tiêu chuẩn ISO 8601 và theo khá» mẫu Bá»n sá» nÄm-hai sá» tháng-hai sá» ngà y (YYYY-MM-DD)
+
+
+ 1.1
+ Dublin Core Metadata Initiative
+ Optional
+ Character String
+ Unlimited
+
+
+
+
+ Resource Type
+ The nature or genre of the content of the resource.
+ Type includes terms describing general categories, functions, genres, or aggregation levels for content. Recommended best practice is to select a value from a controlled vocabulary (for example, the working draft list of Dublin Core Types). To describe the physical or digital manifestation of the resource, use the FORMAT element.
+
+
+
+ Tumomo
+ Te ahua, te tu-ahuatanga ranei o nga kaupapa o te rauemi.
+ Kei roto i te Tumomo nga kupu whakaatu i nga wehewehenga whanui, nga aheinga, nga tu-ahuatanga, te whakaritenga ranei o nga taumata o te/ nga kaupapa. Ko te huarahi tino pai kua tohua, ko te tipako i tetahi uara mai i nga kupu kua whakaritea (hei tauira, ko te tauira rarangi e whakamahia ana o nga Dublin Core Types [DCT1]. Hei whakaatu i te whakatinanatanga o te rauemi, whakamahia ko te huanga WHAKATAKOTORANGA (FORMAT).
+
+
+
+ Type
+ La nature ou le genre du contenu de la ressource.
+ Type inclut des termes décrivant des catégories, fonctions ou genres généraux pour le contenu, ou des niveaux d'agrégation. Il est recommandé de choisir la valeur du type dans une liste de vocabulaire contrÎlé (par exemple, la liste provisoire de Types du Dublin Core[DCT1]). Pour décrire la matérialisation physique ou digitale de la ressource, il faut utiliser l'élément Format.
+
+
+
+ ТОп ÑеÑÑÑÑа
+ ÐÑОÑПЎа ОлО Ð¶Ð°ÐœÑ ÑПЎеÑÐ¶Ð°ÐœÐžÑ ÑеÑÑÑÑа.
+ ТОп вклÑÑÐ°ÐµÑ ÑеÑЌОМÑ, ПпОÑÑваÑÑОе ПбÑОе каÑегПÑОО, ÑÑМкÑОО, жаМÑÑ ÐžÐ»Ðž ПбÑеЎОМеММÑе ÑÑПвМО ÑПЎеÑжаМОÑ. ÐÐ»Ñ Ð¿ÑакÑОÑеÑкПгП ОÑпПлÑÐ·ÐŸÐ²Ð°ÐœÐžÑ ÑекПЌеМЎÑеÑÑÑ Ð²ÑбОÑаÑÑ Ð·ÐœÐ°ÑеМОе Оз кПМÑÑПлОÑÑеЌПгП ÑлПваÑÑ (МапÑОЌеÑ, ÑабПÑегП пÑПекÑа ÑпОÑка ТОпПв Dublin Core DCT1). ÐÐ»Ñ ÐŸÐ¿ÐžÑÐ°ÐœÐžÑ ÑОзОÑеÑ-кПгП ОлО ÑОÑÑПвПгП пÑеЎÑÑÐ°Ð²Ð»ÐµÐœÐžÑ ÑеÑÑÑÑа ОÑпПлÑзÑеÑÑÑ ÑÐ»ÐµÐŒÐµÐœÑ Ð€ÐŸÑЌаÑ.
+
+
+
+ Tipo del Recurso
+ La categorÃa del recurso, por ejemplo página personal, romance, poema, minuta, diccionario. Para asegurar la interoperabilidad, Type deberÃa ser seleccionado de entre una lista de valores que actualmente se encuentra bajo desarrollo en un grupo de trabajo. En http://sunsite.berkeley.edu/Metadata/types.html se puede consultar el estado actual de la discusión en torno a este tema.
+
+
+
+ ÙÙع اÙÙ
+صدر
+ ÙÙ Ù؊ة اÙÙ
+صدر , Ù
+Ø«Ùا اÙصÙØØ© اÙاÙ
+, رÙاÙØ© , Ùطعة ؎عرÙØ© , ÙرÙØ© عÙ
+Ù , تÙرÙر ÙÙÙ , Ù
+Ùا٠, ÙاÙ
+Ùس . Ù Ù
+٠أج٠اÙتعاÙ
+٠اÙÙ
+؎تر٠Ùجؚ Ø£Ù Ùختار اÙÙÙع Ù
+٠اÙÙا؊Ù
+Ø© اÙÙ
+رÙÙ
+Ø© ÙاÙت٠ÙÙÙ
+ اعدادÙا ØاÙÙا ضÙ
+Ù ØÙÙات Ùر؎ة عÙ
+Ù
+
+
+
+ èµæºç±»å
+ èµæºå
+容çç¹åŸæç±»åã
+ èµæºç±»åå
+æ¬æè¿°èµæºå
+容çäžè¬èçŽïŒåèœïŒç§å±ïŒæèç±»å±æ¬¡çæ¯è¯ã建议éçšæ¥èªäºåæ§è¯è¡š äžçåŒïŒäŸåŠDCMIç±»åè¯æ±è¡š[DCMITYPE]ïŒãèŠæè¿°èµæºçç©çææ°ååè¡šç°åœ¢åŒïŒè¯·äœ¿çšâæ ŒåŒïŒFORMATïŒâå
+çŽ ã
+
+
+
+ Typ zdroje
+ Povaha nebo druh obsahu zdroje.
+ Typ obsahuje termÃny popisujÃcà obecné kategorie, funkce, druhy nebo agregaÄnà úrovnÄ obsahu. DoporuÄuje se vybÃrat hodnotu z ÅÃzeného slovnÃku (napÅ. pracovnà návrh seznamu Typů Dublin Core [DCT1]). K popisu fyzické nebo digitálnà reprezentace zdroje uÅŸijte prvek Formát.
+
+
+
+ Bestands type
+ Het soort Internetbron, bijvoorbeeld home page, gedicht, working paper, technical report, essay, woordenboek etc. De DC working groups zijn momenteel bezig met twee voorstellen; een minimalist draft: http://sunsite.berkeley.edu/Metadata/minimalist.html en een structuralist draft: http://sunsite.berkely.edu/Metadata/structuralist.html. Het wordt sterk aanbevolen om "Type" van deze lijsten te selecteren.
+
+
+
+
+
+
+
+
+
+ Typo del ressource
+ Le natura o genere del contento del ressource.
+ Le typo del ressource include terminos que describe categorias general, functiones, generes, o nivellos de aggregation pro le contento. Le practica recommendate es selectionar un valor a partir de un vocabulario controlate (per exemplo, le lista de schizzos de travalio de typos de Dublin Core [DCT1]). Pro describer le manifestation physic o digital del ressource, utiliza le elemento Formato.
+
+
+
+ à€ªà¥à€°à€à€Ÿà€°
+ à€®à€Ÿà€¹à€¿à€€à¥à€žà€Ÿà€ à¥à€¯à€Ÿà€à€Ÿà€ªà¥à€°à€à€Ÿà€°
+ à€®à€Ÿà€¹à€¿à€€à¥à€žà€Ÿà€ à¥à€¯à€Ÿà€à¥ à€µà€°à¥à€à¥à€à€°à€£, à€µà€°à¥à€à€µà€Ÿà€°à¥à€®à€§à¥à€¯à¥ à€à€à€Ÿà€Šà¥à€¯à€Ÿ à€šà¥à€à€Šà¥à€à€Ÿ à€®à¥à€à¥à€¯ à€à€à€ªà¥à€°à€à€Ÿà€°
+
+
+
+ வளம௠வà®à¯
+ வள஀à¯à®€à®¿à®©à¯ à®à®³à¯à®³à®à®à¯à®à®€à¯à®€à®¿à®©à¯ படனà¯à®®à¯ à®
+லà¯à®²à®€à¯ ஀ரமà¯.
+ வà®à¯ à®à®©à¯à®°à®Ÿà®²à¯ பà¯à®€à¯ பிரிவினà¯à®à®³à¯, à®à¯à®¯à®²à¯à®à®³à¯, ஀ரà®à¯à®à®³à¯, à®
+லà¯à®²à®€à¯ à®à®³à¯à®³à®à®à¯à®à®€à¯à®€à®¿à®©à¯ ஀ிரà®à¯à®à¯ சிலà¯à®à®³à¯ à®à®©à¯à®ªà®µà®¯à®¿à®©à¯ பà¯à®¯à®°à¯à®à®³à¯. à®à®à¯à®à¯à®ªà¯à®ªà®à¯à®€à¯à®€à®¿à®¯ à®à¯à®²à¯ வள஀à¯à®€à®¿à®²à®¿à®°à¯à®šà¯à®€à¯ à®à®°à¯ ம஀ிபà¯à®ªà¯ ஀à¯à®°à¯à®šà¯à®€à¯à®à¯à®ªà¯à®ªà®€à¯ சடà®à¯à®à®³à¯ à®®à¯à®²à¯à®€à®°à®®à¯ à®à¯à®¯à®²à®Ÿà® à®à®¿à®ªà®Ÿà®°à®à¯ à®à¯à®¯à¯à®à®¿à®°à¯à®®à¯. (à®à®€à®Ÿà®à®°à®£à®®à¯: Dublin Core Types (à®à®ªà¯à®³à®¿à®©à¯ à®à¯à®°à¯ à®à¯à®ªà¯à®žà¯)பணி à®à¯à®¯à¯à®µà®€à®°à¯à®à®Ÿà®© வரà¯à®µà¯ பà®à¯à®à®¿à®¯à®²à¯). வள஀à¯à®€à®¿à®©à¯ பரà¯à®šà®¿à®²à¯ à®
+லà¯à®²à®€à¯ à®à®²à®à¯à®à®®à¯à®±à¯ வà¯à®³à®¿à®à®Ÿà®à¯à®à®²à¯ விவரிபà¯à®ªà®€à®°à¯à®à¯ FORMAT (பà®à®¿à®µà®®à¯)à®à®±à¯à®ªà¯à®ªà¯ à®à®ªà®¯à¯à®à®¿à®à¯à®à®µà¯à®®à¯.
+
+
+
+ ThỠloại
+ MÃŽ tả bản chất hoặc thá» loại của ná»i dung của nguá»n tin
+ MÃŽ tả thá» loại của nguá»n tin
+
+
+ 1.1
+ Dublin Core Metadata Initiative
+ Optional
+ Character String
+ Unlimited
+
+
+
+
+ Format
+ The physical or digital manifestation of the resource.
+ Typically, Format may include the media-type or dimensions of the resource. Format may be used to determine the software, hardware or other equipment needed to display or operate the resource. Examples of dimensions include size and duration. Recommended best practice is to select a value from a controlled vocabulary (for example, the list of Internet Media Types [MIME] defining computer media formats).
+
+
+
+ Whakatakotoranga
+ Te whakatinanatanga, te whakaputanga a-mati o te rauemi.
+ Ko te tikanga, ka taea te Whakatakotoranga te whakamahi hei whakarite i te rawa-ngohe (software), te rawa-maro (hardware), ma etahi taputapu ranei me matua whiwhi, hei whakahaere i te rauemi. Ko te rahi me te roanga etahi tauira hanga. Ko te tino huarahi kua tohua ko te tipako uara mai i tetahi whakaritenga kupu (hei tauira, te rarangi o nga Tumomo Papaho Ipurangi (Internet Media Types [MIME]) e whakaatu ana i nga whakatakotoranga papaho rorohiko.
+
+
+
+ Format
+ La matérialisation physique ou digitale de la ressource.
+ Typiquement, Format peut inclure le media ou les dimensions de la ressource. Format peut être utilisé pour préciser le logiciel, le matériel ou autre équipement nécessaire pour afficher ou faire fonctionner la ressource. Exemples de dimensions incluent la taille et la durée. Il est recommandé de choisir la valeur du format dans une liste de vocabulaire contrÎlé(par exemple, la liste des types de media définis sur Internet [MIME]).
+
+
+
+ ЀПÑЌаÑ
+ ЀОзОÑеÑкПе ОлО ÑОÑÑПвПе пÑеЎÑÑавлеМОе ÑеÑÑÑÑа.
+ ÐбÑÑМП ЀПÑÐŒÐ°Ñ ÐŒÐŸÐ¶ÐµÑ Ð²ÐºÐ»ÑÑаÑÑ ÑОп аÑЎОПвОзÑалÑМПй ОМÑПÑЌаÑОО (ЌеЎОа-ÑОп) ОлО велОÑÐžÐœÑ ÑеÑÑÑÑа. ЀПÑÐŒÐ°Ñ ÐŒÐŸÐ¶ÐµÑ ÐžÑпПлÑзПваÑÑÑÑ ÐŽÐ»Ñ ÐŸÐ¿ÑÐµÐŽÐµÐ»ÐµÐœÐžÑ Ð°Ð¿Ð¿Ð°ÑаÑМПгП, пÑПгÑаЌЌМПгП ПбеÑпеÑÐµÐœÐžÑ ÐžÐ»Ðž ÐŽÑÑгПгП ПбПÑÑЎПваМОÑ, МеПбÑ
+ПЎОЌПгП ÐŽÐ»Ñ Ð²ÐŸÑпÑÐŸÐžÐ·Ð²ÐµÐŽÐµÐœÐžÑ ÐžÐ»Ðž ÑабПÑÑ Ñ ÑеÑÑÑÑПЌ. ÐÑОЌеÑÑ Ð²ÐµÐ»ÐžÑÐžÐœÑ Ð²ÐºÐ»ÑÑаÑÑ ÑÐ°Ð·ÐŒÐµÑ Ðž пÑПЎПлжОÑелÑМПÑÑÑ. ÐÐ»Ñ Ð¿ÑакÑОÑеÑкПгП ОÑпПлÑÐ·ÐŸÐ²Ð°ÐœÐžÑ ÑекПЌеМЎÑеÑÑÑ Ð²ÑбОÑаÑÑ Ð·ÐœÐ°ÑеМОе Оз кПМÑÑПлОÑÑеЌПгП ÑлПваÑÑ (МапÑОЌеÑ, ÑпОÑка ÐеЎОа-ÑОпПв ÐÐœÑеÑÐœÐµÑ MIME, ПпÑеЎелÑÑÑегП кПЌпÑÑÑеÑÐœÑе ÑПÑЌаÑÑ Ð°ÑЎОПвОзÑалÑМПй ОМÑПÑЌаÑОО).
+
+
+
+ Formato
+ El formato de datos de un recurso, usado para identificar el software y posiblemente, el hardware que se necesitarÃa para mostrar el recurso. Para asegurar la interoperabilidad, los valores de Format deberÃan ser seleccionados de entre una lista de valores que actualmente se encuentra bajo desarrollo en un grupo de trabajo.
+
+
+
+ اÙصÙغة
+ Ùذ٠صÙغة اÙÙ
+عÙÙÙ
+Ø© اÙخاصة ؚاÙÙ
+صدر , ٠تستخدÙ
+ ÙÙتعرÙ٠ؚاÙؚرÙ
+جÙات ÙرؚÙ
+ا اÙصÙØš ÙÙØاسÙØš ٠اÙت٠ÙÙ
+Ù٠أ٠ÙØتاج ÙÙا Ùعرض أ٠ت؎غÙ٠اÙÙ
+صدر . Ù
+٠أج٠اÙتعاÙ
+٠اÙÙ
+؎ترÙ, Ùجؚ أ٠تختار اÙصÙغة Ù
+٠اÙÙا؊Ù
+Ø© اÙÙ
+رÙÙ
+Ø© ٠اÙت٠ÙتÙ
+ اعدادÙا ØاÙÙا ضÙ
+Ù ØÙÙات Ùر؎ة عÙ
+Ù
+
+
+
+ æ ŒåŒ
+ èµæºçç©çææ°åè¡šç°åœ¢åŒã
+ äžè¬èèšïŒæ ŒåŒå¯èœå
+æ¬èµæºçåªäœç±»åæèµæºç倧å°ïŒæ ŒåŒå
+çŽ å¯ä»¥çšæ¥å³å®å±ç€ºææäœèµæºæé ç蜯硬件æå
+¶ä»çžåºè®Ÿå€ïŒäŸåŠå€§å°å
+æ¬èµæºæå çååšç©ºéŽåæç»æ¶éŽã建议éçšæ¥èªäºåæ§è¯è¡š äžçåŒïŒïŒäŸåŠInternetåªäœç±»å[MIME]å®ä¹è®¡ç®æºåªäœæ ŒåŒïŒã
+
+
+
+ Formát
+ Fyzická nebo digitálnà reprezentace zdroje.
+ Typicky můşe Formát obsahovat typ média nebo rozmÄry zdroje. Formát lze pouÅŸÃvat k urÄenà softwaru, hardwaru nebo dalÅ¡Ãho zaÅÃzenà potÅebného k zobrazenà nebo k manipulaci se zdrojem. PÅÃklady rozmÄrů zahrnujà velikost a dobu trvánÃ. DoporuÄuje se vybÃrat hodnotu z ÅÃzeného slovnÃku (napÅ. seznam typů internetovÃœch médià [MIME] definujÃcà formáty poÄÃtaÄovÃœch médiÃ).
+
+
+
+ Format
+ Het data formaat van het Internetbestand. Dit gegeven kan gebruikt worden om systeemvereisten (hard- en software) te identificeren die nodig zijn voor raadpleging of bediening van de Internetbron. "Format" is nog in ontwikkeling bij de DC workshop. Uit compatibiliteitsoverwegingen wordt aanbevolen formaatgegevens te selecteren uit een gecontroleerde lijst. Formaten kunnen van de Internet Media Types (MIME types) lijst gekozen worden: http://www.isi.edu/in-notes/iana/assignments/media-types/media-types
+
+
+
+
+
+
+
+
+
+ Formato
+ Le manifestation physic o digital del ressource.
+ Typicamente le formato pote includer le typo de medio o dimensiones del ressource. Le formato pote esser utilizate pro determinar le software o le equipamento necessari pro exhibir o operar le ressource. Exemplos de dimensiones include grandessa e duration. Le practica recommendate es selectionar un valor de un vocabulario controlate (per exemplo, le lista de typos de medios de Internet [MIME] que defini formatos de medios).
+
+
+
+ à€°à€à€šà€Ÿ
+ à€®à€Ÿà€¹à€¿à€€à¥à€žà€Ÿà€ à¥à€¯à€Ÿà€à¥ à€°à€à€šà€Ÿ, à€šà€®à¥à€šà€Ÿà€¬à¥à€Š à€°à€à€šà€Ÿ
+ à€®à€Ÿà€¹à€¿à€€à¥à€žà€Ÿà€ à¥à€¯à€Ÿà€à¥ à€žà¥à€µà€°à¥à€ª, à€°à€à€šà€Ÿà€à€Šà€Ÿ. à€€à¥à€¯à€Ÿà€à¥ à€°à¥à€ª à€à€žà¥ à€ªà¥à€žà¥à€€à€à€°à¥à€ª, à€žà€à€à€£à€à¥à€¯ à€°à¥à€ª, à€µà€¿à€Šà¥à€¯à¥à€€ à€ªà€°à€®à€Ÿà€£à¥à€à€à¥à€¯à€Ÿ à€žà€¹à€Ÿà€¯à¥à€¯à€Ÿà€šà¥ à€žà€à€à€£à€à¥à€à¥à€€ à€®à€Ÿà€¹à€¿à€€à¥à€žà€Ÿà€ à€Ÿ
+
+
+
+ வà®à®¿à®µà®®à¯
+ வள஀à¯à®€à®¿à®©à¯ பரà¯à®šà®¿à®²à¯ à®
+லà¯à®²à®€à¯ à®à®²à®à¯à®à®®à¯à®±à¯ வà¯à®³à®¿à®à®Ÿà®à¯à®à®²à¯
+ à®à®€à®Ÿà®à®°à®£à®®à¯: à®à®à®à®à¯à®à®³à¯ வà®à¯ à®
+லà¯à®²à®€à¯ வள஀à¯à®€à®¿à®©à¯ படமடணமà¯à®à®³à¯ வà®à®¿à®µà®€à¯à®€à®¿à®²à¯ à®à®°à¯à®à¯à®à¯à®®à¯. வள஀à¯à®€à¯ à®à®¯à®à¯à®à¯à®µà®€à®°à¯à®à¯à®à¯ à®
+லà¯à®²à®€à¯ à®à®Ÿà®à¯à®à¯à®µà®€à®à¯à®à¯ வà¯à®£à¯à®à®¿à®¯ à®®à¯à®©à¯à®ªà¯à®°à¯à®³à¯, வனà¯à®ªà¯à®°à¯à®³à¯ à®
+லà¯à®²à®€à¯ வà¯à®°à¯ à®à®°à¯à®µà®¿à®à®³à¯ ஀à¯à®°à¯à®®à®Ÿà®©à®¿à®ªà®€à®°à¯à®à¯à®à¯ வà®à®¿à®µà®®à¯ à®à®ªà®¯à¯à®à®¿à®à¯à®à®²à®Ÿà®®à¯. பரà¯à®®à®Ÿà®£à®€à¯à®€à®¿à®²à¯ à®
+ளவ௠à®
+லà¯à®²à®€à¯ சà¯à®à®¿à®à¯à®à¯à®®à¯ à®à®Ÿà®²à®®à¯ à®à®³à¯à®ªà¯à®ªà®à¯à®®à¯. à®à®°à¯ à®à®à¯à®à¯à®ªà¯à®ªà®à¯à® à®à¯à®²à¯ வள஀à¯à®€à®¿à®²à®¿à®°à¯à®šà¯à®€à¯ (à®à®€à®Ÿà®à®°à®£à®®à¯: Internet Media Types [MIME] பà®à¯à®à®¿à®¯à®²à¯ à®à®£à®¿à®ªà¯à®ªà¯à®±à®¿ à®à®à®à®à¯à®à®³à¯ வà®à®¿à®µà®à¯à®à®³à¯ விவரி஀à¯à®€à®¿à®°à¯à®à¯à®à¯à®®à¯)à®à®°à¯ ம஀ிபà¯à®ªà¯ ஀ிரசà¯à®€à¯à®à¯à®ªà¯à®ªà®€à¯ சடà®à¯à®à®³à¯ à®à®¿à®ªà®Ÿà®°à®à¯ à®à¯à®¯à¯à®¯à¯à®®à¯ à®®à¯à®²à¯à®€à®°à®®à¯ à®à¯à®¯à®²à¯.
+
+
+
+ Dạng mẫu dữ liá»u
+ MÃŽ tả loại hình váºt lÃœ hoặc sá» (Äiá»n tá») của nguá»n tin.
+ Vá» cÆ¡ bản, Yếu tá» Format cung cấp thÃŽng tin vá» váºt mang tin của nguá»n tin nếu là nguá»n tin khÃŽng trá»±c tuyến. Yếu tá» còn cung cấp thÃŽng tin vá» kiá»u dữ liá»u hoặc kÃch thÆ°á»c, quy mÃŽ của nguá»n tin. Dạng mẫu có thá» sá» dụng Äá» xác Äá»nh phần má»m, phần cứng hoặc thiết bá» khác cần thiết Äá» hiá»n thá» hoặc thao tác vá»i nguá»n tin. Khuyến nghá» sá» dụng từ vá»±ng có kiá»m soát Äá» chá»n lá»±a thuáºt ngữ phù hợp (thà dụ sá» dụng danh mục từ chuẩn tên gá»i loại hình dữ liá»u Internet (MIME) Äá» xác Äá»nh dạng mẫu dữ liá»u Äiá»n tá»)
+
+
+ 1.1
+ Dublin Core Metadata Initiative
+ Optional
+ Character String
+ Unlimited
+
+
+
+
+ Resource Identifier
+ An unambiguous reference to the resource within a given context.
+ Recommended best practice is to identify the resource by means of a string or number conforming to a formal identification system. Example formal identification systems include the Uniform Resource Identifier (URI) (including the Uniform Resource Locator (URL)), the Digital Object Identifier (DOI) and the International Standard Book Number (ISBN).
+
+
+
+ Taututanga
+ He tohutoro e hangai ana ki te rauemi i roto i tetahi horopaki.
+ Ko te tino huarahi kua tohua, ko te tautu i te rauemi ma tetahi aho (string), tau ranei, e hangai ana ki tetahi punaha taututanga okawa. Ko etahi punaha taututanga okawa ko te Taututanga Rauemi Orite (Uniform Resource Identifier - URI), te Taututanga Rauemi Tohu-wahi (Uniform Resource Locator - URL), Te Mea A-mati (Digital Object Identifier - DOI) me te Tau Pukapuka Aro Whanui o te Ao (International Standard Book Number - ISBN).
+
+
+
+ Identifiant
+ Une référence non ambiguë à la ressource dans un contexte donné
+ Il est recommandé d'identifier la ressource par une chaîne de caractÚre ou un nombre conforme à un sytÚme formel d'identification. Exemples de systemes formels d'identification incluent le "Uniform Resource Identifier" (URI) (qui inclut le "Uniform Resource Locator" (URL)), le "Digital Object Identifier"(DOI) et le "International Standard Book Number"(ISBN).
+
+
+
+ ÐЎеМÑОÑОкаÑÐŸÑ ÑеÑÑÑÑа
+ ÐЎМПзМаÑÐœÐ°Ñ ÑÑÑлка Ма ÑеÑÑÑÑ Ð² пÑеЎелаÑ
+ ЎаММПгП кПМÑекÑÑа.
+ ÐÐ»Ñ Ð¿ÑакÑОÑеÑкПгП ОÑпПлÑÐ·ÐŸÐ²Ð°ÐœÐžÑ ÑекПЌеМЎÑеÑÑÑ ÐžÐŽÐµÐœÑОÑОÑОÑПваÑÑ ÑеÑÑÑÑ Ð¿ÐŸÑÑеЎÑÑвПЌ ÑÑÑПкО ОлО ÑОÑла, ÑППÑвеÑÑÑвÑÑÑегП ÑПÑЌалÑМПй ОЎеМÑОÑОкаÑОПММПй ÑОÑÑеЌе. ÐÑОЌеÑÑ ÑПÑЌалÑÐœÑÑ
+ ОЎеМÑОÑОкаÑОПММÑÑ
+ ÑОÑÑеЌ вклÑÑаÑÑ Ð£ÐœÐžÑОÑОÑПваММÑй ÐЎеМÑОÑОкаÑÐŸÑ Ð ÐµÑÑÑÑа (URI), (вклÑÑÐ°Ñ Ð£ÐœÐžÑОÑОÑПваММÑÑй ÐПкаÑÐŸÑ Ð ÐµÑÑÑÑа URL), ÐЎеМÑОÑОкаÑÐŸÑ ÐŠÐžÑÑПвПгП ÐбÑекÑа (DOI) О ÐежЎÑМаÑПЎМÑй СÑаМЎаÑÑÐœÑй ÐМОжМÑй ÐÐŸÐŒÐµÑ (ISBN).
+
+
+
+ Identificador del Recurso
+ Secuencia de caracteres usados para identificar unÃvocamente un recurso. Ejemplos para recursos en lÃnea pueden ser URLs y URNs (cuando estén implementados). Para otros recursos pueden ser usados otros formatos de identificadores, como por ejemplo ISBN ("International Standard Book Number" - Número Internacional Normalizado para Libros)
+
+
+
+ Ù
+عر٠اÙÙ
+صدر
+ ÙÙ Ù
+جÙ
+Ùعة ØرÙÙØ© أ٠رÙÙ
+ ÙستخدÙ
+ ÙتعرÙ٠اÙÙ
+صدر اØدÙا : اÙاÙ
+Ø«ÙØ© ÙذاÙÙ Ù٠اÙÙ
+صادر اÙØŽØšÙÙةتضÙ
+ ) URNs, URLs عÙد ØšÙا؊Ùا ( ÙØ°ÙÙ ÙÙ
+Ù٠اعتؚار اÙÙ
+عرÙات اÙعاÙÙ
+ÙØ© اÙاØادÙØ© Ù
+ث٠اÙرÙÙ
+ اÙدÙÙÙ ÙتصÙÙ٠اÙÙاتؚ (ISBN) Ù
+ر؎ØØ© ÙÙذا اÙعاÙ
+Ù
+
+
+
+ èµæºæ è¯ç¬Š
+ åšç¹å®çèåŽå
+ç»äºèµæºçäžäžªæç¡®çæ è¯ã
+ 建议对èµæºçæ è¯éçšç¬Šåæäžæ£åŒæ è¯äœç³»çå笊䞲åæ°åç»åãäŸåŠæ£åŒçæ è¯äœç³»å
+æ¬ç»äžèµ æºæ è¯ç¬Š(URI) (å
+æ¬åäžèµæºå®äœç¬ŠURL)ãæ°å对象æ è¯ç¬Š(DOI)ååœé
+æ å乊å·(ISBN)ã
+
+
+
+ Identifikátor zdroje
+ JednoznaÄnÃœ odkaz na zdroj v rámci daného kontextu.
+ DoporuÄuje se identifikovat zdroj znakovÃœm ÅetÄzcem nebo ÄÃslem odpovÃdajÃcÃm nÄkterému z formálnÃch identifikaÄnÃch systémů. PÅÃklady formálnÃch identifikaÄnÃch systémů zahrnujà Uniform Resource Identifier (URI) (vÄetnÄ Uniform Resource Locator (URL)), Digital Object Identifier (DOI) a Mezinárodnà standardnà ÄÃslo knihy (ISBN).
+
+
+
+ Bestandsidentificatie
+ Een unieke string of nummer ter identificatie van de Internetbron. Voorbeelden zijn URL's of URN's Andere voorbeelden zijn International Standard Book Number (ISBN) of International Standard Serial Number (ISSN)
+
+
+
+
+
+
+
+
+
+ Identificator del ressource
+ Un referentia inambigue al ressource intra un date contexto.
+ Se recommenda identificar le ressource per medio de un catena de characteres o numero conforme a un systema formal de identification. Exemplos de systemas formal de identification include le Uniform Resource Identifier (URI) (includente le Uniform Resource Locator (URL)), le Digital Object Identifier (DOI) e le International Standard Book Number (ISBN).
+
+
+
+ à€à€³à€
+ à€®à€Ÿà€¹à€¿à€€à¥à€žà€Ÿà€ à¥à€¯à€Ÿà€à€Ÿ à€à€ à€
+à€°à¥à€¥à¥ à€žà€à€Šà€°à¥à€
+ à€à€Šà€Ÿ. à€®à€Ÿà€¹à€¿à€€à¥à€à€Ÿà€³à¥à€¯à€Ÿà€µà€°à¥à€² à€ªà€€à¥à€€à€Ÿ, à€µà€¿à€¶à€¿à€·à¥à€ à€žà¥à€¥à€³, à€ªà¥à€žà¥à€€à€à€Ÿà€à€Ÿ à€à€à€€à€°à€°à€Ÿà€·à¥à€à¥à€°à¥à€¯ à€®à€Ÿà€šà€ à€à¥à€°à€®à€Ÿà€à€, à€®à€Ÿà€¹à€¿à€€à¥à€žà€Ÿà€ à¥à€¯à€Ÿà€à¥ à€à€³à€ à€ªà€à€µà€¿à€£à€Ÿà€°à€Ÿ à€à€à€à€°à€šà¥à€ à€µà€°à¥à€² à€ªà€€à¥à€€à€Ÿ
+
+
+
+ வளம௠à®à¯à®±à®¿à®ªà¯à®ªà®Ÿà®©à¯
+ à®à®°à¯ à®à¯à®Žà®²à®¿à®²à¯ à®à®°à¯à®à¯à®à¯à®®à¯ வள஀à¯à®€à¯ à®à®°à¯ ஀à¯à®³à®¿à®µà®Ÿà®© à®à¯à®°à®¿à®ªà¯à®ªà¯.
+ à®à®°à¯ à®®à¯à®±à¯à®à®Ÿà®°à¯à®šà¯à®€ à®
+à®à¯à®¯à®Ÿà®³ à®
+à®®à¯à®ªà¯à®ªà¯ à®à®£à®à¯à®à®®à®Ÿà®© à®à®°à¯ à®à®°à®®à¯ à®
+லà¯à®²à®€à¯ à®à®£à¯ à®à®ªà®¯à¯à®à®¿à®€à¯à®€à¯ வள஀à¯à®€à¯ à®
+à®à®¯à®Ÿà®³à®®à¯ à®à¯à®¯à¯à®µà®€à¯ சடà®à¯à®à®³à¯ à®à®¿à®ªà®Ÿà®°à®à¯ à®à¯à®¯à¯à®¯à¯à®®à¯ à®®à¯à®²à¯à®€à®°à®®à¯ à®à¯à®¯à®²à¯. à®à®€à®Ÿà®à®°à®£ à®®à¯à®±à¯à®à®Ÿà®°à¯à®šà¯à®€ à®
+à®à¯à®¯à®Ÿà®³ à®
+à®®à¯à®ªà¯à®ªà¯à®à®³à¯: Uniform Resource Identifier (URI)(Uniform Resource Locator (URL)à®à®³à¯à®ªà¯à®ªà®), the Digital Object Identifier (DOI)à®®à¯à®²à¯à®®à¯ International Standard Book Number (ISBN).
+
+
+
+ Äá»nh danh
+ Má»t tham chiếu khÃŽng trùng lặp Äến nguá»n tin trong khung cảnh cụ thá»
+ Khuyến nghá» sá» dụng các Äá»nh danh nguá»n tin theo những chuẩn Äược chấp nháºn quy Äá»nh cho những há» thá»ng Äá»nh danh hình thức. Thà dụ vá» há» thá»ng Äá»nh danh bao gá»m: Äá»nh danh Nguá»n tin thá»ng nhất (Uniform Resource Identifier hoặc URI, trong Äó có Äá»nh vá» nguá»n tin thá»ng nhất URL - Uniform Resource Locator, Tên nguá»n tin thá»ng nhất URN - Uniform Resource Name và Äá»nh vá» nguá»n tin thá»ng nhất á»n Äá»nh PURL - Persistent URL), Äá»nh danh Äá»i tượng sá» DOI (Digital Object Identifier), Chá» sá» sách chuẩn quá»c tế ISBN (International Standard Book Number),...
+
+
+ 1.1
+ Dublin Core Metadata Initiative
+ Optional
+ Character String
+ Unlimited
+
+
+
+
+ Source
+ A Reference to a resource from which the present resource is derived.
+ The present resource may be derived from the Source resource in whole or in part. Recommended best practice is to reference the resource by means of a string or number conforming to a formal identification system.
+
+
+
+ Matapuna
+ He tohutoro ki tetahi rauemi koira te matapuna o te rauemi e tirohia ana.
+ Tera pea i puta te katoa, tetahi wahanga ranei o te rauemi, e tirohia ana, mai i te Matapuna rauemi. Ko te tino huarahi kua tohua ko te tohutoro ki te rauemi ma te aho, ma te tau ranei e hangai ana ki tetahi punaha taututanga okawa.
+
+
+
+ Source
+ Une référence à une ressource à partir de laquelle la ressource actuelle a été dérivée.
+ La ressource actuelle peut avoir été dérivée d'une autre ressource source, en totalité ou en partie. Il est recommandé de reférencer cette source par une chaîne de caractÚre ou un nombre conforme à un systÚme formel d'identification.
+
+
+
+ ÐÑÑПÑМОк
+ СÑÑлка Ма ÑеÑÑÑÑ, Оз кПÑПÑПгП ОзвлеÑеМ МаÑÑПÑÑОй.
+ ÐаÑÑПÑÑОй ÑеÑÑÑÑ ÐŒÐŸÐ¶ÐµÑ Ð±ÑÑÑ ÐžÐ·Ð²Ð»ÐµÑеМ Оз ÐÑÑПÑМОка ÑелОкПЌ ОлО ÑаÑÑОÑМП. ÐÐ»Ñ Ð¿ÑакÑОÑеÑкПгП ОÑпПлÑÐ·ÐŸÐ²Ð°ÐœÐžÑ ÑекПЌеМЎÑеÑÑÑ ÐžÐŽÐµÐœÑОÑОÑОÑПваÑÑ ÑеÑÑÑÑ Ð¿ÐŸÑÑеЎÑÑвПЌ ÑÑÑПкО ОлО ÑОÑла, ÑППÑвеÑÑÑвÑÑÑегП ÑПÑЌалÑМПй ОЎеМÑОÑОкаÑОПММПй ÑОÑÑеЌе.
+
+
+
+ Fuente
+ Secuencia de caracteres utilizado para identificar unÃvocamente un trabajo a partir del cual proviene el recurso actual. Por ejemplo, es posible usar Source con la fecha de 1603 como descripción de una pelÃcula basada en una obra de Shakespeare, pero es preferible, en ese caso, usar Relation "IsBasedOn" con una referencia a un recurso distinto cuya descripción contenga el elemento Date con valor 1603.
+
+
+
+ اÙÙ
+صدر
+ اÙÙ
+عÙÙÙ
+ات اÙخاصة ØšÙ
+صدر ثاÙ٠٠اÙذ٠استÙ
+د Ù
+Ù٠اÙÙ
+صدر اÙØاÙÙ. Ù
+ع Ø£ÙÙ Ù
+٠اÙÙ
+Ùص٠ؚ٠أ٠تÙدÙ
+ اÙعÙاÙ
+Ù Ù
+عÙÙÙ
+ات ع٠اÙÙ
+صدر اÙØاÙÙ ÙÙØ· , ÙÙÙ
+Ù٠أ٠ÙØÙÙ Ùذا اÙعاÙ
+٠اÙتارÙØ®, اÙÙ
+ÙØŽØŠ , اÙصÙغة , اÙÙ
+عر٠, ا٠اÙØ© Ù
+ÙØ© - Ù
+عÙÙÙ
+ات اخر٠ÙÙÙ
+صدر اÙثاÙ٠عÙدÙ
+ا تعتؚر Ù
+ÙÙ
+Ø© ÙاÙت؎ا٠اÙÙ
+صدر اÙØاÙÙ , Ù ÙذاÙÙ ÙÙص٠عÙد اÙتطؚÙÙÙ٠اØس٠اÙÙ
+تعار٠عÙÙ٠ؚاستخداÙ
+ عاÙ
+٠اÙعÙاÙØ©
+
+
+
+ æ¥æº
+ ç°æèµæºæ¥æºçåç
+§ã
+ åœåèµæºå¯èœéšåæå
+šéšæºèªè¯¥å
+çŽ ææ è¯çèµæºïŒå»ºè®®å¯¹è¿äžèµæºçæ è¯éçšäžäžªç¬Šåæ£åŒæ è¯ç³» ç»çåäž²åæ°åç»å ã
+
+
+
+ Zdroj
+ Odkaz na zdroj, z nÄhoÅŸ je popisovanÃœ zdroj odvozen.
+ PopisovanÃœ zdroj můşe bÃœt zcela nebo zÄásti odvozen ze zdroje uvedeného v prvku Zdroj. DoporuÄuje se odkazovat zdroj znakovÃœm ÅetÄzcem nebo ÄÃslem odpovÃdajÃcÃm nÄkterému z formálnÃch identifikaÄnÃch systémů.
+
+
+
+ Bron
+ Informatie over een tweede bron waar de huidige Internetbron is van afgeleid. Bij "Source" mag een datum, auteur of maker, formaat, identificatie of andere metadata voor de tweede bron worden ingevuld. Voorbeeld: het is mogelijk om een "Source" datum 1603 in een omschrijving van een 1996 film bewerking van een Shakespeare stuk te gebruiken. "Source" is niet bruikbaar wanneer de huidige bron de orginele is.
+
+
+
+
+
+
+
+
+
+ Fonte
+ Un referentia a un ressource del qual se deriva le ressource presente.
+ Le ressource presente pote derivar se del ressource-fonte in toto o in parte. Le practica recommendate es facer referentia al ressource per medio de un catena de characteres o un numero conforme a un systema formal de identification.
+
+
+
+ à€à€à€®
+ à€®à€Ÿà€¹à€¿à€€à¥à€à€Ÿ à€à€à€® à€žà€Ÿà€à€à€£à€Ÿà€°à€Ÿ à€à€à€
+à€°à¥à€¥à¥ à€žà€à€Šà€°à¥à€
+ à€à€Šà€Ÿ. à€ªà¥à€žà¥à€€à€, à€®à€Ÿà€žà€¿à€, à€®à€Ÿà€¹à€¿à€€à¥à€à€Ÿà€³à¥à€¯à€Ÿà€µà€°à¥à€² à€ªà€€à¥à€€à€Ÿà€¯à€Ÿà€à€à€Ÿ à€žà€à€Šà€°à¥à€
+
+
+
+ à®®à¯à®²à®®à¯
+ à®à®šà¯à®€ வள஀à¯à®€à®¿à®²à®¿à®°à¯à®šà¯à®€à¯ சிà®à®Žà¯à®®à¯ வளம௠பà¯à®±à¯à®±à®¿à®°à¯à®à¯à®à®¿à®°à®€à¯ à®
+஀௠à®à¯à®±à®¿à®à¯à®à®¿à®°à®€à¯.
+ சிà®à®Žà¯à®®à¯ வளம௠மà¯à®² வள஀à¯à®€à®¿à®²à®¿à®°à¯à®šà¯à®€à¯ à®à®°à¯ படà®à®®à¯ à®
+லà¯à®²à®€à¯ à®®à¯à®Žà¯à®®à¯à®¯à®à®µà¯ பà¯à®±à®²à®Ÿà®®à¯. à®à®°à¯ à®®à¯à®±à¯à®à®Ÿà®°à¯à®šà¯à®€ à®
+à®à¯à®¯à®Ÿà®³ à®
+à®®à¯à®ªà¯à®ªà¯ à®à®£à®à¯à®à®®à®Ÿà®© à®à®°à¯ à®à®°à®®à¯ à®
+லà¯à®²à®€à¯ à®à®£à¯ à®à®ªà®¯à¯à®à®¿à®€à¯à®€à¯ வள஀௠à®
+à®à®¯à®Ÿà®³à®®à¯ à®à¯à®¯à¯à®µà®€à¯ சடà®à¯à®à®³à¯ à®à®¿à®ªà®Ÿà®°à®à¯ à®à¯à®¯à¯à®¯à¯à®®à¯ à®®à¯à®²à¯à®€à®°à®®à¯ à®à¯à®¯à®²à¯.
+
+
+
+ Nguá»n trÃch
+ Tham chiếu vá» nguá»n gá»c mà từ Äó nguá»n tin hiá»n Äược mÃŽ tả Äược rút ra hoặc tạo ra từ Äó
+
+
+
+ 1.1
+ Dublin Core Metadata Initiative
+ Optional
+ Character String
+ Unlimited
+
+
+
+
+ Language
+ A language of the intellectual content of the resource.
+ Recommended best practice for the values of the Language element is defined by RFC 1766 which includes a two-letter Language Code (taken from the ISO 639 standard, followed optionally, by a two-letter Country Code (taken from the ISO 3166 standard). For example, 'en' for English, 'fr' for French, or 'en-uk' for English used in the United Kingdom.
+
+
+
+ Reo
+ Te reo o te whakakaupapatanga o nga matauranga o te rauemi.
+ Ko te tino huarahi kua tohua mo nga uara o te huanga Reo kua whakaritea ki te RFC 1766 [RFC1766] kei roto te Tohu Reo kupu-rua (two-letter Language Code) (no te aro whanui ISO 639 [ISO639], ka taea e tetahi tohu kupu-rua te whai atu (no te aro whanui ISO 3166) [ISO366]). Hei tauira, te 'en' mo te English, te 'fr' mo te French, 'te en-uk' mo te English e whakamahia ana i Ingarangi (UK).
+
+
+
+ Langue
+ La langue du contenu intellectuel de la ressource.
+ Il est recommandé d'utiliser comme valeur de l'élément Langue celles definies par la RFC 1766 [RFC1766] qui comprend un code de langage à deux caractÚres(venant du standard ISO 639 [ISO639]), éventuellement suivi d'un code à deux lettres pour le pays (venant du standard ISO 3166 [ISO3166] ou en français [ISO3166]). Par exemple, 'en' pour l'anglais, 'fr' pour le français, ou 'en-uk' pour l'anglais utilisé au Royaume-Uni.
+
+
+
+ ЯзÑк
+ ЯзÑк ОМÑеллекÑÑалÑМПгП ÑПЎеÑÐ¶Ð°ÐœÐžÑ ÑеÑÑÑÑа.
+ ÐÐ»Ñ Ð¿ÑакÑОÑеÑкПгП ОÑпПлÑÐ·ÐŸÐ²Ð°ÐœÐžÑ ÑекПЌеМЎÑеÑÑÑ Ð·ÐœÐ°ÑеМОе ÑлеЌеМÑа ЯзÑк, ПпÑеЎелÑеЌПе RFC 1766 (ТÑгО ÐŽÐ»Ñ ÐžÐŽÐµÐœÑОÑОкаÑОО ÑзÑка), вклÑÑаÑÑОЌ ЎвÑÑ
+бÑквеММÑй кПЎ ÑзÑка (взÑÑÑй Оз ÑÑаМЎаÑÑа ISO 639 (ÐÐŸÐŽÑ ÐŽÐ»Ñ Ð¿ÑеЎÑÑÐ°Ð²Ð»ÐµÐœÐžÑ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐ¹ ÑзÑкПв)), за кПÑПÑÑÐŒ ÑлеЎÑÐµÑ (пÑО МеПбÑ
+ПЎОЌПÑÑО) ЎвÑÑ
+бÑквеММÑй кПЎ ÑÑÑÐ°ÐœÑ (взÑÑÑЌО Оз ÑÑаМЎаÑÑа ISO 3166 (ÐÐŸÐŽÑ ÐŽÐ»Ñ Ð¿ÑеЎÑÑÐ°Ð²Ð»ÐµÐœÐžÑ ÐœÐ°Ð·Ð²Ð°ÐœÐžÐ¹ ÑÑÑаМ)). ÐапÑОЌеÑ, "en" - ÐŽÐ»Ñ Ð°ÐœÐ³Ð»ÐžÐ¹ÑкПгП, "fr" - ÐŽÐ»Ñ ÑÑаМÑÑзÑкПгП, "en-uk" - ÐŽÐ»Ñ Ð°ÐœÐ³Ð»ÐžÐ¹ÑкПгП, ОÑпПлÑзÑеЌПгП в ÐелОкПбÑОÑаМОО.
+
+
+
+ Lengua
+ Lengua/s del contenido intelectual del recurso. Practicamente el contenido de este campo deberÃa coincidir con los de la RFC 1766 (Tags para la identificación de lenguas, http://ds.internic.net/rfc/rfc1766.txt); por ejemplo: en, es, de, fi, ja y zh.
+
+
+
+ اÙÙغة
+ ÙØ°Ù ÙÙ Ùغة اÙÙ
+ØتÙ٠اÙÙÙر٠ÙÙÙ
+صدر . ÙÙÙ
+ا Ùا٠عÙ
+ÙÙا , Ù
+ØتÙÙ Ù؞ا اÙØÙÙ Ùجؚ Ø£Ù Ùتطاؚ٠Ù
+ع RFC 1766 ] اÙاÙ
+Ø«ÙØ© تضÙ
+ th, ja, fr, es, fi, de, en Ù zh ÙرÙ
+Ùز ÙÙتعرÙ٠ؚاÙÙغة [
+
+
+
+ è¯ç§
+ æè¿°èµæºç¥è¯å
+容çè¯ç§ã
+ 建议æ¬å
+çŽ çåŒéçšRFC 3066[RFC3066]ïŒè¯¥æ åäžISO 639 [ISO639]äžèµ·å®ä¹äºç±äž€äžªåäžäžªè± æåæ¯ç»æçäž»è¯èšæ çŸååæ çŸäŸåŠå
+æ¬âenâæâengâæ¥è¡šç€ºEnglish, "akk" æ¥è¡šç€º "en-GB"衚瀺è±åœè±è¯ã
+
+
+
+ Jazyk
+ Jazyk intelektuálnÃho obsahu zdroje.
+ DoporuÄenÃœ postup pro hodnoty prvku Jazyk je definován v RFC 1766 [RFC1766]: dvouznakovÃœ kód jazyka (pÅevzatÃœ z normy ISO 639 [ISO639]) volitelnÄ následovanÃœ dvouznakovÃœm kódem zemÄ (pÅevzatÃœm z normy ISO 3166 [ISO3166]). NapÅÃklad 'en' pro angliÄtinu, 'fr' pro francouzÅ¡tinu, 'cs' pro ÄeÅ¡tinu, nebo 'en-uk' pro angliÄtinu uÅŸÃvanou ve Spojeném královstvÃ.
+
+
+
+ Taal
+ De taal waarin het document is beschreven. Voorgeschreven wordt de ISO639-1 norm, een twee karakter taalcode van de ISO 639(639-1 en 639-2) norm. Taalcodes kunnen van een lijst worden gekozen: http://www.ics.uci.edu/pub/ietf/http/related/iso639.txt, Eventueel kan ISO3166 (landencodes) gebruikt worden om aan te geven in welk gebied de taal wordt gesproken. Deze kunnen ook van een lijst worden gekozen: http://www.ics.uci.edu/pub/ietf/http/related/iso3166.txt.
+
+
+
+
+
+
+
+
+
+ Lingua
+ Le lingua del contento intellectual del ressource.
+ Le practica recommendate pro le valores del elemento lingua es definite per RFC 1766 [RFC1766], que include un codice de lingua de duo litteras (prendite del standard ISO 639 [ISO639]), sequite optionalmente per un codice de pais de duo litteras (prendite del standard ISO 3166 [ISO3166]). Per exemplo, 'ia' pro interlingua, 'fr' pro francese, o 'en-uk' pro le anglese del Regno Unite.
+
+
+
+ à€à€Ÿà€·à€Ÿ
+ à€®à€Ÿà€¹à€¿à€€à¥à€žà€Ÿà€ à¥à€¯à€Ÿà€à¥ à€à€Ÿà€·à€Ÿ
+ à€à€Šà€Ÿ. à€®à€°à€Ÿà€ à¥ - à€à€Ÿà€°à€€à¥à€¯ à€à€Ÿà€·à€Ÿ
+
+
+
+ à®®à¯à®Žà®¿
+ வள஀à¯à®€à®¿à®©à¯ à®
+றிவியறà¯à®€à®©à®®à®Ÿà®© பà¯à®°à¯à®³à®à®à¯à®à®€à¯à®€à®¿à®©à¯ à®®à¯à®Žà®¿.
+ சடà®à¯à®à®³à¯ à®à®¿à®ªà®Ÿà®°à®à¯ à®à¯à®¯à¯à®¯à¯à®®à¯ à®®à¯à®²à¯à®€à®°à®®à¯ à®à¯à®¯à®²à¯: à®®à¯à®Žà®¿à®¯à®¿à®©à¯ à®à®±à¯à®ªà¯à®ªà®¿à®©à¯ ம஀ிபà¯à®ªà¯à®à®³à¯ RFC 1766 à®à®²à¯ விவரி஀à¯à®€à®€à¯, à®
+஀ில௠à®à®°à®£à¯à®à¯ - à®à®Žà¯à®€à¯à®€à¯ à®®à¯à®Žà®¿ சிரல௠(ISO 639 à®à¯à®šà¯à®€à®°à®€à¯à®€à®¿à®²à®¿à®°à¯à®šà¯à®€à¯ à®à®à¯à®à¯à®à®ªà®à¯à®à®€à¯, வà¯à®£à¯à®à¯à®®à®Ÿà®©à®Ÿà®²à¯ à®à®°à¯ à®à®°à®£à¯à®à¯ - à®à®Žà¯à®€à¯à®€à¯ ஀à¯à®à®®à¯ சிரல௠à®à¯à®°à¯à®€à¯à®€à®¿à®°à¯à®à¯à®à¯à®®à¯ (ISO 3166 à®à¯à®šà¯à®€à®°à®€à¯à®€à®¿à®²à®¿à®°à¯à®šà¯à®€à¯ à®à®à¯à®à¯à®à®ªà®à¯à®à®€à¯). à®à®€à®Ÿà®à®°à®£à®®à¯: English à®à¯à®à¯ 'en', French à®à¯à®à¯ 'fr', à®
+லà¯à®²à¯à®€à¯ English used in the United Kingdom à®à¯à®à¯ 'en-uk'.
+
+
+
+ NgÎn ngữ
+ NgÃŽn ngữ của chÃnh vÄn của ná»i dung của nguá»n tin
+
+
+
+ 1.1
+ Dublin Core Metadata Initiative
+ Optional
+ Character String
+ Unlimited
+
+
+
+
+ Relation
+ A reference to a related resource.
+ Recommended best practice is to reference the resource by means of a string or number conforming to a formal identification system.
+
+
+
+ Whai Panga
+ He tohutoro ki tetahi rauemi whai panga.
+ Ko te tino huarahi kua tohua, ko te tohutoro ki te rauemi ma te aho, te tau ranei, e hangai ana ki te punaha taututanga okawa.
+
+
+
+ Relation
+ Une référence à une autre ressource qui a un rapport avec cette ressource.
+ Il est recommandé de référencer cette ressource par une chaîne de caractÚres ou un numéro conforme à un systÚme formel d'identification.
+
+
+
+ ÐÑМПÑеМОе
+ веММÑй ÑеÑÑÑÑ.
+ ÐÐ»Ñ Ð¿ÑакÑОÑеÑкПгП ОÑпПлÑÐ·ÐŸÐ²Ð°ÐœÐžÑ ÑекПЌеМЎÑеÑÑÑ ÐžÐŽÐµÐœÑОÑОÑОÑПваÑÑ ÑеÑÑÑÑ Ð¿ÐŸÑÑеЎÑÑвПЌ ÑÑÑПкО ОлО ÑОÑла, ÑППÑвеÑÑÑвÑÑÑегП ÑПÑЌалÑМПй ОЎеМÑОÑОкаÑОПММПй ÑОÑÑеЌе.
+
+
+
+ Relación
+ Un identificador de un segundo recurso y su relación con el recurso actual. Este elemento permite enlazar los recursos relacionados y las descripciones de los recursos. Por ejemplo: IsVersionOf - Incluye la edición de un trabajo, IsBasedOn - La traducción de un trabajo, IsPartOf - Un capÃtulo de un libro, IsFormatOf - Un mecanismo de transformación de un conjunto de datos en una imagen. Para asegurar la interoperabilidad, las relaciones deberÃan ser seleccionadas de una lista de elementos que actualmente se encuentra bajo desarrollo en un grupo de trabajo.
+
+
+
+ اÙعÙاÙØ©
+ Ùذا Ù
+عر٠ÙÙÙ
+صدر اÙثاÙ٠٠عÙاÙت٠ؚاÙÙ
+صدر اÙØاÙÙ . ÙسÙ
+Ø Ùذا اÙعاÙ
+٠ؚتÙضÙØ Ø§ÙرÙاؚط ØšÙ٠اÙÙ
+صادر اÙÙ
+تعÙÙØ© ؚؚعضÙا ٠تÙصÙ٠اÙÙ
+صدر . اÙاÙ
+Ø«ÙØ© تضÙ
+ طؚعة اÙعÙ
+Ù ) Ùسخة Ù
+Ù ( ترجÙ
+Ø© عÙ
+Ù ) اعتÙ
+ادا عÙÙ ( Ùص٠Ù
+Ù Ùتاؚ ) جزء Ù
+Ù ( ٠تØÙÙÙÙ Ù
+ÙÙاÙÙÙÙØ© ÙÙ
+جÙ
+Ùعة Ù
+عÙÙÙ
+اتÙØ© اÙ٠صÙرة ) صÙغة Ù
+Ù ( Ù
+٠أج٠اÙتعاÙ
+٠اÙÙ
+؎تر٠, Ùجؚ اختÙار اÙعÙاÙات Ù
+٠اÙÙا؊Ù
+Ø© اÙÙ
+رÙÙ
+Ø© ٠اÙت٠ÙتÙ
+ اعدادÙا ØاÙÙا ضÙ
+Ù ØÙÙات Ùر؎ة عÙ
+Ù
+
+
+
+ å
+³è
+ æ¶åççžå
+³èµæºã
+ èåœçžå
+³èµæºæ¶ïŒå»ºè®®äœ¿çšç¬Šåæ£åŒæ è¯ç³»ç»çå笊䞲æè
+æ°åã
+
+
+
+ Vztah
+ Odkaz na pÅÃbuznÃœ zdroj.
+ DoporuÄuje se odkazovat zdroj znakovÃœm ÅetÄzcem nebo ÄÃslem odpovÃdajÃcÃm nÄkterému z formálnÃch identifikaÄnÃch systémů.
+
+
+
+ Relatie
+ Een identificatie van een tweede bron en de relatie met de huide Internetbron. Voorbeelden zijn een editie van een werk (IsVersionOf), een vertaling van een werk (IsBasedOn), een hoofdstuk van een boek (IsPartOf) en een mechanische transformatie van een dataset in een plaatje (IsFormatOf). De DC Working Groups zijn bezig met een lijst met de meest verwachte relaties. Aanbevolen wordt om de relaties van deze lijst te gebruiken: http://purl.oclc.org/metadata/dublin_core/wrelationdraft.html.
+
+
+
+
+
+
+
+
+
+ Relation
+ Un referentia a un ressource correlate.
+ Le practica recommendate es facer referentia al ressource per medio de un catena de characteres o numero conforme a un systema de identification formal.
+
+
+
+ à€šà€Ÿà€€à¥ , à€žà€à€¬à€à€§
+ à€®à€Ÿà€¹à€¿à€€à¥à€žà€Ÿà€ à¥à€¯à€Ÿà€¶à¥ à€žà€à€¬à€à€§ à€Šà€Ÿà€à€µà€£à€Ÿà€°à€Ÿ à€žà€à€Šà€°à¥à€
+ à€à€Šà€Ÿ. à€®à€Ÿà€¹à€¿à€€à¥ à€à€Ÿà€³à¥à€¯à€Ÿà€µà€°à¥à€² à€ªà€€à¥à€€à€Ÿ(URL)
+
+
+
+ à®à®®à¯à®ªà®šà¯à®€à®®à¯
+ à®à®®à¯à®ªà®šà¯à®€à®ªà®à¯à® வள஀à¯à®€à¯ à®à¯à®±à®¿à®à¯à®à®¿à®°à®€à¯.
+ à®à®°à¯ à®®à¯à®±à¯à®à®Ÿà®°à¯à®šà¯à®€ à®
+à®à¯à®¯à®Ÿà®³ à®
+à®®à¯à®ªà¯à®ªà¯ à®à®£à®à¯à®à®®à®Ÿà®© à®à®°à¯ à®à®°à®®à¯ à®
+லà¯à®²à®€à¯ à®à®£à¯ à®à®ªà®¯à¯à®à®¿à®€à¯à®€à¯ வள஀à¯à®€à¯ à®
+à®à®¯à®Ÿà®³à®®à¯ à®à¯à®¯à¯à®µà®€à¯ சடà®à¯à®à®³à¯ à®à®¿à®ªà®Ÿà®°à®à¯ à®à¯à®¯à¯à®¯à¯à®®à¯ à®®à¯à®²à¯à®€à®°à®®à¯ à®à¯à®¯à®²à¯.
+
+
+
+ Quan há»
+ Tham chiếu Äến các nguá»n tin liên quan Äến nguá»n Äang mÃŽ tả
+
+
+
+ 1.1
+ Dublin Core Metadata Initiative
+ Optional
+ Character String
+ Unlimited
+
+
+
+
+ Coverage
+ The extent or scope of the content of the resource.
+ Coverage will typically include spatial location (a place name or geographic coordinates), temporal period (a period label, date, or date range) or jurisdiction (such as a named administrative entity). Recommended best practice is to select a value from a controlled vocabulary (for example, the Thesaurus of Geographic Names [TGN]) and that, where appropriate, named places or time periods be used in preference to numeric identifiers such as sets of coordinates or date ranges.
+
+
+
+ Kapitanga
+ Te roanga, te whanuitanga ranei o te whakakaupapatanga o te rauemi.
+ Ko te tikanga, ka uru atu te wahi mokowa (te ingoa o tetahi wahi, whakapiritanga matawhenua ranei), whakaritenga wa (he tapatanga wa (period label, ra, whakatakotoranga whanui o nga ra), te whakaritenga ture (penei i te putahi whakahaere). Ko te tino huarahi kua tohua, ko te tipako uara mai i tetahi whakaritenga kupu (hei tauira, i tetahi Puna Kupu Ingoa Matawhenua (Geographic Names [TGN] i nga wahi tika, ko nga wahi me nga whakaritenga wa ka whakamahia i mua i te whakamahitanga o nga taututanga tau penei i nga huinga whakapiritanga me nga whakatakotoranga whanui o nga ra.
+
+
+
+ Couverture
+ La portée ou la couverture spatio-temporelle de la ressource.
+ La couverture typiquement inclut une position géographique (le nom d'un lieu ou ses coordonnées), une période de temps (un nom de période, une date, ou un intervalle de temps) ou une juridiction (telle que le nom d'une entité administrative). Il est recommandé de choisir la valeur de Couverture dans un vocabulaire contrÎlé (par exemple, un thésaurus de noms géographiques, comme[TGN]) et, quand cela est approprié, des noms de lieux ou de périodes plutÎt que des identifiants numériques tels que des coordonnées ou des intervalles de dates.
+
+
+
+ ÐÑ
+ваÑ
+ ÐÑПÑÑжеММПÑÑÑ Ðž гÑаМОÑÑ ÑПЎеÑÐ¶Ð°ÐœÐžÑ ÑеÑÑÑÑа.
+ ÐÑ
+Ð²Ð°Ñ ÐŸÐ±ÑкМПвеММП вклÑÑÐ°ÐµÑ Ð¿ÑПÑÑÑаМÑÑвеММПе ЌеÑÑПМаÑ
+ПжЎеМОе (МазваМОе ЌеÑÑМПÑÑО ОлО геПгÑаÑОÑеÑкОе кППÑЎОМаÑÑ), вÑеЌеММПй пÑПЌежÑÑПк (ÑказаМОе пеÑОПЎа, ЎаÑа ОлО ÑÑÐŽ ЎаÑ) ОлО ÑÑОÑЎОкÑÐžÑ (ÑказаМОе еЎОМОÑÑ Ð°ÐŽÐŒÐžÐœÐžÑÑÑаÑОвМПгП ЎелеМОÑ). Ðа пÑакÑОке ÑекПЌеМЎÑеÑÑÑ Ð²ÑбОÑаÑÑ Ð·ÐœÐ°ÑеМОе Оз кПМÑÑПлОÑÑеЌПгП ÑлПваÑÑ (МапÑОЌеÑ, ТезаÑÑÑÑа геПгÑаÑОÑеÑкОÑ
+ МазваМОй TGN), О, еÑлО ÑÑП ÑЌеÑÑМП, пÑеЎпПÑÑеМОе ПÑЎаеÑÑÑ ÑказаМОÑÐŒ ЌеÑÑМПÑÑей ОлО вÑеЌеММÑÑ
+ пÑПЌежÑÑкПв вЌеÑÑП ÑОÑÑПвÑÑ
+ ОЎеМÑОÑОкаÑПÑПв, как, МапÑОЌеÑ, ÑОÑÑеЌ кППÑÐŽÐžÐœÐ°Ñ ÐžÐ»Ðž вÑеЌеММÑÑ
+ ÑÑЎПв.
+
+
+
+ Cobertura
+ La caracterÃstica de cobertura espacial y/o temporal del contenido intelectual del recurso. La cobertura espacial se refiere a una región fÃsica (por ejemplo, sector celestial); uso de coordenadas (por ejemplo, longitud y latitud) o nombres de lugares extraidos de una lista controlada. La cobertura temporal se refiere al contenido del recurso en vez de a cuando fue creado o puesto accesible ya que este último pertenece al elemento Date. Se usa el mismo formato basado en http://www.w3.org/TR/NOTE-datetime.
+
+
+
+ اÙتغطÙØ©
+ Ù٠اÙخصا؊ص اÙÙ
+ÙاÙÙØ© ا٠اÙزÙ
+ÙÙØ© ÙÙÙ
+ØتÙ٠اÙÙÙر٠ÙÙÙ
+صدر . اÙتغطÙØ© اÙÙ
+ÙاÙÙØ© ت؎Ùر اÙ٠جÙØ© Ø·ØšÙعÙØ© )Ù
+Ø«Ù , Ùطاع سÙ
+اÙÙ ( استخداÙ
+ اÙاØداثÙات ) Ù
+ث٠خط اÙØ·Ù٠٠خط اÙعرض ( Ù٠أسÙ
+اء اÙ
+ÙÙØ© Ù
+ستØÙÙ
+Ø© ا٠Ù
+تجÙات ؚاÙÙاÙ
+Ù . اÙتغطÙØ© اÙزÙ
+ÙÙØ© ثعÙد اÙÙ Ù
+ا Ùرجع اÙÙ٠اÙÙ
+صدر Ù ÙÙس ا٠Ù
+ت٠تÙ
+ تÙÙÙر٠) اÙاخÙر ÙتعÙ٠ؚعاÙ
+٠اÙتارÙØ® ( استخداÙ
+ ÙÙس صÙغة اÙتارÙØ® ا٠اÙÙÙت ) عادة Ù
+د٠] ( صÙاغات اÙÙÙÙ
+ ٠اÙÙÙت ) اعتÙ
+ادا عÙÙ (ISO 8601 اÙÙ
+ÙاØ؞ة اÙÙÙÙØ© [http://www.w3.org/TR/NOTE-datetime, W3C ÙÙ
+ا ÙÙ Ù
+Ùص٠ؚ٠ÙعاÙ
+٠اÙتارÙØ® ا٠Ùترات زÙ
+ÙÙØ© Ù
+Ù Ùا؊Ù
+Ø© Ù
+ستØÙÙ
+Ø© ا٠Ù
+تجÙات ؚاÙÙاÙ
+Ù
+
+
+
+ èŠçèåŽ
+ èµæºå
+容ææ¶åçå€å»¶äžèŠçèåŽ
+ èŠçèåŽäžè¬å
+æ¬ç©ºéŽäœçœ®ïŒäžäžªå°åæå°çåæ ïŒãæ¶éŽåºéŽïŒäžäžªæ¶éŽæ è¯ïŒæ¥ææäžäžªæ¥æè åŽïŒãæè
+æéïŒæ¯åŠåœåçææå®äœïŒæšèèŠçèåŽæ奜æ¯åèªäºäžäžªåæ§è¯è¡šïŒäŸåŠå°åè¯åº [TGN]ïŒïŒå¹¶åºå°œå¯èœå°äœ¿çšç±æ°å衚瀺çåæ ææ¥æåºéŽæ¥æè¿°å°åäžæ¶éŽæ®µã
+
+
+
+ PokrytÃ
+ Rozsah nebo zábÄr obsahu zdroje.
+ Pokrytà bude typicky obsahovat prostorové umÃstÄnà (jméno mÃsta nebo zemÄpisné souÅadnice), Äasové obdobà (oznaÄenà obdobÃ, datum nebo ÄasovÃœ interval) nebo jurisdikci (napÅ. jméno administrativnà jednotky). DoporuÄuje se vybÃrat hodnotu z ÅÃzeného slovnÃku (napÅ. Thesaurus of Geographic Names [TGN]) a tam, kde je to vhodné, uvádÄt mÃsta nebo Äasové úseky spÃÅ¡e jménem neÅŸ ÄÃselnÃœmi identifikátory jako jsou soubory souÅadnic nebo Äasové intervaly.
+
+
+
+ Dekking
+ De ruimtelijke of tijdelijke karakteristieken van de intellectuele inhoud van de Internetbron. Ruimtelijke dekking verwijst naar een geografisch gebied. Gebruik coordinaten (longitude (lengtegraad) en latitude (breedtegraad)) of plaatsnamen die van een gecontroleerde lijst komen of volledig uitgeschreven zijn. Dekking in de tijd geeft de tijdsperiode aan waarop de inhoud van de Internetbron betrekking heeft en niet wanneer de Internetbron is gemaakt of beschikbaar is gesteld (dit laatste hoort ingevult te worden bij "Date"). Gebruik dezelfde datum/tijd formaat als bij "Date"; W3C Technical Note http://www.w3.org/TR/NOTE-datetime of tijdsperioden die van een gecontroleerde lijst komen of volledig uitgeschreven zijn. Coverage is in ontwikkeling bij de Dublin Core Working group http://www.alexandria.ucsb.edu/docs/metadata/dc_coverage.html.
+
+
+
+
+
+
+
+
+
+ Copertura
+ Le extension physic o abstracte del contento del ressource.
+ Le copertura typicamente include un location spatial (un nomine de localitate o coordinatas geographic), un periodo de tempore (un etiquetta de periodo, data, o gamma de datas), o un jurisdiction (tal como un entitate administrative nominate). Le practica recommendate es selectionar un valor a partir de un vocabulario controlate (per exemplo, le Thesaurus of Geographical Names [TGN]) e que, quando appropriate, localitates o periodos de tempore nominate sia utilizate in preferentia a identificatores numeric tales como collectiones de coordinatas o gammas de datas.
+
+
+
+ à€µà¥à€¯à€Ÿà€ªà¥à€€à¥
+ à€®à€Ÿà€¹à€¿à€€à¥à€žà€Ÿà€ à¥à€¯à€Ÿà€à¥ à€à¥à€à¥à€²à€¿à€ à€®à€Ÿà€¹à€¿à€€à¥
+ à€à€Šà€Ÿ. à€à¥à€à¥à€²à€¿à€ à€µà¥à€¯à€Ÿà€ªà¥à€€à¥
+
+
+
+ பரபà¯à®ªà¯
+ வள஀à¯à®€à®¿à®©à¯ பà¯à®°à¯à®³à®à®à¯à®à®€à¯à®€à®¿à®©à¯ விஞà¯à®€à®¿à®°à®£à®®à¯ à®
+லà¯à®²à®€à¯ வரà¯à®¯à¯à®²à¯à®²à¯.
+ à®à®€à®Ÿà®à®°à®£à®®à®Ÿà®: à®à®à®®à¯à®à®Ÿà®°à¯à®šà¯à®€ à®à®°à¯à®ªà¯à®ªà®¿à®à®®à¯ (à®à®°à¯ à®à®à®€à¯à®€à®¿à®©à¯ பà¯à®¯à®°à¯ à®
+லà¯à®²à®€à¯ பà¯à®µà®¿à®¯à®¿à®¯à®²à¯ à®à®¯à®à¯à®à®³à¯), à®à®®à¯à®®à¯à®à¯à®°à®¿à®¯ à®à®Ÿà®²à®µà®°à¯ (à®à®Ÿà®²à®µà®°à¯ à®
+à®à¯à®¯à®Ÿà®³à®®à¯, ஀à¯à®€à®¿, à®
+லà¯à®²à®€à¯ ஀à¯à®€à®¿ வà¯à®à¯à®à¯)à®
+லà¯à®²à®€à¯ à®à®à¯à® à®à®²à¯à®²à¯ (à®à®€à®Ÿà®à®°à®£à®®à¯: சிரà¯à®µà®Ÿà® பà¯à®°à¯à®³à¯)பரபà¯à®ªà®¿à®²à¯ à®à®³à¯à®ªà¯à®ªà®à¯à®®à¯. à®à®°à¯ à®à®à¯à®à¯à®ªà¯à®ªà®à¯à® à®à¯à®²à¯ வள஀à¯à®€à®¿à®²à®¿à®°à¯à®šà¯à®€à¯ (à®à®€à®Ÿà®à®°à®£à®®à¯: Thesaurus of Geographic Names [TGN])à®®à¯à®²à¯à®®à¯ à®à®à¯à®à¯ ஀à®à¯à®®à¯, à®à®£à¯ à®à¯à®±à®¿à®ªà¯à®ªà®¿à®à¯à®à®³à¯ à®à®€à®Ÿà®à®°à®£à®®à®Ÿà® à®à®¯à®à¯à®à®³à¯ à®à®£à®®à¯ à®
+லà¯à®²à®€à¯ ஀à¯à®€à®¿ வà¯à®à¯à®à¯à®à¯à®à¯ ப஀ிலட஠பà¯à®¯à®°à¯à®³à¯à®³ à®à®à®à¯à®à®³à¯ à®
+லà¯à®²à¯à®€à¯ பà¯à®¯à®°à¯à®³à¯à®³ à®à®Ÿà®²à®µà®°à¯à®à®³à¯ à®à®ªà®¯à¯à®à®¿à®à¯à®à¯à®µà®€à¯ சடà®à¯à®à®³à¯ à®à®¿à®ªà®Ÿà®°à®à¯ à®à¯à®¯à¯à®¯à¯à®®à¯ à®®à¯à®²à¯à®€à®°à®®à¯ à®à¯à®¯à®²à¯
+
+
+
+ Phạm vi bao quát
+ MÃŽ tả mức Äá» bao quát của ná»i dung của nguá»n tin
+ Phạm vi bao quát có thá» là vá» phạm vi khÃŽng gian (tên Äá»a danh, toạ Äá» khÃŽng gian,..), thá»i gian (giai Äoạn, chuá»i ngà y tháng, ...), phạm vi vá» tà i phán (tên lãnh thá», nÆ°á»c,..). Khuyến nghá» sá» dụng từ vá»±ng có kiá»m soát Äá» chá»n lá»±a thuáºt ngữ phù hợp. Thà dụ sá» dụng từ Äiá»n từ chuẩn vá» tên Äá»a lÃœ, tên Äá»a danh,...
+
+
+ 1.1
+ Dublin Core Metadata Initiative
+ Optional
+ Character String
+ Unlimited
+
+
+
+
+ Rights Management
+ Information about rights held in and over the resource.
+ Typically, a Rights element will contain a rights management statement for the resource, or reference a service providing such information. Rights information often encompasses Intellectual Property Rights (IPR), Copyright, and various Property Rights. If the Rights element is absent, no assumptions can be made about the status of these and other rights with respect to the resource.
+
+
+
+ Motika
+ Ko nga mohiohio ki nga motika o tetahi rauemi.
+ Ko te tikanga, kei te huanga Motika e pupuri ana he korero mo te whakaritenga motika mo te rauemi, he ratonga tohutoro e whakarato ana ranei i enei tumomo mohiohio. He nui nga wa, puta ai i roto i te mohiohio Motika te Mana Whakairo Hinegaro (Intellectual Property Rights - (IPR)), te Manatarua me nga Tuahua Mana Taonga (Property Rights). Ki te kore te huanga Motika, kaore e taea te pohehe noa ki te mana o enei, nga motika ranei e pa ana ki te rauemi.
+
+
+
+ Droits
+ Information sur les droits sur et au sujet de la ressource.
+ Typiquement, un élément Droits contiendra un état du droit à gérer une ressource, ou la reférence à un service fournissant cette information. Ces droits souvent couvrent les droits de propriété intellectuelle (IPR), Copyright, et divers droits de propriété. Si l'élément Droits est absent, aucune hypothÚse ne peut être faite sur l'état de ces droits, ou de tout autre, par rapport à la ressource.
+
+
+
+ ÐÑавПвПе ÑегÑлОÑПваМОе
+ ÐÐœÑПÑЌаÑÐžÑ ÐŸ пÑаваÑ
+ ОÑпПлÑзПваМОÑ, ÑПЎеÑжаÑаÑÑÑ Ð²ÐœÑÑÑО О вМе ÑеÑÑÑÑа.
+ ÐбÑÑМП ÑÐ»ÐµÐŒÐµÐœÑ ÐÑава ÑПЎеÑÐ¶ÐžÑ Ð¿ÐŸÐ»ÐŸÐ¶ÐµÐœÐžÐµ П пÑавПвÑÑ
+ МПÑЌаÑ
+, ÑегÑлОÑÑÑÑОÑ
+ ÑÑМкÑОПМОÑПваМОе ÑеÑÑÑÑа ОлО ÑÑÑÐ»ÐºÑ ÐœÐ° ÑлÑжбÑ, пÑеЎПÑÑавлÑÑÑÑÑ ÑÑÑ ÐžÐœÑПÑЌаÑОÑ. ÐÑÐ°Ð²ÐŸÐ²Ð°Ñ ÐžÐœÑПÑЌаÑÐžÑ ÐŸÐ±ÑÑМП вклÑÑÐ°ÐµÑ ÑÐ²ÐµÐŽÐµÐœÐžÑ ÐŸ ÐÑаваÑ
+ ОМÑеллекÑÑалÑМПй ÑПбÑÑвеММПÑÑО, ÐвÑПÑÑкПЌ пÑаве О ÐŽÑÑгОÑ
+ ÐÐŒÑÑеÑÑвеММÑÑ
+ пÑаваÑ
+. ÐÑÑÑÑÑÑвОе ÑлеЌеМÑа ÐÑава Ме ÐŒÐŸÐ¶ÐµÑ ÑвлÑÑÑÑÑ ÐŸÑМПваМОеЌ ÐŽÐ»Ñ ÐºÐ°ÐºÐžÑ
+-лОбП пÑеЎпПлПжеМОй П пÑавПвПЌ ÑÑаÑÑÑе О ÐŽÑÑгОÑ
+ пÑаваÑ
+, каÑаÑÑОÑ
+ÑÑ ÑеÑÑÑÑа.
+
+
+
+ Derechos
+ Una referencia (URL, por ejemplo) para una nota sobre derechos de autor, para un servicio de gestión de derechos o para un servicio que dará información sobre términos y condiciones de acceso a un recurso. Una especificación formal del elemento Rights se encuentra catualmente en discusión y por lo tanto su uso se considera experimental.
+
+
+
+ ØÙÙ٠اÙادارة
+ Ù٠اÙادة ØÙÙ٠اÙادارة , Ù
+عر٠Ù
+رتؚط ؚاÙادة ØÙÙ٠ا Ùادارة , Ù
+عر٠Ù
+رتؚط ؚخدÙ
+Ø© تÙدÙ
+ Ù
+عÙÙÙ
+ات ع٠ØÙÙ٠اÙادارة اÙخاصة ؚاÙÙ
+صدر
+
+
+
+ æé
+ æå
+³èµæºæ¬èº«ææçæ被èµäºçæéä¿¡æ¯
+ äžè¬èèšïŒæéå
+çŽ åºå
+æ¬äžäžªå¯¹èµæºçæé声æïŒæè
+æ¯å¯¹æäŸè¿äžä¿¡æ¯çæå¡çåç
+§ãæéäžè¬ å
+æ¬ç¥è¯äº§æ(IPR)ïŒçææå
+¶ä»åç§åæ ·ç产æãåŠæ没ææéå
+çŽ çæ 泚ïŒäžå¯ä»¥å¯¹äžèµæºçžå
+³ çäžè¿°æå
+¶ä»æå©çæ
+åµäœåºä»»äœåå®ã
+
+
+
+ Práva
+ Informace o právech vztahujÃcÃch se k popisovanému zdroji.
+ Prvek Práva bude typicky obsahovat ustanovenà o správÄ autorskÃœch/vlastnickÃœch práv ke zdroji nebo odkaz na sluÅŸbu poskytujÃcà takovéto informace. Informace o právech Äasto zahrnujà práva duÅ¡evnÃho vlastnictvà (IPR), autorské právo a různá vlastnická práva. JestliÅŸe prvek Práva chybÃ, nelze odvozovat şádné pÅedpoklady o stavu tÄchto a jinÃœch práv vztahujÃcÃch se k popisovanému zdroji.
+
+
+
+ Copyright
+ Een copyright verklaring of een link naar een copyright verklaring of een link naar een service die informatie geeft over de copyright van de Internetbron.
+
+
+
+
+
+
+
+
+
+ Gestion de derectos
+ Information super derectos detenite super e a proposito del ressource.
+ Typicamente le elemento derectos continera un declaration de gestion de derectos pro le ressource, o un referentia a un servicio que provide tal information. Information de derectos frequentemente involve derectos de proprietate intellectual (IPR), copyright e varie derectos de proprietate. Si le elemento Derectos es absente, necun hypothese pote esser facite quanto al stato de iste e altere derectos concernente ressource.
+
+
+
+ à€¹à€à¥à€
+ à€¬à¥à€§à¥à€Šà€¿à€ à€žà€à€ªà€Šà¥à€à€Ÿà€¹à€à¥à€
+ à€žà¥à€µà€€à€à€¹à€Ÿà€à¥ à€²à¥à€à€š à€à€Ÿà€ªà¥à€š à€
+à€¥à€µà€Ÿ à€®à€Ÿà€¹à€¿à€€à¥à€à€Ÿà€³à¥à€¯à€Ÿà€µà€° à€ªà¥à€°à€à€Ÿà€¶à€¿à€€ à€à€°à€£à¥à€¯à€Ÿà€à€Ÿ à€²à¥à€à€ à€
+à€¥à€µà€Ÿ à€²à¥à€à€¿à€à¥à€à€Ÿ à€¬à¥à€§à¥à€Šà€¿à€ à€žà€à€ªà€Šà¥à€à€Ÿà€¹à€à¥à€
+
+
+
+ à®à®°à®¿à®®à¯à®à®³à¯ à®®à¯à®²à®Ÿà®£à¯à®®à¯
+ வள஀à¯à®€à®¿à®©à¯à®³à¯ à®à®°à®¿à®®à¯à®à®³à¯ à®®à¯à®²à¯à®®à¯ வள஀à¯à®€à®¿à®©à¯ à®®à¯à®²à¯ à®à®³à¯à®³ à®à®°à®¿à®®à¯à®à®³à¯ பறà¯à®±à®¿à®¯ ஀à®à®µà®²à¯.
+ à®à®€à®Ÿà®à®°à®©à®®à®Ÿà®, à®à®°à¯ à®à®°à®¿à®®à¯ à®à®±à¯à®ªà¯à®ªà¯ à®à®°à¯ வளம௠à®à®°à®¿à®®à¯à®à®³à¯ à®®à¯à®²à®Ÿà®£à¯à®®à¯ à®à¯à®±à¯à®±à¯ à®à®à¯à®®à¯, à®
+லà¯à®²à®€à¯ à®à®šà¯à®€ ஀à®à®µà®²à¯ à®à¯à®à¯à®à¯à®à¯à®®à¯ à®à¯à®µà¯à®¯à®¯à¯ à®à¯à®à¯à®à®¿à®à¯à®à®Ÿà®à¯à®à¯à®®à¯. à®à®°à®¿à®®à¯à®à®³à¯ ஀à®à®µà®²à®¿à®²à¯ à®
+னà¯à®à®®à®Ÿà® à®
+றிவடறà¯à®±à®²à¯ à®à®°à®¿à®®à¯ (Intellectual Property Rights (IPR)), பிரà®à¯à®° (ப஀ிபà¯à®ªà¯) à®à®°à®¿à®®à¯, à®®à¯à®²à¯à®®à¯ பல படனà¯à®®à¯ à®à®°à®¿à®®à¯à®à®³à¯ பறà¯à®±à®¿ à®à®°à¯à®à¯à®à¯à®®à¯.
+
+
+
+ Quyá»n
+ ThÃŽng tin vá» các quyá»n có Äược Äá»i vá»i nguá»n tin hoặc Äá»i vá»i thÃŽng tin.
+ Yếu tá» Quyá»n chứa thÃŽng báo vá» các quyá»n liên quan Äến nguá»n tin hoặc chá» dẫn Äến má»t dá»ch vụ cung cấp thÃŽng báo nhÆ° váºy vá» quyá»n. ThÃŽng tin vá» quyá»n có thá» bao gá»m thÃŽng tin vá» quyá»n sá» hữu trà tuá», bản quyá»n và các quyá»n liên quan khác.
+
+
+ 1.1
+ Dublin Core Metadata Initiative
+ Optional
+ Character String
+ Unlimited
+
+
Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/metadata/ex.mds
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/metadata/ex.mds (revision 27727)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/metadata/ex.mds (revision 27727)
@@ -0,0 +1,496 @@
+
+
+
+
+ Extracted Greenstone Metadata 1.1
+ This document is the reference description, version 1.1 of the automatically extracted Greenstone Metadata Element Set. Most of the possible extracted metadata elements have been added.
+
+
+ Bá» siêu dữ liá»u Greenstone
+ MÃŽ tả vá» bá» siêu dữ liá»u Greenstone phiên bản 1.1 cho yếu tá» siêu dữ liá»u Greenstone Äược triết rút tá»± Äá»ng
+
+
+ ÙاصÙات ØšÙاÙات Greenstone اÙÙ
+ستخرجة 1.0
+ ÙاصÙات ØšÙاÙات ÙرÙÙستÙÙ
+
+
+
+
+ Not always available.
+ The title of the imported document as extracted by Greenstone.
+ Title
+
+
+ Nhan Äá»
+ Nhan Äá» của tà i liá»u nháºp khẩu và o Há» thá»ng và Äược Greenstone triết rút tá»± Äá»ng
+ KhÎng phải lúc nà o cũng sẵn có
+
+
+ اÙعÙÙاÙ
+ اÙعÙÙاÙ
+ غÙر Ù
+تÙÙر دا؊Ù
+ا.
+
+
+
+
+
+ Not always available.
+ The encoding of the imported document as extracted by Greenstone.
+ Encoding
+
+
+ BỠmã kÜ tự
+ ThÃŽng tin bá» mã kÃœ tá»± của tà i liá»u Äược nháºp khẩu mà Greenstone tá»± Äá»ng triết rut Äược
+ KhÎng phải lúc nà o cũng có sẵn
+
+
+ اÙت؎ÙÙر
+ اÙت؎ÙÙر
+ غÙر Ù
+تÙÙر دا؊Ù
+ا.
+
+
+
+
+
+ Not always available.
+ The language of the imported document as extracted by Greenstone.
+ Language
+
+
+ NgÎn ngữ
+ Tên ngÃŽn ngữ của tà i liá»u mà Greenstone tá»± Äá»ng triết rút Äược.
+ KhÎng phải lúc nà o cũng có sẵn
+
+
+ اÙÙغة
+ اÙÙغة
+ غÙر Ù
+تÙÙر دا؊Ù
+ا.
+
+
+
+
+
+
+ The filename of the document imported by Greenstone, suitable for display.
+ Source
+
+
+ Tên tá»p tin
+ Tên tá»p tin củâtì liá»u Äược Greenstone nháºp khẩu và o há» thá»ng.
+ ẚn Äá»i vá»i GLI bá»i Äã Äược hiá»n thá» trong cây thÆ° mục
+
+
+ اسÙ
+اء اÙÙ
+ÙÙات
+
+ غÙر Ù
+تÙÙر دا؊Ù
+ا.
+
+
+
+
+
+ SourceFile
+ The file the metadata has been extracted from
+
+
+
+
+
+ FileSize
+ The size of the source file in bytes
+
+
+
+
+
+ FileFormat
+ The format of the source file
+
+
+
+
+
+ MimeType
+ The MIME type of the source file
+
+
+
+
+
+ Identifier
+ Identifier assigned by Greenstone
+
+
+
+
+
+
+
+
+
+
+ Plugin
+ The Greenstone plugin used to extract metadata
+
+
+
+
+
+ URL
+ The URL the source file was retrieved from
+
+
+
+
+
+ assocfilepath
+ The filepath of any associated files
+
+
+
+
+
+ lastmodified
+ The date of the last modification of the source file
+
+
+
+
+
+ hascover
+ Whether or not a cover has been defined for the source file
+
+
+
+
+
+ NoText
+ True if the source file has no text
+
+
+
+
+
+ Date
+ The date of the source file
+
+
+
+
+
+ Image
+ Image
+
+
+
+
+
+ ImageType
+ The type of the image
+
+
+
+
+
+ ImageSize
+ The size of the image in bytes
+
+
+
+
+
+ ImageHeight
+ The height of the image in pixels
+
+
+
+
+
+ ImageWidth
+ The width of the image in pixels
+
+
+
+
+
+ Thumb
+ Thumbnail image
+
+
+
+
+
+ ThumbType
+ The file type of the thumbnail image
+
+
+
+
+
+ ThumbWidth
+ The width of the thumbnail image in pixels
+
+
+
+
+
+ ThumbHeight
+ The height of the thumbnail image in pixels
+
+
+
+
+
+ Screen
+ Screen
+
+
+
+
+
+ ScreenType
+ The type of the screen
+
+
+
+
+
+ ScreenWidth
+ The width of the screen in pixels
+
+
+
+
+
+ ScreenHeight
+ The height of the screen in pixels
+
+
+
+
+
+ SourceSegment
+ Source segment
+
+
+
+
+
+ NumPages
+ Number of pages
+
+
+
+
+
+ HTMLDisplay
+ from procite plugin
+
+
+
+
+
+ RecordNumber
+ from procite plugin
+
+
+
+
+
+ Workform
+ from procite plugin
+
+
+
+
+
+ Pages
+ Pages
+
+
+
+
+
+ PageNum
+ Number of pages
+
+
+
+
+
+ GENERATOR
+ GENERATOR
+
+
+
+
+
+ ISISRawRecord
+ ISISRawRecord
+
+
+
+
+
+ Creator
+ The Creator of a record, as extracted by Latex, Bibtex, and Refer plugins. Contains a concatenated set of all Authors.
+ Not always available.
+
+
+
+
+ Author
+ The Author of a record, as extracted byLatex, Bibtex, and Refer plugins. Each Author specified individually.
+ Not always available.
+
+
+ اÙÙ
+Ø€Ù٠؎خص
+ اÙÙ
+Ø€Ù٠؎خص
+ غÙر Ù
+تÙÙر دا؊Ù
+ا.
+
+
+
+
+ Placename
+ from gis plugin
+
+
+
+
+
+ Headers
+ from email plugin
+
+
+
+
+
+ InReplyTo
+ from email plugin
+
+
+
+
+
+ FromName
+ from email plugin
+
+
+
+
+
+ FromAddr
+ from email plugin
+
+
+
+
+
+ EmailAddress
+ Email address
+
+
+
+
+
+ EntryType
+ from bibtex plugin
+
+
+
+
+
+ Keyword
+ Keywords for a record, as extracted by Bibtex and Refer plugins.
+ Not always available.
+
+
+ اÙÙÙÙ
+ات اÙÙ
+ÙتاØÙØ©
+ اÙÙÙÙ
+ات اÙÙ
+ÙتاØÙØ©
+ غÙر Ù
+تÙÙر دا؊Ù
+ا.
+
+
+
+
+ BookConfOnly
+ from bibtex, refer plugin
+
+
+
+
+
+ JournalsOnly
+ from bibtex, refer plugin
+
+
+
+
+
+ equivlink
+ equivlink
+
+
+
+
+
+ Acronym
+ Acronym
+
+
+
+
+
+ mp3applet
+ from mp3 plugin
+
+
+
+
+
+ giquery
+ from mp3 plugin
+
+
+
+
+
+ srcurl
+ from mp3 plugin
+
+
+
+
+
+ Keyphrase
+ Keyphrase
+
+
+
+
+
+ Keyphrases
+ Keyphrases
+
+
+
+
Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/metadata/greenstone.mds
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/metadata/greenstone.mds (revision 27727)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/metadata/greenstone.mds (revision 27727)
@@ -0,0 +1,50 @@
+
+
+
+
+ Greenstone metadata set
+ Some special elements particular to Greenstone.
+
+
+ Bá» siêu dữ liá»u riêng của Greenstone
+ Má»t sá» yếu tá» riêng biá»t cho Greenstone.
+
+
+
+ Document Header
+ Headers that will be added to document display. For example, use this to include stylesheets in the document display. The content should be escaped HTML.
+ The _document:documentheader_ macro will be set to the value of this metadata.
+
+
+ Tiêu Äá» tà i liá»u
+ Tiêu Äá» Äược bá» sung và o phần hiá»n thá» của tà i liá»u. Thà dụ, sá» dụng Äiá»u nà y Äá» ÄÆ°a stylesheets và o trong viá»c hiá»n thá» tà i liá»u. Ná»i dung cần là escaped HTML.
+ Macro _document:documentheader_ sẜ Äược thiết láºp cho giá trá» của siêu dữ liá»u nà y
+
+
+
+
+ OAI DateStamp
+ The datestamp of the document to be used by the OAI server. Format must be YYYY-MM-DD. If not defined, oailastmodified will be used instead.
+
+
+
+
+ OAI Resource URL
+ The URL for the document to be used for dc:identifier. If not defined, a URL to the file defined by srclinkFile metadata will be used instead. If no srclinkFile either, then a URL to the Greenstone version of the document will be used.
+
+
+
+
+ Allow Printing
+ Controls whether or not a particular document can be printed from within the Realistic Books software. Defaults to 'true' (i.e allow printing); set to 'false' to prevent this.
+
+
+
+
+ Filename Encoding
+ The encoding of the filename. If this is known, it can be manually set here.
+ If not manually specified, Greenstone will try to guess the encoding of the filename upon building, which may or may not be correct.
+
+
+
+
Index: /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/metadata/profile.xml
===================================================================
--- /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/metadata/profile.xml (revision 27727)
+++ /other-projects/nightly-tasks/diffcol/trunk/model-collect/Word-PDF-Basic/metadata/profile.xml (revision 27727)
@@ -0,0 +1,9 @@
+
+
+
+
+]>
+