3 Larger string buffer for forward address PAZ-987
4 Fixes buffer overflow that could occur if forward address is IPV6.
6 Updates to Windows NMAKE makefile for Visual Studio 2013.
10 Use YAZ backtrace facility PAZ-983. In case of crashes YAZ log may
11 include more details about the fault. Better install gdb and the
12 debug version of pazpar2 (pazpar2-dbg on Debian/Ubuntu).
14 Per target timeout PAZ-981
15 New setting pz:timeout which overrides z3950_operation timeout
20 Re-introduce journal-subpart PAZ-980
21 Both citation and journal-subpart have same value.
25 Add Ubuntu utopic 14.04 and Ubuntu saucy 13.10 to the list of packages
28 Remove from js/pz2.js the code that translates just two diagnostic
29 codes (1 and 2) into human-readable messages. This is no longer
30 necessary at all, as PazPar2 has been returning the message as well as
31 the code in its responses since December 2012. Fixes PAZ-978.
33 primo xsl produces citation rather than journal-subpart PAZ-972
34 (fix in 1.8.1 was incorrect)
36 Fix missing .url files PAZ-977
37 Add missing .url+.cfg and add proper check for it.
41 Turbomarc needs number check for date 903 map PAZ-973
43 primo-pz2.xsl creates citation rather than journal-subpart PAZ-972
45 pz2.js: on successful search, issue a "show" command only if a show
46 callback function has been installed. Fixes part of PAZ-975
50 New command=stop which stops further search&retrieval for active
53 CF/primo XSL generates {volume,issue,pages}-number that are defined
54 in default Pazpar2 service definition. PAZ-968 PAZ-970
58 Various fixes for threaded operation PAZ-960 thru PAZ-966
60 Dump main configuration file during start of Pazpar2 PAZ-957
64 Log ingest failures and record failures:
66 Clean up logging PAZ-942
67 Use session lead in more places. Log hits/records/filtered for each
68 target when fetching is complete. Log hit count when a search
69 (response) is received. Remove some less useful log messages.
71 Fix warning about about missing (internal) stylesheet PAZ-956
73 Report number of filtered records in bytarget PAZ-954
75 Cache XML documents as they appear after normalization. The key
76 for the cache is database+record offset. Cache is removed if query
77 is modified for search. This speeds up re-establishing a result set
78 for databases where new query is same previous query.
82 poll: add assert for number of FDs; abort on poll failure
86 Fix hang for 2nd use of target with unresolved DNS PAZ-949
90 Use poll rather than select for main event loop to overcome limit of
91 1024 file descriptors PAZ-947
93 Override setting with same name (do not append) PAZ-945
97 Separate package: pazpar2-xsl PAZ-932
101 Update OPAC stylesheets for availabilityDate PAZ-943
103 Fix too funny startrecs description
105 Fix broken ~ match if filter contains = PAZ-941
107 --- 1.6.43 2014/06/12
109 Add pz:redis option for ZOOM caching using redis. This is an alternative
110 to memcached. Requires YAZ 5.2.0 to work.
112 --- 1.6.42 2014/05/06
114 Re-ingest native facets PAZ-934
116 Fix medium override for solr-pz2.xsl.
118 --- 1.6.41 2014/04/23
120 Fix URL with leading http:// not working PAZ-933
122 Build packages for Ubuntu Trusty Tahr 14.04 LTS
124 cf.xsl: handle medium override AND md field
126 --- 1.6.40 2014/04/10
128 sortmap relevance always uses increasing=1. PAZ-930
130 solr-pz2.xsl: ensure medium is also applied if Solr record do not
133 Fix leak in getaddrinfo usage for HTTP listener. Not a big deal because
134 this code is only executed once.
136 Fix typos is sortmap documentation.
138 Doc: fix misplaced variablelist tag.
140 --- 1.6.39 2014/02/19
142 Doc: update WRT ICU which is configured for YAZ; not Pazpar2.
143 It's been like that since version 1.1.1 from August 2009.
145 Add support for result-set caching via memcached. See description of
146 pz:memcached. Require that Pazpar2 is using YAZ 5.0.12 or later.
148 Add support for a <metadata> container tag. Patfh from Sven Porst.
150 Add support for XInclude in main configuarion file. Patch from Sven Porst.
152 Add client_{lock,unlock} before call to non_block_events in
153 connection_continue. Problem is that if non_block_events fire records,
154 then we will not unlock client at all. And as a result, a dead-lock
157 --- 1.6.38 2014/01/07
159 Avoid removing slash and other characters for generic metadata that
160 looks like a URL (contains ://). PAZ-915
162 pz2.js: Only use XDR when doing CORS. Favor XHR in all other circumstances.
164 Cluster merge fixes. PAZ-901
166 Set client state to "working" when waiting for DNS resolver. PAZ-907
168 Log when session terminates. PAZ-905
170 Fix LSB/HS conformance for /etc/init.d/pazpar2 PAZ-904
171 Debian: add support for /etc/init.d/pazpar2 status
173 --- 1.6.37 2013/11/18
175 Fix 'Record Missing' for command=show PAZ-903
177 Preserve order of records within cluster PAZ-902
179 testing: use yaz-ztest -V if possible and use YAZ in sibling directory
182 Allow clustered records to be ingested during retrieval. PAZ-900
184 Fix void function error which cannot return a value.
186 --- 1.6.36 2013/11/11
188 SRU pz:authentication="a/b" may end up as x-username=a%2Fb PAZ-899
190 Upgrade to debhelper version 7 PAZ-898
192 Package with libyaz5 PAZ-897
194 Better error message for CCL parse errors PAZ-887
196 --- 1.6.35 2013/09/23
198 New target setting: pz:authentication_mode. PAZ-896
200 pazpar2 PRM: pazpar2 runs as user nobody. PAZ-893
202 Strip #-suffix for ZOOM URLs. PAZ-892
204 --- 1.6.34 2013/08/30
206 Fix issue with hanging show/bytarget. Could happen if new search was
207 fired with filter before show from previous show completed.
209 Add 'date' handling for solr-pz2.xsl.
211 --- 1.6.33 2013/08/13
213 pz:authentication may carry user group password. If pz:authentication
214 has at least one blank in it, that forces Pazpar2 to use idPass Z39.50
215 authentication. Two forms are allowed
218 If no blanks are present, open authentication is in use (as before).
220 Fix {prev,next}recid elements that are returned by record
221 command. These were incorrect in versions 1.6.23 thru 1.6.32.
223 --- 1.6.32 2013/06/14
225 Experimental support for snippets. If argument snippets=1 is given
226 for command record or show, the text will include <match>-tags for
227 those area that matches.
229 Fix memory leak WRT client structures (incorrect inc ref count).
231 Log when a HTTP response is serialized and the time elapsed.
233 New command, service, which returns current service XML in use for
236 --- 1.6.31 2013/05/24
238 Local limit for fields of type "generic" (ie text fields) are
239 now normalized by mergekey rule before comparison takes place.
240 Before, no normalization took place and comparsion was, thus, exact.
242 New facility: dynamic rank , which allows ranking to be changed
243 for an existing result set. The rank can be set for search or
244 show. This overrides the rank for metadata elements (which fields
247 New facility:dynamic mergekey , which allows mergekey to be changed
248 for an existing result set. The mergekey can be set for search or
251 HTTP server: host=@ listens on IPV6 and IPV4 if possible.
252 Also, allow ports to be given as names (not just integers).
253 Fix @-notation on systems that don't support IPV6 sockets.
255 --- 1.6.30 2013/04/26
257 Add MasterKey Connect configuration. Refer to section "non-standard
258 databases" for more information.
260 Allow timeformat for log to be specified with option -m (as Metaproxy
263 New Debian package pazpar2-dbg.
265 Fix NULL ptr reference of se->relevance. If a new search is initiated
266 and a CCL query fails to parse, Pazpar2 could crash.
268 Fix problem with host/port mangling in Pazpar2 HTTP server. Problem
269 existed in 1.6.29 only.
271 --- 1.6.29 2013/04/05
273 IPV6 updates. Allow IPv6 addresses for database hosts and IPv6 address
274 for HTTP server. By default the HTTP server uses IPv4 only, but that can be
275 changed by setting "host" attribute for the "listen" element.
277 Change semantics of pz:extendrecs. Allow for repeated fetches .
278 pz:extendrecs is now the number of extra records to fetch (was total
281 --- 1.6.28 2013/03/21
283 Fix hang or memory violation if show occurred before a search. (not that
284 it makes much sense to perform a show before a search).
286 --- 1.6.27 2013/03/08
288 pz2.js: Element_parseChildNodes concatenates all Text/CDATA nodes, instead
291 --- 1.6.26 2013/03/08
293 New pz:metadata attribute, empty="empty-value" for Pazpar2's
294 internal representation. With this attribute, Pazpar2 treates an empty
295 pz:metadata type as having the value for "empty" - if empty.
297 New setting, pz:extendrecs, which triggers extended fetch of records
298 for a database beyond pz:maxrecs for a show command.
300 Fix warning that was falsely issued for "missing limitmap".
302 Log message for Pazpart start/stop changed. Now using same style as
303 Metaproxy, ie Pazpar2 start SHA1 / Pazpar2 stop .
305 --- 1.6.25 2013/02/07
307 Fix hang of 2nd command=show with esn/syntax given.
309 --- 1.6.24 2013/01/18
311 New merge attribute type: 'first', which takes all metadata fields
312 from first target that returns the particular field.
314 --- 1.6.23 2013/01/02
316 Extend info command with hostname and YAZ SHA1
317 Indent results for both command stat and info.
319 Allow limit on merged content. The new configuration metadata
320 element, limitcluster, configures that a metadata element (name) be used
321 as limit name for search. Applies to the whole service (ie all targets),
322 unlike pz:limitmap which is configured per-target (database).
324 New feature: limitmap local:* matches against all metadata fields.
326 Allow repeated list in limitmap spec . Separated by comma. For
327 example: value="local:title,rpn:@attr 1=4".
329 New element <message> in bytarget response. Holds diagnostic message
330 of code (say 'Unsupported Use Attribute' for Bib-1 114).
332 Improved logging for record ingestion failures.
334 Avoid using struct icu_chain in non-YAZ_HAVE_ICU mode. In the rare case,
335 when YAZ is compiled without ICU support.
337 --- 1.6.22 2012/10/11
339 Requires YAZ-4.2.40 to support native solr support.
341 Fix and improve logic handling whether or not to re-do search on sort
342 order changes. A sort order with change in ascending/descending only
343 whould not trigger a new search, which is required for targets with
344 native sorting capabilities. Each client is now checked if instructions
345 (sortmap) exist for native sorting and only client that does requires
346 it is researched. Other clients is just re-ingesting the records,
347 they already have. The resultset is now cleared if any researching
350 Connection sharing between session has broken since version 1.6.8 with
351 introduction of logic that would minimize searching if pazpar2 could
352 detect this based on same query and limits and partly sort order.
353 This could lead to segementations violations.
355 Added a chapter in the manaul about relevance ranking.
357 --- 1.6.21 2012/09/24
359 Rank tweak: follow=number will increase mult by number if two terms
360 occur next to each other; number-1 if they are one term apart , .. 0
361 if they are number a part (all in order). Default is 0 (following
362 terms has no effect).
364 Rank tweak: lead=k will divide mult by 1 + log2(1+k*l) where k is
365 value given by lead and l is length from beginning of field where
366 term occurs (l=0 for first term, l=1 for second term, ..). Default
369 Rank tweak: length=strategy. length="linear" if mult is to be divided
370 by length (existing, default behavior), length="log" if mult is to be
371 divided by log2(1+length), length="none" if mult is not to be affected
374 --- 1.6.20 2012/09/21
376 Rank algorithm details may be printed as part of show response in
377 element <relevance_info>.. This is only printed if <rank debug="yes"/>
380 Record as returned by show/record command have a minimal indentation
381 which makes things human-readable.
383 New configuration of default sorting criteria (sort-default) in
384 service definition. If no criteria is defined it will be as before
387 Search command now supports sort parameter just as the show command.
388 If no parameter is give, it will use the service sort-default value.
390 --- 1.6.19 2012/09/18
392 Rank algorithm skips strings that gets normalized to empty string.
393 For example, & and ! could map to the empty string. The weight for
394 those terms is now 0 (as if they were not part of the query).
396 Rank algorithm does not use CCL from limitmap; only from the query
397 parameter (user query).
401 --- 1.6.18 2012/09/17
403 Rank algorithm configurable by 'rank' element inside service. So far
404 only, attribute 'cluster' is recognized. If cluster="yes", multiple
405 records inside a cluster boosts higher than single records. This
406 is default behavior and existing behavior. cluster="no" takes the
407 average score of each record in a cluster.
409 --- 1.6.17 2012/09/05
411 Fix bad re-use of connections (connections with changing proxy should not
414 --- 1.6.16 2012/08/22
416 Fix a bug introduce in 1.6.15 around the position sorting. It resetted the
417 resultset and sorting when the sort order is position. However this will be done on
418 every client poll, which will make pazpar2 continuing reset and fetching.
419 It should only be done on FIRST request where the sort order change.
421 Fix an issue on suggestion option: Also disable suggestions on empty string.
423 Clean up in turbo marc stylesheet.
425 Remove the hardcoded size of termlists.
427 --- 1.6.15 2012/06/27
429 New facility: ccldirective may be given in service definition. Allows
430 CCL parsing to be customized a bit, such as defining names of operators
433 New facility: raw record by checksum, rather than offset. The record
434 command optionally takes checksum which identifies certain record from
437 New facility: per field ranking. Rank may be given as M [F N] where
438 M is default rank and N is rank for CCL terms from field F.
440 --- 1.6.14 2012/06/04
442 Fix for IE7/8 in pz.js
444 Applied patch from Giannis Kosmas on keepAlive, which also adds keepAlive to init response.
446 Lower log level some places.
448 Remove some invalid test results.
450 --- 1.6.13 2012/05/23
452 Introducing a version=2 parameter for show, termlist and bytarget commands.
453 This enables pazpar2 to return approximation on hit and count count when
454 doing record filtering using the limit parameter on search and a
455 limitmap with a value of "local:"
457 Setting pz:xslt may embed local XSLT as an alternative to referring
459 Value is not CDATA but XML nodes embedded, so escaping is not necessary
460 but a root element *must* be present. For example:
461 <settings target="target="z3950.indexdata.com/marc">
470 Metadata field rank may given by XML internal document (pz:xslt
471 result). If rank is not given, the rank from service description is
474 Metadata field can now configured a default limitmap and facetmap.
475 Setting limitmap to "local:" would work for all kind of targets, but would
476 prob. not be the optimal solution. But at least better than the default behavior
477 of pazpar2 where no filtering is done.
479 A service definition can now also contains <set/> that defines service-wide
480 settings. These will override server-wide sets and will be overridded by
483 New setting, pz:present_chunk, that specifies number of records to fetch
484 at a time. Zero will disable chunkation; will fetch max_records at once.
486 --- 1.6.12 2012/03/14
488 Revert the format change in termlist response, that could break
489 some clients / UIs since they were expecting an (empty) element
490 if no facet values was found.
492 --- 1.6.11 2012/03/07
494 Revert the behavior of returning errors when unable to block
495 on termlist, bytarget and search, when unable to block due to
496 other block. The client will now receive a regular response,
497 but it will be logged in the server. A parameter (report) is
498 added to change behavior to return error response or WARNING
499 status message. Consider this "API" as private, as it is mostly
500 untested and could be changed in future releases.
502 Fix spell error in pz2.js fix in 1.6.10.
504 New Marc2TurboMarc.xsl (contribution from Sven Porst).
505 Can solve the missing marc21.xsl updates in some cases.
507 tmarc.xsl: Simplify the 6xx to subject-long and fix 1-based
508 substring (contribtion from Sven Porst)
510 marc21.xsl: fix 1-based substring call
512 tmarc.xsl and marc21.xsl: use 856$a as last option for electronic-text.
514 Add test_termlist_block to test suite
516 --- 1.6.10 2012/02/23
518 Fix SEGV for invalid PQFs and SRU/SOLR targets
519 Also refactor a bit the code that converts from PQF to SRU/SOLR queries.
521 Fix pz2.js: "null object" due to change in in bytarget result XML.
523 Fixes in tmarc.xsl: Subject-long shorten for extra commas only.
524 Added this normalization to the other subject-long fields (d6xx),
525 where it was missing.
527 Fixes in marc21.xsl: Updated with most of the new tmarc.xsl.
528 Still differences around medium and holdings. marc21.xsl is not
529 longer active used by Index Data, and should be considered unsupported.
530 Use tmarc.xsl instead.
534 Fix SEGV that could occur for failed connections.
538 Fix bug for command sort that could return no results for active clients
539 (from previous search). This bug was present in 1.6.6-1.6.7.
541 Fix bug in results that could include results that should have been
542 filtered out. This bug was present in 1.6.6-1.6.7.
546 Fix bug introduced in 1.6.6 where a connection re-use could stall
549 Local filtering may now specify a local metadata field, eg.
550 pz:limitmap:somefield[t]=local:otherfield
554 For search, when limit and or filtering is in place and search
555 is identical to previous search, the result set is re-used and the
556 target is not searched.
558 Limits may work perform local filtering as well, by using "local:"
563 Updated bytarget command to contain a suggestions element with misspelled
564 words and suggestions to these. pz2.js has been updated to deliver this
565 onwards as well. Only target that currently delivers this is the solr
566 client in YAZ 4.2.18.
570 New service definition element, xslt, that allows an embedded stylesheet
571 to be defined. This can be referred to from pz:xslt as an alternative to
574 New pz:sortmap:field setting for specifying hints on how to make
575 a target natively sort on a field. This is used for command=show in
576 conjunction with sort.
578 New pz:url setting for specifying the actual URL for a target. When
579 this is used the target ID is not used as URL anymore and the target ID
580 may be almost any string (not including []).
582 command=termlist without name parameter returns all termlists/facets.
583 Previously if name parameter was omitted, only "subject" was returned.
587 Make termlist sorting stable. Terms with same frequency are now sorted by
588 their display name. This makes a pretty display and improves our
589 regression test because qsort is not a stable sort.
591 New sort parameter value 'position'. The 'position' sorts merged records
592 by their original position from the remote target. This is primarily useful
593 for debugging and may be used for targets that already perform some kind
594 of relevance ranking. Note that sort by default is decreasing; so to get
595 records in their original order sort=position:1 must be used.
599 tmarc.xsl: yet another 773$g fix. Was broken in 1.6.1 as well.
601 Facility to change working directory for pazpar2 daemon. Option -wdir
602 sets working directory to dir. This facility is useful if core dumps
603 must be saved. In this case, the current working directory must be
604 writable by the running user, such as "nobody".
608 New configuration element <icu_chain> for <server>/<service> which
609 allows a named ICU rule (chain) to be defined. The names relevance,
610 sort, mergekey and facet are used for those operations. The definition
611 <icu_chain id="sort" locale="en"> .. </icu_chain>
613 <sort> <icu_chain locale="en> ... </icu_chain> </sort>
614 And so on.. for relevance, mergekey and facet as well. The latter
615 style is deprecated. The facet terms are normalized by the facet
616 rule by default. This may be changed on a metadata field basis by
617 defining the new attribute 'facetrule' for the metadata element.
619 <icu_chain id="myrule" locale="en"> ... </icu_chain>
620 <metadata name="author" termlist="yes" facetrule="myrule"/>
622 Preserve rorder for merged metadata. Fixes issue as reported by Sven
623 Porst: http://lists.indexdata.dk/pipermail/yazlist/2011-July/003230.html
625 tmarc.xsl: set journal-subpart to 773$ only.
629 Modify the behavior for the limit parameter (first defined in 1.5.7).
630 Mapping of limit searches are now defined by the new configuration item
631 pz:limitmap. Fix a dead-lock problem with the limit parameter.
633 Extend tmarc.xsl to extract 773$g data (OpenURL).
637 ICU default maps remove backquote (`).
639 Command 'search' takes limit parameter (optional). The limit parameter
640 allows a search to be limited one or more facets and the corresponding
641 values. This is for server side filtering.
643 Configure tweak: Use -lm for log(3) if needed
647 Fix a problem with skiparticle sortkey that could be completely
648 ignored (and reduced to "").
650 Fix dependency problem in pazpar2 RPM package (did not require
651 libyaz4 as it should).
655 Fix memory leak that occurred for command=termlist&name=xtargets .
657 Pazpar2 may save HTTP requests. Enabled by option -R.
661 Experimental support for DTIC DADS target. New dads-pz2.xsl.
663 Support for query_syntax (overrides the default for SRU | Z39.50)
665 Support for extraArgs (ZOOM "extraArgs" option) for targets
667 New commands: status-server and status-session
671 Fix for threaded runs: Client now have a copy of the database URL,
672 which can used after the database has been release from the client.
673 This makes the logging in the connection idle timeout of the client nicer (no NOURL) and should be thread-safe.
675 tmarc.xsl: Add journal-title-abbrev and full text.
677 cf.xsl: new fields: isbn, issn, journaltitle, volume, issue
679 Fix for cmd=record before search.
681 Session Logging clean up.
683 Fix wrong termlist factor when maxrecs is different from 100.
687 Fix missing pz:termlist_term_factor in settings.c messed up pz:preferred.
688 Term factor is default enabled but can be diseabled by
689 pz:termlist_term_factor=0
693 Add scaling of facet count. Currently always enabled, needs fixing.
694 Allow user-defined info for target suffix. This has no meaning in
695 Pazpar2 except to distinguish targets from each other. The suffix
696 data begins with #. For example z3950.indexdata.com/gils#Mydata
698 Added exact-match recordfilter; format name=value
702 SOLR support. Pazpar2 may operate as web service client for SOLR.
706 Fix for show command and block=1 (dead lock). Bug was introduced in
711 New RPM packages: pazpar2, pazpar2-js, pazpar2-doc. These have been
712 tested on CentOS 5.5 only.
716 Fix problem with result sets being removed from a client session
717 if the connection for it was resused by another session. Bug #3489.
719 New iphone UI for Pazpar2 (www/iphone).
723 Fixes for threaded operation.
725 New stylesheets for TurboMARC: tmarc.xsl and opac_turbomarc.xsl.
727 New example services in etc/services in source. In the Debian packages
728 these are located in /etc/pazpar2/services-available
730 Threaded mode operational on Windows. Requires Windows 7 or Windows
733 Default value of setting pz:max_connections is 0 which means that there
734 is no limit on number of connections.
738 Pazpar2 may operate in threaded mode. Enabled by element threads in
739 the configuration. See pazpar2_conf for details.
741 New setting setting: pz:max_connections. Setting pz:max_connections is
742 a limit of number of sockets to a host. When this limit is reached,
743 Pazpar2 will wait up to 5 seconds for a connection to becomes available.
744 The client will be marked Client_Error when it can not be searched
745 (other clients in a session may work). If pz:max_connections is not set
746 for a target, a value of 30 will be used. Note: the pz:max_connections
747 will only work in threaded mode.
749 pz2.js: JSON support for show.
751 Debian package: Enable default service, default.xml, before starting
752 Pazpar2 only if there is no service already in /etc/pazpar2/services-enabled.
756 Debian version depends on on libyaz4. Note that Pazpar2 will still
757 compile from source with YAZ 3.
759 Split services into separate files. The example configuration file
760 pazpar2.cfg.dist now includes a default service default.xml (part of
761 etc). And default.xml includes settings/edu.xml. The default.xml file,
762 not to be confused with settings/defaults.xml, is a template for jsdemo
763 and other services. The Debian package installs /etc/pazpar2/server.xml
764 which is now the main pazpar2 configuration (used to be called pazpar2.cfg).
765 server.xml includes services from /etc/pazpar2/services-enabled/*.xml .
766 The default.xml (from etc) is installed in /etc/pazpar2/services-available
767 and a symlink to it is created from services-enabled. The default.xml
768 service is unnamed and, thus, will be used by jsdemo and test1.
770 New setting pz:negotiation_charset. Patch from Andrei V. Toutoukine. The
771 new setting pz:negotiation_charset specifies character set for Z39.50 Init.
775 Support for additional fields in cf.xsl and pazpar2.conf.dist:
776 publisher, available, due, location (=locallocation), callno
777 (=callnumber), thumburl and score.
779 Describe pz:xslt and the auto setting.
781 Move mergekey definition away from the normalization stylesheets and
782 define a mergekey common for all target types in pazpar2.cfg.
784 Code update: Use the Odr_int type for hit counts. This is part of
785 YAZ 3.0.47 and later and so configure checks for that.
789 Metadata attribute 'skiparticle' also works for ICU based
790 normalization. (was only working for the non-ICU/ASCII before).
792 Command bytarget with argument settings=1 will show settings per
793 target.. This is to be able to verify correct settings and be able to
794 test that they are correct. The database settings array size is now
795 also stored.. Problems with database settings array is that if not
796 careful it will be too small (smaller than dictionary per-service
799 Make record list sorting stable by comparing mergekey for records if
800 relevance/title or other sorting criteria all match. This is merely to
801 ensure that our regressions tests works (reproducible output).
803 Relevance calculation changes: use a different denominator (length) for
804 per-field relevance scoring.. Instead of length of all ranked fields we
805 now use length of individual fields (as if they were individual "free"
806 text fields). This will ensure that documents with a long field with no
807 match (say description) will not "hurt" a title match.
809 Diagnostic member was not set on connection error. Fixed
813 Command search takes two optional parameters, startecs and maxrecs,
814 that specifies the start offset (0, 1, ...) and maximum number of records
815 to fetch for each target.
817 XSLTs + MARC maps are cached within a session so we don't re-parse
818 them over and over again. Even for a session with a single search
819 there's much to be gained because many targets use the same
822 The metadata attribute 'mergekey' now takes one of three values 'no',
823 'required', 'optional' . And the resulting mergekey from metadata
824 is now ordered in the same way as metadata in the service definition.
825 Older Pazpar2 version use the order in which metadata appeared in a
828 The search argument 'filter' now offers a new operator ~ which does a
829 substring match. The = operator works as before: string match for
830 anything but pz:id, or target match for pz:id.
832 New setting pz:recordfilter. The value of this setting takes the
833 form name[~value]. This setting makes Pazpar2 ignore all retrieved
834 records that do not have the metadata element name with value substring
837 Pazpar2 allows YAZ log level to be set (option -v).
841 For WS responses Pazpar2 creates XML header. Exception: raw record.
843 Setting XML files are now stored in etc/settings instead of etc. This
844 reflects the layout with the Debian package layout.
846 Settings may be posted for command=settings. The POSTed settings must
847 have root element 'settings' like regular setting files. In order to be
848 recognized, the POST request must use Content-Type=text/xml.
850 A service may be posted for command=init. This service will be used
851 during the session. The service may have its own target settings,
852 ICU config, timeout, etc. In order to be recognized, the POST request
853 must use Content-Type=text/xml.
855 Timeout values may be given per-service. That's element 'timeout'
856 which takes three attribute values (a subset may be given): 'session',
857 'z3950_operation', 'z3950_session'. Option -T is no longer supported
858 - used to specify session timeout.
860 Option -t tests the Pazpar2 configuration and returns exit code
861 (0=success, non-zero=failure). In previous version of Pazpar2, -t
862 specified local settings.
864 In version 1.2.0 the configuration file - after include processing -
865 was dumped to stdout. Now, the configuration is only dumped to the
866 yaz log file if option -d is given.
870 Configuration may now have multiple server areas. This means that a
871 Pazpar2 instance may listen on multiple ports. Virtual hosting is not
872 yet supported - on a server basis. Configuration may also have multiple
873 services .. That is repeating service elements inside a server. Each
874 has an attribute 'id' which serves as service ID. This ID in turn may
875 be used in a Pazpar2 session, by specifying parameter service=ID for
876 command init. There can be at most one unnamed service inside a server
877 which can be referred to by not specifying an service ID for command
878 init (backwards compatible). In order to partition multiple servers and
879 services a new include directive has been added. This takes an attribute
880 'src' which specifies one or more sub-files. For example to include
881 service files, one might use:
882 <server >.. <include src=/"etc/pazpar2/conf.d/*.xml"/> .. </server>.
883 It is the intention that that completely makes the settings directive
886 Fix problem where the record command would wait forever if there were
887 no targets to wait for (activeclients == 0).
891 One result set is created per session (last search) rather than for
892 each connection which happen to be shared (bug #3009).
894 marc21 stylesheets changed for efficiency.
898 Session timeout may be specified on the command-line as option -T.
900 Pazpar2 may now be operated in a no-merged mode for records.. All records
901 will be considered unique. This mode is enabled if no mergekey is
902 generated by the normalization stylesheet (pz:xslt).
904 Pazpar2 caches original records from each target and the 'record' command
905 with offset returns the original record if 'syntax' and 'esn' are NOT
906 specified. This speeds up retrieval of original records but also means
907 that Pazpar2 uses more memory. The cached records will be freed when the
908 session terminates or a new search is executed.
910 Pazpar2 no longer uses its own ICU wrapper. Instead the ICU wrapper
911 library part of YAZ is used.
913 Added SRU client support.
915 Automatically computes pz:nativesyntax if not provided. Works for XML and
918 --- 1.0.13 2008/11/24
920 Command bytarget returns name of target (if defined).
922 --- 1.0.12 2008/11/04
924 Fixed bug #2021.. location now holds all brief elements.
926 --- 1.0.11 2008/10/15
928 Fixed check for application/x-www-form-urlencoded parameters.
930 --- 1.0.10 2008/10/14
932 Fixes for IE in pz2.js.
934 Fixed bug #2021: non-merged, brief meta data NOT included for command=show.
938 Changed the JS library pz2.js to use POST for long URL (+ params).
940 Added installation instructions for Windows. Note: NT services is
941 NOT available until we make a new release of YAZ.
943 Preserve order of repeated metadata fields (they were reversed before).
945 More MARC21 information extracted for metadata.
949 Fixed bug #1162: HTML entities are not escaped properly.
951 Native Windows port of Pazpar2. Makefile for Visual Studio provided.
955 Marc21 stylesheet updated to reflect multiple full text fields
959 Fixed bug in pz2.js WRT DOMElement attributes on IE.
961 Fixed bug 2100: Database wildcards not working
965 Added support for retrieval of records in binary.
967 Fixed bug 1794: Pazpar2 does not return valid XML.
969 Deal with ICU not returning sortkey (resulted in SEGV before).
973 JavaScript library pzw2.js throws error if WS response (from Pazpar2 or
974 other) is malformed (non-wellformed XML or missing Pazpar2 OK status).
976 Improved diagnostics when Pazpar2 HTTP decoding fails.
978 Pazpar2 requests may be POSTed as using Content-Type
979 application/x-www-form-urlencoded.
981 Pazpar2 honors LF in HTTP headers.
983 Handle targets that handle negative hit counts (should not happen, but it
988 ICU is used for tokenization and normalization of the following: mergekey,
989 sorting, relevance terms.
991 Debian package now enables ICU tokenization and normalization by default.
995 Exposed user setting values (i.e. non-pz: names) to the record systems in two
996 ways: Either as parameters to the normalization stylesheets (which would allow the
997 programmer to postprocess or use the values in any way) or after the normalization
998 step, in which case values are made part of the normalized record (and available for
999 sorting, termlists, display, or other interface-related use.
1001 Implemented sorting by year.
1003 Option -d dumps records to the current log file instead of stderr.
1005 Fixes for compilation on cygwin.
1007 Z39.50 client code uses pz:elements. pz:elements was recognized in
1008 earlier Pazpar2 versions but it was not used for anything.
1010 icu_chain_test is using fgets instead of getline - fixes compilation
1013 Loosen the CCL query parsing so that Pazpar2 only returns error if _all_
1014 query conversions fail (rather than _any_). This means targets that do
1015 not support some fields are ignored in a search.
1017 --- 1.0.1 2007/07/03
1019 Improved handling of socket timeout for Z39.50 connections.
1021 Misc documentation updates and spell fixes.
1023 Debian package pazpar2 creates log rotate entry.
1025 Debian package pazpar2-apache2 reloads Apache2.
1027 jsdemo included in distribution. It illustrates the use of the js/pz2.js
1030 --- 1.0.0 2007/06/20
1032 First public release.