3 Avoid removing slash and other characters for generic metadata that
4 looks like a URL (contains ://). PAZ-915
6 pz2.js: Only use XDR when doing CORS. Favor XHR in all other circumstances.
8 Cluster merge fixes. PAZ-901
10 Set client state to "working" when waiting for DNS resolver. PAZ-907
12 Log when session terminates. PAZ-905
14 Fix LSB/HS conformance for /etc/init.d/pazpar2 PAZ-904
15 Debian: add support for /etc/init.d/pazpar2 status
19 Fix 'Record Missing' for command=show PAZ-903
21 Preserve order of records within cluster PAZ-902
23 testing: use yaz-ztest -V if possible and use YAZ in sibling directory
26 Allow clustered records to be ingested during retrieval. PAZ-900
28 Fix void function error which cannot return a value.
32 SRU pz:authentication="a/b" may end up as x-username=a%2Fb PAZ-899
34 Upgrade to debhelper version 7 PAZ-898
36 Package with libyaz5 PAZ-897
38 Better error message for CCL parse errors PAZ-887
42 New target setting: pz:authentication_mode. PAZ-896
44 pazpar2 PRM: pazpar2 runs as user nobody. PAZ-893
46 Strip #-suffix for ZOOM URLs. PAZ-892
50 Fix issue with hanging show/bytarget. Could happen if new search was
51 fired with filter before show from previous show completed.
53 Add 'date' handling for solr-pz2.xsl.
57 pz:authentication may carry user group password. If pz:authentication
58 has at least one blank in it, that forces Pazpar2 to use idPass Z39.50
59 authentication. Two forms are allowed
62 If no blanks are present, open authentication is in use (as before).
64 Fix {prev,next}recid elements that are returned by record
65 command. These were incorrect in versions 1.6.23 thru 1.6.32.
69 Experimental support for snippets. If argument snippets=1 is given
70 for command record or show, the text will include <match>-tags for
71 those area that matches.
73 Fix memory leak WRT client structures (incorrect inc ref count).
75 Log when a HTTP response is serialized and the time elapsed.
77 New command, service, which returns current service XML in use for
82 Local limit for fields of type "generic" (ie text fields) are
83 now normalized by mergekey rule before comparison takes place.
84 Before, no normalization took place and comparsion was, thus, exact.
86 New facility: dynamic rank , which allows ranking to be changed
87 for an existing result set. The rank can be set for search or
88 show. This overrides the rank for metadata elements (which fields
91 New facility:dynamic mergekey , which allows mergekey to be changed
92 for an existing result set. The mergekey can be set for search or
95 HTTP server: host=@ listens on IPV6 and IPV4 if possible.
96 Also, allow ports to be given as names (not just integers).
97 Fix @-notation on systems that don't support IPV6 sockets.
101 Add MasterKey Connect configuration. Refer to section "non-standard
102 databases" for more information.
104 Allow timeformat for log to be specified with option -m (as Metaproxy
107 New Debian package pazpar2-dbg.
109 Fix NULL ptr reference of se->relevance. If a new search is initiated
110 and a CCL query fails to parse, Pazpar2 could crash.
112 Fix problem with host/port mangling in Pazpar2 HTTP server. Problem
113 existed in 1.6.29 only.
115 --- 1.6.29 2013/04/05
117 IPV6 updates. Allow IPv6 addresses for database hosts and IPv6 address
118 for HTTP server. By default the HTTP server uses IPv4 only, but that can be
119 changed by setting "host" attribute for the "listen" element.
121 Change semantics of pz:extendrecs. Allow for repeated fetches .
122 pz:extendrecs is now the number of extra records to fetch (was total
125 --- 1.6.28 2013/03/21
127 Fix hang or memory violation if show occurred before a search. (not that
128 it makes much sense to perform a show before a search).
130 --- 1.6.27 2013/03/08
132 pz2.js: Element_parseChildNodes concatenates all Text/CDATA nodes, instead
135 --- 1.6.26 2013/03/08
137 New pz:metadata attribute, empty="empty-value" for Pazpar2's
138 internal representation. With this attribute, Pazpar2 treates an empty
139 pz:metadata type as having the value for "empty" - if empty.
141 New setting, pz:extendrecs, which triggers extended fetch of records
142 for a database beyond pz:maxrecs for a show command.
144 Fix warning that was falsely issued for "missing limitmap".
146 Log message for Pazpart start/stop changed. Now using same style as
147 Metaproxy, ie Pazpar2 start SHA1 / Pazpar2 stop .
149 --- 1.6.25 2013/02/07
151 Fix hang of 2nd command=show with esn/syntax given.
153 --- 1.6.24 2013/01/18
155 New merge attribute type: 'first', which takes all metadata fields
156 from first target that returns the particular field.
158 --- 1.6.23 2013/01/02
160 Extend info command with hostname and YAZ SHA1
161 Indent results for both command stat and info.
163 Allow limit on merged content. The new configuration metadata
164 element, limitcluster, configures that a metadata element (name) be used
165 as limit name for search. Applies to the whole service (ie all targets),
166 unlike pz:limitmap which is configured per-target (database).
168 New feature: limitmap local:* matches against all metadata fields.
170 Allow repeated list in limitmap spec . Separated by comma. For
171 example: value="local:title,rpn:@attr 1=4".
173 New element <message> in bytarget response. Holds diagnostic message
174 of code (say 'Unsupported Use Attribute' for Bib-1 114).
176 Improved logging for record ingestion failures.
178 Avoid using struct icu_chain in non-YAZ_HAVE_ICU mode. In the rare case,
179 when YAZ is compiled without ICU support.
181 --- 1.6.22 2012/10/11
183 Requires YAZ-4.2.40 to support native solr support.
185 Fix and improve logic handling whether or not to re-do search on sort
186 order changes. A sort order with change in ascending/descending only
187 whould not trigger a new search, which is required for targets with
188 native sorting capabilities. Each client is now checked if instructions
189 (sortmap) exist for native sorting and only client that does requires
190 it is researched. Other clients is just re-ingesting the records,
191 they already have. The resultset is now cleared if any researching
194 Connection sharing between session has broken since version 1.6.8 with
195 introduction of logic that would minimize searching if pazpar2 could
196 detect this based on same query and limits and partly sort order.
197 This could lead to segementations violations.
199 Added a chapter in the manaul about relevance ranking.
201 --- 1.6.21 2012/09/24
203 Rank tweak: follow=number will increase mult by number if two terms
204 occur next to each other; number-1 if they are one term apart , .. 0
205 if they are number a part (all in order). Default is 0 (following
206 terms has no effect).
208 Rank tweak: lead=k will divide mult by 1 + log2(1+k*l) where k is
209 value given by lead and l is length from beginning of field where
210 term occurs (l=0 for first term, l=1 for second term, ..). Default
213 Rank tweak: length=strategy. length="linear" if mult is to be divided
214 by length (existing, default behavior), length="log" if mult is to be
215 divided by log2(1+length), length="none" if mult is not to be affected
218 --- 1.6.20 2012/09/21
220 Rank algorithm details may be printed as part of show response in
221 element <relevance_info>.. This is only printed if <rank debug="yes"/>
224 Record as returned by show/record command have a minimal indentation
225 which makes things human-readable.
227 New configuration of default sorting criteria (sort-default) in
228 service definition. If no criteria is defined it will be as before
231 Search command now supports sort parameter just as the show command.
232 If no parameter is give, it will use the service sort-default value.
234 --- 1.6.19 2012/09/18
236 Rank algorithm skips strings that gets normalized to empty string.
237 For example, & and ! could map to the empty string. The weight for
238 those terms is now 0 (as if they were not part of the query).
240 Rank algorithm does not use CCL from limitmap; only from the query
241 parameter (user query).
245 --- 1.6.18 2012/09/17
247 Rank algorithm configurable by 'rank' element inside service. So far
248 only, attribute 'cluster' is recognized. If cluster="yes", multiple
249 records inside a cluster boosts higher than single records. This
250 is default behavior and existing behavior. cluster="no" takes the
251 average score of each record in a cluster.
253 --- 1.6.17 2012/09/05
255 Fix bad re-use of connections (connections with changing proxy should not
258 --- 1.6.16 2012/08/22
260 Fix a bug introduce in 1.6.15 around the position sorting. It resetted the
261 resultset and sorting when the sort order is position. However this will be done on
262 every client poll, which will make pazpar2 continuing reset and fetching.
263 It should only be done on FIRST request where the sort order change.
265 Fix an issue on suggestion option: Also disable suggestions on empty string.
267 Clean up in turbo marc stylesheet.
269 Remove the hardcoded size of termlists.
271 --- 1.6.15 2012/06/27
273 New facility: ccldirective may be given in service definition. Allows
274 CCL parsing to be customized a bit, such as defining names of operators
277 New facility: raw record by checksum, rather than offset. The record
278 command optionally takes checksum which identifies certain record from
281 New facility: per field ranking. Rank may be given as M [F N] where
282 M is default rank and N is rank for CCL terms from field F.
284 --- 1.6.14 2012/06/04
286 Fix for IE7/8 in pz.js
288 Applied patch from Giannis Kosmas on keepAlive, which also adds keepAlive to init response.
290 Lower log level some places.
292 Remove some invalid test results.
294 --- 1.6.13 2012/05/23
296 Introducing a version=2 parameter for show, termlist and bytarget commands.
297 This enables pazpar2 to return approximation on hit and count count when
298 doing record filtering using the limit parameter on search and a
299 limitmap with a value of "local:"
301 Setting pz:xslt may embed local XSLT as an alternative to referring
303 Value is not CDATA but XML nodes embedded, so escaping is not necessary
304 but a root element *must* be present. For example:
305 <settings target="target="z3950.indexdata.com/marc">
314 Metadata field rank may given by XML internal document (pz:xslt
315 result). If rank is not given, the rank from service description is
318 Metadata field can now configured a default limitmap and facetmap.
319 Setting limitmap to "local:" would work for all kind of targets, but would
320 prob. not be the optimal solution. But at least better than the default behavior
321 of pazpar2 where no filtering is done.
323 A service definition can now also contains <set/> that defines service-wide
324 settings. These will override server-wide sets and will be overridded by
327 New setting, pz:present_chunk, that specifies number of records to fetch
328 at a time. Zero will disable chunkation; will fetch max_records at once.
330 --- 1.6.12 2012/03/14
332 Revert the format change in termlist response, that could break
333 some clients / UIs since they were expecting an (empty) element
334 if no facet values was found.
336 --- 1.6.11 2012/03/07
338 Revert the behavior of returning errors when unable to block
339 on termlist, bytarget and search, when unable to block due to
340 other block. The client will now receive a regular response,
341 but it will be logged in the server. A parameter (report) is
342 added to change behavior to return error response or WARNING
343 status message. Consider this "API" as private, as it is mostly
344 untested and could be changed in future releases.
346 Fix spell error in pz2.js fix in 1.6.10.
348 New Marc2TurboMarc.xsl (contribution from Sven Porst).
349 Can solve the missing marc21.xsl updates in some cases.
351 tmarc.xsl: Simplify the 6xx to subject-long and fix 1-based
352 substring (contribtion from Sven Porst)
354 marc21.xsl: fix 1-based substring call
356 tmarc.xsl and marc21.xsl: use 856$a as last option for electronic-text.
358 Add test_termlist_block to test suite
360 --- 1.6.10 2012/02/23
362 Fix SEGV for invalid PQFs and SRU/SOLR targets
363 Also refactor a bit the code that converts from PQF to SRU/SOLR queries.
365 Fix pz2.js: "null object" due to change in in bytarget result XML.
367 Fixes in tmarc.xsl: Subject-long shorten for extra commas only.
368 Added this normalization to the other subject-long fields (d6xx),
369 where it was missing.
371 Fixes in marc21.xsl: Updated with most of the new tmarc.xsl.
372 Still differences around medium and holdings. marc21.xsl is not
373 longer active used by Index Data, and should be considered unsupported.
374 Use tmarc.xsl instead.
378 Fix SEGV that could occur for failed connections.
382 Fix bug for command sort that could return no results for active clients
383 (from previous search). This bug was present in 1.6.6-1.6.7.
385 Fix bug in results that could include results that should have been
386 filtered out. This bug was present in 1.6.6-1.6.7.
390 Fix bug introduced in 1.6.6 where a connection re-use could stall
393 Local filtering may now specify a local metadata field, eg.
394 pz:limitmap:somefield[t]=local:otherfield
398 For search, when limit and or filtering is in place and search
399 is identical to previous search, the result set is re-used and the
400 target is not searched.
402 Limits may work perform local filtering as well, by using "local:"
407 Updated bytarget command to contain a suggestions element with misspelled
408 words and suggestions to these. pz2.js has been updated to deliver this
409 onwards as well. Only target that currently delivers this is the solr
410 client in YAZ 4.2.18.
414 New service definition element, xslt, that allows an embedded stylesheet
415 to be defined. This can be referred to from pz:xslt as an alternative to
418 New pz:sortmap:field setting for specifying hints on how to make
419 a target natively sort on a field. This is used for command=show in
420 conjunction with sort.
422 New pz:url setting for specifying the actual URL for a target. When
423 this is used the target ID is not used as URL anymore and the target ID
424 may be almost any string (not including []).
426 command=termlist without name parameter returns all termlists/facets.
427 Previously if name parameter was omitted, only "subject" was returned.
431 Make termlist sorting stable. Terms with same frequency are now sorted by
432 their display name. This makes a pretty display and improves our
433 regression test because qsort is not a stable sort.
435 New sort parameter value 'position'. The 'position' sorts merged records
436 by their original position from the remote target. This is primarily useful
437 for debugging and may be used for targets that already perform some kind
438 of relevance ranking. Note that sort by default is decreasing; so to get
439 records in their original order sort=position:1 must be used.
443 tmarc.xsl: yet another 773$g fix. Was broken in 1.6.1 as well.
445 Facility to change working directory for pazpar2 daemon. Option -wdir
446 sets working directory to dir. This facility is useful if core dumps
447 must be saved. In this case, the current working directory must be
448 writable by the running user, such as "nobody".
452 New configuration element <icu_chain> for <server>/<service> which
453 allows a named ICU rule (chain) to be defined. The names relevance,
454 sort, mergekey and facet are used for those operations. The definition
455 <icu_chain id="sort" locale="en"> .. </icu_chain>
457 <sort> <icu_chain locale="en> ... </icu_chain> </sort>
458 And so on.. for relevance, mergekey and facet as well. The latter
459 style is deprecated. The facet terms are normalized by the facet
460 rule by default. This may be changed on a metadata field basis by
461 defining the new attribute 'facetrule' for the metadata element.
463 <icu_chain id="myrule" locale="en"> ... </icu_chain>
464 <metadata name="author" termlist="yes" facetrule="myrule"/>
466 Preserve rorder for merged metadata. Fixes issue as reported by Sven
467 Porst: http://lists.indexdata.dk/pipermail/yazlist/2011-July/003230.html
469 tmarc.xsl: set journal-subpart to 773$ only.
473 Modify the behavior for the limit parameter (first defined in 1.5.7).
474 Mapping of limit searches are now defined by the new configuration item
475 pz:limitmap. Fix a dead-lock problem with the limit parameter.
477 Extend tmarc.xsl to extract 773$g data (OpenURL).
481 ICU default maps remove backquote (`).
483 Command 'search' takes limit parameter (optional). The limit parameter
484 allows a search to be limited one or more facets and the corresponding
485 values. This is for server side filtering.
487 Configure tweak: Use -lm for log(3) if needed
491 Fix a problem with skiparticle sortkey that could be completely
492 ignored (and reduced to "").
494 Fix dependency problem in pazpar2 RPM package (did not require
495 libyaz4 as it should).
499 Fix memory leak that occurred for command=termlist&name=xtargets .
501 Pazpar2 may save HTTP requests. Enabled by option -R.
505 Experimental support for DTIC DADS target. New dads-pz2.xsl.
507 Support for query_syntax (overrides the default for SRU | Z39.50)
509 Support for extraArgs (ZOOM "extraArgs" option) for targets
511 New commands: status-server and status-session
515 Fix for threaded runs: Client now have a copy of the database URL,
516 which can used after the database has been release from the client.
517 This makes the logging in the connection idle timeout of the client nicer (no NOURL) and should be thread-safe.
519 tmarc.xsl: Add journal-title-abbrev and full text.
521 cf.xsl: new fields: isbn, issn, journaltitle, volume, issue
523 Fix for cmd=record before search.
525 Session Logging clean up.
527 Fix wrong termlist factor when maxrecs is different from 100.
531 Fix missing pz:termlist_term_factor in settings.c messed up pz:preferred.
532 Term factor is default enabled but can be diseabled by
533 pz:termlist_term_factor=0
537 Add scaling of facet count. Currently always enabled, needs fixing.
538 Allow user-defined info for target suffix. This has no meaning in
539 Pazpar2 except to distinguish targets from each other. The suffix
540 data begins with #. For example z3950.indexdata.com/gils#Mydata
542 Added exact-match recordfilter; format name=value
546 SOLR support. Pazpar2 may operate as web service client for SOLR.
550 Fix for show command and block=1 (dead lock). Bug was introduced in
555 New RPM packages: pazpar2, pazpar2-js, pazpar2-doc. These have been
556 tested on CentOS 5.5 only.
560 Fix problem with result sets being removed from a client session
561 if the connection for it was resused by another session. Bug #3489.
563 New iphone UI for Pazpar2 (www/iphone).
567 Fixes for threaded operation.
569 New stylesheets for TurboMARC: tmarc.xsl and opac_turbomarc.xsl.
571 New example services in etc/services in source. In the Debian packages
572 these are located in /etc/pazpar2/services-available
574 Threaded mode operational on Windows. Requires Windows 7 or Windows
577 Default value of setting pz:max_connections is 0 which means that there
578 is no limit on number of connections.
582 Pazpar2 may operate in threaded mode. Enabled by element threads in
583 the configuration. See pazpar2_conf for details.
585 New setting setting: pz:max_connections. Setting pz:max_connections is
586 a limit of number of sockets to a host. When this limit is reached,
587 Pazpar2 will wait up to 5 seconds for a connection to becomes available.
588 The client will be marked Client_Error when it can not be searched
589 (other clients in a session may work). If pz:max_connections is not set
590 for a target, a value of 30 will be used. Note: the pz:max_connections
591 will only work in threaded mode.
593 pz2.js: JSON support for show.
595 Debian package: Enable default service, default.xml, before starting
596 Pazpar2 only if there is no service already in /etc/pazpar2/services-enabled.
600 Debian version depends on on libyaz4. Note that Pazpar2 will still
601 compile from source with YAZ 3.
603 Split services into separate files. The example configuration file
604 pazpar2.cfg.dist now includes a default service default.xml (part of
605 etc). And default.xml includes settings/edu.xml. The default.xml file,
606 not to be confused with settings/defaults.xml, is a template for jsdemo
607 and other services. The Debian package installs /etc/pazpar2/server.xml
608 which is now the main pazpar2 configuration (used to be called pazpar2.cfg).
609 server.xml includes services from /etc/pazpar2/services-enabled/*.xml .
610 The default.xml (from etc) is installed in /etc/pazpar2/services-available
611 and a symlink to it is created from services-enabled. The default.xml
612 service is unnamed and, thus, will be used by jsdemo and test1.
614 New setting pz:negotiation_charset. Patch from Andrei V. Toutoukine. The
615 new setting pz:negotiation_charset specifies character set for Z39.50 Init.
619 Support for additional fields in cf.xsl and pazpar2.conf.dist:
620 publisher, available, due, location (=locallocation), callno
621 (=callnumber), thumburl and score.
623 Describe pz:xslt and the auto setting.
625 Move mergekey definition away from the normalization stylesheets and
626 define a mergekey common for all target types in pazpar2.cfg.
628 Code update: Use the Odr_int type for hit counts. This is part of
629 YAZ 3.0.47 and later and so configure checks for that.
633 Metadata attribute 'skiparticle' also works for ICU based
634 normalization. (was only working for the non-ICU/ASCII before).
636 Command bytarget with argument settings=1 will show settings per
637 target.. This is to be able to verify correct settings and be able to
638 test that they are correct. The database settings array size is now
639 also stored.. Problems with database settings array is that if not
640 careful it will be too small (smaller than dictionary per-service
643 Make record list sorting stable by comparing mergekey for records if
644 relevance/title or other sorting criteria all match. This is merely to
645 ensure that our regressions tests works (reproducible output).
647 Relevance calculation changes: use a different denominator (length) for
648 per-field relevance scoring.. Instead of length of all ranked fields we
649 now use length of individual fields (as if they were individual "free"
650 text fields). This will ensure that documents with a long field with no
651 match (say description) will not "hurt" a title match.
653 Diagnostic member was not set on connection error. Fixed
657 Command search takes two optional parameters, startecs and maxrecs,
658 that specifies the start offset (0, 1, ...) and maximum number of records
659 to fetch for each target.
661 XSLTs + MARC maps are cached within a session so we don't re-parse
662 them over and over again. Even for a session with a single search
663 there's much to be gained because many targets use the same
666 The metadata attribute 'mergekey' now takes one of three values 'no',
667 'required', 'optional' . And the resulting mergekey from metadata
668 is now ordered in the same way as metadata in the service definition.
669 Older Pazpar2 version use the order in which metadata appeared in a
672 The search argument 'filter' now offers a new operator ~ which does a
673 substring match. The = operator works as before: string match for
674 anything but pz:id, or target match for pz:id.
676 New setting pz:recordfilter. The value of this setting takes the
677 form name[~value]. This setting makes Pazpar2 ignore all retrieved
678 records that do not have the metadata element name with value substring
681 Pazpar2 allows YAZ log level to be set (option -v).
685 For WS responses Pazpar2 creates XML header. Exception: raw record.
687 Setting XML files are now stored in etc/settings instead of etc. This
688 reflects the layout with the Debian package layout.
690 Settings may be posted for command=settings. The POSTed settings must
691 have root element 'settings' like regular setting files. In order to be
692 recognized, the POST request must use Content-Type=text/xml.
694 A service may be posted for command=init. This service will be used
695 during the session. The service may have its own target settings,
696 ICU config, timeout, etc. In order to be recognized, the POST request
697 must use Content-Type=text/xml.
699 Timeout values may be given per-service. That's element 'timeout'
700 which takes three attribute values (a subset may be given): 'session',
701 'z3950_operation', 'z3950_session'. Option -T is no longer supported
702 - used to specify session timeout.
704 Option -t tests the Pazpar2 configuration and returns exit code
705 (0=success, non-zero=failure). In previous version of Pazpar2, -t
706 specified local settings.
708 In version 1.2.0 the configuration file - after include processing -
709 was dumped to stdout. Now, the configuration is only dumped to the
710 yaz log file if option -d is given.
714 Configuration may now have multiple server areas. This means that a
715 Pazpar2 instance may listen on multiple ports. Virtual hosting is not
716 yet supported - on a server basis. Configuration may also have multiple
717 services .. That is repeating service elements inside a server. Each
718 has an attribute 'id' which serves as service ID. This ID in turn may
719 be used in a Pazpar2 session, by specifying parameter service=ID for
720 command init. There can be at most one unnamed service inside a server
721 which can be referred to by not specifying an service ID for command
722 init (backwards compatible). In order to partition multiple servers and
723 services a new include directive has been added. This takes an attribute
724 'src' which specifies one or more sub-files. For example to include
725 service files, one might use:
726 <server >.. <include src=/"etc/pazpar2/conf.d/*.xml"/> .. </server>.
727 It is the intention that that completely makes the settings directive
730 Fix problem where the record command would wait forever if there were
731 no targets to wait for (activeclients == 0).
735 One result set is created per session (last search) rather than for
736 each connection which happen to be shared (bug #3009).
738 marc21 stylesheets changed for efficiency.
742 Session timeout may be specified on the command-line as option -T.
744 Pazpar2 may now be operated in a no-merged mode for records.. All records
745 will be considered unique. This mode is enabled if no mergekey is
746 generated by the normalization stylesheet (pz:xslt).
748 Pazpar2 caches original records from each target and the 'record' command
749 with offset returns the original record if 'syntax' and 'esn' are NOT
750 specified. This speeds up retrieval of original records but also means
751 that Pazpar2 uses more memory. The cached records will be freed when the
752 session terminates or a new search is executed.
754 Pazpar2 no longer uses its own ICU wrapper. Instead the ICU wrapper
755 library part of YAZ is used.
757 Added SRU client support.
759 Automatically computes pz:nativesyntax if not provided. Works for XML and
762 --- 1.0.13 2008/11/24
764 Command bytarget returns name of target (if defined).
766 --- 1.0.12 2008/11/04
768 Fixed bug #2021.. location now holds all brief elements.
770 --- 1.0.11 2008/10/15
772 Fixed check for application/x-www-form-urlencoded parameters.
774 --- 1.0.10 2008/10/14
776 Fixes for IE in pz2.js.
778 Fixed bug #2021: non-merged, brief meta data NOT included for command=show.
782 Changed the JS library pz2.js to use POST for long URL (+ params).
784 Added installation instructions for Windows. Note: NT services is
785 NOT available until we make a new release of YAZ.
787 Preserve order of repeated metadata fields (they were reversed before).
789 More MARC21 information extracted for metadata.
793 Fixed bug #1162: HTML entities are not escaped properly.
795 Native Windows port of Pazpar2. Makefile for Visual Studio provided.
799 Marc21 stylesheet updated to reflect multiple full text fields
803 Fixed bug in pz2.js WRT DOMElement attributes on IE.
805 Fixed bug 2100: Database wildcards not working
809 Added support for retrieval of records in binary.
811 Fixed bug 1794: Pazpar2 does not return valid XML.
813 Deal with ICU not returning sortkey (resulted in SEGV before).
817 JavaScript library pzw2.js throws error if WS response (from Pazpar2 or
818 other) is malformed (non-wellformed XML or missing Pazpar2 OK status).
820 Improved diagnostics when Pazpar2 HTTP decoding fails.
822 Pazpar2 requests may be POSTed as using Content-Type
823 application/x-www-form-urlencoded.
825 Pazpar2 honors LF in HTTP headers.
827 Handle targets that handle negative hit counts (should not happen, but it
832 ICU is used for tokenization and normalization of the following: mergekey,
833 sorting, relevance terms.
835 Debian package now enables ICU tokenization and normalization by default.
839 Exposed user setting values (i.e. non-pz: names) to the record systems in two
840 ways: Either as parameters to the normalization stylesheets (which would allow the
841 programmer to postprocess or use the values in any way) or after the normalization
842 step, in which case values are made part of the normalized record (and available for
843 sorting, termlists, display, or other interface-related use.
845 Implemented sorting by year.
847 Option -d dumps records to the current log file instead of stderr.
849 Fixes for compilation on cygwin.
851 Z39.50 client code uses pz:elements. pz:elements was recognized in
852 earlier Pazpar2 versions but it was not used for anything.
854 icu_chain_test is using fgets instead of getline - fixes compilation
857 Loosen the CCL query parsing so that Pazpar2 only returns error if _all_
858 query conversions fail (rather than _any_). This means targets that do
859 not support some fields are ignored in a search.
863 Improved handling of socket timeout for Z39.50 connections.
865 Misc documentation updates and spell fixes.
867 Debian package pazpar2 creates log rotate entry.
869 Debian package pazpar2-apache2 reloads Apache2.
871 jsdemo included in distribution. It illustrates the use of the js/pz2.js
876 First public release.