3 Fix URL with leading http:// not working PAZ-933
5 Build packages for Ubuntu Trusty Tahr 14.04 LTS
7 cf.xsl: handle medium override AND md field
11 sortmap relevance always uses increasing=1. PAZ-930
13 solr-pz2.xsl: ensure medium is also applied if Solr record do not
16 Fix leak in getaddrinfo usage for HTTP listener. Not a big deal because
17 this code is only executed once.
19 Fix typos is sortmap documentation.
21 Doc: fix misplaced variablelist tag.
25 Doc: update WRT ICU which is configured for YAZ; not Pazpar2.
26 It's been like that since version 1.1.1 from August 2009.
28 Add support for result-set caching via memcached. See description of
29 pz:memcached. Require that Pazpar2 is using YAZ 5.0.12 or later.
31 Add support for a <metadata> container tag. Patfh from Sven Porst.
33 Add support for XInclude in main configuarion file. Patch from Sven Porst.
35 Add client_{lock,unlock} before call to non_block_events in
36 connection_continue. Problem is that if non_block_events fire records,
37 then we will not unlock client at all. And as a result, a dead-lock
42 Avoid removing slash and other characters for generic metadata that
43 looks like a URL (contains ://). PAZ-915
45 pz2.js: Only use XDR when doing CORS. Favor XHR in all other circumstances.
47 Cluster merge fixes. PAZ-901
49 Set client state to "working" when waiting for DNS resolver. PAZ-907
51 Log when session terminates. PAZ-905
53 Fix LSB/HS conformance for /etc/init.d/pazpar2 PAZ-904
54 Debian: add support for /etc/init.d/pazpar2 status
58 Fix 'Record Missing' for command=show PAZ-903
60 Preserve order of records within cluster PAZ-902
62 testing: use yaz-ztest -V if possible and use YAZ in sibling directory
65 Allow clustered records to be ingested during retrieval. PAZ-900
67 Fix void function error which cannot return a value.
71 SRU pz:authentication="a/b" may end up as x-username=a%2Fb PAZ-899
73 Upgrade to debhelper version 7 PAZ-898
75 Package with libyaz5 PAZ-897
77 Better error message for CCL parse errors PAZ-887
81 New target setting: pz:authentication_mode. PAZ-896
83 pazpar2 PRM: pazpar2 runs as user nobody. PAZ-893
85 Strip #-suffix for ZOOM URLs. PAZ-892
89 Fix issue with hanging show/bytarget. Could happen if new search was
90 fired with filter before show from previous show completed.
92 Add 'date' handling for solr-pz2.xsl.
96 pz:authentication may carry user group password. If pz:authentication
97 has at least one blank in it, that forces Pazpar2 to use idPass Z39.50
98 authentication. Two forms are allowed
101 If no blanks are present, open authentication is in use (as before).
103 Fix {prev,next}recid elements that are returned by record
104 command. These were incorrect in versions 1.6.23 thru 1.6.32.
106 --- 1.6.32 2013/06/14
108 Experimental support for snippets. If argument snippets=1 is given
109 for command record or show, the text will include <match>-tags for
110 those area that matches.
112 Fix memory leak WRT client structures (incorrect inc ref count).
114 Log when a HTTP response is serialized and the time elapsed.
116 New command, service, which returns current service XML in use for
119 --- 1.6.31 2013/05/24
121 Local limit for fields of type "generic" (ie text fields) are
122 now normalized by mergekey rule before comparison takes place.
123 Before, no normalization took place and comparsion was, thus, exact.
125 New facility: dynamic rank , which allows ranking to be changed
126 for an existing result set. The rank can be set for search or
127 show. This overrides the rank for metadata elements (which fields
130 New facility:dynamic mergekey , which allows mergekey to be changed
131 for an existing result set. The mergekey can be set for search or
134 HTTP server: host=@ listens on IPV6 and IPV4 if possible.
135 Also, allow ports to be given as names (not just integers).
136 Fix @-notation on systems that don't support IPV6 sockets.
138 --- 1.6.30 2013/04/26
140 Add MasterKey Connect configuration. Refer to section "non-standard
141 databases" for more information.
143 Allow timeformat for log to be specified with option -m (as Metaproxy
146 New Debian package pazpar2-dbg.
148 Fix NULL ptr reference of se->relevance. If a new search is initiated
149 and a CCL query fails to parse, Pazpar2 could crash.
151 Fix problem with host/port mangling in Pazpar2 HTTP server. Problem
152 existed in 1.6.29 only.
154 --- 1.6.29 2013/04/05
156 IPV6 updates. Allow IPv6 addresses for database hosts and IPv6 address
157 for HTTP server. By default the HTTP server uses IPv4 only, but that can be
158 changed by setting "host" attribute for the "listen" element.
160 Change semantics of pz:extendrecs. Allow for repeated fetches .
161 pz:extendrecs is now the number of extra records to fetch (was total
164 --- 1.6.28 2013/03/21
166 Fix hang or memory violation if show occurred before a search. (not that
167 it makes much sense to perform a show before a search).
169 --- 1.6.27 2013/03/08
171 pz2.js: Element_parseChildNodes concatenates all Text/CDATA nodes, instead
174 --- 1.6.26 2013/03/08
176 New pz:metadata attribute, empty="empty-value" for Pazpar2's
177 internal representation. With this attribute, Pazpar2 treates an empty
178 pz:metadata type as having the value for "empty" - if empty.
180 New setting, pz:extendrecs, which triggers extended fetch of records
181 for a database beyond pz:maxrecs for a show command.
183 Fix warning that was falsely issued for "missing limitmap".
185 Log message for Pazpart start/stop changed. Now using same style as
186 Metaproxy, ie Pazpar2 start SHA1 / Pazpar2 stop .
188 --- 1.6.25 2013/02/07
190 Fix hang of 2nd command=show with esn/syntax given.
192 --- 1.6.24 2013/01/18
194 New merge attribute type: 'first', which takes all metadata fields
195 from first target that returns the particular field.
197 --- 1.6.23 2013/01/02
199 Extend info command with hostname and YAZ SHA1
200 Indent results for both command stat and info.
202 Allow limit on merged content. The new configuration metadata
203 element, limitcluster, configures that a metadata element (name) be used
204 as limit name for search. Applies to the whole service (ie all targets),
205 unlike pz:limitmap which is configured per-target (database).
207 New feature: limitmap local:* matches against all metadata fields.
209 Allow repeated list in limitmap spec . Separated by comma. For
210 example: value="local:title,rpn:@attr 1=4".
212 New element <message> in bytarget response. Holds diagnostic message
213 of code (say 'Unsupported Use Attribute' for Bib-1 114).
215 Improved logging for record ingestion failures.
217 Avoid using struct icu_chain in non-YAZ_HAVE_ICU mode. In the rare case,
218 when YAZ is compiled without ICU support.
220 --- 1.6.22 2012/10/11
222 Requires YAZ-4.2.40 to support native solr support.
224 Fix and improve logic handling whether or not to re-do search on sort
225 order changes. A sort order with change in ascending/descending only
226 whould not trigger a new search, which is required for targets with
227 native sorting capabilities. Each client is now checked if instructions
228 (sortmap) exist for native sorting and only client that does requires
229 it is researched. Other clients is just re-ingesting the records,
230 they already have. The resultset is now cleared if any researching
233 Connection sharing between session has broken since version 1.6.8 with
234 introduction of logic that would minimize searching if pazpar2 could
235 detect this based on same query and limits and partly sort order.
236 This could lead to segementations violations.
238 Added a chapter in the manaul about relevance ranking.
240 --- 1.6.21 2012/09/24
242 Rank tweak: follow=number will increase mult by number if two terms
243 occur next to each other; number-1 if they are one term apart , .. 0
244 if they are number a part (all in order). Default is 0 (following
245 terms has no effect).
247 Rank tweak: lead=k will divide mult by 1 + log2(1+k*l) where k is
248 value given by lead and l is length from beginning of field where
249 term occurs (l=0 for first term, l=1 for second term, ..). Default
252 Rank tweak: length=strategy. length="linear" if mult is to be divided
253 by length (existing, default behavior), length="log" if mult is to be
254 divided by log2(1+length), length="none" if mult is not to be affected
257 --- 1.6.20 2012/09/21
259 Rank algorithm details may be printed as part of show response in
260 element <relevance_info>.. This is only printed if <rank debug="yes"/>
263 Record as returned by show/record command have a minimal indentation
264 which makes things human-readable.
266 New configuration of default sorting criteria (sort-default) in
267 service definition. If no criteria is defined it will be as before
270 Search command now supports sort parameter just as the show command.
271 If no parameter is give, it will use the service sort-default value.
273 --- 1.6.19 2012/09/18
275 Rank algorithm skips strings that gets normalized to empty string.
276 For example, & and ! could map to the empty string. The weight for
277 those terms is now 0 (as if they were not part of the query).
279 Rank algorithm does not use CCL from limitmap; only from the query
280 parameter (user query).
284 --- 1.6.18 2012/09/17
286 Rank algorithm configurable by 'rank' element inside service. So far
287 only, attribute 'cluster' is recognized. If cluster="yes", multiple
288 records inside a cluster boosts higher than single records. This
289 is default behavior and existing behavior. cluster="no" takes the
290 average score of each record in a cluster.
292 --- 1.6.17 2012/09/05
294 Fix bad re-use of connections (connections with changing proxy should not
297 --- 1.6.16 2012/08/22
299 Fix a bug introduce in 1.6.15 around the position sorting. It resetted the
300 resultset and sorting when the sort order is position. However this will be done on
301 every client poll, which will make pazpar2 continuing reset and fetching.
302 It should only be done on FIRST request where the sort order change.
304 Fix an issue on suggestion option: Also disable suggestions on empty string.
306 Clean up in turbo marc stylesheet.
308 Remove the hardcoded size of termlists.
310 --- 1.6.15 2012/06/27
312 New facility: ccldirective may be given in service definition. Allows
313 CCL parsing to be customized a bit, such as defining names of operators
316 New facility: raw record by checksum, rather than offset. The record
317 command optionally takes checksum which identifies certain record from
320 New facility: per field ranking. Rank may be given as M [F N] where
321 M is default rank and N is rank for CCL terms from field F.
323 --- 1.6.14 2012/06/04
325 Fix for IE7/8 in pz.js
327 Applied patch from Giannis Kosmas on keepAlive, which also adds keepAlive to init response.
329 Lower log level some places.
331 Remove some invalid test results.
333 --- 1.6.13 2012/05/23
335 Introducing a version=2 parameter for show, termlist and bytarget commands.
336 This enables pazpar2 to return approximation on hit and count count when
337 doing record filtering using the limit parameter on search and a
338 limitmap with a value of "local:"
340 Setting pz:xslt may embed local XSLT as an alternative to referring
342 Value is not CDATA but XML nodes embedded, so escaping is not necessary
343 but a root element *must* be present. For example:
344 <settings target="target="z3950.indexdata.com/marc">
353 Metadata field rank may given by XML internal document (pz:xslt
354 result). If rank is not given, the rank from service description is
357 Metadata field can now configured a default limitmap and facetmap.
358 Setting limitmap to "local:" would work for all kind of targets, but would
359 prob. not be the optimal solution. But at least better than the default behavior
360 of pazpar2 where no filtering is done.
362 A service definition can now also contains <set/> that defines service-wide
363 settings. These will override server-wide sets and will be overridded by
366 New setting, pz:present_chunk, that specifies number of records to fetch
367 at a time. Zero will disable chunkation; will fetch max_records at once.
369 --- 1.6.12 2012/03/14
371 Revert the format change in termlist response, that could break
372 some clients / UIs since they were expecting an (empty) element
373 if no facet values was found.
375 --- 1.6.11 2012/03/07
377 Revert the behavior of returning errors when unable to block
378 on termlist, bytarget and search, when unable to block due to
379 other block. The client will now receive a regular response,
380 but it will be logged in the server. A parameter (report) is
381 added to change behavior to return error response or WARNING
382 status message. Consider this "API" as private, as it is mostly
383 untested and could be changed in future releases.
385 Fix spell error in pz2.js fix in 1.6.10.
387 New Marc2TurboMarc.xsl (contribution from Sven Porst).
388 Can solve the missing marc21.xsl updates in some cases.
390 tmarc.xsl: Simplify the 6xx to subject-long and fix 1-based
391 substring (contribtion from Sven Porst)
393 marc21.xsl: fix 1-based substring call
395 tmarc.xsl and marc21.xsl: use 856$a as last option for electronic-text.
397 Add test_termlist_block to test suite
399 --- 1.6.10 2012/02/23
401 Fix SEGV for invalid PQFs and SRU/SOLR targets
402 Also refactor a bit the code that converts from PQF to SRU/SOLR queries.
404 Fix pz2.js: "null object" due to change in in bytarget result XML.
406 Fixes in tmarc.xsl: Subject-long shorten for extra commas only.
407 Added this normalization to the other subject-long fields (d6xx),
408 where it was missing.
410 Fixes in marc21.xsl: Updated with most of the new tmarc.xsl.
411 Still differences around medium and holdings. marc21.xsl is not
412 longer active used by Index Data, and should be considered unsupported.
413 Use tmarc.xsl instead.
417 Fix SEGV that could occur for failed connections.
421 Fix bug for command sort that could return no results for active clients
422 (from previous search). This bug was present in 1.6.6-1.6.7.
424 Fix bug in results that could include results that should have been
425 filtered out. This bug was present in 1.6.6-1.6.7.
429 Fix bug introduced in 1.6.6 where a connection re-use could stall
432 Local filtering may now specify a local metadata field, eg.
433 pz:limitmap:somefield[t]=local:otherfield
437 For search, when limit and or filtering is in place and search
438 is identical to previous search, the result set is re-used and the
439 target is not searched.
441 Limits may work perform local filtering as well, by using "local:"
446 Updated bytarget command to contain a suggestions element with misspelled
447 words and suggestions to these. pz2.js has been updated to deliver this
448 onwards as well. Only target that currently delivers this is the solr
449 client in YAZ 4.2.18.
453 New service definition element, xslt, that allows an embedded stylesheet
454 to be defined. This can be referred to from pz:xslt as an alternative to
457 New pz:sortmap:field setting for specifying hints on how to make
458 a target natively sort on a field. This is used for command=show in
459 conjunction with sort.
461 New pz:url setting for specifying the actual URL for a target. When
462 this is used the target ID is not used as URL anymore and the target ID
463 may be almost any string (not including []).
465 command=termlist without name parameter returns all termlists/facets.
466 Previously if name parameter was omitted, only "subject" was returned.
470 Make termlist sorting stable. Terms with same frequency are now sorted by
471 their display name. This makes a pretty display and improves our
472 regression test because qsort is not a stable sort.
474 New sort parameter value 'position'. The 'position' sorts merged records
475 by their original position from the remote target. This is primarily useful
476 for debugging and may be used for targets that already perform some kind
477 of relevance ranking. Note that sort by default is decreasing; so to get
478 records in their original order sort=position:1 must be used.
482 tmarc.xsl: yet another 773$g fix. Was broken in 1.6.1 as well.
484 Facility to change working directory for pazpar2 daemon. Option -wdir
485 sets working directory to dir. This facility is useful if core dumps
486 must be saved. In this case, the current working directory must be
487 writable by the running user, such as "nobody".
491 New configuration element <icu_chain> for <server>/<service> which
492 allows a named ICU rule (chain) to be defined. The names relevance,
493 sort, mergekey and facet are used for those operations. The definition
494 <icu_chain id="sort" locale="en"> .. </icu_chain>
496 <sort> <icu_chain locale="en> ... </icu_chain> </sort>
497 And so on.. for relevance, mergekey and facet as well. The latter
498 style is deprecated. The facet terms are normalized by the facet
499 rule by default. This may be changed on a metadata field basis by
500 defining the new attribute 'facetrule' for the metadata element.
502 <icu_chain id="myrule" locale="en"> ... </icu_chain>
503 <metadata name="author" termlist="yes" facetrule="myrule"/>
505 Preserve rorder for merged metadata. Fixes issue as reported by Sven
506 Porst: http://lists.indexdata.dk/pipermail/yazlist/2011-July/003230.html
508 tmarc.xsl: set journal-subpart to 773$ only.
512 Modify the behavior for the limit parameter (first defined in 1.5.7).
513 Mapping of limit searches are now defined by the new configuration item
514 pz:limitmap. Fix a dead-lock problem with the limit parameter.
516 Extend tmarc.xsl to extract 773$g data (OpenURL).
520 ICU default maps remove backquote (`).
522 Command 'search' takes limit parameter (optional). The limit parameter
523 allows a search to be limited one or more facets and the corresponding
524 values. This is for server side filtering.
526 Configure tweak: Use -lm for log(3) if needed
530 Fix a problem with skiparticle sortkey that could be completely
531 ignored (and reduced to "").
533 Fix dependency problem in pazpar2 RPM package (did not require
534 libyaz4 as it should).
538 Fix memory leak that occurred for command=termlist&name=xtargets .
540 Pazpar2 may save HTTP requests. Enabled by option -R.
544 Experimental support for DTIC DADS target. New dads-pz2.xsl.
546 Support for query_syntax (overrides the default for SRU | Z39.50)
548 Support for extraArgs (ZOOM "extraArgs" option) for targets
550 New commands: status-server and status-session
554 Fix for threaded runs: Client now have a copy of the database URL,
555 which can used after the database has been release from the client.
556 This makes the logging in the connection idle timeout of the client nicer (no NOURL) and should be thread-safe.
558 tmarc.xsl: Add journal-title-abbrev and full text.
560 cf.xsl: new fields: isbn, issn, journaltitle, volume, issue
562 Fix for cmd=record before search.
564 Session Logging clean up.
566 Fix wrong termlist factor when maxrecs is different from 100.
570 Fix missing pz:termlist_term_factor in settings.c messed up pz:preferred.
571 Term factor is default enabled but can be diseabled by
572 pz:termlist_term_factor=0
576 Add scaling of facet count. Currently always enabled, needs fixing.
577 Allow user-defined info for target suffix. This has no meaning in
578 Pazpar2 except to distinguish targets from each other. The suffix
579 data begins with #. For example z3950.indexdata.com/gils#Mydata
581 Added exact-match recordfilter; format name=value
585 SOLR support. Pazpar2 may operate as web service client for SOLR.
589 Fix for show command and block=1 (dead lock). Bug was introduced in
594 New RPM packages: pazpar2, pazpar2-js, pazpar2-doc. These have been
595 tested on CentOS 5.5 only.
599 Fix problem with result sets being removed from a client session
600 if the connection for it was resused by another session. Bug #3489.
602 New iphone UI for Pazpar2 (www/iphone).
606 Fixes for threaded operation.
608 New stylesheets for TurboMARC: tmarc.xsl and opac_turbomarc.xsl.
610 New example services in etc/services in source. In the Debian packages
611 these are located in /etc/pazpar2/services-available
613 Threaded mode operational on Windows. Requires Windows 7 or Windows
616 Default value of setting pz:max_connections is 0 which means that there
617 is no limit on number of connections.
621 Pazpar2 may operate in threaded mode. Enabled by element threads in
622 the configuration. See pazpar2_conf for details.
624 New setting setting: pz:max_connections. Setting pz:max_connections is
625 a limit of number of sockets to a host. When this limit is reached,
626 Pazpar2 will wait up to 5 seconds for a connection to becomes available.
627 The client will be marked Client_Error when it can not be searched
628 (other clients in a session may work). If pz:max_connections is not set
629 for a target, a value of 30 will be used. Note: the pz:max_connections
630 will only work in threaded mode.
632 pz2.js: JSON support for show.
634 Debian package: Enable default service, default.xml, before starting
635 Pazpar2 only if there is no service already in /etc/pazpar2/services-enabled.
639 Debian version depends on on libyaz4. Note that Pazpar2 will still
640 compile from source with YAZ 3.
642 Split services into separate files. The example configuration file
643 pazpar2.cfg.dist now includes a default service default.xml (part of
644 etc). And default.xml includes settings/edu.xml. The default.xml file,
645 not to be confused with settings/defaults.xml, is a template for jsdemo
646 and other services. The Debian package installs /etc/pazpar2/server.xml
647 which is now the main pazpar2 configuration (used to be called pazpar2.cfg).
648 server.xml includes services from /etc/pazpar2/services-enabled/*.xml .
649 The default.xml (from etc) is installed in /etc/pazpar2/services-available
650 and a symlink to it is created from services-enabled. The default.xml
651 service is unnamed and, thus, will be used by jsdemo and test1.
653 New setting pz:negotiation_charset. Patch from Andrei V. Toutoukine. The
654 new setting pz:negotiation_charset specifies character set for Z39.50 Init.
658 Support for additional fields in cf.xsl and pazpar2.conf.dist:
659 publisher, available, due, location (=locallocation), callno
660 (=callnumber), thumburl and score.
662 Describe pz:xslt and the auto setting.
664 Move mergekey definition away from the normalization stylesheets and
665 define a mergekey common for all target types in pazpar2.cfg.
667 Code update: Use the Odr_int type for hit counts. This is part of
668 YAZ 3.0.47 and later and so configure checks for that.
672 Metadata attribute 'skiparticle' also works for ICU based
673 normalization. (was only working for the non-ICU/ASCII before).
675 Command bytarget with argument settings=1 will show settings per
676 target.. This is to be able to verify correct settings and be able to
677 test that they are correct. The database settings array size is now
678 also stored.. Problems with database settings array is that if not
679 careful it will be too small (smaller than dictionary per-service
682 Make record list sorting stable by comparing mergekey for records if
683 relevance/title or other sorting criteria all match. This is merely to
684 ensure that our regressions tests works (reproducible output).
686 Relevance calculation changes: use a different denominator (length) for
687 per-field relevance scoring.. Instead of length of all ranked fields we
688 now use length of individual fields (as if they were individual "free"
689 text fields). This will ensure that documents with a long field with no
690 match (say description) will not "hurt" a title match.
692 Diagnostic member was not set on connection error. Fixed
696 Command search takes two optional parameters, startecs and maxrecs,
697 that specifies the start offset (0, 1, ...) and maximum number of records
698 to fetch for each target.
700 XSLTs + MARC maps are cached within a session so we don't re-parse
701 them over and over again. Even for a session with a single search
702 there's much to be gained because many targets use the same
705 The metadata attribute 'mergekey' now takes one of three values 'no',
706 'required', 'optional' . And the resulting mergekey from metadata
707 is now ordered in the same way as metadata in the service definition.
708 Older Pazpar2 version use the order in which metadata appeared in a
711 The search argument 'filter' now offers a new operator ~ which does a
712 substring match. The = operator works as before: string match for
713 anything but pz:id, or target match for pz:id.
715 New setting pz:recordfilter. The value of this setting takes the
716 form name[~value]. This setting makes Pazpar2 ignore all retrieved
717 records that do not have the metadata element name with value substring
720 Pazpar2 allows YAZ log level to be set (option -v).
724 For WS responses Pazpar2 creates XML header. Exception: raw record.
726 Setting XML files are now stored in etc/settings instead of etc. This
727 reflects the layout with the Debian package layout.
729 Settings may be posted for command=settings. The POSTed settings must
730 have root element 'settings' like regular setting files. In order to be
731 recognized, the POST request must use Content-Type=text/xml.
733 A service may be posted for command=init. This service will be used
734 during the session. The service may have its own target settings,
735 ICU config, timeout, etc. In order to be recognized, the POST request
736 must use Content-Type=text/xml.
738 Timeout values may be given per-service. That's element 'timeout'
739 which takes three attribute values (a subset may be given): 'session',
740 'z3950_operation', 'z3950_session'. Option -T is no longer supported
741 - used to specify session timeout.
743 Option -t tests the Pazpar2 configuration and returns exit code
744 (0=success, non-zero=failure). In previous version of Pazpar2, -t
745 specified local settings.
747 In version 1.2.0 the configuration file - after include processing -
748 was dumped to stdout. Now, the configuration is only dumped to the
749 yaz log file if option -d is given.
753 Configuration may now have multiple server areas. This means that a
754 Pazpar2 instance may listen on multiple ports. Virtual hosting is not
755 yet supported - on a server basis. Configuration may also have multiple
756 services .. That is repeating service elements inside a server. Each
757 has an attribute 'id' which serves as service ID. This ID in turn may
758 be used in a Pazpar2 session, by specifying parameter service=ID for
759 command init. There can be at most one unnamed service inside a server
760 which can be referred to by not specifying an service ID for command
761 init (backwards compatible). In order to partition multiple servers and
762 services a new include directive has been added. This takes an attribute
763 'src' which specifies one or more sub-files. For example to include
764 service files, one might use:
765 <server >.. <include src=/"etc/pazpar2/conf.d/*.xml"/> .. </server>.
766 It is the intention that that completely makes the settings directive
769 Fix problem where the record command would wait forever if there were
770 no targets to wait for (activeclients == 0).
774 One result set is created per session (last search) rather than for
775 each connection which happen to be shared (bug #3009).
777 marc21 stylesheets changed for efficiency.
781 Session timeout may be specified on the command-line as option -T.
783 Pazpar2 may now be operated in a no-merged mode for records.. All records
784 will be considered unique. This mode is enabled if no mergekey is
785 generated by the normalization stylesheet (pz:xslt).
787 Pazpar2 caches original records from each target and the 'record' command
788 with offset returns the original record if 'syntax' and 'esn' are NOT
789 specified. This speeds up retrieval of original records but also means
790 that Pazpar2 uses more memory. The cached records will be freed when the
791 session terminates or a new search is executed.
793 Pazpar2 no longer uses its own ICU wrapper. Instead the ICU wrapper
794 library part of YAZ is used.
796 Added SRU client support.
798 Automatically computes pz:nativesyntax if not provided. Works for XML and
801 --- 1.0.13 2008/11/24
803 Command bytarget returns name of target (if defined).
805 --- 1.0.12 2008/11/04
807 Fixed bug #2021.. location now holds all brief elements.
809 --- 1.0.11 2008/10/15
811 Fixed check for application/x-www-form-urlencoded parameters.
813 --- 1.0.10 2008/10/14
815 Fixes for IE in pz2.js.
817 Fixed bug #2021: non-merged, brief meta data NOT included for command=show.
821 Changed the JS library pz2.js to use POST for long URL (+ params).
823 Added installation instructions for Windows. Note: NT services is
824 NOT available until we make a new release of YAZ.
826 Preserve order of repeated metadata fields (they were reversed before).
828 More MARC21 information extracted for metadata.
832 Fixed bug #1162: HTML entities are not escaped properly.
834 Native Windows port of Pazpar2. Makefile for Visual Studio provided.
838 Marc21 stylesheet updated to reflect multiple full text fields
842 Fixed bug in pz2.js WRT DOMElement attributes on IE.
844 Fixed bug 2100: Database wildcards not working
848 Added support for retrieval of records in binary.
850 Fixed bug 1794: Pazpar2 does not return valid XML.
852 Deal with ICU not returning sortkey (resulted in SEGV before).
856 JavaScript library pzw2.js throws error if WS response (from Pazpar2 or
857 other) is malformed (non-wellformed XML or missing Pazpar2 OK status).
859 Improved diagnostics when Pazpar2 HTTP decoding fails.
861 Pazpar2 requests may be POSTed as using Content-Type
862 application/x-www-form-urlencoded.
864 Pazpar2 honors LF in HTTP headers.
866 Handle targets that handle negative hit counts (should not happen, but it
871 ICU is used for tokenization and normalization of the following: mergekey,
872 sorting, relevance terms.
874 Debian package now enables ICU tokenization and normalization by default.
878 Exposed user setting values (i.e. non-pz: names) to the record systems in two
879 ways: Either as parameters to the normalization stylesheets (which would allow the
880 programmer to postprocess or use the values in any way) or after the normalization
881 step, in which case values are made part of the normalized record (and available for
882 sorting, termlists, display, or other interface-related use.
884 Implemented sorting by year.
886 Option -d dumps records to the current log file instead of stderr.
888 Fixes for compilation on cygwin.
890 Z39.50 client code uses pz:elements. pz:elements was recognized in
891 earlier Pazpar2 versions but it was not used for anything.
893 icu_chain_test is using fgets instead of getline - fixes compilation
896 Loosen the CCL query parsing so that Pazpar2 only returns error if _all_
897 query conversions fail (rather than _any_). This means targets that do
898 not support some fields are ignored in a search.
902 Improved handling of socket timeout for Z39.50 connections.
904 Misc documentation updates and spell fixes.
906 Debian package pazpar2 creates log rotate entry.
908 Debian package pazpar2-apache2 reloads Apache2.
910 jsdemo included in distribution. It illustrates the use of the js/pz2.js
915 First public release.