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