3 Fix 'Record Missing' for command=show PAZ-903
5 Preserve order of records within cluster PAZ-902
7 testing: use yaz-ztest -V if possible and use YAZ in sibling directory
10 Allow clustered records to be ingested during retrieval. PAZ-900
12 Fix void function error which cannot return a value.
16 SRU pz:authentication="a/b" may end up as x-username=a%2Fb PAZ-899
18 Upgrade to debhelper version 7 PAZ-898
20 Package with libyaz5 PAZ-897
22 Better error message for CCL parse errors PAZ-887
26 New target setting: pz:authentication_mode. PAZ-896
28 pazpar2 PRM: pazpar2 runs as user nobody. PAZ-893
30 Strip #-suffix for ZOOM URLs. PAZ-892
34 Fix issue with hanging show/bytarget. Could happen if new search was
35 fired with filter before show from previous show completed.
37 Add 'date' handling for solr-pz2.xsl.
41 pz:authentication may carry user group password. If pz:authentication
42 has at least one blank in it, that forces Pazpar2 to use idPass Z39.50
43 authentication. Two forms are allowed
46 If no blanks are present, open authentication is in use (as before).
48 Fix {prev,next}recid elements that are returned by record
49 command. These were incorrect in versions 1.6.23 thru 1.6.32.
53 Experimental support for snippets. If argument snippets=1 is given
54 for command record or show, the text will include <match>-tags for
55 those area that matches.
57 Fix memory leak WRT client structures (incorrect inc ref count).
59 Log when a HTTP response is serialized and the time elapsed.
61 New command, service, which returns current service XML in use for
66 Local limit for fields of type "generic" (ie text fields) are
67 now normalized by mergekey rule before comparison takes place.
68 Before, no normalization took place and comparsion was, thus, exact.
70 New facility: dynamic rank , which allows ranking to be changed
71 for an existing result set. The rank can be set for search or
72 show. This overrides the rank for metadata elements (which fields
75 New facility:dynamic mergekey , which allows mergekey to be changed
76 for an existing result set. The mergekey can be set for search or
79 HTTP server: host=@ listens on IPV6 and IPV4 if possible.
80 Also, allow ports to be given as names (not just integers).
81 Fix @-notation on systems that don't support IPV6 sockets.
85 Add MasterKey Connect configuration. Refer to section "non-standard
86 databases" for more information.
88 Allow timeformat for log to be specified with option -m (as Metaproxy
91 New Debian package pazpar2-dbg.
93 Fix NULL ptr reference of se->relevance. If a new search is initiated
94 and a CCL query fails to parse, Pazpar2 could crash.
96 Fix problem with host/port mangling in Pazpar2 HTTP server. Problem
97 existed in 1.6.29 only.
101 IPV6 updates. Allow IPv6 addresses for database hosts and IPv6 address
102 for HTTP server. By default the HTTP server uses IPv4 only, but that can be
103 changed by setting "host" attribute for the "listen" element.
105 Change semantics of pz:extendrecs. Allow for repeated fetches .
106 pz:extendrecs is now the number of extra records to fetch (was total
109 --- 1.6.28 2013/03/21
111 Fix hang or memory violation if show occurred before a search. (not that
112 it makes much sense to perform a show before a search).
114 --- 1.6.27 2013/03/08
116 pz2.js: Element_parseChildNodes concatenates all Text/CDATA nodes, instead
119 --- 1.6.26 2013/03/08
121 New pz:metadata attribute, empty="empty-value" for Pazpar2's
122 internal representation. With this attribute, Pazpar2 treates an empty
123 pz:metadata type as having the value for "empty" - if empty.
125 New setting, pz:extendrecs, which triggers extended fetch of records
126 for a database beyond pz:maxrecs for a show command.
128 Fix warning that was falsely issued for "missing limitmap".
130 Log message for Pazpart start/stop changed. Now using same style as
131 Metaproxy, ie Pazpar2 start SHA1 / Pazpar2 stop .
133 --- 1.6.25 2013/02/07
135 Fix hang of 2nd command=show with esn/syntax given.
137 --- 1.6.24 2013/01/18
139 New merge attribute type: 'first', which takes all metadata fields
140 from first target that returns the particular field.
142 --- 1.6.23 2013/01/02
144 Extend info command with hostname and YAZ SHA1
145 Indent results for both command stat and info.
147 Allow limit on merged content. The new configuration metadata
148 element, limitcluster, configures that a metadata element (name) be used
149 as limit name for search. Applies to the whole service (ie all targets),
150 unlike pz:limitmap which is configured per-target (database).
152 New feature: limitmap local:* matches against all metadata fields.
154 Allow repeated list in limitmap spec . Separated by comma. For
155 example: value="local:title,rpn:@attr 1=4".
157 New element <message> in bytarget response. Holds diagnostic message
158 of code (say 'Unsupported Use Attribute' for Bib-1 114).
160 Improved logging for record ingestion failures.
162 Avoid using struct icu_chain in non-YAZ_HAVE_ICU mode. In the rare case,
163 when YAZ is compiled without ICU support.
165 --- 1.6.22 2012/10/11
167 Requires YAZ-4.2.40 to support native solr support.
169 Fix and improve logic handling whether or not to re-do search on sort
170 order changes. A sort order with change in ascending/descending only
171 whould not trigger a new search, which is required for targets with
172 native sorting capabilities. Each client is now checked if instructions
173 (sortmap) exist for native sorting and only client that does requires
174 it is researched. Other clients is just re-ingesting the records,
175 they already have. The resultset is now cleared if any researching
178 Connection sharing between session has broken since version 1.6.8 with
179 introduction of logic that would minimize searching if pazpar2 could
180 detect this based on same query and limits and partly sort order.
181 This could lead to segementations violations.
183 Added a chapter in the manaul about relevance ranking.
185 --- 1.6.21 2012/09/24
187 Rank tweak: follow=number will increase mult by number if two terms
188 occur next to each other; number-1 if they are one term apart , .. 0
189 if they are number a part (all in order). Default is 0 (following
190 terms has no effect).
192 Rank tweak: lead=k will divide mult by 1 + log2(1+k*l) where k is
193 value given by lead and l is length from beginning of field where
194 term occurs (l=0 for first term, l=1 for second term, ..). Default
197 Rank tweak: length=strategy. length="linear" if mult is to be divided
198 by length (existing, default behavior), length="log" if mult is to be
199 divided by log2(1+length), length="none" if mult is not to be affected
202 --- 1.6.20 2012/09/21
204 Rank algorithm details may be printed as part of show response in
205 element <relevance_info>.. This is only printed if <rank debug="yes"/>
208 Record as returned by show/record command have a minimal indentation
209 which makes things human-readable.
211 New configuration of default sorting criteria (sort-default) in
212 service definition. If no criteria is defined it will be as before
215 Search command now supports sort parameter just as the show command.
216 If no parameter is give, it will use the service sort-default value.
218 --- 1.6.19 2012/09/18
220 Rank algorithm skips strings that gets normalized to empty string.
221 For example, & and ! could map to the empty string. The weight for
222 those terms is now 0 (as if they were not part of the query).
224 Rank algorithm does not use CCL from limitmap; only from the query
225 parameter (user query).
229 --- 1.6.18 2012/09/17
231 Rank algorithm configurable by 'rank' element inside service. So far
232 only, attribute 'cluster' is recognized. If cluster="yes", multiple
233 records inside a cluster boosts higher than single records. This
234 is default behavior and existing behavior. cluster="no" takes the
235 average score of each record in a cluster.
237 --- 1.6.17 2012/09/05
239 Fix bad re-use of connections (connections with changing proxy should not
242 --- 1.6.16 2012/08/22
244 Fix a bug introduce in 1.6.15 around the position sorting. It resetted the
245 resultset and sorting when the sort order is position. However this will be done on
246 every client poll, which will make pazpar2 continuing reset and fetching.
247 It should only be done on FIRST request where the sort order change.
249 Fix an issue on suggestion option: Also disable suggestions on empty string.
251 Clean up in turbo marc stylesheet.
253 Remove the hardcoded size of termlists.
255 --- 1.6.15 2012/06/27
257 New facility: ccldirective may be given in service definition. Allows
258 CCL parsing to be customized a bit, such as defining names of operators
261 New facility: raw record by checksum, rather than offset. The record
262 command optionally takes checksum which identifies certain record from
265 New facility: per field ranking. Rank may be given as M [F N] where
266 M is default rank and N is rank for CCL terms from field F.
268 --- 1.6.14 2012/06/04
270 Fix for IE7/8 in pz.js
272 Applied patch from Giannis Kosmas on keepAlive, which also adds keepAlive to init response.
274 Lower log level some places.
276 Remove some invalid test results.
278 --- 1.6.13 2012/05/23
280 Introducing a version=2 parameter for show, termlist and bytarget commands.
281 This enables pazpar2 to return approximation on hit and count count when
282 doing record filtering using the limit parameter on search and a
283 limitmap with a value of "local:"
285 Setting pz:xslt may embed local XSLT as an alternative to referring
287 Value is not CDATA but XML nodes embedded, so escaping is not necessary
288 but a root element *must* be present. For example:
289 <settings target="target="z3950.indexdata.com/marc">
298 Metadata field rank may given by XML internal document (pz:xslt
299 result). If rank is not given, the rank from service description is
302 Metadata field can now configured a default limitmap and facetmap.
303 Setting limitmap to "local:" would work for all kind of targets, but would
304 prob. not be the optimal solution. But at least better than the default behavior
305 of pazpar2 where no filtering is done.
307 A service definition can now also contains <set/> that defines service-wide
308 settings. These will override server-wide sets and will be overridded by
311 New setting, pz:present_chunk, that specifies number of records to fetch
312 at a time. Zero will disable chunkation; will fetch max_records at once.
314 --- 1.6.12 2012/03/14
316 Revert the format change in termlist response, that could break
317 some clients / UIs since they were expecting an (empty) element
318 if no facet values was found.
320 --- 1.6.11 2012/03/07
322 Revert the behavior of returning errors when unable to block
323 on termlist, bytarget and search, when unable to block due to
324 other block. The client will now receive a regular response,
325 but it will be logged in the server. A parameter (report) is
326 added to change behavior to return error response or WARNING
327 status message. Consider this "API" as private, as it is mostly
328 untested and could be changed in future releases.
330 Fix spell error in pz2.js fix in 1.6.10.
332 New Marc2TurboMarc.xsl (contribution from Sven Porst).
333 Can solve the missing marc21.xsl updates in some cases.
335 tmarc.xsl: Simplify the 6xx to subject-long and fix 1-based
336 substring (contribtion from Sven Porst)
338 marc21.xsl: fix 1-based substring call
340 tmarc.xsl and marc21.xsl: use 856$a as last option for electronic-text.
342 Add test_termlist_block to test suite
344 --- 1.6.10 2012/02/23
346 Fix SEGV for invalid PQFs and SRU/SOLR targets
347 Also refactor a bit the code that converts from PQF to SRU/SOLR queries.
349 Fix pz2.js: "null object" due to change in in bytarget result XML.
351 Fixes in tmarc.xsl: Subject-long shorten for extra commas only.
352 Added this normalization to the other subject-long fields (d6xx),
353 where it was missing.
355 Fixes in marc21.xsl: Updated with most of the new tmarc.xsl.
356 Still differences around medium and holdings. marc21.xsl is not
357 longer active used by Index Data, and should be considered unsupported.
358 Use tmarc.xsl instead.
362 Fix SEGV that could occur for failed connections.
366 Fix bug for command sort that could return no results for active clients
367 (from previous search). This bug was present in 1.6.6-1.6.7.
369 Fix bug in results that could include results that should have been
370 filtered out. This bug was present in 1.6.6-1.6.7.
374 Fix bug introduced in 1.6.6 where a connection re-use could stall
377 Local filtering may now specify a local metadata field, eg.
378 pz:limitmap:somefield[t]=local:otherfield
382 For search, when limit and or filtering is in place and search
383 is identical to previous search, the result set is re-used and the
384 target is not searched.
386 Limits may work perform local filtering as well, by using "local:"
391 Updated bytarget command to contain a suggestions element with misspelled
392 words and suggestions to these. pz2.js has been updated to deliver this
393 onwards as well. Only target that currently delivers this is the solr
394 client in YAZ 4.2.18.
398 New service definition element, xslt, that allows an embedded stylesheet
399 to be defined. This can be referred to from pz:xslt as an alternative to
402 New pz:sortmap:field setting for specifying hints on how to make
403 a target natively sort on a field. This is used for command=show in
404 conjunction with sort.
406 New pz:url setting for specifying the actual URL for a target. When
407 this is used the target ID is not used as URL anymore and the target ID
408 may be almost any string (not including []).
410 command=termlist without name parameter returns all termlists/facets.
411 Previously if name parameter was omitted, only "subject" was returned.
415 Make termlist sorting stable. Terms with same frequency are now sorted by
416 their display name. This makes a pretty display and improves our
417 regression test because qsort is not a stable sort.
419 New sort parameter value 'position'. The 'position' sorts merged records
420 by their original position from the remote target. This is primarily useful
421 for debugging and may be used for targets that already perform some kind
422 of relevance ranking. Note that sort by default is decreasing; so to get
423 records in their original order sort=position:1 must be used.
427 tmarc.xsl: yet another 773$g fix. Was broken in 1.6.1 as well.
429 Facility to change working directory for pazpar2 daemon. Option -wdir
430 sets working directory to dir. This facility is useful if core dumps
431 must be saved. In this case, the current working directory must be
432 writable by the running user, such as "nobody".
436 New configuration element <icu_chain> for <server>/<service> which
437 allows a named ICU rule (chain) to be defined. The names relevance,
438 sort, mergekey and facet are used for those operations. The definition
439 <icu_chain id="sort" locale="en"> .. </icu_chain>
441 <sort> <icu_chain locale="en> ... </icu_chain> </sort>
442 And so on.. for relevance, mergekey and facet as well. The latter
443 style is deprecated. The facet terms are normalized by the facet
444 rule by default. This may be changed on a metadata field basis by
445 defining the new attribute 'facetrule' for the metadata element.
447 <icu_chain id="myrule" locale="en"> ... </icu_chain>
448 <metadata name="author" termlist="yes" facetrule="myrule"/>
450 Preserve rorder for merged metadata. Fixes issue as reported by Sven
451 Porst: http://lists.indexdata.dk/pipermail/yazlist/2011-July/003230.html
453 tmarc.xsl: set journal-subpart to 773$ only.
457 Modify the behavior for the limit parameter (first defined in 1.5.7).
458 Mapping of limit searches are now defined by the new configuration item
459 pz:limitmap. Fix a dead-lock problem with the limit parameter.
461 Extend tmarc.xsl to extract 773$g data (OpenURL).
465 ICU default maps remove backquote (`).
467 Command 'search' takes limit parameter (optional). The limit parameter
468 allows a search to be limited one or more facets and the corresponding
469 values. This is for server side filtering.
471 Configure tweak: Use -lm for log(3) if needed
475 Fix a problem with skiparticle sortkey that could be completely
476 ignored (and reduced to "").
478 Fix dependency problem in pazpar2 RPM package (did not require
479 libyaz4 as it should).
483 Fix memory leak that occurred for command=termlist&name=xtargets .
485 Pazpar2 may save HTTP requests. Enabled by option -R.
489 Experimental support for DTIC DADS target. New dads-pz2.xsl.
491 Support for query_syntax (overrides the default for SRU | Z39.50)
493 Support for extraArgs (ZOOM "extraArgs" option) for targets
495 New commands: status-server and status-session
499 Fix for threaded runs: Client now have a copy of the database URL,
500 which can used after the database has been release from the client.
501 This makes the logging in the connection idle timeout of the client nicer (no NOURL) and should be thread-safe.
503 tmarc.xsl: Add journal-title-abbrev and full text.
505 cf.xsl: new fields: isbn, issn, journaltitle, volume, issue
507 Fix for cmd=record before search.
509 Session Logging clean up.
511 Fix wrong termlist factor when maxrecs is different from 100.
515 Fix missing pz:termlist_term_factor in settings.c messed up pz:preferred.
516 Term factor is default enabled but can be diseabled by
517 pz:termlist_term_factor=0
521 Add scaling of facet count. Currently always enabled, needs fixing.
522 Allow user-defined info for target suffix. This has no meaning in
523 Pazpar2 except to distinguish targets from each other. The suffix
524 data begins with #. For example z3950.indexdata.com/gils#Mydata
526 Added exact-match recordfilter; format name=value
530 SOLR support. Pazpar2 may operate as web service client for SOLR.
534 Fix for show command and block=1 (dead lock). Bug was introduced in
539 New RPM packages: pazpar2, pazpar2-js, pazpar2-doc. These have been
540 tested on CentOS 5.5 only.
544 Fix problem with result sets being removed from a client session
545 if the connection for it was resused by another session. Bug #3489.
547 New iphone UI for Pazpar2 (www/iphone).
551 Fixes for threaded operation.
553 New stylesheets for TurboMARC: tmarc.xsl and opac_turbomarc.xsl.
555 New example services in etc/services in source. In the Debian packages
556 these are located in /etc/pazpar2/services-available
558 Threaded mode operational on Windows. Requires Windows 7 or Windows
561 Default value of setting pz:max_connections is 0 which means that there
562 is no limit on number of connections.
566 Pazpar2 may operate in threaded mode. Enabled by element threads in
567 the configuration. See pazpar2_conf for details.
569 New setting setting: pz:max_connections. Setting pz:max_connections is
570 a limit of number of sockets to a host. When this limit is reached,
571 Pazpar2 will wait up to 5 seconds for a connection to becomes available.
572 The client will be marked Client_Error when it can not be searched
573 (other clients in a session may work). If pz:max_connections is not set
574 for a target, a value of 30 will be used. Note: the pz:max_connections
575 will only work in threaded mode.
577 pz2.js: JSON support for show.
579 Debian package: Enable default service, default.xml, before starting
580 Pazpar2 only if there is no service already in /etc/pazpar2/services-enabled.
584 Debian version depends on on libyaz4. Note that Pazpar2 will still
585 compile from source with YAZ 3.
587 Split services into separate files. The example configuration file
588 pazpar2.cfg.dist now includes a default service default.xml (part of
589 etc). And default.xml includes settings/edu.xml. The default.xml file,
590 not to be confused with settings/defaults.xml, is a template for jsdemo
591 and other services. The Debian package installs /etc/pazpar2/server.xml
592 which is now the main pazpar2 configuration (used to be called pazpar2.cfg).
593 server.xml includes services from /etc/pazpar2/services-enabled/*.xml .
594 The default.xml (from etc) is installed in /etc/pazpar2/services-available
595 and a symlink to it is created from services-enabled. The default.xml
596 service is unnamed and, thus, will be used by jsdemo and test1.
598 New setting pz:negotiation_charset. Patch from Andrei V. Toutoukine. The
599 new setting pz:negotiation_charset specifies character set for Z39.50 Init.
603 Support for additional fields in cf.xsl and pazpar2.conf.dist:
604 publisher, available, due, location (=locallocation), callno
605 (=callnumber), thumburl and score.
607 Describe pz:xslt and the auto setting.
609 Move mergekey definition away from the normalization stylesheets and
610 define a mergekey common for all target types in pazpar2.cfg.
612 Code update: Use the Odr_int type for hit counts. This is part of
613 YAZ 3.0.47 and later and so configure checks for that.
617 Metadata attribute 'skiparticle' also works for ICU based
618 normalization. (was only working for the non-ICU/ASCII before).
620 Command bytarget with argument settings=1 will show settings per
621 target.. This is to be able to verify correct settings and be able to
622 test that they are correct. The database settings array size is now
623 also stored.. Problems with database settings array is that if not
624 careful it will be too small (smaller than dictionary per-service
627 Make record list sorting stable by comparing mergekey for records if
628 relevance/title or other sorting criteria all match. This is merely to
629 ensure that our regressions tests works (reproducible output).
631 Relevance calculation changes: use a different denominator (length) for
632 per-field relevance scoring.. Instead of length of all ranked fields we
633 now use length of individual fields (as if they were individual "free"
634 text fields). This will ensure that documents with a long field with no
635 match (say description) will not "hurt" a title match.
637 Diagnostic member was not set on connection error. Fixed
641 Command search takes two optional parameters, startecs and maxrecs,
642 that specifies the start offset (0, 1, ...) and maximum number of records
643 to fetch for each target.
645 XSLTs + MARC maps are cached within a session so we don't re-parse
646 them over and over again. Even for a session with a single search
647 there's much to be gained because many targets use the same
650 The metadata attribute 'mergekey' now takes one of three values 'no',
651 'required', 'optional' . And the resulting mergekey from metadata
652 is now ordered in the same way as metadata in the service definition.
653 Older Pazpar2 version use the order in which metadata appeared in a
656 The search argument 'filter' now offers a new operator ~ which does a
657 substring match. The = operator works as before: string match for
658 anything but pz:id, or target match for pz:id.
660 New setting pz:recordfilter. The value of this setting takes the
661 form name[~value]. This setting makes Pazpar2 ignore all retrieved
662 records that do not have the metadata element name with value substring
665 Pazpar2 allows YAZ log level to be set (option -v).
669 For WS responses Pazpar2 creates XML header. Exception: raw record.
671 Setting XML files are now stored in etc/settings instead of etc. This
672 reflects the layout with the Debian package layout.
674 Settings may be posted for command=settings. The POSTed settings must
675 have root element 'settings' like regular setting files. In order to be
676 recognized, the POST request must use Content-Type=text/xml.
678 A service may be posted for command=init. This service will be used
679 during the session. The service may have its own target settings,
680 ICU config, timeout, etc. In order to be recognized, the POST request
681 must use Content-Type=text/xml.
683 Timeout values may be given per-service. That's element 'timeout'
684 which takes three attribute values (a subset may be given): 'session',
685 'z3950_operation', 'z3950_session'. Option -T is no longer supported
686 - used to specify session timeout.
688 Option -t tests the Pazpar2 configuration and returns exit code
689 (0=success, non-zero=failure). In previous version of Pazpar2, -t
690 specified local settings.
692 In version 1.2.0 the configuration file - after include processing -
693 was dumped to stdout. Now, the configuration is only dumped to the
694 yaz log file if option -d is given.
698 Configuration may now have multiple server areas. This means that a
699 Pazpar2 instance may listen on multiple ports. Virtual hosting is not
700 yet supported - on a server basis. Configuration may also have multiple
701 services .. That is repeating service elements inside a server. Each
702 has an attribute 'id' which serves as service ID. This ID in turn may
703 be used in a Pazpar2 session, by specifying parameter service=ID for
704 command init. There can be at most one unnamed service inside a server
705 which can be referred to by not specifying an service ID for command
706 init (backwards compatible). In order to partition multiple servers and
707 services a new include directive has been added. This takes an attribute
708 'src' which specifies one or more sub-files. For example to include
709 service files, one might use:
710 <server >.. <include src=/"etc/pazpar2/conf.d/*.xml"/> .. </server>.
711 It is the intention that that completely makes the settings directive
714 Fix problem where the record command would wait forever if there were
715 no targets to wait for (activeclients == 0).
719 One result set is created per session (last search) rather than for
720 each connection which happen to be shared (bug #3009).
722 marc21 stylesheets changed for efficiency.
726 Session timeout may be specified on the command-line as option -T.
728 Pazpar2 may now be operated in a no-merged mode for records.. All records
729 will be considered unique. This mode is enabled if no mergekey is
730 generated by the normalization stylesheet (pz:xslt).
732 Pazpar2 caches original records from each target and the 'record' command
733 with offset returns the original record if 'syntax' and 'esn' are NOT
734 specified. This speeds up retrieval of original records but also means
735 that Pazpar2 uses more memory. The cached records will be freed when the
736 session terminates or a new search is executed.
738 Pazpar2 no longer uses its own ICU wrapper. Instead the ICU wrapper
739 library part of YAZ is used.
741 Added SRU client support.
743 Automatically computes pz:nativesyntax if not provided. Works for XML and
746 --- 1.0.13 2008/11/24
748 Command bytarget returns name of target (if defined).
750 --- 1.0.12 2008/11/04
752 Fixed bug #2021.. location now holds all brief elements.
754 --- 1.0.11 2008/10/15
756 Fixed check for application/x-www-form-urlencoded parameters.
758 --- 1.0.10 2008/10/14
760 Fixes for IE in pz2.js.
762 Fixed bug #2021: non-merged, brief meta data NOT included for command=show.
766 Changed the JS library pz2.js to use POST for long URL (+ params).
768 Added installation instructions for Windows. Note: NT services is
769 NOT available until we make a new release of YAZ.
771 Preserve order of repeated metadata fields (they were reversed before).
773 More MARC21 information extracted for metadata.
777 Fixed bug #1162: HTML entities are not escaped properly.
779 Native Windows port of Pazpar2. Makefile for Visual Studio provided.
783 Marc21 stylesheet updated to reflect multiple full text fields
787 Fixed bug in pz2.js WRT DOMElement attributes on IE.
789 Fixed bug 2100: Database wildcards not working
793 Added support for retrieval of records in binary.
795 Fixed bug 1794: Pazpar2 does not return valid XML.
797 Deal with ICU not returning sortkey (resulted in SEGV before).
801 JavaScript library pzw2.js throws error if WS response (from Pazpar2 or
802 other) is malformed (non-wellformed XML or missing Pazpar2 OK status).
804 Improved diagnostics when Pazpar2 HTTP decoding fails.
806 Pazpar2 requests may be POSTed as using Content-Type
807 application/x-www-form-urlencoded.
809 Pazpar2 honors LF in HTTP headers.
811 Handle targets that handle negative hit counts (should not happen, but it
816 ICU is used for tokenization and normalization of the following: mergekey,
817 sorting, relevance terms.
819 Debian package now enables ICU tokenization and normalization by default.
823 Exposed user setting values (i.e. non-pz: names) to the record systems in two
824 ways: Either as parameters to the normalization stylesheets (which would allow the
825 programmer to postprocess or use the values in any way) or after the normalization
826 step, in which case values are made part of the normalized record (and available for
827 sorting, termlists, display, or other interface-related use.
829 Implemented sorting by year.
831 Option -d dumps records to the current log file instead of stderr.
833 Fixes for compilation on cygwin.
835 Z39.50 client code uses pz:elements. pz:elements was recognized in
836 earlier Pazpar2 versions but it was not used for anything.
838 icu_chain_test is using fgets instead of getline - fixes compilation
841 Loosen the CCL query parsing so that Pazpar2 only returns error if _all_
842 query conversions fail (rather than _any_). This means targets that do
843 not support some fields are ignored in a search.
847 Improved handling of socket timeout for Z39.50 connections.
849 Misc documentation updates and spell fixes.
851 Debian package pazpar2 creates log rotate entry.
853 Debian package pazpar2-apache2 reloads Apache2.
855 jsdemo included in distribution. It illustrates the use of the js/pz2.js
860 First public release.