3 tmarc.xsl: yet another 773$g fix. Was broken in 1.6.1 as well.
5 Facility to change working directory for pazpar2 daemon. Option -wdir
6 sets working directory to dir. This facility is useful if core dumps
7 must be saved. In this case, the current working directory must be
8 writable by the running user, such as "nobody".
12 New configuration element <icu_chain> for <server>/<service> which
13 allows a named ICU rule (chain) to be defined. The names relevance,
14 sort, mergekey and facet are used for those operations. The definition
15 <icu_chain id="sort" locale="en"> .. </icu_chain>
17 <sort> <icu_chain locale="en> ... </icu_chain> </sort>
18 And so on.. for relevance, mergekey and facet as well. The latter
19 style is deprecated. The facet terms are normalized by the facet
20 rule by default. This may be changed on a metadata field basis by
21 defining the new attribute 'facetrule' for the metadata element.
23 <icu_chain id="myrule" locale="en"> ... </icu_chain>
24 <metadata name="author" termlist="yes" facetrule="myrule"/>
26 Preserve rorder for merged metadata. Fixes issue as reported by Sven
27 Porst: http://lists.indexdata.dk/pipermail/yazlist/2011-July/003230.html
29 tmarc.xsl: set journal-subpart to 773$ only.
33 Modify the behavior for the limit parameter (first defined in 1.5.7).
34 Mapping of limit searches are now defined by the new configuration item
35 pz:limitmap. Fix a dead-lock problem with the limit parameter.
37 Extend tmarc.xsl to extract 773$g data (OpenURL).
41 ICU default maps remove backquote (`).
43 Command 'search' takes limit parameter (optional). The limit parameter
44 allows a search to be limited one or more facets and the corresponding
45 values. This is for server side filtering.
47 Configure tweak: Use -lm for log(3) if needed
51 Fix a problem with skiparticle sortkey that could be completely
52 ignored (and reduced to "").
54 Fix dependency problem in pazpar2 RPM package (did not require
55 libyaz4 as it should).
59 Fix memory leak that occurred for command=termlist&name=xtargets .
61 Pazpar2 may save HTTP requests. Enabled by option -R.
65 Experimental support for DTIC DADS target. New dads-pz2.xsl.
67 Support for query_syntax (overrides the default for SRU | Z39.50)
69 Support for extraArgs (ZOOM "extraArgs" option) for targets
71 New commands: status-server and status-session
75 Fix for threaded runs: Client now have a copy of the database URL,
76 which can used after the database has been release from the client.
77 This makes the logging in the connection idle timeout of the client nicer (no NOURL) and should be thread-safe.
79 tmarc.xsl: Add journal-title-abbrev and full text.
81 cf.xsl: new fields: isbn, issn, journaltitle, volume, issue
83 Fix for cmd=record before search.
85 Session Logging clean up.
87 Fix wrong termlist factor when maxrecs is different from 100.
91 Fix missing pz:termlist_term_factor in settings.c messed up pz:preferred.
92 Term factor is default enabled but can be diseabled by
93 pz:termlist_term_factor=0
97 Add scaling of facet count. Currently always enabled, needs fixing.
98 Allow user-defined info for target suffix. This has no meaning in
99 Pazpar2 except to distinguish targets from each other. The suffix
100 data begins with #. For example z3950.indexdata.com/gils#Mydata
102 Added exact-match recordfilter; format name=value
106 SOLR support. Pazpar2 may operate as web service client for SOLR.
110 Fix for show command and block=1 (dead lock). Bug was introduced in
115 New RPM packages: pazpar2, pazpar2-js, pazpar2-doc. These have been
116 tested on CentOS 5.5 only.
120 Fix problem with result sets being removed from a client session
121 if the connection for it was resused by another session. Bug #3489.
123 New iphone UI for Pazpar2 (www/iphone).
127 Fixes for threaded operation.
129 New stylesheets for TurboMARC: tmarc.xsl and opac_turbomarc.xsl.
131 New example services in etc/services in source. In the Debian packages
132 these are located in /etc/pazpar2/services-available
134 Threaded mode operational on Windows. Requires Windows 7 or Windows
137 Default value of setting pz:max_connections is 0 which means that there
138 is no limit on number of connections.
142 Pazpar2 may operate in threaded mode. Enabled by element threads in
143 the configuration. See pazpar2_conf for details.
145 New setting setting: pz:max_connections. Setting pz:max_connections is
146 a limit of number of sockets to a host. When this limit is reached,
147 Pazpar2 will wait up to 5 seconds for a connection to becomes available.
148 The client will be marked Client_Error when it can not be searched
149 (other clients in a session may work). If pz:max_connections is not set
150 for a target, a value of 30 will be used. Note: the pz:max_connections
151 will only work in threaded mode.
153 pz2.js: JSON support for show.
155 Debian package: Enable default service, default.xml, before starting
156 Pazpar2 only if there is no service already in /etc/pazpar2/services-enabled.
160 Debian version depends on on libyaz4. Note that Pazpar2 will still
161 compile from source with YAZ 3.
163 Split services into separate files. The example configuration file
164 pazpar2.cfg.dist now includes a default service default.xml (part of
165 etc). And default.xml includes settings/edu.xml. The default.xml file,
166 not to be confused with settings/defaults.xml, is a template for jsdemo
167 and other services. The Debian package installs /etc/pazpar2/server.xml
168 which is now the main pazpar2 configuration (used to be called pazpar2.cfg).
169 server.xml includes services from /etc/pazpar2/services-enabled/*.xml .
170 The default.xml (from etc) is installed in /etc/pazpar2/services-available
171 and a symlink to it is created from services-enabled. The default.xml
172 service is unnamed and, thus, will be used by jsdemo and test1.
174 New setting pz:negotiation_charset. Patch from Andrei V. Toutoukine. The
175 new setting pz:negotiation_charset specifies character set for Z39.50 Init.
179 Support for additional fields in cf.xsl and pazpar2.conf.dist:
180 publisher, available, due, location (=locallocation), callno
181 (=callnumber), thumburl and score.
183 Describe pz:xslt and the auto setting.
185 Move mergekey definition away from the normalization stylesheets and
186 define a mergekey common for all target types in pazpar2.cfg.
188 Code update: Use the Odr_int type for hit counts. This is part of
189 YAZ 3.0.47 and later and so configure checks for that.
193 Metadata attribute 'skiparticle' also works for ICU based
194 normalization. (was only working for the non-ICU/ASCII before).
196 Command bytarget with argument settings=1 will show settings per
197 target.. This is to be able to verify correct settings and be able to
198 test that they are correct. The database settings array size is now
199 also stored.. Problems with database settings array is that if not
200 careful it will be too small (smaller than dictionary per-service
203 Make record list sorting stable by comparing mergekey for records if
204 relevance/title or other sorting criteria all match. This is merely to
205 ensure that our regressions tests works (reproducible output).
207 Relevance calculation changes: use a different denominator (length) for
208 per-field relevance scoring.. Instead of length of all ranked fields we
209 now use length of individual fields (as if they were individual "free"
210 text fields). This will ensure that documents with a long field with no
211 match (say description) will not "hurt" a title match.
213 Diagnostic member was not set on connection error. Fixed
217 Command search takes two optional parameters, startecs and maxrecs,
218 that specifies the start offset (0, 1, ...) and maximum number of records
219 to fetch for each target.
221 XSLTs + MARC maps are cached within a session so we don't re-parse
222 them over and over again. Even for a session with a single search
223 there's much to be gained because many targets use the same
226 The metadata attribute 'mergekey' now takes one of three values 'no',
227 'required', 'optional' . And the resulting mergekey from metadata
228 is now ordered in the same way as metadata in the service definition.
229 Older Pazpar2 version use the order in which metadata appeared in a
232 The search argument 'filter' now offers a new operator ~ which does a
233 substring match. The = operator works as before: string match for
234 anything but pz:id, or target match for pz:id.
236 New setting pz:recordfilter. The value of this setting takes the
237 form name[~value]. This setting makes Pazpar2 ignore all retrieved
238 records that do not have the metadata element name with value substring
241 Pazpar2 allows YAZ log level to be set (option -v).
245 For WS responses Pazpar2 creates XML header. Exception: raw record.
247 Setting XML files are now stored in etc/settings instead of etc. This
248 reflects the layout with the Debian package layout.
250 Settings may be posted for command=settings. The POSTed settings must
251 have root element 'settings' like regular setting files. In order to be
252 recognized, the POST request must use Content-Type=text/xml.
254 A service may be posted for command=init. This service will be used
255 during the session. The service may have its own target settings,
256 ICU config, timeout, etc. In order to be recognized, the POST request
257 must use Content-Type=text/xml.
259 Timeout values may be given per-service. That's element 'timeout'
260 which takes three attribute values (a subset may be given): 'session',
261 'z3950_operation', 'z3950_session'. Option -T is no longer supported
262 - used to specify session timeout.
264 Option -t tests the Pazpar2 configuration and returns exit code
265 (0=success, non-zero=failure). In previous version of Pazpar2, -t
266 specified local settings.
268 In version 1.2.0 the configuration file - after include processing -
269 was dumped to stdout. Now, the configuration is only dumped to the
270 yaz log file if option -d is given.
274 Configuration may now have multiple server areas. This means that a
275 Pazpar2 instance may listen on multiple ports. Virtual hosting is not
276 yet supported - on a server basis. Configuration may also have multiple
277 services .. That is repeating service elements inside a server. Each
278 has an attribute 'id' which serves as service ID. This ID in turn may
279 be used in a Pazpar2 session, by specifying parameter service=ID for
280 command init. There can be at most one unnamed service inside a server
281 which can be referred to by not specifying an service ID for command
282 init (backwards compatible). In order to partition multiple servers and
283 services a new include directive has been added. This takes an attribute
284 'src' which specifies one or more sub-files. For example to include
285 service files, one might use:
286 <server >.. <include src=/"etc/pazpar2/conf.d/*.xml"/> .. </server>.
287 It is the intention that that completely makes the settings directive
290 Fix problem where the record command would wait forever if there were
291 no targets to wait for (activeclients == 0).
295 One result set is created per session (last search) rather than for
296 each connection which happen to be shared (bug #3009).
298 marc21 stylesheets changed for efficiency.
302 Session timeout may be specified on the command-line as option -T.
304 Pazpar2 may now be operated in a no-merged mode for records.. All records
305 will be considered unique. This mode is enabled if no mergekey is
306 generated by the normalization stylesheet (pz:xslt).
308 Pazpar2 caches original records from each target and the 'record' command
309 with offset returns the original record if 'syntax' and 'esn' are NOT
310 specified. This speeds up retrieval of original records but also means
311 that Pazpar2 uses more memory. The cached records will be freed when the
312 session terminates or a new search is executed.
314 Pazpar2 no longer uses its own ICU wrapper. Instead the ICU wrapper
315 library part of YAZ is used.
317 Added SRU client support.
319 Automatically computes pz:nativesyntax if not provided. Works for XML and
322 --- 1.0.13 2008/11/24
324 Command bytarget returns name of target (if defined).
326 --- 1.0.12 2008/11/04
328 Fixed bug #2021.. location now holds all brief elements.
330 --- 1.0.11 2008/10/15
332 Fixed check for application/x-www-form-urlencoded parameters.
334 --- 1.0.10 2008/10/14
336 Fixes for IE in pz2.js.
338 Fixed bug #2021: non-merged, brief meta data NOT included for command=show.
342 Changed the JS library pz2.js to use POST for long URL (+ params).
344 Added installation instructions for Windows. Note: NT services is
345 NOT available until we make a new release of YAZ.
347 Preserve order of repeated metadata fields (they were reversed before).
349 More MARC21 information extracted for metadata.
353 Fixed bug #1162: HTML entities are not escaped properly.
355 Native Windows port of Pazpar2. Makefile for Visual Studio provided.
359 Marc21 stylesheet updated to reflect multiple full text fields
363 Fixed bug in pz2.js WRT DOMElement attributes on IE.
365 Fixed bug 2100: Database wildcards not working
369 Added support for retrieval of records in binary.
371 Fixed bug 1794: Pazpar2 does not return valid XML.
373 Deal with ICU not returning sortkey (resulted in SEGV before).
377 JavaScript library pzw2.js throws error if WS response (from Pazpar2 or
378 other) is malformed (non-wellformed XML or missing Pazpar2 OK status).
380 Improved diagnostics when Pazpar2 HTTP decoding fails.
382 Pazpar2 requests may be POSTed as using Content-Type
383 application/x-www-form-urlencoded.
385 Pazpar2 honors LF in HTTP headers.
387 Handle targets that handle negative hit counts (should not happen, but it
392 ICU is used for tokenization and normalization of the following: mergekey,
393 sorting, relevance terms.
395 Debian package now enables ICU tokenization and normalization by default.
399 Exposed user setting values (i.e. non-pz: names) to the record systems in two
400 ways: Either as parameters to the normalization stylesheets (which would allow the
401 programmer to postprocess or use the values in any way) or after the normalization
402 step, in which case values are made part of the normalized record (and available for
403 sorting, termlists, display, or other interface-related use.
405 Implemented sorting by year.
407 Option -d dumps records to the current log file instead of stderr.
409 Fixes for compilation on cygwin.
411 Z39.50 client code uses pz:elements. pz:elements was recognized in
412 earlier Pazpar2 versions but it was not used for anything.
414 icu_chain_test is using fgets instead of getline - fixes compilation
417 Loosen the CCL query parsing so that Pazpar2 only returns error if _all_
418 query conversions fail (rather than _any_). This means targets that do
419 not support some fields are ignored in a search.
423 Improved handling of socket timeout for Z39.50 connections.
425 Misc documentation updates and spell fixes.
427 Debian package pazpar2 creates log rotate entry.
429 Debian package pazpar2-apache2 reloads Apache2.
431 jsdemo included in distribution. It illustrates the use of the js/pz2.js
436 First public release.