X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;f=NEWS;h=d9165e80f88de98632b5d34aa73dcc2ec9241f0d;hb=49737fc1110a572e32168401fb70b9de0088d843;hp=0bb6f85beb8ab1bdbdc7ce92d6a63953bcc63744;hpb=0df08cf93e60b248e8ec8cf44e3fd7b784e6ef78;p=pazpar2-moved-to-github.git diff --git a/NEWS b/NEWS index 0bb6f85..d9165e8 100644 --- a/NEWS +++ b/NEWS @@ -1,3 +1,288 @@ +--- 1.6.20 2012/09/21 + +Rank algorithm details may be printed as part of show reseponse 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 +on termlist, bytarget and search, when unable to block due to +other block. The client will now receive a regular response, +but it will be logged in the server. A parameter (report) is +added to change behavior to return error response or WARNING +status message. Consider this "API" as private, as it is mostly +untested and could be changed in future releases. + +Fix spell error in pz2.js fix in 1.6.10. + +New Marc2TurboMarc.xsl (contribution from Sven Porst). +Can solve the missing marc21.xsl updates in some cases. + +tmarc.xsl: Simplify the 6xx to subject-long and fix 1-based +substring (contribtion from Sven Porst) + +marc21.xsl: fix 1-based substring call + +tmarc.xsl and marc21.xsl: use 856$a as last option for electronic-text. + +Add test_termlist_block to test suite + +--- 1.6.10 2012/02/23 + +Fix SEGV for invalid PQFs and SRU/SOLR targets +Also refactor a bit the code that converts from PQF to SRU/SOLR queries. + +Fix pz2.js: "null object" due to change in in bytarget result XML. + +Fixes in tmarc.xsl: Subject-long shorten for extra commas only. +Added this normalization to the other subject-long fields (d6xx), +where it was missing. + +Fixes in marc21.xsl: Updated with most of the new tmarc.xsl. +Still differences around medium and holdings. marc21.xsl is not +longer active used by Index Data, and should be considered unsupported. +Use tmarc.xsl instead. + +--- 1.6.9 2012/01/19 + +Fix SEGV that could occur for failed connections. + +--- 1.6.8 2012/01/17 + +Fix bug for command sort that could return no results for active clients +(from previous search). This bug was present in 1.6.6-1.6.7. + +Fix bug in results that could include results that should have been +filtered out. This bug was present in 1.6.6-1.6.7. + +--- 1.6.7 2011/12/23 + +Fix bug introduced in 1.6.6 where a connection re-use could stall +incoming requests. + +Local filtering may now specify a local metadata field, eg. + pz:limitmap:somefield[t]=local:otherfield + +--- 1.6.6 2011/11/25 + +For search, when limit and or filtering is in place and search +is identical to previous search, the result set is re-used and the +target is not searched. + +Limits may work perform local filtering as well, by using "local:" +for a limitmap. + +--- 1.6.5 2011/11/01 + +Updated bytarget command to contain a suggestions element with misspelled +words and suggestions to these. pz2.js has been updated to deliver this +onwards as well. Only target that currently delivers this is the solr +client in YAZ 4.2.18. + +--- 1.6.4 2011/10/28 + +New service definition element, xslt, that allows an embedded stylesheet +to be defined. This can be referred to from pz:xslt as an alternative to +external files. + +New pz:sortmap:field setting for specifying hints on how to make +a target natively sort on a field. This is used for command=show in +conjunction with sort. + +New pz:url setting for specifying the actual URL for a target. When +this is used the target ID is not used as URL anymore and the target ID +may be almost any string (not including []). + +command=termlist without name parameter returns all termlists/facets. +Previously if name parameter was omitted, only "subject" was returned. + +--- 1.6.3 2011/09/22 + +Make termlist sorting stable. Terms with same frequency are now sorted by +their display name. This makes a pretty display and improves our +regression test because qsort is not a stable sort. + +New sort parameter value 'position'. The 'position' sorts merged records +by their original position from the remote target. This is primarily useful +for debugging and may be used for targets that already perform some kind +of relevance ranking. Note that sort by default is decreasing; so to get +records in their original order sort=position:1 must be used. + +--- 1.6.2 2011/09/15 + +tmarc.xsl: yet another 773$g fix. Was broken in 1.6.1 as well. + +Facility to change working directory for pazpar2 daemon. Option -wdir +sets working directory to dir. This facility is useful if core dumps +must be saved. In this case, the current working directory must be +writable by the running user, such as "nobody". + +--- 1.6.1 2011/09/14 + +New configuration element for / which +allows a named ICU rule (chain) to be defined. The names relevance, +sort, mergekey and facet are used for those operations. The definition + .. +is identical to + ... + + +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). +Mapping of limit searches are now defined by the new configuration item +pz:limitmap. Fix a dead-lock problem with the limit parameter. + +Extend tmarc.xsl to extract 773$g data (OpenURL). + +--- 1.5.7 2011/08/19 + +ICU default maps remove backquote (`). + +Command 'search' takes limit parameter (optional). The limit parameter +allows a search to be limited one or more facets and the corresponding +values. This is for server side filtering. + +Configure tweak: Use -lm for log(3) if needed + +--- 1.5.6 2011/04/15 + +Fix a problem with skiparticle sortkey that could be completely +ignored (and reduced to ""). + +Fix dependency problem in pazpar2 RPM package (did not require +libyaz4 as it should). + +--- 1.5.5 2011/03/28 + +Fix memory leak that occurred for command=termlist&name=xtargets . + +Pazpar2 may save HTTP requests. Enabled by option -R. + --- 1.5.4 2011/03/08 Experimental support for DTIC DADS target. New dads-pz2.xsl.