1 Added exact-match recordfilter; format name=value
5 SOLR support. Pazpar2 may operate as web service client for SOLR.
9 Fix for show command and block=1 (dead lock). Bug was introduced in
14 New RPM packages: pazpar2, pazpar2-js, pazpar2-doc. These have been
15 tested on CentOS 5.5 only.
19 Fix problem with result sets being removed from a client session
20 if the connection for it was resused by another session. Bug #3489.
22 New iphone UI for Pazpar2 (www/iphone).
26 Fixes for threaded operation.
28 New stylesheets for TurboMARC: tmarc.xsl and opac_turbomarc.xsl.
30 New example services in etc/services in source. In the Debian packages
31 these are located in /etc/pazpar2/services-available
33 Threaded mode operational on Windows. Requires Windows 7 or Windows
36 Default value of setting pz:max_connections is 0 which means that there
37 is no limit on number of connections.
41 Pazpar2 may operate in threaded mode. Enabled by element threads in
42 the configuration. See pazpar2_conf for details.
44 New setting setting: pz:max_connections. Setting pz:max_connections is
45 a limit of number of sockets to a host. When this limit is reached,
46 Pazpar2 will wait up to 5 seconds for a connection to becomes available.
47 The client will be marked Client_Error when it can not be searched
48 (other clients in a session may work). If pz:max_connections is not set
49 for a target, a value of 30 will be used. Note: the pz:max_connections
50 will only work in threaded mode.
52 pz2.js: JSON support for show.
54 Debian package: Enable default service, default.xml, before starting
55 Pazpar2 only if there is no service already in /etc/pazpar2/services-enabled.
59 Debian version depends on on libyaz4. Note that Pazpar2 will still
60 compile from source with YAZ 3.
62 Split services into separate files. The example configuration file
63 pazpar2.cfg.dist now includes a default service default.xml (part of
64 etc). And default.xml includes settings/edu.xml. The default.xml file,
65 not to be confused with settings/defaults.xml, is a template for jsdemo
66 and other services. The Debian package installs /etc/pazpar2/server.xml
67 which is now the main pazpar2 configuration (used to be called pazpar2.cfg).
68 server.xml includes services from /etc/pazpar2/services-enabled/*.xml .
69 The default.xml (from etc) is installed in /etc/pazpar2/services-available
70 and a symlink to it is created from services-enabled. The default.xml
71 service is unnamed and, thus, will be used by jsdemo and test1.
73 New setting pz:negotiation_charset. Patch from Andrei V. Toutoukine. The
74 new setting pz:negotiation_charset specifies character set for Z39.50 Init.
78 Support for additional fields in cf.xsl and pazpar2.conf.dist:
79 publisher, available, due, location (=locallocation), callno
80 (=callnumber), thumburl and score.
82 Describe pz:xslt and the auto setting.
84 Move mergekey definition away from the normalization stylesheets and
85 define a mergekey common for all target types in pazpar2.cfg.
87 Code update: Use the Odr_int type for hit counts. This is part of
88 YAZ 3.0.47 and later and so configure checks for that.
92 Metadata attribute 'skiparticle' also works for ICU based
93 normalization. (was only working for the non-ICU/ASCII before).
95 Command bytarget with argument settings=1 will show settings per
96 target.. This is to be able to verify correct settings and be able to
97 test that they are correct. The database settings array size is now
98 also stored.. Problems with database settings array is that if not
99 careful it will be too small (smaller than dictionary per-service
102 Make record list sorting stable by comparing mergekey for records if
103 relevance/title or other sorting criteria all match. This is merely to
104 ensure that our regressions tests works (reproducible output).
106 Relevance calculation changes: use a different denominator (length) for
107 per-field relevance scoring.. Instead of length of all ranked fields we
108 now use length of individual fields (as if they were individual "free"
109 text fields). This will ensure that documents with a long field with no
110 match (say description) will not "hurt" a title match.
112 Diagnostic member was not set on connection error. Fixed
116 Command search takes two optional parameters, startecs and maxrecs,
117 that specifies the start offset (0, 1, ...) and maximum number of records
118 to fetch for each target.
120 XSLTs + MARC maps are cached within a session so we don't re-parse
121 them over and over again. Even for a session with a single search
122 there's much to be gained because many targets use the same
125 The metadata attribute 'mergekey' now takes one of three values 'no',
126 'required', 'optional' . And the resulting mergekey from metadata
127 is now ordered in the same way as metadata in the service definition.
128 Older Pazpar2 version use the order in which metadata appeared in a
131 The search argument 'filter' now offers a new operator ~ which does a
132 substring match. The = operator works as before: string match for
133 anything but pz:id, or target match for pz:id.
135 New setting pz:recordfilter. The value of this setting takes the
136 form name[~value]. This setting makes Pazpar2 ignore all retrieved
137 records that do not have the metadata element name with value substring
140 Pazpar2 allows YAZ log level to be set (option -v).
144 For WS responses Pazpar2 creates XML header. Exception: raw record.
146 Setting XML files are now stored in etc/settings instead of etc. This
147 reflects the layout with the Debian package layout.
149 Settings may be posted for command=settings. The POSTed settings must
150 have root element 'settings' like regular setting files. In order to be
151 recognized, the POST request must use Content-Type=text/xml.
153 A service may be posted for command=init. This service will be used
154 during the session. The service may have its own target settings,
155 ICU config, timeout, etc. In order to be recognized, the POST request
156 must use Content-Type=text/xml.
158 Timeout values may be given per-service. That's element 'timeout'
159 which takes three attribute values (a subset may be given): 'session',
160 'z3950_operation', 'z3950_session'. Option -T is no longer supported
161 - used to specify session timeout.
163 Option -t tests the Pazpar2 configuration and returns exit code
164 (0=success, non-zero=failure). In previous version of Pazpar2, -t
165 specified local settings.
167 In version 1.2.0 the configuration file - after include processing -
168 was dumped to stdout. Now, the configuration is only dumped to the
169 yaz log file if option -d is given.
173 Configuration may now have multiple server areas. This means that a
174 Pazpar2 instance may listen on multiple ports. Virtual hosting is not
175 yet supported - on a server basis. Configuration may also have multiple
176 services .. That is repeating service elements inside a server. Each
177 has an attribute 'id' which serves as service ID. This ID in turn may
178 be used in a Pazpar2 session, by specifying parameter service=ID for
179 command init. There can be at most one unnamed service inside a server
180 which can be referred to by not specifying an service ID for command
181 init (backwards compatible). In order to partition multiple servers and
182 services a new include directive has been added. This takes an attribute
183 'src' which specifies one or more sub-files. For example to include
184 service files, one might use:
185 <server >.. <include src=/"etc/pazpar2/conf.d/*.xml"/> .. </server>.
186 It is the intention that that completely makes the settings directive
189 Fix problem where the record command would wait forever if there were
190 no targets to wait for (activeclients == 0).
194 One result set is created per session (last search) rather than for
195 each connection which happen to be shared (bug #3009).
197 marc21 stylesheets changed for efficiency.
201 Session timeout may be specified on the command-line as option -T.
203 Pazpar2 may now be operated in a no-merged mode for records.. All records
204 will be considered unique. This mode is enabled if no mergekey is
205 generated by the normalization stylesheet (pz:xslt).
207 Pazpar2 caches original records from each target and the 'record' command
208 with offset returns the original record if 'syntax' and 'esn' are NOT
209 specified. This speeds up retrieval of original records but also means
210 that Pazpar2 uses more memory. The cached records will be freed when the
211 session terminates or a new search is executed.
213 Pazpar2 no longer uses its own ICU wrapper. Instead the ICU wrapper
214 library part of YAZ is used.
216 Added SRU client support.
218 Automatically computes pz:nativesyntax if not provided. Works for XML and
221 --- 1.0.13 2008/11/24
223 Command bytarget returns name of target (if defined).
225 --- 1.0.12 2008/11/04
227 Fixed bug #2021.. location now holds all brief elements.
229 --- 1.0.11 2008/10/15
231 Fixed check for application/x-www-form-urlencoded parameters.
233 --- 1.0.10 2008/10/14
235 Fixes for IE in pz2.js.
237 Fixed bug #2021: non-merged, brief meta data NOT included for command=show.
241 Changed the JS library pz2.js to use POST for long URL (+ params).
243 Added installation instructions for Windows. Note: NT services is
244 NOT available until we make a new release of YAZ.
246 Preserve order of repeated metadata fields (they were reversed before).
248 More MARC21 information extracted for metadata.
252 Fixed bug #1162: HTML entities are not escaped properly.
254 Native Windows port of Pazpar2. Makefile for Visual Studio provided.
258 Marc21 stylesheet updated to reflect multiple full text fields
262 Fixed bug in pz2.js WRT DOMElement attributes on IE.
264 Fixed bug 2100: Database wildcards not working
268 Added support for retrieval of records in binary.
270 Fixed bug 1794: Pazpar2 does not return valid XML.
272 Deal with ICU not returning sortkey (resulted in SEGV before).
276 JavaScript library pzw2.js throws error if WS response (from Pazpar2 or
277 other) is malformed (non-wellformed XML or missing Pazpar2 OK status).
279 Improved diagnostics when Pazpar2 HTTP decoding fails.
281 Pazpar2 requests may be POSTed as using Content-Type
282 application/x-www-form-urlencoded.
284 Pazpar2 honors LF in HTTP headers.
286 Handle targets that handle negative hit counts (should not happen, but it
291 ICU is used for tokenization and normalization of the following: mergekey,
292 sorting, relevance terms.
294 Debian package now enables ICU tokenization and normalization by default.
298 Exposed user setting values (i.e. non-pz: names) to the record systems in two
299 ways: Either as parameters to the normalization stylesheets (which would allow the
300 programmer to postprocess or use the values in any way) or after the normalization
301 step, in which case values are made part of the normalized record (and available for
302 sorting, termlists, display, or other interface-related use.
304 Implemented sorting by year.
306 Option -d dumps records to the current log file instead of stderr.
308 Fixes for compilation on cygwin.
310 Z39.50 client code uses pz:elements. pz:elements was recognized in
311 earlier Pazpar2 versions but it was not used for anything.
313 icu_chain_test is using fgets instead of getline - fixes compilation
316 Loosen the CCL query parsing so that Pazpar2 only returns error if _all_
317 query conversions fail (rather than _any_). This means targets that do
318 not support some fields are ignored in a search.
322 Improved handling of socket timeout for Z39.50 connections.
324 Misc documentation updates and spell fixes.
326 Debian package pazpar2 creates log rotate entry.
328 Debian package pazpar2-apache2 reloads Apache2.
330 jsdemo included in distribution. It illustrates the use of the js/pz2.js
335 First public release.