3 Local limit for fields of type "generic" (ie text fields) are
4 now normalized by mergekey rule before comparison takes place.
5 Before, no normalization took place and comparsion was, thus, exact.
7 New facility: dynamic rank , which allows ranking to be changed
8 for an existing result set. The rank can be set for search or
9 show. This overrides the rank for metadata elements (which fields
12 New facility:dynamic mergekey , which allows mergekey to be changed
13 for an existing result set. The mergekey can be set for search or
16 HTTP server: host=@ listens on IPV6 and IPV4 if possible.
17 Also, allow ports to be given as names (not just integers).
18 Fix @-notation on systems that don't support IPV6 sockets.
22 Add MasterKey Connect configuration. Refer to section "non-standard
23 databases" for more information.
25 Allow timeformat for log to be specified with option -m (as Metaproxy
28 New Debian package pazpar2-dbg.
30 Fix NULL ptr reference of se->relevance. If a new search is initiated
31 and a CCL query fails to parse, Pazpar2 could crash.
33 Fix problem with host/port mangling in Pazpar2 HTTP server. Problem
34 existed in 1.6.29 only.
38 IPV6 updates. Allow IPv6 addresses for database hosts and IPv6 address
39 for HTTP server. By default the HTTP server uses IPv4 only, but that can be
40 changed by setting "host" attribute for the "listen" element.
42 Change semantics of pz:extendrecs. Allow for repeated fetches .
43 pz:extendrecs is now the number of extra records to fetch (was total
48 Fix hang or memory violation if show occurred before a search. (not that
49 it makes much sense to perform a show before a search).
53 pz2.js: Element_parseChildNodes concatenates all Text/CDATA nodes, instead
58 New pz:metadata attribute, empty="empty-value" for Pazpar2's
59 internal representation. With this attribute, Pazpar2 treates an empty
60 pz:metadata type as having the value for "empty" - if empty.
62 New setting, pz:extendrecs, which triggers extended fetch of records
63 for a database beyond pz:maxrecs for a show command.
65 Fix warning that was falsely issued for "missing limitmap".
67 Log message for Pazpart start/stop changed. Now using same style as
68 Metaproxy, ie Pazpar2 start SHA1 / Pazpar2 stop .
72 Fix hang of 2nd command=show with esn/syntax given.
76 New merge attribute type: 'first', which takes all metadata fields
77 from first target that returns the particular field.
81 Extend info command with hostname and YAZ SHA1
82 Indent results for both command stat and info.
84 Allow limit on merged content. The new configuration metadata
85 element, limitcluster, configures that a metadata element (name) be used
86 as limit name for search. Applies to the whole service (ie all targets),
87 unlike pz:limitmap which is configured per-target (database).
89 New feature: limitmap local:* matches against all metadata fields.
91 Allow repeated list in limitmap spec . Separated by comma. For
92 example: value="local:title,rpn:@attr 1=4".
94 New element <message> in bytarget response. Holds diagnostic message
95 of code (say 'Unsupported Use Attribute' for Bib-1 114).
97 Improved logging for record ingestion failures.
99 Avoid using struct icu_chain in non-YAZ_HAVE_ICU mode. In the rare case,
100 when YAZ is compiled without ICU support.
102 --- 1.6.22 2012/10/11
104 Requires YAZ-4.2.40 to support native solr support.
106 Fix and improve logic handling whether or not to re-do search on sort
107 order changes. A sort order with change in ascending/descending only
108 whould not trigger a new search, which is required for targets with
109 native sorting capabilities. Each client is now checked if instructions
110 (sortmap) exist for native sorting and only client that does requires
111 it is researched. Other clients is just re-ingesting the records,
112 they already have. The resultset is now cleared if any researching
115 Connection sharing between session has broken since version 1.6.8 with
116 introduction of logic that would minimize searching if pazpar2 could
117 detect this based on same query and limits and partly sort order.
118 This could lead to segementations violations.
120 Added a chapter in the manaul about relevance ranking.
122 --- 1.6.21 2012/09/24
124 Rank tweak: follow=number will increase mult by number if two terms
125 occur next to each other; number-1 if they are one term apart , .. 0
126 if they are number a part (all in order). Default is 0 (following
127 terms has no effect).
129 Rank tweak: lead=k will divide mult by 1 + log2(1+k*l) where k is
130 value given by lead and l is length from beginning of field where
131 term occurs (l=0 for first term, l=1 for second term, ..). Default
134 Rank tweak: length=strategy. length="linear" if mult is to be divided
135 by length (existing, default behavior), length="log" if mult is to be
136 divided by log2(1+length), length="none" if mult is not to be affected
139 --- 1.6.20 2012/09/21
141 Rank algorithm details may be printed as part of show response in
142 element <relevance_info>.. This is only printed if <rank debug="yes"/>
145 Record as returned by show/record command have a minimal indentation
146 which makes things human-readable.
148 New configuration of default sorting criteria (sort-default) in
149 service definition. If no criteria is defined it will be as before
152 Search command now supports sort parameter just as the show command.
153 If no parameter is give, it will use the service sort-default value.
155 --- 1.6.19 2012/09/18
157 Rank algorithm skips strings that gets normalized to empty string.
158 For example, & and ! could map to the empty string. The weight for
159 those terms is now 0 (as if they were not part of the query).
161 Rank algorithm does not use CCL from limitmap; only from the query
162 parameter (user query).
166 --- 1.6.18 2012/09/17
168 Rank algorithm configurable by 'rank' element inside service. So far
169 only, attribute 'cluster' is recognized. If cluster="yes", multiple
170 records inside a cluster boosts higher than single records. This
171 is default behavior and existing behavior. cluster="no" takes the
172 average score of each record in a cluster.
174 --- 1.6.17 2012/09/05
176 Fix bad re-use of connections (connections with changing proxy should not
179 --- 1.6.16 2012/08/22
181 Fix a bug introduce in 1.6.15 around the position sorting. It resetted the
182 resultset and sorting when the sort order is position. However this will be done on
183 every client poll, which will make pazpar2 continuing reset and fetching.
184 It should only be done on FIRST request where the sort order change.
186 Fix an issue on suggestion option: Also disable suggestions on empty string.
188 Clean up in turbo marc stylesheet.
190 Remove the hardcoded size of termlists.
192 --- 1.6.15 2012/06/27
194 New facility: ccldirective may be given in service definition. Allows
195 CCL parsing to be customized a bit, such as defining names of operators
198 New facility: raw record by checksum, rather than offset. The record
199 command optionally takes checksum which identifies certain record from
202 New facility: per field ranking. Rank may be given as M [F N] where
203 M is default rank and N is rank for CCL terms from field F.
205 --- 1.6.14 2012/06/04
207 Fix for IE7/8 in pz.js
209 Applied patch from Giannis Kosmas on keepAlive, which also adds keepAlive to init response.
211 Lower log level some places.
213 Remove some invalid test results.
215 --- 1.6.13 2012/05/23
217 Introducing a version=2 parameter for show, termlist and bytarget commands.
218 This enables pazpar2 to return approximation on hit and count count when
219 doing record filtering using the limit parameter on search and a
220 limitmap with a value of "local:"
222 Setting pz:xslt may embed local XSLT as an alternative to referring
224 Value is not CDATA but XML nodes embedded, so escaping is not necessary
225 but a root element *must* be present. For example:
226 <settings target="target="z3950.indexdata.com/marc">
235 Metadata field rank may given by XML internal document (pz:xslt
236 result). If rank is not given, the rank from service description is
239 Metadata field can now configured a default limitmap and facetmap.
240 Setting limitmap to "local:" would work for all kind of targets, but would
241 prob. not be the optimal solution. But at least better than the default behavior
242 of pazpar2 where no filtering is done.
244 A service definition can now also contains <set/> that defines service-wide
245 settings. These will override server-wide sets and will be overridded by
248 New setting, pz:present_chunk, that specifies number of records to fetch
249 at a time. Zero will disable chunkation; will fetch max_records at once.
251 --- 1.6.12 2012/03/14
253 Revert the format change in termlist response, that could break
254 some clients / UIs since they were expecting an (empty) element
255 if no facet values was found.
257 --- 1.6.11 2012/03/07
259 Revert the behavior of returning errors when unable to block
260 on termlist, bytarget and search, when unable to block due to
261 other block. The client will now receive a regular response,
262 but it will be logged in the server. A parameter (report) is
263 added to change behavior to return error response or WARNING
264 status message. Consider this "API" as private, as it is mostly
265 untested and could be changed in future releases.
267 Fix spell error in pz2.js fix in 1.6.10.
269 New Marc2TurboMarc.xsl (contribution from Sven Porst).
270 Can solve the missing marc21.xsl updates in some cases.
272 tmarc.xsl: Simplify the 6xx to subject-long and fix 1-based
273 substring (contribtion from Sven Porst)
275 marc21.xsl: fix 1-based substring call
277 tmarc.xsl and marc21.xsl: use 856$a as last option for electronic-text.
279 Add test_termlist_block to test suite
281 --- 1.6.10 2012/02/23
283 Fix SEGV for invalid PQFs and SRU/SOLR targets
284 Also refactor a bit the code that converts from PQF to SRU/SOLR queries.
286 Fix pz2.js: "null object" due to change in in bytarget result XML.
288 Fixes in tmarc.xsl: Subject-long shorten for extra commas only.
289 Added this normalization to the other subject-long fields (d6xx),
290 where it was missing.
292 Fixes in marc21.xsl: Updated with most of the new tmarc.xsl.
293 Still differences around medium and holdings. marc21.xsl is not
294 longer active used by Index Data, and should be considered unsupported.
295 Use tmarc.xsl instead.
299 Fix SEGV that could occur for failed connections.
303 Fix bug for command sort that could return no results for active clients
304 (from previous search). This bug was present in 1.6.6-1.6.7.
306 Fix bug in results that could include results that should have been
307 filtered out. This bug was present in 1.6.6-1.6.7.
311 Fix bug introduced in 1.6.6 where a connection re-use could stall
314 Local filtering may now specify a local metadata field, eg.
315 pz:limitmap:somefield[t]=local:otherfield
319 For search, when limit and or filtering is in place and search
320 is identical to previous search, the result set is re-used and the
321 target is not searched.
323 Limits may work perform local filtering as well, by using "local:"
328 Updated bytarget command to contain a suggestions element with misspelled
329 words and suggestions to these. pz2.js has been updated to deliver this
330 onwards as well. Only target that currently delivers this is the solr
331 client in YAZ 4.2.18.
335 New service definition element, xslt, that allows an embedded stylesheet
336 to be defined. This can be referred to from pz:xslt as an alternative to
339 New pz:sortmap:field setting for specifying hints on how to make
340 a target natively sort on a field. This is used for command=show in
341 conjunction with sort.
343 New pz:url setting for specifying the actual URL for a target. When
344 this is used the target ID is not used as URL anymore and the target ID
345 may be almost any string (not including []).
347 command=termlist without name parameter returns all termlists/facets.
348 Previously if name parameter was omitted, only "subject" was returned.
352 Make termlist sorting stable. Terms with same frequency are now sorted by
353 their display name. This makes a pretty display and improves our
354 regression test because qsort is not a stable sort.
356 New sort parameter value 'position'. The 'position' sorts merged records
357 by their original position from the remote target. This is primarily useful
358 for debugging and may be used for targets that already perform some kind
359 of relevance ranking. Note that sort by default is decreasing; so to get
360 records in their original order sort=position:1 must be used.
364 tmarc.xsl: yet another 773$g fix. Was broken in 1.6.1 as well.
366 Facility to change working directory for pazpar2 daemon. Option -wdir
367 sets working directory to dir. This facility is useful if core dumps
368 must be saved. In this case, the current working directory must be
369 writable by the running user, such as "nobody".
373 New configuration element <icu_chain> for <server>/<service> which
374 allows a named ICU rule (chain) to be defined. The names relevance,
375 sort, mergekey and facet are used for those operations. The definition
376 <icu_chain id="sort" locale="en"> .. </icu_chain>
378 <sort> <icu_chain locale="en> ... </icu_chain> </sort>
379 And so on.. for relevance, mergekey and facet as well. The latter
380 style is deprecated. The facet terms are normalized by the facet
381 rule by default. This may be changed on a metadata field basis by
382 defining the new attribute 'facetrule' for the metadata element.
384 <icu_chain id="myrule" locale="en"> ... </icu_chain>
385 <metadata name="author" termlist="yes" facetrule="myrule"/>
387 Preserve rorder for merged metadata. Fixes issue as reported by Sven
388 Porst: http://lists.indexdata.dk/pipermail/yazlist/2011-July/003230.html
390 tmarc.xsl: set journal-subpart to 773$ only.
394 Modify the behavior for the limit parameter (first defined in 1.5.7).
395 Mapping of limit searches are now defined by the new configuration item
396 pz:limitmap. Fix a dead-lock problem with the limit parameter.
398 Extend tmarc.xsl to extract 773$g data (OpenURL).
402 ICU default maps remove backquote (`).
404 Command 'search' takes limit parameter (optional). The limit parameter
405 allows a search to be limited one or more facets and the corresponding
406 values. This is for server side filtering.
408 Configure tweak: Use -lm for log(3) if needed
412 Fix a problem with skiparticle sortkey that could be completely
413 ignored (and reduced to "").
415 Fix dependency problem in pazpar2 RPM package (did not require
416 libyaz4 as it should).
420 Fix memory leak that occurred for command=termlist&name=xtargets .
422 Pazpar2 may save HTTP requests. Enabled by option -R.
426 Experimental support for DTIC DADS target. New dads-pz2.xsl.
428 Support for query_syntax (overrides the default for SRU | Z39.50)
430 Support for extraArgs (ZOOM "extraArgs" option) for targets
432 New commands: status-server and status-session
436 Fix for threaded runs: Client now have a copy of the database URL,
437 which can used after the database has been release from the client.
438 This makes the logging in the connection idle timeout of the client nicer (no NOURL) and should be thread-safe.
440 tmarc.xsl: Add journal-title-abbrev and full text.
442 cf.xsl: new fields: isbn, issn, journaltitle, volume, issue
444 Fix for cmd=record before search.
446 Session Logging clean up.
448 Fix wrong termlist factor when maxrecs is different from 100.
452 Fix missing pz:termlist_term_factor in settings.c messed up pz:preferred.
453 Term factor is default enabled but can be diseabled by
454 pz:termlist_term_factor=0
458 Add scaling of facet count. Currently always enabled, needs fixing.
459 Allow user-defined info for target suffix. This has no meaning in
460 Pazpar2 except to distinguish targets from each other. The suffix
461 data begins with #. For example z3950.indexdata.com/gils#Mydata
463 Added exact-match recordfilter; format name=value
467 SOLR support. Pazpar2 may operate as web service client for SOLR.
471 Fix for show command and block=1 (dead lock). Bug was introduced in
476 New RPM packages: pazpar2, pazpar2-js, pazpar2-doc. These have been
477 tested on CentOS 5.5 only.
481 Fix problem with result sets being removed from a client session
482 if the connection for it was resused by another session. Bug #3489.
484 New iphone UI for Pazpar2 (www/iphone).
488 Fixes for threaded operation.
490 New stylesheets for TurboMARC: tmarc.xsl and opac_turbomarc.xsl.
492 New example services in etc/services in source. In the Debian packages
493 these are located in /etc/pazpar2/services-available
495 Threaded mode operational on Windows. Requires Windows 7 or Windows
498 Default value of setting pz:max_connections is 0 which means that there
499 is no limit on number of connections.
503 Pazpar2 may operate in threaded mode. Enabled by element threads in
504 the configuration. See pazpar2_conf for details.
506 New setting setting: pz:max_connections. Setting pz:max_connections is
507 a limit of number of sockets to a host. When this limit is reached,
508 Pazpar2 will wait up to 5 seconds for a connection to becomes available.
509 The client will be marked Client_Error when it can not be searched
510 (other clients in a session may work). If pz:max_connections is not set
511 for a target, a value of 30 will be used. Note: the pz:max_connections
512 will only work in threaded mode.
514 pz2.js: JSON support for show.
516 Debian package: Enable default service, default.xml, before starting
517 Pazpar2 only if there is no service already in /etc/pazpar2/services-enabled.
521 Debian version depends on on libyaz4. Note that Pazpar2 will still
522 compile from source with YAZ 3.
524 Split services into separate files. The example configuration file
525 pazpar2.cfg.dist now includes a default service default.xml (part of
526 etc). And default.xml includes settings/edu.xml. The default.xml file,
527 not to be confused with settings/defaults.xml, is a template for jsdemo
528 and other services. The Debian package installs /etc/pazpar2/server.xml
529 which is now the main pazpar2 configuration (used to be called pazpar2.cfg).
530 server.xml includes services from /etc/pazpar2/services-enabled/*.xml .
531 The default.xml (from etc) is installed in /etc/pazpar2/services-available
532 and a symlink to it is created from services-enabled. The default.xml
533 service is unnamed and, thus, will be used by jsdemo and test1.
535 New setting pz:negotiation_charset. Patch from Andrei V. Toutoukine. The
536 new setting pz:negotiation_charset specifies character set for Z39.50 Init.
540 Support for additional fields in cf.xsl and pazpar2.conf.dist:
541 publisher, available, due, location (=locallocation), callno
542 (=callnumber), thumburl and score.
544 Describe pz:xslt and the auto setting.
546 Move mergekey definition away from the normalization stylesheets and
547 define a mergekey common for all target types in pazpar2.cfg.
549 Code update: Use the Odr_int type for hit counts. This is part of
550 YAZ 3.0.47 and later and so configure checks for that.
554 Metadata attribute 'skiparticle' also works for ICU based
555 normalization. (was only working for the non-ICU/ASCII before).
557 Command bytarget with argument settings=1 will show settings per
558 target.. This is to be able to verify correct settings and be able to
559 test that they are correct. The database settings array size is now
560 also stored.. Problems with database settings array is that if not
561 careful it will be too small (smaller than dictionary per-service
564 Make record list sorting stable by comparing mergekey for records if
565 relevance/title or other sorting criteria all match. This is merely to
566 ensure that our regressions tests works (reproducible output).
568 Relevance calculation changes: use a different denominator (length) for
569 per-field relevance scoring.. Instead of length of all ranked fields we
570 now use length of individual fields (as if they were individual "free"
571 text fields). This will ensure that documents with a long field with no
572 match (say description) will not "hurt" a title match.
574 Diagnostic member was not set on connection error. Fixed
578 Command search takes two optional parameters, startecs and maxrecs,
579 that specifies the start offset (0, 1, ...) and maximum number of records
580 to fetch for each target.
582 XSLTs + MARC maps are cached within a session so we don't re-parse
583 them over and over again. Even for a session with a single search
584 there's much to be gained because many targets use the same
587 The metadata attribute 'mergekey' now takes one of three values 'no',
588 'required', 'optional' . And the resulting mergekey from metadata
589 is now ordered in the same way as metadata in the service definition.
590 Older Pazpar2 version use the order in which metadata appeared in a
593 The search argument 'filter' now offers a new operator ~ which does a
594 substring match. The = operator works as before: string match for
595 anything but pz:id, or target match for pz:id.
597 New setting pz:recordfilter. The value of this setting takes the
598 form name[~value]. This setting makes Pazpar2 ignore all retrieved
599 records that do not have the metadata element name with value substring
602 Pazpar2 allows YAZ log level to be set (option -v).
606 For WS responses Pazpar2 creates XML header. Exception: raw record.
608 Setting XML files are now stored in etc/settings instead of etc. This
609 reflects the layout with the Debian package layout.
611 Settings may be posted for command=settings. The POSTed settings must
612 have root element 'settings' like regular setting files. In order to be
613 recognized, the POST request must use Content-Type=text/xml.
615 A service may be posted for command=init. This service will be used
616 during the session. The service may have its own target settings,
617 ICU config, timeout, etc. In order to be recognized, the POST request
618 must use Content-Type=text/xml.
620 Timeout values may be given per-service. That's element 'timeout'
621 which takes three attribute values (a subset may be given): 'session',
622 'z3950_operation', 'z3950_session'. Option -T is no longer supported
623 - used to specify session timeout.
625 Option -t tests the Pazpar2 configuration and returns exit code
626 (0=success, non-zero=failure). In previous version of Pazpar2, -t
627 specified local settings.
629 In version 1.2.0 the configuration file - after include processing -
630 was dumped to stdout. Now, the configuration is only dumped to the
631 yaz log file if option -d is given.
635 Configuration may now have multiple server areas. This means that a
636 Pazpar2 instance may listen on multiple ports. Virtual hosting is not
637 yet supported - on a server basis. Configuration may also have multiple
638 services .. That is repeating service elements inside a server. Each
639 has an attribute 'id' which serves as service ID. This ID in turn may
640 be used in a Pazpar2 session, by specifying parameter service=ID for
641 command init. There can be at most one unnamed service inside a server
642 which can be referred to by not specifying an service ID for command
643 init (backwards compatible). In order to partition multiple servers and
644 services a new include directive has been added. This takes an attribute
645 'src' which specifies one or more sub-files. For example to include
646 service files, one might use:
647 <server >.. <include src=/"etc/pazpar2/conf.d/*.xml"/> .. </server>.
648 It is the intention that that completely makes the settings directive
651 Fix problem where the record command would wait forever if there were
652 no targets to wait for (activeclients == 0).
656 One result set is created per session (last search) rather than for
657 each connection which happen to be shared (bug #3009).
659 marc21 stylesheets changed for efficiency.
663 Session timeout may be specified on the command-line as option -T.
665 Pazpar2 may now be operated in a no-merged mode for records.. All records
666 will be considered unique. This mode is enabled if no mergekey is
667 generated by the normalization stylesheet (pz:xslt).
669 Pazpar2 caches original records from each target and the 'record' command
670 with offset returns the original record if 'syntax' and 'esn' are NOT
671 specified. This speeds up retrieval of original records but also means
672 that Pazpar2 uses more memory. The cached records will be freed when the
673 session terminates or a new search is executed.
675 Pazpar2 no longer uses its own ICU wrapper. Instead the ICU wrapper
676 library part of YAZ is used.
678 Added SRU client support.
680 Automatically computes pz:nativesyntax if not provided. Works for XML and
683 --- 1.0.13 2008/11/24
685 Command bytarget returns name of target (if defined).
687 --- 1.0.12 2008/11/04
689 Fixed bug #2021.. location now holds all brief elements.
691 --- 1.0.11 2008/10/15
693 Fixed check for application/x-www-form-urlencoded parameters.
695 --- 1.0.10 2008/10/14
697 Fixes for IE in pz2.js.
699 Fixed bug #2021: non-merged, brief meta data NOT included for command=show.
703 Changed the JS library pz2.js to use POST for long URL (+ params).
705 Added installation instructions for Windows. Note: NT services is
706 NOT available until we make a new release of YAZ.
708 Preserve order of repeated metadata fields (they were reversed before).
710 More MARC21 information extracted for metadata.
714 Fixed bug #1162: HTML entities are not escaped properly.
716 Native Windows port of Pazpar2. Makefile for Visual Studio provided.
720 Marc21 stylesheet updated to reflect multiple full text fields
724 Fixed bug in pz2.js WRT DOMElement attributes on IE.
726 Fixed bug 2100: Database wildcards not working
730 Added support for retrieval of records in binary.
732 Fixed bug 1794: Pazpar2 does not return valid XML.
734 Deal with ICU not returning sortkey (resulted in SEGV before).
738 JavaScript library pzw2.js throws error if WS response (from Pazpar2 or
739 other) is malformed (non-wellformed XML or missing Pazpar2 OK status).
741 Improved diagnostics when Pazpar2 HTTP decoding fails.
743 Pazpar2 requests may be POSTed as using Content-Type
744 application/x-www-form-urlencoded.
746 Pazpar2 honors LF in HTTP headers.
748 Handle targets that handle negative hit counts (should not happen, but it
753 ICU is used for tokenization and normalization of the following: mergekey,
754 sorting, relevance terms.
756 Debian package now enables ICU tokenization and normalization by default.
760 Exposed user setting values (i.e. non-pz: names) to the record systems in two
761 ways: Either as parameters to the normalization stylesheets (which would allow the
762 programmer to postprocess or use the values in any way) or after the normalization
763 step, in which case values are made part of the normalized record (and available for
764 sorting, termlists, display, or other interface-related use.
766 Implemented sorting by year.
768 Option -d dumps records to the current log file instead of stderr.
770 Fixes for compilation on cygwin.
772 Z39.50 client code uses pz:elements. pz:elements was recognized in
773 earlier Pazpar2 versions but it was not used for anything.
775 icu_chain_test is using fgets instead of getline - fixes compilation
778 Loosen the CCL query parsing so that Pazpar2 only returns error if _all_
779 query conversions fail (rather than _any_). This means targets that do
780 not support some fields are ignored in a search.
784 Improved handling of socket timeout for Z39.50 connections.
786 Misc documentation updates and spell fixes.
788 Debian package pazpar2 creates log rotate entry.
790 Debian package pazpar2-apache2 reloads Apache2.
792 jsdemo included in distribution. It illustrates the use of the js/pz2.js
797 First public release.