Ignore local0.ent

[pazpar2-moved-to-github.git] / doc / pazpar2_conf.xml

diff --git a/doc/pazpar2_conf.xml b/doc/pazpar2_conf.xml
index cbad09d..bcdf8ec 100644 (file)
--- 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);
            </para>
+           <para>
+            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.
+           </para>
           </listitem>
          </varlistentry>
          
@@ -361,6 +366,22 @@
          </varlistentry>
          
          <varlistentry>
+          <term id="limitcluster">limitcluster</term>
+          <listitem>
+           <para>
+            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).
+           </para>
+           <note>
+            <para>
+             Requires Pazpar2 1.6.23 or later.
+            </para>
+           </note>
+          </listitem>
+         </varlistentry>
+         
+         <varlistentry>
           <term id="metadata_limitmap">limitmap</term>
           <listitem>
            <para>
@@ -661,7 +682,7 @@
         <para>
          Customization of ranking algorithm was introduced with
          Pazpar2 1.6.18. The semantics of some of the fields changed
-         in versions up to 1.6.21.
+         in versions up to 1.6.22.
         </para>
        </listitem>
        </varlistentry>
@@ -1253,6 +1274,24 @@
      </listitem>
     </varlistentry>
     <varlistentry>
+     <term>pz:extendrecs</term>
+     <listitem>
+      <para>
+       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.
+      </para>
+      <note>
+       <para>
+       The pz:extendrecs setting is supported in Pazpar2 version 1.6.26.
+       </para>
+      </note>
+     </listitem>
+    </varlistentry>
+    <varlistentry>
      <term>pz:presentchunk</term>
      <listitem>
       <para>
@@ -1474,6 +1513,12 @@
        by a field a metadata field (default is to use the name of the 
        limitmap itself).
       </para>
+      <para>
+       For Pazpar2 version 1.6.23 and later the limitmap may include multiple
+       specifications, separated by <literal>,</literal> (comma).
+       For example:
+       <literal>ccl:title,local:ltitle,rpn:@attr 1=4</literal>.
+      </para>
       <note>
        <para>
        The limitmap facility is supported for Pazpar2 version 1.6.0.