X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;f=NEWS;h=4ac1fadb8e76e7f84f45a18da10ab83b7310fd8d;hb=refs%2Ftags%2Fv1.6.1;hp=6f496f8d65587b61003ddcc3929823f3187e04c3;hpb=1638b527d8ddf8917cee2b9533a31e2286b363f7;p=pazpar2-moved-to-github.git

diff --git a/NEWS b/NEWS
index 6f496f8..4ac1fad 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,24 @@
+--- 1.6.1 2011/09/14
+
+New configuration element <icu_chain> for <server>/<service> which
+allows a named ICU rule (chain) to be defined. The names relevance,
+sort, mergekey and facet are used for those operations. The definition
+  <icu_chain id="sort" locale="en"> ..  </icu_chain>
+is identical to
+  <sort> <icu_chain locale="en> ... </icu_chain> </sort>
+And so on.. for relevance, mergekey and facet as well. The latter
+style is deprecated. The facet terms are normalized by the facet
+rule by default. This may be changed on a metadata field basis by
+defining the new attribute 'facetrule' for the metadata element.
+For example:
+  <icu_chain id="myrule" locale="en"> ... </icu_chain>
+  <metadata name="author" termlist="yes" facetrule="myrule"/>
+
+Preserve rorder for merged metadata. Fixes issue as reported by Sven
+Porst: http://lists.indexdata.dk/pipermail/yazlist/2011-July/003230.html
+
+tmarc.xsl: set journal-subpart to 773$ only.
+
 --- 1.6.0 2011/09/12
 
 Modify the behavior for the limit parameter (first defined in 1.5.7).