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