source: main/trunk/greenstone2/runtime-src/packages/yaz/GSDL_USAGE.html@ 26552

Last change on this file since 26552 was 2686, checked in by jrm21, 23 years ago

updated history/bug fix list.

  • Property svn:keywords set to Author Date Id Revision
File size: 4.9 KB
Line 
1<html>
2<head>
3<title>Using the Z39.50 Client in Greenstone</title>
4</head>
5
6<body>
7<a name=top>
8<h1>Using the Z39.50 Client in Greenstone</h1>
9</a>
10<b>Table of Contents</b><br>
11<a href="#whatis">About: What is Z39.50?</a><br>
12<a href="#config">Configuring Greenstone - Adding Servers</a><br>
13<a href="#todo">Currently known problems, and TODO list</a><br>
14<a href="#contact">Contacting Us</a><br>
15
16
17
18<a name=whatis>
19<h2>What is Z39.50?</h2>
20</a>
21Z39.50 is an international client/server protocol for searching bibliographic
22data. It can use the Internet Protocol (TCP/IP), which makes the databases
23on a server available from almost anywhere around the globe. It is widely
24used, for example, in on-line library catalogues. It allows a user to search
25one or more databases and retrieve the results of the query.
26
27<p>
28Our implementation uses the YAZ z39.50 toolkit, written by
29<a href="http://www.indexdata.dk">Index Data</a>.
30
31
32
33<a name=config>
34<h2>Adding Servers</h2>
35</a>
36The file z3950.cfg in the etc/packages directory contains entries for
37each server. By default, no servers are set up, although the config file
38comes with two (commented out) example Z39.50 servers, both for servers
39of the United States' <b>Library of Congress</b>.
40<p>
41Each entry consists of:
42<ul>
43<li>A unique "short name" for internal use by Greenstone.</li>
44<li>The internet name or address of the server, and optionally the
45port that the server is running on if not the default port 210.</li>
46<li>The name of the database to search on that server.</li>
47<li>A string that provides a meaningful name for the "collection".</li>
48<li>An optional "About" string, providing some information about the database
49and/or server.</li>
50<li>Optional icon fields, which are displayed instead of the text on the
51front page.</li>
52</ul>
53The entries need only be separated by whitespace, but for the purposes of
54clarity the sample entry uses newlines and tabs.
55<p>
56The sample Library of Congress entry looks like this:
57<pre>
58LOC
59 z3950.loc.gov:7090
60 Voyager
61 "Library of Congress z39.50 server"
62 About en "This is the z39.50 interface to the US LoC catalogue
63 system. It contains approximately 12 million bibliographic records.
64 For server capabilities, look at
65 &lt;a href=\"http://lcweb.loc.gov/z3950/lcserver.html\"&gt;their web pages&lt;/a&gt;."
66</pre>
67There is a list at the Library Of Congress website containing some
68<a href="http://lcweb.loc.gov/z3950/agency/resources/testport.html">servers
69publicly available for testing</a>.
70
71
72<a name=todo>
73<h2>Known Problems/Issues list</h2>
74</a>
75<ul>
76<li>Because of the open nature of the standard, our client may not work with
77some servers. Please notify the author (contact details below) of any
78such problems.</li>
79<li>Because of the large number of Marc fields, only the most frequently
80used fields have been given explicit names in the results. Furthermore,
81these are currently hard-coded to correspond to the USMARC field names.</li>
82<li><b>The z39.50 client will not work when fast-cgi is used!</b>. Currently,
83the use of the fast-cgi package (off by default) will disable the
84use of the z39.50 client code for Greenstone.</li>
85<li>There are spurious &lt;B&gt; tags in the title of the window when
86viewing an individual record.</li>
87<li>Greenstone will claim there are no collections if there are no
88sub-directories in the "collect" directory, even if there are configured
89z39.50 servers, although it will work if there are unbuilt collections.</li>
90</ul>
91
92<b>History</b><br>
93Jul 2001 - finally tracked down and fixed an annoying bug that caused
94greenstone to segfault when retrieving documents for some queries.<br>
95Jun 2001 - decided to drop href for field 856, as some examples have
96explanatory text in the field as well as the URI.<br>
97Oct 2000 - cache results from server, so cut down the number of connections for
98a single query/document. Also added href for MARC field 856.<br>
99Aug 2000 - Various bug fixes and minor modifications.<br>
100Fri Aug 4 2000 - The z39.50 code is now "stable" in the main source code (in CVS).<br>
101Tue 1 Aug 2000 - selecting a field from the drop-down box now actually works.
102This results in both quicker replies and more accurate results.<br>
103Mon 24 Jul 2000 - queries are now "AND"ed - for example, the query "computer
104science" will now only return records that contain both words.<br>
105May-June 2000 - Code written.<br>
106
107<a name=contact>
108<h2>Contact Details</h2>
109</a>
110For general comments about Greenstone, or suggestions for improvements, send
111email to
112<a href="mailto:[email protected]?subject=z39.50 client in Greenstone">[email protected]</a><br>
113<br>
114For bug reports or questions about the z39.50 code itself, send email to
115the author, John McPherson -
116<a href="mailto:[email protected]?subject=z39.50 client in Greenstone"
117>[email protected]</a>.
118
119<p>
120<a href="#top">Back to top</a>
121<p>
122<address>Last modified: July 12, 2001 by John McPherson</address>
123</body>
124</html>
Note: See TracBrowser for help on using the repository browser.