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