3 SRU pz:authentication="a/b" may end up as x-username=a%2Fb PAZ-899
5 Upgrade to debhelper version 7 PAZ-898
7 Package with libyaz5 PAZ-897
9 Better error message for CCL parse errors PAZ-887
13 New target setting: pz:authentication_mode. PAZ-896
15 pazpar2 PRM: pazpar2 runs as user nobody. PAZ-893
17 Strip #-suffix for ZOOM URLs. PAZ-892
21 Fix issue with hanging show/bytarget. Could happen if new search was
22 fired with filter before show from previous show completed.
24 Add 'date' handling for solr-pz2.xsl.
28 pz:authentication may carry user group password. If pz:authentication
29 has at least one blank in it, that forces Pazpar2 to use idPass Z39.50
30 authentication. Two forms are allowed
33 If no blanks are present, open authentication is in use (as before).
35 Fix {prev,next}recid elements that are returned by record
36 command. These were incorrect in versions 1.6.23 thru 1.6.32.
40 Experimental support for snippets. If argument snippets=1 is given
41 for command record or show, the text will include <match>-tags for
42 those area that matches.
44 Fix memory leak WRT client structures (incorrect inc ref count).
46 Log when a HTTP response is serialized and the time elapsed.
48 New command, service, which returns current service XML in use for
53 Local limit for fields of type "generic" (ie text fields) are
54 now normalized by mergekey rule before comparison takes place.
55 Before, no normalization took place and comparsion was, thus, exact.
57 New facility: dynamic rank , which allows ranking to be changed
58 for an existing result set. The rank can be set for search or
59 show. This overrides the rank for metadata elements (which fields
62 New facility:dynamic mergekey , which allows mergekey to be changed
63 for an existing result set. The mergekey can be set for search or
66 HTTP server: host=@ listens on IPV6 and IPV4 if possible.
67 Also, allow ports to be given as names (not just integers).
68 Fix @-notation on systems that don't support IPV6 sockets.
72 Add MasterKey Connect configuration. Refer to section "non-standard
73 databases" for more information.
75 Allow timeformat for log to be specified with option -m (as Metaproxy
78 New Debian package pazpar2-dbg.
80 Fix NULL ptr reference of se->relevance. If a new search is initiated
81 and a CCL query fails to parse, Pazpar2 could crash.
83 Fix problem with host/port mangling in Pazpar2 HTTP server. Problem
84 existed in 1.6.29 only.
88 IPV6 updates. Allow IPv6 addresses for database hosts and IPv6 address
89 for HTTP server. By default the HTTP server uses IPv4 only, but that can be
90 changed by setting "host" attribute for the "listen" element.
92 Change semantics of pz:extendrecs. Allow for repeated fetches .
93 pz:extendrecs is now the number of extra records to fetch (was total
98 Fix hang or memory violation if show occurred before a search. (not that
99 it makes much sense to perform a show before a search).
101 --- 1.6.27 2013/03/08
103 pz2.js: Element_parseChildNodes concatenates all Text/CDATA nodes, instead
106 --- 1.6.26 2013/03/08
108 New pz:metadata attribute, empty="empty-value" for Pazpar2's
109 internal representation. With this attribute, Pazpar2 treates an empty
110 pz:metadata type as having the value for "empty" - if empty.
112 New setting, pz:extendrecs, which triggers extended fetch of records
113 for a database beyond pz:maxrecs for a show command.
115 Fix warning that was falsely issued for "missing limitmap".
117 Log message for Pazpart start/stop changed. Now using same style as
118 Metaproxy, ie Pazpar2 start SHA1 / Pazpar2 stop .
120 --- 1.6.25 2013/02/07
122 Fix hang of 2nd command=show with esn/syntax given.
124 --- 1.6.24 2013/01/18
126 New merge attribute type: 'first', which takes all metadata fields
127 from first target that returns the particular field.
129 --- 1.6.23 2013/01/02
131 Extend info command with hostname and YAZ SHA1
132 Indent results for both command stat and info.
134 Allow limit on merged content. The new configuration metadata
135 element, limitcluster, configures that a metadata element (name) be used
136 as limit name for search. Applies to the whole service (ie all targets),
137 unlike pz:limitmap which is configured per-target (database).
139 New feature: limitmap local:* matches against all metadata fields.
141 Allow repeated list in limitmap spec . Separated by comma. For
142 example: value="local:title,rpn:@attr 1=4".
144 New element <message> in bytarget response. Holds diagnostic message
145 of code (say 'Unsupported Use Attribute' for Bib-1 114).
147 Improved logging for record ingestion failures.
149 Avoid using struct icu_chain in non-YAZ_HAVE_ICU mode. In the rare case,
150 when YAZ is compiled without ICU support.
152 --- 1.6.22 2012/10/11
154 Requires YAZ-4.2.40 to support native solr support.
156 Fix and improve logic handling whether or not to re-do search on sort
157 order changes. A sort order with change in ascending/descending only
158 whould not trigger a new search, which is required for targets with
159 native sorting capabilities. Each client is now checked if instructions
160 (sortmap) exist for native sorting and only client that does requires
161 it is researched. Other clients is just re-ingesting the records,
162 they already have. The resultset is now cleared if any researching
165 Connection sharing between session has broken since version 1.6.8 with
166 introduction of logic that would minimize searching if pazpar2 could
167 detect this based on same query and limits and partly sort order.
168 This could lead to segementations violations.
170 Added a chapter in the manaul about relevance ranking.
172 --- 1.6.21 2012/09/24
174 Rank tweak: follow=number will increase mult by number if two terms
175 occur next to each other; number-1 if they are one term apart , .. 0
176 if they are number a part (all in order). Default is 0 (following
177 terms has no effect).
179 Rank tweak: lead=k will divide mult by 1 + log2(1+k*l) where k is
180 value given by lead and l is length from beginning of field where
181 term occurs (l=0 for first term, l=1 for second term, ..). Default
184 Rank tweak: length=strategy. length="linear" if mult is to be divided
185 by length (existing, default behavior), length="log" if mult is to be
186 divided by log2(1+length), length="none" if mult is not to be affected
189 --- 1.6.20 2012/09/21
191 Rank algorithm details may be printed as part of show response in
192 element <relevance_info>.. This is only printed if <rank debug="yes"/>
195 Record as returned by show/record command have a minimal indentation
196 which makes things human-readable.
198 New configuration of default sorting criteria (sort-default) in
199 service definition. If no criteria is defined it will be as before
202 Search command now supports sort parameter just as the show command.
203 If no parameter is give, it will use the service sort-default value.
205 --- 1.6.19 2012/09/18
207 Rank algorithm skips strings that gets normalized to empty string.
208 For example, & and ! could map to the empty string. The weight for
209 those terms is now 0 (as if they were not part of the query).
211 Rank algorithm does not use CCL from limitmap; only from the query
212 parameter (user query).
216 --- 1.6.18 2012/09/17
218 Rank algorithm configurable by 'rank' element inside service. So far
219 only, attribute 'cluster' is recognized. If cluster="yes", multiple
220 records inside a cluster boosts higher than single records. This
221 is default behavior and existing behavior. cluster="no" takes the
222 average score of each record in a cluster.
224 --- 1.6.17 2012/09/05
226 Fix bad re-use of connections (connections with changing proxy should not
229 --- 1.6.16 2012/08/22
231 Fix a bug introduce in 1.6.15 around the position sorting. It resetted the
232 resultset and sorting when the sort order is position. However this will be done on
233 every client poll, which will make pazpar2 continuing reset and fetching.
234 It should only be done on FIRST request where the sort order change.
236 Fix an issue on suggestion option: Also disable suggestions on empty string.
238 Clean up in turbo marc stylesheet.
240 Remove the hardcoded size of termlists.
242 --- 1.6.15 2012/06/27
244 New facility: ccldirective may be given in service definition. Allows
245 CCL parsing to be customized a bit, such as defining names of operators
248 New facility: raw record by checksum, rather than offset. The record
249 command optionally takes checksum which identifies certain record from
252 New facility: per field ranking. Rank may be given as M [F N] where
253 M is default rank and N is rank for CCL terms from field F.
255 --- 1.6.14 2012/06/04
257 Fix for IE7/8 in pz.js
259 Applied patch from Giannis Kosmas on keepAlive, which also adds keepAlive to init response.
261 Lower log level some places.
263 Remove some invalid test results.
265 --- 1.6.13 2012/05/23
267 Introducing a version=2 parameter for show, termlist and bytarget commands.
268 This enables pazpar2 to return approximation on hit and count count when
269 doing record filtering using the limit parameter on search and a
270 limitmap with a value of "local:"
272 Setting pz:xslt may embed local XSLT as an alternative to referring
274 Value is not CDATA but XML nodes embedded, so escaping is not necessary
275 but a root element *must* be present. For example:
276 <settings target="target="z3950.indexdata.com/marc">
285 Metadata field rank may given by XML internal document (pz:xslt
286 result). If rank is not given, the rank from service description is
289 Metadata field can now configured a default limitmap and facetmap.
290 Setting limitmap to "local:" would work for all kind of targets, but would
291 prob. not be the optimal solution. But at least better than the default behavior
292 of pazpar2 where no filtering is done.
294 A service definition can now also contains <set/> that defines service-wide
295 settings. These will override server-wide sets and will be overridded by
298 New setting, pz:present_chunk, that specifies number of records to fetch
299 at a time. Zero will disable chunkation; will fetch max_records at once.
301 --- 1.6.12 2012/03/14
303 Revert the format change in termlist response, that could break
304 some clients / UIs since they were expecting an (empty) element
305 if no facet values was found.
307 --- 1.6.11 2012/03/07
309 Revert the behavior of returning errors when unable to block
310 on termlist, bytarget and search, when unable to block due to
311 other block. The client will now receive a regular response,
312 but it will be logged in the server. A parameter (report) is
313 added to change behavior to return error response or WARNING
314 status message. Consider this "API" as private, as it is mostly
315 untested and could be changed in future releases.
317 Fix spell error in pz2.js fix in 1.6.10.
319 New Marc2TurboMarc.xsl (contribution from Sven Porst).
320 Can solve the missing marc21.xsl updates in some cases.
322 tmarc.xsl: Simplify the 6xx to subject-long and fix 1-based
323 substring (contribtion from Sven Porst)
325 marc21.xsl: fix 1-based substring call
327 tmarc.xsl and marc21.xsl: use 856$a as last option for electronic-text.
329 Add test_termlist_block to test suite
331 --- 1.6.10 2012/02/23
333 Fix SEGV for invalid PQFs and SRU/SOLR targets
334 Also refactor a bit the code that converts from PQF to SRU/SOLR queries.
336 Fix pz2.js: "null object" due to change in in bytarget result XML.
338 Fixes in tmarc.xsl: Subject-long shorten for extra commas only.
339 Added this normalization to the other subject-long fields (d6xx),
340 where it was missing.
342 Fixes in marc21.xsl: Updated with most of the new tmarc.xsl.
343 Still differences around medium and holdings. marc21.xsl is not
344 longer active used by Index Data, and should be considered unsupported.
345 Use tmarc.xsl instead.
349 Fix SEGV that could occur for failed connections.
353 Fix bug for command sort that could return no results for active clients
354 (from previous search). This bug was present in 1.6.6-1.6.7.
356 Fix bug in results that could include results that should have been
357 filtered out. This bug was present in 1.6.6-1.6.7.
361 Fix bug introduced in 1.6.6 where a connection re-use could stall
364 Local filtering may now specify a local metadata field, eg.
365 pz:limitmap:somefield[t]=local:otherfield
369 For search, when limit and or filtering is in place and search
370 is identical to previous search, the result set is re-used and the
371 target is not searched.
373 Limits may work perform local filtering as well, by using "local:"
378 Updated bytarget command to contain a suggestions element with misspelled
379 words and suggestions to these. pz2.js has been updated to deliver this
380 onwards as well. Only target that currently delivers this is the solr
381 client in YAZ 4.2.18.
385 New service definition element, xslt, that allows an embedded stylesheet
386 to be defined. This can be referred to from pz:xslt as an alternative to
389 New pz:sortmap:field setting for specifying hints on how to make
390 a target natively sort on a field. This is used for command=show in
391 conjunction with sort.
393 New pz:url setting for specifying the actual URL for a target. When
394 this is used the target ID is not used as URL anymore and the target ID
395 may be almost any string (not including []).
397 command=termlist without name parameter returns all termlists/facets.
398 Previously if name parameter was omitted, only "subject" was returned.
402 Make termlist sorting stable. Terms with same frequency are now sorted by
403 their display name. This makes a pretty display and improves our
404 regression test because qsort is not a stable sort.
406 New sort parameter value 'position'. The 'position' sorts merged records
407 by their original position from the remote target. This is primarily useful
408 for debugging and may be used for targets that already perform some kind
409 of relevance ranking. Note that sort by default is decreasing; so to get
410 records in their original order sort=position:1 must be used.
414 tmarc.xsl: yet another 773$g fix. Was broken in 1.6.1 as well.
416 Facility to change working directory for pazpar2 daemon. Option -wdir
417 sets working directory to dir. This facility is useful if core dumps
418 must be saved. In this case, the current working directory must be
419 writable by the running user, such as "nobody".
423 New configuration element <icu_chain> for <server>/<service> which
424 allows a named ICU rule (chain) to be defined. The names relevance,
425 sort, mergekey and facet are used for those operations. The definition
426 <icu_chain id="sort" locale="en"> .. </icu_chain>
428 <sort> <icu_chain locale="en> ... </icu_chain> </sort>
429 And so on.. for relevance, mergekey and facet as well. The latter
430 style is deprecated. The facet terms are normalized by the facet
431 rule by default. This may be changed on a metadata field basis by
432 defining the new attribute 'facetrule' for the metadata element.
434 <icu_chain id="myrule" locale="en"> ... </icu_chain>
435 <metadata name="author" termlist="yes" facetrule="myrule"/>
437 Preserve rorder for merged metadata. Fixes issue as reported by Sven
438 Porst: http://lists.indexdata.dk/pipermail/yazlist/2011-July/003230.html
440 tmarc.xsl: set journal-subpart to 773$ only.
444 Modify the behavior for the limit parameter (first defined in 1.5.7).
445 Mapping of limit searches are now defined by the new configuration item
446 pz:limitmap. Fix a dead-lock problem with the limit parameter.
448 Extend tmarc.xsl to extract 773$g data (OpenURL).
452 ICU default maps remove backquote (`).
454 Command 'search' takes limit parameter (optional). The limit parameter
455 allows a search to be limited one or more facets and the corresponding
456 values. This is for server side filtering.
458 Configure tweak: Use -lm for log(3) if needed
462 Fix a problem with skiparticle sortkey that could be completely
463 ignored (and reduced to "").
465 Fix dependency problem in pazpar2 RPM package (did not require
466 libyaz4 as it should).
470 Fix memory leak that occurred for command=termlist&name=xtargets .
472 Pazpar2 may save HTTP requests. Enabled by option -R.
476 Experimental support for DTIC DADS target. New dads-pz2.xsl.
478 Support for query_syntax (overrides the default for SRU | Z39.50)
480 Support for extraArgs (ZOOM "extraArgs" option) for targets
482 New commands: status-server and status-session
486 Fix for threaded runs: Client now have a copy of the database URL,
487 which can used after the database has been release from the client.
488 This makes the logging in the connection idle timeout of the client nicer (no NOURL) and should be thread-safe.
490 tmarc.xsl: Add journal-title-abbrev and full text.
492 cf.xsl: new fields: isbn, issn, journaltitle, volume, issue
494 Fix for cmd=record before search.
496 Session Logging clean up.
498 Fix wrong termlist factor when maxrecs is different from 100.
502 Fix missing pz:termlist_term_factor in settings.c messed up pz:preferred.
503 Term factor is default enabled but can be diseabled by
504 pz:termlist_term_factor=0
508 Add scaling of facet count. Currently always enabled, needs fixing.
509 Allow user-defined info for target suffix. This has no meaning in
510 Pazpar2 except to distinguish targets from each other. The suffix
511 data begins with #. For example z3950.indexdata.com/gils#Mydata
513 Added exact-match recordfilter; format name=value
517 SOLR support. Pazpar2 may operate as web service client for SOLR.
521 Fix for show command and block=1 (dead lock). Bug was introduced in
526 New RPM packages: pazpar2, pazpar2-js, pazpar2-doc. These have been
527 tested on CentOS 5.5 only.
531 Fix problem with result sets being removed from a client session
532 if the connection for it was resused by another session. Bug #3489.
534 New iphone UI for Pazpar2 (www/iphone).
538 Fixes for threaded operation.
540 New stylesheets for TurboMARC: tmarc.xsl and opac_turbomarc.xsl.
542 New example services in etc/services in source. In the Debian packages
543 these are located in /etc/pazpar2/services-available
545 Threaded mode operational on Windows. Requires Windows 7 or Windows
548 Default value of setting pz:max_connections is 0 which means that there
549 is no limit on number of connections.
553 Pazpar2 may operate in threaded mode. Enabled by element threads in
554 the configuration. See pazpar2_conf for details.
556 New setting setting: pz:max_connections. Setting pz:max_connections is
557 a limit of number of sockets to a host. When this limit is reached,
558 Pazpar2 will wait up to 5 seconds for a connection to becomes available.
559 The client will be marked Client_Error when it can not be searched
560 (other clients in a session may work). If pz:max_connections is not set
561 for a target, a value of 30 will be used. Note: the pz:max_connections
562 will only work in threaded mode.
564 pz2.js: JSON support for show.
566 Debian package: Enable default service, default.xml, before starting
567 Pazpar2 only if there is no service already in /etc/pazpar2/services-enabled.
571 Debian version depends on on libyaz4. Note that Pazpar2 will still
572 compile from source with YAZ 3.
574 Split services into separate files. The example configuration file
575 pazpar2.cfg.dist now includes a default service default.xml (part of
576 etc). And default.xml includes settings/edu.xml. The default.xml file,
577 not to be confused with settings/defaults.xml, is a template for jsdemo
578 and other services. The Debian package installs /etc/pazpar2/server.xml
579 which is now the main pazpar2 configuration (used to be called pazpar2.cfg).
580 server.xml includes services from /etc/pazpar2/services-enabled/*.xml .
581 The default.xml (from etc) is installed in /etc/pazpar2/services-available
582 and a symlink to it is created from services-enabled. The default.xml
583 service is unnamed and, thus, will be used by jsdemo and test1.
585 New setting pz:negotiation_charset. Patch from Andrei V. Toutoukine. The
586 new setting pz:negotiation_charset specifies character set for Z39.50 Init.
590 Support for additional fields in cf.xsl and pazpar2.conf.dist:
591 publisher, available, due, location (=locallocation), callno
592 (=callnumber), thumburl and score.
594 Describe pz:xslt and the auto setting.
596 Move mergekey definition away from the normalization stylesheets and
597 define a mergekey common for all target types in pazpar2.cfg.
599 Code update: Use the Odr_int type for hit counts. This is part of
600 YAZ 3.0.47 and later and so configure checks for that.
604 Metadata attribute 'skiparticle' also works for ICU based
605 normalization. (was only working for the non-ICU/ASCII before).
607 Command bytarget with argument settings=1 will show settings per
608 target.. This is to be able to verify correct settings and be able to
609 test that they are correct. The database settings array size is now
610 also stored.. Problems with database settings array is that if not
611 careful it will be too small (smaller than dictionary per-service
614 Make record list sorting stable by comparing mergekey for records if
615 relevance/title or other sorting criteria all match. This is merely to
616 ensure that our regressions tests works (reproducible output).
618 Relevance calculation changes: use a different denominator (length) for
619 per-field relevance scoring.. Instead of length of all ranked fields we
620 now use length of individual fields (as if they were individual "free"
621 text fields). This will ensure that documents with a long field with no
622 match (say description) will not "hurt" a title match.
624 Diagnostic member was not set on connection error. Fixed
628 Command search takes two optional parameters, startecs and maxrecs,
629 that specifies the start offset (0, 1, ...) and maximum number of records
630 to fetch for each target.
632 XSLTs + MARC maps are cached within a session so we don't re-parse
633 them over and over again. Even for a session with a single search
634 there's much to be gained because many targets use the same
637 The metadata attribute 'mergekey' now takes one of three values 'no',
638 'required', 'optional' . And the resulting mergekey from metadata
639 is now ordered in the same way as metadata in the service definition.
640 Older Pazpar2 version use the order in which metadata appeared in a
643 The search argument 'filter' now offers a new operator ~ which does a
644 substring match. The = operator works as before: string match for
645 anything but pz:id, or target match for pz:id.
647 New setting pz:recordfilter. The value of this setting takes the
648 form name[~value]. This setting makes Pazpar2 ignore all retrieved
649 records that do not have the metadata element name with value substring
652 Pazpar2 allows YAZ log level to be set (option -v).
656 For WS responses Pazpar2 creates XML header. Exception: raw record.
658 Setting XML files are now stored in etc/settings instead of etc. This
659 reflects the layout with the Debian package layout.
661 Settings may be posted for command=settings. The POSTed settings must
662 have root element 'settings' like regular setting files. In order to be
663 recognized, the POST request must use Content-Type=text/xml.
665 A service may be posted for command=init. This service will be used
666 during the session. The service may have its own target settings,
667 ICU config, timeout, etc. In order to be recognized, the POST request
668 must use Content-Type=text/xml.
670 Timeout values may be given per-service. That's element 'timeout'
671 which takes three attribute values (a subset may be given): 'session',
672 'z3950_operation', 'z3950_session'. Option -T is no longer supported
673 - used to specify session timeout.
675 Option -t tests the Pazpar2 configuration and returns exit code
676 (0=success, non-zero=failure). In previous version of Pazpar2, -t
677 specified local settings.
679 In version 1.2.0 the configuration file - after include processing -
680 was dumped to stdout. Now, the configuration is only dumped to the
681 yaz log file if option -d is given.
685 Configuration may now have multiple server areas. This means that a
686 Pazpar2 instance may listen on multiple ports. Virtual hosting is not
687 yet supported - on a server basis. Configuration may also have multiple
688 services .. That is repeating service elements inside a server. Each
689 has an attribute 'id' which serves as service ID. This ID in turn may
690 be used in a Pazpar2 session, by specifying parameter service=ID for
691 command init. There can be at most one unnamed service inside a server
692 which can be referred to by not specifying an service ID for command
693 init (backwards compatible). In order to partition multiple servers and
694 services a new include directive has been added. This takes an attribute
695 'src' which specifies one or more sub-files. For example to include
696 service files, one might use:
697 <server >.. <include src=/"etc/pazpar2/conf.d/*.xml"/> .. </server>.
698 It is the intention that that completely makes the settings directive
701 Fix problem where the record command would wait forever if there were
702 no targets to wait for (activeclients == 0).
706 One result set is created per session (last search) rather than for
707 each connection which happen to be shared (bug #3009).
709 marc21 stylesheets changed for efficiency.
713 Session timeout may be specified on the command-line as option -T.
715 Pazpar2 may now be operated in a no-merged mode for records.. All records
716 will be considered unique. This mode is enabled if no mergekey is
717 generated by the normalization stylesheet (pz:xslt).
719 Pazpar2 caches original records from each target and the 'record' command
720 with offset returns the original record if 'syntax' and 'esn' are NOT
721 specified. This speeds up retrieval of original records but also means
722 that Pazpar2 uses more memory. The cached records will be freed when the
723 session terminates or a new search is executed.
725 Pazpar2 no longer uses its own ICU wrapper. Instead the ICU wrapper
726 library part of YAZ is used.
728 Added SRU client support.
730 Automatically computes pz:nativesyntax if not provided. Works for XML and
733 --- 1.0.13 2008/11/24
735 Command bytarget returns name of target (if defined).
737 --- 1.0.12 2008/11/04
739 Fixed bug #2021.. location now holds all brief elements.
741 --- 1.0.11 2008/10/15
743 Fixed check for application/x-www-form-urlencoded parameters.
745 --- 1.0.10 2008/10/14
747 Fixes for IE in pz2.js.
749 Fixed bug #2021: non-merged, brief meta data NOT included for command=show.
753 Changed the JS library pz2.js to use POST for long URL (+ params).
755 Added installation instructions for Windows. Note: NT services is
756 NOT available until we make a new release of YAZ.
758 Preserve order of repeated metadata fields (they were reversed before).
760 More MARC21 information extracted for metadata.
764 Fixed bug #1162: HTML entities are not escaped properly.
766 Native Windows port of Pazpar2. Makefile for Visual Studio provided.
770 Marc21 stylesheet updated to reflect multiple full text fields
774 Fixed bug in pz2.js WRT DOMElement attributes on IE.
776 Fixed bug 2100: Database wildcards not working
780 Added support for retrieval of records in binary.
782 Fixed bug 1794: Pazpar2 does not return valid XML.
784 Deal with ICU not returning sortkey (resulted in SEGV before).
788 JavaScript library pzw2.js throws error if WS response (from Pazpar2 or
789 other) is malformed (non-wellformed XML or missing Pazpar2 OK status).
791 Improved diagnostics when Pazpar2 HTTP decoding fails.
793 Pazpar2 requests may be POSTed as using Content-Type
794 application/x-www-form-urlencoded.
796 Pazpar2 honors LF in HTTP headers.
798 Handle targets that handle negative hit counts (should not happen, but it
803 ICU is used for tokenization and normalization of the following: mergekey,
804 sorting, relevance terms.
806 Debian package now enables ICU tokenization and normalization by default.
810 Exposed user setting values (i.e. non-pz: names) to the record systems in two
811 ways: Either as parameters to the normalization stylesheets (which would allow the
812 programmer to postprocess or use the values in any way) or after the normalization
813 step, in which case values are made part of the normalized record (and available for
814 sorting, termlists, display, or other interface-related use.
816 Implemented sorting by year.
818 Option -d dumps records to the current log file instead of stderr.
820 Fixes for compilation on cygwin.
822 Z39.50 client code uses pz:elements. pz:elements was recognized in
823 earlier Pazpar2 versions but it was not used for anything.
825 icu_chain_test is using fgets instead of getline - fixes compilation
828 Loosen the CCL query parsing so that Pazpar2 only returns error if _all_
829 query conversions fail (rather than _any_). This means targets that do
830 not support some fields are ignored in a search.
834 Improved handling of socket timeout for Z39.50 connections.
836 Misc documentation updates and spell fixes.
838 Debian package pazpar2 creates log rotate entry.
840 Debian package pazpar2-apache2 reloads Apache2.
842 jsdemo included in distribution. It illustrates the use of the js/pz2.js
847 First public release.