1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763
|
<!--
Commands for YAZ client.
Included in both manual and man page for yaz-client.
-->
<variablelist>
<varlistentry id="command-open"><term>
<literal>open </literal><replaceable>zurl</replaceable>
</term>
<listitem>
<para>Opens a connection to a server. The syntax for
<replaceable>zurl</replaceable> is the same as described
above for connecting from the command line.
</para>
<para>
Syntax:
</para>
<para>
[<literal>(tcp|ssl|unix|http)':'</literal>]<replaceable>host</replaceable>
[:<replaceable>port</replaceable>][/<replaceable>base</replaceable>]
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>quit</literal>
</term>
<listitem>
<para>Quits YAZ client</para>
</listitem>
</varlistentry>
<varlistentry id="command-find"><term>
<literal>find </literal><replaceable>query</replaceable></term>
<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">querytype</link> for more information.
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>delete</literal> <replaceable>setname</replaceable></term>
<listitem>
<para>Deletes result set with name <replaceable>setname</replaceable>
on the server.</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>base </literal><replaceable>base1</replaceable>
<replaceable>base2</replaceable> ...
</term>
<listitem>
<para>Sets the name(s) of the database(s) to search. One or more
databases may be specified separated by blanks. This commands overrides
the database given in <replaceable>zurl</replaceable>.
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>show </literal>
[<replaceable>start</replaceable>[+<replaceable>number</replaceable>]]
</term>
<listitem>
<para>Fetches records by sending a Present Request from the start
position given by
<replaceable>start</replaceable>
a number of records given by <replaceable>number</replaceable>. If
<replaceable>start</replaceable> is not given, then the client
will fetch from position of the last retrieved record plus 1. If
<replaceable>number</replaceable> is not given, then one record will
be fetched at a time.
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>scan</literal> <replaceable>term</replaceable>
</term>
<listitem>
<simpara>Scans
database index for a term. The syntax resembles the syntax
for <link linkend="command-find"><literal>find</literal></link>.
If you want to scan for the word <literal>water</literal> you could
write
</simpara>
<screen>
scan water
</screen>
<simpara>
but if you want to scan only in, say the title field, you would write
</simpara>
<screen>
scan @attr 1=4 water
</screen>
</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>
<simpara>
Sets preferred position for scan. This value
is used in next scan. By default position is 1.
</simpara>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>scansize</literal> <replaceable>size</replaceable>
</term>
<listitem>
<simpara>
Sets number of entries to be returned by scan. Default
number of entries is 20.
</simpara>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>scanstep</literal> <replaceable>step</replaceable>
</term>
<listitem>
<simpara>
Set step-size for scan. This value is used in next scan
sent to the target. By default step-size is 0.
</simpara>
</listitem>
</varlistentry>
<varlistentry id="sortspec"><term>
<literal>sort</literal> <replaceable>sortspecs</replaceable>
</term>
<listitem>
<para>Sorts a result set. The sort command takes a
sequence of space-separated sort specifications, with each sort
specification consisting of two space-separated words (so that the
whole specification list is made up of an even number of words).
The first word of each specification
holds a field (sort criterion) and the second holds flags.
If the sort criterion includes <literal>=</literal> it is assumed
that the <literal>SortKey</literal> is of type
<literal>sortAttributes</literal> using Bib-1: in this case
the integer before <literal>=</literal> is
the attribute type and the integer following <literal>=</literal>
is the attribute value.
If no <literal>=</literal> is in the criterion it is treated as a
sortfield of type InternationalString.
The flags word of each sort specification must consist of
<literal>s</literal>
for case sensitive or <literal>i</literal> for case insensitive, and
<literal><</literal> for ascending order or <literal>></literal>
for descending order.
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>sort+</literal>
</term>
<listitem>
<para>Same as <literal>sort</literal> but stores the sorted
result set in a new result set.
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>authentication</literal> <replaceable>openauth</replaceable>
</term>
<listitem>
<para>Sets up a authentication string if a server requires
authentication (v2 OpenStyle). The authentication string is first
sent to the server when the
<link linkend="command-open"><literal>open</literal></link> command is
issued and the Z39.50 Initialize Request is sent, so this command
must be used before <literal>open</literal> in order to be effective.
A common convention for the <replaceable>authopen</replaceable> string
is that the username - and password is separated by a slash, e.g.
<literal>myusername/mysecret</literal>.
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>sru</literal> <replaceable>method</replaceable> <replaceable>version</replaceable>
</term>
<listitem>
<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>
<varlistentry><term>
<literal>list_all</literal>
</term>
<listitem>
<para>This command displays status and values for many settings.
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>lslb</literal> <replaceable>n</replaceable>
</term>
<listitem>
<para>Sets the limit for when no records should be returned
together with the search result.
See the
<ulink
url="http://www.loc.gov/z3950/agency/markup/04.html#3.2.2.1.6">
Z39.50 standard on set bounds
</ulink>
for more details.
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>ssub</literal> <replaceable>n</replaceable>
</term>
<listitem>
<para>Sets the limit for when all records should be returned with
the search result.
See the
<ulink
url="http://www.loc.gov/z3950/agency/markup/04.html#3.2.2.1.6">
Z39.50 standard on set bounds
</ulink> for more details.
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>mspn</literal> <replaceable>n</replaceable>
</term>
<listitem>
<para>Sets the number of records should be returned if the
number of records in the result set is between the values of
<literal>lslb</literal> and <literal>ssub</literal>.
See the
<ulink
url="http://www.loc.gov/z3950/agency/markup/04.html#3.2.2.1.6">
Z39.50 standard on set bounds
</ulink>
for more details.
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>status</literal>
</term>
<listitem>
<para>Displays the values of <literal>lslb</literal>,
<literal>ssub</literal> and <literal>mspn</literal>.
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>setname</literal>
</term>
<listitem>
<para>Switches named result sets on and off. Default is on.
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>cancel</literal>
</term>
<listitem>
<para>Sends a Trigger Resource Control Request to the target.
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>format</literal> <replaceable>oid</replaceable>
</term>
<listitem>
<para>Sets the preferred transfer syntax for retrieved records.
yaz-client supports all the record syntaxes that currently
are registered. See
<ulink
url="http://www.loc.gov/z3950/agency/defns/oids.html#5">
Z39.50 Record Syntax Identifiers
</ulink>
for more details. Commonly used records syntaxes include usmarc,
sutrs and xml.
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>elements</literal> <replaceable>e</replaceable>
</term>
<listitem>
<para>Sets the element set name for the records. Many targets support
element sets are B (for brief) and F (for full).
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>close</literal>
</term>
<listitem>
<para>Sends a Z39.50 Close APDU and closes connection with the peer
</para>
</listitem>
</varlistentry>
<varlistentry id="command-querytype"><term>
<literal>querytype</literal> <replaceable>type</replaceable>
</term>
<listitem>
<para>Sets the query type as used by command
<link linkend="command-find"><literal>find</literal></link>.
The following is supported:
<literal>prefix</literal> for
<link linkend="PQF">Prefix Query Notation</link> (Type-1 Query);
<literal>ccl</literal> for CCL search (Type-2 Query),
<literal>cql</literal> for CQL (Type-104 search with CQL OID),
<literal>ccl2rpn</literal> for
<link linkend="CCL">CCL</link> to RPN conversion (Type-1 Query).
<literal>cql2rpn</literal> for
CQL to RPN conversion (Type-1 Query).
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>attributeset</literal> <replaceable>set</replaceable>
</term>
<listitem>
<para>
Sets attribute set OID for prefix queries (RPN, Type-1).
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>refid</literal> <replaceable>id</replaceable>
</term>
<listitem>
<para>Sets reference ID for Z39.50 Request(s).
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>itemorder</literal>
<replaceable>type</replaceable> <replaceable>no</replaceable>
</term>
<listitem>
<para>Sends an Item Order Request using the ILL External.
<replaceable>type</replaceable> is either 1 or 2 which corresponds to
ILL-Profile 1 and 2 respectively. The <replaceable>no</replaceable>
is the Result Set position of the record to be ordered.
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>update</literal>
<replaceable>action</replaceable>
<replaceable>recid</replaceable>
<replaceable>doc</replaceable>
</term>
<listitem>
<para>Sends Item Update Request. The <replaceable>action</replaceable>
argument must be the action type: one of <literal>insert</literal>,
<literal>replace</literal>, <literal>delete</literal> and
<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 preceded with
"<", 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>source</literal>
<replaceable>filename</replaceable>
</term>
<listitem>
<para>Executes list of commands from
file <replaceable>filename</replaceable>, just like source on
most UNIX shells. A single dot (<literal>.</literal>) can be used
as an alternative.
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>!</literal>
<replaceable>args</replaceable>
</term>
<listitem>
<para>Executes command <replaceable>args</replaceable> in subshell
using the <literal>system</literal> call.
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>push_command</literal>
<replaceable>command</replaceable>
</term>
<listitem>
<para>The push_command takes another command as its argument.
That command is then added to the history information (so
you can retrieve it later). The command itself is not
executed. This command only works if you have GNU readline/history
enabled.
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>set_apdufile</literal>
<replaceable>filename</replaceable>
</term>
<listitem>
<para>Sets that APDU should be logged to file
<replaceable>filename</replaceable>. Another way to achieve
APDU log is by using command-line option <literal>-a</literal>.
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>set_auto_reconnect</literal>
<replaceable>flag</replaceable>
</term>
<listitem>
<para>Specifies whether YAZ client automatically reconnect if
target closes connection (Z39.50 only).
</para>
<para>
<replaceable>flag</replaceable> must be either
<literal>on</literal> or <literal>off</literal>.
</para>
</listitem>
</varlistentry>
<varlistentry id="command-set-auto-wait"><term>
<literal>set_auto_wait</literal>
<replaceable>flag</replaceable>
</term>
<listitem>
<para>Specifies whether YAZ client should wait for
response protocol packages after a request.
By default YAZ client waits (on) for response packages immediately
after a command (find, show) has been issued. If <literal>off</literal>
is used, YAZ client does not attempt to receive packages automatically.
These will have to be manually received when command
<link linkend="command-wait-response">
<literal>wait_response</literal>
</link> is used.
</para>
<para>
<replaceable>flag</replaceable> must be either
<literal>on</literal> or <literal>off</literal>.
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>set_marcdump</literal>
<replaceable>filename</replaceable>
</term>
<listitem>
<para>Specifies that all retrieved records should be appended to
file <replaceable>filename</replaceable>. This command does the
thing as option <literal>-m</literal>.
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>schema</literal>
<replaceable>schemaid</replaceable>
</term>
<listitem>
<para>Specifies schema for retrieval.
Schema may be specified as an OID for Z39.50.
For SRU, schema is a simple string URI.
</para>
</listitem>
</varlistentry>
<varlistentry id="command-charset"><term>
<literal>charset</literal>
<replaceable>negotiationcharset</replaceable>
[<replaceable>displaycharset</replaceable>]
[[<replaceable>marccharset</replaceable>]]
</term>
<listitem>
<para>Specifies character set (encoding) for Z39.50
negotiation / SRU encoding and/or character set for output (terminal).
</para>
<para>
<replaceable>negotiationcharset</replaceable> is the name
of the character set to be negotiated by the server. The special name
<literal>-</literal> for <replaceable>negotiationcharset</replaceable>
specifies <emphasis>no</emphasis> character set to be negotiated.
</para>
<para>
If <replaceable>displaycharset</replaceable> is given, it specifies name
of the character set of the output (on the terminal on which
YAZ client is running). To disable conversion of characters
to the output encoding, the special name <literal>-</literal> (dash)
can be used.
If the special name <literal>auto</literal> is given, YAZ client will
convert strings to the encoding of the
terminal as returned by <function>nl_langinfo</function> call.
</para>
<para>
If <replaceable>marcharset</replaceable> is given, it specifies name
of the character set of retrieved MARC records from server. See
also <literal>marcharset</literal> command.
</para>
<note>
<para>
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.
</para>
</note>
<note>
<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 conversion(s).
</para>
</note>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>negcharset</literal>
<replaceable>charset</replaceable>
</term>
<listitem>
<para>Specifies character set for negotiation (Z39.50). The
argument is the same as second argument for command
<link linkend="command-charset"><literal>charset</literal></link>.
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>displaycharset</literal>
<replaceable>charset</replaceable>
</term>
<listitem>
<para>Specifies character set for output (display). The
argument is the same as second argument for command
<link linkend="command-charset"><literal>charset</literal></link>.
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>marccharset</literal>
<replaceable>charset</replaceable>
</term>
<listitem>
<para>Specifies character set for retrieved MARC records so
that YAZ client can display them in a character suitable
for your display. See <literal>charset</literal> command.
If <literal>auto</literal> is given, YAZ will assume
that MARC21/USMARC is using MARC8/UTF8 and ISO-8859-1
for all other MARC variants. The charset argument is the
same as third argument for command
<link linkend="command-charset"><literal>charset</literal></link>.
</para>
</listitem>
</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>
<listitem>
<para>Specifies that CCL fields should be read from file
file <replaceable>filename</replaceable>. This command does the
thing as option <literal>-c</literal>.
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>set_cqlfile</literal>
<replaceable>filename</replaceable>
</term>
<listitem>
<para>Specifies that CQL fields should be read from file
file <replaceable>filename</replaceable>. This command does the
thing as option <literal>-q</literal>.
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>register_oid</literal>
<replaceable>name</replaceable>
<replaceable>class</replaceable>
<replaceable>OID</replaceable>
</term>
<listitem>
<para>This command allows you to register your own object
identifier - so that instead of entering a long dot-notation
you can use a short name instead.
The <replaceable>name</replaceable> is your
name for the OID, <replaceable>class</replaceable> is the
class, and <replaceable>OID</replaceable> is the raw OID in
dot notation. Class is one <literal>appctx</literal>,
<literal>absyn</literal>, <literal>attet</literal>,
<literal>transyn</literal>, <literal>diagset</literal>,
<literal>recsyn</literal>, <literal>resform</literal>,
<literal>accform</literal>, <literal>extserv</literal>,
<literal>userinfo</literal>, <literal>elemspec</literal>,
<literal>varset</literal>, <literal>schema</literal>,
<literal>tagset</literal>, <literal>general</literal>.
If you're in doubt use the <literal>general</literal>
class.
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>register_tab</literal>
<replaceable>command</replaceable>
<replaceable>string</replaceable>
</term>
<listitem>
<para>This command registers a TAB completion string for
the command given.
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>sleep</literal>
<replaceable>seconds</replaceable>
</term>
<listitem>
<para>This command makes YAZ client sleep (be idle) for
the number of seconds given.
</para>
</listitem>
</varlistentry>
<varlistentry id="command-wait-response"><term>
<literal>wait_response</literal>
[ <replaceable>number</replaceable>]
</term>
<listitem>
<para>This command makes YAZ client wait for a number of
response packages from target. If <replaceable>number</replaceable> is
omitted, 1 is assumed.
</para>
<para>This command is rarely used and is only useful if command
<link linkend="command-set-auto-wait">
<literal>set_auto_wait</literal>
</link> is set to off.
</para>
</listitem>
</varlistentry>
<varlistentry id="command-xmles"><term>
<literal>xmles</literal>
<replaceable>OID</replaceable>
<replaceable>doc</replaceable>
</term>
<listitem>
<para>Sends XML Extended Services request using the OID and doc given.
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>zversion</literal>
<replaceable>ver</replaceable>
</term>
<listitem>
<para>This command sets Z39.50 version for negotiation.
Should be used before
<link linkend="command-open"><literal>open</literal></link>.
By default 3 (version 3) is used.
</para>
</listitem>
</varlistentry>
<varlistentry><term>
<literal>options</literal>
<replaceable>op1 op2..</replaceable>
</term>
<listitem>
<para>This command sets Z39.50 options for negotiation.
Should be used before
<link linkend="command-open"><literal>open</literal></link>.
</para>
<para>
The following options are supported:
<literal>search</literal>,
<literal>present</literal>,
<literal>delSet</literal>,
<literal>resourceReport</literal>,
<literal>triggerResourceCtrl</literal>,
<literal>resourceCtrl</literal>,
<literal>accessCtrl</literal>,
<literal>scan</literal>,
<literal>sort</literal>,
<literal>extendedServices</literal>,
<literal>level_1Segmentation</literal>,
<literal>level_2Segmentation</literal>,
<literal>concurrentOperations</literal>,
<literal>namedResultSets</literal>,
<literal>encapsulation</literal>,
<literal>resultCount</literal>,
<literal>negotiationModel</literal>,
<literal>duplicationDetection</literal>,
<literal>queryType104</literal>,
<literal>pQESCorrection</literal>,
<literal>stringSchema</literal>.
</para>
</listitem>
</varlistentry>
</variablelist>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:1
sgml-indent-data:t
sgml-parent-document: "yaz.xml"
sgml-local-catalogs: nil
sgml-namecase-general:t
End:
-->
|