<chapter id="administration">
- <!-- $Id: administration.xml,v 1.6 2002-08-28 08:14:47 mike Exp $ -->
+ <!-- $Id: administration.xml,v 1.7 2002-10-10 14:27:18 heikki Exp $ -->
<title>Administrating Zebra</title>
<para>
in order to modify the indexes correctly at a later time.
</para>
- <para>
- FIXME - There must be a simpler way to do this with Adams string tags -H
- </para>
+ <!--FIXME - There must be a simpler way to do this with Adams string tags -H
+ -->
<para>
For example, to update records of group <literal>esdd</literal>
In order to make changes to the system take effect for the
users, you'll have to submit a "commit" command after a
(sequence of) update operation(s).
- You can ask the indexer to commit the changes immediately
- after the update operation:
</para>
<para>
<screen>
- $ zebraidx update /d1/records update /d2/more-records commit
+ $ zebraidx update /d1/records
+ $ zebraidx commit
</screen>
</para>
<para>
<screen>
- $ zebraidx -g books update /d1/records update /d2/more-records
+ $ zebraidx -g books update /d1/records /d2/more-records
$ zebraidx -g fun update /d3/fun-records
$ zebraidx commit
</screen>
<chapter id="examples">
- <!-- $Id: examples.xml,v 1.7 2002-10-08 08:09:43 mike Exp $ -->
+ <!-- $Id: examples.xml,v 1.8 2002-10-10 14:27:18 heikki Exp $ -->
<title>Example Configurations</title>
<sect1>
$ zebraidx update records
00:45:46-08/10: ../../index/zebraidx(5016) [warn] records/genera.xml:0 Couldn't open GENUS.abs [No such file or directory]
</screen>
+ <!-- FIXME ### This needs more text -->
</para>
</sect1>
</chapter>
The master configuration file, <literal>zebra.cfg</literal>,
which is as short and simple as it can be:
<screen>
- # $Header: /home/cvsroot/idis/doc/examples.xml,v 1.7 2002-10-08 08:09:43 mike Exp $
+ # $Header: /home/cvsroot/idis/doc/examples.xml,v 1.8 2002-10-10 14:27:18 heikki Exp $
# Bare-bones master configuration file for Zebra
profilePath: .:../../tab:../../../yaz/tab
</screen>
The BIB-1 attribute set configuration file,
<literal>bib1.att</literal>, which is also as short as possible:
<screen>
- # $Header: /home/cvsroot/idis/doc/examples.xml,v 1.7 2002-10-08 08:09:43 mike Exp $
+ # $Header: /home/cvsroot/idis/doc/examples.xml,v 1.8 2002-10-10 14:27:18 heikki Exp $
# Bare-bones BIB-1 attribute set file for Zebra
reference Bib-1
</screen>
<chapter id="introduction">
- <!-- $Id: introduction.xml,v 1.14 2002-10-08 08:09:43 mike Exp $ -->
+ <!-- $Id: introduction.xml,v 1.15 2002-10-10 14:27:18 heikki Exp $ -->
<title>Introduction</title>
<sect1>
Zebra is written in portable C, so it runs on most Unix-like systems
as well as Windows NT. A binary distribution for Windows NT is
available at
- <ulink url="http://indexdata.dk/zebra/###"/>
+ <ulink url="http://ftp.indexdata.dk/pub/zebra/win32/">
</para>
</listitem>
announcements from the authors (new
releases, bug fixes, etc.) and general discussion. You are welcome
to seek support there. Join by sending email to
- <email>zebra-subscribe-###@mailman.indexdata.dk</email>
+ <email>zebra-request@indexdata.dk</email>. Put the word 'subscribe'
+ in the body of the message.
+ <!-- zebra-subscribe-###@mailman.indexdata.dk-->
</para>
<para>
Third, it's possible to buy a commercial support contract, with
well defined service levels and response times, from Index Data.
See
- <ulink url="http://www.indexdata.dk/support/###"/>
+ <ulink url="http://www.indexdata.dk/support/?lang=en"/>
+ <!-- ulink url="http://www.indexdata.dk/support/###"/-->
for details.
</para>
</sect1>
<para>
If you think it's all really neat, you're welcome to drop us a line
saying that, too. You can email us on
- <email>indo@indexdata.dk</email>
+ <email>info@indexdata.dk</email>
or check the contact info at the end of this manual.
</para>
<chapter id="record-model">
- <!-- $Id: recordmodel.xml,v 1.5 2002-08-28 09:39:45 mike Exp $ -->
+ <!-- $Id: recordmodel.xml,v 1.6 2002-10-10 14:27:18 heikki Exp $ -->
<title>The Record Model</title>
<para>
</para>
- <note>
- <para>
+ <!-- There is no indentation in the example above! -H
+ -note-
+ -para-
The indentation used above is used to illustrate how Zebra
interprets the mark-up. The indentation, in itself, has no
significance to the parser for the canonical input format, which
discards superfluous whitespace.
- </para>
- </note>
+ -/para-
+ -/note-
+ -->
+
<para>
The keywords surrounded by <...> are
<emphasis>tags</emphasis>, while the sections of text
ROOT
AUTHOR "Robert Pirsig"
</screen>
+ <!-- FIXME That screen makes no sense! -H -->
</para>
AUTHOR
SURNAME "Pirsig"
</screen>
+ <!-- FIXME That screen makes even less sense! -H -->
</para>