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