1 <?xml version="1.0" standalone="no"?>
2 <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.4//EN"
3 "http://www.oasis-open.org/docbook/xml/4.4/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_protocol">
14 <productname>Pazpar2</productname>
15 <productnumber>&version;</productnumber>
16 <info><orgname>Index Data</orgname></info>
19 <refentrytitle>Pazpar2 protocol</refentrytitle>
20 <manvolnum>7</manvolnum>
21 <refmiscinfo class="manual">Conventions and miscellaneous</refmiscinfo>
25 <refname>pazpar2_protocol</refname>
26 <refpurpose>The webservice protocol of Pazpar2</refpurpose>
30 <title>DESCRIPTION</title>
32 Webservice requests are any that refer to filename "search.pz2". Arguments
33 are GET-style parameters. Argument 'command' is always required and specifies
34 the operation to perform. Any request not recognized as a webservice
35 request is forwarded to the HTTP server specified in the configuration
36 using the proxy setting.
37 This way, a regular webserver can host the user interface (itself dynamic
38 or static HTML), and Ajax-style calls can be used from JS (or any other
39 client-based scripting environment) to interact with the search logic
43 Each command is described in sub sections to follow.
45 <refsect2 id="command-init">
48 Initializes a session.
49 Returns session ID to be used in subsequent requests. If
50 a server ID is given in the Pazpar2 server section, then a
51 that is included in the session ID as suffix after a period (.).
54 If the init command is performed as a HTTP GET request, service
55 and settings from local files are used. The service parameter
56 may chose a particular local service.
59 If the init command is performed as a HTTP POST request and
60 the content-type is text/xml, then the content is XML parsed
61 and treated as service for the session. The root element should be
62 service. Refer to descripton of the
63 <link linkend="service_conf">service</link> format.
64 The posting of a service appeared in Pazpar2 version 1.2.1.
69 search.pz2?command=init
78 <session>2044502273</session>
82 The init command may take a number of setting parameters, similar to
83 the 'settings' command described below. These settings are immediately
84 applied to the new session. Other parameters for init are:
90 If this is defined and the value is non-zero, the session will
91 not use the predefined databases in the configuration; only those
92 specified in the settings parameters (per session databases).
101 If this is defined it specifies a service ID. Makes the session use
102 the service with this ID. If this is setting is omitted, the
103 session will use the unnamed service in the Pazpar2 configuration.
111 <refsect2 id="command-ping">
114 Keeps a session alive. An idle session will time out after one minute.
115 The ping command can be used to keep the session alive absent other
117 It is suggested that any browser client have a simple alarm handler which
118 sends a ping every 50 seconds or so once a session has been initialized.
123 search.pz?command=ping&session=2044502273
134 <refsect2 id="command-settings">
135 <title>settings</title>
137 The settings command applies session-specific settings to one or more
138 databases. A typical function of this is to enable access to
139 restricted resources for registered users, or to set a user- or
140 library-specific username/password to use against a target.
143 Each setting parameter has the form name[target]=value, where name is the
144 name of the setting (e.g. pz:authentication), target is a target ID,
145 or possibly a wildcard, and value is the desired value for the
150 Because the settings command manipulates potentially sensitive
151 information, it is possible to configure Pazpar2 to only allow access
152 to this command from a trusted site -- usually from server-side
153 scripting, which in turn is responsible for authenticating the user,
154 and possibly determining which resources he has access to, etc.
159 As a shortcut, it is also possible to override settings directly in
165 If the settings command is performed as HTTP POST and the content-type
166 is text/xml, then the content is XML parsed and treated as settings -
167 with a format identical to local
168 <link linkend="target_settings">settings files</link>.
169 The posting of settings appeared in Pazpar version 1.2.1.
175 search.pz?command=settings&session=2044502273&pz:allow[search.com:210/db1]=1
186 <refsect2 id="command-search">
187 <title>search</title>
189 Launches a search, parameters:
212 Limits the search to a given set of targets specified by the
213 filter. The filter consists a comma separated list of
214 <emphasis>setting</emphasis>+<emphasis>operator</emphasis>+<emphasis>args</emphasis>
215 pairs. The <emphasis>setting</emphasis> is a Pazpar2 setting
216 (such as <literal>pz:id</literal>).
217 The <emphasis>operator</emphasis> is either
218 <literal>=</literal> (string match)
219 or <literal>~</literal> (substring match).
220 The <emphasis>args</emphasis> is a list of values separated
221 by <literal>|</literal> (or , one of the values).
222 The idea is that only targets with a setting matching one of
223 the values given will be included in the search.
231 Narrows the search by one or more fields (typically facets).
232 The limit is sequence of one or more
233 <emphasis>name</emphasis>=<emphasis>args</emphasis> pairs separated
234 by comma. The <emphasis>args</emphasis> is a list of values
235 separated by vertical bar (<literal>|</literal>).
236 The meaning of <literal>|</literal> is alternative, ie OR .
237 A value that contains a comma (<literal>,</literal>),
238 a vertical bar (<literal>|</literal>) or
239 backslash itself must be preceded by backslash (<literal>\</literal>).
240 The <link linkend="limitmap">pz:limitmap</link> configuration
241 item defines how the searches are mapped to a database.
246 <term>startrecs</term>
249 Specifies the first record to retrieve from each target.
250 The first record in a result set for a target is numbered 0, next
251 record is numbered 2. By default maxrecs is 0.
259 Specifies the maximum number of records to retrieve from each
260 target. The default value is 100. This setting has same meaning
261 as per-target setting pz:maxrecs . If pz:maxrecs is set, it takes
262 precedence over argument maxrecs.
270 Specifies sort criteria. The argument is a comma-separated list
271 (no whitespace allowed) of sort fields, with the highest-priority
272 field first. A sort field may be followed by a colon followed by
273 the number '0' (decreasing) or '1' (increasing). Default
274 sort order is decreasing.
275 Sort field names can be any field name designated as a sort field
276 in the pazpar2.cfg file, or the special names 'relevance' and
280 If not specified here or as <link linkend="sort-default">sort-default"</link>
281 in pazpar2.cfg, Pazpar2 will default to the built-in 'relevance' ranking.
284 Having sort criteria at search is important for targets that
285 supports native sorting in order to get best results. Pazpar2
286 will trigger a new search if search criteria changes from Pazpar2
287 to target-based sorting or visa-versa.
293 <term>mergekey</term>
296 Sets mergekey for this search and rest of session, or until
297 another mergekey is given for show/search. The mergekey value is a
298 comma separated list with one or more names as they appear
299 in the service description equivalent to
300 <literal>mergekey="optional"</literal> inside a metadata element.
301 If the empty string is given for mergekey it is disabled
302 and rest of session will use the default mergekey from service
306 This facility, "dynamic mergekey", appeared in Pazpar2 version
316 Sets rank method this search and rest of session, or until
317 another rank is given for show/search. The rank value is a
318 comma separated list of pairs field=value pairs. The
319 format is the same as
320 <xref linkend="metadata-rank">rank</xref> for a metadata element.
321 If the empty string is given for rank it is disabled
322 and rest of session will use the default rank from metadata or
326 This facility, "dynamic ranking", appeared in Pazpar2 version
338 search.pz2?session=2044502273&command=search&query=computer+science
350 <refsect2 id="command-stat">
353 Provides status information about an ongoing search. Parameters:
370 search.pz2?session=2044502273&command=stat
375 <activeclients>3</activeclients>
376 <hits>7</hits> -- Total hitcount
377 <records>7</records> -- Total number of records fetched in last query
378 <clients>1</clients> -- Total number of associated clients
379 <unconnected>0</unconnected> -- Number of disconnected clients
380 <connecting>0</connecting> -- Number of clients in connecting state
381 <initializing>0</initializing> -- Number of clients initializing
382 <searching>0</searching> -- ... searching
383 <presenting>0</presenting> -- ... presenting
384 <idle>1</idle> -- ... idle (not doing anything)
385 <failed>0</failed> -- ... Connection failed
386 <error>0</error> -- ... Error was produced somewhere
392 <refsect2 id="command-show">
395 Shows records retrieved. Parameters:
409 <para>First record to show - 0-indexed.</para>
417 Number of records to show If omitted, 20 is used.
426 If block is set to 1, the command will hang until there are records
427 ready to display. Use this to show first records rapidly without
428 requiring rapid polling.
437 Specifies sort criteria. The argument is a comma-separated list
438 (no whitespace allowed) of sort fields, with the highest-priority
439 field first. A sort field may be followed by a colon followed by
440 the number '0' (decreasing) or '1' (increasing). Default
441 sort order is decreasing.
442 Sort field names can be any field name designated as a sort field
443 in the pazpar2.cfg file, or the special names 'relevance' and
446 If not specified here or as <link linkend="sort-default">sort-default"</link>
447 in pazpar2.cfg, pazpar2 will default to the built-in 'relevance' ranking.
449 Having sort criteria at search is important for targets that
450 supports native sorting in order to get best results. pazpar2
451 will trigger a new search if search criteria changes from pazpar2
452 to target-based sorting.
456 For targets where If <link linkend="pzsortmap">pz:sortmap</link>
457 is defined, a sort operation will be executed (possibly including
458 extending the search).
464 <term>mergekey</term>
467 Sets mergekey for this show and rest of session, or until
468 another mergekey is given for show/search. The mergekey value is a
469 comma separated list with one or more names as they appear
470 in the service description equivalent to
471 <literal>mergekey="optional"</literal> inside a metadata element.
472 If the empty string is given for mergekey it is disabled
473 and rest of session will use the default mergekey from service
477 This facility, "dynamic mergekey", appeared in Pazpar2 version
487 Sets rank method this show and rest of session, or until
488 another rank is given for show/search. The rank value is a
489 comma separated list of pairs field=value pairs. The
490 format is the same as
491 <xref linkend="metadata-rank">rank</xref> for a metadata element.
492 If the empty string is given for rank it is disabled
493 and rest of session will use the default rank from metadata or
497 This facility, "dynamic ranking", appeared in Pazpar2 version
504 <term>snippets</term>
507 If specified and set to 1 data will include snippets marked
508 with <match> tags. Otherwise snippets will not be included.
511 This facility, "snippets", appeared in Pazpar2 version
522 search.pz2?session=2044502273&command=show&start=0&num=2&sort=title:1
528 <activeclients>3</activeclients> -- How many clients are still working
529 <merged>6</merged> -- Number of merged records
530 <total>7</total> -- Total of all hitcounts
531 <start>0</start> -- The start number you requested
532 <num>2</num> -- Number of records retrieved
534 <md-title>How to program a computer, by Jack Collins</md-title>
535 <count>2</count> -- Number of merged records
536 <recid>6</recid> -- Record ID for this record
540 Computer processing of dynamic images from an Anger scintillation camera :
541 the proceedings of a workshop /
550 <refsect2 id="command-record">
551 <title>record</title>
553 Retrieves a detailed record. Unlike the
554 <link linkend="command-show">show</link> command, this command
555 returns metadata records before merging takes place. Parameters:
571 record ID as provided by the
572 <link linkend="command-show">show</link> command.
581 This optional parameter is an integer which, when given, makes
582 Pazpar2 return the original record for a specific target.
583 The record set from first target is numbered 0,
584 second record set is numbered 1, etc.
585 The nativesyntax setting, as usual, is used to determine how to
586 create XML from the original record - unless parameter
587 <literal>binary</literal> is given in which the record is
588 fetched as "raw" from ZOOM C (raw, original record).
591 When offset/checksum is not given, the Pazpar2 metadata for the record
592 is returned and with metadata for each targets' data specified
593 in a 'location' list.
599 <term>checksum</term>
602 This optional parameter is a string which, when given, makes
603 Pazpar2 return the original record for a specific target. The
604 checksum is returned as attribtue 'checksum' in element
605 'location' for show command and record command (when checksum
606 and offset is NOT given).
607 The nativesyntax setting, as usual, is used to determine how to
608 create XML from the original record - unless parameter
609 <literal>binary</literal> is given in which the record is
610 fetched as "raw" from ZOOM C (raw, original record).
613 When offset/checksum is not given, the Pazpar2 metadata for the record
614 is returned and with metadata for each targets' data specified
615 in a 'location' list.
622 <term>nativesyntax</term>
625 This optional parameter can be used to override pz:nativesyntax
626 as given for the target. This allow an alternative nativesyntax
627 to be used for original records (see parameteroffset above).
636 This optional parameter is the record syntax used for raw
637 transfer (i.e. when offset is specified). If syntax is not given,
638 but offset is used, the value of pz:requestsyntax is used.
647 This optional parameter is the element set name used to retrieval
648 of a raw record (i.e. when offset is specified).
649 If esn is not given, but offset is used, the value of pz:elements
659 This optional parameter enables "binary" response for retrieval
660 of a original record (i.e. when offset is specified). For binary
661 response the record by default is fetched from ZOOM C using
662 the "raw" option or by parameter nativesyntax if given.
668 <term>snippets</term>
671 If specified and set to 1 data will include snippets marked
672 with <match> tags. Otherwise snippets will not be included.
675 This facility, "snippets", appeared in Pazpar2 version
686 search.pz2?session=605047297&command=record&id=3
694 The Puget Sound Region : a portfolio of thematic computer maps /
696 <md-date>1974</md-date>
697 <md-author>Mairs, John W.</md-author>
698 <md-subject>Cartography</md-subject>
704 <refsect2 id="command-termlist">
705 <title>termlist</title>
707 Retrieves term list(s). Parameters:
722 comma-separated list of termlist names. If omitted,
723 all termlists are returned.
731 maximum number of entries to return - default is 15.
740 search.pz2?session=2044502273&command=termlist&name=author,subject
745 <activeclients>3</activeclients>
748 <name>Donald Knuth</name>
749 <frequency>10</frequency>
752 <name>Robert Pirsig</name>
753 <frequency>2</frequency>
756 <list name="subject">
758 <name>Computer programming</name>
759 <frequency>10</frequency>
767 For the special termlist name "xtargets", results
768 are returned about the targets which have returned the most hits.
769 The 'term' subtree has additional elements,
770 specifically a state and diagnostic field (in the example below, a
771 target ID is returned in place of 'name'.
772 This may or may not change later.
778 <name>library2.mcmaster.ca</name>
779 <frequency>11734</frequency> -- Number of hits
780 <state>Client_Idle</state> -- See the description of 'bytarget' below
781 <diagnostic>0</diagnostic> -- Z39.50 diagnostic codes
788 <refsect2 id="command-bytarget">
789 <title>bytarget</title>
791 Returns information about the status of each active client. Parameters:
807 search.pz2?session=605047297&command=bytarget&id=3
816 <id>z3950.loc.gov/voyager/</id>
818 <diagnostic>0</diagnostic>
819 <records>65</records>
820 <state>Client_Presenting</state>
822 <!-- ... more target nodes below as necessary -->
826 The following client states are defined: Client_Connecting,
827 Client_Connected, Client_Idle, Client_Initializing, Client_Searching,
828 Client_Searching, Client_Presenting, Client_Error, Client_Failed,
829 Client_Disconnected, Client_Stopped, Client_Continue.
833 <refsect2 id="command-service">
834 <title>service</title>
836 Returns service definition (XML). Parameters:
849 The service command appeared in Pazpar2 version 1.6.32
854 <title>SEE ALSO</title>
858 <refentrytitle>pazpar2</refentrytitle>
859 <manvolnum>8</manvolnum>
863 Pazpar2 Configuration:
865 <refentrytitle>pazpar2_conf</refentrytitle>
866 <manvolnum>5</manvolnum>
872 <!-- Keep this comment at the end of the file