3 Add Ubuntu utopic 14.04 and Ubuntu saucy 13.10 to the list of packages
6 Remove from js/pz2.js the code that translates just two diagnostic
7 codes (1 and 2) into human-readable messages. This is no longer
8 necessary at all, as PazPar2 has been returning the message as well as
9 the code in its responses since December 2012. Fixes PAZ-978.
11 primo xsl produces citation rather than journal-subpart PAZ-972
12 (fix in 1.8.1 was incorrect)
14 Fix missing .url files PAZ-977
15 Add missing .url+.cfg and add proper check for it.
19 Turbomarc needs number check for date 903 map PAZ-973
21 primo-pz2.xsl creates citation rather than journal-subpart PAZ-972
23 pz2.js: on successful search, issue a "show" command only if a show
24 callback function has been installed. Fixes part of PAZ-975
28 New command=stop which stops further search&retrieval for active
31 CF/primo XSL generates {volume,issue,pages}-number that are defined
32 in default Pazpar2 service definition. PAZ-968 PAZ-970
36 Various fixes for threaded operation PAZ-960 thru PAZ-966
38 Dump main configuration file during start of Pazpar2 PAZ-957
42 Log ingest failures and record failures:
44 Clean up logging PAZ-942
45 Use session lead in more places. Log hits/records/filtered for each
46 target when fetching is complete. Log hit count when a search
47 (response) is received. Remove some less useful log messages.
49 Fix warning about about missing (internal) stylesheet PAZ-956
51 Report number of filtered records in bytarget PAZ-954
53 Cache XML documents as they appear after normalization. The key
54 for the cache is database+record offset. Cache is removed if query
55 is modified for search. This speeds up re-establishing a result set
56 for databases where new query is same previous query.
60 poll: add assert for number of FDs; abort on poll failure
64 Fix hang for 2nd use of target with unresolved DNS PAZ-949
68 Use poll rather than select for main event loop to overcome limit of
69 1024 file descriptors PAZ-947
71 Override setting with same name (do not append) PAZ-945
75 Separate package: pazpar2-xsl PAZ-932
79 Update OPAC stylesheets for availabilityDate PAZ-943
81 Fix too funny startrecs description
83 Fix broken ~ match if filter contains = PAZ-941
87 Add pz:redis option for ZOOM caching using redis. This is an alternative
88 to memcached. Requires YAZ 5.2.0 to work.
92 Re-ingest native facets PAZ-934
94 Fix medium override for solr-pz2.xsl.
98 Fix URL with leading http:// not working PAZ-933
100 Build packages for Ubuntu Trusty Tahr 14.04 LTS
102 cf.xsl: handle medium override AND md field
104 --- 1.6.40 2014/04/10
106 sortmap relevance always uses increasing=1. PAZ-930
108 solr-pz2.xsl: ensure medium is also applied if Solr record do not
111 Fix leak in getaddrinfo usage for HTTP listener. Not a big deal because
112 this code is only executed once.
114 Fix typos is sortmap documentation.
116 Doc: fix misplaced variablelist tag.
118 --- 1.6.39 2014/02/19
120 Doc: update WRT ICU which is configured for YAZ; not Pazpar2.
121 It's been like that since version 1.1.1 from August 2009.
123 Add support for result-set caching via memcached. See description of
124 pz:memcached. Require that Pazpar2 is using YAZ 5.0.12 or later.
126 Add support for a <metadata> container tag. Patfh from Sven Porst.
128 Add support for XInclude in main configuarion file. Patch from Sven Porst.
130 Add client_{lock,unlock} before call to non_block_events in
131 connection_continue. Problem is that if non_block_events fire records,
132 then we will not unlock client at all. And as a result, a dead-lock
135 --- 1.6.38 2014/01/07
137 Avoid removing slash and other characters for generic metadata that
138 looks like a URL (contains ://). PAZ-915
140 pz2.js: Only use XDR when doing CORS. Favor XHR in all other circumstances.
142 Cluster merge fixes. PAZ-901
144 Set client state to "working" when waiting for DNS resolver. PAZ-907
146 Log when session terminates. PAZ-905
148 Fix LSB/HS conformance for /etc/init.d/pazpar2 PAZ-904
149 Debian: add support for /etc/init.d/pazpar2 status
151 --- 1.6.37 2013/11/18
153 Fix 'Record Missing' for command=show PAZ-903
155 Preserve order of records within cluster PAZ-902
157 testing: use yaz-ztest -V if possible and use YAZ in sibling directory
160 Allow clustered records to be ingested during retrieval. PAZ-900
162 Fix void function error which cannot return a value.
164 --- 1.6.36 2013/11/11
166 SRU pz:authentication="a/b" may end up as x-username=a%2Fb PAZ-899
168 Upgrade to debhelper version 7 PAZ-898
170 Package with libyaz5 PAZ-897
172 Better error message for CCL parse errors PAZ-887
174 --- 1.6.35 2013/09/23
176 New target setting: pz:authentication_mode. PAZ-896
178 pazpar2 PRM: pazpar2 runs as user nobody. PAZ-893
180 Strip #-suffix for ZOOM URLs. PAZ-892
182 --- 1.6.34 2013/08/30
184 Fix issue with hanging show/bytarget. Could happen if new search was
185 fired with filter before show from previous show completed.
187 Add 'date' handling for solr-pz2.xsl.
189 --- 1.6.33 2013/08/13
191 pz:authentication may carry user group password. If pz:authentication
192 has at least one blank in it, that forces Pazpar2 to use idPass Z39.50
193 authentication. Two forms are allowed
196 If no blanks are present, open authentication is in use (as before).
198 Fix {prev,next}recid elements that are returned by record
199 command. These were incorrect in versions 1.6.23 thru 1.6.32.
201 --- 1.6.32 2013/06/14
203 Experimental support for snippets. If argument snippets=1 is given
204 for command record or show, the text will include <match>-tags for
205 those area that matches.
207 Fix memory leak WRT client structures (incorrect inc ref count).
209 Log when a HTTP response is serialized and the time elapsed.
211 New command, service, which returns current service XML in use for
214 --- 1.6.31 2013/05/24
216 Local limit for fields of type "generic" (ie text fields) are
217 now normalized by mergekey rule before comparison takes place.
218 Before, no normalization took place and comparsion was, thus, exact.
220 New facility: dynamic rank , which allows ranking to be changed
221 for an existing result set. The rank can be set for search or
222 show. This overrides the rank for metadata elements (which fields
225 New facility:dynamic mergekey , which allows mergekey to be changed
226 for an existing result set. The mergekey can be set for search or
229 HTTP server: host=@ listens on IPV6 and IPV4 if possible.
230 Also, allow ports to be given as names (not just integers).
231 Fix @-notation on systems that don't support IPV6 sockets.
233 --- 1.6.30 2013/04/26
235 Add MasterKey Connect configuration. Refer to section "non-standard
236 databases" for more information.
238 Allow timeformat for log to be specified with option -m (as Metaproxy
241 New Debian package pazpar2-dbg.
243 Fix NULL ptr reference of se->relevance. If a new search is initiated
244 and a CCL query fails to parse, Pazpar2 could crash.
246 Fix problem with host/port mangling in Pazpar2 HTTP server. Problem
247 existed in 1.6.29 only.
249 --- 1.6.29 2013/04/05
251 IPV6 updates. Allow IPv6 addresses for database hosts and IPv6 address
252 for HTTP server. By default the HTTP server uses IPv4 only, but that can be
253 changed by setting "host" attribute for the "listen" element.
255 Change semantics of pz:extendrecs. Allow for repeated fetches .
256 pz:extendrecs is now the number of extra records to fetch (was total
259 --- 1.6.28 2013/03/21
261 Fix hang or memory violation if show occurred before a search. (not that
262 it makes much sense to perform a show before a search).
264 --- 1.6.27 2013/03/08
266 pz2.js: Element_parseChildNodes concatenates all Text/CDATA nodes, instead
269 --- 1.6.26 2013/03/08
271 New pz:metadata attribute, empty="empty-value" for Pazpar2's
272 internal representation. With this attribute, Pazpar2 treates an empty
273 pz:metadata type as having the value for "empty" - if empty.
275 New setting, pz:extendrecs, which triggers extended fetch of records
276 for a database beyond pz:maxrecs for a show command.
278 Fix warning that was falsely issued for "missing limitmap".
280 Log message for Pazpart start/stop changed. Now using same style as
281 Metaproxy, ie Pazpar2 start SHA1 / Pazpar2 stop .
283 --- 1.6.25 2013/02/07
285 Fix hang of 2nd command=show with esn/syntax given.
287 --- 1.6.24 2013/01/18
289 New merge attribute type: 'first', which takes all metadata fields
290 from first target that returns the particular field.
292 --- 1.6.23 2013/01/02
294 Extend info command with hostname and YAZ SHA1
295 Indent results for both command stat and info.
297 Allow limit on merged content. The new configuration metadata
298 element, limitcluster, configures that a metadata element (name) be used
299 as limit name for search. Applies to the whole service (ie all targets),
300 unlike pz:limitmap which is configured per-target (database).
302 New feature: limitmap local:* matches against all metadata fields.
304 Allow repeated list in limitmap spec . Separated by comma. For
305 example: value="local:title,rpn:@attr 1=4".
307 New element <message> in bytarget response. Holds diagnostic message
308 of code (say 'Unsupported Use Attribute' for Bib-1 114).
310 Improved logging for record ingestion failures.
312 Avoid using struct icu_chain in non-YAZ_HAVE_ICU mode. In the rare case,
313 when YAZ is compiled without ICU support.
315 --- 1.6.22 2012/10/11
317 Requires YAZ-4.2.40 to support native solr support.
319 Fix and improve logic handling whether or not to re-do search on sort
320 order changes. A sort order with change in ascending/descending only
321 whould not trigger a new search, which is required for targets with
322 native sorting capabilities. Each client is now checked if instructions
323 (sortmap) exist for native sorting and only client that does requires
324 it is researched. Other clients is just re-ingesting the records,
325 they already have. The resultset is now cleared if any researching
328 Connection sharing between session has broken since version 1.6.8 with
329 introduction of logic that would minimize searching if pazpar2 could
330 detect this based on same query and limits and partly sort order.
331 This could lead to segementations violations.
333 Added a chapter in the manaul about relevance ranking.
335 --- 1.6.21 2012/09/24
337 Rank tweak: follow=number will increase mult by number if two terms
338 occur next to each other; number-1 if they are one term apart , .. 0
339 if they are number a part (all in order). Default is 0 (following
340 terms has no effect).
342 Rank tweak: lead=k will divide mult by 1 + log2(1+k*l) where k is
343 value given by lead and l is length from beginning of field where
344 term occurs (l=0 for first term, l=1 for second term, ..). Default
347 Rank tweak: length=strategy. length="linear" if mult is to be divided
348 by length (existing, default behavior), length="log" if mult is to be
349 divided by log2(1+length), length="none" if mult is not to be affected
352 --- 1.6.20 2012/09/21
354 Rank algorithm details may be printed as part of show response in
355 element <relevance_info>.. This is only printed if <rank debug="yes"/>
358 Record as returned by show/record command have a minimal indentation
359 which makes things human-readable.
361 New configuration of default sorting criteria (sort-default) in
362 service definition. If no criteria is defined it will be as before
365 Search command now supports sort parameter just as the show command.
366 If no parameter is give, it will use the service sort-default value.
368 --- 1.6.19 2012/09/18
370 Rank algorithm skips strings that gets normalized to empty string.
371 For example, & and ! could map to the empty string. The weight for
372 those terms is now 0 (as if they were not part of the query).
374 Rank algorithm does not use CCL from limitmap; only from the query
375 parameter (user query).
379 --- 1.6.18 2012/09/17
381 Rank algorithm configurable by 'rank' element inside service. So far
382 only, attribute 'cluster' is recognized. If cluster="yes", multiple
383 records inside a cluster boosts higher than single records. This
384 is default behavior and existing behavior. cluster="no" takes the
385 average score of each record in a cluster.
387 --- 1.6.17 2012/09/05
389 Fix bad re-use of connections (connections with changing proxy should not
392 --- 1.6.16 2012/08/22
394 Fix a bug introduce in 1.6.15 around the position sorting. It resetted the
395 resultset and sorting when the sort order is position. However this will be done on
396 every client poll, which will make pazpar2 continuing reset and fetching.
397 It should only be done on FIRST request where the sort order change.
399 Fix an issue on suggestion option: Also disable suggestions on empty string.
401 Clean up in turbo marc stylesheet.
403 Remove the hardcoded size of termlists.
405 --- 1.6.15 2012/06/27
407 New facility: ccldirective may be given in service definition. Allows
408 CCL parsing to be customized a bit, such as defining names of operators
411 New facility: raw record by checksum, rather than offset. The record
412 command optionally takes checksum which identifies certain record from
415 New facility: per field ranking. Rank may be given as M [F N] where
416 M is default rank and N is rank for CCL terms from field F.
418 --- 1.6.14 2012/06/04
420 Fix for IE7/8 in pz.js
422 Applied patch from Giannis Kosmas on keepAlive, which also adds keepAlive to init response.
424 Lower log level some places.
426 Remove some invalid test results.
428 --- 1.6.13 2012/05/23
430 Introducing a version=2 parameter for show, termlist and bytarget commands.
431 This enables pazpar2 to return approximation on hit and count count when
432 doing record filtering using the limit parameter on search and a
433 limitmap with a value of "local:"
435 Setting pz:xslt may embed local XSLT as an alternative to referring
437 Value is not CDATA but XML nodes embedded, so escaping is not necessary
438 but a root element *must* be present. For example:
439 <settings target="target="z3950.indexdata.com/marc">
448 Metadata field rank may given by XML internal document (pz:xslt
449 result). If rank is not given, the rank from service description is
452 Metadata field can now configured a default limitmap and facetmap.
453 Setting limitmap to "local:" would work for all kind of targets, but would
454 prob. not be the optimal solution. But at least better than the default behavior
455 of pazpar2 where no filtering is done.
457 A service definition can now also contains <set/> that defines service-wide
458 settings. These will override server-wide sets and will be overridded by
461 New setting, pz:present_chunk, that specifies number of records to fetch
462 at a time. Zero will disable chunkation; will fetch max_records at once.
464 --- 1.6.12 2012/03/14
466 Revert the format change in termlist response, that could break
467 some clients / UIs since they were expecting an (empty) element
468 if no facet values was found.
470 --- 1.6.11 2012/03/07
472 Revert the behavior of returning errors when unable to block
473 on termlist, bytarget and search, when unable to block due to
474 other block. The client will now receive a regular response,
475 but it will be logged in the server. A parameter (report) is
476 added to change behavior to return error response or WARNING
477 status message. Consider this "API" as private, as it is mostly
478 untested and could be changed in future releases.
480 Fix spell error in pz2.js fix in 1.6.10.
482 New Marc2TurboMarc.xsl (contribution from Sven Porst).
483 Can solve the missing marc21.xsl updates in some cases.
485 tmarc.xsl: Simplify the 6xx to subject-long and fix 1-based
486 substring (contribtion from Sven Porst)
488 marc21.xsl: fix 1-based substring call
490 tmarc.xsl and marc21.xsl: use 856$a as last option for electronic-text.
492 Add test_termlist_block to test suite
494 --- 1.6.10 2012/02/23
496 Fix SEGV for invalid PQFs and SRU/SOLR targets
497 Also refactor a bit the code that converts from PQF to SRU/SOLR queries.
499 Fix pz2.js: "null object" due to change in in bytarget result XML.
501 Fixes in tmarc.xsl: Subject-long shorten for extra commas only.
502 Added this normalization to the other subject-long fields (d6xx),
503 where it was missing.
505 Fixes in marc21.xsl: Updated with most of the new tmarc.xsl.
506 Still differences around medium and holdings. marc21.xsl is not
507 longer active used by Index Data, and should be considered unsupported.
508 Use tmarc.xsl instead.
512 Fix SEGV that could occur for failed connections.
516 Fix bug for command sort that could return no results for active clients
517 (from previous search). This bug was present in 1.6.6-1.6.7.
519 Fix bug in results that could include results that should have been
520 filtered out. This bug was present in 1.6.6-1.6.7.
524 Fix bug introduced in 1.6.6 where a connection re-use could stall
527 Local filtering may now specify a local metadata field, eg.
528 pz:limitmap:somefield[t]=local:otherfield
532 For search, when limit and or filtering is in place and search
533 is identical to previous search, the result set is re-used and the
534 target is not searched.
536 Limits may work perform local filtering as well, by using "local:"
541 Updated bytarget command to contain a suggestions element with misspelled
542 words and suggestions to these. pz2.js has been updated to deliver this
543 onwards as well. Only target that currently delivers this is the solr
544 client in YAZ 4.2.18.
548 New service definition element, xslt, that allows an embedded stylesheet
549 to be defined. This can be referred to from pz:xslt as an alternative to
552 New pz:sortmap:field setting for specifying hints on how to make
553 a target natively sort on a field. This is used for command=show in
554 conjunction with sort.
556 New pz:url setting for specifying the actual URL for a target. When
557 this is used the target ID is not used as URL anymore and the target ID
558 may be almost any string (not including []).
560 command=termlist without name parameter returns all termlists/facets.
561 Previously if name parameter was omitted, only "subject" was returned.
565 Make termlist sorting stable. Terms with same frequency are now sorted by
566 their display name. This makes a pretty display and improves our
567 regression test because qsort is not a stable sort.
569 New sort parameter value 'position'. The 'position' sorts merged records
570 by their original position from the remote target. This is primarily useful
571 for debugging and may be used for targets that already perform some kind
572 of relevance ranking. Note that sort by default is decreasing; so to get
573 records in their original order sort=position:1 must be used.
577 tmarc.xsl: yet another 773$g fix. Was broken in 1.6.1 as well.
579 Facility to change working directory for pazpar2 daemon. Option -wdir
580 sets working directory to dir. This facility is useful if core dumps
581 must be saved. In this case, the current working directory must be
582 writable by the running user, such as "nobody".
586 New configuration element <icu_chain> for <server>/<service> which
587 allows a named ICU rule (chain) to be defined. The names relevance,
588 sort, mergekey and facet are used for those operations. The definition
589 <icu_chain id="sort" locale="en"> .. </icu_chain>
591 <sort> <icu_chain locale="en> ... </icu_chain> </sort>
592 And so on.. for relevance, mergekey and facet as well. The latter
593 style is deprecated. The facet terms are normalized by the facet
594 rule by default. This may be changed on a metadata field basis by
595 defining the new attribute 'facetrule' for the metadata element.
597 <icu_chain id="myrule" locale="en"> ... </icu_chain>
598 <metadata name="author" termlist="yes" facetrule="myrule"/>
600 Preserve rorder for merged metadata. Fixes issue as reported by Sven
601 Porst: http://lists.indexdata.dk/pipermail/yazlist/2011-July/003230.html
603 tmarc.xsl: set journal-subpart to 773$ only.
607 Modify the behavior for the limit parameter (first defined in 1.5.7).
608 Mapping of limit searches are now defined by the new configuration item
609 pz:limitmap. Fix a dead-lock problem with the limit parameter.
611 Extend tmarc.xsl to extract 773$g data (OpenURL).
615 ICU default maps remove backquote (`).
617 Command 'search' takes limit parameter (optional). The limit parameter
618 allows a search to be limited one or more facets and the corresponding
619 values. This is for server side filtering.
621 Configure tweak: Use -lm for log(3) if needed
625 Fix a problem with skiparticle sortkey that could be completely
626 ignored (and reduced to "").
628 Fix dependency problem in pazpar2 RPM package (did not require
629 libyaz4 as it should).
633 Fix memory leak that occurred for command=termlist&name=xtargets .
635 Pazpar2 may save HTTP requests. Enabled by option -R.
639 Experimental support for DTIC DADS target. New dads-pz2.xsl.
641 Support for query_syntax (overrides the default for SRU | Z39.50)
643 Support for extraArgs (ZOOM "extraArgs" option) for targets
645 New commands: status-server and status-session
649 Fix for threaded runs: Client now have a copy of the database URL,
650 which can used after the database has been release from the client.
651 This makes the logging in the connection idle timeout of the client nicer (no NOURL) and should be thread-safe.
653 tmarc.xsl: Add journal-title-abbrev and full text.
655 cf.xsl: new fields: isbn, issn, journaltitle, volume, issue
657 Fix for cmd=record before search.
659 Session Logging clean up.
661 Fix wrong termlist factor when maxrecs is different from 100.
665 Fix missing pz:termlist_term_factor in settings.c messed up pz:preferred.
666 Term factor is default enabled but can be diseabled by
667 pz:termlist_term_factor=0
671 Add scaling of facet count. Currently always enabled, needs fixing.
672 Allow user-defined info for target suffix. This has no meaning in
673 Pazpar2 except to distinguish targets from each other. The suffix
674 data begins with #. For example z3950.indexdata.com/gils#Mydata
676 Added exact-match recordfilter; format name=value
680 SOLR support. Pazpar2 may operate as web service client for SOLR.
684 Fix for show command and block=1 (dead lock). Bug was introduced in
689 New RPM packages: pazpar2, pazpar2-js, pazpar2-doc. These have been
690 tested on CentOS 5.5 only.
694 Fix problem with result sets being removed from a client session
695 if the connection for it was resused by another session. Bug #3489.
697 New iphone UI for Pazpar2 (www/iphone).
701 Fixes for threaded operation.
703 New stylesheets for TurboMARC: tmarc.xsl and opac_turbomarc.xsl.
705 New example services in etc/services in source. In the Debian packages
706 these are located in /etc/pazpar2/services-available
708 Threaded mode operational on Windows. Requires Windows 7 or Windows
711 Default value of setting pz:max_connections is 0 which means that there
712 is no limit on number of connections.
716 Pazpar2 may operate in threaded mode. Enabled by element threads in
717 the configuration. See pazpar2_conf for details.
719 New setting setting: pz:max_connections. Setting pz:max_connections is
720 a limit of number of sockets to a host. When this limit is reached,
721 Pazpar2 will wait up to 5 seconds for a connection to becomes available.
722 The client will be marked Client_Error when it can not be searched
723 (other clients in a session may work). If pz:max_connections is not set
724 for a target, a value of 30 will be used. Note: the pz:max_connections
725 will only work in threaded mode.
727 pz2.js: JSON support for show.
729 Debian package: Enable default service, default.xml, before starting
730 Pazpar2 only if there is no service already in /etc/pazpar2/services-enabled.
734 Debian version depends on on libyaz4. Note that Pazpar2 will still
735 compile from source with YAZ 3.
737 Split services into separate files. The example configuration file
738 pazpar2.cfg.dist now includes a default service default.xml (part of
739 etc). And default.xml includes settings/edu.xml. The default.xml file,
740 not to be confused with settings/defaults.xml, is a template for jsdemo
741 and other services. The Debian package installs /etc/pazpar2/server.xml
742 which is now the main pazpar2 configuration (used to be called pazpar2.cfg).
743 server.xml includes services from /etc/pazpar2/services-enabled/*.xml .
744 The default.xml (from etc) is installed in /etc/pazpar2/services-available
745 and a symlink to it is created from services-enabled. The default.xml
746 service is unnamed and, thus, will be used by jsdemo and test1.
748 New setting pz:negotiation_charset. Patch from Andrei V. Toutoukine. The
749 new setting pz:negotiation_charset specifies character set for Z39.50 Init.
753 Support for additional fields in cf.xsl and pazpar2.conf.dist:
754 publisher, available, due, location (=locallocation), callno
755 (=callnumber), thumburl and score.
757 Describe pz:xslt and the auto setting.
759 Move mergekey definition away from the normalization stylesheets and
760 define a mergekey common for all target types in pazpar2.cfg.
762 Code update: Use the Odr_int type for hit counts. This is part of
763 YAZ 3.0.47 and later and so configure checks for that.
767 Metadata attribute 'skiparticle' also works for ICU based
768 normalization. (was only working for the non-ICU/ASCII before).
770 Command bytarget with argument settings=1 will show settings per
771 target.. This is to be able to verify correct settings and be able to
772 test that they are correct. The database settings array size is now
773 also stored.. Problems with database settings array is that if not
774 careful it will be too small (smaller than dictionary per-service
777 Make record list sorting stable by comparing mergekey for records if
778 relevance/title or other sorting criteria all match. This is merely to
779 ensure that our regressions tests works (reproducible output).
781 Relevance calculation changes: use a different denominator (length) for
782 per-field relevance scoring.. Instead of length of all ranked fields we
783 now use length of individual fields (as if they were individual "free"
784 text fields). This will ensure that documents with a long field with no
785 match (say description) will not "hurt" a title match.
787 Diagnostic member was not set on connection error. Fixed
791 Command search takes two optional parameters, startecs and maxrecs,
792 that specifies the start offset (0, 1, ...) and maximum number of records
793 to fetch for each target.
795 XSLTs + MARC maps are cached within a session so we don't re-parse
796 them over and over again. Even for a session with a single search
797 there's much to be gained because many targets use the same
800 The metadata attribute 'mergekey' now takes one of three values 'no',
801 'required', 'optional' . And the resulting mergekey from metadata
802 is now ordered in the same way as metadata in the service definition.
803 Older Pazpar2 version use the order in which metadata appeared in a
806 The search argument 'filter' now offers a new operator ~ which does a
807 substring match. The = operator works as before: string match for
808 anything but pz:id, or target match for pz:id.
810 New setting pz:recordfilter. The value of this setting takes the
811 form name[~value]. This setting makes Pazpar2 ignore all retrieved
812 records that do not have the metadata element name with value substring
815 Pazpar2 allows YAZ log level to be set (option -v).
819 For WS responses Pazpar2 creates XML header. Exception: raw record.
821 Setting XML files are now stored in etc/settings instead of etc. This
822 reflects the layout with the Debian package layout.
824 Settings may be posted for command=settings. The POSTed settings must
825 have root element 'settings' like regular setting files. In order to be
826 recognized, the POST request must use Content-Type=text/xml.
828 A service may be posted for command=init. This service will be used
829 during the session. The service may have its own target settings,
830 ICU config, timeout, etc. In order to be recognized, the POST request
831 must use Content-Type=text/xml.
833 Timeout values may be given per-service. That's element 'timeout'
834 which takes three attribute values (a subset may be given): 'session',
835 'z3950_operation', 'z3950_session'. Option -T is no longer supported
836 - used to specify session timeout.
838 Option -t tests the Pazpar2 configuration and returns exit code
839 (0=success, non-zero=failure). In previous version of Pazpar2, -t
840 specified local settings.
842 In version 1.2.0 the configuration file - after include processing -
843 was dumped to stdout. Now, the configuration is only dumped to the
844 yaz log file if option -d is given.
848 Configuration may now have multiple server areas. This means that a
849 Pazpar2 instance may listen on multiple ports. Virtual hosting is not
850 yet supported - on a server basis. Configuration may also have multiple
851 services .. That is repeating service elements inside a server. Each
852 has an attribute 'id' which serves as service ID. This ID in turn may
853 be used in a Pazpar2 session, by specifying parameter service=ID for
854 command init. There can be at most one unnamed service inside a server
855 which can be referred to by not specifying an service ID for command
856 init (backwards compatible). In order to partition multiple servers and
857 services a new include directive has been added. This takes an attribute
858 'src' which specifies one or more sub-files. For example to include
859 service files, one might use:
860 <server >.. <include src=/"etc/pazpar2/conf.d/*.xml"/> .. </server>.
861 It is the intention that that completely makes the settings directive
864 Fix problem where the record command would wait forever if there were
865 no targets to wait for (activeclients == 0).
869 One result set is created per session (last search) rather than for
870 each connection which happen to be shared (bug #3009).
872 marc21 stylesheets changed for efficiency.
876 Session timeout may be specified on the command-line as option -T.
878 Pazpar2 may now be operated in a no-merged mode for records.. All records
879 will be considered unique. This mode is enabled if no mergekey is
880 generated by the normalization stylesheet (pz:xslt).
882 Pazpar2 caches original records from each target and the 'record' command
883 with offset returns the original record if 'syntax' and 'esn' are NOT
884 specified. This speeds up retrieval of original records but also means
885 that Pazpar2 uses more memory. The cached records will be freed when the
886 session terminates or a new search is executed.
888 Pazpar2 no longer uses its own ICU wrapper. Instead the ICU wrapper
889 library part of YAZ is used.
891 Added SRU client support.
893 Automatically computes pz:nativesyntax if not provided. Works for XML and
896 --- 1.0.13 2008/11/24
898 Command bytarget returns name of target (if defined).
900 --- 1.0.12 2008/11/04
902 Fixed bug #2021.. location now holds all brief elements.
904 --- 1.0.11 2008/10/15
906 Fixed check for application/x-www-form-urlencoded parameters.
908 --- 1.0.10 2008/10/14
910 Fixes for IE in pz2.js.
912 Fixed bug #2021: non-merged, brief meta data NOT included for command=show.
916 Changed the JS library pz2.js to use POST for long URL (+ params).
918 Added installation instructions for Windows. Note: NT services is
919 NOT available until we make a new release of YAZ.
921 Preserve order of repeated metadata fields (they were reversed before).
923 More MARC21 information extracted for metadata.
927 Fixed bug #1162: HTML entities are not escaped properly.
929 Native Windows port of Pazpar2. Makefile for Visual Studio provided.
933 Marc21 stylesheet updated to reflect multiple full text fields
937 Fixed bug in pz2.js WRT DOMElement attributes on IE.
939 Fixed bug 2100: Database wildcards not working
943 Added support for retrieval of records in binary.
945 Fixed bug 1794: Pazpar2 does not return valid XML.
947 Deal with ICU not returning sortkey (resulted in SEGV before).
951 JavaScript library pzw2.js throws error if WS response (from Pazpar2 or
952 other) is malformed (non-wellformed XML or missing Pazpar2 OK status).
954 Improved diagnostics when Pazpar2 HTTP decoding fails.
956 Pazpar2 requests may be POSTed as using Content-Type
957 application/x-www-form-urlencoded.
959 Pazpar2 honors LF in HTTP headers.
961 Handle targets that handle negative hit counts (should not happen, but it
966 ICU is used for tokenization and normalization of the following: mergekey,
967 sorting, relevance terms.
969 Debian package now enables ICU tokenization and normalization by default.
973 Exposed user setting values (i.e. non-pz: names) to the record systems in two
974 ways: Either as parameters to the normalization stylesheets (which would allow the
975 programmer to postprocess or use the values in any way) or after the normalization
976 step, in which case values are made part of the normalized record (and available for
977 sorting, termlists, display, or other interface-related use.
979 Implemented sorting by year.
981 Option -d dumps records to the current log file instead of stderr.
983 Fixes for compilation on cygwin.
985 Z39.50 client code uses pz:elements. pz:elements was recognized in
986 earlier Pazpar2 versions but it was not used for anything.
988 icu_chain_test is using fgets instead of getline - fixes compilation
991 Loosen the CCL query parsing so that Pazpar2 only returns error if _all_
992 query conversions fail (rather than _any_). This means targets that do
993 not support some fields are ignored in a search.
997 Improved handling of socket timeout for Z39.50 connections.
999 Misc documentation updates and spell fixes.
1001 Debian package pazpar2 creates log rotate entry.
1003 Debian package pazpar2-apache2 reloads Apache2.
1005 jsdemo included in distribution. It illustrates the use of the js/pz2.js
1008 --- 1.0.0 2007/06/20
1010 First public release.