3 Make termlist sorting stable. Terms with same frequency are now sorted by
4 their display name. This makes a pretty display and improves our
5 regression test because qsort is not a stable sort.
7 New sort parameter value 'position'. The 'position' sorts merged records
8 by their original position from the remote target. This is primarily useful
9 for debugging and may be used for targets that already perform some kind
10 of relevance ranking. Note that sort by default is decreasing; so to get
11 records in their original order sort=position:1 must be used.
15 tmarc.xsl: yet another 773$g fix. Was broken in 1.6.1 as well.
17 Facility to change working directory for pazpar2 daemon. Option -wdir
18 sets working directory to dir. This facility is useful if core dumps
19 must be saved. In this case, the current working directory must be
20 writable by the running user, such as "nobody".
24 New configuration element <icu_chain> for <server>/<service> which
25 allows a named ICU rule (chain) to be defined. The names relevance,
26 sort, mergekey and facet are used for those operations. The definition
27 <icu_chain id="sort" locale="en"> .. </icu_chain>
29 <sort> <icu_chain locale="en> ... </icu_chain> </sort>
30 And so on.. for relevance, mergekey and facet as well. The latter
31 style is deprecated. The facet terms are normalized by the facet
32 rule by default. This may be changed on a metadata field basis by
33 defining the new attribute 'facetrule' for the metadata element.
35 <icu_chain id="myrule" locale="en"> ... </icu_chain>
36 <metadata name="author" termlist="yes" facetrule="myrule"/>
38 Preserve rorder for merged metadata. Fixes issue as reported by Sven
39 Porst: http://lists.indexdata.dk/pipermail/yazlist/2011-July/003230.html
41 tmarc.xsl: set journal-subpart to 773$ only.
45 Modify the behavior for the limit parameter (first defined in 1.5.7).
46 Mapping of limit searches are now defined by the new configuration item
47 pz:limitmap. Fix a dead-lock problem with the limit parameter.
49 Extend tmarc.xsl to extract 773$g data (OpenURL).
53 ICU default maps remove backquote (`).
55 Command 'search' takes limit parameter (optional). The limit parameter
56 allows a search to be limited one or more facets and the corresponding
57 values. This is for server side filtering.
59 Configure tweak: Use -lm for log(3) if needed
63 Fix a problem with skiparticle sortkey that could be completely
64 ignored (and reduced to "").
66 Fix dependency problem in pazpar2 RPM package (did not require
67 libyaz4 as it should).
71 Fix memory leak that occurred for command=termlist&name=xtargets .
73 Pazpar2 may save HTTP requests. Enabled by option -R.
77 Experimental support for DTIC DADS target. New dads-pz2.xsl.
79 Support for query_syntax (overrides the default for SRU | Z39.50)
81 Support for extraArgs (ZOOM "extraArgs" option) for targets
83 New commands: status-server and status-session
87 Fix for threaded runs: Client now have a copy of the database URL,
88 which can used after the database has been release from the client.
89 This makes the logging in the connection idle timeout of the client nicer (no NOURL) and should be thread-safe.
91 tmarc.xsl: Add journal-title-abbrev and full text.
93 cf.xsl: new fields: isbn, issn, journaltitle, volume, issue
95 Fix for cmd=record before search.
97 Session Logging clean up.
99 Fix wrong termlist factor when maxrecs is different from 100.
103 Fix missing pz:termlist_term_factor in settings.c messed up pz:preferred.
104 Term factor is default enabled but can be diseabled by
105 pz:termlist_term_factor=0
109 Add scaling of facet count. Currently always enabled, needs fixing.
110 Allow user-defined info for target suffix. This has no meaning in
111 Pazpar2 except to distinguish targets from each other. The suffix
112 data begins with #. For example z3950.indexdata.com/gils#Mydata
114 Added exact-match recordfilter; format name=value
118 SOLR support. Pazpar2 may operate as web service client for SOLR.
122 Fix for show command and block=1 (dead lock). Bug was introduced in
127 New RPM packages: pazpar2, pazpar2-js, pazpar2-doc. These have been
128 tested on CentOS 5.5 only.
132 Fix problem with result sets being removed from a client session
133 if the connection for it was resused by another session. Bug #3489.
135 New iphone UI for Pazpar2 (www/iphone).
139 Fixes for threaded operation.
141 New stylesheets for TurboMARC: tmarc.xsl and opac_turbomarc.xsl.
143 New example services in etc/services in source. In the Debian packages
144 these are located in /etc/pazpar2/services-available
146 Threaded mode operational on Windows. Requires Windows 7 or Windows
149 Default value of setting pz:max_connections is 0 which means that there
150 is no limit on number of connections.
154 Pazpar2 may operate in threaded mode. Enabled by element threads in
155 the configuration. See pazpar2_conf for details.
157 New setting setting: pz:max_connections. Setting pz:max_connections is
158 a limit of number of sockets to a host. When this limit is reached,
159 Pazpar2 will wait up to 5 seconds for a connection to becomes available.
160 The client will be marked Client_Error when it can not be searched
161 (other clients in a session may work). If pz:max_connections is not set
162 for a target, a value of 30 will be used. Note: the pz:max_connections
163 will only work in threaded mode.
165 pz2.js: JSON support for show.
167 Debian package: Enable default service, default.xml, before starting
168 Pazpar2 only if there is no service already in /etc/pazpar2/services-enabled.
172 Debian version depends on on libyaz4. Note that Pazpar2 will still
173 compile from source with YAZ 3.
175 Split services into separate files. The example configuration file
176 pazpar2.cfg.dist now includes a default service default.xml (part of
177 etc). And default.xml includes settings/edu.xml. The default.xml file,
178 not to be confused with settings/defaults.xml, is a template for jsdemo
179 and other services. The Debian package installs /etc/pazpar2/server.xml
180 which is now the main pazpar2 configuration (used to be called pazpar2.cfg).
181 server.xml includes services from /etc/pazpar2/services-enabled/*.xml .
182 The default.xml (from etc) is installed in /etc/pazpar2/services-available
183 and a symlink to it is created from services-enabled. The default.xml
184 service is unnamed and, thus, will be used by jsdemo and test1.
186 New setting pz:negotiation_charset. Patch from Andrei V. Toutoukine. The
187 new setting pz:negotiation_charset specifies character set for Z39.50 Init.
191 Support for additional fields in cf.xsl and pazpar2.conf.dist:
192 publisher, available, due, location (=locallocation), callno
193 (=callnumber), thumburl and score.
195 Describe pz:xslt and the auto setting.
197 Move mergekey definition away from the normalization stylesheets and
198 define a mergekey common for all target types in pazpar2.cfg.
200 Code update: Use the Odr_int type for hit counts. This is part of
201 YAZ 3.0.47 and later and so configure checks for that.
205 Metadata attribute 'skiparticle' also works for ICU based
206 normalization. (was only working for the non-ICU/ASCII before).
208 Command bytarget with argument settings=1 will show settings per
209 target.. This is to be able to verify correct settings and be able to
210 test that they are correct. The database settings array size is now
211 also stored.. Problems with database settings array is that if not
212 careful it will be too small (smaller than dictionary per-service
215 Make record list sorting stable by comparing mergekey for records if
216 relevance/title or other sorting criteria all match. This is merely to
217 ensure that our regressions tests works (reproducible output).
219 Relevance calculation changes: use a different denominator (length) for
220 per-field relevance scoring.. Instead of length of all ranked fields we
221 now use length of individual fields (as if they were individual "free"
222 text fields). This will ensure that documents with a long field with no
223 match (say description) will not "hurt" a title match.
225 Diagnostic member was not set on connection error. Fixed
229 Command search takes two optional parameters, startecs and maxrecs,
230 that specifies the start offset (0, 1, ...) and maximum number of records
231 to fetch for each target.
233 XSLTs + MARC maps are cached within a session so we don't re-parse
234 them over and over again. Even for a session with a single search
235 there's much to be gained because many targets use the same
238 The metadata attribute 'mergekey' now takes one of three values 'no',
239 'required', 'optional' . And the resulting mergekey from metadata
240 is now ordered in the same way as metadata in the service definition.
241 Older Pazpar2 version use the order in which metadata appeared in a
244 The search argument 'filter' now offers a new operator ~ which does a
245 substring match. The = operator works as before: string match for
246 anything but pz:id, or target match for pz:id.
248 New setting pz:recordfilter. The value of this setting takes the
249 form name[~value]. This setting makes Pazpar2 ignore all retrieved
250 records that do not have the metadata element name with value substring
253 Pazpar2 allows YAZ log level to be set (option -v).
257 For WS responses Pazpar2 creates XML header. Exception: raw record.
259 Setting XML files are now stored in etc/settings instead of etc. This
260 reflects the layout with the Debian package layout.
262 Settings may be posted for command=settings. The POSTed settings must
263 have root element 'settings' like regular setting files. In order to be
264 recognized, the POST request must use Content-Type=text/xml.
266 A service may be posted for command=init. This service will be used
267 during the session. The service may have its own target settings,
268 ICU config, timeout, etc. In order to be recognized, the POST request
269 must use Content-Type=text/xml.
271 Timeout values may be given per-service. That's element 'timeout'
272 which takes three attribute values (a subset may be given): 'session',
273 'z3950_operation', 'z3950_session'. Option -T is no longer supported
274 - used to specify session timeout.
276 Option -t tests the Pazpar2 configuration and returns exit code
277 (0=success, non-zero=failure). In previous version of Pazpar2, -t
278 specified local settings.
280 In version 1.2.0 the configuration file - after include processing -
281 was dumped to stdout. Now, the configuration is only dumped to the
282 yaz log file if option -d is given.
286 Configuration may now have multiple server areas. This means that a
287 Pazpar2 instance may listen on multiple ports. Virtual hosting is not
288 yet supported - on a server basis. Configuration may also have multiple
289 services .. That is repeating service elements inside a server. Each
290 has an attribute 'id' which serves as service ID. This ID in turn may
291 be used in a Pazpar2 session, by specifying parameter service=ID for
292 command init. There can be at most one unnamed service inside a server
293 which can be referred to by not specifying an service ID for command
294 init (backwards compatible). In order to partition multiple servers and
295 services a new include directive has been added. This takes an attribute
296 'src' which specifies one or more sub-files. For example to include
297 service files, one might use:
298 <server >.. <include src=/"etc/pazpar2/conf.d/*.xml"/> .. </server>.
299 It is the intention that that completely makes the settings directive
302 Fix problem where the record command would wait forever if there were
303 no targets to wait for (activeclients == 0).
307 One result set is created per session (last search) rather than for
308 each connection which happen to be shared (bug #3009).
310 marc21 stylesheets changed for efficiency.
314 Session timeout may be specified on the command-line as option -T.
316 Pazpar2 may now be operated in a no-merged mode for records.. All records
317 will be considered unique. This mode is enabled if no mergekey is
318 generated by the normalization stylesheet (pz:xslt).
320 Pazpar2 caches original records from each target and the 'record' command
321 with offset returns the original record if 'syntax' and 'esn' are NOT
322 specified. This speeds up retrieval of original records but also means
323 that Pazpar2 uses more memory. The cached records will be freed when the
324 session terminates or a new search is executed.
326 Pazpar2 no longer uses its own ICU wrapper. Instead the ICU wrapper
327 library part of YAZ is used.
329 Added SRU client support.
331 Automatically computes pz:nativesyntax if not provided. Works for XML and
334 --- 1.0.13 2008/11/24
336 Command bytarget returns name of target (if defined).
338 --- 1.0.12 2008/11/04
340 Fixed bug #2021.. location now holds all brief elements.
342 --- 1.0.11 2008/10/15
344 Fixed check for application/x-www-form-urlencoded parameters.
346 --- 1.0.10 2008/10/14
348 Fixes for IE in pz2.js.
350 Fixed bug #2021: non-merged, brief meta data NOT included for command=show.
354 Changed the JS library pz2.js to use POST for long URL (+ params).
356 Added installation instructions for Windows. Note: NT services is
357 NOT available until we make a new release of YAZ.
359 Preserve order of repeated metadata fields (they were reversed before).
361 More MARC21 information extracted for metadata.
365 Fixed bug #1162: HTML entities are not escaped properly.
367 Native Windows port of Pazpar2. Makefile for Visual Studio provided.
371 Marc21 stylesheet updated to reflect multiple full text fields
375 Fixed bug in pz2.js WRT DOMElement attributes on IE.
377 Fixed bug 2100: Database wildcards not working
381 Added support for retrieval of records in binary.
383 Fixed bug 1794: Pazpar2 does not return valid XML.
385 Deal with ICU not returning sortkey (resulted in SEGV before).
389 JavaScript library pzw2.js throws error if WS response (from Pazpar2 or
390 other) is malformed (non-wellformed XML or missing Pazpar2 OK status).
392 Improved diagnostics when Pazpar2 HTTP decoding fails.
394 Pazpar2 requests may be POSTed as using Content-Type
395 application/x-www-form-urlencoded.
397 Pazpar2 honors LF in HTTP headers.
399 Handle targets that handle negative hit counts (should not happen, but it
404 ICU is used for tokenization and normalization of the following: mergekey,
405 sorting, relevance terms.
407 Debian package now enables ICU tokenization and normalization by default.
411 Exposed user setting values (i.e. non-pz: names) to the record systems in two
412 ways: Either as parameters to the normalization stylesheets (which would allow the
413 programmer to postprocess or use the values in any way) or after the normalization
414 step, in which case values are made part of the normalized record (and available for
415 sorting, termlists, display, or other interface-related use.
417 Implemented sorting by year.
419 Option -d dumps records to the current log file instead of stderr.
421 Fixes for compilation on cygwin.
423 Z39.50 client code uses pz:elements. pz:elements was recognized in
424 earlier Pazpar2 versions but it was not used for anything.
426 icu_chain_test is using fgets instead of getline - fixes compilation
429 Loosen the CCL query parsing so that Pazpar2 only returns error if _all_
430 query conversions fail (rather than _any_). This means targets that do
431 not support some fields are ignored in a search.
435 Improved handling of socket timeout for Z39.50 connections.
437 Misc documentation updates and spell fixes.
439 Debian package pazpar2 creates log rotate entry.
441 Debian package pazpar2-apache2 reloads Apache2.
443 jsdemo included in distribution. It illustrates the use of the js/pz2.js
448 First public release.