</varlistentry>
<varlistentry>
- <term>service</term>
+ <term id="service_conf">service</term>
<listitem>
<para>
This nested element controls the behavior of Pazpar2 with
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>
<para>
The XML configuration may be partitioned into multiple files by using
the <literal>include</literal> element which takes a single attribute,
- <literal>src</literal>. The of the <literal>src</literal> attribute is
+ <literal>src</literal>. The <literal>src</literal> attribute is
regular Shell like glob-pattern. For example,
<screen><![CDATA[
<include src="/etc/pazpar2/conf.d/*.xml"/>
</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 positive
+ value. then Pazpar2 wait for show to fetch pz:extendrecs more
+ records. 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 default value of pz:extendrecs is 0 (no extended fetch).
+ </para>
+ <warning>
+ <para>
+ The pz:extendrecs setting appeared in Pazpar2 version 1.6.26.
+ But the bahavior changed with the release of Pazpar2 1.6.29.
+ </para>
+ </warning>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
<term>pz:presentchunk</term>
<listitem>
<para>