3 Debian version depends on on libyaz4. Note that Pazpar2 will still
4 compile from source with YAZ 3.
6 Split services into separate files. The example configuration file
7 pazpar2.cfg.dist now includes a default service default.xml (part of
8 etc). And default.xml includes settings/edu.xml. The default.xml file,
9 not to be confused with settings/defaults.xml, is a template for jsdemo
10 and other services. The Debian package installs /etc/pazpar2/server.xml
11 which is now the main pazpar2 configuration (used to be called pazpar2.cfg).
12 server.xml includes services from /etc/pazpar2/services-enabled/*.xml .
13 The default.xml (from etc) is installed in /etc/pazpar2/services-available
14 and a symlink to it is created from services-enabled. The default.xml
15 service is unnamed and, thus, will be used by jsdemo and test1.
17 New setting pz:negotiation_charset. Patch from Andrei V. Toutoukine. The
18 new setting pz:negotiation_charset specifies character set for Z39.50 Init.
22 Support for additional fields in cf.xsl and pazpar2.conf.dist:
23 publisher, available, due, location (=locallocation), callno
24 (=callnumber), thumburl and score.
26 Describe pz:xslt and the auto setting.
28 Move mergekey definition away from the normalization stylesheets and
29 define a mergekey common for all target types in pazpar2.cfg.
31 Code update: Use the Odr_int type for hit counts. This is part of
32 YAZ 3.0.47 and later and so configure checks for that.
36 Metadata attribute 'skiparticle' also works for ICU based
37 normalization. (was only working for the non-ICU/ASCII before).
39 Command bytarget with argument settings=1 will show settings per
40 target.. This is to be able to verify correct settings and be able to
41 test that they are correct. The database settings array size is now
42 also stored.. Problems with database settings array is that if not
43 careful it will be too small (smaller than dictionary per-service
46 Make record list sorting stable by comparing mergekey for records if
47 relevance/title or other sorting criteria all match. This is merely to
48 ensure that our regressions tests works (reproducible output).
50 Relevance calculation changes: use a different denominator (length) for
51 per-field relevance scoring.. Instead of length of all ranked fields we
52 now use length of individual fields (as if they were individual "free"
53 text fields). This will ensure that documents with a long field with no
54 match (say description) will not "hurt" a title match.
56 Diagnostic member was not set on connection error. Fixed
60 Command search takes two optional parameters, startecs and maxrecs,
61 that specifies the start offset (0, 1, ...) and maximum number of records
62 to fetch for each target.
64 XSLTs + MARC maps are cached within a session so we don't re-parse
65 them over and over again. Even for a session with a single search
66 there's much to be gained because many targets use the same
69 The metadata attribute 'mergekey' now takes one of three values 'no',
70 'required', 'optional' . And the resulting mergekey from metadata
71 is now ordered in the same way as metadata in the service definition.
72 Older Pazpar2 version use the order in which metadata appeared in a
75 The search argument 'filter' now offers a new operator ~ which does a
76 substring match. The = operator works as before: string match for
77 anything but pz:id, or target match for pz:id.
79 New setting pz:recordfilter. The value of this setting takes the
80 form name[~value]. This setting makes Pazpar2 ignore all retrieved
81 records that do not have the metadata element name with value substring
84 Pazpar2 allows YAZ log level to be set (option -v).
88 For WS responses Pazpar2 creates XML header. Exception: raw record.
90 Setting XML files are now stored in etc/settings instead of etc. This
91 reflects the layout with the Debian package layout.
93 Settings may be posted for command=settings. The POSTed settings must
94 have root element 'settings' like regular setting files. In order to be
95 recognized, the POST request must use Content-Type=text/xml.
97 A service may be posted for command=init. This service will be used
98 during the session. The service may have its own target settings,
99 ICU config, timeout, etc. In order to be recognized, the POST request
100 must use Content-Type=text/xml.
102 Timeout values may be given per-service. That's element 'timeout'
103 which takes three attribute values (a subset may be given): 'session',
104 'z3950_operation', 'z3950_session'. Option -T is no longer supported
105 - used to specify session timeout.
107 Option -t tests the Pazpar2 configuration and returns exit code
108 (0=success, non-zero=failure). In previous version of Pazpar2, -t
109 specified local settings.
111 In version 1.2.0 the configuration file - after include processing -
112 was dumped to stdout. Now, the configuration is only dumped to the
113 yaz log file if option -d is given.
117 Configuration may now have multiple server areas. This means that a
118 Pazpar2 instance may listen on multiple ports. Virtual hosting is not
119 yet supported - on a server basis. Configuration may also have multiple
120 services .. That is repeating service elements inside a server. Each
121 has an attribute 'id' which serves as service ID. This ID in turn may
122 be used in a Pazpar2 session, by specifying parameter service=ID for
123 command init. There can be at most one unnamed service inside a server
124 which can be referred to by not specifying an service ID for command
125 init (backwards compatible). In order to partition multiple servers and
126 services a new include directive has been added. This takes an attribute
127 'src' which specifies one or more sub-files. For example to include
128 service files, one might use:
129 <server >.. <include src=/"etc/pazpar2/conf.d/*.xml"/> .. </server>.
130 It is the intention that that completely makes the settings directive
133 Fix problem where the record command would wait forever if there were
134 no targets to wait for (activeclients == 0).
138 One result set is created per session (last search) rather than for
139 each connection which happen to be shared (bug #3009).
141 marc21 stylesheets changed for efficiency.
145 Session timeout may be specified on the command-line as option -T.
147 Pazpar2 may now be operated in a no-merged mode for records.. All records
148 will be considered unique. This mode is enabled if no mergekey is
149 generated by the normalization stylesheet (pz:xslt).
151 Pazpar2 caches original records from each target and the 'record' command
152 with offset returns the original record if 'syntax' and 'esn' are NOT
153 specified. This speeds up retrieval of original records but also means
154 that Pazpar2 uses more memory. The cached records will be freed when the
155 session terminates or a new search is executed.
157 Pazpar2 no longer uses its own ICU wrapper. Instead the ICU wrapper
158 library part of YAZ is used.
160 Added SRU client support.
162 Automatically computes pz:nativesyntax if not provided. Works for XML and
165 --- 1.0.13 2008/11/24
167 Command bytarget returns name of target (if defined).
169 --- 1.0.12 2008/11/04
171 Fixed bug #2021.. location now holds all brief elements.
173 --- 1.0.11 2008/10/15
175 Fixed check for application/x-www-form-urlencoded parameters.
177 --- 1.0.10 2008/10/14
179 Fixes for IE in pz2.js.
181 Fixed bug #2021: non-merged, brief meta data NOT included for command=show.
185 Changed the JS library pz2.js to use POST for long URL (+ params).
187 Added installation instructions for Windows. Note: NT services is
188 NOT available until we make a new release of YAZ.
190 Preserve order of repeated metadata fields (they were reversed before).
192 More MARC21 information extracted for metadata.
196 Fixed bug #1162: HTML entities are not escaped properly.
198 Native Windows port of Pazpar2. Makefile for Visual Studio provided.
202 Marc21 stylesheet updated to reflect multiple full text fields
206 Fixed bug in pz2.js WRT DOMElement attributes on IE.
208 Fixed bug 2100: Database wildcards not working
212 Added support for retrieval of records in binary.
214 Fixed bug 1794: Pazpar2 does not return valid XML.
216 Deal with ICU not returning sortkey (resulted in SEGV before).
220 JavaScript library pzw2.js throws error if WS response (from Pazpar2 or
221 other) is malformed (non-wellformed XML or missing Pazpar2 OK status).
223 Improved diagnostics when Pazpar2 HTTP decoding fails.
225 Pazpar2 requests may be POSTed as using Content-Type
226 application/x-www-form-urlencoded.
228 Pazpar2 honors LF in HTTP headers.
230 Handle targets that handle negative hit counts (should not happen, but it
235 ICU is used for tokenization and normalization of the following: mergekey,
236 sorting, relevance terms.
238 Debian package now enables ICU tokenization and normalization by default.
242 Exposed user setting values (i.e. non-pz: names) to the record systems in two
243 ways: Either as parameters to the normalization stylesheets (which would allow the
244 programmer to postprocess or use the values in any way) or after the normalization
245 step, in which case values are made part of the normalized record (and available for
246 sorting, termlists, display, or other interface-related use.
248 Implemented sorting by year.
250 Option -d dumps records to the current log file instead of stderr.
252 Fixes for compilation on cygwin.
254 Z39.50 client code uses pz:elements. pz:elements was recognized in
255 earlier Pazpar2 versions but it was not used for anything.
257 icu_chain_test is using fgets instead of getline - fixes compilation
260 Loosen the CCL query parsing so that Pazpar2 only returns error if _all_
261 query conversions fail (rather than _any_). This means targets that do
262 not support some fields are ignored in a search.
266 Improved handling of socket timeout for Z39.50 connections.
268 Misc documentation updates and spell fixes.
270 Debian package pazpar2 creates log rotate entry.
272 Debian package pazpar2-apache2 reloads Apache2.
274 jsdemo included in distribution. It illustrates the use of the js/pz2.js
279 First public release.