3 Fixes for threaded operation.
5 New stylesheets for TurboMARC: tmarc.xsl and opac_turbomarc.xsl.
7 New example services in etc/services in source. In the Debian packages
8 these are located in /etc/pazpar2/services-available
10 Threaded mode operational on Windows. Requires Windows 7 or Windows
13 Default value of setting pz:max_connections is 0 which means that there
14 is no limit on number of connections.
18 Pazpar2 may operate in threaded mode. Enabled by element threads in
19 the configuration. See pazpar2_conf for details.
21 New setting setting: pz:max_connections. Setting pz:max_connections is
22 a limit of number of sockets to a host. When this limit is reached,
23 Pazpar2 will wait up to 5 seconds for a connection to becomes available.
24 The client will be marked Client_Error when it can not be searched
25 (other clients in a session may work). If pz:max_connections is not set
26 for a target, a value of 30 will be used. Note: the pz:max_connections
27 will only work in threaded mode.
29 pz2.js: JSON support for show.
31 Debian package: Enable default service, default.xml, before starting
32 Pazpar2 only if there is no service already in /etc/pazpar2/services-enabled.
36 Debian version depends on on libyaz4. Note that Pazpar2 will still
37 compile from source with YAZ 3.
39 Split services into separate files. The example configuration file
40 pazpar2.cfg.dist now includes a default service default.xml (part of
41 etc). And default.xml includes settings/edu.xml. The default.xml file,
42 not to be confused with settings/defaults.xml, is a template for jsdemo
43 and other services. The Debian package installs /etc/pazpar2/server.xml
44 which is now the main pazpar2 configuration (used to be called pazpar2.cfg).
45 server.xml includes services from /etc/pazpar2/services-enabled/*.xml .
46 The default.xml (from etc) is installed in /etc/pazpar2/services-available
47 and a symlink to it is created from services-enabled. The default.xml
48 service is unnamed and, thus, will be used by jsdemo and test1.
50 New setting pz:negotiation_charset. Patch from Andrei V. Toutoukine. The
51 new setting pz:negotiation_charset specifies character set for Z39.50 Init.
55 Support for additional fields in cf.xsl and pazpar2.conf.dist:
56 publisher, available, due, location (=locallocation), callno
57 (=callnumber), thumburl and score.
59 Describe pz:xslt and the auto setting.
61 Move mergekey definition away from the normalization stylesheets and
62 define a mergekey common for all target types in pazpar2.cfg.
64 Code update: Use the Odr_int type for hit counts. This is part of
65 YAZ 3.0.47 and later and so configure checks for that.
69 Metadata attribute 'skiparticle' also works for ICU based
70 normalization. (was only working for the non-ICU/ASCII before).
72 Command bytarget with argument settings=1 will show settings per
73 target.. This is to be able to verify correct settings and be able to
74 test that they are correct. The database settings array size is now
75 also stored.. Problems with database settings array is that if not
76 careful it will be too small (smaller than dictionary per-service
79 Make record list sorting stable by comparing mergekey for records if
80 relevance/title or other sorting criteria all match. This is merely to
81 ensure that our regressions tests works (reproducible output).
83 Relevance calculation changes: use a different denominator (length) for
84 per-field relevance scoring.. Instead of length of all ranked fields we
85 now use length of individual fields (as if they were individual "free"
86 text fields). This will ensure that documents with a long field with no
87 match (say description) will not "hurt" a title match.
89 Diagnostic member was not set on connection error. Fixed
93 Command search takes two optional parameters, startecs and maxrecs,
94 that specifies the start offset (0, 1, ...) and maximum number of records
95 to fetch for each target.
97 XSLTs + MARC maps are cached within a session so we don't re-parse
98 them over and over again. Even for a session with a single search
99 there's much to be gained because many targets use the same
102 The metadata attribute 'mergekey' now takes one of three values 'no',
103 'required', 'optional' . And the resulting mergekey from metadata
104 is now ordered in the same way as metadata in the service definition.
105 Older Pazpar2 version use the order in which metadata appeared in a
108 The search argument 'filter' now offers a new operator ~ which does a
109 substring match. The = operator works as before: string match for
110 anything but pz:id, or target match for pz:id.
112 New setting pz:recordfilter. The value of this setting takes the
113 form name[~value]. This setting makes Pazpar2 ignore all retrieved
114 records that do not have the metadata element name with value substring
117 Pazpar2 allows YAZ log level to be set (option -v).
121 For WS responses Pazpar2 creates XML header. Exception: raw record.
123 Setting XML files are now stored in etc/settings instead of etc. This
124 reflects the layout with the Debian package layout.
126 Settings may be posted for command=settings. The POSTed settings must
127 have root element 'settings' like regular setting files. In order to be
128 recognized, the POST request must use Content-Type=text/xml.
130 A service may be posted for command=init. This service will be used
131 during the session. The service may have its own target settings,
132 ICU config, timeout, etc. In order to be recognized, the POST request
133 must use Content-Type=text/xml.
135 Timeout values may be given per-service. That's element 'timeout'
136 which takes three attribute values (a subset may be given): 'session',
137 'z3950_operation', 'z3950_session'. Option -T is no longer supported
138 - used to specify session timeout.
140 Option -t tests the Pazpar2 configuration and returns exit code
141 (0=success, non-zero=failure). In previous version of Pazpar2, -t
142 specified local settings.
144 In version 1.2.0 the configuration file - after include processing -
145 was dumped to stdout. Now, the configuration is only dumped to the
146 yaz log file if option -d is given.
150 Configuration may now have multiple server areas. This means that a
151 Pazpar2 instance may listen on multiple ports. Virtual hosting is not
152 yet supported - on a server basis. Configuration may also have multiple
153 services .. That is repeating service elements inside a server. Each
154 has an attribute 'id' which serves as service ID. This ID in turn may
155 be used in a Pazpar2 session, by specifying parameter service=ID for
156 command init. There can be at most one unnamed service inside a server
157 which can be referred to by not specifying an service ID for command
158 init (backwards compatible). In order to partition multiple servers and
159 services a new include directive has been added. This takes an attribute
160 'src' which specifies one or more sub-files. For example to include
161 service files, one might use:
162 <server >.. <include src=/"etc/pazpar2/conf.d/*.xml"/> .. </server>.
163 It is the intention that that completely makes the settings directive
166 Fix problem where the record command would wait forever if there were
167 no targets to wait for (activeclients == 0).
171 One result set is created per session (last search) rather than for
172 each connection which happen to be shared (bug #3009).
174 marc21 stylesheets changed for efficiency.
178 Session timeout may be specified on the command-line as option -T.
180 Pazpar2 may now be operated in a no-merged mode for records.. All records
181 will be considered unique. This mode is enabled if no mergekey is
182 generated by the normalization stylesheet (pz:xslt).
184 Pazpar2 caches original records from each target and the 'record' command
185 with offset returns the original record if 'syntax' and 'esn' are NOT
186 specified. This speeds up retrieval of original records but also means
187 that Pazpar2 uses more memory. The cached records will be freed when the
188 session terminates or a new search is executed.
190 Pazpar2 no longer uses its own ICU wrapper. Instead the ICU wrapper
191 library part of YAZ is used.
193 Added SRU client support.
195 Automatically computes pz:nativesyntax if not provided. Works for XML and
198 --- 1.0.13 2008/11/24
200 Command bytarget returns name of target (if defined).
202 --- 1.0.12 2008/11/04
204 Fixed bug #2021.. location now holds all brief elements.
206 --- 1.0.11 2008/10/15
208 Fixed check for application/x-www-form-urlencoded parameters.
210 --- 1.0.10 2008/10/14
212 Fixes for IE in pz2.js.
214 Fixed bug #2021: non-merged, brief meta data NOT included for command=show.
218 Changed the JS library pz2.js to use POST for long URL (+ params).
220 Added installation instructions for Windows. Note: NT services is
221 NOT available until we make a new release of YAZ.
223 Preserve order of repeated metadata fields (they were reversed before).
225 More MARC21 information extracted for metadata.
229 Fixed bug #1162: HTML entities are not escaped properly.
231 Native Windows port of Pazpar2. Makefile for Visual Studio provided.
235 Marc21 stylesheet updated to reflect multiple full text fields
239 Fixed bug in pz2.js WRT DOMElement attributes on IE.
241 Fixed bug 2100: Database wildcards not working
245 Added support for retrieval of records in binary.
247 Fixed bug 1794: Pazpar2 does not return valid XML.
249 Deal with ICU not returning sortkey (resulted in SEGV before).
253 JavaScript library pzw2.js throws error if WS response (from Pazpar2 or
254 other) is malformed (non-wellformed XML or missing Pazpar2 OK status).
256 Improved diagnostics when Pazpar2 HTTP decoding fails.
258 Pazpar2 requests may be POSTed as using Content-Type
259 application/x-www-form-urlencoded.
261 Pazpar2 honors LF in HTTP headers.
263 Handle targets that handle negative hit counts (should not happen, but it
268 ICU is used for tokenization and normalization of the following: mergekey,
269 sorting, relevance terms.
271 Debian package now enables ICU tokenization and normalization by default.
275 Exposed user setting values (i.e. non-pz: names) to the record systems in two
276 ways: Either as parameters to the normalization stylesheets (which would allow the
277 programmer to postprocess or use the values in any way) or after the normalization
278 step, in which case values are made part of the normalized record (and available for
279 sorting, termlists, display, or other interface-related use.
281 Implemented sorting by year.
283 Option -d dumps records to the current log file instead of stderr.
285 Fixes for compilation on cygwin.
287 Z39.50 client code uses pz:elements. pz:elements was recognized in
288 earlier Pazpar2 versions but it was not used for anything.
290 icu_chain_test is using fgets instead of getline - fixes compilation
293 Loosen the CCL query parsing so that Pazpar2 only returns error if _all_
294 query conversions fail (rather than _any_). This means targets that do
295 not support some fields are ignored in a search.
299 Improved handling of socket timeout for Z39.50 connections.
301 Misc documentation updates and spell fixes.
303 Debian package pazpar2 creates log rotate entry.
305 Debian package pazpar2-apache2 reloads Apache2.
307 jsdemo included in distribution. It illustrates the use of the js/pz2.js
312 First public release.