1 Fix bug for command sort, that could return no results for active clients
2 (from previous search). This bug was present in 1.6.6-1.6.7.
4 Fix bug in results that could include results that should have been
5 filtered out. This bug was present in 1.6.6-1.6.7.
9 Fix bug introduced in 1.6.6 where a connection re-use could stall
12 Local filtering may now specify a local metadata field, eg.
13 pz:limitmap:somefield[t]=local:otherfield
17 For search, when limit and or filtering is in place and search
18 is identical to previous search, the result set is re-used and the
19 target is not searched.
21 Limits may work perform local filtering as well, by using "local:"
26 Updated bytarget command to contain a suggestions element with misspelled
27 words and suggestions to these. pz2.js has been updated to deliver this
28 onwards as well. Only target that currently delivers this is the solr
33 New service definition element, xslt, that allows an embedded stylesheet
34 to be defined. This can be referred to from pz:xslt as an alternative to
37 New pz:sortmap:field setting for specifying hints on how to make
38 a target natively sort on a field. This is used for command=show in
39 conjunction with sort.
41 New pz:url setting for specifying the actual URL for a target. When
42 this is used the target ID is not used as URL anymore and the target ID
43 may be almost any string (not including []).
45 command=termlist without name parameter returns all termlists/facets.
46 Previously if name parameter was omitted, only "subject" was returned.
50 Make termlist sorting stable. Terms with same frequency are now sorted by
51 their display name. This makes a pretty display and improves our
52 regression test because qsort is not a stable sort.
54 New sort parameter value 'position'. The 'position' sorts merged records
55 by their original position from the remote target. This is primarily useful
56 for debugging and may be used for targets that already perform some kind
57 of relevance ranking. Note that sort by default is decreasing; so to get
58 records in their original order sort=position:1 must be used.
62 tmarc.xsl: yet another 773$g fix. Was broken in 1.6.1 as well.
64 Facility to change working directory for pazpar2 daemon. Option -wdir
65 sets working directory to dir. This facility is useful if core dumps
66 must be saved. In this case, the current working directory must be
67 writable by the running user, such as "nobody".
71 New configuration element <icu_chain> for <server>/<service> which
72 allows a named ICU rule (chain) to be defined. The names relevance,
73 sort, mergekey and facet are used for those operations. The definition
74 <icu_chain id="sort" locale="en"> .. </icu_chain>
76 <sort> <icu_chain locale="en> ... </icu_chain> </sort>
77 And so on.. for relevance, mergekey and facet as well. The latter
78 style is deprecated. The facet terms are normalized by the facet
79 rule by default. This may be changed on a metadata field basis by
80 defining the new attribute 'facetrule' for the metadata element.
82 <icu_chain id="myrule" locale="en"> ... </icu_chain>
83 <metadata name="author" termlist="yes" facetrule="myrule"/>
85 Preserve rorder for merged metadata. Fixes issue as reported by Sven
86 Porst: http://lists.indexdata.dk/pipermail/yazlist/2011-July/003230.html
88 tmarc.xsl: set journal-subpart to 773$ only.
92 Modify the behavior for the limit parameter (first defined in 1.5.7).
93 Mapping of limit searches are now defined by the new configuration item
94 pz:limitmap. Fix a dead-lock problem with the limit parameter.
96 Extend tmarc.xsl to extract 773$g data (OpenURL).
100 ICU default maps remove backquote (`).
102 Command 'search' takes limit parameter (optional). The limit parameter
103 allows a search to be limited one or more facets and the corresponding
104 values. This is for server side filtering.
106 Configure tweak: Use -lm for log(3) if needed
110 Fix a problem with skiparticle sortkey that could be completely
111 ignored (and reduced to "").
113 Fix dependency problem in pazpar2 RPM package (did not require
114 libyaz4 as it should).
118 Fix memory leak that occurred for command=termlist&name=xtargets .
120 Pazpar2 may save HTTP requests. Enabled by option -R.
124 Experimental support for DTIC DADS target. New dads-pz2.xsl.
126 Support for query_syntax (overrides the default for SRU | Z39.50)
128 Support for extraArgs (ZOOM "extraArgs" option) for targets
130 New commands: status-server and status-session
134 Fix for threaded runs: Client now have a copy of the database URL,
135 which can used after the database has been release from the client.
136 This makes the logging in the connection idle timeout of the client nicer (no NOURL) and should be thread-safe.
138 tmarc.xsl: Add journal-title-abbrev and full text.
140 cf.xsl: new fields: isbn, issn, journaltitle, volume, issue
142 Fix for cmd=record before search.
144 Session Logging clean up.
146 Fix wrong termlist factor when maxrecs is different from 100.
150 Fix missing pz:termlist_term_factor in settings.c messed up pz:preferred.
151 Term factor is default enabled but can be diseabled by
152 pz:termlist_term_factor=0
156 Add scaling of facet count. Currently always enabled, needs fixing.
157 Allow user-defined info for target suffix. This has no meaning in
158 Pazpar2 except to distinguish targets from each other. The suffix
159 data begins with #. For example z3950.indexdata.com/gils#Mydata
161 Added exact-match recordfilter; format name=value
165 SOLR support. Pazpar2 may operate as web service client for SOLR.
169 Fix for show command and block=1 (dead lock). Bug was introduced in
174 New RPM packages: pazpar2, pazpar2-js, pazpar2-doc. These have been
175 tested on CentOS 5.5 only.
179 Fix problem with result sets being removed from a client session
180 if the connection for it was resused by another session. Bug #3489.
182 New iphone UI for Pazpar2 (www/iphone).
186 Fixes for threaded operation.
188 New stylesheets for TurboMARC: tmarc.xsl and opac_turbomarc.xsl.
190 New example services in etc/services in source. In the Debian packages
191 these are located in /etc/pazpar2/services-available
193 Threaded mode operational on Windows. Requires Windows 7 or Windows
196 Default value of setting pz:max_connections is 0 which means that there
197 is no limit on number of connections.
201 Pazpar2 may operate in threaded mode. Enabled by element threads in
202 the configuration. See pazpar2_conf for details.
204 New setting setting: pz:max_connections. Setting pz:max_connections is
205 a limit of number of sockets to a host. When this limit is reached,
206 Pazpar2 will wait up to 5 seconds for a connection to becomes available.
207 The client will be marked Client_Error when it can not be searched
208 (other clients in a session may work). If pz:max_connections is not set
209 for a target, a value of 30 will be used. Note: the pz:max_connections
210 will only work in threaded mode.
212 pz2.js: JSON support for show.
214 Debian package: Enable default service, default.xml, before starting
215 Pazpar2 only if there is no service already in /etc/pazpar2/services-enabled.
219 Debian version depends on on libyaz4. Note that Pazpar2 will still
220 compile from source with YAZ 3.
222 Split services into separate files. The example configuration file
223 pazpar2.cfg.dist now includes a default service default.xml (part of
224 etc). And default.xml includes settings/edu.xml. The default.xml file,
225 not to be confused with settings/defaults.xml, is a template for jsdemo
226 and other services. The Debian package installs /etc/pazpar2/server.xml
227 which is now the main pazpar2 configuration (used to be called pazpar2.cfg).
228 server.xml includes services from /etc/pazpar2/services-enabled/*.xml .
229 The default.xml (from etc) is installed in /etc/pazpar2/services-available
230 and a symlink to it is created from services-enabled. The default.xml
231 service is unnamed and, thus, will be used by jsdemo and test1.
233 New setting pz:negotiation_charset. Patch from Andrei V. Toutoukine. The
234 new setting pz:negotiation_charset specifies character set for Z39.50 Init.
238 Support for additional fields in cf.xsl and pazpar2.conf.dist:
239 publisher, available, due, location (=locallocation), callno
240 (=callnumber), thumburl and score.
242 Describe pz:xslt and the auto setting.
244 Move mergekey definition away from the normalization stylesheets and
245 define a mergekey common for all target types in pazpar2.cfg.
247 Code update: Use the Odr_int type for hit counts. This is part of
248 YAZ 3.0.47 and later and so configure checks for that.
252 Metadata attribute 'skiparticle' also works for ICU based
253 normalization. (was only working for the non-ICU/ASCII before).
255 Command bytarget with argument settings=1 will show settings per
256 target.. This is to be able to verify correct settings and be able to
257 test that they are correct. The database settings array size is now
258 also stored.. Problems with database settings array is that if not
259 careful it will be too small (smaller than dictionary per-service
262 Make record list sorting stable by comparing mergekey for records if
263 relevance/title or other sorting criteria all match. This is merely to
264 ensure that our regressions tests works (reproducible output).
266 Relevance calculation changes: use a different denominator (length) for
267 per-field relevance scoring.. Instead of length of all ranked fields we
268 now use length of individual fields (as if they were individual "free"
269 text fields). This will ensure that documents with a long field with no
270 match (say description) will not "hurt" a title match.
272 Diagnostic member was not set on connection error. Fixed
276 Command search takes two optional parameters, startecs and maxrecs,
277 that specifies the start offset (0, 1, ...) and maximum number of records
278 to fetch for each target.
280 XSLTs + MARC maps are cached within a session so we don't re-parse
281 them over and over again. Even for a session with a single search
282 there's much to be gained because many targets use the same
285 The metadata attribute 'mergekey' now takes one of three values 'no',
286 'required', 'optional' . And the resulting mergekey from metadata
287 is now ordered in the same way as metadata in the service definition.
288 Older Pazpar2 version use the order in which metadata appeared in a
291 The search argument 'filter' now offers a new operator ~ which does a
292 substring match. The = operator works as before: string match for
293 anything but pz:id, or target match for pz:id.
295 New setting pz:recordfilter. The value of this setting takes the
296 form name[~value]. This setting makes Pazpar2 ignore all retrieved
297 records that do not have the metadata element name with value substring
300 Pazpar2 allows YAZ log level to be set (option -v).
304 For WS responses Pazpar2 creates XML header. Exception: raw record.
306 Setting XML files are now stored in etc/settings instead of etc. This
307 reflects the layout with the Debian package layout.
309 Settings may be posted for command=settings. The POSTed settings must
310 have root element 'settings' like regular setting files. In order to be
311 recognized, the POST request must use Content-Type=text/xml.
313 A service may be posted for command=init. This service will be used
314 during the session. The service may have its own target settings,
315 ICU config, timeout, etc. In order to be recognized, the POST request
316 must use Content-Type=text/xml.
318 Timeout values may be given per-service. That's element 'timeout'
319 which takes three attribute values (a subset may be given): 'session',
320 'z3950_operation', 'z3950_session'. Option -T is no longer supported
321 - used to specify session timeout.
323 Option -t tests the Pazpar2 configuration and returns exit code
324 (0=success, non-zero=failure). In previous version of Pazpar2, -t
325 specified local settings.
327 In version 1.2.0 the configuration file - after include processing -
328 was dumped to stdout. Now, the configuration is only dumped to the
329 yaz log file if option -d is given.
333 Configuration may now have multiple server areas. This means that a
334 Pazpar2 instance may listen on multiple ports. Virtual hosting is not
335 yet supported - on a server basis. Configuration may also have multiple
336 services .. That is repeating service elements inside a server. Each
337 has an attribute 'id' which serves as service ID. This ID in turn may
338 be used in a Pazpar2 session, by specifying parameter service=ID for
339 command init. There can be at most one unnamed service inside a server
340 which can be referred to by not specifying an service ID for command
341 init (backwards compatible). In order to partition multiple servers and
342 services a new include directive has been added. This takes an attribute
343 'src' which specifies one or more sub-files. For example to include
344 service files, one might use:
345 <server >.. <include src=/"etc/pazpar2/conf.d/*.xml"/> .. </server>.
346 It is the intention that that completely makes the settings directive
349 Fix problem where the record command would wait forever if there were
350 no targets to wait for (activeclients == 0).
354 One result set is created per session (last search) rather than for
355 each connection which happen to be shared (bug #3009).
357 marc21 stylesheets changed for efficiency.
361 Session timeout may be specified on the command-line as option -T.
363 Pazpar2 may now be operated in a no-merged mode for records.. All records
364 will be considered unique. This mode is enabled if no mergekey is
365 generated by the normalization stylesheet (pz:xslt).
367 Pazpar2 caches original records from each target and the 'record' command
368 with offset returns the original record if 'syntax' and 'esn' are NOT
369 specified. This speeds up retrieval of original records but also means
370 that Pazpar2 uses more memory. The cached records will be freed when the
371 session terminates or a new search is executed.
373 Pazpar2 no longer uses its own ICU wrapper. Instead the ICU wrapper
374 library part of YAZ is used.
376 Added SRU client support.
378 Automatically computes pz:nativesyntax if not provided. Works for XML and
381 --- 1.0.13 2008/11/24
383 Command bytarget returns name of target (if defined).
385 --- 1.0.12 2008/11/04
387 Fixed bug #2021.. location now holds all brief elements.
389 --- 1.0.11 2008/10/15
391 Fixed check for application/x-www-form-urlencoded parameters.
393 --- 1.0.10 2008/10/14
395 Fixes for IE in pz2.js.
397 Fixed bug #2021: non-merged, brief meta data NOT included for command=show.
401 Changed the JS library pz2.js to use POST for long URL (+ params).
403 Added installation instructions for Windows. Note: NT services is
404 NOT available until we make a new release of YAZ.
406 Preserve order of repeated metadata fields (they were reversed before).
408 More MARC21 information extracted for metadata.
412 Fixed bug #1162: HTML entities are not escaped properly.
414 Native Windows port of Pazpar2. Makefile for Visual Studio provided.
418 Marc21 stylesheet updated to reflect multiple full text fields
422 Fixed bug in pz2.js WRT DOMElement attributes on IE.
424 Fixed bug 2100: Database wildcards not working
428 Added support for retrieval of records in binary.
430 Fixed bug 1794: Pazpar2 does not return valid XML.
432 Deal with ICU not returning sortkey (resulted in SEGV before).
436 JavaScript library pzw2.js throws error if WS response (from Pazpar2 or
437 other) is malformed (non-wellformed XML or missing Pazpar2 OK status).
439 Improved diagnostics when Pazpar2 HTTP decoding fails.
441 Pazpar2 requests may be POSTed as using Content-Type
442 application/x-www-form-urlencoded.
444 Pazpar2 honors LF in HTTP headers.
446 Handle targets that handle negative hit counts (should not happen, but it
451 ICU is used for tokenization and normalization of the following: mergekey,
452 sorting, relevance terms.
454 Debian package now enables ICU tokenization and normalization by default.
458 Exposed user setting values (i.e. non-pz: names) to the record systems in two
459 ways: Either as parameters to the normalization stylesheets (which would allow the
460 programmer to postprocess or use the values in any way) or after the normalization
461 step, in which case values are made part of the normalized record (and available for
462 sorting, termlists, display, or other interface-related use.
464 Implemented sorting by year.
466 Option -d dumps records to the current log file instead of stderr.
468 Fixes for compilation on cygwin.
470 Z39.50 client code uses pz:elements. pz:elements was recognized in
471 earlier Pazpar2 versions but it was not used for anything.
473 icu_chain_test is using fgets instead of getline - fixes compilation
476 Loosen the CCL query parsing so that Pazpar2 only returns error if _all_
477 query conversions fail (rather than _any_). This means targets that do
478 not support some fields are ignored in a search.
482 Improved handling of socket timeout for Z39.50 connections.
484 Misc documentation updates and spell fixes.
486 Debian package pazpar2 creates log rotate entry.
488 Debian package pazpar2-apache2 reloads Apache2.
490 jsdemo included in distribution. It illustrates the use of the js/pz2.js
495 First public release.