X-Git-Url: http://git.indexdata.com/?p=yaz-moved-to-github.git;a=blobdiff_plain;f=doc%2Fyaz-client-commands.xml;h=dbd3c2dd44f8366342d22e199ff6ac7c23984f3a;hp=0d08739af086440f7ae3071d506f657bc73cfe3c;hb=64dbcabe91775e26370b75ee899c435f36389989;hpb=21f7c16c6b1b694405dbc1760d3d6cb3caac38f6

diff --git a/doc/yaz-client-commands.xml b/doc/yaz-client-commands.xml
index 0d08739..dbd3c2d 100644
--- a/doc/yaz-client-commands.xml
+++ b/doc/yaz-client-commands.xml
@@ -1,5 +1,4 @@
 <!-- 
-   $Id: yaz-client-commands.xml,v 1.16 2006-06-13 16:01:51 adam Exp $
    Commands for YAZ client.
    Included in both manual and man page for yaz-client.
 -->
@@ -33,7 +32,7 @@
   <listitem>
    <para>Sends a Search Request using the <replaceable>query</replaceable>
     given. By default the query is assumed to be PQF. See command
-    <link linkend="command-querytype"><literal>querytype</literal></link>.
+    <link linkend="command-querytype">querytype</link> for more information.
    </para>
   </listitem>
  </varlistentry>
@@ -93,6 +92,15 @@
   </listitem>
  </varlistentry>
  <varlistentry><term>
+   <literal>setscan</literal> <replaceable>set</replaceable> <replaceable>term</replaceable>
+  </term>
+  <listitem>
+   <simpara>Scans database index for a term within a result set. This
+    is similar to the scan command but has a result set as its first argument.
+   </simpara>
+  </listitem>
+ </varlistentry>
+ <varlistentry><term>
    <literal>scanpos</literal> <replaceable>pos</replaceable>
   </term>
   <listitem>
@@ -175,11 +183,16 @@
  </varlistentry>
 
  <varlistentry><term>
-   <literal>sru</literal> <replaceable>method</replaceable>
+   <literal>sru</literal> <replaceable>method</replaceable> <replaceable>version</replaceable>
   </term>
   <listitem>
-   <para>Selects SRU method. Must be one of <literal>POST</literal>,
-    <literal>GET</literal>, <literal>SOAP</literal> (default).
+   <para>Selects Web Service method and version.
+    Must be one of <literal>POST</literal>,
+    <literal>GET</literal>, <literal>SOAP</literal> (default)
+    or <literal>SOLR</literal>. Version
+    should be either 1.1 or 1.2 for SRU. Other versions are allowed - for testing
+    purposes (version negotiation with SRU server). 
+    The version is currently not used for SOLR Web Services
    </para>
   </listitem>
  </varlistentry>
@@ -202,7 +215,7 @@
     See the
     <ulink
      url="http://www.loc.gov/z3950/agency/markup/04.html#3.2.2.1.6">
-     Z39.50 standard
+     Z39.50 standard on set bounds
     </ulink>
     for more details.
    </para>
@@ -218,7 +231,7 @@
     See the
     <ulink
      url="http://www.loc.gov/z3950/agency/markup/04.html#3.2.2.1.6">
-     Z39.50 standard
+     Z39.50 standard on set bounds
     </ulink> for more details.
    </para>
   </listitem>
@@ -234,7 +247,7 @@
     See the
     <ulink
      url="http://www.loc.gov/z3950/agency/markup/04.html#3.2.2.1.6">
-     Z39.50 standard
+     Z39.50 standard on set bounds
     </ulink>
     for more details.
    </para>
@@ -274,10 +287,10 @@
     are registered. See
     <ulink
      url="http://www.loc.gov/z3950/agency/defns/oids.html#5">
-     Z39.50 Standard
+     Z39.50 Record Syntax Identifiers
     </ulink>
     for more details. Commonly used records syntaxes include usmarc,
-    sutrs, grs1 and xml.
+    sutrs and xml.
    </para>
   </listitem>
  </varlistentry>
@@ -358,24 +371,25 @@
     <literal>update</literal>. The second argument, 
     <replaceable>recid</replaceable>, is the
     record identifier (any string). Third argument which is optional is
-    the record document for the request. If doc is a quoted string
-    (double quotes) the string content is used verbatim. If doc is not
-    a quoted string, it is assumed to be a filename which is read, then
-    sent as the docuemnt content. If doc is omitted, the last received
-    record (as parf of present response or piggybacked search response) 
-    is used for the update.
+    the record document for the request. If doc is preceded with 
+    "&lt;", then the following characters are treated as a filename
+    with the records to be updated. Otherwise doc is treated as
+    a document itself. The doc may also be quited in double quotes.
+    If doc is omitted, the last received record (as part of present
+    response or piggybacked search response) is used for the update.
    </para>
   </listitem>
  </varlistentry>
 
  <varlistentry><term>
-   <literal>.</literal>
+   <literal>source</literal>
    <replaceable>filename</replaceable>
   </term>
   <listitem>
    <para>Executes list of commands from
     file <replaceable>filename</replaceable>, just like source on
-    most UNIX shells.
+    most UNIX shells. A single dot (<literal>.</literal>) can be used
+    as an alternative.
    </para>
   </listitem>
  </varlistentry>
@@ -511,7 +525,7 @@
    </para>
    <note>
     <para>
-     Since character set negotation takes effect in the Z39.50
+     Since character set negotiation takes effect in the Z39.50
      Initialize Request you should issue this command before
      command <link linkend="command-open"><literal>open</literal></link>
      is used.
@@ -521,7 +535,7 @@
     <para>
      MARC records are not covered by Z39.50 character set negotiation,
      so that's why there is a separate character that must be known
-     in order to do meaningful converson(s).
+     in order to do meaningful conversion(s).
     </para>
    </note>
   </listitem>
@@ -569,6 +583,19 @@
  </varlistentry>
 
  <varlistentry><term>
+   <literal>querycharset</literal>
+   <replaceable>charset</replaceable>
+  </term>
+  <listitem>
+   <para>Specifies character set for query terms for Z39.50 RPN
+    queries and Z39.50 Scan Requests (termListAndStartPoint).
+    This is a pure client-side conversion which converts from
+    displayCharset to queryCharset.
+   </para>
+  </listitem>
+ </varlistentry>
+ 
+ <varlistentry><term>
    <literal>set_cclfile</literal>
    <replaceable>filename</replaceable>
   </term>