X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;f=NEWS;h=d0602efc1ecc39b3b12a4841f9d55de4e481309f;hb=ba41c99b2bf8920b8d5d46c1aed9dd4f676a2e79;hp=78d5256d61091c1ca46bae497dc0e35ddf73c41d;hpb=ab4491b2109b6831258aa28c29ed6a7495801ece;p=pazpar2-moved-to-github.git

diff --git a/NEWS b/NEWS
index 78d5256..d0602ef 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,60 @@
+--- 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,