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