Rewrite introduction

[mkws-moved-to-github.git] / doc / library-configuration.txt

diff --git a/doc/library-configuration.txt b/doc/library-configuration.txt
index 5132887..311c3b0 100644 (file)
--- a/doc/library-configuration.txt
+++ b/doc/library-configuration.txt
@@ -2,15 +2,28 @@ MKWS Target Selection
 =====================
 
 
-MKWS accesses targets using the Pazpar2 metasearching engine, almost
-always fronted by the Service Proxy to manage target selection. This
-document assumes the SP is used, and so that a library of targets is
-available, maintained using an instance of MKAdmin (often
+MKWS accesses targets using the Pazpar2 metasearching engine. Although
+Pazpar2 can be used directly, using a statically configured set of
+targets, this usage is unusual. More often, Pazpar2 is fronted by the
+Service Proxy (SP), which manages authentication, sessions, target
+selection, etc.
+
+This document assumes the SP is used, and explains how to go about
+making a set of targets (a "library") available, how to connect your
+MKWS application to that library, and how to choose which of the
+available targets to use.
+
+
+1. Maintaining the library
+--------------------------
+
+### and so that a library of targets
+is available, maintained using an instance of MKAdmin (often
 http://mkc-admin.indexdata.com/console/)
 
 
-1. Selecting targets within the library
----------------------------------------
+2. Choosing targets from the library
+------------------------------------
 
 MKWS applications can choose what subset of the library's targets to
 use, by means of several alternative settings on individual widgets or
@@ -40,7 +53,7 @@ in the mkws_config structure:
        udb==NAME
 
 
-2. Authenticating onto the library
+3. Authenticating onto the library
 ----------------------------------
 
 Some MKWS applications will be content to use the default library with