Context Navigation

← Previous Changeset
Next Changeset →

Changeset 9486

Timestamp:

2005-03-23T13:47:51+12:00 (19 years ago)

Author:

kjdon

Message:

moved the supportform and faq text out of here into teh relevant files, cos its not translated

File:

: 1 edited

trunk/greenorg/macros/english.dm (modified) (4 diffs)

Legend:

: Unmodified
: Added
: Removed

trunk/greenorg/macros/english.dm

-              r9483
+              r9486
+}
 _textimagepref_ {Preferences page}
 …
 _textimagedownload_ {Download}
 _textimageexamples_ {Examples}
-# These are not translated because the pages themselves are not translated
-_textimagefaq_ {FAQ}
 _textimagesupport_ {Support}
 #------------------------------------------------------------
 …
 _httpicontexmplon_ {_httpimg_/exmplon.gif}
-# These are not translated because the pages themselves are not translated
-## "faq" ## nav_bar_button ## tfaq ##
-_httpicontfaqof_ {_httpimg_/faqof.gif}
-_httpicontfaqon_ {_httpimg_/faqon.gif}
 ## "support" ## nav_bar_button ## tsup ##
 _httpicontsupof_ {_httpimg_/supof.gif}
 _httpicontsupon_ {_httpimg_/supon.gif}
 #######################################################################
 …
 Alternatively, if your department/organization is willing to organise and fund a Greenstone workshop in your area, we might be able to run it (depending on what other commitments we have). We would require our air travel and basic accomodation to be paid for, and if you're feeling generous, a donation towards our research costs would be appreciated.
