X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;f=NEWS;h=b512a9b0db0af50dd5bae483ee8bc77b02401a85;hb=f38f7a4918a64868c25cd59befc2df50a037223d;hp=0f1f78b84529e9b3835db10987f27f6670a591c0;hpb=e7ddfbefed018d35da68a5422eaaf7fc071e4cd5;p=pazpar2-moved-to-github.git diff --git a/NEWS b/NEWS index 0f1f78b..b512a9b 100644 --- a/NEWS +++ b/NEWS @@ -1,3 +1,134 @@ +--- 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 + +For WS responses Pazpar2 creates XML header. Exception: raw record. + +Setting XML files are now stored in etc/settings instead of etc. This +reflects the layout with the Debian package layout. + +Settings may be posted for command=settings. The POSTed settings must +have root element 'settings' like regular setting files. In order to be +recognized, the POST request must use Content-Type=text/xml. + +A service may be posted for command=init. This service will be used +during the session. The service may have its own target settings, +ICU config, timeout, etc. In order to be recognized, the POST request +must use Content-Type=text/xml. + +Timeout values may be given per-service. That's element 'timeout' +which takes three attribute values (a subset may be given): 'session', +'z3950_operation', 'z3950_session'. Option -T is no longer supported +- used to specify session timeout. + +Option -t tests the Pazpar2 configuration and returns exit code +(0=success, non-zero=failure). In previous version of Pazpar2, -t +specified local settings. + +In version 1.2.0 the configuration file - after include processing - +was dumped to stdout. Now, the configuration is only dumped to the +yaz log file if option -d is given. + +--- 1.2.0 2009/09/10 + +Configuration may now have multiple server areas. This means that a +Pazpar2 instance may listen on multiple ports. Virtual hosting is not +yet supported - on a server basis. Configuration may also have multiple +services .. That is repeating service elements inside a server. Each +has an attribute 'id' which serves as service ID. This ID in turn may +be used in a Pazpar2 session, by specifying parameter service=ID for +command init. There can be at most one unnamed service inside a server +which can be referred to by not specifying an service ID for command +init (backwards compatible). In order to partition multiple servers and +services a new include directive has been added. This takes an attribute +'src' which specifies one or more sub-files. For example to include +service files, one might use: + .. .. . +It is the intention that that completely makes the settings directive +redundant. + +Fix problem where the record command would wait forever if there were +no targets to wait for (activeclients == 0). + +--- 1.1.1 2009/08/28 + +One result set is created per session (last search) rather than for +each connection which happen to be shared (bug #3009). + +marc21 stylesheets changed for efficiency. + +--- 1.1.0 2009/08/19 + +Session timeout may be specified on the command-line as option -T. + +Pazpar2 may now be operated in a no-merged mode for records.. All records +will be considered unique. This mode is enabled if no mergekey is +generated by the normalization stylesheet (pz:xslt). + +Pazpar2 caches original records from each target and the 'record' command +with offset returns the original record if 'syntax' and 'esn' are NOT +specified. This speeds up retrieval of original records but also means +that Pazpar2 uses more memory. The cached records will be freed when the +session terminates or a new search is executed. + +Pazpar2 no longer uses its own ICU wrapper. Instead the ICU wrapper +library part of YAZ is used. + +Added SRU client support. + +Automatically computes pz:nativesyntax if not provided. Works for XML and +MARC. + --- 1.0.13 2008/11/24 Command bytarget returns name of target (if defined).