in main thread).
</para>
</refsect2>
+ <refsect2 id="config-sockets">
+ <title>sockets</title>
+ <para>
+ This section is optional and is supported for Pazpar2 version 1.13.0 and
+ later . It is identified by element "<literal>sockets</literal>" which
+ may include one attribute "<literal>max</literal>" which specifies
+ the maximum number of sockets to be used by Pazpar2.
+ </para>
+ </refsect2>
<refsect2 id="config-file">
<title>file</title>
<para>
<emphasis>user, password</emphasis>.
</para>
<para>
- For HTTP based procotols, such as SRU and Solr, the authentication
- string includes a username term and, optionally, a password term.
+ For HTTP based procotols, such as SRU and Apache Solr, the
+ authentication string includes a username term and, optionally,
+ a password term.
Each term is separated by a single blank. The
authentication information is passed either by HTTP basic
- authentication or via URL parameters. The mode is operation is
+ authentication or via URL parameters. The mode of operation is
determined by <literal>pz:authentication_mode</literal> setting.
</para>
</listitem>
supports (native) facets. The value is the name of the
field on the target.
</para>
- <note>
- <para>
- At this point only Solr targets have been tested with this
- facility.
- </para>
- </note>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>pz:facetmap:split:<replaceable>name</replaceable></term>
+ <listitem>
+ <para>
+ Like pz:facetmap, but makes Pazpar2 inspect the term value consisting
+ of two items separated by colon. First item is the raw ID to be
+ sent to database if limitmap on the field
+ <replaceable>name</replaceable> is used. The second item is
+ the display term.
+ </para>
+ <para>
+ This facility was added in Pazpar2 version 1.11.0.
+ </para>
</listitem>
</varlistentry>