</varlistentry>
<varlistentry>
- <term>service</term>
+ <term id="service_conf">service</term>
<listitem>
<para>
This nested element controls the behavior of Pazpar2 with
</varlistentry>
<varlistentry>
- <term>rank</term>
+ <term id="metadata-rank">rank</term>
<listitem>
<para>
Specifies that this element is to be used to
<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>
<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.
+ 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>
- <note>
+ <warning>
<para>
- The pz:extendrecs setting is supported in Pazpar2 version 1.6.26.
+ The pz:extendrecs setting appeared in Pazpar2 version 1.6.26.
+ But the bahavior changed with the release of Pazpar2 1.6.29.
</para>
- </note>
+ </warning>
</listitem>
</varlistentry>
<varlistentry>
It has four possible settings.
'get', enables SRU access through GET requests. 'post' enables SRU/POST
support, less commonly supported, but useful if very large requests are
- to be submitted. 'srw' enables the SRW (SRU over SOAP) variation of
+ to be submitted. 'soap' enables the SRW (SRU over SOAP) variation of
the protocol.
</para>
<para>