X-Git-Url: http://lists.indexdata.dk/cgi-bin?a=blobdiff_plain;f=doc%2Fpazpar2_conf.xml;h=bcdf8ec0beac9fa2f912c6ce22ff74cca83a9ea8;hb=75918f1f3466ce4347f7d178ce49a7cb87158f53;hp=df8bd6ab020dc67cae083ee4bb54be72af70df0f;hpb=009e0e931b5759f9ca0be4009d6527933fd71d22;p=pazpar2-moved-to-github.git
diff --git a/doc/pazpar2_conf.xml b/doc/pazpar2_conf.xml
index df8bd6a..bcdf8ec 100644
--- a/doc/pazpar2_conf.xml
+++ b/doc/pazpar2_conf.xml
@@ -322,6 +322,11 @@
all elements), or 'no' (don't merge; this is the
default);
+
+ Pazpar 1.6.24 also offers a new value for merge, 'first', which
+ is like 'all' but only takes all from first database that returns
+ the particular metadata field.
+
@@ -361,6 +366,22 @@
+ limitcluster
+
+
+ Allow a limit on merged metadata. The value of this attribute
+ is the name of actual metadata content to be used for matching
+ (most often same name as metadata name).
+
+
+
+ Requires Pazpar2 1.6.23 or later.
+
+
+
+
+
+
limitmap
@@ -1253,6 +1274,24 @@
+ pz:extendrecs
+
+
+ If a show command goes to the boundary of a result set for a
+ database - depends on sorting - and pz:extendrecs is set to a larger
+ value of pz:maxrecs, then Pazpar2 wait for show to fetch remaining
+ records - up to pz:extendrecs. This setting is best used if a
+ database does native sorting, because the result set otherwise may
+ be completely re-sorted during extended fetch.
+
+
+
+ The pz:extendrecs setting is supported in Pazpar2 version 1.6.26.
+
+
+
+
+
pz:presentchunk
@@ -1474,6 +1513,12 @@
by a field a metadata field (default is to use the name of the
limitmap itself).
+
+ For Pazpar2 version 1.6.23 and later the limitmap may include multiple
+ specifications, separated by , (comma).
+ For example:
+ ccl:title,local:ltitle,rpn:@attr 1=4.
+
The limitmap facility is supported for Pazpar2 version 1.6.0.