3 Update OPAC stylesheets for availabilityDate PAZ-943
5 Fix too funny startrecs description
7 Fix broken ~ match if filter contains = PAZ-941
11 Add pz:redis option for ZOOM caching using redis. This is an alternative
12 to memcached. Requires YAZ 5.2.0 to work.
16 Re-ingest native facets PAZ-934
18 Fix medium override for solr-pz2.xsl.
22 Fix URL with leading http:// not working PAZ-933
24 Build packages for Ubuntu Trusty Tahr 14.04 LTS
26 cf.xsl: handle medium override AND md field
30 sortmap relevance always uses increasing=1. PAZ-930
32 solr-pz2.xsl: ensure medium is also applied if Solr record do not
35 Fix leak in getaddrinfo usage for HTTP listener. Not a big deal because
36 this code is only executed once.
38 Fix typos is sortmap documentation.
40 Doc: fix misplaced variablelist tag.
44 Doc: update WRT ICU which is configured for YAZ; not Pazpar2.
45 It's been like that since version 1.1.1 from August 2009.
47 Add support for result-set caching via memcached. See description of
48 pz:memcached. Require that Pazpar2 is using YAZ 5.0.12 or later.
50 Add support for a <metadata> container tag. Patfh from Sven Porst.
52 Add support for XInclude in main configuarion file. Patch from Sven Porst.
54 Add client_{lock,unlock} before call to non_block_events in
55 connection_continue. Problem is that if non_block_events fire records,
56 then we will not unlock client at all. And as a result, a dead-lock
61 Avoid removing slash and other characters for generic metadata that
62 looks like a URL (contains ://). PAZ-915
64 pz2.js: Only use XDR when doing CORS. Favor XHR in all other circumstances.
66 Cluster merge fixes. PAZ-901
68 Set client state to "working" when waiting for DNS resolver. PAZ-907
70 Log when session terminates. PAZ-905
72 Fix LSB/HS conformance for /etc/init.d/pazpar2 PAZ-904
73 Debian: add support for /etc/init.d/pazpar2 status
77 Fix 'Record Missing' for command=show PAZ-903
79 Preserve order of records within cluster PAZ-902
81 testing: use yaz-ztest -V if possible and use YAZ in sibling directory
84 Allow clustered records to be ingested during retrieval. PAZ-900
86 Fix void function error which cannot return a value.
90 SRU pz:authentication="a/b" may end up as x-username=a%2Fb PAZ-899
92 Upgrade to debhelper version 7 PAZ-898
94 Package with libyaz5 PAZ-897
96 Better error message for CCL parse errors PAZ-887
100 New target setting: pz:authentication_mode. PAZ-896
102 pazpar2 PRM: pazpar2 runs as user nobody. PAZ-893
104 Strip #-suffix for ZOOM URLs. PAZ-892
106 --- 1.6.34 2013/08/30
108 Fix issue with hanging show/bytarget. Could happen if new search was
109 fired with filter before show from previous show completed.
111 Add 'date' handling for solr-pz2.xsl.
113 --- 1.6.33 2013/08/13
115 pz:authentication may carry user group password. If pz:authentication
116 has at least one blank in it, that forces Pazpar2 to use idPass Z39.50
117 authentication. Two forms are allowed
120 If no blanks are present, open authentication is in use (as before).
122 Fix {prev,next}recid elements that are returned by record
123 command. These were incorrect in versions 1.6.23 thru 1.6.32.
125 --- 1.6.32 2013/06/14
127 Experimental support for snippets. If argument snippets=1 is given
128 for command record or show, the text will include <match>-tags for
129 those area that matches.
131 Fix memory leak WRT client structures (incorrect inc ref count).
133 Log when a HTTP response is serialized and the time elapsed.
135 New command, service, which returns current service XML in use for
138 --- 1.6.31 2013/05/24
140 Local limit for fields of type "generic" (ie text fields) are
141 now normalized by mergekey rule before comparison takes place.
142 Before, no normalization took place and comparsion was, thus, exact.
144 New facility: dynamic rank , which allows ranking to be changed
145 for an existing result set. The rank can be set for search or
146 show. This overrides the rank for metadata elements (which fields
149 New facility:dynamic mergekey , which allows mergekey to be changed
150 for an existing result set. The mergekey can be set for search or
153 HTTP server: host=@ listens on IPV6 and IPV4 if possible.
154 Also, allow ports to be given as names (not just integers).
155 Fix @-notation on systems that don't support IPV6 sockets.
157 --- 1.6.30 2013/04/26
159 Add MasterKey Connect configuration. Refer to section "non-standard
160 databases" for more information.
162 Allow timeformat for log to be specified with option -m (as Metaproxy
165 New Debian package pazpar2-dbg.
167 Fix NULL ptr reference of se->relevance. If a new search is initiated
168 and a CCL query fails to parse, Pazpar2 could crash.
170 Fix problem with host/port mangling in Pazpar2 HTTP server. Problem
171 existed in 1.6.29 only.
173 --- 1.6.29 2013/04/05
175 IPV6 updates. Allow IPv6 addresses for database hosts and IPv6 address
176 for HTTP server. By default the HTTP server uses IPv4 only, but that can be
177 changed by setting "host" attribute for the "listen" element.
179 Change semantics of pz:extendrecs. Allow for repeated fetches .
180 pz:extendrecs is now the number of extra records to fetch (was total
183 --- 1.6.28 2013/03/21
185 Fix hang or memory violation if show occurred before a search. (not that
186 it makes much sense to perform a show before a search).
188 --- 1.6.27 2013/03/08
190 pz2.js: Element_parseChildNodes concatenates all Text/CDATA nodes, instead
193 --- 1.6.26 2013/03/08
195 New pz:metadata attribute, empty="empty-value" for Pazpar2's
196 internal representation. With this attribute, Pazpar2 treates an empty
197 pz:metadata type as having the value for "empty" - if empty.
199 New setting, pz:extendrecs, which triggers extended fetch of records
200 for a database beyond pz:maxrecs for a show command.
202 Fix warning that was falsely issued for "missing limitmap".
204 Log message for Pazpart start/stop changed. Now using same style as
205 Metaproxy, ie Pazpar2 start SHA1 / Pazpar2 stop .
207 --- 1.6.25 2013/02/07
209 Fix hang of 2nd command=show with esn/syntax given.
211 --- 1.6.24 2013/01/18
213 New merge attribute type: 'first', which takes all metadata fields
214 from first target that returns the particular field.
216 --- 1.6.23 2013/01/02
218 Extend info command with hostname and YAZ SHA1
219 Indent results for both command stat and info.
221 Allow limit on merged content. The new configuration metadata
222 element, limitcluster, configures that a metadata element (name) be used
223 as limit name for search. Applies to the whole service (ie all targets),
224 unlike pz:limitmap which is configured per-target (database).
226 New feature: limitmap local:* matches against all metadata fields.
228 Allow repeated list in limitmap spec . Separated by comma. For
229 example: value="local:title,rpn:@attr 1=4".
231 New element <message> in bytarget response. Holds diagnostic message
232 of code (say 'Unsupported Use Attribute' for Bib-1 114).
234 Improved logging for record ingestion failures.
236 Avoid using struct icu_chain in non-YAZ_HAVE_ICU mode. In the rare case,
237 when YAZ is compiled without ICU support.
239 --- 1.6.22 2012/10/11
241 Requires YAZ-4.2.40 to support native solr support.
243 Fix and improve logic handling whether or not to re-do search on sort
244 order changes. A sort order with change in ascending/descending only
245 whould not trigger a new search, which is required for targets with
246 native sorting capabilities. Each client is now checked if instructions
247 (sortmap) exist for native sorting and only client that does requires
248 it is researched. Other clients is just re-ingesting the records,
249 they already have. The resultset is now cleared if any researching
252 Connection sharing between session has broken since version 1.6.8 with
253 introduction of logic that would minimize searching if pazpar2 could
254 detect this based on same query and limits and partly sort order.
255 This could lead to segementations violations.
257 Added a chapter in the manaul about relevance ranking.
259 --- 1.6.21 2012/09/24
261 Rank tweak: follow=number will increase mult by number if two terms
262 occur next to each other; number-1 if they are one term apart , .. 0
263 if they are number a part (all in order). Default is 0 (following
264 terms has no effect).
266 Rank tweak: lead=k will divide mult by 1 + log2(1+k*l) where k is
267 value given by lead and l is length from beginning of field where
268 term occurs (l=0 for first term, l=1 for second term, ..). Default
271 Rank tweak: length=strategy. length="linear" if mult is to be divided
272 by length (existing, default behavior), length="log" if mult is to be
273 divided by log2(1+length), length="none" if mult is not to be affected
276 --- 1.6.20 2012/09/21
278 Rank algorithm details may be printed as part of show response in
279 element <relevance_info>.. This is only printed if <rank debug="yes"/>
282 Record as returned by show/record command have a minimal indentation
283 which makes things human-readable.
285 New configuration of default sorting criteria (sort-default) in
286 service definition. If no criteria is defined it will be as before
289 Search command now supports sort parameter just as the show command.
290 If no parameter is give, it will use the service sort-default value.
292 --- 1.6.19 2012/09/18
294 Rank algorithm skips strings that gets normalized to empty string.
295 For example, & and ! could map to the empty string. The weight for
296 those terms is now 0 (as if they were not part of the query).
298 Rank algorithm does not use CCL from limitmap; only from the query
299 parameter (user query).
303 --- 1.6.18 2012/09/17
305 Rank algorithm configurable by 'rank' element inside service. So far
306 only, attribute 'cluster' is recognized. If cluster="yes", multiple
307 records inside a cluster boosts higher than single records. This
308 is default behavior and existing behavior. cluster="no" takes the
309 average score of each record in a cluster.
311 --- 1.6.17 2012/09/05
313 Fix bad re-use of connections (connections with changing proxy should not
316 --- 1.6.16 2012/08/22
318 Fix a bug introduce in 1.6.15 around the position sorting. It resetted the
319 resultset and sorting when the sort order is position. However this will be done on
320 every client poll, which will make pazpar2 continuing reset and fetching.
321 It should only be done on FIRST request where the sort order change.
323 Fix an issue on suggestion option: Also disable suggestions on empty string.
325 Clean up in turbo marc stylesheet.
327 Remove the hardcoded size of termlists.
329 --- 1.6.15 2012/06/27
331 New facility: ccldirective may be given in service definition. Allows
332 CCL parsing to be customized a bit, such as defining names of operators
335 New facility: raw record by checksum, rather than offset. The record
336 command optionally takes checksum which identifies certain record from
339 New facility: per field ranking. Rank may be given as M [F N] where
340 M is default rank and N is rank for CCL terms from field F.
342 --- 1.6.14 2012/06/04
344 Fix for IE7/8 in pz.js
346 Applied patch from Giannis Kosmas on keepAlive, which also adds keepAlive to init response.
348 Lower log level some places.
350 Remove some invalid test results.
352 --- 1.6.13 2012/05/23
354 Introducing a version=2 parameter for show, termlist and bytarget commands.
355 This enables pazpar2 to return approximation on hit and count count when
356 doing record filtering using the limit parameter on search and a
357 limitmap with a value of "local:"
359 Setting pz:xslt may embed local XSLT as an alternative to referring
361 Value is not CDATA but XML nodes embedded, so escaping is not necessary
362 but a root element *must* be present. For example:
363 <settings target="target="z3950.indexdata.com/marc">
372 Metadata field rank may given by XML internal document (pz:xslt
373 result). If rank is not given, the rank from service description is
376 Metadata field can now configured a default limitmap and facetmap.
377 Setting limitmap to "local:" would work for all kind of targets, but would
378 prob. not be the optimal solution. But at least better than the default behavior
379 of pazpar2 where no filtering is done.
381 A service definition can now also contains <set/> that defines service-wide
382 settings. These will override server-wide sets and will be overridded by
385 New setting, pz:present_chunk, that specifies number of records to fetch
386 at a time. Zero will disable chunkation; will fetch max_records at once.
388 --- 1.6.12 2012/03/14
390 Revert the format change in termlist response, that could break
391 some clients / UIs since they were expecting an (empty) element
392 if no facet values was found.
394 --- 1.6.11 2012/03/07
396 Revert the behavior of returning errors when unable to block
397 on termlist, bytarget and search, when unable to block due to
398 other block. The client will now receive a regular response,
399 but it will be logged in the server. A parameter (report) is
400 added to change behavior to return error response or WARNING
401 status message. Consider this "API" as private, as it is mostly
402 untested and could be changed in future releases.
404 Fix spell error in pz2.js fix in 1.6.10.
406 New Marc2TurboMarc.xsl (contribution from Sven Porst).
407 Can solve the missing marc21.xsl updates in some cases.
409 tmarc.xsl: Simplify the 6xx to subject-long and fix 1-based
410 substring (contribtion from Sven Porst)
412 marc21.xsl: fix 1-based substring call
414 tmarc.xsl and marc21.xsl: use 856$a as last option for electronic-text.
416 Add test_termlist_block to test suite
418 --- 1.6.10 2012/02/23
420 Fix SEGV for invalid PQFs and SRU/SOLR targets
421 Also refactor a bit the code that converts from PQF to SRU/SOLR queries.
423 Fix pz2.js: "null object" due to change in in bytarget result XML.
425 Fixes in tmarc.xsl: Subject-long shorten for extra commas only.
426 Added this normalization to the other subject-long fields (d6xx),
427 where it was missing.
429 Fixes in marc21.xsl: Updated with most of the new tmarc.xsl.
430 Still differences around medium and holdings. marc21.xsl is not
431 longer active used by Index Data, and should be considered unsupported.
432 Use tmarc.xsl instead.
436 Fix SEGV that could occur for failed connections.
440 Fix bug for command sort that could return no results for active clients
441 (from previous search). This bug was present in 1.6.6-1.6.7.
443 Fix bug in results that could include results that should have been
444 filtered out. This bug was present in 1.6.6-1.6.7.
448 Fix bug introduced in 1.6.6 where a connection re-use could stall
451 Local filtering may now specify a local metadata field, eg.
452 pz:limitmap:somefield[t]=local:otherfield
456 For search, when limit and or filtering is in place and search
457 is identical to previous search, the result set is re-used and the
458 target is not searched.
460 Limits may work perform local filtering as well, by using "local:"
465 Updated bytarget command to contain a suggestions element with misspelled
466 words and suggestions to these. pz2.js has been updated to deliver this
467 onwards as well. Only target that currently delivers this is the solr
468 client in YAZ 4.2.18.
472 New service definition element, xslt, that allows an embedded stylesheet
473 to be defined. This can be referred to from pz:xslt as an alternative to
476 New pz:sortmap:field setting for specifying hints on how to make
477 a target natively sort on a field. This is used for command=show in
478 conjunction with sort.
480 New pz:url setting for specifying the actual URL for a target. When
481 this is used the target ID is not used as URL anymore and the target ID
482 may be almost any string (not including []).
484 command=termlist without name parameter returns all termlists/facets.
485 Previously if name parameter was omitted, only "subject" was returned.
489 Make termlist sorting stable. Terms with same frequency are now sorted by
490 their display name. This makes a pretty display and improves our
491 regression test because qsort is not a stable sort.
493 New sort parameter value 'position'. The 'position' sorts merged records
494 by their original position from the remote target. This is primarily useful
495 for debugging and may be used for targets that already perform some kind
496 of relevance ranking. Note that sort by default is decreasing; so to get
497 records in their original order sort=position:1 must be used.
501 tmarc.xsl: yet another 773$g fix. Was broken in 1.6.1 as well.
503 Facility to change working directory for pazpar2 daemon. Option -wdir
504 sets working directory to dir. This facility is useful if core dumps
505 must be saved. In this case, the current working directory must be
506 writable by the running user, such as "nobody".
510 New configuration element <icu_chain> for <server>/<service> which
511 allows a named ICU rule (chain) to be defined. The names relevance,
512 sort, mergekey and facet are used for those operations. The definition
513 <icu_chain id="sort" locale="en"> .. </icu_chain>
515 <sort> <icu_chain locale="en> ... </icu_chain> </sort>
516 And so on.. for relevance, mergekey and facet as well. The latter
517 style is deprecated. The facet terms are normalized by the facet
518 rule by default. This may be changed on a metadata field basis by
519 defining the new attribute 'facetrule' for the metadata element.
521 <icu_chain id="myrule" locale="en"> ... </icu_chain>
522 <metadata name="author" termlist="yes" facetrule="myrule"/>
524 Preserve rorder for merged metadata. Fixes issue as reported by Sven
525 Porst: http://lists.indexdata.dk/pipermail/yazlist/2011-July/003230.html
527 tmarc.xsl: set journal-subpart to 773$ only.
531 Modify the behavior for the limit parameter (first defined in 1.5.7).
532 Mapping of limit searches are now defined by the new configuration item
533 pz:limitmap. Fix a dead-lock problem with the limit parameter.
535 Extend tmarc.xsl to extract 773$g data (OpenURL).
539 ICU default maps remove backquote (`).
541 Command 'search' takes limit parameter (optional). The limit parameter
542 allows a search to be limited one or more facets and the corresponding
543 values. This is for server side filtering.
545 Configure tweak: Use -lm for log(3) if needed
549 Fix a problem with skiparticle sortkey that could be completely
550 ignored (and reduced to "").
552 Fix dependency problem in pazpar2 RPM package (did not require
553 libyaz4 as it should).
557 Fix memory leak that occurred for command=termlist&name=xtargets .
559 Pazpar2 may save HTTP requests. Enabled by option -R.
563 Experimental support for DTIC DADS target. New dads-pz2.xsl.
565 Support for query_syntax (overrides the default for SRU | Z39.50)
567 Support for extraArgs (ZOOM "extraArgs" option) for targets
569 New commands: status-server and status-session
573 Fix for threaded runs: Client now have a copy of the database URL,
574 which can used after the database has been release from the client.
575 This makes the logging in the connection idle timeout of the client nicer (no NOURL) and should be thread-safe.
577 tmarc.xsl: Add journal-title-abbrev and full text.
579 cf.xsl: new fields: isbn, issn, journaltitle, volume, issue
581 Fix for cmd=record before search.
583 Session Logging clean up.
585 Fix wrong termlist factor when maxrecs is different from 100.
589 Fix missing pz:termlist_term_factor in settings.c messed up pz:preferred.
590 Term factor is default enabled but can be diseabled by
591 pz:termlist_term_factor=0
595 Add scaling of facet count. Currently always enabled, needs fixing.
596 Allow user-defined info for target suffix. This has no meaning in
597 Pazpar2 except to distinguish targets from each other. The suffix
598 data begins with #. For example z3950.indexdata.com/gils#Mydata
600 Added exact-match recordfilter; format name=value
604 SOLR support. Pazpar2 may operate as web service client for SOLR.
608 Fix for show command and block=1 (dead lock). Bug was introduced in
613 New RPM packages: pazpar2, pazpar2-js, pazpar2-doc. These have been
614 tested on CentOS 5.5 only.
618 Fix problem with result sets being removed from a client session
619 if the connection for it was resused by another session. Bug #3489.
621 New iphone UI for Pazpar2 (www/iphone).
625 Fixes for threaded operation.
627 New stylesheets for TurboMARC: tmarc.xsl and opac_turbomarc.xsl.
629 New example services in etc/services in source. In the Debian packages
630 these are located in /etc/pazpar2/services-available
632 Threaded mode operational on Windows. Requires Windows 7 or Windows
635 Default value of setting pz:max_connections is 0 which means that there
636 is no limit on number of connections.
640 Pazpar2 may operate in threaded mode. Enabled by element threads in
641 the configuration. See pazpar2_conf for details.
643 New setting setting: pz:max_connections. Setting pz:max_connections is
644 a limit of number of sockets to a host. When this limit is reached,
645 Pazpar2 will wait up to 5 seconds for a connection to becomes available.
646 The client will be marked Client_Error when it can not be searched
647 (other clients in a session may work). If pz:max_connections is not set
648 for a target, a value of 30 will be used. Note: the pz:max_connections
649 will only work in threaded mode.
651 pz2.js: JSON support for show.
653 Debian package: Enable default service, default.xml, before starting
654 Pazpar2 only if there is no service already in /etc/pazpar2/services-enabled.
658 Debian version depends on on libyaz4. Note that Pazpar2 will still
659 compile from source with YAZ 3.
661 Split services into separate files. The example configuration file
662 pazpar2.cfg.dist now includes a default service default.xml (part of
663 etc). And default.xml includes settings/edu.xml. The default.xml file,
664 not to be confused with settings/defaults.xml, is a template for jsdemo
665 and other services. The Debian package installs /etc/pazpar2/server.xml
666 which is now the main pazpar2 configuration (used to be called pazpar2.cfg).
667 server.xml includes services from /etc/pazpar2/services-enabled/*.xml .
668 The default.xml (from etc) is installed in /etc/pazpar2/services-available
669 and a symlink to it is created from services-enabled. The default.xml
670 service is unnamed and, thus, will be used by jsdemo and test1.
672 New setting pz:negotiation_charset. Patch from Andrei V. Toutoukine. The
673 new setting pz:negotiation_charset specifies character set for Z39.50 Init.
677 Support for additional fields in cf.xsl and pazpar2.conf.dist:
678 publisher, available, due, location (=locallocation), callno
679 (=callnumber), thumburl and score.
681 Describe pz:xslt and the auto setting.
683 Move mergekey definition away from the normalization stylesheets and
684 define a mergekey common for all target types in pazpar2.cfg.
686 Code update: Use the Odr_int type for hit counts. This is part of
687 YAZ 3.0.47 and later and so configure checks for that.
691 Metadata attribute 'skiparticle' also works for ICU based
692 normalization. (was only working for the non-ICU/ASCII before).
694 Command bytarget with argument settings=1 will show settings per
695 target.. This is to be able to verify correct settings and be able to
696 test that they are correct. The database settings array size is now
697 also stored.. Problems with database settings array is that if not
698 careful it will be too small (smaller than dictionary per-service
701 Make record list sorting stable by comparing mergekey for records if
702 relevance/title or other sorting criteria all match. This is merely to
703 ensure that our regressions tests works (reproducible output).
705 Relevance calculation changes: use a different denominator (length) for
706 per-field relevance scoring.. Instead of length of all ranked fields we
707 now use length of individual fields (as if they were individual "free"
708 text fields). This will ensure that documents with a long field with no
709 match (say description) will not "hurt" a title match.
711 Diagnostic member was not set on connection error. Fixed
715 Command search takes two optional parameters, startecs and maxrecs,
716 that specifies the start offset (0, 1, ...) and maximum number of records
717 to fetch for each target.
719 XSLTs + MARC maps are cached within a session so we don't re-parse
720 them over and over again. Even for a session with a single search
721 there's much to be gained because many targets use the same
724 The metadata attribute 'mergekey' now takes one of three values 'no',
725 'required', 'optional' . And the resulting mergekey from metadata
726 is now ordered in the same way as metadata in the service definition.
727 Older Pazpar2 version use the order in which metadata appeared in a
730 The search argument 'filter' now offers a new operator ~ which does a
731 substring match. The = operator works as before: string match for
732 anything but pz:id, or target match for pz:id.
734 New setting pz:recordfilter. The value of this setting takes the
735 form name[~value]. This setting makes Pazpar2 ignore all retrieved
736 records that do not have the metadata element name with value substring
739 Pazpar2 allows YAZ log level to be set (option -v).
743 For WS responses Pazpar2 creates XML header. Exception: raw record.
745 Setting XML files are now stored in etc/settings instead of etc. This
746 reflects the layout with the Debian package layout.
748 Settings may be posted for command=settings. The POSTed settings must
749 have root element 'settings' like regular setting files. In order to be
750 recognized, the POST request must use Content-Type=text/xml.
752 A service may be posted for command=init. This service will be used
753 during the session. The service may have its own target settings,
754 ICU config, timeout, etc. In order to be recognized, the POST request
755 must use Content-Type=text/xml.
757 Timeout values may be given per-service. That's element 'timeout'
758 which takes three attribute values (a subset may be given): 'session',
759 'z3950_operation', 'z3950_session'. Option -T is no longer supported
760 - used to specify session timeout.
762 Option -t tests the Pazpar2 configuration and returns exit code
763 (0=success, non-zero=failure). In previous version of Pazpar2, -t
764 specified local settings.
766 In version 1.2.0 the configuration file - after include processing -
767 was dumped to stdout. Now, the configuration is only dumped to the
768 yaz log file if option -d is given.
772 Configuration may now have multiple server areas. This means that a
773 Pazpar2 instance may listen on multiple ports. Virtual hosting is not
774 yet supported - on a server basis. Configuration may also have multiple
775 services .. That is repeating service elements inside a server. Each
776 has an attribute 'id' which serves as service ID. This ID in turn may
777 be used in a Pazpar2 session, by specifying parameter service=ID for
778 command init. There can be at most one unnamed service inside a server
779 which can be referred to by not specifying an service ID for command
780 init (backwards compatible). In order to partition multiple servers and
781 services a new include directive has been added. This takes an attribute
782 'src' which specifies one or more sub-files. For example to include
783 service files, one might use:
784 <server >.. <include src=/"etc/pazpar2/conf.d/*.xml"/> .. </server>.
785 It is the intention that that completely makes the settings directive
788 Fix problem where the record command would wait forever if there were
789 no targets to wait for (activeclients == 0).
793 One result set is created per session (last search) rather than for
794 each connection which happen to be shared (bug #3009).
796 marc21 stylesheets changed for efficiency.
800 Session timeout may be specified on the command-line as option -T.
802 Pazpar2 may now be operated in a no-merged mode for records.. All records
803 will be considered unique. This mode is enabled if no mergekey is
804 generated by the normalization stylesheet (pz:xslt).
806 Pazpar2 caches original records from each target and the 'record' command
807 with offset returns the original record if 'syntax' and 'esn' are NOT
808 specified. This speeds up retrieval of original records but also means
809 that Pazpar2 uses more memory. The cached records will be freed when the
810 session terminates or a new search is executed.
812 Pazpar2 no longer uses its own ICU wrapper. Instead the ICU wrapper
813 library part of YAZ is used.
815 Added SRU client support.
817 Automatically computes pz:nativesyntax if not provided. Works for XML and
820 --- 1.0.13 2008/11/24
822 Command bytarget returns name of target (if defined).
824 --- 1.0.12 2008/11/04
826 Fixed bug #2021.. location now holds all brief elements.
828 --- 1.0.11 2008/10/15
830 Fixed check for application/x-www-form-urlencoded parameters.
832 --- 1.0.10 2008/10/14
834 Fixes for IE in pz2.js.
836 Fixed bug #2021: non-merged, brief meta data NOT included for command=show.
840 Changed the JS library pz2.js to use POST for long URL (+ params).
842 Added installation instructions for Windows. Note: NT services is
843 NOT available until we make a new release of YAZ.
845 Preserve order of repeated metadata fields (they were reversed before).
847 More MARC21 information extracted for metadata.
851 Fixed bug #1162: HTML entities are not escaped properly.
853 Native Windows port of Pazpar2. Makefile for Visual Studio provided.
857 Marc21 stylesheet updated to reflect multiple full text fields
861 Fixed bug in pz2.js WRT DOMElement attributes on IE.
863 Fixed bug 2100: Database wildcards not working
867 Added support for retrieval of records in binary.
869 Fixed bug 1794: Pazpar2 does not return valid XML.
871 Deal with ICU not returning sortkey (resulted in SEGV before).
875 JavaScript library pzw2.js throws error if WS response (from Pazpar2 or
876 other) is malformed (non-wellformed XML or missing Pazpar2 OK status).
878 Improved diagnostics when Pazpar2 HTTP decoding fails.
880 Pazpar2 requests may be POSTed as using Content-Type
881 application/x-www-form-urlencoded.
883 Pazpar2 honors LF in HTTP headers.
885 Handle targets that handle negative hit counts (should not happen, but it
890 ICU is used for tokenization and normalization of the following: mergekey,
891 sorting, relevance terms.
893 Debian package now enables ICU tokenization and normalization by default.
897 Exposed user setting values (i.e. non-pz: names) to the record systems in two
898 ways: Either as parameters to the normalization stylesheets (which would allow the
899 programmer to postprocess or use the values in any way) or after the normalization
900 step, in which case values are made part of the normalized record (and available for
901 sorting, termlists, display, or other interface-related use.
903 Implemented sorting by year.
905 Option -d dumps records to the current log file instead of stderr.
907 Fixes for compilation on cygwin.
909 Z39.50 client code uses pz:elements. pz:elements was recognized in
910 earlier Pazpar2 versions but it was not used for anything.
912 icu_chain_test is using fgets instead of getline - fixes compilation
915 Loosen the CCL query parsing so that Pazpar2 only returns error if _all_
916 query conversions fail (rather than _any_). This means targets that do
917 not support some fields are ignored in a search.
921 Improved handling of socket timeout for Z39.50 connections.
923 Misc documentation updates and spell fixes.
925 Debian package pazpar2 creates log rotate entry.
927 Debian package pazpar2-apache2 reloads Apache2.
929 jsdemo included in distribution. It illustrates the use of the js/pz2.js
934 First public release.