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