+}
-#######################################################################
-package supportform
-_tsupportformintro_ {
-To send a query to the Greenstone support staff, please fill in the form
-below and click the "Submit Query" button to submit the query. Please fill in
-the form as fully as possible to aid our staff in giving the best possible
-service.
+}
-_t113_ {PERSONAL INFORMATION}
-_t114_ {Name}
-_t115_ {E-mail address}
-_t116_ {SYSTEM INFORMATION}
-_t117_ {Operating System}
-_t118_ {Windows 95}
-_t119_ {Windows 98}
-_t120_ {Windows ME}
-_t121_ {Windows NT 4}
-_t122_ {Windows 2000}
-_t123_ {Windows XP}
-_t124_ {Windows 3.11}
-_t125_ {Windows 3.1}
-_t126_ {Linux}
-_t127_ {Other (please specify below)}
-_t128_ {Other OS}
-_t129_ {CPU (type and speed)}
-_t130_ {Memory (RAM) in MB}
-_t131_ {Web browser}
-_t132_ {Netscape 4}
-_t133_ {Netscape 4.5}
-_t134_ {Netscape 6}
-_t135_ {Mozilla}
-_t136_ {Internet Explorer 4}
-_t137_ {Internet Explorer 5}
-_t138_ {Internet Explorer 6}
-_t139_ {Other web browser}
-_t140_ {Was your browser provided by your internet service provider?}
-_t141_ {no}
-_t142_ {yes}
-_t143_ {don't know}
-_t144_ {Is your browser configured to use a proxy?}
-_t145_ {Web server}
-_t146_ {not applicable}
-_t147_ {Apache 1.3}
-_t148_ {Apache 2.0}
-_t149_ {Microsoft IIS 4.0}
-_t150_ {Microsoft IIS 5.0}
-_t151_ {Microsoft PWS}
-_t152_ {Other server}
-_t153_ {GREENSTONE INFORMATION}
-_t154_ {Version}
-_t155_ {CD-ROM distribution}
-_t156_ {Installation type}
-_t157_ {local library}
-_t158_ {web library}
-_t159_ {PROBLEM DESCRIPTION}
-_t160_ {Problem type}
-_t161_ {question}
-_t162_ {problem/error}
-_t163_ {suggested enhancement}
-_t164_ {other}
-_t165_ {Can the problem be reproduced at will?}
-_t166_ {Short description}
-_t167_ {Long description}
-_t168_ {
-(If you are reporting a problem, please go into as much detail as possible.
-Make sure you describe all steps leading up to the problem and include any
-relevant URLs.)
+}
-#######################################################################
-package faq
-_greenstonefaq_ {Greenstone FAQ}
-_headinggeneral_ {General Information}
-_t171_ {What is Greenstone?}
-_t172_ {How is Greenstone licensed?}
-_t173_ {What platforms will Greenstone run on?}
-_t174_ {Are there any mailing lists concerned with Greenstone?}
-_t175_ {Are the mailing lists archived anywhere?}
-_t176_ {How do I contribute to Greenstone?}
-_headingobtaining_ {Obtaining Greenstone}
-_t178_ {Where do I get Greenstone from?}
-_t179_ {Are there binary distributions of Greenstone available?}
-_t180_ {Is Greenstone available on CD-ROM?}
-_t181_ {Is the Greenstone source code available via CVS?}
-_headinginstalling_ {Installing Greenstone}
-_t183_ {How do I compile Greenstone from a source or CVS distribution?}
-_t184_ {What is the difference between Greenstone's <i>local library</i> and <i>web library</i>?}
-_tfaqgliapplettitle_ {How do I install the Greenstone Librarian Interface as an applet?}
-_headingrunning_ {Running Greenstone}
-_t186_ {OK, I've installed Greenstone. Now how do I make it go?}
-_t187_ {What web browser do I need to view Greenstone collections?}
-_t188_ {When I start the Windows local library there are two buttons in the
-dialog box, "Enter Library" and "Restricted
-Version". They both seem to do the same thing, what's the difference?}
-_t189_ {So when should I use the "Restricted Version" of the local library?}
-_t190_ {When I start the Windows local library my computer asks me to dial
-up my Internet Service Provider. Do I really need to be online to run
-Greenstone?}
-_t191_ {I'm trying to use the Windows local library. My web browser is
-starting up as expected but the Greenstone home page never gets loaded or gives an error message. What's wrong?}
-_t192_ {Where can I get more Greenstone collections?}
-_t193_ {When I attempt to access certain parts of Greenstone I'm asked for
-a username and password. What do I enter?}
-_t194_ {When I use the <i>large query box</i> function I occassionally get
-a <i>Not Found</i> error.}
-_headingbuilding_ {Building Greenstone Collections}
-_tfaqbuildglititle_ {What is the "Greenstone Librarian Interface"?}
-_t196_ {What is "the Collector"?}
-_t197_ {How do I build a collection from the command line or DOS prompt?}
-_t198_ {I built a new Greenstone collection on my Windows
-machine. Everything appeared to work fine while building, however when I
-tried to view the collection some of the documents contained no
-text. Sometimes Greenstone appeared to crash completely. What have I done
-wrong?}
-_t199_ {Why won't the Collector's "export to CD-ROM" function work?}
-_t200_ {I'm trying to use the Collector on Windows 2000 but it's running
-extremely slowly. Is this normal?}
-_t201_ {What is "the Organizer"?}
-_t202_ {Where do I get the Organizer?}
-_t203_ {I'm attempting to build a collection with the collector but it
-keeps failing with an error. What am I doing wrong?}
-_t204_ {Where can I find some example collect.cfg configuration files?}
-_t205_ {How can I build my collection using MGPP?}
-_tfaqbuild11title_ {I've added a new type of classification to my collection. How do I create and add the navigation bar images?}
-_tfaqbuildexpattitle_ {How do I fix XML::Parser errors during import.pl?}
-_tfaqbuildsizelimittitle_ {Are there any limits to the size of collections?}
-_headingplugins_ {More About Plugins}
-_tfaqplugins0title_ {Does Greenstone have a plugin for my data format?}
-_tfaqplugins1title_ {What metadata is available for each plugin?}
-_tfaqplugins2title_ {I'm having problems with my PDF files! What's wrong?}
-_tfaqplugins3title_ {How do I use UnknownPlug to handle my new format?}
-_headingcustomize_ {Customizing Your Greenstone Library}
-_tfaqcustomizefrontpagelogotitle_ {How do I change the logo on the front page of my library ("greenstone digital library software")?}
-_tfaqcustomizemoreinfotitle_ {Where can I get more information about customizing my Greenstone library?}
-_tfaqcustomizeformattitle_ {What are the formatting options available for my collection?}
-_tfaqcustomizemetadatalinkingtitle_ {How can I hyperlink individual metadata elements?}
-_t207_ {FAQ Main Page}
-_t372_ {Show entire FAQ on a single page}
-_t373_ {Show FAQ on multiple pages}
-#######################################################################
-package faqgen
-_t208_ {
-Greenstone is a suite of software which has the ability to serve digital
-library collections and build new collections. It provides a new way of
-organizing information and publishing it on the Internet or on CD-ROM.
-For more information, read the <a href="_httppagex_(factsheet)">Greenstone Fact Sheet</a>.}
-_t209_ {
-Greenstone is open-source software, distributed under the terms of the <a
-href="http://www.gnu.org/copyleft/gpl.html">GNU General Public License</a>.
+}
-_t210_ {
-Greenstone has been tested on Windows 3.1/3.11/95/98/Me/NT/2000, most
-distributions of GNU/Linux, Darwin (Mac OS X), Solaris, and FreeBSD.  It
-should in fact work on any Windows or Unix system. If you use a system
-other than those mentioned and you find Greenstone doesn't run, please <a
-href="_httppagex_(support)">contact</a> us.
-<p>Please note that the downloadable Windows distribution of Greenstone
-comes with an installer that will not work on 16 bit Windows. If you need
-to use Greenstone on Windows 3.1/3.11 please <a
-href="_httppagex_(support)">contact</a> us.</p>
+}
-_t211_ {
-There are two Greenstone mailing lists. You can subscribe to them from the
-<a href="_httppagex_(docs)#mailing-lists">documentation</a> page.
+}
-_t212_ {
-The most popular mailing list ([email protected]) is
-archived as a Greenstone collection at <a
-href="http://www.nzdl.org/cgi-bin/library?a=p&p=about&c=gsarch">www.nzdl.org</a>.
-Note that this collection is updated only sporadically so may not always be
-completely up to date.
+}
-_t213_ {
-We welcome contributions or improvements to the Greenstone software!
-<br />Before you send in any contribution, you first need to make sure that
-your changes are compatible with the latest snapshop of the Greenstone
-source code. To get the latest code you'll need to use CVS (see <a
-href="_httppagex_(cvs)">here</a> for details).
-<br />You should then send the modified files, along with details of the
-modifications you've made, to <a
-href="mailto:[email protected]">[email protected]</a>.
-<p>Before beginning work, you should announce what you're doing on the <a
-href="mailto:[email protected]">greenstone developer's list</a>
-to tell us what you plan to do and get some feedback.</p>
+}
-#######################################################################
-package faqob
-_t215_ {
-From the greenstone.org <a href="_httppagex_(download)">download</a> page.
+}
-_t216_ {
-Yes. At present there are binary distributions for 32 bit Windows, PowerPC
-Mac OS X, and i386 linux. They can be downloaded from the <a
-href="_httppagex_(download)">download</a> page.
+}
-_t217_ {
-While some version 2.37 and 2.38 CD-ROMs have been produced they're not
-currently being made widely available. You are encouraged to download the
-latest release of Greenstone from the <a
-href="_httppagex_(download)">download</a> page. If your internet connection
-is such that downloading Greenstone isn't possible please <a
-href="_httppagex_(support)">contact</a> us and we may be able to arrange
-for a CD-ROM to be sent out.
+}
-_t218_ {
-Yes, see our <a href="_httppagex_(cvs)">CVS page</a> for details.
+}
-#######################################################################
-package faqinst
-_t220_ {
-See our <a href="_httpdocsdir_/compiling.html">compiling page</a>.
+}
-_t221_ {
-Firstly, the <i>local library</i> is only available if you're running
-Greenstone under Windows. It's not yet available on Unix.
-<p>The major difference between the two is that the <i>local library</i>
-contains it's own built-in webserver. The <i>web library</i> however,
-requires an external webserver like Apache or Microsoft IIS. This makes the
-<i>local library</i> much easier to install and configure than the web
-library.</p>
-<p>For this reason, it's recommended that Windows users install the
-<i>local library</i> unless they're sure that they need the <i>web
-library</i>. Even if you think you might need the <i>web library</i>, try
-installing the <i>local library</i> first. You can always uninstall it
-later and install the <i>web library</i> if you then decide you need
-it.</p>
-<p>A situation where the <i>web library</i> may be preferable is if you
-plan to serve your Greenstone collections as a full-time service on the
-web. In this case you'll probably want the added stability that running the
-<i>web library</i> in conjunction with an external webserver can
-provide.</p>
-<p>Please note that the <i>local library</i> is quite capable of serving
-Greenstone collections over a local area network or the web (despite its
-rather misleading name).</p>
+}
-_tfaqgliapplet_ {
-<p>To get the GLI applet running, please do the following:
-<ol>
-<li>Install Greenstone and the GLI on your server computer. Currently, this must be a GNU/Linux or Unix machine.</li>
-<li>Set up your web server (eg. Apache) for Greenstone. Check that standard Greenstone works.</li>
-<li>The following four steps require the Java SDK. If you don't already have this it is available for download from <a href="http://java.sun.com/j2se/1.4.2/download.html">http://java.sun.com/j2se/1.4.2/download.html</a>.
-<li>In the gsdl/gli directory, run
-    <br><small><tt>keytool -genkey -alias privateKey -keystore appletstore -storepass greenstone</tt></small><br>
-  Enter the appropriate details for your organization. When it asks to enter the key password for &lt;privateKey&gt;, choose your own password or hit Enter to use "greenstone".</li>
-<li>Run makegli.sh.</li>
-<li>Run makejar.sh.</li>
-<li>Run
-    <br><small><tt>jarsigner -keystore appletstore -signedjar SignedGatherer.jar GLI.jar privateKey</tt></small><br>
-  When it prompts, enter the password you used above.</li>
-<li>Move the SignedGatherer.jar file created into the gsdl/bin/java directory.</li>
-<li>Edit the gsdl/etc/main.cfg file and set the "gliapplet" field to "enabled".</li>
-<li>Visit your Greenstone homepage and click "The Librarian Interface" button. The applet should load and appear on this page, producing a button that says "Launch Greenstone Librarian Interface...". Clicking this will run the GLI as an applet, allowing users to build collections on your server without having Greenstone installed on their machines.</li>
-</ol>
-<p>Note that the applet transfers a lot of data between the machine it is running on and the server. This makes using the GLI applet impractical if you don't have a high speed connection between your machine and the server.
-</p>
+}
-#######################################################################
-package faqrun
-_t223_ {
-If you're using the Windows <i>local library</i> you should be able to
-simply select "Greenstone Digital Library" from within the
-programs in your <i>start</i> menu.
-<p>If you're using the <i>web library</i> things are a little less obvious
-however. First make sure your webserver is configured correctly and is
-running (see the <a href="_httppagex_(docs)">Greenstone Installer's
-Guide</a> and your webserver's documentation for details). You can then
-simply open your web browser and point it at the URL of Greenstone's
-library executable. This is dependant on the way you configured Greenstone
-and your webserver. Typically it might be something like
-http://localhost/gsdl/cgi-bin/library.exe.</p>
+}
-_t224_ {
-Greenstone relies on a web browser that supports tables, javascript, and in
-some places, frames. Any reasonably modern browser will do. Examples are
-Microsoft Internet Explorer 4, Netscape 4, and Mozilla. Newer releases of
-all these browsers will also work.
-<p>If you find that your favourite web browser does not work with
-Greenstone, please <a href="_httppagex_(support)">contact us</a>.</p>
-<p>Note that there is an exception to the rule that any modern browser will
-do when running Greenstone. That is when you're using the restricted
-version of the Windows local library when you must use Netscape. See the
-discussion below on the differences between the "Restricted
-Version" and the standard "Enter Library" version of the
-local library for details.</p>
+}
-_t225_ {
-The webserver built into the local library uses the networking software
-built into your Windows operating system in order to function. If your
-computer has never been connected to a network this networking software may
-not be installed however. For this reason Greenstone comes with some
-networking software of it's own that it will use if it can't find any
-installed on your computer.
-<p>When you click the "Enter Library" button, Greenstone first
-checks to see if your computer has it's own networking software. If it
-does, it starts up using that, if not it starts up using it's own
-networking software.</p>
-<p>When you click the "Restricted Version" button, Greenstone
-doesn't bother checking your system for networking software, it just goes
-ahead and uses it's own.</p>
-<p>The catch is that there are several limitations with using the
-Greenstone supplied networking software. The most important limitations are
-that the local library won't be accessible from the network if run in this
-way (that is, it really will be "local" to the machine on which
-it's running) and that it must use a Netscape web browser. Using your
-computer's built-in networking software is therefore the prefered
-option.</p>
+}
-_t226_ {
-Since Greenstone will automatically use it's own networking software if it
-can't find any installed on your computer it should not normally be
-necessary to run the "Restricted Version" explicitly.
-<p>Times when it may be necessary are.</p>
-<ul>
-<li>If your computer's networking software has been installed incorrectly.</li>
-<li>If Windows keeps attempting to dial up your internet service provider
-when you click the "Enter Library" button.</li>
-</ul>
+}
-_t227_ {
-No you don't need to be online. This is caused by the webserver built into
-Greenstone's local library sending a message to your computer's networking
-software to make sure it's functioning correctly. On many Windows systems
-this causes the familiar dial up dialog box to appear. In most situations
-you can simply cancel the dialog box and (if required) press your browser's
-<i>reload</i> button to continue.
-<p>If this does not solve the problem, try starting the local library by
-clicking the "Restricted Version" button rather than the
-"Enter Library" button. See the discussion above on the
-differences between the standard and restricted versions of the local
-library for further details.</p>
+}
-_t228_ {
-<ol>
-<li>Check your web browser's internet proxy settings and turn proxies off (use
-<i>Edit preferences</i> on Netscape or <i>Internet options</i> on
-Explorer).</li>
-<li>If Internet Explorer gives a message saying "The page cannot be
-displayed" and "Cannot find server or DNS error" at the bottom of the
-page, check in your network settings that your computer's name is set
-up correctly. For example, if there is a DNS suffix entered in your
-TCP/IP properties (in the Control Panel), make sure that your host
-name and suffix are correct for your computer. If the server is running
-correctly, you should be able to connect by visiting
-<a href="http://127.0.0.1/">http://127.0.0.1/</a> in a web browser on the
-same machine that the local library is running on.</li>
-</ol>
+}
-_t229_ {
-Collections like those at <a href="http://www.nzdl.org">www.nzdl.org</a>
-will soon be made available for download.
+}
-_t230_ {
-The initial username required here is <i>admin</i>.
-<p>If you installed Greenstone using the InstallShield installer on Windows
-or the Install.sh script on Unix you should have been asked to set a
-password during the installation procedure.</p>
-<p>If you didn't, don't worry, the password defaults to being
-<i>admin</i>.</p>
-<p>So if you don't know what to enter you should try username =
-<i>admin</i>, password = <i>admin</i>.<p>
+}
-_t231_ {
-This may be caused by the URL becoming too long for your web
-browser. Because Greenstone currently stores all state information in the
-URL, if you do a search for a long phrase the URL can become very
-long. Different browser's on different platforms have different maximum URL
-lengths but in general it seems that Netscape can handle longer URLs than
-can Microsoft Internet Explorer.
-<p>There is very little you can do to avoid this problem with the way
-Greenstone is currently implemented (aside from not searching for long
-phrases). Future versions of Greenstone may store some state information on
-the server rather than in the URL but this has yet to be implemented.</p>
+}
-#######################################################################
-package faqbuild
-_tfaqbuildglibody_ {
-The Greenstone Librarian Interface (GLI) is a graphical tool for building new
-collections, altering or
-deleting existing collections, and exporting existing collections to
-stand-alone CD-ROMs. It allows you to import or assign metadata, and
-has an interactive collection design module. Launch the GLI under Windows
-by selecting <i>Greenstone Digital Library</i> from the <i>Programs</i>
-section of the <i>Start</i> menu and choosing <i>Librarian Interface</i>.
-Under Linux, run <i>gli.sh</i> from the <i>gsdl/gli</i> directory.
-For details on using the Librarian Interface see the
-<a href="_httppagex_(docs)">Greenstone User's Guide</a>.
+}
-_t233_ {
-The Collector is a web interface for collection building, altering and
-exporting. It predates the Librarian Interface and for most
-practical purposes, the Librarian Interface should be used instead.
-To begin using the Collector, click the "The
-Collector" button on your Greenstone home page. For further details on
-using the Collector see the <a href="_httppagex_(docs)">Greenstone User's
-Guide</a>.
+}
-_t234_ {
-It's occasionally preferable to build your Greenstone collections from the
-command line rather than from the Collector. This allows you greater
-control over how your new collection turns out. See the <a
-href="_httppagex_(docs)">Greenstone Developer's Guide</a> for detailed step
-by step instructions on building collections from the command line.
+}
-_t235_ {
-Are you running Norton Anti-Virus? There are some incompatibilities between
-Norton and the Greenstone collection building process that cause
-unpredictable things to happen if you build your collection while Norton is
-running. Try disabling Norton and rebuilding the collection.
-<p>If you do not have Norton or disabling Norton does not solve the problem
-please <a href="_httppagex_(support)">contact us</a> for further help.</p>
+}
-_t236_ {
-If you downloaded Greenstone from the web you will not have all the
-components required to make the "export to CD-ROM" function
-work. These extra components have been made available in a separate
-download which you can get from the <a
-href="_httppagex_(download)#packages">download</a> page.
+}
-_t237_ {
-Are you using a Netscape web browser with the local library? If so, try
-using Internet Explorer instead. There are some socket connection problems
-that show up on Windows 2000 when using Netscape.
+}
-_t238_ {
-The Organizer (also called the "Collection Organizer") is a
-Windows utility used for automatically generating some of the configuration
-files (metadata.xml, sub.txt etc.) used by complex Greenstone collections.
+}
-_t239_ {
-From the <a href="_httppagex_(download)#utilities">download</a> page.
+}
-_t240_ {
-There are several reasons that the collector might fail to build a
-collection and the error messages it produces are not always very helpful.
-<p>If you changed the default configuration during the <i>configure
-collection</i> stage you'll need to make sure the changes were valid. For
-example, if you added a new <i>classify</i> or <i>plugin</i> line you'll
-need to make sure that the classifier and/or plugin names and arguments are
-all correct. If they're not the collector will fail. A good test is to
-build your collection without changing the configuration. If it builds ok
-with the default configuration but fails after you change the configuration
-you'll need to look closely at the changes you're making.</p>
-<p>Another good thing to do if having problems with the collector is to
-build your collection from the command line instead. You'll get much more
-feedback to help debug problems when building in this way. For details on
-how to build a collection from the command line see the <a
-href="_httppagex_(docs)">Greenstone developer's guide</a>.</p>
+}
-_t241_ {
-The collect.cfg files for many of the collections at <a
-href="http://www.nzdl.org">www.nzdl.org</a> have been made available <a
-href="_httppagex_(colcfg)">here</a>.
+}
-_t242_ {
-The <a href="_httpdocsdir_/mgpp_user.pdf">MGPP user manual</a> gives some
-instructions.
+}
-_tfaqbuild11body_ {
-Visit <a href="http://www.cs.waikato.ac.nz/~mdewsnip/greenstone/make-images.html">this page</a> and follow the instructions.
+}
-_tfaqbuildexpatbody_ {
-Our prebuilt Linux and Mac OS X Greenstone distributions are built on machines using Perl 5.6, and these distributions contain a few binary perl modules. These cause problems if you are using a recent version of perl like 5.8 or 5.8.1 (you can type "perl -v" from the command line to see the version).
-<p>
-On the Mac, our distribution contains modules for both perl 5.6 and 5.8 and the correct one should (hopefully) be installed.
-<p>
-A typical error message during import.pl would be:
-<p>
-Uncaught exception from user code: Can't load '/home/httpd/gsdl/perllib/cpan/auto/XML/Parser/Expat/Expat.so' for module XML::Parser::Expat: /home/httpd/gsdl/perllib/cpan/auto/XML/Parser/Expat/Expat.so: undefined symbol: PL_sv_undef at /usr/lib/perl5/5.8.0/i386-linux-thread-multi/DynaLoader.pm line 229. at /home/httpd/gsdl/perllib/cpan/XML/Parser.pm line 14
-<p>
-To remedy this, you need to remove the "gsdl/perllib/cpan/XML" and "gsdl/perllib/cpan/auto" directories. (For version 2.52, remove gsdl/perllib/cpan/perl-5.8/XML and gsdl/perllib/cpan/perl-5.8/auto.) Then you need to install the perl XML::Parser natively for your system.
-<p>
-On redhat or mandrake, install the .rpm named "perl-XML-Parser", on debian, install the "libxml-parser-perl" package. For other Linuxes, use your distribution's package, or you can get it from <a href="http://search.cpan.org/~msergeant/XML-Parser-2.34/">http://search.cpan.org/~msergeant/XML-Parser-2.34/</a>.
-<p>
-You may also need to get Expat, available from <a href="http://sourceforge.net/projects/expat/">http://sourceforge.net/projects/expat/</a>.
+}
-_tfaqbuildsizelimitbody_ {
-The largest collections we have built have been 7 Gb of text, and 11 million short documents (about 3 Gb text). These built with no problems. We haven't tried larger amounts of text because we don't have larger amounts of
-text lying around.  It's no good using 7 Gb twice over to make 14 Gb because the vocabulary hasn't grown accordingly, as it would
-with a real collection.
-<p>
-There are three main limitations:
-<ol>
-<li>There is a file size limit of 2 Gb on Linux (soon to be increased to
-    infinity, the Linux people say).  I don't know about corresponding
-    figures for Windows; we use Linux for development.  There are systems
-    that go higher, but we don't have access to them.<br>
-    The compressed text will hit the limit first.  MG stores the compressed
-    text in a single file.  7 Gb will compress to just under 2 Gb, so you
-    can't go much higher without splitting the compressed-text file (hacky,
-    but probably easy).
-</li>
-<li>    Technical.  There is a Huffman coding limitation which we would expect
-    to run into at collections of around 16 Gb.  However, the solution is
-    very easy, we just haven't bothered to implement it until we have
-    encountered the problem.
-</li>
-<li>
-Build time.  For building a single index on an already-imported
-    collection, extrapolations indicate that on a modern machine with 1 Gb
-    of main memory, you should be able to build a 60 Gb collection in about
-days.  However, there are often large gaps
-    between theory and practice in this area!  The more indexes you have,
-    the longer things take to build.
-</li>
-</ol>
-In practice, the solution for very large amounts of data is not to treat the collection
-as one huge monolith, but to partition it into subcollections and arrange for
-the search engine to search them all together behind the scenes. However, while
-you can amalgamate the results of searching subcollections fairly easily, it's
-much harder with browsing.  Of course, A-Z lists and datelists and the like
-aren't really much use with very large collections.
-This is where new techniques of hierarchical phrase browsing come into their
-own.  And the really good news is that you can partition a collection into
-subcollections, each with individual phrase browsers, and arrange to view them
-all together in a single hierarchical browsing structure, as one coordinated
-whole.  We haven't actually demonstrated this yet, but it seems quite feasible.
-<p>
-A test collection was built by "Archivo Digital", an office
-that depends on the "Archivo Nacional de la Memoria" (National Memory
-Archive in English), in Argentina. It contained sequences of page images with
-associated OCR text.
-<p/><i>Setup details</i>
-<ul>
-<li>Greenstone version: 2.52</li>
-<li>Server: Pentium IV 1.8 GHz, 512 Mb RAM, Windows XP Prof.</li>
-<li>Number of indexed documents: 17,655</li>
-<li>Number of images (tiff format): 980,000</li>
-<li>Total size of text files: 3.2 Gb</li>
-<li>Built indexes: section:text document:Title</li>
-<li>Used Plugin: PagedImgPlug</li>
-<li>5 classifiers</li>
-</ul>
-<p/><i>Statistics</i>
-<ul>
-<li>Time to import the collection: Almost a week was spent collecting documents and importing them. No image conversion was done.</li>
-<li>Time to build the collection (excluding import): almost 24 hours. The archives and the indexes were on  separate hard disks, to reduce the overhead that reading and writing from the same disk would cause.</li>
-<li>Time to open a hierarchy node that contains 908 objects: 23 seconds</li>
-<li>Average Time to search only one word in text index: 2 to 5 seconds</li>
-<li>Average Time to search 3 words in text index: 2 to 5 seconds</li>
-<li>Average Time to search exact phrases (includes 4, 5 and 6 words): 30 seconds</li></ul>
+}
-#######################################################################
-package faqplugins
-_available_ {
-See <a href="_gwcgi_?a=p&p=plugins">this page</a>.
+}
-# base puts in surrounding <p> and </p>, so skip first and last ones
+#
-_metadata_ {
-"Default" means that the metadata fields will be automatically assigned (or
-extracted if possible), while the "Available fields" lists other items
-of metadata that the plugin may be able to assign based on any arguments
-given to that plugin in the <tt>collect.cfg</tt> file.
-All plugins are derived from BasPlug, and have following metadata fields:
-<table border="1">
-<tr>
-  <th>  </th>
-  <th> Default fields </th>
-  <th> Available fields </th>
-</tr>
-<tr>
-  <td> BasPlug </td>
-  <td> Language, Encoding, Source </td>
-  <td> FirstNNNN, Keyphrases, Acronym </td>
-</tr>
-</table>
-</p>
-<p>
-In addition, many plugins have additional fields available:
-<table border="1">
-<tr>
-  <th> Plugin name </th>
-  <th> Default fields </th>
-  <th> Available fields </th>
-</tr>
-<tr>
-  <td> BibTexPlug </td>
-  <td> Title, Creator, Abstract, Author, Booktitle, Chapter, Copyright, Date,
-       Edition, Editor, EntryType Journal, Keywords, Month, Note, Number,
-       Pages, Publisher, PublisherAddress, Volume, Year </td>
-  <td>&nbsp;</td>
-</tr>
-<tr>
-  <td> DBPlug </td>
-  <td>&nbsp;</td>
-  <td> (arbitrary metadata field names based on Database configuration file)
-  </td>
-</tr>
-<tr>
-  <td> EMAILPlug </td>
-  <td>  Date, DateText, From, FromAddr, FromName, Headers, Subject,
-        Title (based on subject, from, and date), To
- </td>
-  <td>&nbsp;</td>
-</tr>
-<tr>
-  <td> ExcelPlug </td>
-  <td>&nbsp;</td>
-  <td> (all fields as in HTMLPlug) </td>
-</tr>
-<tr>
-  <td> HTMLPlug </td>
-  <td> Title, URL </td>
-  <td> Author, Creator, Email (others as found in the <tt>-metadata_fields</tt> option) </td>
-</tr>
-<tr>
-  <td> ImagePlug </td>
-  <td> Image, ImageHeight, ImageSize, ImageType, ImageWidth, ScreenHeight,
-        screenicon, ScreenSize, ScreenType, ScreenWidth, Source, srclink,
-        srcicon, Thumb, ThumbHeight, ThumbType, ThumbWidth </td>
-  <td>&nbsp;</td>
-</tr>
-<tr>
-  <td> IndexPlug </td>
-  <td> as in the <tt>index.txt</tt> file </td>
-  <td> (use metadata.xml files instead of using this plugin) </td>
-</tr>
-<tr>
-  <td> MARCPlug </td>
-  <td> Creator, Description, MarcIdentifier, MarcSource, URL, Publisher,
-       Relation, Rights, Subject, Title, Type </td>
-  <td> (Metadata fields as in the <tt>marctodc.txt</tt> file) </td>
-</tr>
-<tr>
-  <td> OAIPlug </td>
-  <td> URL, (all metadata in <tt>.oai</tt> markup file) </td>
-  <td>&nbsp;</td>
-</tr>
-<tr>
-  <td> PagedImgPlug </td>
-  <td> Image, ImageHeight, ImageSize, ImageType, ImageWidth, ScreenHeight,
-        screenicon, ScreenSize, ScreenType, ScreenWidth, Source, srclink,
-        srcicon, Thumb, ThumbHeight, ThumbType, ThumbWidth </td>
-  <td>&nbsp;</td>
-</tr>
-<tr>
-  <td> PDFPlug </td>
-  <td>&nbsp;</td>
-  <td> (all fields in HTMLPlug) </td>
-</tr>
-<tr>
-  <td> PPTPlug </td>
-  <td>&nbsp;</td>
-  <td> (all fields in HTMLPlug) </td>
-</tr>
-<tr>
-  <td> PSPlug </td>
-  <td> Title </td>
-  <td> Date, Pages, (all fields in TextPlug) </td>
-</tr>
-<tr>
-  <td> ReferPlug </td>
-  <td> Abstract, BookConfOnly, Booktitle, Copyright, Creator, Date, Editor,
-       Keywords, Journal, JournalsOnly, Number, Pages, Publisher,
-       Publisheraddr, Report, Title, Volume  </td>
-  <td>&nbsp;</td>
-</tr>
-<tr>
-  <td> RTFPlug </td>
-  <td>&nbsp;</td>
-  <td> (all fields in HTMLPlug) </td>
-</tr>
-<tr>
-  <td> SRCPlug </td>
-  <td> Title, filename, includes, class, classdecl </td>
-  <td>&nbsp;</td>
-</tr>
-<tr>
-  <td> TEXTPlug </td>
-  <td> Title </td>
-  <td>&nbsp;</td>
-</tr>
-<tr>
-  <td> UnknownPlug </td>
-  <td> (as given in the <tt>-assoc_field</tt> plugin argument) </td>
-  <td>&nbsp;</td>
-</tr>
-<tr>
-  <td> WordPlug </td>
-  <td>&nbsp;</td>
-  <td> (all fields in HTMLPlug) </td>
-</tr>
-</table>
-</p>
-<p>See section two of the _docs:developersguide_ for information about
-options to plugins, or run the <tt>pluginfo.pl</tt> command on the
-plugin name after setting up your environment for Greenstone.
-(For example, "<tt>perl&nbsp;-S&nbsp;pluginfo.pl&nbsp;BasPlug</tt>".)
-</p>
-<p>
-In addition, every document can be manually assigned arbitrary metadata
-fields and values through use of <tt>metadata.xml</tt> files, as discussed
-in the manual.
+}
-# base puts in surrounding <p> and </p>, so skip first and last ones
+#
-_pdfproblems_ {
-PDF is a "page description language". This means that the document contains
-objects and commands such as "draw this text here" and "draw this
-image here".
-</p>
-<p>
-Greenstone uses an external program called "<tt>pdftohtml</tt>" to
-extract text out of PDF files. Sometimes, there is no text that can be
-extracted. This often depends on how the PDF was created.
-<ol>
-<li>Adobe Acrobat Writer can be used to create PDFs from paper
-documents that are scanned in by a scanner. In this case, the PDF file
-contains images of text, rather than computer-readable text. Therefore,
-<tt>pdftohtml</tt> cannot find any text to extract.</li>
-<li>Some programs (such as older versions of <tt>GNU ghostscript</tt>,
-which is used by <tt>ps2pdf</tt> on Unix computers) sometimes create
-"bitmap fonts", which means that every character in the document is
-really an image rather than a computer readable letter. The
-<tt>LaTeX</tt> type-setting program sometimes does this when the
-"Computer Modern Roman" font is used.</li>
-<li>Certain characters and character combinations may be extracted incorrectly,
-depending on the program that generated the PDF file. For example, "ligatures"
-such as "fi", "fl", "ff" and "ffl" are often rendered using a special glyph
-rather than as individual characters, and this information may be lost in
-the textual representation. Also, some PDF generating programs may not
-correctly encode accented characters. For example, to draw a lowercase "u"
-with an umlaut accent, LaTeX draws a "u" and then draws an umlaut accent over
-it. This means that <tt>pdftohtml</tt> will extract two separate characters
-('Âš' and 'u') rather than a single accented character (ÃŒ).</li>
-<li>PDF contains pieces of text, and coordinates for where that text
-should be displayed. This means that <tt>pdftohtml</tt> may
-incorrectly guess the order that the text fragments are supposed to
-occur in. For example, for text that is in two or more columns, the text
-may be extracted as the first sentence of each column, then the second
-sentence of each column, and so on. In this case, the extracted text
-is still usable for indexing purposes, but should not be displayed.
-In this case, a format statement should be added to the <tt>collect.cfg</tt>
-file to provide a link to the original PDF file but not to the extracted
-text, such as:
-<center>
-<small><tt>format SearchVList "&lt;td valign=top&gt;[srclink][srcicon][/srclink]&lt;/td&gt; &lt;td&gt;[srclink][Title][/srclink]&lt;/td&gt;"</tt></small>
-</center>
-</li>
-<li>Because of the way that images are embedded in PDF files,
-<tt>pdftohtml</tt> occasionally extracts an image upside-down, or mirrored.
-This appears to be a bug in the program.</li>
-</ol>
+}
-_unknownplug_ {UnknownPlug is a simple plugin for importing files in formats
-that Greenstone doesn't know anything about.  A dummy document will be
-created for every such file, and the file itself will be passed to Greenstone
-as the \"associated file\" of the document.
-<p>
-Here's an example where it is useful: A collection has pictures and includes
-a couple of quicktime movie files with names like DCP_0163.MOV.
-Rather than write a new plugin for quicktime movies, add this line to the
-collection configuration file:
-<center>
-<small><tt>plugin UnknownPlug -process_exp "*.MOV" -assoc_field "movie"</tt></small></center>
-<p>
-A document is created for each movie, with the associated movie
-file's name in the "movie" metadata field.  In the collection's
-format strings, use the \{If\} macro to output different text for
-each type of file, like this:
-<center>
-<small><tt> \{If\}\{[movie],&lt;HTML for displaying movie&gt;\}<br>
-\{If\}\{[Image],&lt;HTML for displaying image&gt;\}</tt></small></center>
-<p>
- You can also add extra metadata, such as the Title, Subject, and
- Duration, using the Librarian Interface (or with metadata.xml files and RecPlug).
-<p>
-The <tt>-process_exp</tt> option is a regular expression that matches filenames which should be processed by UnknownPlug. You can have several UnknownPlugs specified
-for a collection, each processing a different kind of file.
-<p>
-The <tt>-assoc_field</tt> option is the name of the metadata field that will hold the
-associated file's name. This can be used to test for these files. You can also specify the mime type of the files to
-be processed using the <tt>-mime_type</tt> option. To display the original file, use <tt>[srclink][/srclink]</tt> metadata.
+}
-#######################################################################
-package faqcustomize
-_tfaqcustomizefrontpagelogo_ {
-You can change the logo that appears at the top of the front page of your library by editing the <tt>home.dm</tt> file in your Greenstone "macros" folder and replacing all instances of "gsdlhead.gif" with the name of your logo image file.
+}
-_tfaqcustomizemoreinfo_ {
-Try <a href="_httppagex_(docs)#user_supplied">this document</a>.
+}
-_tfaqcustomizeformat_ {
-Section 2.3 of the <a href="_httppagex_(docs)">Greenstone Developer's Guide</a> discusses how to format the output of your collection. However, the list of options is incomplete. The full list of formatting options is shown here. But for more information about how to use these options, the developer's guide is the place to go.
-<p>
-<i><u>Site-wide formatting options</u></i><br>
-These should be placed in gsdl/etc/main.cfg. <br>
-Syntax: <b>SiteFormat &lt;option-name&gt; &lt;option-value&gt;</b>
-<p>
-<table class="faq-table"><tr><th width=180>Item</th><th>Description</th></tr>
-<tr><td>HomePageCols int</td><td>Set the number of columns used to display collections on the home page.<br>Default: 3</td></tr>
-<tr><td>HomePageType pulldown</td><td>Display the collection list on the home page as a pulldown menu, rather than using the default table of collection images. This alters the html that appears in the dynamically generated _homeextra_ macro. You can then move this macro around in home.dm.<br>Default: not set</td></tr>
-</table>
-<p>
-<i><u>Collection-specific formatting options</u></i><br>
-These should be placed in gsdl/collect/&lt;collname&gt;/etc/collect.cfg. <br>
-Syntax: <b>format &lt;option-name&gt; &lt;option-value&gt;</b>
-<p>
-<table class="faq-table">
-<tr><th width=220>Item</th><th>Description</th></tr>
-<tr><td>DocumentImages true/false</td><td>If true, display a cover image at the top left of the document page<br>Default: false</td></tr>
-<tr><td>DocumentTitles true/false</td><td>If DocumentImages is false, and this is true, use DocumentHeading to display the title.<br>Default: true</td></tr>
-<tr><td>DocumentHeading formatstring</td><td>This is used for a document heading at the top left if DocumentImages is false and DocumentTitles is true.<br>Default: \{Or\}\{[parent(Top):Title],[Title],untitled\} &lt;br&gt;[Title] </td></tr>
-<tr><td>DocumentContents true/false</td><td colspan=2>Display table of contents (if document is hierarchical), or next/previous section arrows and "page k of n" text (if document is paged)<br>Default: true</td></tr>
-<tr><td>DocumentButtons string</td><td colspan=2>Controls the buttons that are displayed on a document page. Valid options are Detach, Highlight, Expand Text, Expand Contents. Should be separated by |.<br>Default: "Detach|Highlight"</td></tr>
-<tr><td>DocumentText formatstring</td><td>Format of the text to be displayed on a document page<br>Default: &lt;center&gt; &lt;table width=537&gt; &lt;tr&gt;&lt;td&gt;[Text]&lt;/td&gt;&lt;/tr&gt; &lt;/table&gt; &lt;/center&gt;</td></tr>
-<tr><td>DocumentArrowsTop true/false</td><td>Display next/previous section arrows at top of document, underneath the navigation bar, on document page<br>Default: false</td></tr>
-<tr><td>DocumentArrowsBottom true/false</td><td>Display next/previous section arrows at bottom of document page<br>Default: true</td></tr>
-<tr><td>DocumentUseHTML true/false</td><td>If true, each document is displayed in a separate frame. The Preferences page will also change slightly, adding options applicable to a collection of HTML documents.<br>Default: false</td></tr>
-<!--<tr><td>RelatedDocuments string</td><td>Don't know that this gets used<br>Default: ""</td></tr>-->
-<tr><td>NavigationBar pulldown</td><td>If set, provides a drop down list in place of the usual navigation bar (that contains search and classifier options). This alters the html that appears in the dynamically generated _navigationbar_ macro.<br>Default: not set</td></tr>
-<tr><td>AllowExtendedOptions true/false</td><td>This allows the entire content of the document page to be controlled by format statements. Use DocumentHeading and DocumentText to format the document. This option prevents the other hard coded stuff (table of contents, buttons etc) from being output. It effectively disables the DocumentContents, DocumentButtons, DocumentImages format options. New format items are provided for use in format statements if AllowExtendedOptions is true (see table below)<br>Default: false</td></tr>
-</table>
-<p>
-<i><u>Formatting Lists</u></i><br>
-The standard use of format statements is for the lists in search results, classifiers etc. Here is a list of the various lists available for format, and what they control. Note that classifiers are numbered from 1 upwards, in the order that they appear in the config file.
-<p>
-<table class="faq-table"><tr><th align=left>Item</th><th align=left>Description</th></tr>
-<tr><td>VList</td><td>Applies to all vertical lists, unless overridden by a more specific format item. These include search results, classifier lists, and table of contents</td></tr>
-<tr><td>HList</td><td>Applies to all horizontal lists. Horizontal lists are often used in classifiers, particularly AZ[Compact][Section]Lists</td></tr>
-<tr><td>DateList</td><td>Applies to all date lists - these are the vertical lists generated by a DateList classifier.</td></tr>
-<tr><td>SearchVList</td><td>The vertical list of search results</td></tr>
-<tr><td>CL1VList</td><td>Applies only to the vertical list of classifier 1</td></tr>
-<tr><td>CL1HList</td><td>Applies only to the horizontal list of classifier 1</td></tr>
-<tr><td>CL1DateList</td><td>Applies only to the DateList in classifier 1</td></tr>
-</table>
-<p>
-<i><u>Formatstring items</u></i><br>
-<p>
-<table class="faq-table"><tr><th align=left>Item</th><th align=left>Description</th></tr>
-<tr><td>[link][/link]</td><td>Link to the document (Greenstone version)</td></tr>
-<tr><td>[srclink][/srclink]</td><td>Link to the original document (only if the original was converted to another form)</td></tr>
-<tr><td>[icon]</td><td>An appropriate icon for a classifier/document node. E.g. bookshelf, book, chapter, page</td></tr>
-<tr><td>[srcicon]</td><td>An appropriate icon for the original source document. E.g. Word, PDF, PS icon.</td></tr>
-<!--<tr><td>[href]</td><td>not sure what this does and it caused a segmentation fault when I tried to use it</td></tr>-->
-<tr><td>[num]</td><td>The document number (position in the search results - useful for debugging)</td></tr>
-<tr><td>[numleafdocs]</td><td>The number of documents below the current classifier node. This is often used as a test for classifier nodes, as numleafdocs will not be set for documents. This allows different formatting for classifier nodes and document nodes in a hierarchy.</td></tr>
-<tr><td>[Text]</td><td>The text of the current section</td></tr>
-<tr><td>[RelatedDocuments]</td><td>Related Documents info (if available). This is a vertical list of Titles (or Subjects if Titles aren't available) that link to the related documents. It is based on "relation" metadata, which is a space separated list of collection,OID pairs.</td></tr>
-<tr><td>[highlight][/highlight]</td><td>These are used for 'highlighting' (actually bolding) the selected section in a hierarchical table of contents, and the selected node in a classifier. Apart from those two cases, this has no effect. If you actually want to highlight/bold/italicise something in a list, and have it apply to all items in the list, then use actual html tags, like &lt;b&gt;&lt;/b&gt;, &lt;u&gt;&lt;/u&gt; and &lt;i&gt;&lt;/i&gt;</td></tr>
-<tr><td>[Summary]</td><td>Displays Summary metadata if available, otherwise displays a short summary created on the fly.</td></tr>
-<tr><td>[DocOID]</td><td>The internal identifier of the document</td></tr>
-<tr><td>[DocRank]</td><td>The rank of the current document - used in search results</td></tr>
-<tr><td>[metadata-name]</td><td>The value of this metadata element for the document</td></tr>
-</table>
-<p>
-<i><u>Extended metadata names</u></i><br>
-There are a few options for displaying metadata. The basic way is to specify e.g. [Title] or [dc.Title]: this displays the value of that particular metadata element for the current document/section. Metadata names can be prefixed by parent: or sibling. The following examples all use Title or Subject metadata, but any metadata could be used, including ones with namespaces (e.g. dc.Title). Any metadata name can also be prefixed by "cgisafe:". This results in the value being formatted so that it is safe to put in a URL.
-<p>
-<table class="faq-table">
-<tr><td>[parent:Title]</td><td>The Title of the immediate parent section</td></tr>
-<tr><td>[parent(Top):Title]</td><td>The Title of the topmost parent section</td></tr>
-<tr><td>[parent(All):Title]</td><td>All Titles of the parent sections, separated by ", "</td></tr>
-<tr><td>[parent(All':&nbsp;'):Title]</td><td>All Titles of the parent sections, separated by ": " (or whatever appears inside the ' ')</td></tr>
-<tr><td>[sibling:Subject]</td><td>All Subjects of the current section, separated by ", ". This is used for displaying metadata where there is more than one value. [Subject] will just display the first value.</td></tr>
-<tr><td>[sibling(All:'&lt;br&gt;'):Subject]</td><td>All Subjects of the current section, separated by &lt;br&gt;. </td></tr>
-<tr><td>[cgisafe:parent(Top):Title]</td><td>The Title of the topmost parent section, made safe for URLs.</td></tr>
-<tr><td>[cgisafe:sibling(All:'&lt;br&gt;'):Subject]</td><td>All Subjects of the current section, separated by &lt;br&gt;, made safe for URLs.</td></tr>
-</table>
-<p>
-<i><u>Extended Formatstring items</u></i><br>
-These items are only available if AllowExtendedOptions is true.
-<p>
-<table class="faq-table"><tr><th align=left>Item</th><th align=left>Description</th></tr>
-<tr><td>[DocumentButtonDetach]</td><td>The Detach button</td></tr>
-<tr><td>[DocumentButtonHighlight]</td><td>The Highlight button</td></tr>
-<tr><td>[DocumentButtonExpandText]</td><td>The Expand Text button</td></tr>
-<tr><td>[DocumentButtonExpandContents]</td><td>The Expand Contents button</td></tr>
-<tr><td>[DocImage]</td><td>The cover image of the document</td></tr>
-<tr><td>[DocTOC]</td><td>The table of contents for a hierarchical document, or the next/previous and go to page x bits for a paged document.</td></tr>
-</table>
-<p>
-<i><u>Conditional expressions in formatstrings</u></i><br>
-<table class="faq-table">
-<tr><td>\{If\}\{[metadata], action-if-non-null, action-if null\}</td><td>If there is a value for this metadata element, then output the first clause, otherwise output the second clause. Either clause is optional: if empty, nothing will be done for that case. <br>This is useful for displaying classifier nodes differently to document nodes: \{If\}\{[numleafdocs],format for classifier,format for document\}</td></tr>
-<tr><td>\{If\}\{"[metadata]" eq "value", action-if-equal, action-if-not-equal\}</td><td>Can do tests on metadata values: equals</td></tr>
-<tr><td>\{If\}\{"[metadata]" ne "value", action-if-not-equal, action-if-equal\}</td><td>Can do tests on metadata values: not equals</td></tr>
-<tr><td>\{Or\}\{[metadata], [metadata2], [metadata3]...\}</td><td>Each metadata is evaluated in turn, and the first one that exists is output<br>Useful for cases where there are different namespaced version of the same metadata, e.g. \{Or\}\{[dc.Title],[dls.Title],[Title],Untitled\}</td></tr>
-</table>
+}
-_tfaqcustomizemetadatalinking_ {
-<i>[contributed by Axel Schild]</i><br/>
-When a metadata element has only one value, it is easy to make a hyperlink out of the value. In the format statement, you just put an &lt;a&gt; tag around the metadata item, for example:
-<br><small><tt>&lt;a href="url to link to"&gt;[dc.Subject]&lt;/a&gt;</tt></small><br>
-When the metadata item has multiple values, and you want to link each one separately, it is a bit more difficult. The following is Axel's solution to his particular problem: display all the Creator elements, each one hyperlinked to a search of that Creator in the Creators index.
-<p>
-Use the format string below in the collect.cfg file (in this case, as part of the "format DocumentText" statement)
-<br><small><tt><pre>
-\{If\}\{[dc.Creator],
-&lt;tr&gt;
-&lt;td align=right valign=top&gt;&lt;b&gt;Authors:&lt;/b&gt;&lt;/td&gt;
-&lt;td align=left valign=bottom&gt;&lt;label name=AuthorField id=AuthorField&gt;
-\_httpquery\_;[cgisafe:sibling(All:\\' ; \\'):dc.Creator];[sibling(All:\\'\_\\'):dc.Creator]
-&lt;/label&gt;&lt;/td&gt;
-&lt;/tr&gt;\}&nbsp;
-</pre></tt></small>
-This statement includes a label definition with the name "AuthorField". "\_httpquery\_" is a macro which resolves into the http-address of the query page of the collection. "[cgisafe:sibling(All:\\' ; \\'):dc.Creator]" displays all Creators, separated by ; and with any special characters escaped for use within a web address. [sibling(All:\\'\_\\'):dc.Creator] produces a similar string without escaping the special characters. Notice the different separation symbols, these are needed later on.
-<p>
-Additional changes have to be made in order to make this whole thing work. You further need to change the \_header\_ or \_textheader\_ macro in the package of the page the format string will be displayed in (in this case the document package). The change is that \_htmlhead\_ has to be parametrized with
-<small><tt>\_htmlhead\_(onload="ExtractAuthors();")</tt></small>, where ExtractAuthors(); is a Javascript function that is called on loading the corresponding page (the document display page). Since you do not want to mess in the standard macro files, create an extra.dm file (in gsdl/collect/&lt;collname&gt;/macros) and override the chosen macro with a collection specific macro. In this example this is done by the code sequence
-<br><small><tt><pre>
-package document
-###document display
-###HTML-Page Header
-\_textheader\_ [c=exacol] \{\_cgihead\_
-\_htmlhead\_(onload="ExtractSubjects();ExtractAuthors();")
-&lt;center&gt;
-&lt;table width=_pagewidth_&gt;&lt;tr&gt;&lt;td align=right&gt;
-\_icontab\_\_javalinks\_&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;
-&lt;/center&gt;
-\}
-</pre></tt></small>
-Now all that is missing is the Javascript function which has to be included into the \_pagescriptextra\_ macro of the same package. Copy this macro out of the corresponding standard macro file and paste it into your extra.dm file. Make the necessary modification which is in this case
-<br><small><tt><pre>
-### Self-made Javascript functions
-\_pagescriptextra\_\{
-function ExtractAuthors() \\\{
-  var res;
-  a = AuthorField.outerText.split(";");
-  resolver = a[0]+"&q=";
-  b = a[1].split("+%3b+");
-  c = a[2].split("\_");
-  res = "";
-  for (i = 0; i &lt; b.length ;i++)
-    \\{
-       res = res + "&lt;a href=" + resolver + b[i]+ "&h=dd0&t=0&gt;" + c[i] + "&lt;/a&gt;&lt;br/&gt;";
-    \\}
-  AuthorField.outerHTML = res;
-\\}
-\}
-</pre></tt></small>
-This Javascript function evaluates the string of the defined label, splits it into several strings and composes a string out of those values, which is then set to the "outerHTML" element of the label. "&h=dd0" indicates which index to search in; dd0 should be replaced with the name of the appropriate index. The file gsdl/collect/&lt;collname&gt;/index/build.cfg gives the names of the various indexes.
+}
 #######################################################################

Note: See TracChangeset for help on using the changeset viewer.

Context Navigation

Changeset 9486

Legend:

trunk/greenorg/macros/english.dm

Download in other formats: