3 pz:authentication may carry user group password. If pz:authentication
4 has at least one blank in it, that forces Pazpar2 to use idPass Z39.50
5 authentication. Two forms are allowed
8 If no blanks are present, open authentication is in use (as before).
10 Fix {prev,next}recid elements that are returned by record
11 command. These were incorrect in versions 1.6.23 thru 1.6.32.
15 Experimental support for snippets. If argument snippets=1 is given
16 for command record or show, the text will include <match>-tags for
17 those area that matches.
19 Fix memory leak WRT client structures (incorrect inc ref count).
21 Log when a HTTP response is serialized and the time elapsed.
23 New command, service, which returns current service XML in use for
28 Local limit for fields of type "generic" (ie text fields) are
29 now normalized by mergekey rule before comparison takes place.
30 Before, no normalization took place and comparsion was, thus, exact.
32 New facility: dynamic rank , which allows ranking to be changed
33 for an existing result set. The rank can be set for search or
34 show. This overrides the rank for metadata elements (which fields
37 New facility:dynamic mergekey , which allows mergekey to be changed
38 for an existing result set. The mergekey can be set for search or
41 HTTP server: host=@ listens on IPV6 and IPV4 if possible.
42 Also, allow ports to be given as names (not just integers).
43 Fix @-notation on systems that don't support IPV6 sockets.
47 Add MasterKey Connect configuration. Refer to section "non-standard
48 databases" for more information.
50 Allow timeformat for log to be specified with option -m (as Metaproxy
53 New Debian package pazpar2-dbg.
55 Fix NULL ptr reference of se->relevance. If a new search is initiated
56 and a CCL query fails to parse, Pazpar2 could crash.
58 Fix problem with host/port mangling in Pazpar2 HTTP server. Problem
59 existed in 1.6.29 only.
63 IPV6 updates. Allow IPv6 addresses for database hosts and IPv6 address
64 for HTTP server. By default the HTTP server uses IPv4 only, but that can be
65 changed by setting "host" attribute for the "listen" element.
67 Change semantics of pz:extendrecs. Allow for repeated fetches .
68 pz:extendrecs is now the number of extra records to fetch (was total
73 Fix hang or memory violation if show occurred before a search. (not that
74 it makes much sense to perform a show before a search).
78 pz2.js: Element_parseChildNodes concatenates all Text/CDATA nodes, instead
83 New pz:metadata attribute, empty="empty-value" for Pazpar2's
84 internal representation. With this attribute, Pazpar2 treates an empty
85 pz:metadata type as having the value for "empty" - if empty.
87 New setting, pz:extendrecs, which triggers extended fetch of records
88 for a database beyond pz:maxrecs for a show command.
90 Fix warning that was falsely issued for "missing limitmap".
92 Log message for Pazpart start/stop changed. Now using same style as
93 Metaproxy, ie Pazpar2 start SHA1 / Pazpar2 stop .
97 Fix hang of 2nd command=show with esn/syntax given.
101 New merge attribute type: 'first', which takes all metadata fields
102 from first target that returns the particular field.
104 --- 1.6.23 2013/01/02
106 Extend info command with hostname and YAZ SHA1
107 Indent results for both command stat and info.
109 Allow limit on merged content. The new configuration metadata
110 element, limitcluster, configures that a metadata element (name) be used
111 as limit name for search. Applies to the whole service (ie all targets),
112 unlike pz:limitmap which is configured per-target (database).
114 New feature: limitmap local:* matches against all metadata fields.
116 Allow repeated list in limitmap spec . Separated by comma. For
117 example: value="local:title,rpn:@attr 1=4".
119 New element <message> in bytarget response. Holds diagnostic message
120 of code (say 'Unsupported Use Attribute' for Bib-1 114).
122 Improved logging for record ingestion failures.
124 Avoid using struct icu_chain in non-YAZ_HAVE_ICU mode. In the rare case,
125 when YAZ is compiled without ICU support.
127 --- 1.6.22 2012/10/11
129 Requires YAZ-4.2.40 to support native solr support.
131 Fix and improve logic handling whether or not to re-do search on sort
132 order changes. A sort order with change in ascending/descending only
133 whould not trigger a new search, which is required for targets with
134 native sorting capabilities. Each client is now checked if instructions
135 (sortmap) exist for native sorting and only client that does requires
136 it is researched. Other clients is just re-ingesting the records,
137 they already have. The resultset is now cleared if any researching
140 Connection sharing between session has broken since version 1.6.8 with
141 introduction of logic that would minimize searching if pazpar2 could
142 detect this based on same query and limits and partly sort order.
143 This could lead to segementations violations.
145 Added a chapter in the manaul about relevance ranking.
147 --- 1.6.21 2012/09/24
149 Rank tweak: follow=number will increase mult by number if two terms
150 occur next to each other; number-1 if they are one term apart , .. 0
151 if they are number a part (all in order). Default is 0 (following
152 terms has no effect).
154 Rank tweak: lead=k will divide mult by 1 + log2(1+k*l) where k is
155 value given by lead and l is length from beginning of field where
156 term occurs (l=0 for first term, l=1 for second term, ..). Default
159 Rank tweak: length=strategy. length="linear" if mult is to be divided
160 by length (existing, default behavior), length="log" if mult is to be
161 divided by log2(1+length), length="none" if mult is not to be affected
164 --- 1.6.20 2012/09/21
166 Rank algorithm details may be printed as part of show response in
167 element <relevance_info>.. This is only printed if <rank debug="yes"/>
170 Record as returned by show/record command have a minimal indentation
171 which makes things human-readable.
173 New configuration of default sorting criteria (sort-default) in
174 service definition. If no criteria is defined it will be as before
177 Search command now supports sort parameter just as the show command.
178 If no parameter is give, it will use the service sort-default value.
180 --- 1.6.19 2012/09/18
182 Rank algorithm skips strings that gets normalized to empty string.
183 For example, & and ! could map to the empty string. The weight for
184 those terms is now 0 (as if they were not part of the query).
186 Rank algorithm does not use CCL from limitmap; only from the query
187 parameter (user query).
191 --- 1.6.18 2012/09/17
193 Rank algorithm configurable by 'rank' element inside service. So far
194 only, attribute 'cluster' is recognized. If cluster="yes", multiple
195 records inside a cluster boosts higher than single records. This
196 is default behavior and existing behavior. cluster="no" takes the
197 average score of each record in a cluster.
199 --- 1.6.17 2012/09/05
201 Fix bad re-use of connections (connections with changing proxy should not
204 --- 1.6.16 2012/08/22
206 Fix a bug introduce in 1.6.15 around the position sorting. It resetted the
207 resultset and sorting when the sort order is position. However this will be done on
208 every client poll, which will make pazpar2 continuing reset and fetching.
209 It should only be done on FIRST request where the sort order change.
211 Fix an issue on suggestion option: Also disable suggestions on empty string.
213 Clean up in turbo marc stylesheet.
215 Remove the hardcoded size of termlists.
217 --- 1.6.15 2012/06/27
219 New facility: ccldirective may be given in service definition. Allows
220 CCL parsing to be customized a bit, such as defining names of operators
223 New facility: raw record by checksum, rather than offset. The record
224 command optionally takes checksum which identifies certain record from
227 New facility: per field ranking. Rank may be given as M [F N] where
228 M is default rank and N is rank for CCL terms from field F.
230 --- 1.6.14 2012/06/04
232 Fix for IE7/8 in pz.js
234 Applied patch from Giannis Kosmas on keepAlive, which also adds keepAlive to init response.
236 Lower log level some places.
238 Remove some invalid test results.
240 --- 1.6.13 2012/05/23
242 Introducing a version=2 parameter for show, termlist and bytarget commands.
243 This enables pazpar2 to return approximation on hit and count count when
244 doing record filtering using the limit parameter on search and a
245 limitmap with a value of "local:"
247 Setting pz:xslt may embed local XSLT as an alternative to referring
249 Value is not CDATA but XML nodes embedded, so escaping is not necessary
250 but a root element *must* be present. For example:
251 <settings target="target="z3950.indexdata.com/marc">
260 Metadata field rank may given by XML internal document (pz:xslt
261 result). If rank is not given, the rank from service description is
264 Metadata field can now configured a default limitmap and facetmap.
265 Setting limitmap to "local:" would work for all kind of targets, but would
266 prob. not be the optimal solution. But at least better than the default behavior
267 of pazpar2 where no filtering is done.
269 A service definition can now also contains <set/> that defines service-wide
270 settings. These will override server-wide sets and will be overridded by
273 New setting, pz:present_chunk, that specifies number of records to fetch
274 at a time. Zero will disable chunkation; will fetch max_records at once.
276 --- 1.6.12 2012/03/14
278 Revert the format change in termlist response, that could break
279 some clients / UIs since they were expecting an (empty) element
280 if no facet values was found.
282 --- 1.6.11 2012/03/07
284 Revert the behavior of returning errors when unable to block
285 on termlist, bytarget and search, when unable to block due to
286 other block. The client will now receive a regular response,
287 but it will be logged in the server. A parameter (report) is
288 added to change behavior to return error response or WARNING
289 status message. Consider this "API" as private, as it is mostly
290 untested and could be changed in future releases.
292 Fix spell error in pz2.js fix in 1.6.10.
294 New Marc2TurboMarc.xsl (contribution from Sven Porst).
295 Can solve the missing marc21.xsl updates in some cases.
297 tmarc.xsl: Simplify the 6xx to subject-long and fix 1-based
298 substring (contribtion from Sven Porst)
300 marc21.xsl: fix 1-based substring call
302 tmarc.xsl and marc21.xsl: use 856$a as last option for electronic-text.
304 Add test_termlist_block to test suite
306 --- 1.6.10 2012/02/23
308 Fix SEGV for invalid PQFs and SRU/SOLR targets
309 Also refactor a bit the code that converts from PQF to SRU/SOLR queries.
311 Fix pz2.js: "null object" due to change in in bytarget result XML.
313 Fixes in tmarc.xsl: Subject-long shorten for extra commas only.
314 Added this normalization to the other subject-long fields (d6xx),
315 where it was missing.
317 Fixes in marc21.xsl: Updated with most of the new tmarc.xsl.
318 Still differences around medium and holdings. marc21.xsl is not
319 longer active used by Index Data, and should be considered unsupported.
320 Use tmarc.xsl instead.
324 Fix SEGV that could occur for failed connections.
328 Fix bug for command sort that could return no results for active clients
329 (from previous search). This bug was present in 1.6.6-1.6.7.
331 Fix bug in results that could include results that should have been
332 filtered out. This bug was present in 1.6.6-1.6.7.
336 Fix bug introduced in 1.6.6 where a connection re-use could stall
339 Local filtering may now specify a local metadata field, eg.
340 pz:limitmap:somefield[t]=local:otherfield
344 For search, when limit and or filtering is in place and search
345 is identical to previous search, the result set is re-used and the
346 target is not searched.
348 Limits may work perform local filtering as well, by using "local:"
353 Updated bytarget command to contain a suggestions element with misspelled
354 words and suggestions to these. pz2.js has been updated to deliver this
355 onwards as well. Only target that currently delivers this is the solr
356 client in YAZ 4.2.18.
360 New service definition element, xslt, that allows an embedded stylesheet
361 to be defined. This can be referred to from pz:xslt as an alternative to
364 New pz:sortmap:field setting for specifying hints on how to make
365 a target natively sort on a field. This is used for command=show in
366 conjunction with sort.
368 New pz:url setting for specifying the actual URL for a target. When
369 this is used the target ID is not used as URL anymore and the target ID
370 may be almost any string (not including []).
372 command=termlist without name parameter returns all termlists/facets.
373 Previously if name parameter was omitted, only "subject" was returned.
377 Make termlist sorting stable. Terms with same frequency are now sorted by
378 their display name. This makes a pretty display and improves our
379 regression test because qsort is not a stable sort.
381 New sort parameter value 'position'. The 'position' sorts merged records
382 by their original position from the remote target. This is primarily useful
383 for debugging and may be used for targets that already perform some kind
384 of relevance ranking. Note that sort by default is decreasing; so to get
385 records in their original order sort=position:1 must be used.
389 tmarc.xsl: yet another 773$g fix. Was broken in 1.6.1 as well.
391 Facility to change working directory for pazpar2 daemon. Option -wdir
392 sets working directory to dir. This facility is useful if core dumps
393 must be saved. In this case, the current working directory must be
394 writable by the running user, such as "nobody".
398 New configuration element <icu_chain> for <server>/<service> which
399 allows a named ICU rule (chain) to be defined. The names relevance,
400 sort, mergekey and facet are used for those operations. The definition
401 <icu_chain id="sort" locale="en"> .. </icu_chain>
403 <sort> <icu_chain locale="en> ... </icu_chain> </sort>
404 And so on.. for relevance, mergekey and facet as well. The latter
405 style is deprecated. The facet terms are normalized by the facet
406 rule by default. This may be changed on a metadata field basis by
407 defining the new attribute 'facetrule' for the metadata element.
409 <icu_chain id="myrule" locale="en"> ... </icu_chain>
410 <metadata name="author" termlist="yes" facetrule="myrule"/>
412 Preserve rorder for merged metadata. Fixes issue as reported by Sven
413 Porst: http://lists.indexdata.dk/pipermail/yazlist/2011-July/003230.html
415 tmarc.xsl: set journal-subpart to 773$ only.
419 Modify the behavior for the limit parameter (first defined in 1.5.7).
420 Mapping of limit searches are now defined by the new configuration item
421 pz:limitmap. Fix a dead-lock problem with the limit parameter.
423 Extend tmarc.xsl to extract 773$g data (OpenURL).
427 ICU default maps remove backquote (`).
429 Command 'search' takes limit parameter (optional). The limit parameter
430 allows a search to be limited one or more facets and the corresponding
431 values. This is for server side filtering.
433 Configure tweak: Use -lm for log(3) if needed
437 Fix a problem with skiparticle sortkey that could be completely
438 ignored (and reduced to "").
440 Fix dependency problem in pazpar2 RPM package (did not require
441 libyaz4 as it should).
445 Fix memory leak that occurred for command=termlist&name=xtargets .
447 Pazpar2 may save HTTP requests. Enabled by option -R.
451 Experimental support for DTIC DADS target. New dads-pz2.xsl.
453 Support for query_syntax (overrides the default for SRU | Z39.50)
455 Support for extraArgs (ZOOM "extraArgs" option) for targets
457 New commands: status-server and status-session
461 Fix for threaded runs: Client now have a copy of the database URL,
462 which can used after the database has been release from the client.
463 This makes the logging in the connection idle timeout of the client nicer (no NOURL) and should be thread-safe.
465 tmarc.xsl: Add journal-title-abbrev and full text.
467 cf.xsl: new fields: isbn, issn, journaltitle, volume, issue
469 Fix for cmd=record before search.
471 Session Logging clean up.
473 Fix wrong termlist factor when maxrecs is different from 100.
477 Fix missing pz:termlist_term_factor in settings.c messed up pz:preferred.
478 Term factor is default enabled but can be diseabled by
479 pz:termlist_term_factor=0
483 Add scaling of facet count. Currently always enabled, needs fixing.
484 Allow user-defined info for target suffix. This has no meaning in
485 Pazpar2 except to distinguish targets from each other. The suffix
486 data begins with #. For example z3950.indexdata.com/gils#Mydata
488 Added exact-match recordfilter; format name=value
492 SOLR support. Pazpar2 may operate as web service client for SOLR.
496 Fix for show command and block=1 (dead lock). Bug was introduced in
501 New RPM packages: pazpar2, pazpar2-js, pazpar2-doc. These have been
502 tested on CentOS 5.5 only.
506 Fix problem with result sets being removed from a client session
507 if the connection for it was resused by another session. Bug #3489.
509 New iphone UI for Pazpar2 (www/iphone).
513 Fixes for threaded operation.
515 New stylesheets for TurboMARC: tmarc.xsl and opac_turbomarc.xsl.
517 New example services in etc/services in source. In the Debian packages
518 these are located in /etc/pazpar2/services-available
520 Threaded mode operational on Windows. Requires Windows 7 or Windows
523 Default value of setting pz:max_connections is 0 which means that there
524 is no limit on number of connections.
528 Pazpar2 may operate in threaded mode. Enabled by element threads in
529 the configuration. See pazpar2_conf for details.
531 New setting setting: pz:max_connections. Setting pz:max_connections is
532 a limit of number of sockets to a host. When this limit is reached,
533 Pazpar2 will wait up to 5 seconds for a connection to becomes available.
534 The client will be marked Client_Error when it can not be searched
535 (other clients in a session may work). If pz:max_connections is not set
536 for a target, a value of 30 will be used. Note: the pz:max_connections
537 will only work in threaded mode.
539 pz2.js: JSON support for show.
541 Debian package: Enable default service, default.xml, before starting
542 Pazpar2 only if there is no service already in /etc/pazpar2/services-enabled.
546 Debian version depends on on libyaz4. Note that Pazpar2 will still
547 compile from source with YAZ 3.
549 Split services into separate files. The example configuration file
550 pazpar2.cfg.dist now includes a default service default.xml (part of
551 etc). And default.xml includes settings/edu.xml. The default.xml file,
552 not to be confused with settings/defaults.xml, is a template for jsdemo
553 and other services. The Debian package installs /etc/pazpar2/server.xml
554 which is now the main pazpar2 configuration (used to be called pazpar2.cfg).
555 server.xml includes services from /etc/pazpar2/services-enabled/*.xml .
556 The default.xml (from etc) is installed in /etc/pazpar2/services-available
557 and a symlink to it is created from services-enabled. The default.xml
558 service is unnamed and, thus, will be used by jsdemo and test1.
560 New setting pz:negotiation_charset. Patch from Andrei V. Toutoukine. The
561 new setting pz:negotiation_charset specifies character set for Z39.50 Init.
565 Support for additional fields in cf.xsl and pazpar2.conf.dist:
566 publisher, available, due, location (=locallocation), callno
567 (=callnumber), thumburl and score.
569 Describe pz:xslt and the auto setting.
571 Move mergekey definition away from the normalization stylesheets and
572 define a mergekey common for all target types in pazpar2.cfg.
574 Code update: Use the Odr_int type for hit counts. This is part of
575 YAZ 3.0.47 and later and so configure checks for that.
579 Metadata attribute 'skiparticle' also works for ICU based
580 normalization. (was only working for the non-ICU/ASCII before).
582 Command bytarget with argument settings=1 will show settings per
583 target.. This is to be able to verify correct settings and be able to
584 test that they are correct. The database settings array size is now
585 also stored.. Problems with database settings array is that if not
586 careful it will be too small (smaller than dictionary per-service
589 Make record list sorting stable by comparing mergekey for records if
590 relevance/title or other sorting criteria all match. This is merely to
591 ensure that our regressions tests works (reproducible output).
593 Relevance calculation changes: use a different denominator (length) for
594 per-field relevance scoring.. Instead of length of all ranked fields we
595 now use length of individual fields (as if they were individual "free"
596 text fields). This will ensure that documents with a long field with no
597 match (say description) will not "hurt" a title match.
599 Diagnostic member was not set on connection error. Fixed
603 Command search takes two optional parameters, startecs and maxrecs,
604 that specifies the start offset (0, 1, ...) and maximum number of records
605 to fetch for each target.
607 XSLTs + MARC maps are cached within a session so we don't re-parse
608 them over and over again. Even for a session with a single search
609 there's much to be gained because many targets use the same
612 The metadata attribute 'mergekey' now takes one of three values 'no',
613 'required', 'optional' . And the resulting mergekey from metadata
614 is now ordered in the same way as metadata in the service definition.
615 Older Pazpar2 version use the order in which metadata appeared in a
618 The search argument 'filter' now offers a new operator ~ which does a
619 substring match. The = operator works as before: string match for
620 anything but pz:id, or target match for pz:id.
622 New setting pz:recordfilter. The value of this setting takes the
623 form name[~value]. This setting makes Pazpar2 ignore all retrieved
624 records that do not have the metadata element name with value substring
627 Pazpar2 allows YAZ log level to be set (option -v).
631 For WS responses Pazpar2 creates XML header. Exception: raw record.
633 Setting XML files are now stored in etc/settings instead of etc. This
634 reflects the layout with the Debian package layout.
636 Settings may be posted for command=settings. The POSTed settings must
637 have root element 'settings' like regular setting files. In order to be
638 recognized, the POST request must use Content-Type=text/xml.
640 A service may be posted for command=init. This service will be used
641 during the session. The service may have its own target settings,
642 ICU config, timeout, etc. In order to be recognized, the POST request
643 must use Content-Type=text/xml.
645 Timeout values may be given per-service. That's element 'timeout'
646 which takes three attribute values (a subset may be given): 'session',
647 'z3950_operation', 'z3950_session'. Option -T is no longer supported
648 - used to specify session timeout.
650 Option -t tests the Pazpar2 configuration and returns exit code
651 (0=success, non-zero=failure). In previous version of Pazpar2, -t
652 specified local settings.
654 In version 1.2.0 the configuration file - after include processing -
655 was dumped to stdout. Now, the configuration is only dumped to the
656 yaz log file if option -d is given.
660 Configuration may now have multiple server areas. This means that a
661 Pazpar2 instance may listen on multiple ports. Virtual hosting is not
662 yet supported - on a server basis. Configuration may also have multiple
663 services .. That is repeating service elements inside a server. Each
664 has an attribute 'id' which serves as service ID. This ID in turn may
665 be used in a Pazpar2 session, by specifying parameter service=ID for
666 command init. There can be at most one unnamed service inside a server
667 which can be referred to by not specifying an service ID for command
668 init (backwards compatible). In order to partition multiple servers and
669 services a new include directive has been added. This takes an attribute
670 'src' which specifies one or more sub-files. For example to include
671 service files, one might use:
672 <server >.. <include src=/"etc/pazpar2/conf.d/*.xml"/> .. </server>.
673 It is the intention that that completely makes the settings directive
676 Fix problem where the record command would wait forever if there were
677 no targets to wait for (activeclients == 0).
681 One result set is created per session (last search) rather than for
682 each connection which happen to be shared (bug #3009).
684 marc21 stylesheets changed for efficiency.
688 Session timeout may be specified on the command-line as option -T.
690 Pazpar2 may now be operated in a no-merged mode for records.. All records
691 will be considered unique. This mode is enabled if no mergekey is
692 generated by the normalization stylesheet (pz:xslt).
694 Pazpar2 caches original records from each target and the 'record' command
695 with offset returns the original record if 'syntax' and 'esn' are NOT
696 specified. This speeds up retrieval of original records but also means
697 that Pazpar2 uses more memory. The cached records will be freed when the
698 session terminates or a new search is executed.
700 Pazpar2 no longer uses its own ICU wrapper. Instead the ICU wrapper
701 library part of YAZ is used.
703 Added SRU client support.
705 Automatically computes pz:nativesyntax if not provided. Works for XML and
708 --- 1.0.13 2008/11/24
710 Command bytarget returns name of target (if defined).
712 --- 1.0.12 2008/11/04
714 Fixed bug #2021.. location now holds all brief elements.
716 --- 1.0.11 2008/10/15
718 Fixed check for application/x-www-form-urlencoded parameters.
720 --- 1.0.10 2008/10/14
722 Fixes for IE in pz2.js.
724 Fixed bug #2021: non-merged, brief meta data NOT included for command=show.
728 Changed the JS library pz2.js to use POST for long URL (+ params).
730 Added installation instructions for Windows. Note: NT services is
731 NOT available until we make a new release of YAZ.
733 Preserve order of repeated metadata fields (they were reversed before).
735 More MARC21 information extracted for metadata.
739 Fixed bug #1162: HTML entities are not escaped properly.
741 Native Windows port of Pazpar2. Makefile for Visual Studio provided.
745 Marc21 stylesheet updated to reflect multiple full text fields
749 Fixed bug in pz2.js WRT DOMElement attributes on IE.
751 Fixed bug 2100: Database wildcards not working
755 Added support for retrieval of records in binary.
757 Fixed bug 1794: Pazpar2 does not return valid XML.
759 Deal with ICU not returning sortkey (resulted in SEGV before).
763 JavaScript library pzw2.js throws error if WS response (from Pazpar2 or
764 other) is malformed (non-wellformed XML or missing Pazpar2 OK status).
766 Improved diagnostics when Pazpar2 HTTP decoding fails.
768 Pazpar2 requests may be POSTed as using Content-Type
769 application/x-www-form-urlencoded.
771 Pazpar2 honors LF in HTTP headers.
773 Handle targets that handle negative hit counts (should not happen, but it
778 ICU is used for tokenization and normalization of the following: mergekey,
779 sorting, relevance terms.
781 Debian package now enables ICU tokenization and normalization by default.
785 Exposed user setting values (i.e. non-pz: names) to the record systems in two
786 ways: Either as parameters to the normalization stylesheets (which would allow the
787 programmer to postprocess or use the values in any way) or after the normalization
788 step, in which case values are made part of the normalized record (and available for
789 sorting, termlists, display, or other interface-related use.
791 Implemented sorting by year.
793 Option -d dumps records to the current log file instead of stderr.
795 Fixes for compilation on cygwin.
797 Z39.50 client code uses pz:elements. pz:elements was recognized in
798 earlier Pazpar2 versions but it was not used for anything.
800 icu_chain_test is using fgets instead of getline - fixes compilation
803 Loosen the CCL query parsing so that Pazpar2 only returns error if _all_
804 query conversions fail (rather than _any_). This means targets that do
805 not support some fields are ignored in a search.
809 Improved handling of socket timeout for Z39.50 connections.
811 Misc documentation updates and spell fixes.
813 Debian package pazpar2 creates log rotate entry.
815 Debian package pazpar2-apache2 reloads Apache2.
817 jsdemo included in distribution. It illustrates the use of the js/pz2.js
822 First public release.