1 Fix memory leak WRT client structures (incorrect inc ref count).
3 Log when a HTTP response is serialized and the time elapsed.
5 New command, service, which returns current service XML in use for
10 Local limit for fields of type "generic" (ie text fields) are
11 now normalized by mergekey rule before comparison takes place.
12 Before, no normalization took place and comparsion was, thus, exact.
14 New facility: dynamic rank , which allows ranking to be changed
15 for an existing result set. The rank can be set for search or
16 show. This overrides the rank for metadata elements (which fields
19 New facility:dynamic mergekey , which allows mergekey to be changed
20 for an existing result set. The mergekey can be set for search or
23 HTTP server: host=@ listens on IPV6 and IPV4 if possible.
24 Also, allow ports to be given as names (not just integers).
25 Fix @-notation on systems that don't support IPV6 sockets.
29 Add MasterKey Connect configuration. Refer to section "non-standard
30 databases" for more information.
32 Allow timeformat for log to be specified with option -m (as Metaproxy
35 New Debian package pazpar2-dbg.
37 Fix NULL ptr reference of se->relevance. If a new search is initiated
38 and a CCL query fails to parse, Pazpar2 could crash.
40 Fix problem with host/port mangling in Pazpar2 HTTP server. Problem
41 existed in 1.6.29 only.
45 IPV6 updates. Allow IPv6 addresses for database hosts and IPv6 address
46 for HTTP server. By default the HTTP server uses IPv4 only, but that can be
47 changed by setting "host" attribute for the "listen" element.
49 Change semantics of pz:extendrecs. Allow for repeated fetches .
50 pz:extendrecs is now the number of extra records to fetch (was total
55 Fix hang or memory violation if show occurred before a search. (not that
56 it makes much sense to perform a show before a search).
60 pz2.js: Element_parseChildNodes concatenates all Text/CDATA nodes, instead
65 New pz:metadata attribute, empty="empty-value" for Pazpar2's
66 internal representation. With this attribute, Pazpar2 treates an empty
67 pz:metadata type as having the value for "empty" - if empty.
69 New setting, pz:extendrecs, which triggers extended fetch of records
70 for a database beyond pz:maxrecs for a show command.
72 Fix warning that was falsely issued for "missing limitmap".
74 Log message for Pazpart start/stop changed. Now using same style as
75 Metaproxy, ie Pazpar2 start SHA1 / Pazpar2 stop .
79 Fix hang of 2nd command=show with esn/syntax given.
83 New merge attribute type: 'first', which takes all metadata fields
84 from first target that returns the particular field.
88 Extend info command with hostname and YAZ SHA1
89 Indent results for both command stat and info.
91 Allow limit on merged content. The new configuration metadata
92 element, limitcluster, configures that a metadata element (name) be used
93 as limit name for search. Applies to the whole service (ie all targets),
94 unlike pz:limitmap which is configured per-target (database).
96 New feature: limitmap local:* matches against all metadata fields.
98 Allow repeated list in limitmap spec . Separated by comma. For
99 example: value="local:title,rpn:@attr 1=4".
101 New element <message> in bytarget response. Holds diagnostic message
102 of code (say 'Unsupported Use Attribute' for Bib-1 114).
104 Improved logging for record ingestion failures.
106 Avoid using struct icu_chain in non-YAZ_HAVE_ICU mode. In the rare case,
107 when YAZ is compiled without ICU support.
109 --- 1.6.22 2012/10/11
111 Requires YAZ-4.2.40 to support native solr support.
113 Fix and improve logic handling whether or not to re-do search on sort
114 order changes. A sort order with change in ascending/descending only
115 whould not trigger a new search, which is required for targets with
116 native sorting capabilities. Each client is now checked if instructions
117 (sortmap) exist for native sorting and only client that does requires
118 it is researched. Other clients is just re-ingesting the records,
119 they already have. The resultset is now cleared if any researching
122 Connection sharing between session has broken since version 1.6.8 with
123 introduction of logic that would minimize searching if pazpar2 could
124 detect this based on same query and limits and partly sort order.
125 This could lead to segementations violations.
127 Added a chapter in the manaul about relevance ranking.
129 --- 1.6.21 2012/09/24
131 Rank tweak: follow=number will increase mult by number if two terms
132 occur next to each other; number-1 if they are one term apart , .. 0
133 if they are number a part (all in order). Default is 0 (following
134 terms has no effect).
136 Rank tweak: lead=k will divide mult by 1 + log2(1+k*l) where k is
137 value given by lead and l is length from beginning of field where
138 term occurs (l=0 for first term, l=1 for second term, ..). Default
141 Rank tweak: length=strategy. length="linear" if mult is to be divided
142 by length (existing, default behavior), length="log" if mult is to be
143 divided by log2(1+length), length="none" if mult is not to be affected
146 --- 1.6.20 2012/09/21
148 Rank algorithm details may be printed as part of show response in
149 element <relevance_info>.. This is only printed if <rank debug="yes"/>
152 Record as returned by show/record command have a minimal indentation
153 which makes things human-readable.
155 New configuration of default sorting criteria (sort-default) in
156 service definition. If no criteria is defined it will be as before
159 Search command now supports sort parameter just as the show command.
160 If no parameter is give, it will use the service sort-default value.
162 --- 1.6.19 2012/09/18
164 Rank algorithm skips strings that gets normalized to empty string.
165 For example, & and ! could map to the empty string. The weight for
166 those terms is now 0 (as if they were not part of the query).
168 Rank algorithm does not use CCL from limitmap; only from the query
169 parameter (user query).
173 --- 1.6.18 2012/09/17
175 Rank algorithm configurable by 'rank' element inside service. So far
176 only, attribute 'cluster' is recognized. If cluster="yes", multiple
177 records inside a cluster boosts higher than single records. This
178 is default behavior and existing behavior. cluster="no" takes the
179 average score of each record in a cluster.
181 --- 1.6.17 2012/09/05
183 Fix bad re-use of connections (connections with changing proxy should not
186 --- 1.6.16 2012/08/22
188 Fix a bug introduce in 1.6.15 around the position sorting. It resetted the
189 resultset and sorting when the sort order is position. However this will be done on
190 every client poll, which will make pazpar2 continuing reset and fetching.
191 It should only be done on FIRST request where the sort order change.
193 Fix an issue on suggestion option: Also disable suggestions on empty string.
195 Clean up in turbo marc stylesheet.
197 Remove the hardcoded size of termlists.
199 --- 1.6.15 2012/06/27
201 New facility: ccldirective may be given in service definition. Allows
202 CCL parsing to be customized a bit, such as defining names of operators
205 New facility: raw record by checksum, rather than offset. The record
206 command optionally takes checksum which identifies certain record from
209 New facility: per field ranking. Rank may be given as M [F N] where
210 M is default rank and N is rank for CCL terms from field F.
212 --- 1.6.14 2012/06/04
214 Fix for IE7/8 in pz.js
216 Applied patch from Giannis Kosmas on keepAlive, which also adds keepAlive to init response.
218 Lower log level some places.
220 Remove some invalid test results.
222 --- 1.6.13 2012/05/23
224 Introducing a version=2 parameter for show, termlist and bytarget commands.
225 This enables pazpar2 to return approximation on hit and count count when
226 doing record filtering using the limit parameter on search and a
227 limitmap with a value of "local:"
229 Setting pz:xslt may embed local XSLT as an alternative to referring
231 Value is not CDATA but XML nodes embedded, so escaping is not necessary
232 but a root element *must* be present. For example:
233 <settings target="target="z3950.indexdata.com/marc">
242 Metadata field rank may given by XML internal document (pz:xslt
243 result). If rank is not given, the rank from service description is
246 Metadata field can now configured a default limitmap and facetmap.
247 Setting limitmap to "local:" would work for all kind of targets, but would
248 prob. not be the optimal solution. But at least better than the default behavior
249 of pazpar2 where no filtering is done.
251 A service definition can now also contains <set/> that defines service-wide
252 settings. These will override server-wide sets and will be overridded by
255 New setting, pz:present_chunk, that specifies number of records to fetch
256 at a time. Zero will disable chunkation; will fetch max_records at once.
258 --- 1.6.12 2012/03/14
260 Revert the format change in termlist response, that could break
261 some clients / UIs since they were expecting an (empty) element
262 if no facet values was found.
264 --- 1.6.11 2012/03/07
266 Revert the behavior of returning errors when unable to block
267 on termlist, bytarget and search, when unable to block due to
268 other block. The client will now receive a regular response,
269 but it will be logged in the server. A parameter (report) is
270 added to change behavior to return error response or WARNING
271 status message. Consider this "API" as private, as it is mostly
272 untested and could be changed in future releases.
274 Fix spell error in pz2.js fix in 1.6.10.
276 New Marc2TurboMarc.xsl (contribution from Sven Porst).
277 Can solve the missing marc21.xsl updates in some cases.
279 tmarc.xsl: Simplify the 6xx to subject-long and fix 1-based
280 substring (contribtion from Sven Porst)
282 marc21.xsl: fix 1-based substring call
284 tmarc.xsl and marc21.xsl: use 856$a as last option for electronic-text.
286 Add test_termlist_block to test suite
288 --- 1.6.10 2012/02/23
290 Fix SEGV for invalid PQFs and SRU/SOLR targets
291 Also refactor a bit the code that converts from PQF to SRU/SOLR queries.
293 Fix pz2.js: "null object" due to change in in bytarget result XML.
295 Fixes in tmarc.xsl: Subject-long shorten for extra commas only.
296 Added this normalization to the other subject-long fields (d6xx),
297 where it was missing.
299 Fixes in marc21.xsl: Updated with most of the new tmarc.xsl.
300 Still differences around medium and holdings. marc21.xsl is not
301 longer active used by Index Data, and should be considered unsupported.
302 Use tmarc.xsl instead.
306 Fix SEGV that could occur for failed connections.
310 Fix bug for command sort that could return no results for active clients
311 (from previous search). This bug was present in 1.6.6-1.6.7.
313 Fix bug in results that could include results that should have been
314 filtered out. This bug was present in 1.6.6-1.6.7.
318 Fix bug introduced in 1.6.6 where a connection re-use could stall
321 Local filtering may now specify a local metadata field, eg.
322 pz:limitmap:somefield[t]=local:otherfield
326 For search, when limit and or filtering is in place and search
327 is identical to previous search, the result set is re-used and the
328 target is not searched.
330 Limits may work perform local filtering as well, by using "local:"
335 Updated bytarget command to contain a suggestions element with misspelled
336 words and suggestions to these. pz2.js has been updated to deliver this
337 onwards as well. Only target that currently delivers this is the solr
338 client in YAZ 4.2.18.
342 New service definition element, xslt, that allows an embedded stylesheet
343 to be defined. This can be referred to from pz:xslt as an alternative to
346 New pz:sortmap:field setting for specifying hints on how to make
347 a target natively sort on a field. This is used for command=show in
348 conjunction with sort.
350 New pz:url setting for specifying the actual URL for a target. When
351 this is used the target ID is not used as URL anymore and the target ID
352 may be almost any string (not including []).
354 command=termlist without name parameter returns all termlists/facets.
355 Previously if name parameter was omitted, only "subject" was returned.
359 Make termlist sorting stable. Terms with same frequency are now sorted by
360 their display name. This makes a pretty display and improves our
361 regression test because qsort is not a stable sort.
363 New sort parameter value 'position'. The 'position' sorts merged records
364 by their original position from the remote target. This is primarily useful
365 for debugging and may be used for targets that already perform some kind
366 of relevance ranking. Note that sort by default is decreasing; so to get
367 records in their original order sort=position:1 must be used.
371 tmarc.xsl: yet another 773$g fix. Was broken in 1.6.1 as well.
373 Facility to change working directory for pazpar2 daemon. Option -wdir
374 sets working directory to dir. This facility is useful if core dumps
375 must be saved. In this case, the current working directory must be
376 writable by the running user, such as "nobody".
380 New configuration element <icu_chain> for <server>/<service> which
381 allows a named ICU rule (chain) to be defined. The names relevance,
382 sort, mergekey and facet are used for those operations. The definition
383 <icu_chain id="sort" locale="en"> .. </icu_chain>
385 <sort> <icu_chain locale="en> ... </icu_chain> </sort>
386 And so on.. for relevance, mergekey and facet as well. The latter
387 style is deprecated. The facet terms are normalized by the facet
388 rule by default. This may be changed on a metadata field basis by
389 defining the new attribute 'facetrule' for the metadata element.
391 <icu_chain id="myrule" locale="en"> ... </icu_chain>
392 <metadata name="author" termlist="yes" facetrule="myrule"/>
394 Preserve rorder for merged metadata. Fixes issue as reported by Sven
395 Porst: http://lists.indexdata.dk/pipermail/yazlist/2011-July/003230.html
397 tmarc.xsl: set journal-subpart to 773$ only.
401 Modify the behavior for the limit parameter (first defined in 1.5.7).
402 Mapping of limit searches are now defined by the new configuration item
403 pz:limitmap. Fix a dead-lock problem with the limit parameter.
405 Extend tmarc.xsl to extract 773$g data (OpenURL).
409 ICU default maps remove backquote (`).
411 Command 'search' takes limit parameter (optional). The limit parameter
412 allows a search to be limited one or more facets and the corresponding
413 values. This is for server side filtering.
415 Configure tweak: Use -lm for log(3) if needed
419 Fix a problem with skiparticle sortkey that could be completely
420 ignored (and reduced to "").
422 Fix dependency problem in pazpar2 RPM package (did not require
423 libyaz4 as it should).
427 Fix memory leak that occurred for command=termlist&name=xtargets .
429 Pazpar2 may save HTTP requests. Enabled by option -R.
433 Experimental support for DTIC DADS target. New dads-pz2.xsl.
435 Support for query_syntax (overrides the default for SRU | Z39.50)
437 Support for extraArgs (ZOOM "extraArgs" option) for targets
439 New commands: status-server and status-session
443 Fix for threaded runs: Client now have a copy of the database URL,
444 which can used after the database has been release from the client.
445 This makes the logging in the connection idle timeout of the client nicer (no NOURL) and should be thread-safe.
447 tmarc.xsl: Add journal-title-abbrev and full text.
449 cf.xsl: new fields: isbn, issn, journaltitle, volume, issue
451 Fix for cmd=record before search.
453 Session Logging clean up.
455 Fix wrong termlist factor when maxrecs is different from 100.
459 Fix missing pz:termlist_term_factor in settings.c messed up pz:preferred.
460 Term factor is default enabled but can be diseabled by
461 pz:termlist_term_factor=0
465 Add scaling of facet count. Currently always enabled, needs fixing.
466 Allow user-defined info for target suffix. This has no meaning in
467 Pazpar2 except to distinguish targets from each other. The suffix
468 data begins with #. For example z3950.indexdata.com/gils#Mydata
470 Added exact-match recordfilter; format name=value
474 SOLR support. Pazpar2 may operate as web service client for SOLR.
478 Fix for show command and block=1 (dead lock). Bug was introduced in
483 New RPM packages: pazpar2, pazpar2-js, pazpar2-doc. These have been
484 tested on CentOS 5.5 only.
488 Fix problem with result sets being removed from a client session
489 if the connection for it was resused by another session. Bug #3489.
491 New iphone UI for Pazpar2 (www/iphone).
495 Fixes for threaded operation.
497 New stylesheets for TurboMARC: tmarc.xsl and opac_turbomarc.xsl.
499 New example services in etc/services in source. In the Debian packages
500 these are located in /etc/pazpar2/services-available
502 Threaded mode operational on Windows. Requires Windows 7 or Windows
505 Default value of setting pz:max_connections is 0 which means that there
506 is no limit on number of connections.
510 Pazpar2 may operate in threaded mode. Enabled by element threads in
511 the configuration. See pazpar2_conf for details.
513 New setting setting: pz:max_connections. Setting pz:max_connections is
514 a limit of number of sockets to a host. When this limit is reached,
515 Pazpar2 will wait up to 5 seconds for a connection to becomes available.
516 The client will be marked Client_Error when it can not be searched
517 (other clients in a session may work). If pz:max_connections is not set
518 for a target, a value of 30 will be used. Note: the pz:max_connections
519 will only work in threaded mode.
521 pz2.js: JSON support for show.
523 Debian package: Enable default service, default.xml, before starting
524 Pazpar2 only if there is no service already in /etc/pazpar2/services-enabled.
528 Debian version depends on on libyaz4. Note that Pazpar2 will still
529 compile from source with YAZ 3.
531 Split services into separate files. The example configuration file
532 pazpar2.cfg.dist now includes a default service default.xml (part of
533 etc). And default.xml includes settings/edu.xml. The default.xml file,
534 not to be confused with settings/defaults.xml, is a template for jsdemo
535 and other services. The Debian package installs /etc/pazpar2/server.xml
536 which is now the main pazpar2 configuration (used to be called pazpar2.cfg).
537 server.xml includes services from /etc/pazpar2/services-enabled/*.xml .
538 The default.xml (from etc) is installed in /etc/pazpar2/services-available
539 and a symlink to it is created from services-enabled. The default.xml
540 service is unnamed and, thus, will be used by jsdemo and test1.
542 New setting pz:negotiation_charset. Patch from Andrei V. Toutoukine. The
543 new setting pz:negotiation_charset specifies character set for Z39.50 Init.
547 Support for additional fields in cf.xsl and pazpar2.conf.dist:
548 publisher, available, due, location (=locallocation), callno
549 (=callnumber), thumburl and score.
551 Describe pz:xslt and the auto setting.
553 Move mergekey definition away from the normalization stylesheets and
554 define a mergekey common for all target types in pazpar2.cfg.
556 Code update: Use the Odr_int type for hit counts. This is part of
557 YAZ 3.0.47 and later and so configure checks for that.
561 Metadata attribute 'skiparticle' also works for ICU based
562 normalization. (was only working for the non-ICU/ASCII before).
564 Command bytarget with argument settings=1 will show settings per
565 target.. This is to be able to verify correct settings and be able to
566 test that they are correct. The database settings array size is now
567 also stored.. Problems with database settings array is that if not
568 careful it will be too small (smaller than dictionary per-service
571 Make record list sorting stable by comparing mergekey for records if
572 relevance/title or other sorting criteria all match. This is merely to
573 ensure that our regressions tests works (reproducible output).
575 Relevance calculation changes: use a different denominator (length) for
576 per-field relevance scoring.. Instead of length of all ranked fields we
577 now use length of individual fields (as if they were individual "free"
578 text fields). This will ensure that documents with a long field with no
579 match (say description) will not "hurt" a title match.
581 Diagnostic member was not set on connection error. Fixed
585 Command search takes two optional parameters, startecs and maxrecs,
586 that specifies the start offset (0, 1, ...) and maximum number of records
587 to fetch for each target.
589 XSLTs + MARC maps are cached within a session so we don't re-parse
590 them over and over again. Even for a session with a single search
591 there's much to be gained because many targets use the same
594 The metadata attribute 'mergekey' now takes one of three values 'no',
595 'required', 'optional' . And the resulting mergekey from metadata
596 is now ordered in the same way as metadata in the service definition.
597 Older Pazpar2 version use the order in which metadata appeared in a
600 The search argument 'filter' now offers a new operator ~ which does a
601 substring match. The = operator works as before: string match for
602 anything but pz:id, or target match for pz:id.
604 New setting pz:recordfilter. The value of this setting takes the
605 form name[~value]. This setting makes Pazpar2 ignore all retrieved
606 records that do not have the metadata element name with value substring
609 Pazpar2 allows YAZ log level to be set (option -v).
613 For WS responses Pazpar2 creates XML header. Exception: raw record.
615 Setting XML files are now stored in etc/settings instead of etc. This
616 reflects the layout with the Debian package layout.
618 Settings may be posted for command=settings. The POSTed settings must
619 have root element 'settings' like regular setting files. In order to be
620 recognized, the POST request must use Content-Type=text/xml.
622 A service may be posted for command=init. This service will be used
623 during the session. The service may have its own target settings,
624 ICU config, timeout, etc. In order to be recognized, the POST request
625 must use Content-Type=text/xml.
627 Timeout values may be given per-service. That's element 'timeout'
628 which takes three attribute values (a subset may be given): 'session',
629 'z3950_operation', 'z3950_session'. Option -T is no longer supported
630 - used to specify session timeout.
632 Option -t tests the Pazpar2 configuration and returns exit code
633 (0=success, non-zero=failure). In previous version of Pazpar2, -t
634 specified local settings.
636 In version 1.2.0 the configuration file - after include processing -
637 was dumped to stdout. Now, the configuration is only dumped to the
638 yaz log file if option -d is given.
642 Configuration may now have multiple server areas. This means that a
643 Pazpar2 instance may listen on multiple ports. Virtual hosting is not
644 yet supported - on a server basis. Configuration may also have multiple
645 services .. That is repeating service elements inside a server. Each
646 has an attribute 'id' which serves as service ID. This ID in turn may
647 be used in a Pazpar2 session, by specifying parameter service=ID for
648 command init. There can be at most one unnamed service inside a server
649 which can be referred to by not specifying an service ID for command
650 init (backwards compatible). In order to partition multiple servers and
651 services a new include directive has been added. This takes an attribute
652 'src' which specifies one or more sub-files. For example to include
653 service files, one might use:
654 <server >.. <include src=/"etc/pazpar2/conf.d/*.xml"/> .. </server>.
655 It is the intention that that completely makes the settings directive
658 Fix problem where the record command would wait forever if there were
659 no targets to wait for (activeclients == 0).
663 One result set is created per session (last search) rather than for
664 each connection which happen to be shared (bug #3009).
666 marc21 stylesheets changed for efficiency.
670 Session timeout may be specified on the command-line as option -T.
672 Pazpar2 may now be operated in a no-merged mode for records.. All records
673 will be considered unique. This mode is enabled if no mergekey is
674 generated by the normalization stylesheet (pz:xslt).
676 Pazpar2 caches original records from each target and the 'record' command
677 with offset returns the original record if 'syntax' and 'esn' are NOT
678 specified. This speeds up retrieval of original records but also means
679 that Pazpar2 uses more memory. The cached records will be freed when the
680 session terminates or a new search is executed.
682 Pazpar2 no longer uses its own ICU wrapper. Instead the ICU wrapper
683 library part of YAZ is used.
685 Added SRU client support.
687 Automatically computes pz:nativesyntax if not provided. Works for XML and
690 --- 1.0.13 2008/11/24
692 Command bytarget returns name of target (if defined).
694 --- 1.0.12 2008/11/04
696 Fixed bug #2021.. location now holds all brief elements.
698 --- 1.0.11 2008/10/15
700 Fixed check for application/x-www-form-urlencoded parameters.
702 --- 1.0.10 2008/10/14
704 Fixes for IE in pz2.js.
706 Fixed bug #2021: non-merged, brief meta data NOT included for command=show.
710 Changed the JS library pz2.js to use POST for long URL (+ params).
712 Added installation instructions for Windows. Note: NT services is
713 NOT available until we make a new release of YAZ.
715 Preserve order of repeated metadata fields (they were reversed before).
717 More MARC21 information extracted for metadata.
721 Fixed bug #1162: HTML entities are not escaped properly.
723 Native Windows port of Pazpar2. Makefile for Visual Studio provided.
727 Marc21 stylesheet updated to reflect multiple full text fields
731 Fixed bug in pz2.js WRT DOMElement attributes on IE.
733 Fixed bug 2100: Database wildcards not working
737 Added support for retrieval of records in binary.
739 Fixed bug 1794: Pazpar2 does not return valid XML.
741 Deal with ICU not returning sortkey (resulted in SEGV before).
745 JavaScript library pzw2.js throws error if WS response (from Pazpar2 or
746 other) is malformed (non-wellformed XML or missing Pazpar2 OK status).
748 Improved diagnostics when Pazpar2 HTTP decoding fails.
750 Pazpar2 requests may be POSTed as using Content-Type
751 application/x-www-form-urlencoded.
753 Pazpar2 honors LF in HTTP headers.
755 Handle targets that handle negative hit counts (should not happen, but it
760 ICU is used for tokenization and normalization of the following: mergekey,
761 sorting, relevance terms.
763 Debian package now enables ICU tokenization and normalization by default.
767 Exposed user setting values (i.e. non-pz: names) to the record systems in two
768 ways: Either as parameters to the normalization stylesheets (which would allow the
769 programmer to postprocess or use the values in any way) or after the normalization
770 step, in which case values are made part of the normalized record (and available for
771 sorting, termlists, display, or other interface-related use.
773 Implemented sorting by year.
775 Option -d dumps records to the current log file instead of stderr.
777 Fixes for compilation on cygwin.
779 Z39.50 client code uses pz:elements. pz:elements was recognized in
780 earlier Pazpar2 versions but it was not used for anything.
782 icu_chain_test is using fgets instead of getline - fixes compilation
785 Loosen the CCL query parsing so that Pazpar2 only returns error if _all_
786 query conversions fail (rather than _any_). This means targets that do
787 not support some fields are ignored in a search.
791 Improved handling of socket timeout for Z39.50 connections.
793 Misc documentation updates and spell fixes.
795 Debian package pazpar2 creates log rotate entry.
797 Debian package pazpar2-apache2 reloads Apache2.
799 jsdemo included in distribution. It illustrates the use of the js/pz2.js
804 First public release.