3 Modify the behavior for the limit parameter (first defined in 1.5.7).
4 Mapping of limit searches are now defined by the new configuration item
5 pz:limitmap. Fix a dead-lock problem with the limit parameter.
7 Extend tmarc.xsl to extract 773$g data (OpenURL).
11 ICU default maps remove backquote (`).
13 Command 'search' takes limit parameter (optional). The limit parameter
14 allows a search to be limited one or more facets and the corresponding
15 values. This is for server side filtering.
17 Configure tweak: Use -lm for log(3) if needed
21 Fix a problem with skiparticle sortkey that could be completely
22 ignored (and reduced to "").
24 Fix dependency problem in pazpar2 RPM package (did not require
25 libyaz4 as it should).
29 Fix memory leak that occurred for command=termlist&name=xtargets .
31 Pazpar2 may save HTTP requests. Enabled by option -R.
35 Experimental support for DTIC DADS target. New dads-pz2.xsl.
37 Support for query_syntax (overrides the default for SRU | Z39.50)
39 Support for extraArgs (ZOOM "extraArgs" option) for targets
41 New commands: status-server and status-session
45 Fix for threaded runs: Client now have a copy of the database URL,
46 which can used after the database has been release from the client.
47 This makes the logging in the connection idle timeout of the client nicer (no NOURL) and should be thread-safe.
49 tmarc.xsl: Add journal-title-abbrev and full text.
51 cf.xsl: new fields: isbn, issn, journaltitle, volume, issue
53 Fix for cmd=record before search.
55 Session Logging clean up.
57 Fix wrong termlist factor when maxrecs is different from 100.
61 Fix missing pz:termlist_term_factor in settings.c messed up pz:preferred.
62 Term factor is default enabled but can be diseabled by
63 pz:termlist_term_factor=0
67 Add scaling of facet count. Currently always enabled, needs fixing.
68 Allow user-defined info for target suffix. This has no meaning in
69 Pazpar2 except to distinguish targets from each other. The suffix
70 data begins with #. For example z3950.indexdata.com/gils#Mydata
72 Added exact-match recordfilter; format name=value
76 SOLR support. Pazpar2 may operate as web service client for SOLR.
80 Fix for show command and block=1 (dead lock). Bug was introduced in
85 New RPM packages: pazpar2, pazpar2-js, pazpar2-doc. These have been
86 tested on CentOS 5.5 only.
90 Fix problem with result sets being removed from a client session
91 if the connection for it was resused by another session. Bug #3489.
93 New iphone UI for Pazpar2 (www/iphone).
97 Fixes for threaded operation.
99 New stylesheets for TurboMARC: tmarc.xsl and opac_turbomarc.xsl.
101 New example services in etc/services in source. In the Debian packages
102 these are located in /etc/pazpar2/services-available
104 Threaded mode operational on Windows. Requires Windows 7 or Windows
107 Default value of setting pz:max_connections is 0 which means that there
108 is no limit on number of connections.
112 Pazpar2 may operate in threaded mode. Enabled by element threads in
113 the configuration. See pazpar2_conf for details.
115 New setting setting: pz:max_connections. Setting pz:max_connections is
116 a limit of number of sockets to a host. When this limit is reached,
117 Pazpar2 will wait up to 5 seconds for a connection to becomes available.
118 The client will be marked Client_Error when it can not be searched
119 (other clients in a session may work). If pz:max_connections is not set
120 for a target, a value of 30 will be used. Note: the pz:max_connections
121 will only work in threaded mode.
123 pz2.js: JSON support for show.
125 Debian package: Enable default service, default.xml, before starting
126 Pazpar2 only if there is no service already in /etc/pazpar2/services-enabled.
130 Debian version depends on on libyaz4. Note that Pazpar2 will still
131 compile from source with YAZ 3.
133 Split services into separate files. The example configuration file
134 pazpar2.cfg.dist now includes a default service default.xml (part of
135 etc). And default.xml includes settings/edu.xml. The default.xml file,
136 not to be confused with settings/defaults.xml, is a template for jsdemo
137 and other services. The Debian package installs /etc/pazpar2/server.xml
138 which is now the main pazpar2 configuration (used to be called pazpar2.cfg).
139 server.xml includes services from /etc/pazpar2/services-enabled/*.xml .
140 The default.xml (from etc) is installed in /etc/pazpar2/services-available
141 and a symlink to it is created from services-enabled. The default.xml
142 service is unnamed and, thus, will be used by jsdemo and test1.
144 New setting pz:negotiation_charset. Patch from Andrei V. Toutoukine. The
145 new setting pz:negotiation_charset specifies character set for Z39.50 Init.
149 Support for additional fields in cf.xsl and pazpar2.conf.dist:
150 publisher, available, due, location (=locallocation), callno
151 (=callnumber), thumburl and score.
153 Describe pz:xslt and the auto setting.
155 Move mergekey definition away from the normalization stylesheets and
156 define a mergekey common for all target types in pazpar2.cfg.
158 Code update: Use the Odr_int type for hit counts. This is part of
159 YAZ 3.0.47 and later and so configure checks for that.
163 Metadata attribute 'skiparticle' also works for ICU based
164 normalization. (was only working for the non-ICU/ASCII before).
166 Command bytarget with argument settings=1 will show settings per
167 target.. This is to be able to verify correct settings and be able to
168 test that they are correct. The database settings array size is now
169 also stored.. Problems with database settings array is that if not
170 careful it will be too small (smaller than dictionary per-service
173 Make record list sorting stable by comparing mergekey for records if
174 relevance/title or other sorting criteria all match. This is merely to
175 ensure that our regressions tests works (reproducible output).
177 Relevance calculation changes: use a different denominator (length) for
178 per-field relevance scoring.. Instead of length of all ranked fields we
179 now use length of individual fields (as if they were individual "free"
180 text fields). This will ensure that documents with a long field with no
181 match (say description) will not "hurt" a title match.
183 Diagnostic member was not set on connection error. Fixed
187 Command search takes two optional parameters, startecs and maxrecs,
188 that specifies the start offset (0, 1, ...) and maximum number of records
189 to fetch for each target.
191 XSLTs + MARC maps are cached within a session so we don't re-parse
192 them over and over again. Even for a session with a single search
193 there's much to be gained because many targets use the same
196 The metadata attribute 'mergekey' now takes one of three values 'no',
197 'required', 'optional' . And the resulting mergekey from metadata
198 is now ordered in the same way as metadata in the service definition.
199 Older Pazpar2 version use the order in which metadata appeared in a
202 The search argument 'filter' now offers a new operator ~ which does a
203 substring match. The = operator works as before: string match for
204 anything but pz:id, or target match for pz:id.
206 New setting pz:recordfilter. The value of this setting takes the
207 form name[~value]. This setting makes Pazpar2 ignore all retrieved
208 records that do not have the metadata element name with value substring
211 Pazpar2 allows YAZ log level to be set (option -v).
215 For WS responses Pazpar2 creates XML header. Exception: raw record.
217 Setting XML files are now stored in etc/settings instead of etc. This
218 reflects the layout with the Debian package layout.
220 Settings may be posted for command=settings. The POSTed settings must
221 have root element 'settings' like regular setting files. In order to be
222 recognized, the POST request must use Content-Type=text/xml.
224 A service may be posted for command=init. This service will be used
225 during the session. The service may have its own target settings,
226 ICU config, timeout, etc. In order to be recognized, the POST request
227 must use Content-Type=text/xml.
229 Timeout values may be given per-service. That's element 'timeout'
230 which takes three attribute values (a subset may be given): 'session',
231 'z3950_operation', 'z3950_session'. Option -T is no longer supported
232 - used to specify session timeout.
234 Option -t tests the Pazpar2 configuration and returns exit code
235 (0=success, non-zero=failure). In previous version of Pazpar2, -t
236 specified local settings.
238 In version 1.2.0 the configuration file - after include processing -
239 was dumped to stdout. Now, the configuration is only dumped to the
240 yaz log file if option -d is given.
244 Configuration may now have multiple server areas. This means that a
245 Pazpar2 instance may listen on multiple ports. Virtual hosting is not
246 yet supported - on a server basis. Configuration may also have multiple
247 services .. That is repeating service elements inside a server. Each
248 has an attribute 'id' which serves as service ID. This ID in turn may
249 be used in a Pazpar2 session, by specifying parameter service=ID for
250 command init. There can be at most one unnamed service inside a server
251 which can be referred to by not specifying an service ID for command
252 init (backwards compatible). In order to partition multiple servers and
253 services a new include directive has been added. This takes an attribute
254 'src' which specifies one or more sub-files. For example to include
255 service files, one might use:
256 <server >.. <include src=/"etc/pazpar2/conf.d/*.xml"/> .. </server>.
257 It is the intention that that completely makes the settings directive
260 Fix problem where the record command would wait forever if there were
261 no targets to wait for (activeclients == 0).
265 One result set is created per session (last search) rather than for
266 each connection which happen to be shared (bug #3009).
268 marc21 stylesheets changed for efficiency.
272 Session timeout may be specified on the command-line as option -T.
274 Pazpar2 may now be operated in a no-merged mode for records.. All records
275 will be considered unique. This mode is enabled if no mergekey is
276 generated by the normalization stylesheet (pz:xslt).
278 Pazpar2 caches original records from each target and the 'record' command
279 with offset returns the original record if 'syntax' and 'esn' are NOT
280 specified. This speeds up retrieval of original records but also means
281 that Pazpar2 uses more memory. The cached records will be freed when the
282 session terminates or a new search is executed.
284 Pazpar2 no longer uses its own ICU wrapper. Instead the ICU wrapper
285 library part of YAZ is used.
287 Added SRU client support.
289 Automatically computes pz:nativesyntax if not provided. Works for XML and
292 --- 1.0.13 2008/11/24
294 Command bytarget returns name of target (if defined).
296 --- 1.0.12 2008/11/04
298 Fixed bug #2021.. location now holds all brief elements.
300 --- 1.0.11 2008/10/15
302 Fixed check for application/x-www-form-urlencoded parameters.
304 --- 1.0.10 2008/10/14
306 Fixes for IE in pz2.js.
308 Fixed bug #2021: non-merged, brief meta data NOT included for command=show.
312 Changed the JS library pz2.js to use POST for long URL (+ params).
314 Added installation instructions for Windows. Note: NT services is
315 NOT available until we make a new release of YAZ.
317 Preserve order of repeated metadata fields (they were reversed before).
319 More MARC21 information extracted for metadata.
323 Fixed bug #1162: HTML entities are not escaped properly.
325 Native Windows port of Pazpar2. Makefile for Visual Studio provided.
329 Marc21 stylesheet updated to reflect multiple full text fields
333 Fixed bug in pz2.js WRT DOMElement attributes on IE.
335 Fixed bug 2100: Database wildcards not working
339 Added support for retrieval of records in binary.
341 Fixed bug 1794: Pazpar2 does not return valid XML.
343 Deal with ICU not returning sortkey (resulted in SEGV before).
347 JavaScript library pzw2.js throws error if WS response (from Pazpar2 or
348 other) is malformed (non-wellformed XML or missing Pazpar2 OK status).
350 Improved diagnostics when Pazpar2 HTTP decoding fails.
352 Pazpar2 requests may be POSTed as using Content-Type
353 application/x-www-form-urlencoded.
355 Pazpar2 honors LF in HTTP headers.
357 Handle targets that handle negative hit counts (should not happen, but it
362 ICU is used for tokenization and normalization of the following: mergekey,
363 sorting, relevance terms.
365 Debian package now enables ICU tokenization and normalization by default.
369 Exposed user setting values (i.e. non-pz: names) to the record systems in two
370 ways: Either as parameters to the normalization stylesheets (which would allow the
371 programmer to postprocess or use the values in any way) or after the normalization
372 step, in which case values are made part of the normalized record (and available for
373 sorting, termlists, display, or other interface-related use.
375 Implemented sorting by year.
377 Option -d dumps records to the current log file instead of stderr.
379 Fixes for compilation on cygwin.
381 Z39.50 client code uses pz:elements. pz:elements was recognized in
382 earlier Pazpar2 versions but it was not used for anything.
384 icu_chain_test is using fgets instead of getline - fixes compilation
387 Loosen the CCL query parsing so that Pazpar2 only returns error if _all_
388 query conversions fail (rather than _any_). This means targets that do
389 not support some fields are ignored in a search.
393 Improved handling of socket timeout for Z39.50 connections.
395 Misc documentation updates and spell fixes.
397 Debian package pazpar2 creates log rotate entry.
399 Debian package pazpar2-apache2 reloads Apache2.
401 jsdemo included in distribution. It illustrates the use of the js/pz2.js
406 First public release.