3 Re-introduce journal-subpart PAZ-980
4 Both citation and journal-subpart have same value.
8 Add Ubuntu utopic 14.04 and Ubuntu saucy 13.10 to the list of packages
11 Remove from js/pz2.js the code that translates just two diagnostic
12 codes (1 and 2) into human-readable messages. This is no longer
13 necessary at all, as PazPar2 has been returning the message as well as
14 the code in its responses since December 2012. Fixes PAZ-978.
16 primo xsl produces citation rather than journal-subpart PAZ-972
17 (fix in 1.8.1 was incorrect)
19 Fix missing .url files PAZ-977
20 Add missing .url+.cfg and add proper check for it.
24 Turbomarc needs number check for date 903 map PAZ-973
26 primo-pz2.xsl creates citation rather than journal-subpart PAZ-972
28 pz2.js: on successful search, issue a "show" command only if a show
29 callback function has been installed. Fixes part of PAZ-975
33 New command=stop which stops further search&retrieval for active
36 CF/primo XSL generates {volume,issue,pages}-number that are defined
37 in default Pazpar2 service definition. PAZ-968 PAZ-970
41 Various fixes for threaded operation PAZ-960 thru PAZ-966
43 Dump main configuration file during start of Pazpar2 PAZ-957
47 Log ingest failures and record failures:
49 Clean up logging PAZ-942
50 Use session lead in more places. Log hits/records/filtered for each
51 target when fetching is complete. Log hit count when a search
52 (response) is received. Remove some less useful log messages.
54 Fix warning about about missing (internal) stylesheet PAZ-956
56 Report number of filtered records in bytarget PAZ-954
58 Cache XML documents as they appear after normalization. The key
59 for the cache is database+record offset. Cache is removed if query
60 is modified for search. This speeds up re-establishing a result set
61 for databases where new query is same previous query.
65 poll: add assert for number of FDs; abort on poll failure
69 Fix hang for 2nd use of target with unresolved DNS PAZ-949
73 Use poll rather than select for main event loop to overcome limit of
74 1024 file descriptors PAZ-947
76 Override setting with same name (do not append) PAZ-945
80 Separate package: pazpar2-xsl PAZ-932
84 Update OPAC stylesheets for availabilityDate PAZ-943
86 Fix too funny startrecs description
88 Fix broken ~ match if filter contains = PAZ-941
92 Add pz:redis option for ZOOM caching using redis. This is an alternative
93 to memcached. Requires YAZ 5.2.0 to work.
97 Re-ingest native facets PAZ-934
99 Fix medium override for solr-pz2.xsl.
101 --- 1.6.41 2014/04/23
103 Fix URL with leading http:// not working PAZ-933
105 Build packages for Ubuntu Trusty Tahr 14.04 LTS
107 cf.xsl: handle medium override AND md field
109 --- 1.6.40 2014/04/10
111 sortmap relevance always uses increasing=1. PAZ-930
113 solr-pz2.xsl: ensure medium is also applied if Solr record do not
116 Fix leak in getaddrinfo usage for HTTP listener. Not a big deal because
117 this code is only executed once.
119 Fix typos is sortmap documentation.
121 Doc: fix misplaced variablelist tag.
123 --- 1.6.39 2014/02/19
125 Doc: update WRT ICU which is configured for YAZ; not Pazpar2.
126 It's been like that since version 1.1.1 from August 2009.
128 Add support for result-set caching via memcached. See description of
129 pz:memcached. Require that Pazpar2 is using YAZ 5.0.12 or later.
131 Add support for a <metadata> container tag. Patfh from Sven Porst.
133 Add support for XInclude in main configuarion file. Patch from Sven Porst.
135 Add client_{lock,unlock} before call to non_block_events in
136 connection_continue. Problem is that if non_block_events fire records,
137 then we will not unlock client at all. And as a result, a dead-lock
140 --- 1.6.38 2014/01/07
142 Avoid removing slash and other characters for generic metadata that
143 looks like a URL (contains ://). PAZ-915
145 pz2.js: Only use XDR when doing CORS. Favor XHR in all other circumstances.
147 Cluster merge fixes. PAZ-901
149 Set client state to "working" when waiting for DNS resolver. PAZ-907
151 Log when session terminates. PAZ-905
153 Fix LSB/HS conformance for /etc/init.d/pazpar2 PAZ-904
154 Debian: add support for /etc/init.d/pazpar2 status
156 --- 1.6.37 2013/11/18
158 Fix 'Record Missing' for command=show PAZ-903
160 Preserve order of records within cluster PAZ-902
162 testing: use yaz-ztest -V if possible and use YAZ in sibling directory
165 Allow clustered records to be ingested during retrieval. PAZ-900
167 Fix void function error which cannot return a value.
169 --- 1.6.36 2013/11/11
171 SRU pz:authentication="a/b" may end up as x-username=a%2Fb PAZ-899
173 Upgrade to debhelper version 7 PAZ-898
175 Package with libyaz5 PAZ-897
177 Better error message for CCL parse errors PAZ-887
179 --- 1.6.35 2013/09/23
181 New target setting: pz:authentication_mode. PAZ-896
183 pazpar2 PRM: pazpar2 runs as user nobody. PAZ-893
185 Strip #-suffix for ZOOM URLs. PAZ-892
187 --- 1.6.34 2013/08/30
189 Fix issue with hanging show/bytarget. Could happen if new search was
190 fired with filter before show from previous show completed.
192 Add 'date' handling for solr-pz2.xsl.
194 --- 1.6.33 2013/08/13
196 pz:authentication may carry user group password. If pz:authentication
197 has at least one blank in it, that forces Pazpar2 to use idPass Z39.50
198 authentication. Two forms are allowed
201 If no blanks are present, open authentication is in use (as before).
203 Fix {prev,next}recid elements that are returned by record
204 command. These were incorrect in versions 1.6.23 thru 1.6.32.
206 --- 1.6.32 2013/06/14
208 Experimental support for snippets. If argument snippets=1 is given
209 for command record or show, the text will include <match>-tags for
210 those area that matches.
212 Fix memory leak WRT client structures (incorrect inc ref count).
214 Log when a HTTP response is serialized and the time elapsed.
216 New command, service, which returns current service XML in use for
219 --- 1.6.31 2013/05/24
221 Local limit for fields of type "generic" (ie text fields) are
222 now normalized by mergekey rule before comparison takes place.
223 Before, no normalization took place and comparsion was, thus, exact.
225 New facility: dynamic rank , which allows ranking to be changed
226 for an existing result set. The rank can be set for search or
227 show. This overrides the rank for metadata elements (which fields
230 New facility:dynamic mergekey , which allows mergekey to be changed
231 for an existing result set. The mergekey can be set for search or
234 HTTP server: host=@ listens on IPV6 and IPV4 if possible.
235 Also, allow ports to be given as names (not just integers).
236 Fix @-notation on systems that don't support IPV6 sockets.
238 --- 1.6.30 2013/04/26
240 Add MasterKey Connect configuration. Refer to section "non-standard
241 databases" for more information.
243 Allow timeformat for log to be specified with option -m (as Metaproxy
246 New Debian package pazpar2-dbg.
248 Fix NULL ptr reference of se->relevance. If a new search is initiated
249 and a CCL query fails to parse, Pazpar2 could crash.
251 Fix problem with host/port mangling in Pazpar2 HTTP server. Problem
252 existed in 1.6.29 only.
254 --- 1.6.29 2013/04/05
256 IPV6 updates. Allow IPv6 addresses for database hosts and IPv6 address
257 for HTTP server. By default the HTTP server uses IPv4 only, but that can be
258 changed by setting "host" attribute for the "listen" element.
260 Change semantics of pz:extendrecs. Allow for repeated fetches .
261 pz:extendrecs is now the number of extra records to fetch (was total
264 --- 1.6.28 2013/03/21
266 Fix hang or memory violation if show occurred before a search. (not that
267 it makes much sense to perform a show before a search).
269 --- 1.6.27 2013/03/08
271 pz2.js: Element_parseChildNodes concatenates all Text/CDATA nodes, instead
274 --- 1.6.26 2013/03/08
276 New pz:metadata attribute, empty="empty-value" for Pazpar2's
277 internal representation. With this attribute, Pazpar2 treates an empty
278 pz:metadata type as having the value for "empty" - if empty.
280 New setting, pz:extendrecs, which triggers extended fetch of records
281 for a database beyond pz:maxrecs for a show command.
283 Fix warning that was falsely issued for "missing limitmap".
285 Log message for Pazpart start/stop changed. Now using same style as
286 Metaproxy, ie Pazpar2 start SHA1 / Pazpar2 stop .
288 --- 1.6.25 2013/02/07
290 Fix hang of 2nd command=show with esn/syntax given.
292 --- 1.6.24 2013/01/18
294 New merge attribute type: 'first', which takes all metadata fields
295 from first target that returns the particular field.
297 --- 1.6.23 2013/01/02
299 Extend info command with hostname and YAZ SHA1
300 Indent results for both command stat and info.
302 Allow limit on merged content. The new configuration metadata
303 element, limitcluster, configures that a metadata element (name) be used
304 as limit name for search. Applies to the whole service (ie all targets),
305 unlike pz:limitmap which is configured per-target (database).
307 New feature: limitmap local:* matches against all metadata fields.
309 Allow repeated list in limitmap spec . Separated by comma. For
310 example: value="local:title,rpn:@attr 1=4".
312 New element <message> in bytarget response. Holds diagnostic message
313 of code (say 'Unsupported Use Attribute' for Bib-1 114).
315 Improved logging for record ingestion failures.
317 Avoid using struct icu_chain in non-YAZ_HAVE_ICU mode. In the rare case,
318 when YAZ is compiled without ICU support.
320 --- 1.6.22 2012/10/11
322 Requires YAZ-4.2.40 to support native solr support.
324 Fix and improve logic handling whether or not to re-do search on sort
325 order changes. A sort order with change in ascending/descending only
326 whould not trigger a new search, which is required for targets with
327 native sorting capabilities. Each client is now checked if instructions
328 (sortmap) exist for native sorting and only client that does requires
329 it is researched. Other clients is just re-ingesting the records,
330 they already have. The resultset is now cleared if any researching
333 Connection sharing between session has broken since version 1.6.8 with
334 introduction of logic that would minimize searching if pazpar2 could
335 detect this based on same query and limits and partly sort order.
336 This could lead to segementations violations.
338 Added a chapter in the manaul about relevance ranking.
340 --- 1.6.21 2012/09/24
342 Rank tweak: follow=number will increase mult by number if two terms
343 occur next to each other; number-1 if they are one term apart , .. 0
344 if they are number a part (all in order). Default is 0 (following
345 terms has no effect).
347 Rank tweak: lead=k will divide mult by 1 + log2(1+k*l) where k is
348 value given by lead and l is length from beginning of field where
349 term occurs (l=0 for first term, l=1 for second term, ..). Default
352 Rank tweak: length=strategy. length="linear" if mult is to be divided
353 by length (existing, default behavior), length="log" if mult is to be
354 divided by log2(1+length), length="none" if mult is not to be affected
357 --- 1.6.20 2012/09/21
359 Rank algorithm details may be printed as part of show response in
360 element <relevance_info>.. This is only printed if <rank debug="yes"/>
363 Record as returned by show/record command have a minimal indentation
364 which makes things human-readable.
366 New configuration of default sorting criteria (sort-default) in
367 service definition. If no criteria is defined it will be as before
370 Search command now supports sort parameter just as the show command.
371 If no parameter is give, it will use the service sort-default value.
373 --- 1.6.19 2012/09/18
375 Rank algorithm skips strings that gets normalized to empty string.
376 For example, & and ! could map to the empty string. The weight for
377 those terms is now 0 (as if they were not part of the query).
379 Rank algorithm does not use CCL from limitmap; only from the query
380 parameter (user query).
384 --- 1.6.18 2012/09/17
386 Rank algorithm configurable by 'rank' element inside service. So far
387 only, attribute 'cluster' is recognized. If cluster="yes", multiple
388 records inside a cluster boosts higher than single records. This
389 is default behavior and existing behavior. cluster="no" takes the
390 average score of each record in a cluster.
392 --- 1.6.17 2012/09/05
394 Fix bad re-use of connections (connections with changing proxy should not
397 --- 1.6.16 2012/08/22
399 Fix a bug introduce in 1.6.15 around the position sorting. It resetted the
400 resultset and sorting when the sort order is position. However this will be done on
401 every client poll, which will make pazpar2 continuing reset and fetching.
402 It should only be done on FIRST request where the sort order change.
404 Fix an issue on suggestion option: Also disable suggestions on empty string.
406 Clean up in turbo marc stylesheet.
408 Remove the hardcoded size of termlists.
410 --- 1.6.15 2012/06/27
412 New facility: ccldirective may be given in service definition. Allows
413 CCL parsing to be customized a bit, such as defining names of operators
416 New facility: raw record by checksum, rather than offset. The record
417 command optionally takes checksum which identifies certain record from
420 New facility: per field ranking. Rank may be given as M [F N] where
421 M is default rank and N is rank for CCL terms from field F.
423 --- 1.6.14 2012/06/04
425 Fix for IE7/8 in pz.js
427 Applied patch from Giannis Kosmas on keepAlive, which also adds keepAlive to init response.
429 Lower log level some places.
431 Remove some invalid test results.
433 --- 1.6.13 2012/05/23
435 Introducing a version=2 parameter for show, termlist and bytarget commands.
436 This enables pazpar2 to return approximation on hit and count count when
437 doing record filtering using the limit parameter on search and a
438 limitmap with a value of "local:"
440 Setting pz:xslt may embed local XSLT as an alternative to referring
442 Value is not CDATA but XML nodes embedded, so escaping is not necessary
443 but a root element *must* be present. For example:
444 <settings target="target="z3950.indexdata.com/marc">
453 Metadata field rank may given by XML internal document (pz:xslt
454 result). If rank is not given, the rank from service description is
457 Metadata field can now configured a default limitmap and facetmap.
458 Setting limitmap to "local:" would work for all kind of targets, but would
459 prob. not be the optimal solution. But at least better than the default behavior
460 of pazpar2 where no filtering is done.
462 A service definition can now also contains <set/> that defines service-wide
463 settings. These will override server-wide sets and will be overridded by
466 New setting, pz:present_chunk, that specifies number of records to fetch
467 at a time. Zero will disable chunkation; will fetch max_records at once.
469 --- 1.6.12 2012/03/14
471 Revert the format change in termlist response, that could break
472 some clients / UIs since they were expecting an (empty) element
473 if no facet values was found.
475 --- 1.6.11 2012/03/07
477 Revert the behavior of returning errors when unable to block
478 on termlist, bytarget and search, when unable to block due to
479 other block. The client will now receive a regular response,
480 but it will be logged in the server. A parameter (report) is
481 added to change behavior to return error response or WARNING
482 status message. Consider this "API" as private, as it is mostly
483 untested and could be changed in future releases.
485 Fix spell error in pz2.js fix in 1.6.10.
487 New Marc2TurboMarc.xsl (contribution from Sven Porst).
488 Can solve the missing marc21.xsl updates in some cases.
490 tmarc.xsl: Simplify the 6xx to subject-long and fix 1-based
491 substring (contribtion from Sven Porst)
493 marc21.xsl: fix 1-based substring call
495 tmarc.xsl and marc21.xsl: use 856$a as last option for electronic-text.
497 Add test_termlist_block to test suite
499 --- 1.6.10 2012/02/23
501 Fix SEGV for invalid PQFs and SRU/SOLR targets
502 Also refactor a bit the code that converts from PQF to SRU/SOLR queries.
504 Fix pz2.js: "null object" due to change in in bytarget result XML.
506 Fixes in tmarc.xsl: Subject-long shorten for extra commas only.
507 Added this normalization to the other subject-long fields (d6xx),
508 where it was missing.
510 Fixes in marc21.xsl: Updated with most of the new tmarc.xsl.
511 Still differences around medium and holdings. marc21.xsl is not
512 longer active used by Index Data, and should be considered unsupported.
513 Use tmarc.xsl instead.
517 Fix SEGV that could occur for failed connections.
521 Fix bug for command sort that could return no results for active clients
522 (from previous search). This bug was present in 1.6.6-1.6.7.
524 Fix bug in results that could include results that should have been
525 filtered out. This bug was present in 1.6.6-1.6.7.
529 Fix bug introduced in 1.6.6 where a connection re-use could stall
532 Local filtering may now specify a local metadata field, eg.
533 pz:limitmap:somefield[t]=local:otherfield
537 For search, when limit and or filtering is in place and search
538 is identical to previous search, the result set is re-used and the
539 target is not searched.
541 Limits may work perform local filtering as well, by using "local:"
546 Updated bytarget command to contain a suggestions element with misspelled
547 words and suggestions to these. pz2.js has been updated to deliver this
548 onwards as well. Only target that currently delivers this is the solr
549 client in YAZ 4.2.18.
553 New service definition element, xslt, that allows an embedded stylesheet
554 to be defined. This can be referred to from pz:xslt as an alternative to
557 New pz:sortmap:field setting for specifying hints on how to make
558 a target natively sort on a field. This is used for command=show in
559 conjunction with sort.
561 New pz:url setting for specifying the actual URL for a target. When
562 this is used the target ID is not used as URL anymore and the target ID
563 may be almost any string (not including []).
565 command=termlist without name parameter returns all termlists/facets.
566 Previously if name parameter was omitted, only "subject" was returned.
570 Make termlist sorting stable. Terms with same frequency are now sorted by
571 their display name. This makes a pretty display and improves our
572 regression test because qsort is not a stable sort.
574 New sort parameter value 'position'. The 'position' sorts merged records
575 by their original position from the remote target. This is primarily useful
576 for debugging and may be used for targets that already perform some kind
577 of relevance ranking. Note that sort by default is decreasing; so to get
578 records in their original order sort=position:1 must be used.
582 tmarc.xsl: yet another 773$g fix. Was broken in 1.6.1 as well.
584 Facility to change working directory for pazpar2 daemon. Option -wdir
585 sets working directory to dir. This facility is useful if core dumps
586 must be saved. In this case, the current working directory must be
587 writable by the running user, such as "nobody".
591 New configuration element <icu_chain> for <server>/<service> which
592 allows a named ICU rule (chain) to be defined. The names relevance,
593 sort, mergekey and facet are used for those operations. The definition
594 <icu_chain id="sort" locale="en"> .. </icu_chain>
596 <sort> <icu_chain locale="en> ... </icu_chain> </sort>
597 And so on.. for relevance, mergekey and facet as well. The latter
598 style is deprecated. The facet terms are normalized by the facet
599 rule by default. This may be changed on a metadata field basis by
600 defining the new attribute 'facetrule' for the metadata element.
602 <icu_chain id="myrule" locale="en"> ... </icu_chain>
603 <metadata name="author" termlist="yes" facetrule="myrule"/>
605 Preserve rorder for merged metadata. Fixes issue as reported by Sven
606 Porst: http://lists.indexdata.dk/pipermail/yazlist/2011-July/003230.html
608 tmarc.xsl: set journal-subpart to 773$ only.
612 Modify the behavior for the limit parameter (first defined in 1.5.7).
613 Mapping of limit searches are now defined by the new configuration item
614 pz:limitmap. Fix a dead-lock problem with the limit parameter.
616 Extend tmarc.xsl to extract 773$g data (OpenURL).
620 ICU default maps remove backquote (`).
622 Command 'search' takes limit parameter (optional). The limit parameter
623 allows a search to be limited one or more facets and the corresponding
624 values. This is for server side filtering.
626 Configure tweak: Use -lm for log(3) if needed
630 Fix a problem with skiparticle sortkey that could be completely
631 ignored (and reduced to "").
633 Fix dependency problem in pazpar2 RPM package (did not require
634 libyaz4 as it should).
638 Fix memory leak that occurred for command=termlist&name=xtargets .
640 Pazpar2 may save HTTP requests. Enabled by option -R.
644 Experimental support for DTIC DADS target. New dads-pz2.xsl.
646 Support for query_syntax (overrides the default for SRU | Z39.50)
648 Support for extraArgs (ZOOM "extraArgs" option) for targets
650 New commands: status-server and status-session
654 Fix for threaded runs: Client now have a copy of the database URL,
655 which can used after the database has been release from the client.
656 This makes the logging in the connection idle timeout of the client nicer (no NOURL) and should be thread-safe.
658 tmarc.xsl: Add journal-title-abbrev and full text.
660 cf.xsl: new fields: isbn, issn, journaltitle, volume, issue
662 Fix for cmd=record before search.
664 Session Logging clean up.
666 Fix wrong termlist factor when maxrecs is different from 100.
670 Fix missing pz:termlist_term_factor in settings.c messed up pz:preferred.
671 Term factor is default enabled but can be diseabled by
672 pz:termlist_term_factor=0
676 Add scaling of facet count. Currently always enabled, needs fixing.
677 Allow user-defined info for target suffix. This has no meaning in
678 Pazpar2 except to distinguish targets from each other. The suffix
679 data begins with #. For example z3950.indexdata.com/gils#Mydata
681 Added exact-match recordfilter; format name=value
685 SOLR support. Pazpar2 may operate as web service client for SOLR.
689 Fix for show command and block=1 (dead lock). Bug was introduced in
694 New RPM packages: pazpar2, pazpar2-js, pazpar2-doc. These have been
695 tested on CentOS 5.5 only.
699 Fix problem with result sets being removed from a client session
700 if the connection for it was resused by another session. Bug #3489.
702 New iphone UI for Pazpar2 (www/iphone).
706 Fixes for threaded operation.
708 New stylesheets for TurboMARC: tmarc.xsl and opac_turbomarc.xsl.
710 New example services in etc/services in source. In the Debian packages
711 these are located in /etc/pazpar2/services-available
713 Threaded mode operational on Windows. Requires Windows 7 or Windows
716 Default value of setting pz:max_connections is 0 which means that there
717 is no limit on number of connections.
721 Pazpar2 may operate in threaded mode. Enabled by element threads in
722 the configuration. See pazpar2_conf for details.
724 New setting setting: pz:max_connections. Setting pz:max_connections is
725 a limit of number of sockets to a host. When this limit is reached,
726 Pazpar2 will wait up to 5 seconds for a connection to becomes available.
727 The client will be marked Client_Error when it can not be searched
728 (other clients in a session may work). If pz:max_connections is not set
729 for a target, a value of 30 will be used. Note: the pz:max_connections
730 will only work in threaded mode.
732 pz2.js: JSON support for show.
734 Debian package: Enable default service, default.xml, before starting
735 Pazpar2 only if there is no service already in /etc/pazpar2/services-enabled.
739 Debian version depends on on libyaz4. Note that Pazpar2 will still
740 compile from source with YAZ 3.
742 Split services into separate files. The example configuration file
743 pazpar2.cfg.dist now includes a default service default.xml (part of
744 etc). And default.xml includes settings/edu.xml. The default.xml file,
745 not to be confused with settings/defaults.xml, is a template for jsdemo
746 and other services. The Debian package installs /etc/pazpar2/server.xml
747 which is now the main pazpar2 configuration (used to be called pazpar2.cfg).
748 server.xml includes services from /etc/pazpar2/services-enabled/*.xml .
749 The default.xml (from etc) is installed in /etc/pazpar2/services-available
750 and a symlink to it is created from services-enabled. The default.xml
751 service is unnamed and, thus, will be used by jsdemo and test1.
753 New setting pz:negotiation_charset. Patch from Andrei V. Toutoukine. The
754 new setting pz:negotiation_charset specifies character set for Z39.50 Init.
758 Support for additional fields in cf.xsl and pazpar2.conf.dist:
759 publisher, available, due, location (=locallocation), callno
760 (=callnumber), thumburl and score.
762 Describe pz:xslt and the auto setting.
764 Move mergekey definition away from the normalization stylesheets and
765 define a mergekey common for all target types in pazpar2.cfg.
767 Code update: Use the Odr_int type for hit counts. This is part of
768 YAZ 3.0.47 and later and so configure checks for that.
772 Metadata attribute 'skiparticle' also works for ICU based
773 normalization. (was only working for the non-ICU/ASCII before).
775 Command bytarget with argument settings=1 will show settings per
776 target.. This is to be able to verify correct settings and be able to
777 test that they are correct. The database settings array size is now
778 also stored.. Problems with database settings array is that if not
779 careful it will be too small (smaller than dictionary per-service
782 Make record list sorting stable by comparing mergekey for records if
783 relevance/title or other sorting criteria all match. This is merely to
784 ensure that our regressions tests works (reproducible output).
786 Relevance calculation changes: use a different denominator (length) for
787 per-field relevance scoring.. Instead of length of all ranked fields we
788 now use length of individual fields (as if they were individual "free"
789 text fields). This will ensure that documents with a long field with no
790 match (say description) will not "hurt" a title match.
792 Diagnostic member was not set on connection error. Fixed
796 Command search takes two optional parameters, startecs and maxrecs,
797 that specifies the start offset (0, 1, ...) and maximum number of records
798 to fetch for each target.
800 XSLTs + MARC maps are cached within a session so we don't re-parse
801 them over and over again. Even for a session with a single search
802 there's much to be gained because many targets use the same
805 The metadata attribute 'mergekey' now takes one of three values 'no',
806 'required', 'optional' . And the resulting mergekey from metadata
807 is now ordered in the same way as metadata in the service definition.
808 Older Pazpar2 version use the order in which metadata appeared in a
811 The search argument 'filter' now offers a new operator ~ which does a
812 substring match. The = operator works as before: string match for
813 anything but pz:id, or target match for pz:id.
815 New setting pz:recordfilter. The value of this setting takes the
816 form name[~value]. This setting makes Pazpar2 ignore all retrieved
817 records that do not have the metadata element name with value substring
820 Pazpar2 allows YAZ log level to be set (option -v).
824 For WS responses Pazpar2 creates XML header. Exception: raw record.
826 Setting XML files are now stored in etc/settings instead of etc. This
827 reflects the layout with the Debian package layout.
829 Settings may be posted for command=settings. The POSTed settings must
830 have root element 'settings' like regular setting files. In order to be
831 recognized, the POST request must use Content-Type=text/xml.
833 A service may be posted for command=init. This service will be used
834 during the session. The service may have its own target settings,
835 ICU config, timeout, etc. In order to be recognized, the POST request
836 must use Content-Type=text/xml.
838 Timeout values may be given per-service. That's element 'timeout'
839 which takes three attribute values (a subset may be given): 'session',
840 'z3950_operation', 'z3950_session'. Option -T is no longer supported
841 - used to specify session timeout.
843 Option -t tests the Pazpar2 configuration and returns exit code
844 (0=success, non-zero=failure). In previous version of Pazpar2, -t
845 specified local settings.
847 In version 1.2.0 the configuration file - after include processing -
848 was dumped to stdout. Now, the configuration is only dumped to the
849 yaz log file if option -d is given.
853 Configuration may now have multiple server areas. This means that a
854 Pazpar2 instance may listen on multiple ports. Virtual hosting is not
855 yet supported - on a server basis. Configuration may also have multiple
856 services .. That is repeating service elements inside a server. Each
857 has an attribute 'id' which serves as service ID. This ID in turn may
858 be used in a Pazpar2 session, by specifying parameter service=ID for
859 command init. There can be at most one unnamed service inside a server
860 which can be referred to by not specifying an service ID for command
861 init (backwards compatible). In order to partition multiple servers and
862 services a new include directive has been added. This takes an attribute
863 'src' which specifies one or more sub-files. For example to include
864 service files, one might use:
865 <server >.. <include src=/"etc/pazpar2/conf.d/*.xml"/> .. </server>.
866 It is the intention that that completely makes the settings directive
869 Fix problem where the record command would wait forever if there were
870 no targets to wait for (activeclients == 0).
874 One result set is created per session (last search) rather than for
875 each connection which happen to be shared (bug #3009).
877 marc21 stylesheets changed for efficiency.
881 Session timeout may be specified on the command-line as option -T.
883 Pazpar2 may now be operated in a no-merged mode for records.. All records
884 will be considered unique. This mode is enabled if no mergekey is
885 generated by the normalization stylesheet (pz:xslt).
887 Pazpar2 caches original records from each target and the 'record' command
888 with offset returns the original record if 'syntax' and 'esn' are NOT
889 specified. This speeds up retrieval of original records but also means
890 that Pazpar2 uses more memory. The cached records will be freed when the
891 session terminates or a new search is executed.
893 Pazpar2 no longer uses its own ICU wrapper. Instead the ICU wrapper
894 library part of YAZ is used.
896 Added SRU client support.
898 Automatically computes pz:nativesyntax if not provided. Works for XML and
901 --- 1.0.13 2008/11/24
903 Command bytarget returns name of target (if defined).
905 --- 1.0.12 2008/11/04
907 Fixed bug #2021.. location now holds all brief elements.
909 --- 1.0.11 2008/10/15
911 Fixed check for application/x-www-form-urlencoded parameters.
913 --- 1.0.10 2008/10/14
915 Fixes for IE in pz2.js.
917 Fixed bug #2021: non-merged, brief meta data NOT included for command=show.
921 Changed the JS library pz2.js to use POST for long URL (+ params).
923 Added installation instructions for Windows. Note: NT services is
924 NOT available until we make a new release of YAZ.
926 Preserve order of repeated metadata fields (they were reversed before).
928 More MARC21 information extracted for metadata.
932 Fixed bug #1162: HTML entities are not escaped properly.
934 Native Windows port of Pazpar2. Makefile for Visual Studio provided.
938 Marc21 stylesheet updated to reflect multiple full text fields
942 Fixed bug in pz2.js WRT DOMElement attributes on IE.
944 Fixed bug 2100: Database wildcards not working
948 Added support for retrieval of records in binary.
950 Fixed bug 1794: Pazpar2 does not return valid XML.
952 Deal with ICU not returning sortkey (resulted in SEGV before).
956 JavaScript library pzw2.js throws error if WS response (from Pazpar2 or
957 other) is malformed (non-wellformed XML or missing Pazpar2 OK status).
959 Improved diagnostics when Pazpar2 HTTP decoding fails.
961 Pazpar2 requests may be POSTed as using Content-Type
962 application/x-www-form-urlencoded.
964 Pazpar2 honors LF in HTTP headers.
966 Handle targets that handle negative hit counts (should not happen, but it
971 ICU is used for tokenization and normalization of the following: mergekey,
972 sorting, relevance terms.
974 Debian package now enables ICU tokenization and normalization by default.
978 Exposed user setting values (i.e. non-pz: names) to the record systems in two
979 ways: Either as parameters to the normalization stylesheets (which would allow the
980 programmer to postprocess or use the values in any way) or after the normalization
981 step, in which case values are made part of the normalized record (and available for
982 sorting, termlists, display, or other interface-related use.
984 Implemented sorting by year.
986 Option -d dumps records to the current log file instead of stderr.
988 Fixes for compilation on cygwin.
990 Z39.50 client code uses pz:elements. pz:elements was recognized in
991 earlier Pazpar2 versions but it was not used for anything.
993 icu_chain_test is using fgets instead of getline - fixes compilation
996 Loosen the CCL query parsing so that Pazpar2 only returns error if _all_
997 query conversions fail (rather than _any_). This means targets that do
998 not support some fields are ignored in a search.
1000 --- 1.0.1 2007/07/03
1002 Improved handling of socket timeout for Z39.50 connections.
1004 Misc documentation updates and spell fixes.
1006 Debian package pazpar2 creates log rotate entry.
1008 Debian package pazpar2-apache2 reloads Apache2.
1010 jsdemo included in distribution. It illustrates the use of the js/pz2.js
1013 --- 1.0.0 2007/06/20
1015 First public release.