5 Applied patch from Giannis Kosmas on keepAlive, which also adds keepAlive to init response.
7 Lower log level some places.
9 Remove some invalid test results.
13 Introducing a version=2 parameter for show, termlist and bytarget commands.
14 This enables pazpar2 to return approximation on hit and count count when
15 doing record filtering using the limit parameter on search and a
16 limitmap with a value of "local:"
18 Setting pz:xslt may embed local XSLT as an alternative to referring
20 Value is not CDATA but XML nodes embedded, so escaping is not necessary
21 but a root element *must* be present. For example:
22 <settings target="target="z3950.indexdata.com/marc">
31 Metadata field rank may given by XML internal document (pz:xslt
32 result). If rank is not given, the rank from service description is
35 Metadata field can now configured a default limitmap and facetmap.
36 Setting limitmap to "local:" would work for all kind of targets, but would
37 prob. not be the optimal solution. But at least better than the default behavior
38 of pazpar2 where no filtering is done.
40 A service definition can now also contains <set/> that defines service-wide
41 settings. These will override server-wide sets and will be overridded by
44 New setting, pz:present_chunk, that specifies number of records to fetch
45 at a time. Zero will disable chunkation; will fetch max_records at once.
49 Revert the format change in termlist response, that could break
50 some clients / UIs since they were expecting an (empty) element
51 if no facet values was found.
55 Revert the behavior of returning errors when unable to block
56 on termlist, bytarget and search, when unable to block due to
57 other block. The client will now receive a regular response,
58 but it will be logged in the server. A parameter (report) is
59 added to change behavior to return error response or WARNING
60 status message. Consider this "API" as private, as it is mostly
61 untested and could be changed in future releases.
63 Fix spell error in pz2.js fix in 1.6.10.
65 New Marc2TurboMarc.xsl (contribution from Sven Porst).
66 Can solve the missing marc21.xsl updates in some cases.
68 tmarc.xsl: Simplify the 6xx to subject-long and fix 1-based
69 substring (contribtion from Sven Porst)
71 marc21.xsl: fix 1-based substring call
73 tmarc.xsl and marc21.xsl: use 856$a as last option for electronic-text.
75 Add test_termlist_block to test suite
79 Fix SEGV for invalid PQFs and SRU/SOLR targets
80 Also refactor a bit the code that converts from PQF to SRU/SOLR queries.
82 Fix pz2.js: "null object" due to change in in bytarget result XML.
84 Fixes in tmarc.xsl: Subject-long shorten for extra commas only.
85 Added this normalization to the other subject-long fields (d6xx),
88 Fixes in marc21.xsl: Updated with most of the new tmarc.xsl.
89 Still differences around medium and holdings. marc21.xsl is not
90 longer active used by Index Data, and should be considered unsupported.
91 Use tmarc.xsl instead.
95 Fix SEGV that could occur for failed connections.
99 Fix bug for command sort that could return no results for active clients
100 (from previous search). This bug was present in 1.6.6-1.6.7.
102 Fix bug in results that could include results that should have been
103 filtered out. This bug was present in 1.6.6-1.6.7.
107 Fix bug introduced in 1.6.6 where a connection re-use could stall
110 Local filtering may now specify a local metadata field, eg.
111 pz:limitmap:somefield[t]=local:otherfield
115 For search, when limit and or filtering is in place and search
116 is identical to previous search, the result set is re-used and the
117 target is not searched.
119 Limits may work perform local filtering as well, by using "local:"
124 Updated bytarget command to contain a suggestions element with misspelled
125 words and suggestions to these. pz2.js has been updated to deliver this
126 onwards as well. Only target that currently delivers this is the solr
127 client in YAZ 4.2.18.
131 New service definition element, xslt, that allows an embedded stylesheet
132 to be defined. This can be referred to from pz:xslt as an alternative to
135 New pz:sortmap:field setting for specifying hints on how to make
136 a target natively sort on a field. This is used for command=show in
137 conjunction with sort.
139 New pz:url setting for specifying the actual URL for a target. When
140 this is used the target ID is not used as URL anymore and the target ID
141 may be almost any string (not including []).
143 command=termlist without name parameter returns all termlists/facets.
144 Previously if name parameter was omitted, only "subject" was returned.
148 Make termlist sorting stable. Terms with same frequency are now sorted by
149 their display name. This makes a pretty display and improves our
150 regression test because qsort is not a stable sort.
152 New sort parameter value 'position'. The 'position' sorts merged records
153 by their original position from the remote target. This is primarily useful
154 for debugging and may be used for targets that already perform some kind
155 of relevance ranking. Note that sort by default is decreasing; so to get
156 records in their original order sort=position:1 must be used.
160 tmarc.xsl: yet another 773$g fix. Was broken in 1.6.1 as well.
162 Facility to change working directory for pazpar2 daemon. Option -wdir
163 sets working directory to dir. This facility is useful if core dumps
164 must be saved. In this case, the current working directory must be
165 writable by the running user, such as "nobody".
169 New configuration element <icu_chain> for <server>/<service> which
170 allows a named ICU rule (chain) to be defined. The names relevance,
171 sort, mergekey and facet are used for those operations. The definition
172 <icu_chain id="sort" locale="en"> .. </icu_chain>
174 <sort> <icu_chain locale="en> ... </icu_chain> </sort>
175 And so on.. for relevance, mergekey and facet as well. The latter
176 style is deprecated. The facet terms are normalized by the facet
177 rule by default. This may be changed on a metadata field basis by
178 defining the new attribute 'facetrule' for the metadata element.
180 <icu_chain id="myrule" locale="en"> ... </icu_chain>
181 <metadata name="author" termlist="yes" facetrule="myrule"/>
183 Preserve rorder for merged metadata. Fixes issue as reported by Sven
184 Porst: http://lists.indexdata.dk/pipermail/yazlist/2011-July/003230.html
186 tmarc.xsl: set journal-subpart to 773$ only.
190 Modify the behavior for the limit parameter (first defined in 1.5.7).
191 Mapping of limit searches are now defined by the new configuration item
192 pz:limitmap. Fix a dead-lock problem with the limit parameter.
194 Extend tmarc.xsl to extract 773$g data (OpenURL).
198 ICU default maps remove backquote (`).
200 Command 'search' takes limit parameter (optional). The limit parameter
201 allows a search to be limited one or more facets and the corresponding
202 values. This is for server side filtering.
204 Configure tweak: Use -lm for log(3) if needed
208 Fix a problem with skiparticle sortkey that could be completely
209 ignored (and reduced to "").
211 Fix dependency problem in pazpar2 RPM package (did not require
212 libyaz4 as it should).
216 Fix memory leak that occurred for command=termlist&name=xtargets .
218 Pazpar2 may save HTTP requests. Enabled by option -R.
222 Experimental support for DTIC DADS target. New dads-pz2.xsl.
224 Support for query_syntax (overrides the default for SRU | Z39.50)
226 Support for extraArgs (ZOOM "extraArgs" option) for targets
228 New commands: status-server and status-session
232 Fix for threaded runs: Client now have a copy of the database URL,
233 which can used after the database has been release from the client.
234 This makes the logging in the connection idle timeout of the client nicer (no NOURL) and should be thread-safe.
236 tmarc.xsl: Add journal-title-abbrev and full text.
238 cf.xsl: new fields: isbn, issn, journaltitle, volume, issue
240 Fix for cmd=record before search.
242 Session Logging clean up.
244 Fix wrong termlist factor when maxrecs is different from 100.
248 Fix missing pz:termlist_term_factor in settings.c messed up pz:preferred.
249 Term factor is default enabled but can be diseabled by
250 pz:termlist_term_factor=0
254 Add scaling of facet count. Currently always enabled, needs fixing.
255 Allow user-defined info for target suffix. This has no meaning in
256 Pazpar2 except to distinguish targets from each other. The suffix
257 data begins with #. For example z3950.indexdata.com/gils#Mydata
259 Added exact-match recordfilter; format name=value
263 SOLR support. Pazpar2 may operate as web service client for SOLR.
267 Fix for show command and block=1 (dead lock). Bug was introduced in
272 New RPM packages: pazpar2, pazpar2-js, pazpar2-doc. These have been
273 tested on CentOS 5.5 only.
277 Fix problem with result sets being removed from a client session
278 if the connection for it was resused by another session. Bug #3489.
280 New iphone UI for Pazpar2 (www/iphone).
284 Fixes for threaded operation.
286 New stylesheets for TurboMARC: tmarc.xsl and opac_turbomarc.xsl.
288 New example services in etc/services in source. In the Debian packages
289 these are located in /etc/pazpar2/services-available
291 Threaded mode operational on Windows. Requires Windows 7 or Windows
294 Default value of setting pz:max_connections is 0 which means that there
295 is no limit on number of connections.
299 Pazpar2 may operate in threaded mode. Enabled by element threads in
300 the configuration. See pazpar2_conf for details.
302 New setting setting: pz:max_connections. Setting pz:max_connections is
303 a limit of number of sockets to a host. When this limit is reached,
304 Pazpar2 will wait up to 5 seconds for a connection to becomes available.
305 The client will be marked Client_Error when it can not be searched
306 (other clients in a session may work). If pz:max_connections is not set
307 for a target, a value of 30 will be used. Note: the pz:max_connections
308 will only work in threaded mode.
310 pz2.js: JSON support for show.
312 Debian package: Enable default service, default.xml, before starting
313 Pazpar2 only if there is no service already in /etc/pazpar2/services-enabled.
317 Debian version depends on on libyaz4. Note that Pazpar2 will still
318 compile from source with YAZ 3.
320 Split services into separate files. The example configuration file
321 pazpar2.cfg.dist now includes a default service default.xml (part of
322 etc). And default.xml includes settings/edu.xml. The default.xml file,
323 not to be confused with settings/defaults.xml, is a template for jsdemo
324 and other services. The Debian package installs /etc/pazpar2/server.xml
325 which is now the main pazpar2 configuration (used to be called pazpar2.cfg).
326 server.xml includes services from /etc/pazpar2/services-enabled/*.xml .
327 The default.xml (from etc) is installed in /etc/pazpar2/services-available
328 and a symlink to it is created from services-enabled. The default.xml
329 service is unnamed and, thus, will be used by jsdemo and test1.
331 New setting pz:negotiation_charset. Patch from Andrei V. Toutoukine. The
332 new setting pz:negotiation_charset specifies character set for Z39.50 Init.
336 Support for additional fields in cf.xsl and pazpar2.conf.dist:
337 publisher, available, due, location (=locallocation), callno
338 (=callnumber), thumburl and score.
340 Describe pz:xslt and the auto setting.
342 Move mergekey definition away from the normalization stylesheets and
343 define a mergekey common for all target types in pazpar2.cfg.
345 Code update: Use the Odr_int type for hit counts. This is part of
346 YAZ 3.0.47 and later and so configure checks for that.
350 Metadata attribute 'skiparticle' also works for ICU based
351 normalization. (was only working for the non-ICU/ASCII before).
353 Command bytarget with argument settings=1 will show settings per
354 target.. This is to be able to verify correct settings and be able to
355 test that they are correct. The database settings array size is now
356 also stored.. Problems with database settings array is that if not
357 careful it will be too small (smaller than dictionary per-service
360 Make record list sorting stable by comparing mergekey for records if
361 relevance/title or other sorting criteria all match. This is merely to
362 ensure that our regressions tests works (reproducible output).
364 Relevance calculation changes: use a different denominator (length) for
365 per-field relevance scoring.. Instead of length of all ranked fields we
366 now use length of individual fields (as if they were individual "free"
367 text fields). This will ensure that documents with a long field with no
368 match (say description) will not "hurt" a title match.
370 Diagnostic member was not set on connection error. Fixed
374 Command search takes two optional parameters, startecs and maxrecs,
375 that specifies the start offset (0, 1, ...) and maximum number of records
376 to fetch for each target.
378 XSLTs + MARC maps are cached within a session so we don't re-parse
379 them over and over again. Even for a session with a single search
380 there's much to be gained because many targets use the same
383 The metadata attribute 'mergekey' now takes one of three values 'no',
384 'required', 'optional' . And the resulting mergekey from metadata
385 is now ordered in the same way as metadata in the service definition.
386 Older Pazpar2 version use the order in which metadata appeared in a
389 The search argument 'filter' now offers a new operator ~ which does a
390 substring match. The = operator works as before: string match for
391 anything but pz:id, or target match for pz:id.
393 New setting pz:recordfilter. The value of this setting takes the
394 form name[~value]. This setting makes Pazpar2 ignore all retrieved
395 records that do not have the metadata element name with value substring
398 Pazpar2 allows YAZ log level to be set (option -v).
402 For WS responses Pazpar2 creates XML header. Exception: raw record.
404 Setting XML files are now stored in etc/settings instead of etc. This
405 reflects the layout with the Debian package layout.
407 Settings may be posted for command=settings. The POSTed settings must
408 have root element 'settings' like regular setting files. In order to be
409 recognized, the POST request must use Content-Type=text/xml.
411 A service may be posted for command=init. This service will be used
412 during the session. The service may have its own target settings,
413 ICU config, timeout, etc. In order to be recognized, the POST request
414 must use Content-Type=text/xml.
416 Timeout values may be given per-service. That's element 'timeout'
417 which takes three attribute values (a subset may be given): 'session',
418 'z3950_operation', 'z3950_session'. Option -T is no longer supported
419 - used to specify session timeout.
421 Option -t tests the Pazpar2 configuration and returns exit code
422 (0=success, non-zero=failure). In previous version of Pazpar2, -t
423 specified local settings.
425 In version 1.2.0 the configuration file - after include processing -
426 was dumped to stdout. Now, the configuration is only dumped to the
427 yaz log file if option -d is given.
431 Configuration may now have multiple server areas. This means that a
432 Pazpar2 instance may listen on multiple ports. Virtual hosting is not
433 yet supported - on a server basis. Configuration may also have multiple
434 services .. That is repeating service elements inside a server. Each
435 has an attribute 'id' which serves as service ID. This ID in turn may
436 be used in a Pazpar2 session, by specifying parameter service=ID for
437 command init. There can be at most one unnamed service inside a server
438 which can be referred to by not specifying an service ID for command
439 init (backwards compatible). In order to partition multiple servers and
440 services a new include directive has been added. This takes an attribute
441 'src' which specifies one or more sub-files. For example to include
442 service files, one might use:
443 <server >.. <include src=/"etc/pazpar2/conf.d/*.xml"/> .. </server>.
444 It is the intention that that completely makes the settings directive
447 Fix problem where the record command would wait forever if there were
448 no targets to wait for (activeclients == 0).
452 One result set is created per session (last search) rather than for
453 each connection which happen to be shared (bug #3009).
455 marc21 stylesheets changed for efficiency.
459 Session timeout may be specified on the command-line as option -T.
461 Pazpar2 may now be operated in a no-merged mode for records.. All records
462 will be considered unique. This mode is enabled if no mergekey is
463 generated by the normalization stylesheet (pz:xslt).
465 Pazpar2 caches original records from each target and the 'record' command
466 with offset returns the original record if 'syntax' and 'esn' are NOT
467 specified. This speeds up retrieval of original records but also means
468 that Pazpar2 uses more memory. The cached records will be freed when the
469 session terminates or a new search is executed.
471 Pazpar2 no longer uses its own ICU wrapper. Instead the ICU wrapper
472 library part of YAZ is used.
474 Added SRU client support.
476 Automatically computes pz:nativesyntax if not provided. Works for XML and
479 --- 1.0.13 2008/11/24
481 Command bytarget returns name of target (if defined).
483 --- 1.0.12 2008/11/04
485 Fixed bug #2021.. location now holds all brief elements.
487 --- 1.0.11 2008/10/15
489 Fixed check for application/x-www-form-urlencoded parameters.
491 --- 1.0.10 2008/10/14
493 Fixes for IE in pz2.js.
495 Fixed bug #2021: non-merged, brief meta data NOT included for command=show.
499 Changed the JS library pz2.js to use POST for long URL (+ params).
501 Added installation instructions for Windows. Note: NT services is
502 NOT available until we make a new release of YAZ.
504 Preserve order of repeated metadata fields (they were reversed before).
506 More MARC21 information extracted for metadata.
510 Fixed bug #1162: HTML entities are not escaped properly.
512 Native Windows port of Pazpar2. Makefile for Visual Studio provided.
516 Marc21 stylesheet updated to reflect multiple full text fields
520 Fixed bug in pz2.js WRT DOMElement attributes on IE.
522 Fixed bug 2100: Database wildcards not working
526 Added support for retrieval of records in binary.
528 Fixed bug 1794: Pazpar2 does not return valid XML.
530 Deal with ICU not returning sortkey (resulted in SEGV before).
534 JavaScript library pzw2.js throws error if WS response (from Pazpar2 or
535 other) is malformed (non-wellformed XML or missing Pazpar2 OK status).
537 Improved diagnostics when Pazpar2 HTTP decoding fails.
539 Pazpar2 requests may be POSTed as using Content-Type
540 application/x-www-form-urlencoded.
542 Pazpar2 honors LF in HTTP headers.
544 Handle targets that handle negative hit counts (should not happen, but it
549 ICU is used for tokenization and normalization of the following: mergekey,
550 sorting, relevance terms.
552 Debian package now enables ICU tokenization and normalization by default.
556 Exposed user setting values (i.e. non-pz: names) to the record systems in two
557 ways: Either as parameters to the normalization stylesheets (which would allow the
558 programmer to postprocess or use the values in any way) or after the normalization
559 step, in which case values are made part of the normalized record (and available for
560 sorting, termlists, display, or other interface-related use.
562 Implemented sorting by year.
564 Option -d dumps records to the current log file instead of stderr.
566 Fixes for compilation on cygwin.
568 Z39.50 client code uses pz:elements. pz:elements was recognized in
569 earlier Pazpar2 versions but it was not used for anything.
571 icu_chain_test is using fgets instead of getline - fixes compilation
574 Loosen the CCL query parsing so that Pazpar2 only returns error if _all_
575 query conversions fail (rather than _any_). This means targets that do
576 not support some fields are ignored in a search.
580 Improved handling of socket timeout for Z39.50 connections.
582 Misc documentation updates and spell fixes.
584 Debian package pazpar2 creates log rotate entry.
586 Debian package pazpar2-apache2 reloads Apache2.
588 jsdemo included in distribution. It illustrates the use of the js/pz2.js
593 First public release.