X-Git-Url: http://lists.indexdata.com/cgi-bin?a=blobdiff_plain;f=doc%2Fpazpar2_conf.xml;h=4cf49d87cb7e5a517cce938944d77d304beac8c3;hb=c26686a5a1448254fd0fff71dbfa962b04caf677;hp=931bc3fff149a8fa92409b826e8d9e855cefae2d;hpb=089cf6349e1bf28671e20fbde9792d453b443216;p=pazpar2-moved-to-github.git
diff --git a/doc/pazpar2_conf.xml b/doc/pazpar2_conf.xml
index 931bc3f..4cf49d8 100644
--- a/doc/pazpar2_conf.xml
+++ b/doc/pazpar2_conf.xml
@@ -59,8 +59,9 @@
server
- This section governs overall behavior of the client. The data
- elements are described below.
+ This section governs overall behavior of the server. The data
+ elements are described below. From Pazpar2 version 1.2 this is
+ a repeatable element.
@@ -189,7 +190,16 @@
extraction of data from the internal representation, primarily
through the 'metadata' sub-element.
-
+
+ Pazpar2 version 1.2 and later allows multiple service elements.
+ Multiple services must be given a unique ID by specifying
+ attribute id.
+ A single service may be unnamed (service ID omitted). The
+ service ID is referred to in the
+ init webservice
+ command's service parameter.
+
+
metadata
@@ -302,6 +312,17 @@
+ mergekey
+
+
+ If set to yes, the value of this
+ metadata element is appended to the resulting mergekey.
+ By default metadata is not part of a mergekey.
+
+
+
+
+
setting
@@ -334,7 +355,7 @@
-
+
EXAMPLE
@@ -373,7 +394,22 @@
]]>
-
+
+ INCLUDE FACILITY
+
+ The XML configuration may be partitioned into multiple files by using
+ the include element which takes a single attribute,
+ src. The of the src attribute is
+ regular Shell like glob-pattern. For example,
+
+ ]]>
+
+
+ The include facility requires Pazpar2 version 1.2.
+
+
+
TARGET SETTINGS
Pazpar2 features a cunning scheme by which you can associate various
@@ -409,7 +445,9 @@
environment, where different end-users may need to be represented to
some search targets in different ways. This, again, can be managed
using an external database or other lookup mechanism. Setting overrides
- can be performed either using the 'init' or the 'settings' webservice
+ can be performed either using the
+ init or the
+ settings webservice
command.
@@ -422,8 +460,10 @@
Finally, as an extreme case of this, the webservice client can
- introduce entirely new targets, on the fly, as part of the init or
- settings command. This is useful if you desire to manage information
+ introduce entirely new targets, on the fly, as part of the
+ init or
+ settings command.
+ This is useful if you desire to manage information
about your search targets in a separate application such as a database.
You do not need any static settings file whatsoever to run Pazpar2 -- as
long as the webservice client is prepared to supply the necessary