X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;f=NEWS;h=e5fc24cbe4c069eb4eb86a578489050e36d02a3f;hb=27ab2f49456d0372acde70853f10dddcc353d579;hp=87f469872a810b175d6533edc9ad3c52c6703821;hpb=e6f087568c5d1188b208514169e13e0bcfc310e5;p=pazpar2-moved-to-github.git diff --git a/NEWS b/NEWS index 87f4698..e5fc24c 100644 --- a/NEWS +++ b/NEWS @@ -1,3 +1,179 @@ +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 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 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 + +Rank tweak: follow=number will increase mult by number if two terms +occur next to each other; number-1 if they are one term apart , .. 0 +if they are number a part (all in order). Default is 0 (following +terms has no effect). + +Rank tweak: lead=k will divide mult by 1 + log2(1+k*l) where k is +value given by lead and l is length from beginning of field where +term occurs (l=0 for first term, l=1 for second term, ..). Default +value of k is 0.0. + +Rank tweak: length=strategy. length="linear" if mult is to be divided +by length (existing, default behavior), length="log" if mult is to be +divided by log2(1+length), length="none" if mult is not to be affected +by length. + +--- 1.6.20 2012/09/21 + +Rank algorithm details may be printed as part of show response in +element .. This is only printed if +is used in service. + +Record as returned by show/record command have a minimal indentation +which makes things human-readable. + +New configuration of default sorting criteria (sort-default) in +service definition. If no criteria is defined it will be as before +'relevance'. + +Search command now supports sort parameter just as the show command. +If no parameter is give, it will use the service sort-default value. + +--- 1.6.19 2012/09/18 + +Rank algorithm skips strings that gets normalized to empty string. +For example, & and ! could map to the empty string. The weight for +those terms is now 0 (as if they were not part of the query). + +Rank algorithm does not use CCL from limitmap; only from the query +parameter (user query). + +Obey -w dir. + +--- 1.6.18 2012/09/17 + +Rank algorithm configurable by 'rank' element inside service. So far +only, attribute 'cluster' is recognized. If cluster="yes", multiple +records inside a cluster boosts higher than single records. This +is default behavior and existing behavior. cluster="no" takes the +average score of each record in a cluster. + +--- 1.6.17 2012/09/05 + +Fix bad re-use of connections (connections with changing proxy should not +be reused). + +--- 1.6.16 2012/08/22 + +Fix a bug introduce in 1.6.15 around the position sorting. It resetted the +resultset and sorting when the sort order is position. However this will be done on +every client poll, which will make pazpar2 continuing reset and fetching. +It should only be done on FIRST request where the sort order change. + +Fix an issue on suggestion option: Also disable suggestions on empty string. + +Clean up in turbo marc stylesheet. + +Remove the hardcoded size of termlists. + +--- 1.6.15 2012/06/27 + +New facility: ccldirective may be given in service definition. Allows +CCL parsing to be customized a bit, such as defining names of operators +and, or, not. + +New facility: raw record by checksum, rather than offset. The record +command optionally takes checksum which identifies certain record from +a database. + +New facility: per field ranking. Rank may be given as M [F N] where +M is default rank and N is rank for CCL terms from field F. + +--- 1.6.14 2012/06/04 + +Fix for IE7/8 in pz.js + +Applied patch from Giannis Kosmas on keepAlive, which also adds keepAlive to init response. + +Lower log level some places. + +Remove some invalid test results. + +--- 1.6.13 2012/05/23 + +Introducing a version=2 parameter for show, termlist and bytarget commands. +This enables pazpar2 to return approximation on hit and count count when +doing record filtering using the limit parameter on search and a +limitmap with a value of "local:" + +Setting pz:xslt may embed local XSLT as an alternative to referring +to filenames. +Value is not CDATA but XML nodes embedded, so escaping is not necessary +but a root element *must* be present. For example: + + + + + + +Metadata field rank may given by XML internal document (pz:xslt +result). If rank is not given, the rank from service description is +used - as before. + +Metadata field can now configured a default limitmap and facetmap. +Setting limitmap to "local:" would work for all kind of targets, but would +prob. not be the optimal solution. But at least better than the default behavior +of pazpar2 where no filtering is done. + +A service definition can now also contains that defines service-wide +settings. These will override server-wide sets and will be overridded by +settings. + +New setting, pz:present_chunk, that specifies number of records to fetch +at a time. Zero will disable chunkation; will fetch max_records at once. + +--- 1.6.12 2012/03/14 + +Revert the format change in termlist response, that could break +some clients / UIs since they were expecting an (empty) element +if no facet values was found. + --- 1.6.11 2012/03/07 Revert the behavior of returning errors when unable to block