3 sortmap relevance always uses increasing=1. PAZ-930
5 solr-pz2.xsl: ensure medium is also applied if Solr record do not
8 Fix leak in getaddrinfo usage for HTTP listener. Not a big deal because
9 this code is only executed once.
11 Fix typos is sortmap documentation.
13 Doc: fix misplaced variablelist tag.
17 Doc: update WRT ICU which is configured for YAZ; not Pazpar2.
18 It's been like that since version 1.1.1 from August 2009.
20 Add support for result-set caching via memcached. See description of
21 pz:memcached. Require that Pazpar2 is using YAZ 5.0.12 or later.
23 Add support for a <metadata> container tag. Patfh from Sven Porst.
25 Add support for XInclude in main configuarion file. Patch from Sven Porst.
27 Add client_{lock,unlock} before call to non_block_events in
28 connection_continue. Problem is that if non_block_events fire records,
29 then we will not unlock client at all. And as a result, a dead-lock
34 Avoid removing slash and other characters for generic metadata that
35 looks like a URL (contains ://). PAZ-915
37 pz2.js: Only use XDR when doing CORS. Favor XHR in all other circumstances.
39 Cluster merge fixes. PAZ-901
41 Set client state to "working" when waiting for DNS resolver. PAZ-907
43 Log when session terminates. PAZ-905
45 Fix LSB/HS conformance for /etc/init.d/pazpar2 PAZ-904
46 Debian: add support for /etc/init.d/pazpar2 status
50 Fix 'Record Missing' for command=show PAZ-903
52 Preserve order of records within cluster PAZ-902
54 testing: use yaz-ztest -V if possible and use YAZ in sibling directory
57 Allow clustered records to be ingested during retrieval. PAZ-900
59 Fix void function error which cannot return a value.
63 SRU pz:authentication="a/b" may end up as x-username=a%2Fb PAZ-899
65 Upgrade to debhelper version 7 PAZ-898
67 Package with libyaz5 PAZ-897
69 Better error message for CCL parse errors PAZ-887
73 New target setting: pz:authentication_mode. PAZ-896
75 pazpar2 PRM: pazpar2 runs as user nobody. PAZ-893
77 Strip #-suffix for ZOOM URLs. PAZ-892
81 Fix issue with hanging show/bytarget. Could happen if new search was
82 fired with filter before show from previous show completed.
84 Add 'date' handling for solr-pz2.xsl.
88 pz:authentication may carry user group password. If pz:authentication
89 has at least one blank in it, that forces Pazpar2 to use idPass Z39.50
90 authentication. Two forms are allowed
93 If no blanks are present, open authentication is in use (as before).
95 Fix {prev,next}recid elements that are returned by record
96 command. These were incorrect in versions 1.6.23 thru 1.6.32.
100 Experimental support for snippets. If argument snippets=1 is given
101 for command record or show, the text will include <match>-tags for
102 those area that matches.
104 Fix memory leak WRT client structures (incorrect inc ref count).
106 Log when a HTTP response is serialized and the time elapsed.
108 New command, service, which returns current service XML in use for
111 --- 1.6.31 2013/05/24
113 Local limit for fields of type "generic" (ie text fields) are
114 now normalized by mergekey rule before comparison takes place.
115 Before, no normalization took place and comparsion was, thus, exact.
117 New facility: dynamic rank , which allows ranking to be changed
118 for an existing result set. The rank can be set for search or
119 show. This overrides the rank for metadata elements (which fields
122 New facility:dynamic mergekey , which allows mergekey to be changed
123 for an existing result set. The mergekey can be set for search or
126 HTTP server: host=@ listens on IPV6 and IPV4 if possible.
127 Also, allow ports to be given as names (not just integers).
128 Fix @-notation on systems that don't support IPV6 sockets.
130 --- 1.6.30 2013/04/26
132 Add MasterKey Connect configuration. Refer to section "non-standard
133 databases" for more information.
135 Allow timeformat for log to be specified with option -m (as Metaproxy
138 New Debian package pazpar2-dbg.
140 Fix NULL ptr reference of se->relevance. If a new search is initiated
141 and a CCL query fails to parse, Pazpar2 could crash.
143 Fix problem with host/port mangling in Pazpar2 HTTP server. Problem
144 existed in 1.6.29 only.
146 --- 1.6.29 2013/04/05
148 IPV6 updates. Allow IPv6 addresses for database hosts and IPv6 address
149 for HTTP server. By default the HTTP server uses IPv4 only, but that can be
150 changed by setting "host" attribute for the "listen" element.
152 Change semantics of pz:extendrecs. Allow for repeated fetches .
153 pz:extendrecs is now the number of extra records to fetch (was total
156 --- 1.6.28 2013/03/21
158 Fix hang or memory violation if show occurred before a search. (not that
159 it makes much sense to perform a show before a search).
161 --- 1.6.27 2013/03/08
163 pz2.js: Element_parseChildNodes concatenates all Text/CDATA nodes, instead
166 --- 1.6.26 2013/03/08
168 New pz:metadata attribute, empty="empty-value" for Pazpar2's
169 internal representation. With this attribute, Pazpar2 treates an empty
170 pz:metadata type as having the value for "empty" - if empty.
172 New setting, pz:extendrecs, which triggers extended fetch of records
173 for a database beyond pz:maxrecs for a show command.
175 Fix warning that was falsely issued for "missing limitmap".
177 Log message for Pazpart start/stop changed. Now using same style as
178 Metaproxy, ie Pazpar2 start SHA1 / Pazpar2 stop .
180 --- 1.6.25 2013/02/07
182 Fix hang of 2nd command=show with esn/syntax given.
184 --- 1.6.24 2013/01/18
186 New merge attribute type: 'first', which takes all metadata fields
187 from first target that returns the particular field.
189 --- 1.6.23 2013/01/02
191 Extend info command with hostname and YAZ SHA1
192 Indent results for both command stat and info.
194 Allow limit on merged content. The new configuration metadata
195 element, limitcluster, configures that a metadata element (name) be used
196 as limit name for search. Applies to the whole service (ie all targets),
197 unlike pz:limitmap which is configured per-target (database).
199 New feature: limitmap local:* matches against all metadata fields.
201 Allow repeated list in limitmap spec . Separated by comma. For
202 example: value="local:title,rpn:@attr 1=4".
204 New element <message> in bytarget response. Holds diagnostic message
205 of code (say 'Unsupported Use Attribute' for Bib-1 114).
207 Improved logging for record ingestion failures.
209 Avoid using struct icu_chain in non-YAZ_HAVE_ICU mode. In the rare case,
210 when YAZ is compiled without ICU support.
212 --- 1.6.22 2012/10/11
214 Requires YAZ-4.2.40 to support native solr support.
216 Fix and improve logic handling whether or not to re-do search on sort
217 order changes. A sort order with change in ascending/descending only
218 whould not trigger a new search, which is required for targets with
219 native sorting capabilities. Each client is now checked if instructions
220 (sortmap) exist for native sorting and only client that does requires
221 it is researched. Other clients is just re-ingesting the records,
222 they already have. The resultset is now cleared if any researching
225 Connection sharing between session has broken since version 1.6.8 with
226 introduction of logic that would minimize searching if pazpar2 could
227 detect this based on same query and limits and partly sort order.
228 This could lead to segementations violations.
230 Added a chapter in the manaul about relevance ranking.
232 --- 1.6.21 2012/09/24
234 Rank tweak: follow=number will increase mult by number if two terms
235 occur next to each other; number-1 if they are one term apart , .. 0
236 if they are number a part (all in order). Default is 0 (following
237 terms has no effect).
239 Rank tweak: lead=k will divide mult by 1 + log2(1+k*l) where k is
240 value given by lead and l is length from beginning of field where
241 term occurs (l=0 for first term, l=1 for second term, ..). Default
244 Rank tweak: length=strategy. length="linear" if mult is to be divided
245 by length (existing, default behavior), length="log" if mult is to be
246 divided by log2(1+length), length="none" if mult is not to be affected
249 --- 1.6.20 2012/09/21
251 Rank algorithm details may be printed as part of show response in
252 element <relevance_info>.. This is only printed if <rank debug="yes"/>
255 Record as returned by show/record command have a minimal indentation
256 which makes things human-readable.
258 New configuration of default sorting criteria (sort-default) in
259 service definition. If no criteria is defined it will be as before
262 Search command now supports sort parameter just as the show command.
263 If no parameter is give, it will use the service sort-default value.
265 --- 1.6.19 2012/09/18
267 Rank algorithm skips strings that gets normalized to empty string.
268 For example, & and ! could map to the empty string. The weight for
269 those terms is now 0 (as if they were not part of the query).
271 Rank algorithm does not use CCL from limitmap; only from the query
272 parameter (user query).
276 --- 1.6.18 2012/09/17
278 Rank algorithm configurable by 'rank' element inside service. So far
279 only, attribute 'cluster' is recognized. If cluster="yes", multiple
280 records inside a cluster boosts higher than single records. This
281 is default behavior and existing behavior. cluster="no" takes the
282 average score of each record in a cluster.
284 --- 1.6.17 2012/09/05
286 Fix bad re-use of connections (connections with changing proxy should not
289 --- 1.6.16 2012/08/22
291 Fix a bug introduce in 1.6.15 around the position sorting. It resetted the
292 resultset and sorting when the sort order is position. However this will be done on
293 every client poll, which will make pazpar2 continuing reset and fetching.
294 It should only be done on FIRST request where the sort order change.
296 Fix an issue on suggestion option: Also disable suggestions on empty string.
298 Clean up in turbo marc stylesheet.
300 Remove the hardcoded size of termlists.
302 --- 1.6.15 2012/06/27
304 New facility: ccldirective may be given in service definition. Allows
305 CCL parsing to be customized a bit, such as defining names of operators
308 New facility: raw record by checksum, rather than offset. The record
309 command optionally takes checksum which identifies certain record from
312 New facility: per field ranking. Rank may be given as M [F N] where
313 M is default rank and N is rank for CCL terms from field F.
315 --- 1.6.14 2012/06/04
317 Fix for IE7/8 in pz.js
319 Applied patch from Giannis Kosmas on keepAlive, which also adds keepAlive to init response.
321 Lower log level some places.
323 Remove some invalid test results.
325 --- 1.6.13 2012/05/23
327 Introducing a version=2 parameter for show, termlist and bytarget commands.
328 This enables pazpar2 to return approximation on hit and count count when
329 doing record filtering using the limit parameter on search and a
330 limitmap with a value of "local:"
332 Setting pz:xslt may embed local XSLT as an alternative to referring
334 Value is not CDATA but XML nodes embedded, so escaping is not necessary
335 but a root element *must* be present. For example:
336 <settings target="target="z3950.indexdata.com/marc">
345 Metadata field rank may given by XML internal document (pz:xslt
346 result). If rank is not given, the rank from service description is
349 Metadata field can now configured a default limitmap and facetmap.
350 Setting limitmap to "local:" would work for all kind of targets, but would
351 prob. not be the optimal solution. But at least better than the default behavior
352 of pazpar2 where no filtering is done.
354 A service definition can now also contains <set/> that defines service-wide
355 settings. These will override server-wide sets and will be overridded by
358 New setting, pz:present_chunk, that specifies number of records to fetch
359 at a time. Zero will disable chunkation; will fetch max_records at once.
361 --- 1.6.12 2012/03/14
363 Revert the format change in termlist response, that could break
364 some clients / UIs since they were expecting an (empty) element
365 if no facet values was found.
367 --- 1.6.11 2012/03/07
369 Revert the behavior of returning errors when unable to block
370 on termlist, bytarget and search, when unable to block due to
371 other block. The client will now receive a regular response,
372 but it will be logged in the server. A parameter (report) is
373 added to change behavior to return error response or WARNING
374 status message. Consider this "API" as private, as it is mostly
375 untested and could be changed in future releases.
377 Fix spell error in pz2.js fix in 1.6.10.
379 New Marc2TurboMarc.xsl (contribution from Sven Porst).
380 Can solve the missing marc21.xsl updates in some cases.
382 tmarc.xsl: Simplify the 6xx to subject-long and fix 1-based
383 substring (contribtion from Sven Porst)
385 marc21.xsl: fix 1-based substring call
387 tmarc.xsl and marc21.xsl: use 856$a as last option for electronic-text.
389 Add test_termlist_block to test suite
391 --- 1.6.10 2012/02/23
393 Fix SEGV for invalid PQFs and SRU/SOLR targets
394 Also refactor a bit the code that converts from PQF to SRU/SOLR queries.
396 Fix pz2.js: "null object" due to change in in bytarget result XML.
398 Fixes in tmarc.xsl: Subject-long shorten for extra commas only.
399 Added this normalization to the other subject-long fields (d6xx),
400 where it was missing.
402 Fixes in marc21.xsl: Updated with most of the new tmarc.xsl.
403 Still differences around medium and holdings. marc21.xsl is not
404 longer active used by Index Data, and should be considered unsupported.
405 Use tmarc.xsl instead.
409 Fix SEGV that could occur for failed connections.
413 Fix bug for command sort that could return no results for active clients
414 (from previous search). This bug was present in 1.6.6-1.6.7.
416 Fix bug in results that could include results that should have been
417 filtered out. This bug was present in 1.6.6-1.6.7.
421 Fix bug introduced in 1.6.6 where a connection re-use could stall
424 Local filtering may now specify a local metadata field, eg.
425 pz:limitmap:somefield[t]=local:otherfield
429 For search, when limit and or filtering is in place and search
430 is identical to previous search, the result set is re-used and the
431 target is not searched.
433 Limits may work perform local filtering as well, by using "local:"
438 Updated bytarget command to contain a suggestions element with misspelled
439 words and suggestions to these. pz2.js has been updated to deliver this
440 onwards as well. Only target that currently delivers this is the solr
441 client in YAZ 4.2.18.
445 New service definition element, xslt, that allows an embedded stylesheet
446 to be defined. This can be referred to from pz:xslt as an alternative to
449 New pz:sortmap:field setting for specifying hints on how to make
450 a target natively sort on a field. This is used for command=show in
451 conjunction with sort.
453 New pz:url setting for specifying the actual URL for a target. When
454 this is used the target ID is not used as URL anymore and the target ID
455 may be almost any string (not including []).
457 command=termlist without name parameter returns all termlists/facets.
458 Previously if name parameter was omitted, only "subject" was returned.
462 Make termlist sorting stable. Terms with same frequency are now sorted by
463 their display name. This makes a pretty display and improves our
464 regression test because qsort is not a stable sort.
466 New sort parameter value 'position'. The 'position' sorts merged records
467 by their original position from the remote target. This is primarily useful
468 for debugging and may be used for targets that already perform some kind
469 of relevance ranking. Note that sort by default is decreasing; so to get
470 records in their original order sort=position:1 must be used.
474 tmarc.xsl: yet another 773$g fix. Was broken in 1.6.1 as well.
476 Facility to change working directory for pazpar2 daemon. Option -wdir
477 sets working directory to dir. This facility is useful if core dumps
478 must be saved. In this case, the current working directory must be
479 writable by the running user, such as "nobody".
483 New configuration element <icu_chain> for <server>/<service> which
484 allows a named ICU rule (chain) to be defined. The names relevance,
485 sort, mergekey and facet are used for those operations. The definition
486 <icu_chain id="sort" locale="en"> .. </icu_chain>
488 <sort> <icu_chain locale="en> ... </icu_chain> </sort>
489 And so on.. for relevance, mergekey and facet as well. The latter
490 style is deprecated. The facet terms are normalized by the facet
491 rule by default. This may be changed on a metadata field basis by
492 defining the new attribute 'facetrule' for the metadata element.
494 <icu_chain id="myrule" locale="en"> ... </icu_chain>
495 <metadata name="author" termlist="yes" facetrule="myrule"/>
497 Preserve rorder for merged metadata. Fixes issue as reported by Sven
498 Porst: http://lists.indexdata.dk/pipermail/yazlist/2011-July/003230.html
500 tmarc.xsl: set journal-subpart to 773$ only.
504 Modify the behavior for the limit parameter (first defined in 1.5.7).
505 Mapping of limit searches are now defined by the new configuration item
506 pz:limitmap. Fix a dead-lock problem with the limit parameter.
508 Extend tmarc.xsl to extract 773$g data (OpenURL).
512 ICU default maps remove backquote (`).
514 Command 'search' takes limit parameter (optional). The limit parameter
515 allows a search to be limited one or more facets and the corresponding
516 values. This is for server side filtering.
518 Configure tweak: Use -lm for log(3) if needed
522 Fix a problem with skiparticle sortkey that could be completely
523 ignored (and reduced to "").
525 Fix dependency problem in pazpar2 RPM package (did not require
526 libyaz4 as it should).
530 Fix memory leak that occurred for command=termlist&name=xtargets .
532 Pazpar2 may save HTTP requests. Enabled by option -R.
536 Experimental support for DTIC DADS target. New dads-pz2.xsl.
538 Support for query_syntax (overrides the default for SRU | Z39.50)
540 Support for extraArgs (ZOOM "extraArgs" option) for targets
542 New commands: status-server and status-session
546 Fix for threaded runs: Client now have a copy of the database URL,
547 which can used after the database has been release from the client.
548 This makes the logging in the connection idle timeout of the client nicer (no NOURL) and should be thread-safe.
550 tmarc.xsl: Add journal-title-abbrev and full text.
552 cf.xsl: new fields: isbn, issn, journaltitle, volume, issue
554 Fix for cmd=record before search.
556 Session Logging clean up.
558 Fix wrong termlist factor when maxrecs is different from 100.
562 Fix missing pz:termlist_term_factor in settings.c messed up pz:preferred.
563 Term factor is default enabled but can be diseabled by
564 pz:termlist_term_factor=0
568 Add scaling of facet count. Currently always enabled, needs fixing.
569 Allow user-defined info for target suffix. This has no meaning in
570 Pazpar2 except to distinguish targets from each other. The suffix
571 data begins with #. For example z3950.indexdata.com/gils#Mydata
573 Added exact-match recordfilter; format name=value
577 SOLR support. Pazpar2 may operate as web service client for SOLR.
581 Fix for show command and block=1 (dead lock). Bug was introduced in
586 New RPM packages: pazpar2, pazpar2-js, pazpar2-doc. These have been
587 tested on CentOS 5.5 only.
591 Fix problem with result sets being removed from a client session
592 if the connection for it was resused by another session. Bug #3489.
594 New iphone UI for Pazpar2 (www/iphone).
598 Fixes for threaded operation.
600 New stylesheets for TurboMARC: tmarc.xsl and opac_turbomarc.xsl.
602 New example services in etc/services in source. In the Debian packages
603 these are located in /etc/pazpar2/services-available
605 Threaded mode operational on Windows. Requires Windows 7 or Windows
608 Default value of setting pz:max_connections is 0 which means that there
609 is no limit on number of connections.
613 Pazpar2 may operate in threaded mode. Enabled by element threads in
614 the configuration. See pazpar2_conf for details.
616 New setting setting: pz:max_connections. Setting pz:max_connections is
617 a limit of number of sockets to a host. When this limit is reached,
618 Pazpar2 will wait up to 5 seconds for a connection to becomes available.
619 The client will be marked Client_Error when it can not be searched
620 (other clients in a session may work). If pz:max_connections is not set
621 for a target, a value of 30 will be used. Note: the pz:max_connections
622 will only work in threaded mode.
624 pz2.js: JSON support for show.
626 Debian package: Enable default service, default.xml, before starting
627 Pazpar2 only if there is no service already in /etc/pazpar2/services-enabled.
631 Debian version depends on on libyaz4. Note that Pazpar2 will still
632 compile from source with YAZ 3.
634 Split services into separate files. The example configuration file
635 pazpar2.cfg.dist now includes a default service default.xml (part of
636 etc). And default.xml includes settings/edu.xml. The default.xml file,
637 not to be confused with settings/defaults.xml, is a template for jsdemo
638 and other services. The Debian package installs /etc/pazpar2/server.xml
639 which is now the main pazpar2 configuration (used to be called pazpar2.cfg).
640 server.xml includes services from /etc/pazpar2/services-enabled/*.xml .
641 The default.xml (from etc) is installed in /etc/pazpar2/services-available
642 and a symlink to it is created from services-enabled. The default.xml
643 service is unnamed and, thus, will be used by jsdemo and test1.
645 New setting pz:negotiation_charset. Patch from Andrei V. Toutoukine. The
646 new setting pz:negotiation_charset specifies character set for Z39.50 Init.
650 Support for additional fields in cf.xsl and pazpar2.conf.dist:
651 publisher, available, due, location (=locallocation), callno
652 (=callnumber), thumburl and score.
654 Describe pz:xslt and the auto setting.
656 Move mergekey definition away from the normalization stylesheets and
657 define a mergekey common for all target types in pazpar2.cfg.
659 Code update: Use the Odr_int type for hit counts. This is part of
660 YAZ 3.0.47 and later and so configure checks for that.
664 Metadata attribute 'skiparticle' also works for ICU based
665 normalization. (was only working for the non-ICU/ASCII before).
667 Command bytarget with argument settings=1 will show settings per
668 target.. This is to be able to verify correct settings and be able to
669 test that they are correct. The database settings array size is now
670 also stored.. Problems with database settings array is that if not
671 careful it will be too small (smaller than dictionary per-service
674 Make record list sorting stable by comparing mergekey for records if
675 relevance/title or other sorting criteria all match. This is merely to
676 ensure that our regressions tests works (reproducible output).
678 Relevance calculation changes: use a different denominator (length) for
679 per-field relevance scoring.. Instead of length of all ranked fields we
680 now use length of individual fields (as if they were individual "free"
681 text fields). This will ensure that documents with a long field with no
682 match (say description) will not "hurt" a title match.
684 Diagnostic member was not set on connection error. Fixed
688 Command search takes two optional parameters, startecs and maxrecs,
689 that specifies the start offset (0, 1, ...) and maximum number of records
690 to fetch for each target.
692 XSLTs + MARC maps are cached within a session so we don't re-parse
693 them over and over again. Even for a session with a single search
694 there's much to be gained because many targets use the same
697 The metadata attribute 'mergekey' now takes one of three values 'no',
698 'required', 'optional' . And the resulting mergekey from metadata
699 is now ordered in the same way as metadata in the service definition.
700 Older Pazpar2 version use the order in which metadata appeared in a
703 The search argument 'filter' now offers a new operator ~ which does a
704 substring match. The = operator works as before: string match for
705 anything but pz:id, or target match for pz:id.
707 New setting pz:recordfilter. The value of this setting takes the
708 form name[~value]. This setting makes Pazpar2 ignore all retrieved
709 records that do not have the metadata element name with value substring
712 Pazpar2 allows YAZ log level to be set (option -v).
716 For WS responses Pazpar2 creates XML header. Exception: raw record.
718 Setting XML files are now stored in etc/settings instead of etc. This
719 reflects the layout with the Debian package layout.
721 Settings may be posted for command=settings. The POSTed settings must
722 have root element 'settings' like regular setting files. In order to be
723 recognized, the POST request must use Content-Type=text/xml.
725 A service may be posted for command=init. This service will be used
726 during the session. The service may have its own target settings,
727 ICU config, timeout, etc. In order to be recognized, the POST request
728 must use Content-Type=text/xml.
730 Timeout values may be given per-service. That's element 'timeout'
731 which takes three attribute values (a subset may be given): 'session',
732 'z3950_operation', 'z3950_session'. Option -T is no longer supported
733 - used to specify session timeout.
735 Option -t tests the Pazpar2 configuration and returns exit code
736 (0=success, non-zero=failure). In previous version of Pazpar2, -t
737 specified local settings.
739 In version 1.2.0 the configuration file - after include processing -
740 was dumped to stdout. Now, the configuration is only dumped to the
741 yaz log file if option -d is given.
745 Configuration may now have multiple server areas. This means that a
746 Pazpar2 instance may listen on multiple ports. Virtual hosting is not
747 yet supported - on a server basis. Configuration may also have multiple
748 services .. That is repeating service elements inside a server. Each
749 has an attribute 'id' which serves as service ID. This ID in turn may
750 be used in a Pazpar2 session, by specifying parameter service=ID for
751 command init. There can be at most one unnamed service inside a server
752 which can be referred to by not specifying an service ID for command
753 init (backwards compatible). In order to partition multiple servers and
754 services a new include directive has been added. This takes an attribute
755 'src' which specifies one or more sub-files. For example to include
756 service files, one might use:
757 <server >.. <include src=/"etc/pazpar2/conf.d/*.xml"/> .. </server>.
758 It is the intention that that completely makes the settings directive
761 Fix problem where the record command would wait forever if there were
762 no targets to wait for (activeclients == 0).
766 One result set is created per session (last search) rather than for
767 each connection which happen to be shared (bug #3009).
769 marc21 stylesheets changed for efficiency.
773 Session timeout may be specified on the command-line as option -T.
775 Pazpar2 may now be operated in a no-merged mode for records.. All records
776 will be considered unique. This mode is enabled if no mergekey is
777 generated by the normalization stylesheet (pz:xslt).
779 Pazpar2 caches original records from each target and the 'record' command
780 with offset returns the original record if 'syntax' and 'esn' are NOT
781 specified. This speeds up retrieval of original records but also means
782 that Pazpar2 uses more memory. The cached records will be freed when the
783 session terminates or a new search is executed.
785 Pazpar2 no longer uses its own ICU wrapper. Instead the ICU wrapper
786 library part of YAZ is used.
788 Added SRU client support.
790 Automatically computes pz:nativesyntax if not provided. Works for XML and
793 --- 1.0.13 2008/11/24
795 Command bytarget returns name of target (if defined).
797 --- 1.0.12 2008/11/04
799 Fixed bug #2021.. location now holds all brief elements.
801 --- 1.0.11 2008/10/15
803 Fixed check for application/x-www-form-urlencoded parameters.
805 --- 1.0.10 2008/10/14
807 Fixes for IE in pz2.js.
809 Fixed bug #2021: non-merged, brief meta data NOT included for command=show.
813 Changed the JS library pz2.js to use POST for long URL (+ params).
815 Added installation instructions for Windows. Note: NT services is
816 NOT available until we make a new release of YAZ.
818 Preserve order of repeated metadata fields (they were reversed before).
820 More MARC21 information extracted for metadata.
824 Fixed bug #1162: HTML entities are not escaped properly.
826 Native Windows port of Pazpar2. Makefile for Visual Studio provided.
830 Marc21 stylesheet updated to reflect multiple full text fields
834 Fixed bug in pz2.js WRT DOMElement attributes on IE.
836 Fixed bug 2100: Database wildcards not working
840 Added support for retrieval of records in binary.
842 Fixed bug 1794: Pazpar2 does not return valid XML.
844 Deal with ICU not returning sortkey (resulted in SEGV before).
848 JavaScript library pzw2.js throws error if WS response (from Pazpar2 or
849 other) is malformed (non-wellformed XML or missing Pazpar2 OK status).
851 Improved diagnostics when Pazpar2 HTTP decoding fails.
853 Pazpar2 requests may be POSTed as using Content-Type
854 application/x-www-form-urlencoded.
856 Pazpar2 honors LF in HTTP headers.
858 Handle targets that handle negative hit counts (should not happen, but it
863 ICU is used for tokenization and normalization of the following: mergekey,
864 sorting, relevance terms.
866 Debian package now enables ICU tokenization and normalization by default.
870 Exposed user setting values (i.e. non-pz: names) to the record systems in two
871 ways: Either as parameters to the normalization stylesheets (which would allow the
872 programmer to postprocess or use the values in any way) or after the normalization
873 step, in which case values are made part of the normalized record (and available for
874 sorting, termlists, display, or other interface-related use.
876 Implemented sorting by year.
878 Option -d dumps records to the current log file instead of stderr.
880 Fixes for compilation on cygwin.
882 Z39.50 client code uses pz:elements. pz:elements was recognized in
883 earlier Pazpar2 versions but it was not used for anything.
885 icu_chain_test is using fgets instead of getline - fixes compilation
888 Loosen the CCL query parsing so that Pazpar2 only returns error if _all_
889 query conversions fail (rather than _any_). This means targets that do
890 not support some fields are ignored in a search.
894 Improved handling of socket timeout for Z39.50 connections.
896 Misc documentation updates and spell fixes.
898 Debian package pazpar2 creates log rotate entry.
900 Debian package pazpar2-apache2 reloads Apache2.
902 jsdemo included in distribution. It illustrates the use of the js/pz2.js
907 First public release.