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>
</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>
</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>