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