X-Git-Url: http://jsfdemo.indexdata.com/?a=blobdiff_plain;f=doc%2Fbook.xml;h=e3217281c81ca1510adc1ea8a518fb6c93049788;hb=cce5da278d7ce802452bbc14b4c2d577f638291b;hp=aae3a77151d00da5df26f76018758bd1409b662e;hpb=ac0bcf66d85044be0461cf2748ecd5fc1b90186f;p=pazpar2-moved-to-github.git
diff --git a/doc/book.xml b/doc/book.xml
index aae3a77..e321728 100644
--- a/doc/book.xml
+++ b/doc/book.xml
@@ -67,7 +67,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 protocol. Proprietary
+ Z39.50 and SRU/SRW
+ protocol. Proprietary
backend modules can be used to support a large number of other protocols
(please contact Index Data for further information about this).
@@ -87,7 +88,7 @@
scenes. Pazpar2 connects to servers, carries out searches, and
retrieves, deduplicates, and stores results internally. Your application
code may periodically inquire about the status of an ongoing operation,
- and ask to see records or other result set facets. Result become
+ and ask to see records or other result set facets. Result becomes
available immediately, and it is easy to build end-user interfaces which
feel extremely responsive, even when searching more than 100 servers
concurrently.
@@ -118,8 +119,8 @@
If you wish to connect to commercial or other databases which do not
support open standards, please contact Index Data. We have a licensing
agreement with a third party vendor which will enable Pazpar2 to access
- thousands of online databases, in addition the vast number of catalogs
- and online services that support the Z39.50 protocol.
+ thousands of online databases, in addition to the vast number of catalogs
+ and online services that support the Z39.50/SRU/SRW protocols.
Pazpar2 is our attempt to re-think the traditional paradigms for
@@ -148,7 +149,7 @@
Installation
- The Pazpar2 package very small. It includes documentation as well
+ The Pazpar2 package is very small. It includes documentation as well
as the Pazpar2 server. The package also includes a simple user
interface test1 which consists of a single HTML page and a single
JavaScript file to illustrate the use of Pazpar2.
@@ -465,8 +466,8 @@
Sometimes, it may be necessary to implement functionality on your
regular webserver that makes use of search results, for example to
implement data import functionality, emailing results, history
- lists, personal citation lists, interlibrary loan functionality
- ,etc. Fortunately, it is simple to exchange information between
+ lists, personal citation lists, interlibrary loan functionality,
+ etc. Fortunately, it is simple to exchange information between
Pazpar2, your browser scripting, and backend server-side scripting.
You can send a session ID and possibly a record ID from your browser
code to your server code, and from there use Pazpar2s webservice API
@@ -481,7 +482,7 @@
Your data model
Pazpar2 does not have a preconceived model of what makes up a data
- model. There are no assumption that records have specific fields or
+ model. There are no assumptions that records have specific fields or
that they are organized in any particular way. The only assumption
is that data comes packaged in a form that the software can work
with (presently, that means XML or MARC), and that you can provide
@@ -579,7 +580,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. It is, however, equipped
+ is concerned, all resources speak Z39.50, or its webservices derivatives,
+ SRU/SRW. 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
@@ -597,8 +599,7 @@
- But what about resources that don't support Z39.50 at all? The NISO
- SRU (MXG) protocol is slowly gathering steam. Other resources might
+ But what about resources that don't support Z39.50 at all? Some resources might
support OpenSearch, private, XML/HTTP-based protocols, or something
else entirely. Some databases exist only as web user interfaces and
will require screen-scraping. Still others exist only as static