X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;f=NEWS;h=f9678bfd0df4aa6d4c248f219875fd561265cb6b;hb=9a1674900947c5617edc49ee2cad8158c321cbaf;hp=9e5ed6b10beca7bd9f37f024617291ad664204eb;hpb=14157d6fcdf0c762d7615fd55a8a2cb88a287f56;p=pazpar2-moved-to-github.git

diff --git a/NEWS b/NEWS
index 9e5ed6b..f9678bf 100644
--- a/NEWS
+++ b/NEWS
@@ -1,10 +1,54 @@
---- 1.6.22 2012/10/05
+--- 1.6.25 2013/02/07
+
+Fix hang of 2nd command=show with esn/syntax given.
+
+--- 1.6.24 2013/01/18
+
+New merge attribute type: 'first', which takes all metadata fields
+from first target that returns the particular field.
+
+--- 1.6.23 2013/01/02
+
+Extend info command with hostname and YAZ SHA1
+Indent results for both command stat and info.
+
+Allow limit on merged content. The new configuration metadata
+element, limitcluster, configures that a metadata element (name) be used
+as limit name for search. Applies to the whole service (ie all targets),
+unlike pz:limitmap which is configured per-target (database).
+
+New feature: limitmap local:* matches against all metadata fields.
+
+Allow repeated list in limitmap spec . Separated by comma. For
+example: value="local:title,rpn:@attr 1=4".
+
+New element <message> in bytarget response. Holds diagnostic message
+of code (say 'Unsupported Use Attribute' for Bib-1 114).
+
+Improved logging for record ingestion failures.
+
+Avoid using struct icu_chain in non-YAZ_HAVE_ICU mode. In the rare case,
+when YAZ is compiled without ICU support.
+
+--- 1.6.22 2012/10/11
 
 Requires YAZ-4.2.40 to support native solr support. 
 
-Fix logic handling whether or not to re-do search. A new sort order 
-whould not trigger a new search, which is required for targets with
-native sorting capabilities.
+Fix and improve logic handling whether or not to re-do search on sort 
+order changes. A sort order with change in ascending/descending only 
+whould not trigger a new search, which is required for targets with 
+native sorting capabilities. Each client is now checked if instructions
+(sortmap) exist for native sorting and only client that does requires 
+it is researched. Other clients is just re-ingesting the records, 
+they already have. The resultset is now cleared if any researching 
+is done. 
+
+Connection sharing between session has broken since version 1.6.8 with 
+introduction of logic that would minimize searching if pazpar2 could 
+detect this based on same query and limits and partly sort order. 
+This could lead to segementations violations.
+
+Added a chapter in the manaul about relevance ranking.
 
 --- 1.6.21 2012/09/24
 
@@ -25,7 +69,7 @@ by length.
 
 --- 1.6.20 2012/09/21
 
-Rank algorithm details may be printed as part of show reseponse in
+Rank algorithm details may be printed as part of show response in
 element <relevance_info>.. This is only printed if <rank debug="yes"/>
 is used in service.