From 9cfb3f33ac2c7c96dee3d1d5473d3f37c3dafb76 Mon Sep 17 00:00:00 2001 From: Sebastian Hammer Date: Wed, 1 Aug 2007 11:48:26 +0000 Subject: [PATCH] Updated doc to reflect changes in settings system --- doc/pazpar2_conf.xml | 32 +++++++++++++++++++++++++++++--- 1 file changed, 29 insertions(+), 3 deletions(-) diff --git a/doc/pazpar2_conf.xml b/doc/pazpar2_conf.xml index 9b06d58..2e294bd 100644 --- a/doc/pazpar2_conf.xml +++ b/doc/pazpar2_conf.xml @@ -9,7 +9,7 @@ %idcommon; ]> - + Pazpar2 @@ -291,6 +291,30 @@ + + setting + + + This attribute allows you to make use of static database + settings in the processing of records. Three possible values + are allowed. 'no' is the default and doesn't do anything. + 'postproc' copies the value of a setting with the same name + into the output of the normalization stylesheet(s). 'parameter' + makes the value of a setting with the same name available + as a parameter to the normalization stylesheet, so you + can further process the value inside of the stylesheet, or use + the value to decide how to deal with other data values. + + + + The purpose of using settings in this way can either be to + control the behavior of normalization stylesheet in a database- + dependent way, or to easily make database-dependent values + available to display-logic in your user interface, without having + to implement complicated interactions between the user interface + and your configuration system. + + @@ -352,7 +376,9 @@ pairs with groups of targets -- for instance, if you would like to place all commercial full-text bases in one group for selection purposes, or you would like to control what targets are accessible - to users by default. + to users by default. Per-database settings values can even be used + to drive sorting, facet/termlist generation, or end-user interface display + logic. @@ -542,7 +568,7 @@ - + -- 1.7.10.4