2 Each of the following examples is an example target settings file. On startup,
3 pazpar2 will read any number of these files recursively from a directory hierarchy.
4 Explanations for the examples below.
6 The following file explicitly sets name=value for a whole bunch of targets for a
7 bunch of users.. I don't imagine this format will be used much for human
8 entry, but it might be used to export settings from a relational database.. it is
9 also there as one extreme form of a generic format.
11 If user is omitted, the setting applies to any user. For target, there are two wildcard
12 forms: * matches any target not otherwise matched, and xx/* matches any database on a given
13 host. A setting for an explicit host/db always overrides a wildcard setting.
16 <set target="xx" name="xx" value="xx" user="xx"/>
17 <set target="xx" name="xx" value="xx" user="xx"/>
18 <set target="xx" name="xx" value="xx" user="xx"/>
21 More useful, you can group a number of settings about a target into one file like this.
22 This comes closer to the conventional target setting files we're used to.
24 <settings target="xx">
25 <set name="xx" value="xx"/>
26 <set name="xx" value="xx"/>
27 <set name="xx" value="xx"/>
30 This file sets a number of name=value pairs for a list of targets. A typical example might
31 be to associate all these targets with a specific category or type, or to otherwise make
32 them part of a set -- like 'all full-text', 'all free-access', etc.
34 <settings name="xx" value="xx">
41 Here's the shortest possible file.. it sets one name=value for one target
43 <settings target="xx" name="xx" value="xx" user="xx"/>
45 This sets different values for a given named setting (attribute) for one target.
47 <settings name="xx" target="xx">
53 This sets different values for one attribute for different targets
63 This sets one or more named values for a set of targets.
69 <set name="xx" value="xx"/>
70 <set name="xx" value="xx"/>
73 This is a more concrete example.. it allows specific users access to a given target.
75 <settings name="pz:allow" target="xx" value="yes">
81 While this default setting disallows access to anything for everybody not otherwise
84 // Whitelist default -- disallow all access
85 <settings name="pz:allow" target="*" value="no"/>
87 .. except these 'free' targets which are open to anyone.
90 <settings name="pz:allow" value="yes">
96 The setting below sets a default record normalization stylesheet. Yes, values can be simple
97 strings, or they can be XML trees.
99 <settings xmlns="http://www.indexdata.com/pazpar2/1" target="*" name="pz:normalize">
101 <xsl:stylesheet xmlns:xsl="xxx" ..>