<TABAREA tabs="Greenstone3,Greenstone2"> <TAB> URL's are greatly simplified in Greenstone3. Using URL rewriting, Greenstone3's URL's are logical, short, and informative. For example, the URL for a document page in a Greenstone2 collection will look something like this:

http://localhost:8283/greenstone/cgi-bin/library.cgi?e=d-01000-00---off-0games--00-1----0-10-0---0---0direct-10---4-------0-1l--11-en-50---20-about---00-3-1-00-00--4--0--0-0-11-10-0utfZz-8-00&a=d&c=games&cl=CL1&d=HASH017893f810ba88942720384e

In Greenstone3, the URL for a document page will look like this:

http://localhost:8383/greenstone3/library/collection/lucene-jdbm-demo/document/ec159e

So, as this example shows, you can easily access any document in any collection in a library simply by navigating to http://localhost:8383/greenstone3/<library-name>/collection/<collection-name>/document/<document-ID>.

<baseurl>/<context>/<servlet>

By default, The Greenstone3 server runs on http://localhost:8383 and Greenstone is located at http://localhost:8383/greenstone3. Every library (and any other servlets) are

context 'technically' set by the name of the file in Greenstone3/packages/tomcat/conf/Catlina/localhost, which is, by default greenstone3.xml. HOWEVER, every time you start the server, Greenstone3/build.xml copies this the file from Greenstone3/resources/tomcat into the correct folder.

    <!-- [line 1287] set up the greenstone3 context -->
    <copy file="${basedir}/resources/tomcat/greenstone3.xml" tofile="${packages.home}/tomcat/conf/Catalina/localhost/greenstone3.xml" overwrite="true">
      <filterset>
        <filter token="gsdl3webhome" value="${web.home}"/>
        <filter token="gsdl3webwritablehome" value="${web.writablehome}"/>
	<filter token="privilegedattribute" value ="${privileged.attribute}"/>
      </filterset>
    </copy>

To change the context, change variable in Greenstone3/build.properties.

# The context name of your GS3 digital library. By default this will be "greenstone3". 
# Ensure this has a value. If you change this multiple times, you need to remove the old versions
# of <custom.context>.xml from GS3/packages/tomcat/conf/Catalina/localhost
# does not contain previous 
custom.context=greenstone3

o is output Find more information on arguments: Greenstone3 → src → java → org → greenstone → gsdl3 → action

• Linking metadata values to a search for that metadata

</TAB> <TAB>

CGI arguments encode the parameters of each page, for instance, what kind of page to display, what query to carry out etc. This page describes the common actions and arguments used by the Greenstone library server.

a is the main cgi argument and determines which action is used to dipslay the page.

You can set the default value of any cgi argument in the Greenstone\etc\main.cfg file. Add a line like

 cgiarg shortname=a argdefault=p

This will set the default value of argument 'a' to 'p'.

Displays 'static' pages, such as home, about, help and preferences pages.

Displays search form and results, and optionally search history. Many of the options are set from the preferences page.

The following arguments are only available for MGPP and Lucene collections, which provide form searching.

Used for displaying documents and classifiers

Handles displaying documents which are external web pages

Clicking on a link to an external resource from a Greenstone document takes the user to an intermediate page that says something like the following: "External Link The link you have selected is external to any of your currently selected collections. If you still wish to view this link and your browser has access to the Web, you can go forward to this page; otherwise use your browsers "back" button to return to the previous document.”

To get rid of this intermediate page, add the following to greenstone/etc/main.cfg

 cgiarg shortname=el argdefault=direct

You may want to redirect a more convenient URL to your Greenstone cgi program. For example, on our system the URL http://nzdl.org (which is shorthand for http://nzdl.org/index.html) is redirected to http://nzdl.org/cgi-bin/library . The Apache webserver accomplishes this with the Redirect directive. Along with other directives, this goes into the C:\Program Files\Apache Group\Apache\conf\httpd.conf configuration file. To redirect the URL http://www.yourserver.com to http://www.yourserver.com/cgi-bin/library , put this line into httpd.conf:

Redirect /index.html http://www.yourserver.com/cgi-bin/library

Then you will reach your digital library system directly from the URL http://www.yourserver.com . Instead, if you wanted a URL like http://www.yourserver.com/greenstone to be redirected to http://www.yourserver.com/cgi-bin/library , include in the httpd.conf file

Redirect /greenstone http://www.yourserver.com/cgi-bin/library

If your computer doesn't have a domain name (like the “www.yourserver.com” above), just replace www.yourserver.com by localhost 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.

Instead of putting redirect directives into the file httpd.conf, you can equally well put them into a file called .htaccess within your server's document root directory. In fact, doing so has two advantages. First, changes to .htaccess take effect immediately, whereas you have to restart the Apache webserver to see the effect of changes to httpd.conf. Second, on Unix systems you usually have to be logged in as the “root” user to edit httpd.conf, whereas you don't to edit .htaccess.

</TAB> </TABAREA>