X-Git-Url: http://jsfdemo.indexdata.com/?a=blobdiff_plain;f=doc%2Fbook.xml;h=d6ec4df6a02b82789edbe9c114f7a0534b138beb;hb=3d0cff4393b9af790eb77ad1fa75faebf9ec4013;hp=be55bed52bd78e23e4fe3212e0a3828010c252b1;hpb=a198c40f05431855a5cdfa1ba4736b15959d8590;p=pazpar2-moved-to-github.git diff --git a/doc/book.xml b/doc/book.xml index be55bed..d6ec4df 100644 --- a/doc/book.xml +++ b/doc/book.xml @@ -1,6 +1,6 @@ - %local; @@ -27,6 +27,9 @@ MikeTaylor + + DennisSchafroth + &version; ©right-year; @@ -76,8 +79,8 @@ -- XSLT is used to normalize and extract data from retrieval records for display and analysis. It can be used against any server which supports the - Z39.50 or SRU/SRW - protocol. Proprietary + Z39.50, SRU/SRW + or SOLR protocol. Proprietary backend modules can function as connectors between these standard protocols and any non-standard API, including web-site scraping, to support a large number of other protocols. @@ -159,7 +162,7 @@ proprietary framework for building connectors that enable Pazpar2 to access thousands of online databases, in addition to the vast number of catalogs - and online services that support the Z39.50/SRU/SRW protocols. + and online services that support the Z39.50/SRU/SRW/SOLR protocols. @@ -312,14 +315,15 @@
- Installation of test1 interface + Installation of test interfaces - In this section we outline how to install a simple interface that - is part of the Pazpar2 source package. Note that Debian users can - save time by just installing package pazpar2-test1. + In this section we show how to make available the set of simple + interfaces that are part of the Pazpar2 source package, and which + demonstrate some ways to use Pazpar2. (Note that Debian users can + save time by just installing the package pazpar2-test1.) - A web server must be installed and running on the system, such as Apache. + A web server, such as Apache, must be installed and running on the system. @@ -337,31 +341,51 @@ ..\bin\pazpar2 -f pazpar2.cfg This will start a Pazpar2 listener on port 9004. It will proxy - HTTP requests to localhost - port 80, which we assume will be the regular + HTTP requests to port 80 on localhost, which we assume will be the regular HTTP server on the system. Inspect and modify pazpar2.cfg as needed - if this is to be changed. The pazpar2.cfg includes settings from the + if this is to be changed. The pazpar2.cfg file includes settings from the file settings/edu.xml to use for searches. + - Make a new console and move to the other stuff. - For more information about pazpar2 options refer to the manpage. + The test UIs are located in www. Ensure that this + directory is available to the web server by copying + www to the document root, + using Apache's Alias directive, or + creating a symbolic link: for example, on a Debian or Ubuntu + system with Apache2 installed from the standard package, you might + make the link as follows: + + cd .../pazpar2 + sudo ln -s `pwd`/www /var/www/pazpar2-demo + - + - The test1 UI is located in www/test1. Ensure this - directory is available to the web server by either copying - test1 to the document root, create a symlink or - use Apache's Alias directive. + This makes the test applications visible at + + but they can not be run successfully from that URL, as they submit + search requests back to the server form which they were served, + and Apache2 doesn't know how to handle them. Instead, the test + applications must be accessed from Pazpar2 itself, acting as a + proxy to Apache2, at the URL + - The interface test1 interface should now be available on port 8004. + From here, the demo applications can be + accessed: test1, test2 and + jsdemo + are pure HTML+JavaScript setups, needing no server-side + intelligence; + demo + requires PHP on the server. - If you don't see the test1 interface. See if test1 is really available - on the same URL but on port 80. If it's not, the Apache configuration - (or other) is not correct. + If you don't see the test interfaces, check whether they are available + on port 80 (i.e. directly from the Apache2 server). If not, the + Apache configuration is incorrect. In order to use Apache as frontend for the interface on port 80 @@ -371,12 +395,15 @@
- Installation on Debian GNU/Linux + Installation on Debian or Ubuntu GNU/Linux - Index Data provides Debian packages for Pazpar2. These are prepared - for Debian versions Etch and Lenny (as of 2007). - These packages are available at - . + Index Data provides Debian and Ubuntu packages for Pazpar2. + As of February 2010, these + are prepared for Debian versions Etch, Lenny and Squeeze; and for + Ubuntu versions 8.04 (hardy), 8.10 (intrepid), 9.04 (jaunty) and + 9.10 (karmic). These packages are available at + and + .
@@ -620,8 +647,8 @@ Connecting to non-standard resources Pazpar2 uses Z39.50 as its switchboard language -- i.e. as far as it - is concerned, all resources speak Z39.50, or its webservices derivatives, - SRU/SRW. It is, however, equipped + is concerned, all resources speak Z39.50, its webservices derivatives, + SRU/SRW and SOLR servers exposing Lucene indexes. It is, however, equipped to handle a broad range of different server behavior, through configurable query mapping and record normalization. If you develop configuration, stylesheets, etc., for a new type of resources, we