1 <?xml version="1.0" standalone="no"?>
2 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML 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">
14 <title>Pazpar2 - User's Guide and Reference</title>
16 <firstname>Sebastian</firstname><surname>Hammer</surname>
19 <firstname>Adam</firstname><surname>Dickmeiss</surname>
22 <firstname>Marc</firstname><surname>Cromme</surname>
25 <firstname>Jakub</firstname><surname>Skoczen</surname>
28 <firstname>Mike</firstname><surname>Taylor</surname>
30 <releaseinfo>&version;</releaseinfo>
32 <year>©right-year;</year>
33 <holder>Index Data</holder>
37 Pazpar2 is a high-performance metasearch engine featuring
38 merging, relevance ranking, record sorting,
40 It is middleware: it has no user interface of its own, but can be
41 configured and controlled by an XML-over-HTTP web-service to provide
42 metasearching functionality behind any user interface.
45 This document is a guide and reference to Pazpar2 version &version;.
50 <imagedata fileref="common/id.png" format="PNG"/>
53 <imagedata fileref="common/id.eps" format="EPS"/>
60 <chapter id="introduction">
61 <title>Introduction</title>
63 <section id="what.pazpar2.is">
64 <title>What Pazpar2 is</title>
66 Pazpar2 is a stand-alone metasearch engine with a web-service API, designed
67 to be used either from a browser-based client (JavaScript, Flash,
69 etc.), from server-side code, or any combination of the two.
70 Pazpar2 is a highly optimized client designed to
71 search many resources in parallel. It implements record merging,
72 relevance-ranking and sorting by arbitrary data content, and facet
73 analysis for browsing purposes. It is designed to be data-model
74 independent, and is capable of working with MARC, DublinCore, or any
75 other <ulink url="&url.xml;">XML</ulink>-structured response format
76 -- <ulink url="&url.xslt;">XSLT</ulink> is used to normalize and extract
77 data from retrieval records for display and analysis. It can be used
78 against any server which supports the
79 <ulink url="&url.z39.50;">Z39.50</ulink> or <ulink url="&url.sru;">SRU/SRW</ulink>
81 backend modules can function as connectors between these standard
82 protocols and any non-standard API, including web-site scraping, to
83 support a large number of other protocols.
86 Additional functionality such as
87 user management and attractive displays are expected to be implemented by
88 applications that use Pazpar2. Pazpar2 itself is user-interface independent.
89 Its functionality is exposed through a simple XML-based web-service API,
90 designed to be easy to use from an Ajax-enabled browser, Flash
91 animation, Java applet, etc., or from a higher-level server-side language
92 like PHP, Perl or Java. Because session information can be shared between
93 browser-based logic and server-side scripting, there is tremendous
94 flexibility in how you implement application-specific logic on top
98 Once you launch a search in Pazpar2, the operation continues behind the
99 scenes. Pazpar2 connects to servers, carries out searches, and
100 retrieves, deduplicates, and stores results internally. Your application
101 code may periodically inquire about the status of an ongoing operation,
102 and ask to see records or result set facets. Results become
103 available immediately, and it is easy to build end-user interfaces than
104 feel extremely responsive, even when searching more than 100 servers
108 Pazpar2 is designed to be highly configurable. Incoming records are
109 normalized to XML/UTF-8, and then further normalized using XSLT to a
110 simple internal representation that is suitable for analysis. By
111 providing XSLT stylesheets for different kinds of result records, you
112 can configure Pazpar2 to work against different kinds of information
113 retrieval servers. Finally, metadata is extracted in a configurable
114 way from this internal record, to support display, merging, ranking,
115 result set facets, and sorting. Pazpar2 is not bound to a specific model
116 of metadata, such as DublinCore or MARC: by providing the right
117 configuration, it can work with any combination of different kinds of data in
118 support of many different applications.
121 Pazpar2 is designed to be efficient and scalable. You can set it up to
122 search several hundred targets in parallel, or you can use it to support
123 hundreds of concurrent users. It is implemented with the same attention
124 to performance and economy that we use in our indexing engines, so that
125 you can focus on building your application without worrying about the
126 details of metasearch logic. You can devote all of your attention to
127 usability and let Pazpar2 do what it does best -- metasearch.
130 Pazpar2 is our attempt to re-think the traditional paradigms for
131 implementing and deploying metasearch logic, with an uncompromising
132 approach to performance, and attempting to make maximum use of the
133 capabilities of modern browsers. The demo user interface that
134 accompanies the distribution is but one example. If you think of new
135 ways of using Pazpar2, we hope you'll share them with us, and if we
136 can provide assistance with regards to training, design, programming,
137 integration with different backends, hosting, or support, please don't
138 hesitate to contact us. If you'd like to see functionality in Pazpar2
139 that is not there today, please don't hesitate to contact us. It may
140 already be in our development pipeline, or there might be a
141 possibility for you to help out by sponsoring development time or
142 code. Either way, get in touch and we will give you straight answers.
148 Pazpar2 is covered by the GNU General Public License (GPL) version 2.
149 See <xref linkend="license"/> for further information.
153 <section id="connectors">
154 <title>Connectors to non-standard databases</title>
156 If you wish to connect to commercial or other databases which do not
157 support open standards, please contact Index Data on
158 <email>info@indexdata.com</email>. We have a
159 proprietary framework for building connectors that enable Pazpar2
161 thousands of online databases, in addition to the vast number of catalogs
162 and online services that support the Z39.50/SRU/SRW protocols.
167 <title>A note on the name Pazpar2</title>
169 The name Pazpar2 derives from three sources. One one hand, it is
170 Index Data's second major piece of software that does parallel
171 searching of Z39.50 targets. On the other, it is a near-homophone
172 of Passpartout, the ever-helpful servant in Jules Verne's novel
173 Around the World in Eighty Days (who helpfully uses the language
174 of his master). Finally, "passe par tout" means something like
175 "passes through anything" in French -- on other words, a universal
176 solution, or if you like a MasterKey.
181 <chapter id="installation">
182 <title>Installation</title>
184 The Pazpar2 package is very small. It includes documentation as well
185 as the Pazpar2 server. The package also includes a simple user
186 interface test1 which consists of a single HTML page and a single
187 JavaScript file to illustrate the use of Pazpar2.
190 Pazpar2 depends on the following tools/libraries:
192 <varlistentry><term><ulink url="&url.yaz;">YAZ</ulink></term>
195 The popular Z39.50 toolkit for the C language.
196 YAZ <emphasis>must</emphasis> be compiled with Libxml2/Libxslt support.
200 <varlistentry><term><ulink url="&url.icu;">International
201 Components for Unicode (ICU)</ulink></term>
204 ICU provides Unicode support for non-English languages with
205 character sets outside the range of 7bit ASCII, like
206 Greek, Russian, German and French. Pazpar2 uses the ICU
207 Unicode character conversions, Unicode normalization, case
208 folding and other fundamental operations needed in
209 tokenization, normalization and ranking of records.
212 Compiling, linking, and usage of the ICU libraries is optional,
213 but strongly recommended for usage in an international
221 In order to compile Pazpar2, a C compiler which supports C99 or later
225 <section id="installation.unix">
226 <title>Installation on Unix (from Source)</title>
228 The latest source code for Pazpar2 is available from
229 <ulink url="&url.pazpar2.download;"/>.
230 Only few systems have none of the required
231 tools binary packages.
232 If, for example, Libxml2/libXSLT libraries
233 are already installed as development packages use these.
237 Ensure that the development libraries + header files are
238 available on your system before compiling Pazpar2. For installation
239 of YAZ, refer to the YAZ installation chapter.
242 gunzip -c pazpar2-version.tar.gz|tar xf -
250 The <literal>make install</literal> will install manpages as well as the
251 Pazpar2 server, <literal>pazpar2</literal>,
252 in PREFIX<literal>/sbin</literal>.
253 By default, PREFIX is <literal>/usr/local/</literal> . This can be
254 changed with configure option <option>--prefix</option>.
258 <section id="installation.win32">
259 <title>Installation on Windows (from Source)</title>
261 Pazpar2 can be built for Windows using
262 <ulink url="&url.vstudio;">Microsoft Visual Studio</ulink>.
263 The support files for building YAZ on Windows are located in the
264 <filename>win</filename> directory. The compilation is performed
265 using the <filename>win/makefile</filename> which is to be
266 processed by the NMAKE utility part of Visual Studio.
269 Ensure that the development libraries + header files are
270 available on your system before compiling Pazpar2. For installation
271 of YAZ, refer to the YAZ installation chapter.
272 It is easiest if YAZ and Pazpar2 are unpacked in the same
273 directory (side-by-side).
276 The compilation is tuned by editing the makefile of Pazpar2.
277 The process is similar to YAZ. Adjust the various directories
278 <literal>YAZ_DIR</literal>, <literal>ZLIB_DIR</literal>, ..
281 Compile Pazpar2 by invoking <application>nmake</application> in
282 the <filename>win</filename> directory.
283 The resulting binaries of the build process are located in the
284 <filename>bin</filename> of the Pazpar2 source
285 tree - including the <filename>pazpar2.exe</filename> and necessary DLLs.
288 The Windows version of Pazpar2 is a console application. It may
289 be installed as a Windows Service by adding option
290 <literal>-install</literal> for the pazpar2 program. This will
291 register Pazpar2 as a service and use the other options provided
292 in the same invocation. For example:
295 ..\bin\pazpar2 -install -f pazpar2.cfg -l pazpar2.log
297 The Pazpar2 service may now be controlled via the Service Control
298 Panel. It may be unregistered by passing the <literal>-remove</literal>
302 ..\bin\pazpar2 -remove
307 <section id="installation.test1">
308 <title>Installation of test1 interface</title>
310 In this section we outline how to install a simple interface that
311 is part of the Pazpar2 source package. Note that Debian users can
312 save time by just installing package <literal>pazpar2-test1</literal>.
315 A web server must be installed and running on the system, such as Apache.
319 Start the Pazpar2 daemon using the 'in-source' binary of the Pazpar2
320 daemon. On Unix the process is:
323 cp pazpar2.cfg.dist pazpar2.cfg
324 ../src/pazpar2 -f pazpar2.cfg
329 copy pazpar2.cfg.dist pazpar2.cfg
330 ..\bin\pazpar2 -f pazpar2.cfg
332 This will start a Pazpar2 listener on port 9004. It will proxy
333 HTTP requests to localhost - port 80, which we assume will be the regular
334 HTTP server on the system. Inspect and modify pazpar2.cfg as needed
335 if this is to be changed. The pazpar2.cfg includes settings from the
336 file <filename>settings/edu.xml</filename>
340 Make a new console and move to the other stuff.
341 For more information about pazpar2 options refer to the manpage.
345 The test1 UI is located in <literal>www/test1</literal>. Ensure this
346 directory is available to the web server by either copying
347 <literal>test1</literal> to the document root, create a symlink or
348 use Apache's <literal>Alias</literal> directive.
352 The interface test1 interface should now be available on port 8004.
355 If you don't see the test1 interface. See if test1 is really available
356 on the same URL but on port 80. If it's not, the Apache configuration
357 (or other) is not correct.
360 In order to use Apache as frontend for the interface on port 80
361 for public access etc., refer to
362 <xref linkend="installation.apache2proxy"/>.
366 <section id="installation.debian">
367 <title>Installation on Debian GNU/Linux</title>
369 Index Data provides Debian packages for Pazpar2. These are prepared
370 for Debian versions Etch and Lenny (as of 2007).
371 These packages are available at
372 <ulink url="&url.pazpar2.download.debian;"/>.
376 <section id="installation.apache2proxy">
377 <title>Apache 2 Proxy</title>
380 <ulink url="http://httpd.apache.org/docs/2.2/mod/mod_proxy.html">
382 </ulink> which allows Pazpar2 to become a backend to an Apache 2
383 based web service. The Apache 2 proxy must operate in the
384 <emphasis>Reverse</emphasis> Proxy mode.
388 On a Debian based Apache 2 system, the relevant modules can
391 sudo a2enmod proxy_http
396 Traditionally Pazpar2 interprets URL paths with suffix
397 <literal>/search.pz2</literal>.
400 url="http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxypass"
401 >ProxyPass</ulink> directive of Apache must be used to map a URL path
402 the the Pazpar2 server (listening port).
407 The ProxyPass directive takes a prefix rather than
408 a suffix as URL path. It is important that the Java Script code
409 uses the prefix given for it.
413 <example id="installation.apache2proxy.example">
414 <title>Apache 2 proxy configuration</title>
416 If Pazpar2 is running on port 8004 and the portal is using
417 <filename>search.pz2</filename> inside portal in directory
418 <filename>/myportal/</filename> we could use the following
419 Apache 2 configuration:
422 <IfModule mod_proxy.c>
426 AddDefaultCharset off
431 ProxyPass /myportal/search.pz2 http://localhost:8004/search.pz2
442 <title>Using Pazpar2</title>
444 This chapter provides a general introduction to the use and
445 deployment of Pazpar2.
448 <section id="architecture">
449 <title>Pazpar2 and your systems architecture</title>
451 Pazpar2 is designed to provide asynchronous, behind-the-scenes
452 metasearching functionality to your application, exposing this
453 functionality using a simple webservice API that can be accessed
454 from any number of development environments. In particular, it is
455 possible to combine Pazpar2 either with your server-side dynamic
456 website scripting, with scripting or code running in the browser, or
457 with any combination of the two. Pazpar2 is an excellent tool for
458 building advanced, Ajax-based user interfaces for metasearch
459 functionality, but it isn't a requirement -- you can choose to use
460 Pazpar2 entirely as a backend to your regular server-side scripting.
461 When you do use Pazpar2 in conjunction
462 with browser scripting (JavaScript/Ajax, Flash, applets,
463 etc.), there are special considerations.
467 Pazpar2 implements a simple but efficient HTTP server, and it is
468 designed to interact directly with scripting running in the browser
469 for the best possible performance, and to limit overhead when
470 several browser clients generate numerous webservice requests.
471 However, it is still desirable to use a conventional webserver,
472 such as Apache, to serve up graphics, HTML documents, and
473 server-side scripting. Because the security sandbox environment of
474 most browser-side programming environments only allows communication
475 with the server from which the enclosing HTML page or object
476 originated, Pazpar2 is designed so that it can act as a transparent
477 proxy in front of an existing webserver (see <xref
478 linkend="pazpar2_conf"/> for details).
479 In this mode, all regular
480 HTTP requests are transparently passed through to your webserver,
481 while Pazpar2 only intercepts search-related webservice requests.
485 If you want to expose your combined service on port 80, you can
486 either run your regular webserver on a different port, a different
487 server, or a different IP address associated with the same server.
491 Pazpar2 can also work behind
492 a reverse Proxy. Refer to <xref linkend="installation.apache2proxy"/>)
493 for more information.
494 This allows your existing HTTP server to operate on port 80 as usual.
495 Pazpar2 can be started on another (internal) port.
499 Sometimes, it may be necessary to implement functionality on your
500 regular webserver that makes use of search results, for example to
501 implement data import functionality, emailing results, history
502 lists, personal citation lists, interlibrary loan functionality,
503 etc. Fortunately, it is simple to exchange information between
504 Pazpar2, your browser scripting, and backend server-side scripting.
505 You can send a session ID and possibly a record ID from your browser
506 code to your server code, and from there use Pazpar2s webservice API
507 to access result sets or individual records. You could even 'hide'
508 all of Pazpar2s functionality between your own API implemented on
509 the server-side, and access that from the browser or elsewhere. The
510 possibilities are just about endless.
514 <section id="data_model">
515 <title>Your data model</title>
517 Pazpar2 does not have a preconceived model of what makes up a data
518 model. There are no assumptions that records have specific fields or
519 that they are organized in any particular way. The only assumption
520 is that data comes packaged in a form that the software can work
521 with (presently, that means XML or MARC), and that you can provide
522 the necessary information to massage it into Pazpar2's internal
527 Handling retrieval records in Pazpar2 is a two-step process. First,
528 you decide which data elements of the source record you are
529 interested in, and you specify any desired massaging or combining of
530 elements using an XSLT stylesheet (MARC records are automatically
531 normalized to <ulink url="&url.marcxml;">MARCXML</ulink> before this step).
532 If desired, you can run multiple XSLT stylesheets in series to accomplish
533 this, but the output of the last one should be a representation of the
534 record in a schema that Pazpar2 understands.
538 The intermediate, internal representation of the record looks like
541 <record xmlns="http://www.indexdata.com/pazpar2/1.0"
542 mergekey="title The Shining author King, Stephen">
544 <metadata type="title">The Shining</metadata>
546 <metadata type="author">King, Stephen</metadata>
548 <metadata type="kind">ebook</metadata>
550 <!-- ... and so on -->
554 As you can see, there isn't much to it. There are really only a few
555 important elements to this file.
559 Elements should belong to the namespace
560 <literal>http://www.indexdata.com/pazpar2/1.0</literal>.
561 If the root node contains the
562 attribute 'mergekey', then every record that generates the same
563 merge key (normalized for case differences, white space, and
564 truncation) will be joined into a cluster. In other words, you
565 decide how records are merged. If you don't include a merge key,
566 records are never merged. The 'metadata' elements provide the meat
567 of the elements -- the content. the 'type' attribute is used to
568 match each element against processing rules that determine what
569 happens to the data element next.
573 The next processing step is the extraction of metadata from the
574 intermediate representation of the record. This is governed by the
575 'metadata' elements in the 'service' section of the configuration
576 file. See <xref linkend="config-server"/> for details. The metadata
577 in the retrieval record ultimately drives merging, sorting, ranking,
578 the extraction of browse facets, and display, all configurable.
582 <section id="client">
583 <title>Client development overview</title>
585 You can use Pazpar2 from any environment that allows you to use
586 webservices. The initial goal of the software was to support
587 Ajax-based applications, but there literally are no limits to what
588 you can do. You can use Pazpar2 from Javascript, Flash, Java, etc.,
589 on the browser side, and from any development environment on the
590 server side, and you can pass session tokens and record IDs freely
591 around between these environments to build sophisticated applications.
592 Use your imagination.
596 The webservice API of Pazpar2 is described in detail in <xref
597 linkend="pazpar2_protocol"/>.
601 In brief, you use the 'init' command to create a session, a
602 temporary workspace which carries information about the current
603 search. You start a new search using the 'search' command. Once the
604 search has been started, you can follow its progress using the
605 'stat', 'bytarget', 'termlist', or 'show' commands. Detailed records
606 can be fetched using the 'record' command.
612 <section id="nonstandard">
613 <title>Connecting to non-standard resources</title>
615 Pazpar2 uses Z39.50 as its switchboard language -- i.e. as far as it
616 is concerned, all resources speak Z39.50, or its webservices derivatives,
617 SRU/SRW. It is, however, equipped
618 to handle a broad range of different server behavior, through
619 configurable query mapping and record normalization. If you develop
620 configuration, stylesheets, etc., for a new type of resources, we
621 encourage you to share your work. But you can also use Pazpar2 to
622 connect to hundreds of resources that do not support standard
627 For a growing number of resources, Z39.50 is all you need. Over the
628 last few years, a number of commercial, full-text resources have
629 implemented Z39.50. These can be used through Pazpar2 with little or
630 no effort. Resources that use non-standard record formats will
631 require a bit of XSLT work, but that's all.
635 But what about resources that don't support Z39.50 at all? Some resources might
636 support OpenSearch, private, XML/HTTP-based protocols, or something
637 else entirely. Some databases exist only as web user interfaces and
638 will require screen-scraping. Still others exist only as static
639 files, or perhaps as databases supporting the OAI-PMH protocol.
640 There is hope! Read on.
644 Index Data continues to advocate the support of open standards. We
645 work with database vendors to support standards, so you don't have
646 to worry about programming against non-standard services. We also
647 provide tools (see <ulink
648 url="http://www.indexdata.com/simpleserver">SimpleServer</ulink>)
649 which make it comparatively easy to build gateways against servers
650 with non-standard behavior. Again, we encourage you to share any
651 work you do in this direction.
655 But the bottom line is that working with non-standard resources in
656 metasearching is really, really hard. If you want to build a
657 project with Pazpar2, and you need access to resources with
658 non-standard interfaces, we can help. We run gateways to more than
659 2,000 popular, commercial databases and other resources,
661 to plug them directly into Pazpar2. For a small annual fee per
662 database, we can help you establish connections to your licensed
663 resources. Meanwhile, you can help! If you build your own
664 standards-compliant gateways, host them for others, or share the
665 code! And tell your vendors that they can save everybody money and
666 increase the appeal of their resources by supporting standards.
670 There are those who will ask us why we are using Z39.50 as our
671 switchboard language rather than a different protocol. Basically,
672 we believe that Z39.50 is presently the most widely implemented
673 information retrieval protocol that has the level of functionality
674 required to support a good metasearching experience (structured
675 searching, structured, well-defined results). It is also compact and
676 efficient, and there is a very broad range of tools available to
681 <section id="unicode">
682 <title>Unicode Compliance</title>
684 Pazpar2 is Unicode compliant and language and locale aware but relies
685 on character encoding for the targets to be specified correctly if
686 the targets themselves are not UTF-8 based (most aren't).
687 Just a few bad behaving targets can spoil the search experience
688 considerably if for example Greek, Russian or otherwise non 7-bit ASCII
689 search terms are entered. In these cases some targets return
690 records irrelevant to the query, and the result screens will be
691 cluttered with noise.
694 While noise from misbehaving targets can not be removed, it can
695 be reduced using truly Unicode based ranking. This is an
696 option which is available to the system administrator if ICU
697 support is compiled into Pazpar2, see
698 <xref linkend="installation"/> for details.
701 In addition, the ICU tokenization and normalization rules must
702 be defined in the master configuration file described in
703 <xref linkend="config-server"/>.
707 <section id="load_balancing">
708 <title>Load balancing</title>
710 Just like any web server, Pazpar2, can be load balanced by a standard hardware or software load balancer as long as the session stickiness is ensured. If you are already running the Apache2 web server in front of Pazpar2 and use the apache mod_proxy module to 'relay' client requests to Pazpar2, this set up can be easily extended to include load balancing capabilites. To do so you need to enable the <ulink url="http://httpd.apache.org/docs/2.2/mod/mod_proxy_balancer.html">
712 </ulink> module in your Apache2 installation.
716 On a Debian based Apache 2 system, the relevant modules can
719 sudo a2enmod proxy_http
724 The mod_proxy_balancer can pass all 'sessionsticky' requests to the same backend worker as long as the requests are marked with the originating worker's ID (called 'route'). If the Pazpar2 serverID is configured (by setting an 'id' attribute on the 'server' element in the Pazpar2 configuration file) Pazpar2 will append it to the 'session' element returned during the 'init' in a mod_proxy_balancer compatible manner. Since the 'session' is then re-sent by the client (for all pazpar2 request besides 'init'), the balancer can use the marker to pass the request to the right route. To do so the balancer needs to be configured to inspect the 'session' parameter.
727 <example id="load_balancing.example">
728 <title>Apache 2 load balancing configuration</title>
730 Having 4 Pazpar2 instances running on the same host, port range of 8004-8007 and serverIDs of: pz1, pz2, pz3 and pz4 respectively we could use the following Apache 2 configuration to expose a single pazpar2 'endpoint' on a standard (<filename>/pazpar2/search.pz2</filename>) location:
734 AddDefaultCharset off
740 # 'route' has to match the configured pazpar2 server ID
741 <Proxy balancer://pz2cluster>
742 BalancerMember http://localhost:8004 route=pz1
743 BalancerMember http://localhost:8005 route=pz2
744 BalancerMember http://localhost:8006 route=pz3
745 BalancerMember http://localhost:8007 route=pz4
748 # route is resent in the 'session' param which has the form:
749 # 'sessid.serverid', understandable by the mod_proxy_load_balancer
750 # this is not going to work if the client tampers with the 'session' param
751 ProxyPass /pazpar2/search.pz2 balancer://pz2cluster lbmethod=byrequests stickysession=session nofailover=On]]></screen>
753 The 'ProxyPass' line sets up a reverse proxy for request ‘/pazpar2/search.pz2’ and delegates all requests to the load balancer (virtual worker) with name ‘pz2cluster’. Sticky sessions are enabled and implemented using the ‘session’ parameter. The ‘Proxy’ section lists all the servers (real workers) which the load balancer can use.
761 </chapter> <!-- Using Pazpar2 -->
763 <reference id="reference">
764 <title>Reference</title>
765 <partintro id="reference-introduction">
767 The material in this chapter is drawn directly from the individual
774 <appendix id="license"><title>License</title>
778 Copyright © ©right-year; Index Data.
782 Pazpar2 is free software; you can redistribute it and/or modify it under
783 the terms of the GNU General Public License as published by the Free
784 Software Foundation; either version 2, or (at your option) any later
789 Pazpar2 is distributed in the hope that it will be useful, but WITHOUT ANY
790 WARRANTY; without even the implied warranty of MERCHANTABILITY or
791 FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
796 You should have received a copy of the GNU General Public License
797 along with Pazpar2; see the file LICENSE. If not, write to the
798 Free Software Foundation,
799 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
808 <!-- Keep this comment at the end of the file
813 sgml-minimize-attributes:nil
814 sgml-always-quote-attributes:t
817 sgml-parent-document: nil
818 sgml-local-catalogs: nil
819 sgml-namecase-general:t