- <term id="pzxslt" xreflabel="pz:xslt">pz:xslt</term>
- <listitem>
- <para>
- Is a comma separated list of of stylesheet names that specifies
- how to convert incoming records to the internal representation.
- </para>
- <para>
- For each name, the embedded stylesheets (XSL) that comes with the
- service definition are consulted first and takes precedence over
- external files; see <xref linkend="servicexslt"/>
- of service definition).
- If the name does not match an embedded stylesheet it is
- considered a filename.
- </para>
- <para>
- The suffix of each file specifies the kind of tranformation.
- Suffix "<literal>.xsl</literal>" makes an XSL transform. Suffix
- "<literal>.mmap</literal>" will use the MMAP transform (described below).
- </para>
- <para>
- The special value "<literal>auto</literal>" will use a file
- which is the <link linkend="requestsyntax">pz:requestsyntax's</link>
- value followed by
- <literal>'.xsl'</literal>.
- </para>
- <para>
- When mapping MARC records, XSLT can be bypassed for increased
- performance with the alternate "MARC map" format. Provide the
- path of a file with extension ".mmap" containing on each line:
- <programlisting>
- <field> <subfield> <metadata element></programlisting>
- For example:
- <programlisting>
- 245 a title
- 500 $ description
- 773 * citation
- </programlisting>
- To map the field value specify a subfield of '$'. To store a
- concatenation of all subfields, specify a subfield of '*'.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>pz:authentication</term>
- <listitem>
- <para>
- Sets an authentication string for a given server. See the section on
- authorization and authentication for discussion.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>pz:allow</term>
- <listitem>
- <para>
- Allows or denies access to the resources it is applied to. Possible
- values are '0' and '1'.
- The default is '1' (allow access to this resource).
- See the manual section on authorization and authentication for
- discussion about how to use this setting.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>pz:maxrecs</term>
- <listitem>
- <para>
- Controls the maximum number of records to be retrieved from a
- server. The default is 100.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>pz:presentchunk</term>
- <listitem>
- <para>
- Controls the chunk size in present requests. Pazpar2 will
- make (maxrecs / chunk) request(s). The default is 20.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>pz:id</term>
- <listitem>
- <para>
- This setting can't be 'set' -- it contains the ID (normally
- ZURL) for a given target, and is useful for filtering --
- specifically when you want to select one or more specific
- targets in the search command.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>pz:zproxy</term>
- <listitem>
- <para>
- The 'pz:zproxy' setting has the value syntax
- 'host.internet.adress:port', it is used to tunnel Z39.50
- requests through the named Z39.50 proxy.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>pz:apdulog</term>
- <listitem>
- <para>
- If the 'pz:apdulog' setting is defined and has other value than 0,
- then Z39.50 APDUs are written to the log.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>pz:sru</term>
- <listitem>
- <para>
- This setting enables
- <ulink url="&url.sru;">SRU</ulink>/<ulink url="&url.solr;">Solr</ulink>
- support.
- 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
- the protocol.
- </para>
- <para>
- A value of 'solr' enables Solr client support. This is supported
- for Pazpar version 1.5.0 and later.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>pz:sru_version</term>