3 Fix bad re-use of connections (connections with changing proxy should not
8 Fix a bug introduce in 1.6.15 around the position sorting. It resetted the
9 resultset and sorting when the sort order is position. However this will be done on
10 every client poll, which will make pazpar2 continuing reset and fetching.
11 It should only be done on FIRST request where the sort order change.
13 Fix an issue on suggestion option: Also disable suggestions on empty string.
15 Clean up in turbo marc stylesheet.
17 Remove the hardcoded size of termlists.
21 New facility: ccldirective may be given in service definition. Allows
22 CCL parsing to be customized a bit, such as defining names of operators
25 New facility: raw record by checksum, rather than offset. The record
26 command optionally takes checksum which identifies certain record from
29 New facility: per field ranking. Rank may be given as M [F N] where
30 M is default rank and N is rank for CCL terms from field F.
34 Fix for IE7/8 in pz.js
36 Applied patch from Giannis Kosmas on keepAlive, which also adds keepAlive to init response.
38 Lower log level some places.
40 Remove some invalid test results.
44 Introducing a version=2 parameter for show, termlist and bytarget commands.
45 This enables pazpar2 to return approximation on hit and count count when
46 doing record filtering using the limit parameter on search and a
47 limitmap with a value of "local:"
49 Setting pz:xslt may embed local XSLT as an alternative to referring
51 Value is not CDATA but XML nodes embedded, so escaping is not necessary
52 but a root element *must* be present. For example:
53 <settings target="target="z3950.indexdata.com/marc">
62 Metadata field rank may given by XML internal document (pz:xslt
63 result). If rank is not given, the rank from service description is
66 Metadata field can now configured a default limitmap and facetmap.
67 Setting limitmap to "local:" would work for all kind of targets, but would
68 prob. not be the optimal solution. But at least better than the default behavior
69 of pazpar2 where no filtering is done.
71 A service definition can now also contains <set/> that defines service-wide
72 settings. These will override server-wide sets and will be overridded by
75 New setting, pz:present_chunk, that specifies number of records to fetch
76 at a time. Zero will disable chunkation; will fetch max_records at once.
80 Revert the format change in termlist response, that could break
81 some clients / UIs since they were expecting an (empty) element
82 if no facet values was found.
86 Revert the behavior of returning errors when unable to block
87 on termlist, bytarget and search, when unable to block due to
88 other block. The client will now receive a regular response,
89 but it will be logged in the server. A parameter (report) is
90 added to change behavior to return error response or WARNING
91 status message. Consider this "API" as private, as it is mostly
92 untested and could be changed in future releases.
94 Fix spell error in pz2.js fix in 1.6.10.
96 New Marc2TurboMarc.xsl (contribution from Sven Porst).
97 Can solve the missing marc21.xsl updates in some cases.
99 tmarc.xsl: Simplify the 6xx to subject-long and fix 1-based
100 substring (contribtion from Sven Porst)
102 marc21.xsl: fix 1-based substring call
104 tmarc.xsl and marc21.xsl: use 856$a as last option for electronic-text.
106 Add test_termlist_block to test suite
108 --- 1.6.10 2012/02/23
110 Fix SEGV for invalid PQFs and SRU/SOLR targets
111 Also refactor a bit the code that converts from PQF to SRU/SOLR queries.
113 Fix pz2.js: "null object" due to change in in bytarget result XML.
115 Fixes in tmarc.xsl: Subject-long shorten for extra commas only.
116 Added this normalization to the other subject-long fields (d6xx),
117 where it was missing.
119 Fixes in marc21.xsl: Updated with most of the new tmarc.xsl.
120 Still differences around medium and holdings. marc21.xsl is not
121 longer active used by Index Data, and should be considered unsupported.
122 Use tmarc.xsl instead.
126 Fix SEGV that could occur for failed connections.
130 Fix bug for command sort that could return no results for active clients
131 (from previous search). This bug was present in 1.6.6-1.6.7.
133 Fix bug in results that could include results that should have been
134 filtered out. This bug was present in 1.6.6-1.6.7.
138 Fix bug introduced in 1.6.6 where a connection re-use could stall
141 Local filtering may now specify a local metadata field, eg.
142 pz:limitmap:somefield[t]=local:otherfield
146 For search, when limit and or filtering is in place and search
147 is identical to previous search, the result set is re-used and the
148 target is not searched.
150 Limits may work perform local filtering as well, by using "local:"
155 Updated bytarget command to contain a suggestions element with misspelled
156 words and suggestions to these. pz2.js has been updated to deliver this
157 onwards as well. Only target that currently delivers this is the solr
158 client in YAZ 4.2.18.
162 New service definition element, xslt, that allows an embedded stylesheet
163 to be defined. This can be referred to from pz:xslt as an alternative to
166 New pz:sortmap:field setting for specifying hints on how to make
167 a target natively sort on a field. This is used for command=show in
168 conjunction with sort.
170 New pz:url setting for specifying the actual URL for a target. When
171 this is used the target ID is not used as URL anymore and the target ID
172 may be almost any string (not including []).
174 command=termlist without name parameter returns all termlists/facets.
175 Previously if name parameter was omitted, only "subject" was returned.
179 Make termlist sorting stable. Terms with same frequency are now sorted by
180 their display name. This makes a pretty display and improves our
181 regression test because qsort is not a stable sort.
183 New sort parameter value 'position'. The 'position' sorts merged records
184 by their original position from the remote target. This is primarily useful
185 for debugging and may be used for targets that already perform some kind
186 of relevance ranking. Note that sort by default is decreasing; so to get
187 records in their original order sort=position:1 must be used.
191 tmarc.xsl: yet another 773$g fix. Was broken in 1.6.1 as well.
193 Facility to change working directory for pazpar2 daemon. Option -wdir
194 sets working directory to dir. This facility is useful if core dumps
195 must be saved. In this case, the current working directory must be
196 writable by the running user, such as "nobody".
200 New configuration element <icu_chain> for <server>/<service> which
201 allows a named ICU rule (chain) to be defined. The names relevance,
202 sort, mergekey and facet are used for those operations. The definition
203 <icu_chain id="sort" locale="en"> .. </icu_chain>
205 <sort> <icu_chain locale="en> ... </icu_chain> </sort>
206 And so on.. for relevance, mergekey and facet as well. The latter
207 style is deprecated. The facet terms are normalized by the facet
208 rule by default. This may be changed on a metadata field basis by
209 defining the new attribute 'facetrule' for the metadata element.
211 <icu_chain id="myrule" locale="en"> ... </icu_chain>
212 <metadata name="author" termlist="yes" facetrule="myrule"/>
214 Preserve rorder for merged metadata. Fixes issue as reported by Sven
215 Porst: http://lists.indexdata.dk/pipermail/yazlist/2011-July/003230.html
217 tmarc.xsl: set journal-subpart to 773$ only.
221 Modify the behavior for the limit parameter (first defined in 1.5.7).
222 Mapping of limit searches are now defined by the new configuration item
223 pz:limitmap. Fix a dead-lock problem with the limit parameter.
225 Extend tmarc.xsl to extract 773$g data (OpenURL).
229 ICU default maps remove backquote (`).
231 Command 'search' takes limit parameter (optional). The limit parameter
232 allows a search to be limited one or more facets and the corresponding
233 values. This is for server side filtering.
235 Configure tweak: Use -lm for log(3) if needed
239 Fix a problem with skiparticle sortkey that could be completely
240 ignored (and reduced to "").
242 Fix dependency problem in pazpar2 RPM package (did not require
243 libyaz4 as it should).
247 Fix memory leak that occurred for command=termlist&name=xtargets .
249 Pazpar2 may save HTTP requests. Enabled by option -R.
253 Experimental support for DTIC DADS target. New dads-pz2.xsl.
255 Support for query_syntax (overrides the default for SRU | Z39.50)
257 Support for extraArgs (ZOOM "extraArgs" option) for targets
259 New commands: status-server and status-session
263 Fix for threaded runs: Client now have a copy of the database URL,
264 which can used after the database has been release from the client.
265 This makes the logging in the connection idle timeout of the client nicer (no NOURL) and should be thread-safe.
267 tmarc.xsl: Add journal-title-abbrev and full text.
269 cf.xsl: new fields: isbn, issn, journaltitle, volume, issue
271 Fix for cmd=record before search.
273 Session Logging clean up.
275 Fix wrong termlist factor when maxrecs is different from 100.
279 Fix missing pz:termlist_term_factor in settings.c messed up pz:preferred.
280 Term factor is default enabled but can be diseabled by
281 pz:termlist_term_factor=0
285 Add scaling of facet count. Currently always enabled, needs fixing.
286 Allow user-defined info for target suffix. This has no meaning in
287 Pazpar2 except to distinguish targets from each other. The suffix
288 data begins with #. For example z3950.indexdata.com/gils#Mydata
290 Added exact-match recordfilter; format name=value
294 SOLR support. Pazpar2 may operate as web service client for SOLR.
298 Fix for show command and block=1 (dead lock). Bug was introduced in
303 New RPM packages: pazpar2, pazpar2-js, pazpar2-doc. These have been
304 tested on CentOS 5.5 only.
308 Fix problem with result sets being removed from a client session
309 if the connection for it was resused by another session. Bug #3489.
311 New iphone UI for Pazpar2 (www/iphone).
315 Fixes for threaded operation.
317 New stylesheets for TurboMARC: tmarc.xsl and opac_turbomarc.xsl.
319 New example services in etc/services in source. In the Debian packages
320 these are located in /etc/pazpar2/services-available
322 Threaded mode operational on Windows. Requires Windows 7 or Windows
325 Default value of setting pz:max_connections is 0 which means that there
326 is no limit on number of connections.
330 Pazpar2 may operate in threaded mode. Enabled by element threads in
331 the configuration. See pazpar2_conf for details.
333 New setting setting: pz:max_connections. Setting pz:max_connections is
334 a limit of number of sockets to a host. When this limit is reached,
335 Pazpar2 will wait up to 5 seconds for a connection to becomes available.
336 The client will be marked Client_Error when it can not be searched
337 (other clients in a session may work). If pz:max_connections is not set
338 for a target, a value of 30 will be used. Note: the pz:max_connections
339 will only work in threaded mode.
341 pz2.js: JSON support for show.
343 Debian package: Enable default service, default.xml, before starting
344 Pazpar2 only if there is no service already in /etc/pazpar2/services-enabled.
348 Debian version depends on on libyaz4. Note that Pazpar2 will still
349 compile from source with YAZ 3.
351 Split services into separate files. The example configuration file
352 pazpar2.cfg.dist now includes a default service default.xml (part of
353 etc). And default.xml includes settings/edu.xml. The default.xml file,
354 not to be confused with settings/defaults.xml, is a template for jsdemo
355 and other services. The Debian package installs /etc/pazpar2/server.xml
356 which is now the main pazpar2 configuration (used to be called pazpar2.cfg).
357 server.xml includes services from /etc/pazpar2/services-enabled/*.xml .
358 The default.xml (from etc) is installed in /etc/pazpar2/services-available
359 and a symlink to it is created from services-enabled. The default.xml
360 service is unnamed and, thus, will be used by jsdemo and test1.
362 New setting pz:negotiation_charset. Patch from Andrei V. Toutoukine. The
363 new setting pz:negotiation_charset specifies character set for Z39.50 Init.
367 Support for additional fields in cf.xsl and pazpar2.conf.dist:
368 publisher, available, due, location (=locallocation), callno
369 (=callnumber), thumburl and score.
371 Describe pz:xslt and the auto setting.
373 Move mergekey definition away from the normalization stylesheets and
374 define a mergekey common for all target types in pazpar2.cfg.
376 Code update: Use the Odr_int type for hit counts. This is part of
377 YAZ 3.0.47 and later and so configure checks for that.
381 Metadata attribute 'skiparticle' also works for ICU based
382 normalization. (was only working for the non-ICU/ASCII before).
384 Command bytarget with argument settings=1 will show settings per
385 target.. This is to be able to verify correct settings and be able to
386 test that they are correct. The database settings array size is now
387 also stored.. Problems with database settings array is that if not
388 careful it will be too small (smaller than dictionary per-service
391 Make record list sorting stable by comparing mergekey for records if
392 relevance/title or other sorting criteria all match. This is merely to
393 ensure that our regressions tests works (reproducible output).
395 Relevance calculation changes: use a different denominator (length) for
396 per-field relevance scoring.. Instead of length of all ranked fields we
397 now use length of individual fields (as if they were individual "free"
398 text fields). This will ensure that documents with a long field with no
399 match (say description) will not "hurt" a title match.
401 Diagnostic member was not set on connection error. Fixed
405 Command search takes two optional parameters, startecs and maxrecs,
406 that specifies the start offset (0, 1, ...) and maximum number of records
407 to fetch for each target.
409 XSLTs + MARC maps are cached within a session so we don't re-parse
410 them over and over again. Even for a session with a single search
411 there's much to be gained because many targets use the same
414 The metadata attribute 'mergekey' now takes one of three values 'no',
415 'required', 'optional' . And the resulting mergekey from metadata
416 is now ordered in the same way as metadata in the service definition.
417 Older Pazpar2 version use the order in which metadata appeared in a
420 The search argument 'filter' now offers a new operator ~ which does a
421 substring match. The = operator works as before: string match for
422 anything but pz:id, or target match for pz:id.
424 New setting pz:recordfilter. The value of this setting takes the
425 form name[~value]. This setting makes Pazpar2 ignore all retrieved
426 records that do not have the metadata element name with value substring
429 Pazpar2 allows YAZ log level to be set (option -v).
433 For WS responses Pazpar2 creates XML header. Exception: raw record.
435 Setting XML files are now stored in etc/settings instead of etc. This
436 reflects the layout with the Debian package layout.
438 Settings may be posted for command=settings. The POSTed settings must
439 have root element 'settings' like regular setting files. In order to be
440 recognized, the POST request must use Content-Type=text/xml.
442 A service may be posted for command=init. This service will be used
443 during the session. The service may have its own target settings,
444 ICU config, timeout, etc. In order to be recognized, the POST request
445 must use Content-Type=text/xml.
447 Timeout values may be given per-service. That's element 'timeout'
448 which takes three attribute values (a subset may be given): 'session',
449 'z3950_operation', 'z3950_session'. Option -T is no longer supported
450 - used to specify session timeout.
452 Option -t tests the Pazpar2 configuration and returns exit code
453 (0=success, non-zero=failure). In previous version of Pazpar2, -t
454 specified local settings.
456 In version 1.2.0 the configuration file - after include processing -
457 was dumped to stdout. Now, the configuration is only dumped to the
458 yaz log file if option -d is given.
462 Configuration may now have multiple server areas. This means that a
463 Pazpar2 instance may listen on multiple ports. Virtual hosting is not
464 yet supported - on a server basis. Configuration may also have multiple
465 services .. That is repeating service elements inside a server. Each
466 has an attribute 'id' which serves as service ID. This ID in turn may
467 be used in a Pazpar2 session, by specifying parameter service=ID for
468 command init. There can be at most one unnamed service inside a server
469 which can be referred to by not specifying an service ID for command
470 init (backwards compatible). In order to partition multiple servers and
471 services a new include directive has been added. This takes an attribute
472 'src' which specifies one or more sub-files. For example to include
473 service files, one might use:
474 <server >.. <include src=/"etc/pazpar2/conf.d/*.xml"/> .. </server>.
475 It is the intention that that completely makes the settings directive
478 Fix problem where the record command would wait forever if there were
479 no targets to wait for (activeclients == 0).
483 One result set is created per session (last search) rather than for
484 each connection which happen to be shared (bug #3009).
486 marc21 stylesheets changed for efficiency.
490 Session timeout may be specified on the command-line as option -T.
492 Pazpar2 may now be operated in a no-merged mode for records.. All records
493 will be considered unique. This mode is enabled if no mergekey is
494 generated by the normalization stylesheet (pz:xslt).
496 Pazpar2 caches original records from each target and the 'record' command
497 with offset returns the original record if 'syntax' and 'esn' are NOT
498 specified. This speeds up retrieval of original records but also means
499 that Pazpar2 uses more memory. The cached records will be freed when the
500 session terminates or a new search is executed.
502 Pazpar2 no longer uses its own ICU wrapper. Instead the ICU wrapper
503 library part of YAZ is used.
505 Added SRU client support.
507 Automatically computes pz:nativesyntax if not provided. Works for XML and
510 --- 1.0.13 2008/11/24
512 Command bytarget returns name of target (if defined).
514 --- 1.0.12 2008/11/04
516 Fixed bug #2021.. location now holds all brief elements.
518 --- 1.0.11 2008/10/15
520 Fixed check for application/x-www-form-urlencoded parameters.
522 --- 1.0.10 2008/10/14
524 Fixes for IE in pz2.js.
526 Fixed bug #2021: non-merged, brief meta data NOT included for command=show.
530 Changed the JS library pz2.js to use POST for long URL (+ params).
532 Added installation instructions for Windows. Note: NT services is
533 NOT available until we make a new release of YAZ.
535 Preserve order of repeated metadata fields (they were reversed before).
537 More MARC21 information extracted for metadata.
541 Fixed bug #1162: HTML entities are not escaped properly.
543 Native Windows port of Pazpar2. Makefile for Visual Studio provided.
547 Marc21 stylesheet updated to reflect multiple full text fields
551 Fixed bug in pz2.js WRT DOMElement attributes on IE.
553 Fixed bug 2100: Database wildcards not working
557 Added support for retrieval of records in binary.
559 Fixed bug 1794: Pazpar2 does not return valid XML.
561 Deal with ICU not returning sortkey (resulted in SEGV before).
565 JavaScript library pzw2.js throws error if WS response (from Pazpar2 or
566 other) is malformed (non-wellformed XML or missing Pazpar2 OK status).
568 Improved diagnostics when Pazpar2 HTTP decoding fails.
570 Pazpar2 requests may be POSTed as using Content-Type
571 application/x-www-form-urlencoded.
573 Pazpar2 honors LF in HTTP headers.
575 Handle targets that handle negative hit counts (should not happen, but it
580 ICU is used for tokenization and normalization of the following: mergekey,
581 sorting, relevance terms.
583 Debian package now enables ICU tokenization and normalization by default.
587 Exposed user setting values (i.e. non-pz: names) to the record systems in two
588 ways: Either as parameters to the normalization stylesheets (which would allow the
589 programmer to postprocess or use the values in any way) or after the normalization
590 step, in which case values are made part of the normalized record (and available for
591 sorting, termlists, display, or other interface-related use.
593 Implemented sorting by year.
595 Option -d dumps records to the current log file instead of stderr.
597 Fixes for compilation on cygwin.
599 Z39.50 client code uses pz:elements. pz:elements was recognized in
600 earlier Pazpar2 versions but it was not used for anything.
602 icu_chain_test is using fgets instead of getline - fixes compilation
605 Loosen the CCL query parsing so that Pazpar2 only returns error if _all_
606 query conversions fail (rather than _any_). This means targets that do
607 not support some fields are ignored in a search.
611 Improved handling of socket timeout for Z39.50 connections.
613 Misc documentation updates and spell fixes.
615 Debian package pazpar2 creates log rotate entry.
617 Debian package pazpar2-apache2 reloads Apache2.
619 jsdemo included in distribution. It illustrates the use of the js/pz2.js
624 First public release.