3 Fix a bug introduce in 1.6.15 around the position sorting. It resetted the
4 resultset and sorting when the sort order is position. However this will be done on
5 every client poll, which will make pazpar2 continuing reset and fetching.
6 It should only be done on FIRST request where the sort order change.
8 Fix an issue on suggestion option: Also disable suggestions on empty string.
10 Clean up in turbo marc stylesheet.
12 Remove the hardcoded size of termlists.
16 New facility: ccldirective may be given in service definition. Allows
17 CCL parsing to be customized a bit, such as defining names of operators
20 New facility: raw record by checksum, rather than offset. The record
21 command optionally takes checksum which identifies certain record from
24 New facility: per field ranking. Rank may be given as M [F N] where
25 M is default rank and N is rank for CCL terms from field F.
29 Fix for IE7/8 in pz.js
31 Applied patch from Giannis Kosmas on keepAlive, which also adds keepAlive to init response.
33 Lower log level some places.
35 Remove some invalid test results.
39 Introducing a version=2 parameter for show, termlist and bytarget commands.
40 This enables pazpar2 to return approximation on hit and count count when
41 doing record filtering using the limit parameter on search and a
42 limitmap with a value of "local:"
44 Setting pz:xslt may embed local XSLT as an alternative to referring
46 Value is not CDATA but XML nodes embedded, so escaping is not necessary
47 but a root element *must* be present. For example:
48 <settings target="target="z3950.indexdata.com/marc">
57 Metadata field rank may given by XML internal document (pz:xslt
58 result). If rank is not given, the rank from service description is
61 Metadata field can now configured a default limitmap and facetmap.
62 Setting limitmap to "local:" would work for all kind of targets, but would
63 prob. not be the optimal solution. But at least better than the default behavior
64 of pazpar2 where no filtering is done.
66 A service definition can now also contains <set/> that defines service-wide
67 settings. These will override server-wide sets and will be overridded by
70 New setting, pz:present_chunk, that specifies number of records to fetch
71 at a time. Zero will disable chunkation; will fetch max_records at once.
75 Revert the format change in termlist response, that could break
76 some clients / UIs since they were expecting an (empty) element
77 if no facet values was found.
81 Revert the behavior of returning errors when unable to block
82 on termlist, bytarget and search, when unable to block due to
83 other block. The client will now receive a regular response,
84 but it will be logged in the server. A parameter (report) is
85 added to change behavior to return error response or WARNING
86 status message. Consider this "API" as private, as it is mostly
87 untested and could be changed in future releases.
89 Fix spell error in pz2.js fix in 1.6.10.
91 New Marc2TurboMarc.xsl (contribution from Sven Porst).
92 Can solve the missing marc21.xsl updates in some cases.
94 tmarc.xsl: Simplify the 6xx to subject-long and fix 1-based
95 substring (contribtion from Sven Porst)
97 marc21.xsl: fix 1-based substring call
99 tmarc.xsl and marc21.xsl: use 856$a as last option for electronic-text.
101 Add test_termlist_block to test suite
103 --- 1.6.10 2012/02/23
105 Fix SEGV for invalid PQFs and SRU/SOLR targets
106 Also refactor a bit the code that converts from PQF to SRU/SOLR queries.
108 Fix pz2.js: "null object" due to change in in bytarget result XML.
110 Fixes in tmarc.xsl: Subject-long shorten for extra commas only.
111 Added this normalization to the other subject-long fields (d6xx),
112 where it was missing.
114 Fixes in marc21.xsl: Updated with most of the new tmarc.xsl.
115 Still differences around medium and holdings. marc21.xsl is not
116 longer active used by Index Data, and should be considered unsupported.
117 Use tmarc.xsl instead.
121 Fix SEGV that could occur for failed connections.
125 Fix bug for command sort that could return no results for active clients
126 (from previous search). This bug was present in 1.6.6-1.6.7.
128 Fix bug in results that could include results that should have been
129 filtered out. This bug was present in 1.6.6-1.6.7.
133 Fix bug introduced in 1.6.6 where a connection re-use could stall
136 Local filtering may now specify a local metadata field, eg.
137 pz:limitmap:somefield[t]=local:otherfield
141 For search, when limit and or filtering is in place and search
142 is identical to previous search, the result set is re-used and the
143 target is not searched.
145 Limits may work perform local filtering as well, by using "local:"
150 Updated bytarget command to contain a suggestions element with misspelled
151 words and suggestions to these. pz2.js has been updated to deliver this
152 onwards as well. Only target that currently delivers this is the solr
153 client in YAZ 4.2.18.
157 New service definition element, xslt, that allows an embedded stylesheet
158 to be defined. This can be referred to from pz:xslt as an alternative to
161 New pz:sortmap:field setting for specifying hints on how to make
162 a target natively sort on a field. This is used for command=show in
163 conjunction with sort.
165 New pz:url setting for specifying the actual URL for a target. When
166 this is used the target ID is not used as URL anymore and the target ID
167 may be almost any string (not including []).
169 command=termlist without name parameter returns all termlists/facets.
170 Previously if name parameter was omitted, only "subject" was returned.
174 Make termlist sorting stable. Terms with same frequency are now sorted by
175 their display name. This makes a pretty display and improves our
176 regression test because qsort is not a stable sort.
178 New sort parameter value 'position'. The 'position' sorts merged records
179 by their original position from the remote target. This is primarily useful
180 for debugging and may be used for targets that already perform some kind
181 of relevance ranking. Note that sort by default is decreasing; so to get
182 records in their original order sort=position:1 must be used.
186 tmarc.xsl: yet another 773$g fix. Was broken in 1.6.1 as well.
188 Facility to change working directory for pazpar2 daemon. Option -wdir
189 sets working directory to dir. This facility is useful if core dumps
190 must be saved. In this case, the current working directory must be
191 writable by the running user, such as "nobody".
195 New configuration element <icu_chain> for <server>/<service> which
196 allows a named ICU rule (chain) to be defined. The names relevance,
197 sort, mergekey and facet are used for those operations. The definition
198 <icu_chain id="sort" locale="en"> .. </icu_chain>
200 <sort> <icu_chain locale="en> ... </icu_chain> </sort>
201 And so on.. for relevance, mergekey and facet as well. The latter
202 style is deprecated. The facet terms are normalized by the facet
203 rule by default. This may be changed on a metadata field basis by
204 defining the new attribute 'facetrule' for the metadata element.
206 <icu_chain id="myrule" locale="en"> ... </icu_chain>
207 <metadata name="author" termlist="yes" facetrule="myrule"/>
209 Preserve rorder for merged metadata. Fixes issue as reported by Sven
210 Porst: http://lists.indexdata.dk/pipermail/yazlist/2011-July/003230.html
212 tmarc.xsl: set journal-subpart to 773$ only.
216 Modify the behavior for the limit parameter (first defined in 1.5.7).
217 Mapping of limit searches are now defined by the new configuration item
218 pz:limitmap. Fix a dead-lock problem with the limit parameter.
220 Extend tmarc.xsl to extract 773$g data (OpenURL).
224 ICU default maps remove backquote (`).
226 Command 'search' takes limit parameter (optional). The limit parameter
227 allows a search to be limited one or more facets and the corresponding
228 values. This is for server side filtering.
230 Configure tweak: Use -lm for log(3) if needed
234 Fix a problem with skiparticle sortkey that could be completely
235 ignored (and reduced to "").
237 Fix dependency problem in pazpar2 RPM package (did not require
238 libyaz4 as it should).
242 Fix memory leak that occurred for command=termlist&name=xtargets .
244 Pazpar2 may save HTTP requests. Enabled by option -R.
248 Experimental support for DTIC DADS target. New dads-pz2.xsl.
250 Support for query_syntax (overrides the default for SRU | Z39.50)
252 Support for extraArgs (ZOOM "extraArgs" option) for targets
254 New commands: status-server and status-session
258 Fix for threaded runs: Client now have a copy of the database URL,
259 which can used after the database has been release from the client.
260 This makes the logging in the connection idle timeout of the client nicer (no NOURL) and should be thread-safe.
262 tmarc.xsl: Add journal-title-abbrev and full text.
264 cf.xsl: new fields: isbn, issn, journaltitle, volume, issue
266 Fix for cmd=record before search.
268 Session Logging clean up.
270 Fix wrong termlist factor when maxrecs is different from 100.
274 Fix missing pz:termlist_term_factor in settings.c messed up pz:preferred.
275 Term factor is default enabled but can be diseabled by
276 pz:termlist_term_factor=0
280 Add scaling of facet count. Currently always enabled, needs fixing.
281 Allow user-defined info for target suffix. This has no meaning in
282 Pazpar2 except to distinguish targets from each other. The suffix
283 data begins with #. For example z3950.indexdata.com/gils#Mydata
285 Added exact-match recordfilter; format name=value
289 SOLR support. Pazpar2 may operate as web service client for SOLR.
293 Fix for show command and block=1 (dead lock). Bug was introduced in
298 New RPM packages: pazpar2, pazpar2-js, pazpar2-doc. These have been
299 tested on CentOS 5.5 only.
303 Fix problem with result sets being removed from a client session
304 if the connection for it was resused by another session. Bug #3489.
306 New iphone UI for Pazpar2 (www/iphone).
310 Fixes for threaded operation.
312 New stylesheets for TurboMARC: tmarc.xsl and opac_turbomarc.xsl.
314 New example services in etc/services in source. In the Debian packages
315 these are located in /etc/pazpar2/services-available
317 Threaded mode operational on Windows. Requires Windows 7 or Windows
320 Default value of setting pz:max_connections is 0 which means that there
321 is no limit on number of connections.
325 Pazpar2 may operate in threaded mode. Enabled by element threads in
326 the configuration. See pazpar2_conf for details.
328 New setting setting: pz:max_connections. Setting pz:max_connections is
329 a limit of number of sockets to a host. When this limit is reached,
330 Pazpar2 will wait up to 5 seconds for a connection to becomes available.
331 The client will be marked Client_Error when it can not be searched
332 (other clients in a session may work). If pz:max_connections is not set
333 for a target, a value of 30 will be used. Note: the pz:max_connections
334 will only work in threaded mode.
336 pz2.js: JSON support for show.
338 Debian package: Enable default service, default.xml, before starting
339 Pazpar2 only if there is no service already in /etc/pazpar2/services-enabled.
343 Debian version depends on on libyaz4. Note that Pazpar2 will still
344 compile from source with YAZ 3.
346 Split services into separate files. The example configuration file
347 pazpar2.cfg.dist now includes a default service default.xml (part of
348 etc). And default.xml includes settings/edu.xml. The default.xml file,
349 not to be confused with settings/defaults.xml, is a template for jsdemo
350 and other services. The Debian package installs /etc/pazpar2/server.xml
351 which is now the main pazpar2 configuration (used to be called pazpar2.cfg).
352 server.xml includes services from /etc/pazpar2/services-enabled/*.xml .
353 The default.xml (from etc) is installed in /etc/pazpar2/services-available
354 and a symlink to it is created from services-enabled. The default.xml
355 service is unnamed and, thus, will be used by jsdemo and test1.
357 New setting pz:negotiation_charset. Patch from Andrei V. Toutoukine. The
358 new setting pz:negotiation_charset specifies character set for Z39.50 Init.
362 Support for additional fields in cf.xsl and pazpar2.conf.dist:
363 publisher, available, due, location (=locallocation), callno
364 (=callnumber), thumburl and score.
366 Describe pz:xslt and the auto setting.
368 Move mergekey definition away from the normalization stylesheets and
369 define a mergekey common for all target types in pazpar2.cfg.
371 Code update: Use the Odr_int type for hit counts. This is part of
372 YAZ 3.0.47 and later and so configure checks for that.
376 Metadata attribute 'skiparticle' also works for ICU based
377 normalization. (was only working for the non-ICU/ASCII before).
379 Command bytarget with argument settings=1 will show settings per
380 target.. This is to be able to verify correct settings and be able to
381 test that they are correct. The database settings array size is now
382 also stored.. Problems with database settings array is that if not
383 careful it will be too small (smaller than dictionary per-service
386 Make record list sorting stable by comparing mergekey for records if
387 relevance/title or other sorting criteria all match. This is merely to
388 ensure that our regressions tests works (reproducible output).
390 Relevance calculation changes: use a different denominator (length) for
391 per-field relevance scoring.. Instead of length of all ranked fields we
392 now use length of individual fields (as if they were individual "free"
393 text fields). This will ensure that documents with a long field with no
394 match (say description) will not "hurt" a title match.
396 Diagnostic member was not set on connection error. Fixed
400 Command search takes two optional parameters, startecs and maxrecs,
401 that specifies the start offset (0, 1, ...) and maximum number of records
402 to fetch for each target.
404 XSLTs + MARC maps are cached within a session so we don't re-parse
405 them over and over again. Even for a session with a single search
406 there's much to be gained because many targets use the same
409 The metadata attribute 'mergekey' now takes one of three values 'no',
410 'required', 'optional' . And the resulting mergekey from metadata
411 is now ordered in the same way as metadata in the service definition.
412 Older Pazpar2 version use the order in which metadata appeared in a
415 The search argument 'filter' now offers a new operator ~ which does a
416 substring match. The = operator works as before: string match for
417 anything but pz:id, or target match for pz:id.
419 New setting pz:recordfilter. The value of this setting takes the
420 form name[~value]. This setting makes Pazpar2 ignore all retrieved
421 records that do not have the metadata element name with value substring
424 Pazpar2 allows YAZ log level to be set (option -v).
428 For WS responses Pazpar2 creates XML header. Exception: raw record.
430 Setting XML files are now stored in etc/settings instead of etc. This
431 reflects the layout with the Debian package layout.
433 Settings may be posted for command=settings. The POSTed settings must
434 have root element 'settings' like regular setting files. In order to be
435 recognized, the POST request must use Content-Type=text/xml.
437 A service may be posted for command=init. This service will be used
438 during the session. The service may have its own target settings,
439 ICU config, timeout, etc. In order to be recognized, the POST request
440 must use Content-Type=text/xml.
442 Timeout values may be given per-service. That's element 'timeout'
443 which takes three attribute values (a subset may be given): 'session',
444 'z3950_operation', 'z3950_session'. Option -T is no longer supported
445 - used to specify session timeout.
447 Option -t tests the Pazpar2 configuration and returns exit code
448 (0=success, non-zero=failure). In previous version of Pazpar2, -t
449 specified local settings.
451 In version 1.2.0 the configuration file - after include processing -
452 was dumped to stdout. Now, the configuration is only dumped to the
453 yaz log file if option -d is given.
457 Configuration may now have multiple server areas. This means that a
458 Pazpar2 instance may listen on multiple ports. Virtual hosting is not
459 yet supported - on a server basis. Configuration may also have multiple
460 services .. That is repeating service elements inside a server. Each
461 has an attribute 'id' which serves as service ID. This ID in turn may
462 be used in a Pazpar2 session, by specifying parameter service=ID for
463 command init. There can be at most one unnamed service inside a server
464 which can be referred to by not specifying an service ID for command
465 init (backwards compatible). In order to partition multiple servers and
466 services a new include directive has been added. This takes an attribute
467 'src' which specifies one or more sub-files. For example to include
468 service files, one might use:
469 <server >.. <include src=/"etc/pazpar2/conf.d/*.xml"/> .. </server>.
470 It is the intention that that completely makes the settings directive
473 Fix problem where the record command would wait forever if there were
474 no targets to wait for (activeclients == 0).
478 One result set is created per session (last search) rather than for
479 each connection which happen to be shared (bug #3009).
481 marc21 stylesheets changed for efficiency.
485 Session timeout may be specified on the command-line as option -T.
487 Pazpar2 may now be operated in a no-merged mode for records.. All records
488 will be considered unique. This mode is enabled if no mergekey is
489 generated by the normalization stylesheet (pz:xslt).
491 Pazpar2 caches original records from each target and the 'record' command
492 with offset returns the original record if 'syntax' and 'esn' are NOT
493 specified. This speeds up retrieval of original records but also means
494 that Pazpar2 uses more memory. The cached records will be freed when the
495 session terminates or a new search is executed.
497 Pazpar2 no longer uses its own ICU wrapper. Instead the ICU wrapper
498 library part of YAZ is used.
500 Added SRU client support.
502 Automatically computes pz:nativesyntax if not provided. Works for XML and
505 --- 1.0.13 2008/11/24
507 Command bytarget returns name of target (if defined).
509 --- 1.0.12 2008/11/04
511 Fixed bug #2021.. location now holds all brief elements.
513 --- 1.0.11 2008/10/15
515 Fixed check for application/x-www-form-urlencoded parameters.
517 --- 1.0.10 2008/10/14
519 Fixes for IE in pz2.js.
521 Fixed bug #2021: non-merged, brief meta data NOT included for command=show.
525 Changed the JS library pz2.js to use POST for long URL (+ params).
527 Added installation instructions for Windows. Note: NT services is
528 NOT available until we make a new release of YAZ.
530 Preserve order of repeated metadata fields (they were reversed before).
532 More MARC21 information extracted for metadata.
536 Fixed bug #1162: HTML entities are not escaped properly.
538 Native Windows port of Pazpar2. Makefile for Visual Studio provided.
542 Marc21 stylesheet updated to reflect multiple full text fields
546 Fixed bug in pz2.js WRT DOMElement attributes on IE.
548 Fixed bug 2100: Database wildcards not working
552 Added support for retrieval of records in binary.
554 Fixed bug 1794: Pazpar2 does not return valid XML.
556 Deal with ICU not returning sortkey (resulted in SEGV before).
560 JavaScript library pzw2.js throws error if WS response (from Pazpar2 or
561 other) is malformed (non-wellformed XML or missing Pazpar2 OK status).
563 Improved diagnostics when Pazpar2 HTTP decoding fails.
565 Pazpar2 requests may be POSTed as using Content-Type
566 application/x-www-form-urlencoded.
568 Pazpar2 honors LF in HTTP headers.
570 Handle targets that handle negative hit counts (should not happen, but it
575 ICU is used for tokenization and normalization of the following: mergekey,
576 sorting, relevance terms.
578 Debian package now enables ICU tokenization and normalization by default.
582 Exposed user setting values (i.e. non-pz: names) to the record systems in two
583 ways: Either as parameters to the normalization stylesheets (which would allow the
584 programmer to postprocess or use the values in any way) or after the normalization
585 step, in which case values are made part of the normalized record (and available for
586 sorting, termlists, display, or other interface-related use.
588 Implemented sorting by year.
590 Option -d dumps records to the current log file instead of stderr.
592 Fixes for compilation on cygwin.
594 Z39.50 client code uses pz:elements. pz:elements was recognized in
595 earlier Pazpar2 versions but it was not used for anything.
597 icu_chain_test is using fgets instead of getline - fixes compilation
600 Loosen the CCL query parsing so that Pazpar2 only returns error if _all_
601 query conversions fail (rather than _any_). This means targets that do
602 not support some fields are ignored in a search.
606 Improved handling of socket timeout for Z39.50 connections.
608 Misc documentation updates and spell fixes.
610 Debian package pazpar2 creates log rotate entry.
612 Debian package pazpar2-apache2 reloads Apache2.
614 jsdemo included in distribution. It illustrates the use of the js/pz2.js
619 First public release.