+--- 1.3.0 2010/01/25
+
+Debian version depends on on libyaz4. Note that Pazpar2 will still
+compile from source with YAZ 3.
+
+Split services into separate files. The example configuration file
+pazpar2.cfg.dist now includes a default service default.xml (part of
+etc). And default.xml includes settings/edu.xml. The default.xml file,
+not to be confused with settings/defaults.xml, is a template for jsdemo
+and other services. The Debian package installs /etc/pazpar2/server.xml
+which is now the main pazpar2 configuration (used to be called pazpar2.cfg).
+server.xml includes services from /etc/pazpar2/services-enabled/*.xml .
+The default.xml (from etc) is installed in /etc/pazpar2/services-available
+and a symlink to it is created from services-enabled. The default.xml
+service is unnamed and, thus, will be used by jsdemo and test1.
+
+New setting pz:negotiation_charset. Patch from Andrei V. Toutoukine. The
+new setting pz:negotiation_charset specifies character set for Z39.50 Init.
+
+--- 1.2.4 2010/01/15
+
+Support for additional fields in cf.xsl and pazpar2.conf.dist:
+publisher, available, due, location (=locallocation), callno
+(=callnumber), thumburl and score.
+
+Describe pz:xslt and the auto setting.
+
+Move mergekey definition away from the normalization stylesheets and
+define a mergekey common for all target types in pazpar2.cfg.
+
+Code update: Use the Odr_int type for hit counts. This is part of
+YAZ 3.0.47 and later and so configure checks for that.
+
+--- 1.2.3 2009/11/24
+
+Metadata attribute 'skiparticle' also works for ICU based
+normalization. (was only working for the non-ICU/ASCII before).
+
+Command bytarget with argument settings=1 will show settings per
+target.. This is to be able to verify correct settings and be able to
+test that they are correct. The database settings array size is now
+also stored.. Problems with database settings array is that if not
+careful it will be too small (smaller than dictionary per-service
+in settings).
+
+Make record list sorting stable by comparing mergekey for records if
+relevance/title or other sorting criteria all match. This is merely to
+ensure that our regressions tests works (reproducible output).
+
+Relevance calculation changes: use a different denominator (length) for
+per-field relevance scoring.. Instead of length of all ranked fields we
+now use length of individual fields (as if they were individual "free"
+text fields). This will ensure that documents with a long field with no
+match (say description) will not "hurt" a title match.
+
+Diagnostic member was not set on connection error. Fixed
+
+--- 1.2.2 2009/10/13
+
+Command search takes two optional parameters, startecs and maxrecs,
+that specifies the start offset (0, 1, ...) and maximum number of records
+to fetch for each target.
+
+XSLTs + MARC maps are cached within a session so we don't re-parse
+them over and over again. Even for a session with a single search
+there's much to be gained because many targets use the same
+transformation.
+
+The metadata attribute 'mergekey' now takes one of three values 'no',
+'required', 'optional' . And the resulting mergekey from metadata
+is now ordered in the same way as metadata in the service definition.
+Older Pazpar2 version use the order in which metadata appeared in a
+record instance.
+
+The search argument 'filter' now offers a new operator ~ which does a
+substring match. The = operator works as before: string match for
+anything but pz:id, or target match for pz:id.
+
+New setting pz:recordfilter. The value of this setting takes the
+form name[~value]. This setting makes Pazpar2 ignore all retrieved
+records that do not have the metadata element name with value substring
+(if given).
+
+Pazpar2 allows YAZ log level to be set (option -v).
+
+--- 1.2.1 2009/10/05
+
+For WS responses Pazpar2 creates XML header. Exception: raw record.
+
+Setting XML files are now stored in etc/settings instead of etc. This
+reflects the layout with the Debian package layout.
+
+Settings may be posted for command=settings. The POSTed settings must
+have root element 'settings' like regular setting files. In order to be
+recognized, the POST request must use Content-Type=text/xml.
+
+A service may be posted for command=init. This service will be used
+during the session. The service may have its own target settings,
+ICU config, timeout, etc. In order to be recognized, the POST request
+must use Content-Type=text/xml.
+
Timeout values may be given per-service. That's element 'timeout'
which takes three attribute values (a subset may be given): 'session',
-'z3950_connect', 'z3950_session'. Option -T is no longer supported
+'z3950_operation', 'z3950_session'. Option -T is no longer supported
- used to specify session timeout.
Option -t tests the Pazpar2 configuration and returns exit code
projects / pazpar2-moved-to-github.git / blobdiff