<chapter id="administration">
- <!-- $Id: administration.xml,v 1.35 2006-06-12 11:48:24 marc Exp $ -->
+ <!-- $Id: administration.xml,v 1.39 2006-06-13 13:45:08 marc Exp $ -->
<title>Administrating Zebra</title>
<!-- ### It's a bit daft that this chapter (which describes half of
the configuration-file formats) is separated from
<screen>
staticrank: 1
</screen>
- directive in the main core Zebra config file, the internal document
- keys used for ordering are augmented by a preceeding integer, which
+ directive in the main core Zebra configuration file, the internal document
+ keys used for ordering are augmented by a preceding integer, which
contains the static rank of a given document, and the index lists
are ordered
first by ascending static rank,
<para>
The experimental <literal>alvis</literal> filter provides a
directive to fetch static rank information out of the indexed XML
- records, thus making <emphasis>all</emphasis> hit sets orderd
+ records, thus making <emphasis>all</emphasis> hit sets ordered
after <emphasis>ascending</emphasis> static
rank, and for those doc's which have the same static rank, ordered
after <emphasis>ascending</emphasis> doc <literal>ID</literal>.
ranking or score functions. These functions return positive
integer scores, where <emphasis>highest</emphasis> score is
``best'';
- hit sets are sorted according to <emphasis>decending</emphasis>
+ hit sets are sorted according to <emphasis>descending</emphasis>
scores (in contrary
to the index lists which are sorted according to
ascending rank number and document ID).
</para>
<para>
Dynamic ranking is enabled by a directive like one of the
- following in the zebra config file (use only one of these a time!):
+ following in the zebra configuration file (use only one of these a time!):
<screen>
rank: rank-1 # default TDF-IDF like
rank: rank-static # dummy do-nothing
the Bib-1 relation attribute with
value ``relevance'' to the PQF query (that is,
<literal>@attr 2=102</literal>, see also
- <ulink url="ftp://ftp.loc.gov/pub/z3950/defs/bib1.txt">
- The BIB-1 Attribute Set Semantics</ulink>).
+ <ulink url="&url.z39.50;bib1.html">
+ The BIB-1 Attribute Set Semantics</ulink>, also in
+ <ulink url="&url.z39.50.attset.bib1;">HTML</ulink>).
To find all articles with the word <literal>Eoraptor</literal> in
the title, and present them relevance ranked, issue the PQF query:
<screen>
algorithms, which only considers searching in one full-text
index, this one works on multiple indexes at the same time.
More precisely,
- Zebra does boolean queries and searches in specific adressed
+ Zebra does boolean queries and searches in specific addressed
indexes (there are inverted indexes pointing from terms in the
- dictionaly to documents and term positions inside documents).
+ dictionary to documents and term positions inside documents).
It works like this:
<variablelist>
<varlistentry>
</screen>
searches for all documents which have the term 'Utah' on the
body of text, and which have the term 'Springer' in the publisher
- field, and sort them in the order of the relvance ranking made on
+ field, and sort them in the order of the relevance ranking made on
the body-of-text index only.
</para>
</listitem>
<term>Hit list merging</term>
<listitem>
<para>
- Fourth, the atomic hist lists are merged according to the boolean
+ Fourth, the atomic hit lists are merged according to the boolean
conditions to a final hit list of documents to be returned.
</para>
<para>
<para>
<literal>Dynamic ranking</literal> is not compatible
with <literal>estimated hit sizes</literal>, as all documents in
- a hit set must be acessed to compute the correct placing in a
+ a hit set must be accessed to compute the correct placing in a
ranking sorted list. Therefore the use attribute setting
<literal>@attr 2=102</literal> clashes with
<literal>@attr 9=integer</literal>.
xelm /*/@created Date/time-added-to-db:s
</screen>
to any <literal>.abs</literal> record-indexing configuration file.
- Similarily, one could add an indexing element of the form
+ Similarly, one could add an indexing element of the form
<screen><![CDATA[
<z:index name="date-modified" type="s">
<xsl:value-of select="some/xpath"/>
</sect1>
- <sect1 id="administration-cql-to-pqf">
- <title>Server Side CQL to PQF Query Translation</title>
- <para>
- Using the
- <literal><cql2rpn>l2rpn.txt</cql2rpn></literal>
- YAZ Frontend Virtual
- Hosts option, one can configure
- the YAZ Frontend CQL-to-PQF
- converter, specifying the interpretation of various
- <ulink url="http://www.loc.gov/standards/sru/cql/">CQL</ulink>
- indexes, relations, etc. in terms of Type-1 query attributes.
- <!-- The yaz-client config file -->
- </para>
- <para>
- For example, using server-side CQL-to-PQF conversion, one might
- query a zebra server like this:
- <screen>
- <![CDATA[
- yaz-client localhost:9999
- Z> querytype cql
- Z> find text=(plant and soil)
- ]]>
- </screen>
- and - if properly configured - even static relevance ranking can
- be performed using CQL query syntax:
- <screen>
- <![CDATA[
- Z> find text = /relevant (plant and soil)
- ]]>
- </screen>
- </para>
-
- <para>
- By the way, the same configuration can be used to
- search using client-side CQL-to-PQF conversion:
- (the only difference is <literal>querytype cql2rpn</literal>
- instead of
- <literal>querytype cql</literal>, and the call specifying a local
- conversion file)
- <screen>
- <![CDATA[
- yaz-client -q local/cql2pqf.txt localhost:9999
- Z> querytype cql2rpn
- Z> find text=(plant and soil)
- ]]>
- </screen>
- </para>
-
- <para>
- Exhaustive information can be found in the
- Section "Specification of CQL to RPN mappings" in the YAZ manual.
- <ulink url="http://www.indexdata.dk/yaz/doc/tools.tkl#tools.cql.map">
- http://www.indexdata.dk/yaz/doc/tools.tkl#tools.cql.map</ulink>,
- and shall therefore not be repeated here.
- </para>
- <!--
- <para>
- See
- <ulink url="http://www.loc.gov/z3950/agency/zing/cql/dc-indexes.html">
- http://www.loc.gov/z3950/agency/zing/cql/dc-indexes.html</ulink>
- for the Maintenance Agency's work-in-progress mapping of Dublin Core
- indexes to Attribute Architecture (util, XD and BIB-2)
- attributes.
- </para>
- -->
- </sect1>
-
-
</chapter>
projects / idzebra-moved-to-github.git / blobdiff