Table of Contents
Unlike many simpler retrieval systems, Zebra supports safe, incremental updates to an existing index.
Normally, when Zebra modifies the index it reads a number of records that you specify. Depending on your specifications and on the contents of each record one the following events take place for each record:
The record is indexed as if it never occurred before. Either the Zebra system doesn't know how to identify the record or Zebra can identify the record but didn't find it to be already indexed.
The record has already been indexed. In this case either the contents of the record or the location (file) of the record indicates that it has been indexed before.
The record is deleted from the index. As in the update-case it must be able to identify the record.
Please note that in both the modify- and delete- case the Zebra indexer must be able to generate a unique key that identifies the record in question (more on this below).
To administrate the Zebra retrieval system, you run the
This program supports a number of options which are preceded by a dash,
and a few commands (not preceded by dash).
Both the Zebra administrative tool and the Z39.50 server share a
set of index files and a global configuration file.
The name of the configuration file defaults to
The configuration file includes specifications on how to index
various kinds of records and where the other configuration files
must be run in the directory where the
configuration file lives unless you indicate the location of the
configuration file by option
Indexing is a per-record process, in which either insert/modify/delete
will occur. Before a record is indexed search keys are extracted from
whatever might be the layout the original record (sgml,html,text, etc..).
The Zebra system currently supports two fundamental types of records:
structured and simple text.
To specify a particular extraction process, use either the
command line option
-t or specify a
recordType setting in the configuration file.