X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;f=NEWS;h=b512a9b0db0af50dd5bae483ee8bc77b02401a85;hb=05d6317190cd52051660b96a4fa873e5391bbc73;hp=c4eacb35f6cc61616d1aedc42809c217c8c76996;hpb=b2807317725db68d786503711be67ecf163115b7;p=pazpar2-moved-to-github.git

diff --git a/NEWS b/NEWS
index c4eacb3..b512a9b 100644
--- a/NEWS
+++ b/NEWS
@@ -1,9 +1,53 @@
+--- 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