3 Add scaling of facet count. Currently always enabled, needs fixing.
4 Allow user-defined info for target suffix. This has no meaning in
5 Pazpar2 except to distinguish targets from each other. The suffix
6 data begins with #. For example z3950.indexdata.com/gils#Mydata
8 Added exact-match recordfilter; format name=value
12 SOLR support. Pazpar2 may operate as web service client for SOLR.
16 Fix for show command and block=1 (dead lock). Bug was introduced in
21 New RPM packages: pazpar2, pazpar2-js, pazpar2-doc. These have been
22 tested on CentOS 5.5 only.
26 Fix problem with result sets being removed from a client session
27 if the connection for it was resused by another session. Bug #3489.
29 New iphone UI for Pazpar2 (www/iphone).
33 Fixes for threaded operation.
35 New stylesheets for TurboMARC: tmarc.xsl and opac_turbomarc.xsl.
37 New example services in etc/services in source. In the Debian packages
38 these are located in /etc/pazpar2/services-available
40 Threaded mode operational on Windows. Requires Windows 7 or Windows
43 Default value of setting pz:max_connections is 0 which means that there
44 is no limit on number of connections.
48 Pazpar2 may operate in threaded mode. Enabled by element threads in
49 the configuration. See pazpar2_conf for details.
51 New setting setting: pz:max_connections. Setting pz:max_connections is
52 a limit of number of sockets to a host. When this limit is reached,
53 Pazpar2 will wait up to 5 seconds for a connection to becomes available.
54 The client will be marked Client_Error when it can not be searched
55 (other clients in a session may work). If pz:max_connections is not set
56 for a target, a value of 30 will be used. Note: the pz:max_connections
57 will only work in threaded mode.
59 pz2.js: JSON support for show.
61 Debian package: Enable default service, default.xml, before starting
62 Pazpar2 only if there is no service already in /etc/pazpar2/services-enabled.
66 Debian version depends on on libyaz4. Note that Pazpar2 will still
67 compile from source with YAZ 3.
69 Split services into separate files. The example configuration file
70 pazpar2.cfg.dist now includes a default service default.xml (part of
71 etc). And default.xml includes settings/edu.xml. The default.xml file,
72 not to be confused with settings/defaults.xml, is a template for jsdemo
73 and other services. The Debian package installs /etc/pazpar2/server.xml
74 which is now the main pazpar2 configuration (used to be called pazpar2.cfg).
75 server.xml includes services from /etc/pazpar2/services-enabled/*.xml .
76 The default.xml (from etc) is installed in /etc/pazpar2/services-available
77 and a symlink to it is created from services-enabled. The default.xml
78 service is unnamed and, thus, will be used by jsdemo and test1.
80 New setting pz:negotiation_charset. Patch from Andrei V. Toutoukine. The
81 new setting pz:negotiation_charset specifies character set for Z39.50 Init.
85 Support for additional fields in cf.xsl and pazpar2.conf.dist:
86 publisher, available, due, location (=locallocation), callno
87 (=callnumber), thumburl and score.
89 Describe pz:xslt and the auto setting.
91 Move mergekey definition away from the normalization stylesheets and
92 define a mergekey common for all target types in pazpar2.cfg.
94 Code update: Use the Odr_int type for hit counts. This is part of
95 YAZ 3.0.47 and later and so configure checks for that.
99 Metadata attribute 'skiparticle' also works for ICU based
100 normalization. (was only working for the non-ICU/ASCII before).
102 Command bytarget with argument settings=1 will show settings per
103 target.. This is to be able to verify correct settings and be able to
104 test that they are correct. The database settings array size is now
105 also stored.. Problems with database settings array is that if not
106 careful it will be too small (smaller than dictionary per-service
109 Make record list sorting stable by comparing mergekey for records if
110 relevance/title or other sorting criteria all match. This is merely to
111 ensure that our regressions tests works (reproducible output).
113 Relevance calculation changes: use a different denominator (length) for
114 per-field relevance scoring.. Instead of length of all ranked fields we
115 now use length of individual fields (as if they were individual "free"
116 text fields). This will ensure that documents with a long field with no
117 match (say description) will not "hurt" a title match.
119 Diagnostic member was not set on connection error. Fixed
123 Command search takes two optional parameters, startecs and maxrecs,
124 that specifies the start offset (0, 1, ...) and maximum number of records
125 to fetch for each target.
127 XSLTs + MARC maps are cached within a session so we don't re-parse
128 them over and over again. Even for a session with a single search
129 there's much to be gained because many targets use the same
132 The metadata attribute 'mergekey' now takes one of three values 'no',
133 'required', 'optional' . And the resulting mergekey from metadata
134 is now ordered in the same way as metadata in the service definition.
135 Older Pazpar2 version use the order in which metadata appeared in a
138 The search argument 'filter' now offers a new operator ~ which does a
139 substring match. The = operator works as before: string match for
140 anything but pz:id, or target match for pz:id.
142 New setting pz:recordfilter. The value of this setting takes the
143 form name[~value]. This setting makes Pazpar2 ignore all retrieved
144 records that do not have the metadata element name with value substring
147 Pazpar2 allows YAZ log level to be set (option -v).
151 For WS responses Pazpar2 creates XML header. Exception: raw record.
153 Setting XML files are now stored in etc/settings instead of etc. This
154 reflects the layout with the Debian package layout.
156 Settings may be posted for command=settings. The POSTed settings must
157 have root element 'settings' like regular setting files. In order to be
158 recognized, the POST request must use Content-Type=text/xml.
160 A service may be posted for command=init. This service will be used
161 during the session. The service may have its own target settings,
162 ICU config, timeout, etc. In order to be recognized, the POST request
163 must use Content-Type=text/xml.
165 Timeout values may be given per-service. That's element 'timeout'
166 which takes three attribute values (a subset may be given): 'session',
167 'z3950_operation', 'z3950_session'. Option -T is no longer supported
168 - used to specify session timeout.
170 Option -t tests the Pazpar2 configuration and returns exit code
171 (0=success, non-zero=failure). In previous version of Pazpar2, -t
172 specified local settings.
174 In version 1.2.0 the configuration file - after include processing -
175 was dumped to stdout. Now, the configuration is only dumped to the
176 yaz log file if option -d is given.
180 Configuration may now have multiple server areas. This means that a
181 Pazpar2 instance may listen on multiple ports. Virtual hosting is not
182 yet supported - on a server basis. Configuration may also have multiple
183 services .. That is repeating service elements inside a server. Each
184 has an attribute 'id' which serves as service ID. This ID in turn may
185 be used in a Pazpar2 session, by specifying parameter service=ID for
186 command init. There can be at most one unnamed service inside a server
187 which can be referred to by not specifying an service ID for command
188 init (backwards compatible). In order to partition multiple servers and
189 services a new include directive has been added. This takes an attribute
190 'src' which specifies one or more sub-files. For example to include
191 service files, one might use:
192 <server >.. <include src=/"etc/pazpar2/conf.d/*.xml"/> .. </server>.
193 It is the intention that that completely makes the settings directive
196 Fix problem where the record command would wait forever if there were
197 no targets to wait for (activeclients == 0).
201 One result set is created per session (last search) rather than for
202 each connection which happen to be shared (bug #3009).
204 marc21 stylesheets changed for efficiency.
208 Session timeout may be specified on the command-line as option -T.
210 Pazpar2 may now be operated in a no-merged mode for records.. All records
211 will be considered unique. This mode is enabled if no mergekey is
212 generated by the normalization stylesheet (pz:xslt).
214 Pazpar2 caches original records from each target and the 'record' command
215 with offset returns the original record if 'syntax' and 'esn' are NOT
216 specified. This speeds up retrieval of original records but also means
217 that Pazpar2 uses more memory. The cached records will be freed when the
218 session terminates or a new search is executed.
220 Pazpar2 no longer uses its own ICU wrapper. Instead the ICU wrapper
221 library part of YAZ is used.
223 Added SRU client support.
225 Automatically computes pz:nativesyntax if not provided. Works for XML and
228 --- 1.0.13 2008/11/24
230 Command bytarget returns name of target (if defined).
232 --- 1.0.12 2008/11/04
234 Fixed bug #2021.. location now holds all brief elements.
236 --- 1.0.11 2008/10/15
238 Fixed check for application/x-www-form-urlencoded parameters.
240 --- 1.0.10 2008/10/14
242 Fixes for IE in pz2.js.
244 Fixed bug #2021: non-merged, brief meta data NOT included for command=show.
248 Changed the JS library pz2.js to use POST for long URL (+ params).
250 Added installation instructions for Windows. Note: NT services is
251 NOT available until we make a new release of YAZ.
253 Preserve order of repeated metadata fields (they were reversed before).
255 More MARC21 information extracted for metadata.
259 Fixed bug #1162: HTML entities are not escaped properly.
261 Native Windows port of Pazpar2. Makefile for Visual Studio provided.
265 Marc21 stylesheet updated to reflect multiple full text fields
269 Fixed bug in pz2.js WRT DOMElement attributes on IE.
271 Fixed bug 2100: Database wildcards not working
275 Added support for retrieval of records in binary.
277 Fixed bug 1794: Pazpar2 does not return valid XML.
279 Deal with ICU not returning sortkey (resulted in SEGV before).
283 JavaScript library pzw2.js throws error if WS response (from Pazpar2 or
284 other) is malformed (non-wellformed XML or missing Pazpar2 OK status).
286 Improved diagnostics when Pazpar2 HTTP decoding fails.
288 Pazpar2 requests may be POSTed as using Content-Type
289 application/x-www-form-urlencoded.
291 Pazpar2 honors LF in HTTP headers.
293 Handle targets that handle negative hit counts (should not happen, but it
298 ICU is used for tokenization and normalization of the following: mergekey,
299 sorting, relevance terms.
301 Debian package now enables ICU tokenization and normalization by default.
305 Exposed user setting values (i.e. non-pz: names) to the record systems in two
306 ways: Either as parameters to the normalization stylesheets (which would allow the
307 programmer to postprocess or use the values in any way) or after the normalization
308 step, in which case values are made part of the normalized record (and available for
309 sorting, termlists, display, or other interface-related use.
311 Implemented sorting by year.
313 Option -d dumps records to the current log file instead of stderr.
315 Fixes for compilation on cygwin.
317 Z39.50 client code uses pz:elements. pz:elements was recognized in
318 earlier Pazpar2 versions but it was not used for anything.
320 icu_chain_test is using fgets instead of getline - fixes compilation
323 Loosen the CCL query parsing so that Pazpar2 only returns error if _all_
324 query conversions fail (rather than _any_). This means targets that do
325 not support some fields are ignored in a search.
329 Improved handling of socket timeout for Z39.50 connections.
331 Misc documentation updates and spell fixes.
333 Debian package pazpar2 creates log rotate entry.
335 Debian package pazpar2-apache2 reloads Apache2.
337 jsdemo included in distribution. It illustrates the use of the js/pz2.js
342 First public release.