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