1 --- 1.8.2 [IN PROGRESS]
3 Remove from js/pz2.js the code that translates just two diagnostic
4 codes (1 and 2) into human-readable messages. This is no longer
5 necessary at all, as PazPar2 has been returning the message as well as
6 the code in its responses since December 2012. Fixes PAZ-978.
10 Turbomarc needs number check for date 903 map PAZ-973
12 primo-pz2.xsl creates citation rather than journal-subpart PAZ-972
14 pz2.js: on successful search, issue a "show" command only if a show
15 callback function has been installed. Fixes part of PAZ-975
19 New command=stop which stops further search&retrieval for active
22 CF/primo XSL generates {volume,issue,pages}-number that are defined
23 in default Pazpar2 service definition. PAZ-968 PAZ-970
27 Various fixes for threaded operation PAZ-960 thru PAZ-966
29 Dump main configuration file during start of Pazpar2 PAZ-957
33 Log ingest failures and record failures:
35 Clean up logging PAZ-942
36 Use session lead in more places. Log hits/records/filtered for each
37 target when fetching is complete. Log hit count when a search
38 (response) is received. Remove some less useful log messages.
40 Fix warning about about missing (internal) stylesheet PAZ-956
42 Report number of filtered records in bytarget PAZ-954
44 Cache XML documents as they appear after normalization. The key
45 for the cache is database+record offset. Cache is removed if query
46 is modified for search. This speeds up re-establishing a result set
47 for databases where new query is same previous query.
51 poll: add assert for number of FDs; abort on poll failure
55 Fix hang for 2nd use of target with unresolved DNS PAZ-949
59 Use poll rather than select for main event loop to overcome limit of
60 1024 file descriptors PAZ-947
62 Override setting with same name (do not append) PAZ-945
66 Separate package: pazpar2-xsl PAZ-932
70 Update OPAC stylesheets for availabilityDate PAZ-943
72 Fix too funny startrecs description
74 Fix broken ~ match if filter contains = PAZ-941
78 Add pz:redis option for ZOOM caching using redis. This is an alternative
79 to memcached. Requires YAZ 5.2.0 to work.
83 Re-ingest native facets PAZ-934
85 Fix medium override for solr-pz2.xsl.
89 Fix URL with leading http:// not working PAZ-933
91 Build packages for Ubuntu Trusty Tahr 14.04 LTS
93 cf.xsl: handle medium override AND md field
97 sortmap relevance always uses increasing=1. PAZ-930
99 solr-pz2.xsl: ensure medium is also applied if Solr record do not
102 Fix leak in getaddrinfo usage for HTTP listener. Not a big deal because
103 this code is only executed once.
105 Fix typos is sortmap documentation.
107 Doc: fix misplaced variablelist tag.
109 --- 1.6.39 2014/02/19
111 Doc: update WRT ICU which is configured for YAZ; not Pazpar2.
112 It's been like that since version 1.1.1 from August 2009.
114 Add support for result-set caching via memcached. See description of
115 pz:memcached. Require that Pazpar2 is using YAZ 5.0.12 or later.
117 Add support for a <metadata> container tag. Patfh from Sven Porst.
119 Add support for XInclude in main configuarion file. Patch from Sven Porst.
121 Add client_{lock,unlock} before call to non_block_events in
122 connection_continue. Problem is that if non_block_events fire records,
123 then we will not unlock client at all. And as a result, a dead-lock
126 --- 1.6.38 2014/01/07
128 Avoid removing slash and other characters for generic metadata that
129 looks like a URL (contains ://). PAZ-915
131 pz2.js: Only use XDR when doing CORS. Favor XHR in all other circumstances.
133 Cluster merge fixes. PAZ-901
135 Set client state to "working" when waiting for DNS resolver. PAZ-907
137 Log when session terminates. PAZ-905
139 Fix LSB/HS conformance for /etc/init.d/pazpar2 PAZ-904
140 Debian: add support for /etc/init.d/pazpar2 status
142 --- 1.6.37 2013/11/18
144 Fix 'Record Missing' for command=show PAZ-903
146 Preserve order of records within cluster PAZ-902
148 testing: use yaz-ztest -V if possible and use YAZ in sibling directory
151 Allow clustered records to be ingested during retrieval. PAZ-900
153 Fix void function error which cannot return a value.
155 --- 1.6.36 2013/11/11
157 SRU pz:authentication="a/b" may end up as x-username=a%2Fb PAZ-899
159 Upgrade to debhelper version 7 PAZ-898
161 Package with libyaz5 PAZ-897
163 Better error message for CCL parse errors PAZ-887
165 --- 1.6.35 2013/09/23
167 New target setting: pz:authentication_mode. PAZ-896
169 pazpar2 PRM: pazpar2 runs as user nobody. PAZ-893
171 Strip #-suffix for ZOOM URLs. PAZ-892
173 --- 1.6.34 2013/08/30
175 Fix issue with hanging show/bytarget. Could happen if new search was
176 fired with filter before show from previous show completed.
178 Add 'date' handling for solr-pz2.xsl.
180 --- 1.6.33 2013/08/13
182 pz:authentication may carry user group password. If pz:authentication
183 has at least one blank in it, that forces Pazpar2 to use idPass Z39.50
184 authentication. Two forms are allowed
187 If no blanks are present, open authentication is in use (as before).
189 Fix {prev,next}recid elements that are returned by record
190 command. These were incorrect in versions 1.6.23 thru 1.6.32.
192 --- 1.6.32 2013/06/14
194 Experimental support for snippets. If argument snippets=1 is given
195 for command record or show, the text will include <match>-tags for
196 those area that matches.
198 Fix memory leak WRT client structures (incorrect inc ref count).
200 Log when a HTTP response is serialized and the time elapsed.
202 New command, service, which returns current service XML in use for
205 --- 1.6.31 2013/05/24
207 Local limit for fields of type "generic" (ie text fields) are
208 now normalized by mergekey rule before comparison takes place.
209 Before, no normalization took place and comparsion was, thus, exact.
211 New facility: dynamic rank , which allows ranking to be changed
212 for an existing result set. The rank can be set for search or
213 show. This overrides the rank for metadata elements (which fields
216 New facility:dynamic mergekey , which allows mergekey to be changed
217 for an existing result set. The mergekey can be set for search or
220 HTTP server: host=@ listens on IPV6 and IPV4 if possible.
221 Also, allow ports to be given as names (not just integers).
222 Fix @-notation on systems that don't support IPV6 sockets.
224 --- 1.6.30 2013/04/26
226 Add MasterKey Connect configuration. Refer to section "non-standard
227 databases" for more information.
229 Allow timeformat for log to be specified with option -m (as Metaproxy
232 New Debian package pazpar2-dbg.
234 Fix NULL ptr reference of se->relevance. If a new search is initiated
235 and a CCL query fails to parse, Pazpar2 could crash.
237 Fix problem with host/port mangling in Pazpar2 HTTP server. Problem
238 existed in 1.6.29 only.
240 --- 1.6.29 2013/04/05
242 IPV6 updates. Allow IPv6 addresses for database hosts and IPv6 address
243 for HTTP server. By default the HTTP server uses IPv4 only, but that can be
244 changed by setting "host" attribute for the "listen" element.
246 Change semantics of pz:extendrecs. Allow for repeated fetches .
247 pz:extendrecs is now the number of extra records to fetch (was total
250 --- 1.6.28 2013/03/21
252 Fix hang or memory violation if show occurred before a search. (not that
253 it makes much sense to perform a show before a search).
255 --- 1.6.27 2013/03/08
257 pz2.js: Element_parseChildNodes concatenates all Text/CDATA nodes, instead
260 --- 1.6.26 2013/03/08
262 New pz:metadata attribute, empty="empty-value" for Pazpar2's
263 internal representation. With this attribute, Pazpar2 treates an empty
264 pz:metadata type as having the value for "empty" - if empty.
266 New setting, pz:extendrecs, which triggers extended fetch of records
267 for a database beyond pz:maxrecs for a show command.
269 Fix warning that was falsely issued for "missing limitmap".
271 Log message for Pazpart start/stop changed. Now using same style as
272 Metaproxy, ie Pazpar2 start SHA1 / Pazpar2 stop .
274 --- 1.6.25 2013/02/07
276 Fix hang of 2nd command=show with esn/syntax given.
278 --- 1.6.24 2013/01/18
280 New merge attribute type: 'first', which takes all metadata fields
281 from first target that returns the particular field.
283 --- 1.6.23 2013/01/02
285 Extend info command with hostname and YAZ SHA1
286 Indent results for both command stat and info.
288 Allow limit on merged content. The new configuration metadata
289 element, limitcluster, configures that a metadata element (name) be used
290 as limit name for search. Applies to the whole service (ie all targets),
291 unlike pz:limitmap which is configured per-target (database).
293 New feature: limitmap local:* matches against all metadata fields.
295 Allow repeated list in limitmap spec . Separated by comma. For
296 example: value="local:title,rpn:@attr 1=4".
298 New element <message> in bytarget response. Holds diagnostic message
299 of code (say 'Unsupported Use Attribute' for Bib-1 114).
301 Improved logging for record ingestion failures.
303 Avoid using struct icu_chain in non-YAZ_HAVE_ICU mode. In the rare case,
304 when YAZ is compiled without ICU support.
306 --- 1.6.22 2012/10/11
308 Requires YAZ-4.2.40 to support native solr support.
310 Fix and improve logic handling whether or not to re-do search on sort
311 order changes. A sort order with change in ascending/descending only
312 whould not trigger a new search, which is required for targets with
313 native sorting capabilities. Each client is now checked if instructions
314 (sortmap) exist for native sorting and only client that does requires
315 it is researched. Other clients is just re-ingesting the records,
316 they already have. The resultset is now cleared if any researching
319 Connection sharing between session has broken since version 1.6.8 with
320 introduction of logic that would minimize searching if pazpar2 could
321 detect this based on same query and limits and partly sort order.
322 This could lead to segementations violations.
324 Added a chapter in the manaul about relevance ranking.
326 --- 1.6.21 2012/09/24
328 Rank tweak: follow=number will increase mult by number if two terms
329 occur next to each other; number-1 if they are one term apart , .. 0
330 if they are number a part (all in order). Default is 0 (following
331 terms has no effect).
333 Rank tweak: lead=k will divide mult by 1 + log2(1+k*l) where k is
334 value given by lead and l is length from beginning of field where
335 term occurs (l=0 for first term, l=1 for second term, ..). Default
338 Rank tweak: length=strategy. length="linear" if mult is to be divided
339 by length (existing, default behavior), length="log" if mult is to be
340 divided by log2(1+length), length="none" if mult is not to be affected
343 --- 1.6.20 2012/09/21
345 Rank algorithm details may be printed as part of show response in
346 element <relevance_info>.. This is only printed if <rank debug="yes"/>
349 Record as returned by show/record command have a minimal indentation
350 which makes things human-readable.
352 New configuration of default sorting criteria (sort-default) in
353 service definition. If no criteria is defined it will be as before
356 Search command now supports sort parameter just as the show command.
357 If no parameter is give, it will use the service sort-default value.
359 --- 1.6.19 2012/09/18
361 Rank algorithm skips strings that gets normalized to empty string.
362 For example, & and ! could map to the empty string. The weight for
363 those terms is now 0 (as if they were not part of the query).
365 Rank algorithm does not use CCL from limitmap; only from the query
366 parameter (user query).
370 --- 1.6.18 2012/09/17
372 Rank algorithm configurable by 'rank' element inside service. So far
373 only, attribute 'cluster' is recognized. If cluster="yes", multiple
374 records inside a cluster boosts higher than single records. This
375 is default behavior and existing behavior. cluster="no" takes the
376 average score of each record in a cluster.
378 --- 1.6.17 2012/09/05
380 Fix bad re-use of connections (connections with changing proxy should not
383 --- 1.6.16 2012/08/22
385 Fix a bug introduce in 1.6.15 around the position sorting. It resetted the
386 resultset and sorting when the sort order is position. However this will be done on
387 every client poll, which will make pazpar2 continuing reset and fetching.
388 It should only be done on FIRST request where the sort order change.
390 Fix an issue on suggestion option: Also disable suggestions on empty string.
392 Clean up in turbo marc stylesheet.
394 Remove the hardcoded size of termlists.
396 --- 1.6.15 2012/06/27
398 New facility: ccldirective may be given in service definition. Allows
399 CCL parsing to be customized a bit, such as defining names of operators
402 New facility: raw record by checksum, rather than offset. The record
403 command optionally takes checksum which identifies certain record from
406 New facility: per field ranking. Rank may be given as M [F N] where
407 M is default rank and N is rank for CCL terms from field F.
409 --- 1.6.14 2012/06/04
411 Fix for IE7/8 in pz.js
413 Applied patch from Giannis Kosmas on keepAlive, which also adds keepAlive to init response.
415 Lower log level some places.
417 Remove some invalid test results.
419 --- 1.6.13 2012/05/23
421 Introducing a version=2 parameter for show, termlist and bytarget commands.
422 This enables pazpar2 to return approximation on hit and count count when
423 doing record filtering using the limit parameter on search and a
424 limitmap with a value of "local:"
426 Setting pz:xslt may embed local XSLT as an alternative to referring
428 Value is not CDATA but XML nodes embedded, so escaping is not necessary
429 but a root element *must* be present. For example:
430 <settings target="target="z3950.indexdata.com/marc">
439 Metadata field rank may given by XML internal document (pz:xslt
440 result). If rank is not given, the rank from service description is
443 Metadata field can now configured a default limitmap and facetmap.
444 Setting limitmap to "local:" would work for all kind of targets, but would
445 prob. not be the optimal solution. But at least better than the default behavior
446 of pazpar2 where no filtering is done.
448 A service definition can now also contains <set/> that defines service-wide
449 settings. These will override server-wide sets and will be overridded by
452 New setting, pz:present_chunk, that specifies number of records to fetch
453 at a time. Zero will disable chunkation; will fetch max_records at once.
455 --- 1.6.12 2012/03/14
457 Revert the format change in termlist response, that could break
458 some clients / UIs since they were expecting an (empty) element
459 if no facet values was found.
461 --- 1.6.11 2012/03/07
463 Revert the behavior of returning errors when unable to block
464 on termlist, bytarget and search, when unable to block due to
465 other block. The client will now receive a regular response,
466 but it will be logged in the server. A parameter (report) is
467 added to change behavior to return error response or WARNING
468 status message. Consider this "API" as private, as it is mostly
469 untested and could be changed in future releases.
471 Fix spell error in pz2.js fix in 1.6.10.
473 New Marc2TurboMarc.xsl (contribution from Sven Porst).
474 Can solve the missing marc21.xsl updates in some cases.
476 tmarc.xsl: Simplify the 6xx to subject-long and fix 1-based
477 substring (contribtion from Sven Porst)
479 marc21.xsl: fix 1-based substring call
481 tmarc.xsl and marc21.xsl: use 856$a as last option for electronic-text.
483 Add test_termlist_block to test suite
485 --- 1.6.10 2012/02/23
487 Fix SEGV for invalid PQFs and SRU/SOLR targets
488 Also refactor a bit the code that converts from PQF to SRU/SOLR queries.
490 Fix pz2.js: "null object" due to change in in bytarget result XML.
492 Fixes in tmarc.xsl: Subject-long shorten for extra commas only.
493 Added this normalization to the other subject-long fields (d6xx),
494 where it was missing.
496 Fixes in marc21.xsl: Updated with most of the new tmarc.xsl.
497 Still differences around medium and holdings. marc21.xsl is not
498 longer active used by Index Data, and should be considered unsupported.
499 Use tmarc.xsl instead.
503 Fix SEGV that could occur for failed connections.
507 Fix bug for command sort that could return no results for active clients
508 (from previous search). This bug was present in 1.6.6-1.6.7.
510 Fix bug in results that could include results that should have been
511 filtered out. This bug was present in 1.6.6-1.6.7.
515 Fix bug introduced in 1.6.6 where a connection re-use could stall
518 Local filtering may now specify a local metadata field, eg.
519 pz:limitmap:somefield[t]=local:otherfield
523 For search, when limit and or filtering is in place and search
524 is identical to previous search, the result set is re-used and the
525 target is not searched.
527 Limits may work perform local filtering as well, by using "local:"
532 Updated bytarget command to contain a suggestions element with misspelled
533 words and suggestions to these. pz2.js has been updated to deliver this
534 onwards as well. Only target that currently delivers this is the solr
535 client in YAZ 4.2.18.
539 New service definition element, xslt, that allows an embedded stylesheet
540 to be defined. This can be referred to from pz:xslt as an alternative to
543 New pz:sortmap:field setting for specifying hints on how to make
544 a target natively sort on a field. This is used for command=show in
545 conjunction with sort.
547 New pz:url setting for specifying the actual URL for a target. When
548 this is used the target ID is not used as URL anymore and the target ID
549 may be almost any string (not including []).
551 command=termlist without name parameter returns all termlists/facets.
552 Previously if name parameter was omitted, only "subject" was returned.
556 Make termlist sorting stable. Terms with same frequency are now sorted by
557 their display name. This makes a pretty display and improves our
558 regression test because qsort is not a stable sort.
560 New sort parameter value 'position'. The 'position' sorts merged records
561 by their original position from the remote target. This is primarily useful
562 for debugging and may be used for targets that already perform some kind
563 of relevance ranking. Note that sort by default is decreasing; so to get
564 records in their original order sort=position:1 must be used.
568 tmarc.xsl: yet another 773$g fix. Was broken in 1.6.1 as well.
570 Facility to change working directory for pazpar2 daemon. Option -wdir
571 sets working directory to dir. This facility is useful if core dumps
572 must be saved. In this case, the current working directory must be
573 writable by the running user, such as "nobody".
577 New configuration element <icu_chain> for <server>/<service> which
578 allows a named ICU rule (chain) to be defined. The names relevance,
579 sort, mergekey and facet are used for those operations. The definition
580 <icu_chain id="sort" locale="en"> .. </icu_chain>
582 <sort> <icu_chain locale="en> ... </icu_chain> </sort>
583 And so on.. for relevance, mergekey and facet as well. The latter
584 style is deprecated. The facet terms are normalized by the facet
585 rule by default. This may be changed on a metadata field basis by
586 defining the new attribute 'facetrule' for the metadata element.
588 <icu_chain id="myrule" locale="en"> ... </icu_chain>
589 <metadata name="author" termlist="yes" facetrule="myrule"/>
591 Preserve rorder for merged metadata. Fixes issue as reported by Sven
592 Porst: http://lists.indexdata.dk/pipermail/yazlist/2011-July/003230.html
594 tmarc.xsl: set journal-subpart to 773$ only.
598 Modify the behavior for the limit parameter (first defined in 1.5.7).
599 Mapping of limit searches are now defined by the new configuration item
600 pz:limitmap. Fix a dead-lock problem with the limit parameter.
602 Extend tmarc.xsl to extract 773$g data (OpenURL).
606 ICU default maps remove backquote (`).
608 Command 'search' takes limit parameter (optional). The limit parameter
609 allows a search to be limited one or more facets and the corresponding
610 values. This is for server side filtering.
612 Configure tweak: Use -lm for log(3) if needed
616 Fix a problem with skiparticle sortkey that could be completely
617 ignored (and reduced to "").
619 Fix dependency problem in pazpar2 RPM package (did not require
620 libyaz4 as it should).
624 Fix memory leak that occurred for command=termlist&name=xtargets .
626 Pazpar2 may save HTTP requests. Enabled by option -R.
630 Experimental support for DTIC DADS target. New dads-pz2.xsl.
632 Support for query_syntax (overrides the default for SRU | Z39.50)
634 Support for extraArgs (ZOOM "extraArgs" option) for targets
636 New commands: status-server and status-session
640 Fix for threaded runs: Client now have a copy of the database URL,
641 which can used after the database has been release from the client.
642 This makes the logging in the connection idle timeout of the client nicer (no NOURL) and should be thread-safe.
644 tmarc.xsl: Add journal-title-abbrev and full text.
646 cf.xsl: new fields: isbn, issn, journaltitle, volume, issue
648 Fix for cmd=record before search.
650 Session Logging clean up.
652 Fix wrong termlist factor when maxrecs is different from 100.
656 Fix missing pz:termlist_term_factor in settings.c messed up pz:preferred.
657 Term factor is default enabled but can be diseabled by
658 pz:termlist_term_factor=0
662 Add scaling of facet count. Currently always enabled, needs fixing.
663 Allow user-defined info for target suffix. This has no meaning in
664 Pazpar2 except to distinguish targets from each other. The suffix
665 data begins with #. For example z3950.indexdata.com/gils#Mydata
667 Added exact-match recordfilter; format name=value
671 SOLR support. Pazpar2 may operate as web service client for SOLR.
675 Fix for show command and block=1 (dead lock). Bug was introduced in
680 New RPM packages: pazpar2, pazpar2-js, pazpar2-doc. These have been
681 tested on CentOS 5.5 only.
685 Fix problem with result sets being removed from a client session
686 if the connection for it was resused by another session. Bug #3489.
688 New iphone UI for Pazpar2 (www/iphone).
692 Fixes for threaded operation.
694 New stylesheets for TurboMARC: tmarc.xsl and opac_turbomarc.xsl.
696 New example services in etc/services in source. In the Debian packages
697 these are located in /etc/pazpar2/services-available
699 Threaded mode operational on Windows. Requires Windows 7 or Windows
702 Default value of setting pz:max_connections is 0 which means that there
703 is no limit on number of connections.
707 Pazpar2 may operate in threaded mode. Enabled by element threads in
708 the configuration. See pazpar2_conf for details.
710 New setting setting: pz:max_connections. Setting pz:max_connections is
711 a limit of number of sockets to a host. When this limit is reached,
712 Pazpar2 will wait up to 5 seconds for a connection to becomes available.
713 The client will be marked Client_Error when it can not be searched
714 (other clients in a session may work). If pz:max_connections is not set
715 for a target, a value of 30 will be used. Note: the pz:max_connections
716 will only work in threaded mode.
718 pz2.js: JSON support for show.
720 Debian package: Enable default service, default.xml, before starting
721 Pazpar2 only if there is no service already in /etc/pazpar2/services-enabled.
725 Debian version depends on on libyaz4. Note that Pazpar2 will still
726 compile from source with YAZ 3.
728 Split services into separate files. The example configuration file
729 pazpar2.cfg.dist now includes a default service default.xml (part of
730 etc). And default.xml includes settings/edu.xml. The default.xml file,
731 not to be confused with settings/defaults.xml, is a template for jsdemo
732 and other services. The Debian package installs /etc/pazpar2/server.xml
733 which is now the main pazpar2 configuration (used to be called pazpar2.cfg).
734 server.xml includes services from /etc/pazpar2/services-enabled/*.xml .
735 The default.xml (from etc) is installed in /etc/pazpar2/services-available
736 and a symlink to it is created from services-enabled. The default.xml
737 service is unnamed and, thus, will be used by jsdemo and test1.
739 New setting pz:negotiation_charset. Patch from Andrei V. Toutoukine. The
740 new setting pz:negotiation_charset specifies character set for Z39.50 Init.
744 Support for additional fields in cf.xsl and pazpar2.conf.dist:
745 publisher, available, due, location (=locallocation), callno
746 (=callnumber), thumburl and score.
748 Describe pz:xslt and the auto setting.
750 Move mergekey definition away from the normalization stylesheets and
751 define a mergekey common for all target types in pazpar2.cfg.
753 Code update: Use the Odr_int type for hit counts. This is part of
754 YAZ 3.0.47 and later and so configure checks for that.
758 Metadata attribute 'skiparticle' also works for ICU based
759 normalization. (was only working for the non-ICU/ASCII before).
761 Command bytarget with argument settings=1 will show settings per
762 target.. This is to be able to verify correct settings and be able to
763 test that they are correct. The database settings array size is now
764 also stored.. Problems with database settings array is that if not
765 careful it will be too small (smaller than dictionary per-service
768 Make record list sorting stable by comparing mergekey for records if
769 relevance/title or other sorting criteria all match. This is merely to
770 ensure that our regressions tests works (reproducible output).
772 Relevance calculation changes: use a different denominator (length) for
773 per-field relevance scoring.. Instead of length of all ranked fields we
774 now use length of individual fields (as if they were individual "free"
775 text fields). This will ensure that documents with a long field with no
776 match (say description) will not "hurt" a title match.
778 Diagnostic member was not set on connection error. Fixed
782 Command search takes two optional parameters, startecs and maxrecs,
783 that specifies the start offset (0, 1, ...) and maximum number of records
784 to fetch for each target.
786 XSLTs + MARC maps are cached within a session so we don't re-parse
787 them over and over again. Even for a session with a single search
788 there's much to be gained because many targets use the same
791 The metadata attribute 'mergekey' now takes one of three values 'no',
792 'required', 'optional' . And the resulting mergekey from metadata
793 is now ordered in the same way as metadata in the service definition.
794 Older Pazpar2 version use the order in which metadata appeared in a
797 The search argument 'filter' now offers a new operator ~ which does a
798 substring match. The = operator works as before: string match for
799 anything but pz:id, or target match for pz:id.
801 New setting pz:recordfilter. The value of this setting takes the
802 form name[~value]. This setting makes Pazpar2 ignore all retrieved
803 records that do not have the metadata element name with value substring
806 Pazpar2 allows YAZ log level to be set (option -v).
810 For WS responses Pazpar2 creates XML header. Exception: raw record.
812 Setting XML files are now stored in etc/settings instead of etc. This
813 reflects the layout with the Debian package layout.
815 Settings may be posted for command=settings. The POSTed settings must
816 have root element 'settings' like regular setting files. In order to be
817 recognized, the POST request must use Content-Type=text/xml.
819 A service may be posted for command=init. This service will be used
820 during the session. The service may have its own target settings,
821 ICU config, timeout, etc. In order to be recognized, the POST request
822 must use Content-Type=text/xml.
824 Timeout values may be given per-service. That's element 'timeout'
825 which takes three attribute values (a subset may be given): 'session',
826 'z3950_operation', 'z3950_session'. Option -T is no longer supported
827 - used to specify session timeout.
829 Option -t tests the Pazpar2 configuration and returns exit code
830 (0=success, non-zero=failure). In previous version of Pazpar2, -t
831 specified local settings.
833 In version 1.2.0 the configuration file - after include processing -
834 was dumped to stdout. Now, the configuration is only dumped to the
835 yaz log file if option -d is given.
839 Configuration may now have multiple server areas. This means that a
840 Pazpar2 instance may listen on multiple ports. Virtual hosting is not
841 yet supported - on a server basis. Configuration may also have multiple
842 services .. That is repeating service elements inside a server. Each
843 has an attribute 'id' which serves as service ID. This ID in turn may
844 be used in a Pazpar2 session, by specifying parameter service=ID for
845 command init. There can be at most one unnamed service inside a server
846 which can be referred to by not specifying an service ID for command
847 init (backwards compatible). In order to partition multiple servers and
848 services a new include directive has been added. This takes an attribute
849 'src' which specifies one or more sub-files. For example to include
850 service files, one might use:
851 <server >.. <include src=/"etc/pazpar2/conf.d/*.xml"/> .. </server>.
852 It is the intention that that completely makes the settings directive
855 Fix problem where the record command would wait forever if there were
856 no targets to wait for (activeclients == 0).
860 One result set is created per session (last search) rather than for
861 each connection which happen to be shared (bug #3009).
863 marc21 stylesheets changed for efficiency.
867 Session timeout may be specified on the command-line as option -T.
869 Pazpar2 may now be operated in a no-merged mode for records.. All records
870 will be considered unique. This mode is enabled if no mergekey is
871 generated by the normalization stylesheet (pz:xslt).
873 Pazpar2 caches original records from each target and the 'record' command
874 with offset returns the original record if 'syntax' and 'esn' are NOT
875 specified. This speeds up retrieval of original records but also means
876 that Pazpar2 uses more memory. The cached records will be freed when the
877 session terminates or a new search is executed.
879 Pazpar2 no longer uses its own ICU wrapper. Instead the ICU wrapper
880 library part of YAZ is used.
882 Added SRU client support.
884 Automatically computes pz:nativesyntax if not provided. Works for XML and
887 --- 1.0.13 2008/11/24
889 Command bytarget returns name of target (if defined).
891 --- 1.0.12 2008/11/04
893 Fixed bug #2021.. location now holds all brief elements.
895 --- 1.0.11 2008/10/15
897 Fixed check for application/x-www-form-urlencoded parameters.
899 --- 1.0.10 2008/10/14
901 Fixes for IE in pz2.js.
903 Fixed bug #2021: non-merged, brief meta data NOT included for command=show.
907 Changed the JS library pz2.js to use POST for long URL (+ params).
909 Added installation instructions for Windows. Note: NT services is
910 NOT available until we make a new release of YAZ.
912 Preserve order of repeated metadata fields (they were reversed before).
914 More MARC21 information extracted for metadata.
918 Fixed bug #1162: HTML entities are not escaped properly.
920 Native Windows port of Pazpar2. Makefile for Visual Studio provided.
924 Marc21 stylesheet updated to reflect multiple full text fields
928 Fixed bug in pz2.js WRT DOMElement attributes on IE.
930 Fixed bug 2100: Database wildcards not working
934 Added support for retrieval of records in binary.
936 Fixed bug 1794: Pazpar2 does not return valid XML.
938 Deal with ICU not returning sortkey (resulted in SEGV before).
942 JavaScript library pzw2.js throws error if WS response (from Pazpar2 or
943 other) is malformed (non-wellformed XML or missing Pazpar2 OK status).
945 Improved diagnostics when Pazpar2 HTTP decoding fails.
947 Pazpar2 requests may be POSTed as using Content-Type
948 application/x-www-form-urlencoded.
950 Pazpar2 honors LF in HTTP headers.
952 Handle targets that handle negative hit counts (should not happen, but it
957 ICU is used for tokenization and normalization of the following: mergekey,
958 sorting, relevance terms.
960 Debian package now enables ICU tokenization and normalization by default.
964 Exposed user setting values (i.e. non-pz: names) to the record systems in two
965 ways: Either as parameters to the normalization stylesheets (which would allow the
966 programmer to postprocess or use the values in any way) or after the normalization
967 step, in which case values are made part of the normalized record (and available for
968 sorting, termlists, display, or other interface-related use.
970 Implemented sorting by year.
972 Option -d dumps records to the current log file instead of stderr.
974 Fixes for compilation on cygwin.
976 Z39.50 client code uses pz:elements. pz:elements was recognized in
977 earlier Pazpar2 versions but it was not used for anything.
979 icu_chain_test is using fgets instead of getline - fixes compilation
982 Loosen the CCL query parsing so that Pazpar2 only returns error if _all_
983 query conversions fail (rather than _any_). This means targets that do
984 not support some fields are ignored in a search.
988 Improved handling of socket timeout for Z39.50 connections.
990 Misc documentation updates and spell fixes.
992 Debian package pazpar2 creates log rotate entry.
994 Debian package pazpar2-apache2 reloads Apache2.
996 jsdemo included in distribution. It illustrates the use of the js/pz2.js
1001 First public release.