1 <?xml version="1.0" standalone="no"?>
2 <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"
3 "http://www.oasis-open.org/docbook/xml/4.1/docbookx.dtd"
5 <!ENTITY % local SYSTEM "local.ent">
7 <!ENTITY % entities SYSTEM "entities.ent">
9 <!ENTITY % idcommon SYSTEM "common/common.ent">
12 <refentry id="pazpar2_conf">
14 <productname>Pazpar2</productname>
15 <productnumber>&version;</productnumber>
18 <refentrytitle>Pazpar2 conf</refentrytitle>
19 <manvolnum>5</manvolnum>
23 <refname>pazpar2_conf</refname>
24 <refpurpose>Pazpar2 Configuration</refpurpose>
29 <command>pazpar2.conf</command>
33 <refsect1><title>DESCRIPTION</title>
35 The Pazpar2 configuration file, together with any referenced XSLT files,
36 govern Pazpar2's behavior as a client, and control the normalization and
37 extraction of data elements from incoming result records, for the
38 purposes of merging, sorting, facet analysis, and display.
42 The file is specified using the option -f on the Pazpar2 command line.
43 There is not presently a way to reload the configuration file without
44 restarting Pazpar2, although this will most likely be added some time
49 <refsect1><title>FORMAT</title>
51 The configuration file is XML-structured. It must be valid XML. All
52 elements specific to Pazpar2 should belong to the namespace
53 <literal>http://www.indexdata.com/pazpar2/1.0</literal>
54 (this is assumed in the
55 following examples). The root element is named <literal>pazpar2</literal>.
56 Under the root element are a number of elements which group categories of
57 information. The categories are described below.
60 <refsect2 id="config-server"><title>server</title>
62 This section governs overall behavior of the server. The data
63 elements are described below. From Pazpar2 version 1.2 this is
66 <variablelist> <!-- level 1 -->
71 Configures the webservice -- this controls how you can connect
72 to Pazpar2 from your browser or server-side code. The
73 attributes 'host' and 'port' control the binding of the
74 server. The 'host' attribute can be used to bind the server to
75 a secondary IP address of your system, enabling you to run
76 Pazpar2 on port 80 alongside a conventional web server. You
77 can override this setting on the command line using the option -h.
86 If this item is given, Pazpar2 will forward all incoming HTTP
87 requests that do not contain the filename 'search.pz2' to the
88 host and port specified using the 'host' and 'port'
89 attributes. The 'myurl' attribute is required, and should provide
90 the base URL of the server. Generally, the HTTP URL for the host
91 specified in the 'listen' parameter. This functionality is
92 crucial if you wish to use
93 Pazpar2 in conjunction with browser-based code (JS, Flash,
94 applets, etc.) which operates in a security sandbox. Such code
95 can only connect to the same server from which the enclosing
96 HTML page originated. Pazpar2s proxy functionality enables you
97 to host all of the main pages (plus images, CSS, etc) of your
98 application on a conventional webserver, while efficiently
99 processing webservice requests for metasearch status, results,
106 <term>relevance / sort / mergekey</term>
109 Specifies character set normalization for relevancy / sorting
110 and the mergekey - for the server. These definitions serves as
111 default for services that don't have these given. For the meaning
112 of these settings refer to the "relevance" element inside service.
118 <term>settings</term>
121 Specifies target settings for the server.. These settings serves
122 as default for all services which don't have these given.
123 The settings element requires one attribute 'src' which specifies
124 a settings file or a directory . If a directory is given all
125 files with suffix <filename>.xml</filename> is read from this
127 <xref linkend="target_settings"/> for more information.
136 This nested element controls the behavior of Pazpar2 with
137 respect to your data model. In Pazpar2, incoming records are
138 normalized, using XSLT, into an internal representation.
139 The 'service' section controls the further processing and
140 extraction of data from the internal representation, primarily
141 through the 'metadata' sub-element.
144 Pazpar2 version 1.2 and later allows multiple service elements.
145 Multiple services must be given a unique ID by specifying
146 attribute <literal>id</literal>.
147 A single service may be unnamed (service ID omitted). The
148 service ID is referred to in the
149 <link linkend="command-init"><literal>init</literal></link> webservice
150 command's <literal>service</literal> parameter.
153 <variablelist> <!-- Level 2 -->
154 <varlistentry><term>metadata</term>
157 One of these elements is required for every data element in
158 the internal representation of the record (see
159 <xref linkend="data_model"/>. It governs
160 subsequent processing as pertains to sorting, relevance
161 ranking, merging, and display of data elements. It supports
162 the following attributes:
165 <variablelist> <!-- level 3 -->
166 <varlistentry><term>name</term>
169 This is the name of the data element. It is matched
170 against the 'type' attribute of the
172 in the normalized record. A warning is produced if
173 metadata elements with an unknown name are
175 normalized record. This name is also used to
177 data elements in the records returned by the
178 webservice API, and to name sort lists and browse
184 <varlistentry><term>type</term>
187 The type of data element. This value governs any
188 normalization or special processing that might take
189 place on an element. Possible values are 'generic'
190 (basic string), 'year' (a range is computed if
191 multiple years are found in the record). Note: This
192 list is likely to increase in the future.
197 <varlistentry><term>brief</term>
200 If this is set to 'yes', then the data element is
201 includes in brief records in the webservice API. Note
202 that this only makes sense for metadata elements that
203 are merged (see below). The default value is 'no'.
208 <varlistentry><term>sortkey</term>
211 Specifies that this data element is to be used for
212 sorting. The possible values are 'numeric' (numeric
213 value), 'skiparticle' (string; skip common, leading
214 articles), and 'no' (no sorting). The default value is
220 <varlistentry><term>rank</term>
223 Specifies that this element is to be used to
225 records against the user's query (when ranking is
226 requested). The value is an integer, used as a
227 multiplier against the basic TF*IDF score. A value of
228 1 is the base, higher values give additional
230 elements of this type. The default is '0', which
231 excludes this element from the rank calculation.
236 <varlistentry><term>termlist</term>
239 Specifies that this element is to be used as a
240 termlist, or browse facet. Values are tabulated from
241 incoming records, and a highscore of values (with
242 their associated frequency) is made available to the
243 client through the webservice API.
245 are 'yes' and 'no' (default).
250 <varlistentry><term>merge</term>
253 This governs whether, and how elements are extracted
254 from individual records and merged into cluster
255 records. The possible values are: 'unique' (include
256 all unique elements), 'longest' (include only the
257 longest element (strlen), 'range' (calculate a range
258 of values across all matching records), 'all' (include
259 all elements), or 'no' (don't merge; this is the
265 <varlistentry><term>mergekey</term>
268 If set to '<literal>required</literal>', the value of this
269 metadata element is appended to the resulting mergekey if
270 the metadata is present in a record instance.
271 If the metadata element is not present, the a unique mergekey
272 will be generated instead.
275 If set to '<literal>optional</literal>', the value of this
276 metadata element is appended to the resulting mergekey if the
277 the metadata is present in a record instance. If the metadata
278 is not present, it will be empty.
281 If set to '<literal>no</literal>' or the mergekey attribute is
282 omitted, the metadata will not be used in the creation of a
288 <varlistentry><term>setting</term>
291 This attribute allows you to make use of static database
292 settings in the processing of records. Three possible values
293 are allowed. 'no' is the default and doesn't do anything.
294 'postproc' copies the value of a setting with the same name
295 into the output of the normalization stylesheet(s). 'parameter'
296 makes the value of a setting with the same name available
297 as a parameter to the normalization stylesheet, so you
298 can further process the value inside of the stylesheet, or use
299 the value to decide how to deal with other data values.
302 The purpose of using settings in this way can either be to
303 control the behavior of normalization stylesheet in a database-
304 dependent way, or to easily make database-dependent values
305 available to display-logic in your user interface, without having
306 to implement complicated interactions between the user interface
307 and your configuration system.
312 </variablelist> <!-- attributes to metadata -->
318 <term>relevance</term>
321 Specifies ICU tokenization and transformation rules
322 for tokens that are used in Pazpar2's relevance ranking.
323 The 'id' attribute is currently not used, and the 'locale'
324 attribute must be set to one of the locale strings
325 defined in ICU. The child elements listed below can be
326 in any order, except the 'index' element which logically
327 belongs to the end of the list. The stated tokenization,
328 transformation and charmapping instructions are performed
329 in order from top to bottom.
331 <variablelist> <!-- Level 2 -->
332 <varlistentry><term>casemap</term>
335 The attribute 'rule' defines the direction of the
336 per-character casemapping, allowed values are "l"
337 (lower), "u" (upper), "t" (title).
341 <varlistentry><term>transform</term>
344 Normalization and transformation of tokens follows
345 the rules defined in the 'rule' attribute. For
346 possible values we refer to the extensive ICU
347 documentation found at the
348 <ulink url="&url.icu.transform;">ICU
349 transformation</ulink> home page. Set filtering
350 principles are explained at the
351 <ulink url="&url.icu.unicode.set;">ICU set and
352 filtering</ulink> page.
356 <varlistentry><term>tokenize</term>
359 Tokenization is the only rule in the ICU chain
360 which splits one token into multiple tokens. The
361 'rule' attribute may have the following values:
362 "s" (sentence), "l" (line-break), "w" (word), and
363 "c" (character), the later probably not being
364 very useful in a pruning Pazpar2 installation.
370 From Pazpar2 version 1.1 the ICU wrapper from YAZ is used.
371 Refer to the <ulink url="&url.yaz.yaz-icu;">yaz-icu</ulink>
372 utility for more information.
381 Specifies ICU tokenization and transformation rules
382 for tokens that are used in Pazpar2's sorting. The contents
383 is similar to that of <literal>relevance</literal>.
389 <term>mergekey</term>
392 Specifies ICU tokenization and transformation rules
393 for tokens that are used in Pazpar2's mergekey. The contents
394 is similar to that of <literal>relevance</literal>.
400 <term>settings</term>
403 Specifies target settings for this service. Refer to
404 <xref linkend="target_settings"/>.
413 Specifies timeout parameters for this service.
414 The <literal>timeout</literal>
415 element supports the following attributes:
416 <literal>session</literal>, <literal>z3950_operation</literal>,
417 <literal>z3950_session</literal> which specifies
418 'session timeout', 'Z39.50 operation timeout',
419 'Z39.50 session timeout' respectively. The Z39.50 operation
420 timeout is the time Pazpar2 will wait for an active Z39.50/SRU
421 operation before it gives up (times out). The Z39.50 session
422 time out is the time Pazpar2 will keep the session alive for
423 an idle session (no operation).
426 The following is recommended but not required:
427 z3950_operation (30) < session (60) < z3950_session (180) .
428 The default values are given in parantheses.
433 </variablelist> <!-- Data elements in service directive -->
437 </variablelist> <!-- Data elements in server directive -->
442 <refsect1><title>EXAMPLE</title>
443 <para>Below is a working example configuration:
445 <?xml version="1.0" encoding="UTF-8"?>
446 <pazpar2 xmlns="http://www.indexdata.com/pazpar2/1.0">
449 <listen port="9004"/>
451 <metadata name="title" brief="yes" sortkey="skiparticle"
452 merge="longest" rank="6"/>
453 <metadata name="isbn" merge="unique"/>
454 <metadata name="date" brief="yes" sortkey="numeric"
455 type="year" merge="range" termlist="yes"/>
456 <metadata name="author" brief="yes" termlist="yes"
457 merge="longest" rank="2"/>
458 <metadata name="subject" merge="unique" termlist="yes" rank="3"/>
459 <metadata name="url" merge="unique"/>
461 <icu_chain id="relevance" locale="el">
462 <transform rule="[:Control:] Any-Remove"/>
464 <transform rule="[[:WhiteSpace:][:Punctuation:]] Remove"/>
468 <settings src="mysettings"/>
469 <timeout session="60"/>
477 <refsect1 id="config-include"><title>INCLUDE FACILITY</title>
479 The XML configuration may be partitioned into multiple files by using
480 the <literal>include</literal> element which takes a single attribute,
481 <literal>src</literal>. The of the <literal>src</literal> attribute is
482 regular Shell like glob-pattern. For example,
484 <include src="/etc/pazpar2/conf.d/*.xml"/>
488 The include facility requires Pazpar2 version 1.2.
492 <refsect1 id="target_settings"><title>TARGET SETTINGS</title>
494 Pazpar2 features a cunning scheme by which you can associate various
495 kinds of attributes, or settings with search targets. This can be done
496 through XML files which are read at startup; each file can associate
497 one or more settings with one or more targets. The file format is generic
498 in nature, designed to support a wide range of application requirements. The
499 settings can be purely technical things, like, how to perform a title
500 search against a given target, or it can associate arbitrary name=value
501 pairs with groups of targets -- for instance, if you would like to
502 place all commercial full-text bases in one group for selection
503 purposes, or you would like to control what targets are accessible
504 to users by default. Per-database settings values can even be used
505 to drive sorting, facet/termlist generation, or end-user interface display
510 During startup, Pazpar2 will recursively read a specified directory
511 (can be identified in the pazpar2.cfg file or on the command line), and
512 process any settings files found therein.
516 Clients of the Pazpar2 webservice interface can selectively override
517 settings for individual targets within the scope of one session. This
518 can be used in conjunction with an external authentication system to
519 determine which resources are to be accessible to which users. Pazpar2
520 itself has no notion of end-users, and so can be used in conjunction
521 with any type of authentication system. Similarly, the authentication
522 tokens submitted to access-controlled search targets can similarly be
523 overridden, to allow use of Pazpar2 in a consortial or multi-library
524 environment, where different end-users may need to be represented to
525 some search targets in different ways. This, again, can be managed
526 using an external database or other lookup mechanism. Setting overrides
527 can be performed either using the
528 <link linkend="command-init">init</link> or the
529 <link linkend="command-settings">settings</link> webservice
534 In fact, every setting that applies to a database (except pz:id, which
535 can only be used for filtering targets to use for a search) can be overridden
536 on a per-session basis. This allows the client to override specific CCL fields
537 for searching, etc., to meet the needs of a session or user.
541 Finally, as an extreme case of this, the webservice client can
542 introduce entirely new targets, on the fly, as part of the
543 <link linkend="command-init">init</link> or
544 <link linkend="command-settings">settings</link> command.
545 This is useful if you desire to manage information
546 about your search targets in a separate application such as a database.
547 You do not need any static settings file whatsoever to run Pazpar2 -- as
548 long as the webservice client is prepared to supply the necessary
549 information at the beginning of every session.
554 The following discussion of practical issues related to session and settings
555 management are cast in terms of a user interface based on Ajax/Javascript
556 technology. It would apply equally well to many other kinds of browser-based logic.
561 Typically, a Javascript client is not allowed to directly alter the parameters
562 of a session. There are two reasons for this. One has to do with access
563 to information; typically, information about a user will be stored in a
564 system on the server side, or it will be accessible in some way from the server.
565 However, since the Javascript client cannot be entirely trusted (some hostile
566 agent might in fact 'pretend' to be a regular ws client), it is more robust
567 to control session settings from scripting that you run as part of your
568 webserver. Typically, this can be handled during the session initialization,
573 Step 1: The Javascript client loads, and asks the webserver for a new Pazpar2
574 session ID. This can be done using a Javascript call, for instance. Note that
575 it is possible to submit Ajax HTTPXmlRequest calls either to Pazpar2 or to the
576 webserver that Pazpar2 is proxying for. See (XXX Insert link to Pazpar2 protocol).
580 Step 2: Code on the webserver authenticates the user, by database lookup,
581 LDAP access, NCIP, etc. Determines which resources the user has access to,
582 and any user-specific parameters that are to be applied during this session.
586 Step 3: The webserver initializes a new Pazpar2 settings, and sets user-specific
587 parameters as necessary, using the init webservice command. A new session ID is
592 Step 4: The webserver returns this session ID to the Javascript client, which then
593 uses the session ID to submit searches, show results, etc.
597 Step 5: When the Javascript client ceases to use the session, Pazpar2 destroys
598 any session-specific information.
601 <refsect2><title>SETTINGS FILE FORMAT</title>
603 Each file contains a root element named <settings>. It may
604 contain one or more <set> elements. The settings and set
605 elements may contain the following attributes. Attributes in the set node
606 overrides those in the setting root element. Each set node must
607 specify (directly, or inherited from the parent node) at least a
608 target, name, and value.
616 This specifies the search target to which this setting should be
617 applied. Targets are identified by their Z39.50 URL, generally
618 including the host, port, and database name, (e.g.
619 <literal>bagel.indexdata.com:210/marc</literal>).
620 Two wildcard forms are accepted:
621 * (asterisk) matches all known targets;
622 <literal>bagel.indexdata.com:210/*</literal> matches all
623 known databases on the given host.
626 A precedence system determines what happens if there are
627 overlapping values for the same setting name for the same
628 target. A setting for a specific target name overrides a
629 setting which specifies target using a wildcard. This makes it
630 easy to set defaults for all targets, and then override them
631 for specific targets or hosts. If there are
632 multiple overlapping settings with the same name and target
633 value, the 'precedence' attribute determines what happens.
641 The name of the setting. This can be anything you like.
642 However, Pazpar2 reserves a number of setting names for
643 specific purposes, all starting with 'pz:', and it is a good
644 idea to avoid that prefix if you make up your own setting
645 names. See below for a list of reserved variables.
653 The value of the setting. Generally, this can be anything you
654 want -- however, some of the reserved settings may expect
655 specific kinds of values.
660 <term>precedence</term>
663 This should be an integer. If not provided, the default value
664 is 0. If two (or more) settings have the same content for
665 target and name, the precedence value determines the outcome.
666 If both settings have the same precedence value, they are both
667 applied to the target(s). If one has a higher value, then the
668 value of that setting is applied, and the other one is ignored.
675 By setting defaults for target, name, or value in the root
676 settings node, you can use the settings files in many different
677 ways. For instance, you can use a single file to set defaults for
678 many different settings, like search fields, retrieval syntaxes,
679 etc. You can have one file per server, which groups settings for
680 that server or target. You could also have one file which associates
681 a number of targets with a given setting, for instance, to associate
682 many databases with a given category or class that makes sense
683 within your application.
687 The following examples illustrate uses of the settings system to
688 associate settings with targets to meet different requirements.
692 The example below associates a set of default values that can be
693 used across many targets. Note the wildcard for targets.
694 This associates the given settings with all targets for which no
695 other information is provided.
697 <settings target="*">
699 <!-- This file introduces default settings for pazpar2 -->
701 <!-- mapping for unqualified search -->
702 <set name="pz:cclmap:term" value="u=1016 t=l,r s=al"/>
704 <!-- field-specific mappings -->
705 <set name="pz:cclmap:ti" value="u=4 s=al"/>
706 <set name="pz:cclmap:su" value="u=21 s=al"/>
707 <set name="pz:cclmap:isbn" value="u=7"/>
708 <set name="pz:cclmap:issn" value="u=8"/>
709 <set name="pz:cclmap:date" value="u=30 r=r"/>
711 <!-- Retrieval settings -->
713 <set name="pz:requestsyntax" value="marc21"/>
714 <set name="pz:elements" value="F"/>
716 <!-- Query encoding -->
717 <set name="pz:queryencoding" value="iso-8859-1"/>
719 <!-- Result normalization settings -->
721 <set name="pz:nativesyntax" value="iso2709"/>
722 <set name="pz:xslt" value="../etc/marc21.xsl"/>
730 The next example shows certain settings overridden for one target,
731 one which returns XML records containing DublinCore elements, and
732 which furthermore requires a username/password.
734 <settings target="funkytarget.com:210/db1">
735 <set name="pz:requestsyntax" value="xml"/>
736 <set name="pz:nativesyntax" value="xml"/>
737 <set name="pz:xslt" value="../etc/dublincore.xsl"/>
739 <set name="pz:authentication" value="myuser/password"/>
745 The following example associates a specific name/value combination
746 with a number of targets. The targets below are access-restricted,
747 and can only be used by users with special credentials.
749 <settings name="pz:allow" value="0">
750 <set target="funkytarget.com:210/*"/>
751 <set target="commercial.com:2100/expensiveDb"/>
758 <refsect2><title>RESERVED SETTING NAMES</title>
760 The following setting names are reserved by Pazpar2 to control the
761 behavior of the client function.
766 <term>pz:cclmap:xxx</term>
769 This establishes a CCL field definition or other setting, for
770 the purpose of mapping end-user queries. XXX is the field or
771 setting name, and the value of the setting provides parameters
772 (e.g. parameters to send to the server, etc.). Please consult
773 the YAZ manual for a full overview of the many capabilities of
774 the powerful and flexible CCL parser.
777 Note that it is easy to establish a set of default parameters,
778 and then override them individually for a given target.
782 <varlistentry id="requestsyntax">
783 <term>pz:requestsyntax</term>
786 This specifies the record syntax to use when requesting
787 records from a given server. The value can be a symbolic name like
788 marc21 or xml, or it can be a Z39.50-style dot-separated OID.
793 <term>pz:elements</term>
796 The element set name to be used when retrieving records from a
802 <term>pz:piggyback</term>
805 Piggybacking enables the server to retrieve records from the
806 server as part of the search response in Z39.50. Almost all
807 servers support this (or fail it gracefully), but a few
808 servers will produce undesirable results.
809 Set to '1' to enable piggybacking, '0' to disable it. Default
810 is 1 (piggybacking enabled).
815 <term>pz:nativesyntax</term>
818 The representation (syntax) of the retrieval records. Currently
819 recognized values are iso2709 and xml.
822 For iso2709, can also specify a native character set, e.g. "iso2709;latin-1".
823 If no character set is provided, MARC-8 is assumed.
826 If pz:nativesyntax is not specified, pazpar2 will attempt to determine
827 the value based on the response from the server.
833 <term>pz:queryencoding</term>
836 The encoding of the search terms that a target accepts. Most
837 targets do not honor UTF-8 in which case this needs to be specified.
838 Each term in a query will be converted if this setting is given.
847 Is a comma separated list of of files that specifies
848 how to convert incoming records to the internal representation.
851 The suffix of each file specifies the kind of tranformation.
852 Suffix "<literal>.xsl</literal>" makes an XSL transform. Suffix
853 "<literal>.mmap</literal>" will use the MMAP transform (described below).
856 The special value "<literal>auto</literal>" will use a file
857 which is the <link linkend="requestsyntax">pz:requestsyntax's</link>
859 <literal>'.xsl'</literal>.
862 When mapping MARC records, XSLT can be bypassed for increased
863 performance with the alternate "MARC map" format. Provide the
864 path of a file with extension ".mmap" containing on each line:
866 <field> <subfield> <metadata element></programlisting>
871 773 * citation</programlisting>
872 To map the field value specify a subfield of '$'. To store a
873 concatenation of all subfields, specify a subfield of '*'.
878 <term>pz:authentication</term>
881 Sets an authentication string for a given server. See the section on
882 authorization and authentication for discussion.
887 <term>pz:allow</term>
890 Allows or denies access to the resources it is applied to. Possible
891 values are '0' and '1'. The default is '1' (allow access to this resource).
892 See the manual section on authorization and authentication for discussion
893 about how to use this setting.
898 <term>pz:maxrecs</term>
901 Controls the maximum number of records to be retrieved from a
902 server. The default is 100.
910 This setting can't be 'set' -- it contains the ID (normally
911 ZURL) for a given target, and is useful for filtering --
912 specifically when you want to select one or more specific
913 targets in the search command.
918 <term>pz:zproxy</term>
921 The 'pz:zproxy' setting has the value syntax
922 'host.internet.adress:port', it is used to tunnel Z39.50
923 requests through the named Z39.50 proxy.
929 <term>pz:apdulog</term>
932 If the 'pz:apdulog' setting is defined and has other value than 0,
933 then Z39.50 APDUs are written to the log.
942 This setting enables SRU/SRW support. It has three possible settings.
943 'get', enables SRU access through GET requests. 'post' enables SRU/POST
944 support, less commonly supported, but useful if very large requests are
945 to be submitted. 'srw' enables the SRW variation of the protocol.
951 <term>pz:sru_version</term>
954 This allows SRU version to be specified. If unset Pazpar2
955 will the default of YAZ (currently 1.2). Should be set
962 <term>pz:pqf_prefix</term>
965 Allows you to specify an arbitrary PQF query language substring.
966 The provided string is prefixed the user's query after it has been
967 normalized to PQF internally in pazpar2.
968 This allows you to attach complex 'filters' to queries for a given
969 target, sometimes necessary to select sub-catalogs
970 in union catalog systems, etc.
976 <term>pz:pqf_strftime</term>
979 Allows you to extend a query with dates and operators.
980 The provided string allows certain substitutions and serves as a
982 The special two character sequence '%%' gets converted to the
983 original query. Other characters leading with the percent sign are
984 conversions supported by strftime.
985 All other characters are copied verbatim. For example, the string
986 <literal>@and @attr 1=30 @attr 2=3 %Y %%</literal>
987 would search for current year combined with the original PQF (%%).
996 Specifies sort criteria to be applied to the result set.
997 Only works for targets which support the sort service.
1003 <term>pz:recordfilter</term>
1006 Specifies a filter which allows Pazpar2 to only include
1007 records that meet a certain criteria in a result. Unmatched records
1008 will be ignored. The filter takes the form name[~value] , which
1009 will include only records with metadata element (name) that has the
1010 substring (value) given. If value is omitted all records with the
1011 metadata present will be included.
1020 <refsect1><title>SEE ALSO</title>
1023 <refentrytitle>pazpar2</refentrytitle>
1024 <manvolnum>8</manvolnum>
1027 <refentrytitle>yaz-icu</refentrytitle>
1028 <manvolnum>1</manvolnum>
1031 <refentrytitle>pazpar2_protocol</refentrytitle>
1032 <manvolnum>7</manvolnum>
1037 <!-- Keep this comment at the end of the file
1042 sgml-minimize-attributes:nil
1043 sgml-always-quote-attributes:t
1046 sgml-parent-document:nil
1047 sgml-local-catalogs: nil
1048 sgml-namecase-general:t