3 Use poll rather than select for main event loop to overcome limit of
4 1024 file descriptors PAZ-947
6 Override setting with same name (do not append) PAZ-945
10 Separate package: pazpar2-xsl PAZ-932
14 Update OPAC stylesheets for availabilityDate PAZ-943
16 Fix too funny startrecs description
18 Fix broken ~ match if filter contains = PAZ-941
22 Add pz:redis option for ZOOM caching using redis. This is an alternative
23 to memcached. Requires YAZ 5.2.0 to work.
27 Re-ingest native facets PAZ-934
29 Fix medium override for solr-pz2.xsl.
33 Fix URL with leading http:// not working PAZ-933
35 Build packages for Ubuntu Trusty Tahr 14.04 LTS
37 cf.xsl: handle medium override AND md field
41 sortmap relevance always uses increasing=1. PAZ-930
43 solr-pz2.xsl: ensure medium is also applied if Solr record do not
46 Fix leak in getaddrinfo usage for HTTP listener. Not a big deal because
47 this code is only executed once.
49 Fix typos is sortmap documentation.
51 Doc: fix misplaced variablelist tag.
55 Doc: update WRT ICU which is configured for YAZ; not Pazpar2.
56 It's been like that since version 1.1.1 from August 2009.
58 Add support for result-set caching via memcached. See description of
59 pz:memcached. Require that Pazpar2 is using YAZ 5.0.12 or later.
61 Add support for a <metadata> container tag. Patfh from Sven Porst.
63 Add support for XInclude in main configuarion file. Patch from Sven Porst.
65 Add client_{lock,unlock} before call to non_block_events in
66 connection_continue. Problem is that if non_block_events fire records,
67 then we will not unlock client at all. And as a result, a dead-lock
72 Avoid removing slash and other characters for generic metadata that
73 looks like a URL (contains ://). PAZ-915
75 pz2.js: Only use XDR when doing CORS. Favor XHR in all other circumstances.
77 Cluster merge fixes. PAZ-901
79 Set client state to "working" when waiting for DNS resolver. PAZ-907
81 Log when session terminates. PAZ-905
83 Fix LSB/HS conformance for /etc/init.d/pazpar2 PAZ-904
84 Debian: add support for /etc/init.d/pazpar2 status
88 Fix 'Record Missing' for command=show PAZ-903
90 Preserve order of records within cluster PAZ-902
92 testing: use yaz-ztest -V if possible and use YAZ in sibling directory
95 Allow clustered records to be ingested during retrieval. PAZ-900
97 Fix void function error which cannot return a value.
101 SRU pz:authentication="a/b" may end up as x-username=a%2Fb PAZ-899
103 Upgrade to debhelper version 7 PAZ-898
105 Package with libyaz5 PAZ-897
107 Better error message for CCL parse errors PAZ-887
109 --- 1.6.35 2013/09/23
111 New target setting: pz:authentication_mode. PAZ-896
113 pazpar2 PRM: pazpar2 runs as user nobody. PAZ-893
115 Strip #-suffix for ZOOM URLs. PAZ-892
117 --- 1.6.34 2013/08/30
119 Fix issue with hanging show/bytarget. Could happen if new search was
120 fired with filter before show from previous show completed.
122 Add 'date' handling for solr-pz2.xsl.
124 --- 1.6.33 2013/08/13
126 pz:authentication may carry user group password. If pz:authentication
127 has at least one blank in it, that forces Pazpar2 to use idPass Z39.50
128 authentication. Two forms are allowed
131 If no blanks are present, open authentication is in use (as before).
133 Fix {prev,next}recid elements that are returned by record
134 command. These were incorrect in versions 1.6.23 thru 1.6.32.
136 --- 1.6.32 2013/06/14
138 Experimental support for snippets. If argument snippets=1 is given
139 for command record or show, the text will include <match>-tags for
140 those area that matches.
142 Fix memory leak WRT client structures (incorrect inc ref count).
144 Log when a HTTP response is serialized and the time elapsed.
146 New command, service, which returns current service XML in use for
149 --- 1.6.31 2013/05/24
151 Local limit for fields of type "generic" (ie text fields) are
152 now normalized by mergekey rule before comparison takes place.
153 Before, no normalization took place and comparsion was, thus, exact.
155 New facility: dynamic rank , which allows ranking to be changed
156 for an existing result set. The rank can be set for search or
157 show. This overrides the rank for metadata elements (which fields
160 New facility:dynamic mergekey , which allows mergekey to be changed
161 for an existing result set. The mergekey can be set for search or
164 HTTP server: host=@ listens on IPV6 and IPV4 if possible.
165 Also, allow ports to be given as names (not just integers).
166 Fix @-notation on systems that don't support IPV6 sockets.
168 --- 1.6.30 2013/04/26
170 Add MasterKey Connect configuration. Refer to section "non-standard
171 databases" for more information.
173 Allow timeformat for log to be specified with option -m (as Metaproxy
176 New Debian package pazpar2-dbg.
178 Fix NULL ptr reference of se->relevance. If a new search is initiated
179 and a CCL query fails to parse, Pazpar2 could crash.
181 Fix problem with host/port mangling in Pazpar2 HTTP server. Problem
182 existed in 1.6.29 only.
184 --- 1.6.29 2013/04/05
186 IPV6 updates. Allow IPv6 addresses for database hosts and IPv6 address
187 for HTTP server. By default the HTTP server uses IPv4 only, but that can be
188 changed by setting "host" attribute for the "listen" element.
190 Change semantics of pz:extendrecs. Allow for repeated fetches .
191 pz:extendrecs is now the number of extra records to fetch (was total
194 --- 1.6.28 2013/03/21
196 Fix hang or memory violation if show occurred before a search. (not that
197 it makes much sense to perform a show before a search).
199 --- 1.6.27 2013/03/08
201 pz2.js: Element_parseChildNodes concatenates all Text/CDATA nodes, instead
204 --- 1.6.26 2013/03/08
206 New pz:metadata attribute, empty="empty-value" for Pazpar2's
207 internal representation. With this attribute, Pazpar2 treates an empty
208 pz:metadata type as having the value for "empty" - if empty.
210 New setting, pz:extendrecs, which triggers extended fetch of records
211 for a database beyond pz:maxrecs for a show command.
213 Fix warning that was falsely issued for "missing limitmap".
215 Log message for Pazpart start/stop changed. Now using same style as
216 Metaproxy, ie Pazpar2 start SHA1 / Pazpar2 stop .
218 --- 1.6.25 2013/02/07
220 Fix hang of 2nd command=show with esn/syntax given.
222 --- 1.6.24 2013/01/18
224 New merge attribute type: 'first', which takes all metadata fields
225 from first target that returns the particular field.
227 --- 1.6.23 2013/01/02
229 Extend info command with hostname and YAZ SHA1
230 Indent results for both command stat and info.
232 Allow limit on merged content. The new configuration metadata
233 element, limitcluster, configures that a metadata element (name) be used
234 as limit name for search. Applies to the whole service (ie all targets),
235 unlike pz:limitmap which is configured per-target (database).
237 New feature: limitmap local:* matches against all metadata fields.
239 Allow repeated list in limitmap spec . Separated by comma. For
240 example: value="local:title,rpn:@attr 1=4".
242 New element <message> in bytarget response. Holds diagnostic message
243 of code (say 'Unsupported Use Attribute' for Bib-1 114).
245 Improved logging for record ingestion failures.
247 Avoid using struct icu_chain in non-YAZ_HAVE_ICU mode. In the rare case,
248 when YAZ is compiled without ICU support.
250 --- 1.6.22 2012/10/11
252 Requires YAZ-4.2.40 to support native solr support.
254 Fix and improve logic handling whether or not to re-do search on sort
255 order changes. A sort order with change in ascending/descending only
256 whould not trigger a new search, which is required for targets with
257 native sorting capabilities. Each client is now checked if instructions
258 (sortmap) exist for native sorting and only client that does requires
259 it is researched. Other clients is just re-ingesting the records,
260 they already have. The resultset is now cleared if any researching
263 Connection sharing between session has broken since version 1.6.8 with
264 introduction of logic that would minimize searching if pazpar2 could
265 detect this based on same query and limits and partly sort order.
266 This could lead to segementations violations.
268 Added a chapter in the manaul about relevance ranking.
270 --- 1.6.21 2012/09/24
272 Rank tweak: follow=number will increase mult by number if two terms
273 occur next to each other; number-1 if they are one term apart , .. 0
274 if they are number a part (all in order). Default is 0 (following
275 terms has no effect).
277 Rank tweak: lead=k will divide mult by 1 + log2(1+k*l) where k is
278 value given by lead and l is length from beginning of field where
279 term occurs (l=0 for first term, l=1 for second term, ..). Default
282 Rank tweak: length=strategy. length="linear" if mult is to be divided
283 by length (existing, default behavior), length="log" if mult is to be
284 divided by log2(1+length), length="none" if mult is not to be affected
287 --- 1.6.20 2012/09/21
289 Rank algorithm details may be printed as part of show response in
290 element <relevance_info>.. This is only printed if <rank debug="yes"/>
293 Record as returned by show/record command have a minimal indentation
294 which makes things human-readable.
296 New configuration of default sorting criteria (sort-default) in
297 service definition. If no criteria is defined it will be as before
300 Search command now supports sort parameter just as the show command.
301 If no parameter is give, it will use the service sort-default value.
303 --- 1.6.19 2012/09/18
305 Rank algorithm skips strings that gets normalized to empty string.
306 For example, & and ! could map to the empty string. The weight for
307 those terms is now 0 (as if they were not part of the query).
309 Rank algorithm does not use CCL from limitmap; only from the query
310 parameter (user query).
314 --- 1.6.18 2012/09/17
316 Rank algorithm configurable by 'rank' element inside service. So far
317 only, attribute 'cluster' is recognized. If cluster="yes", multiple
318 records inside a cluster boosts higher than single records. This
319 is default behavior and existing behavior. cluster="no" takes the
320 average score of each record in a cluster.
322 --- 1.6.17 2012/09/05
324 Fix bad re-use of connections (connections with changing proxy should not
327 --- 1.6.16 2012/08/22
329 Fix a bug introduce in 1.6.15 around the position sorting. It resetted the
330 resultset and sorting when the sort order is position. However this will be done on
331 every client poll, which will make pazpar2 continuing reset and fetching.
332 It should only be done on FIRST request where the sort order change.
334 Fix an issue on suggestion option: Also disable suggestions on empty string.
336 Clean up in turbo marc stylesheet.
338 Remove the hardcoded size of termlists.
340 --- 1.6.15 2012/06/27
342 New facility: ccldirective may be given in service definition. Allows
343 CCL parsing to be customized a bit, such as defining names of operators
346 New facility: raw record by checksum, rather than offset. The record
347 command optionally takes checksum which identifies certain record from
350 New facility: per field ranking. Rank may be given as M [F N] where
351 M is default rank and N is rank for CCL terms from field F.
353 --- 1.6.14 2012/06/04
355 Fix for IE7/8 in pz.js
357 Applied patch from Giannis Kosmas on keepAlive, which also adds keepAlive to init response.
359 Lower log level some places.
361 Remove some invalid test results.
363 --- 1.6.13 2012/05/23
365 Introducing a version=2 parameter for show, termlist and bytarget commands.
366 This enables pazpar2 to return approximation on hit and count count when
367 doing record filtering using the limit parameter on search and a
368 limitmap with a value of "local:"
370 Setting pz:xslt may embed local XSLT as an alternative to referring
372 Value is not CDATA but XML nodes embedded, so escaping is not necessary
373 but a root element *must* be present. For example:
374 <settings target="target="z3950.indexdata.com/marc">
383 Metadata field rank may given by XML internal document (pz:xslt
384 result). If rank is not given, the rank from service description is
387 Metadata field can now configured a default limitmap and facetmap.
388 Setting limitmap to "local:" would work for all kind of targets, but would
389 prob. not be the optimal solution. But at least better than the default behavior
390 of pazpar2 where no filtering is done.
392 A service definition can now also contains <set/> that defines service-wide
393 settings. These will override server-wide sets and will be overridded by
396 New setting, pz:present_chunk, that specifies number of records to fetch
397 at a time. Zero will disable chunkation; will fetch max_records at once.
399 --- 1.6.12 2012/03/14
401 Revert the format change in termlist response, that could break
402 some clients / UIs since they were expecting an (empty) element
403 if no facet values was found.
405 --- 1.6.11 2012/03/07
407 Revert the behavior of returning errors when unable to block
408 on termlist, bytarget and search, when unable to block due to
409 other block. The client will now receive a regular response,
410 but it will be logged in the server. A parameter (report) is
411 added to change behavior to return error response or WARNING
412 status message. Consider this "API" as private, as it is mostly
413 untested and could be changed in future releases.
415 Fix spell error in pz2.js fix in 1.6.10.
417 New Marc2TurboMarc.xsl (contribution from Sven Porst).
418 Can solve the missing marc21.xsl updates in some cases.
420 tmarc.xsl: Simplify the 6xx to subject-long and fix 1-based
421 substring (contribtion from Sven Porst)
423 marc21.xsl: fix 1-based substring call
425 tmarc.xsl and marc21.xsl: use 856$a as last option for electronic-text.
427 Add test_termlist_block to test suite
429 --- 1.6.10 2012/02/23
431 Fix SEGV for invalid PQFs and SRU/SOLR targets
432 Also refactor a bit the code that converts from PQF to SRU/SOLR queries.
434 Fix pz2.js: "null object" due to change in in bytarget result XML.
436 Fixes in tmarc.xsl: Subject-long shorten for extra commas only.
437 Added this normalization to the other subject-long fields (d6xx),
438 where it was missing.
440 Fixes in marc21.xsl: Updated with most of the new tmarc.xsl.
441 Still differences around medium and holdings. marc21.xsl is not
442 longer active used by Index Data, and should be considered unsupported.
443 Use tmarc.xsl instead.
447 Fix SEGV that could occur for failed connections.
451 Fix bug for command sort that could return no results for active clients
452 (from previous search). This bug was present in 1.6.6-1.6.7.
454 Fix bug in results that could include results that should have been
455 filtered out. This bug was present in 1.6.6-1.6.7.
459 Fix bug introduced in 1.6.6 where a connection re-use could stall
462 Local filtering may now specify a local metadata field, eg.
463 pz:limitmap:somefield[t]=local:otherfield
467 For search, when limit and or filtering is in place and search
468 is identical to previous search, the result set is re-used and the
469 target is not searched.
471 Limits may work perform local filtering as well, by using "local:"
476 Updated bytarget command to contain a suggestions element with misspelled
477 words and suggestions to these. pz2.js has been updated to deliver this
478 onwards as well. Only target that currently delivers this is the solr
479 client in YAZ 4.2.18.
483 New service definition element, xslt, that allows an embedded stylesheet
484 to be defined. This can be referred to from pz:xslt as an alternative to
487 New pz:sortmap:field setting for specifying hints on how to make
488 a target natively sort on a field. This is used for command=show in
489 conjunction with sort.
491 New pz:url setting for specifying the actual URL for a target. When
492 this is used the target ID is not used as URL anymore and the target ID
493 may be almost any string (not including []).
495 command=termlist without name parameter returns all termlists/facets.
496 Previously if name parameter was omitted, only "subject" was returned.
500 Make termlist sorting stable. Terms with same frequency are now sorted by
501 their display name. This makes a pretty display and improves our
502 regression test because qsort is not a stable sort.
504 New sort parameter value 'position'. The 'position' sorts merged records
505 by their original position from the remote target. This is primarily useful
506 for debugging and may be used for targets that already perform some kind
507 of relevance ranking. Note that sort by default is decreasing; so to get
508 records in their original order sort=position:1 must be used.
512 tmarc.xsl: yet another 773$g fix. Was broken in 1.6.1 as well.
514 Facility to change working directory for pazpar2 daemon. Option -wdir
515 sets working directory to dir. This facility is useful if core dumps
516 must be saved. In this case, the current working directory must be
517 writable by the running user, such as "nobody".
521 New configuration element <icu_chain> for <server>/<service> which
522 allows a named ICU rule (chain) to be defined. The names relevance,
523 sort, mergekey and facet are used for those operations. The definition
524 <icu_chain id="sort" locale="en"> .. </icu_chain>
526 <sort> <icu_chain locale="en> ... </icu_chain> </sort>
527 And so on.. for relevance, mergekey and facet as well. The latter
528 style is deprecated. The facet terms are normalized by the facet
529 rule by default. This may be changed on a metadata field basis by
530 defining the new attribute 'facetrule' for the metadata element.
532 <icu_chain id="myrule" locale="en"> ... </icu_chain>
533 <metadata name="author" termlist="yes" facetrule="myrule"/>
535 Preserve rorder for merged metadata. Fixes issue as reported by Sven
536 Porst: http://lists.indexdata.dk/pipermail/yazlist/2011-July/003230.html
538 tmarc.xsl: set journal-subpart to 773$ only.
542 Modify the behavior for the limit parameter (first defined in 1.5.7).
543 Mapping of limit searches are now defined by the new configuration item
544 pz:limitmap. Fix a dead-lock problem with the limit parameter.
546 Extend tmarc.xsl to extract 773$g data (OpenURL).
550 ICU default maps remove backquote (`).
552 Command 'search' takes limit parameter (optional). The limit parameter
553 allows a search to be limited one or more facets and the corresponding
554 values. This is for server side filtering.
556 Configure tweak: Use -lm for log(3) if needed
560 Fix a problem with skiparticle sortkey that could be completely
561 ignored (and reduced to "").
563 Fix dependency problem in pazpar2 RPM package (did not require
564 libyaz4 as it should).
568 Fix memory leak that occurred for command=termlist&name=xtargets .
570 Pazpar2 may save HTTP requests. Enabled by option -R.
574 Experimental support for DTIC DADS target. New dads-pz2.xsl.
576 Support for query_syntax (overrides the default for SRU | Z39.50)
578 Support for extraArgs (ZOOM "extraArgs" option) for targets
580 New commands: status-server and status-session
584 Fix for threaded runs: Client now have a copy of the database URL,
585 which can used after the database has been release from the client.
586 This makes the logging in the connection idle timeout of the client nicer (no NOURL) and should be thread-safe.
588 tmarc.xsl: Add journal-title-abbrev and full text.
590 cf.xsl: new fields: isbn, issn, journaltitle, volume, issue
592 Fix for cmd=record before search.
594 Session Logging clean up.
596 Fix wrong termlist factor when maxrecs is different from 100.
600 Fix missing pz:termlist_term_factor in settings.c messed up pz:preferred.
601 Term factor is default enabled but can be diseabled by
602 pz:termlist_term_factor=0
606 Add scaling of facet count. Currently always enabled, needs fixing.
607 Allow user-defined info for target suffix. This has no meaning in
608 Pazpar2 except to distinguish targets from each other. The suffix
609 data begins with #. For example z3950.indexdata.com/gils#Mydata
611 Added exact-match recordfilter; format name=value
615 SOLR support. Pazpar2 may operate as web service client for SOLR.
619 Fix for show command and block=1 (dead lock). Bug was introduced in
624 New RPM packages: pazpar2, pazpar2-js, pazpar2-doc. These have been
625 tested on CentOS 5.5 only.
629 Fix problem with result sets being removed from a client session
630 if the connection for it was resused by another session. Bug #3489.
632 New iphone UI for Pazpar2 (www/iphone).
636 Fixes for threaded operation.
638 New stylesheets for TurboMARC: tmarc.xsl and opac_turbomarc.xsl.
640 New example services in etc/services in source. In the Debian packages
641 these are located in /etc/pazpar2/services-available
643 Threaded mode operational on Windows. Requires Windows 7 or Windows
646 Default value of setting pz:max_connections is 0 which means that there
647 is no limit on number of connections.
651 Pazpar2 may operate in threaded mode. Enabled by element threads in
652 the configuration. See pazpar2_conf for details.
654 New setting setting: pz:max_connections. Setting pz:max_connections is
655 a limit of number of sockets to a host. When this limit is reached,
656 Pazpar2 will wait up to 5 seconds for a connection to becomes available.
657 The client will be marked Client_Error when it can not be searched
658 (other clients in a session may work). If pz:max_connections is not set
659 for a target, a value of 30 will be used. Note: the pz:max_connections
660 will only work in threaded mode.
662 pz2.js: JSON support for show.
664 Debian package: Enable default service, default.xml, before starting
665 Pazpar2 only if there is no service already in /etc/pazpar2/services-enabled.
669 Debian version depends on on libyaz4. Note that Pazpar2 will still
670 compile from source with YAZ 3.
672 Split services into separate files. The example configuration file
673 pazpar2.cfg.dist now includes a default service default.xml (part of
674 etc). And default.xml includes settings/edu.xml. The default.xml file,
675 not to be confused with settings/defaults.xml, is a template for jsdemo
676 and other services. The Debian package installs /etc/pazpar2/server.xml
677 which is now the main pazpar2 configuration (used to be called pazpar2.cfg).
678 server.xml includes services from /etc/pazpar2/services-enabled/*.xml .
679 The default.xml (from etc) is installed in /etc/pazpar2/services-available
680 and a symlink to it is created from services-enabled. The default.xml
681 service is unnamed and, thus, will be used by jsdemo and test1.
683 New setting pz:negotiation_charset. Patch from Andrei V. Toutoukine. The
684 new setting pz:negotiation_charset specifies character set for Z39.50 Init.
688 Support for additional fields in cf.xsl and pazpar2.conf.dist:
689 publisher, available, due, location (=locallocation), callno
690 (=callnumber), thumburl and score.
692 Describe pz:xslt and the auto setting.
694 Move mergekey definition away from the normalization stylesheets and
695 define a mergekey common for all target types in pazpar2.cfg.
697 Code update: Use the Odr_int type for hit counts. This is part of
698 YAZ 3.0.47 and later and so configure checks for that.
702 Metadata attribute 'skiparticle' also works for ICU based
703 normalization. (was only working for the non-ICU/ASCII before).
705 Command bytarget with argument settings=1 will show settings per
706 target.. This is to be able to verify correct settings and be able to
707 test that they are correct. The database settings array size is now
708 also stored.. Problems with database settings array is that if not
709 careful it will be too small (smaller than dictionary per-service
712 Make record list sorting stable by comparing mergekey for records if
713 relevance/title or other sorting criteria all match. This is merely to
714 ensure that our regressions tests works (reproducible output).
716 Relevance calculation changes: use a different denominator (length) for
717 per-field relevance scoring.. Instead of length of all ranked fields we
718 now use length of individual fields (as if they were individual "free"
719 text fields). This will ensure that documents with a long field with no
720 match (say description) will not "hurt" a title match.
722 Diagnostic member was not set on connection error. Fixed
726 Command search takes two optional parameters, startecs and maxrecs,
727 that specifies the start offset (0, 1, ...) and maximum number of records
728 to fetch for each target.
730 XSLTs + MARC maps are cached within a session so we don't re-parse
731 them over and over again. Even for a session with a single search
732 there's much to be gained because many targets use the same
735 The metadata attribute 'mergekey' now takes one of three values 'no',
736 'required', 'optional' . And the resulting mergekey from metadata
737 is now ordered in the same way as metadata in the service definition.
738 Older Pazpar2 version use the order in which metadata appeared in a
741 The search argument 'filter' now offers a new operator ~ which does a
742 substring match. The = operator works as before: string match for
743 anything but pz:id, or target match for pz:id.
745 New setting pz:recordfilter. The value of this setting takes the
746 form name[~value]. This setting makes Pazpar2 ignore all retrieved
747 records that do not have the metadata element name with value substring
750 Pazpar2 allows YAZ log level to be set (option -v).
754 For WS responses Pazpar2 creates XML header. Exception: raw record.
756 Setting XML files are now stored in etc/settings instead of etc. This
757 reflects the layout with the Debian package layout.
759 Settings may be posted for command=settings. The POSTed settings must
760 have root element 'settings' like regular setting files. In order to be
761 recognized, the POST request must use Content-Type=text/xml.
763 A service may be posted for command=init. This service will be used
764 during the session. The service may have its own target settings,
765 ICU config, timeout, etc. In order to be recognized, the POST request
766 must use Content-Type=text/xml.
768 Timeout values may be given per-service. That's element 'timeout'
769 which takes three attribute values (a subset may be given): 'session',
770 'z3950_operation', 'z3950_session'. Option -T is no longer supported
771 - used to specify session timeout.
773 Option -t tests the Pazpar2 configuration and returns exit code
774 (0=success, non-zero=failure). In previous version of Pazpar2, -t
775 specified local settings.
777 In version 1.2.0 the configuration file - after include processing -
778 was dumped to stdout. Now, the configuration is only dumped to the
779 yaz log file if option -d is given.
783 Configuration may now have multiple server areas. This means that a
784 Pazpar2 instance may listen on multiple ports. Virtual hosting is not
785 yet supported - on a server basis. Configuration may also have multiple
786 services .. That is repeating service elements inside a server. Each
787 has an attribute 'id' which serves as service ID. This ID in turn may
788 be used in a Pazpar2 session, by specifying parameter service=ID for
789 command init. There can be at most one unnamed service inside a server
790 which can be referred to by not specifying an service ID for command
791 init (backwards compatible). In order to partition multiple servers and
792 services a new include directive has been added. This takes an attribute
793 'src' which specifies one or more sub-files. For example to include
794 service files, one might use:
795 <server >.. <include src=/"etc/pazpar2/conf.d/*.xml"/> .. </server>.
796 It is the intention that that completely makes the settings directive
799 Fix problem where the record command would wait forever if there were
800 no targets to wait for (activeclients == 0).
804 One result set is created per session (last search) rather than for
805 each connection which happen to be shared (bug #3009).
807 marc21 stylesheets changed for efficiency.
811 Session timeout may be specified on the command-line as option -T.
813 Pazpar2 may now be operated in a no-merged mode for records.. All records
814 will be considered unique. This mode is enabled if no mergekey is
815 generated by the normalization stylesheet (pz:xslt).
817 Pazpar2 caches original records from each target and the 'record' command
818 with offset returns the original record if 'syntax' and 'esn' are NOT
819 specified. This speeds up retrieval of original records but also means
820 that Pazpar2 uses more memory. The cached records will be freed when the
821 session terminates or a new search is executed.
823 Pazpar2 no longer uses its own ICU wrapper. Instead the ICU wrapper
824 library part of YAZ is used.
826 Added SRU client support.
828 Automatically computes pz:nativesyntax if not provided. Works for XML and
831 --- 1.0.13 2008/11/24
833 Command bytarget returns name of target (if defined).
835 --- 1.0.12 2008/11/04
837 Fixed bug #2021.. location now holds all brief elements.
839 --- 1.0.11 2008/10/15
841 Fixed check for application/x-www-form-urlencoded parameters.
843 --- 1.0.10 2008/10/14
845 Fixes for IE in pz2.js.
847 Fixed bug #2021: non-merged, brief meta data NOT included for command=show.
851 Changed the JS library pz2.js to use POST for long URL (+ params).
853 Added installation instructions for Windows. Note: NT services is
854 NOT available until we make a new release of YAZ.
856 Preserve order of repeated metadata fields (they were reversed before).
858 More MARC21 information extracted for metadata.
862 Fixed bug #1162: HTML entities are not escaped properly.
864 Native Windows port of Pazpar2. Makefile for Visual Studio provided.
868 Marc21 stylesheet updated to reflect multiple full text fields
872 Fixed bug in pz2.js WRT DOMElement attributes on IE.
874 Fixed bug 2100: Database wildcards not working
878 Added support for retrieval of records in binary.
880 Fixed bug 1794: Pazpar2 does not return valid XML.
882 Deal with ICU not returning sortkey (resulted in SEGV before).
886 JavaScript library pzw2.js throws error if WS response (from Pazpar2 or
887 other) is malformed (non-wellformed XML or missing Pazpar2 OK status).
889 Improved diagnostics when Pazpar2 HTTP decoding fails.
891 Pazpar2 requests may be POSTed as using Content-Type
892 application/x-www-form-urlencoded.
894 Pazpar2 honors LF in HTTP headers.
896 Handle targets that handle negative hit counts (should not happen, but it
901 ICU is used for tokenization and normalization of the following: mergekey,
902 sorting, relevance terms.
904 Debian package now enables ICU tokenization and normalization by default.
908 Exposed user setting values (i.e. non-pz: names) to the record systems in two
909 ways: Either as parameters to the normalization stylesheets (which would allow the
910 programmer to postprocess or use the values in any way) or after the normalization
911 step, in which case values are made part of the normalized record (and available for
912 sorting, termlists, display, or other interface-related use.
914 Implemented sorting by year.
916 Option -d dumps records to the current log file instead of stderr.
918 Fixes for compilation on cygwin.
920 Z39.50 client code uses pz:elements. pz:elements was recognized in
921 earlier Pazpar2 versions but it was not used for anything.
923 icu_chain_test is using fgets instead of getline - fixes compilation
926 Loosen the CCL query parsing so that Pazpar2 only returns error if _all_
927 query conversions fail (rather than _any_). This means targets that do
928 not support some fields are ignored in a search.
932 Improved handling of socket timeout for Z39.50 connections.
934 Misc documentation updates and spell fixes.
936 Debian package pazpar2 creates log rotate entry.
938 Debian package pazpar2-apache2 reloads Apache2.
940 jsdemo included in distribution. It illustrates the use of the js/pz2.js
945 First public release.