<chapter id="quick-start">
- <!-- $Id: quickstart.xml,v 1.8 2002-12-01 23:26:26 mike Exp $ -->
+ <!-- $Id: quickstart.xml,v 1.14 2007-05-24 13:44:09 adam Exp $ -->
<title>Quick Start </title>
<para>
<!-- ### ulink to GILS profile: what's the URL? -->
In this section, we will test the system by indexing a small set of
- sample GILS records that are included with the Zebra distribution,
- running Zebra a server against the newly created database, and
+ sample GILS records that are included with the &zebra; distribution,
+ running a &zebra; server against the newly created database, and
searching the indexes with a client that connects to that server.
</para>
<para>
</para>
<para>
- The Zebra index that you have just created has a single database
+ The &zebra; index that you have just created has a single database
named <literal>Default</literal>.
The database contains records structured according to
the GILS profile, and the server will
- return records in USMARC, GRS-1, or SUTRS format depending
+ return records in &acro.usmarc;, &acro.grs1;, or &acro.sutrs; format depending
on what the client asks for.
</para>
<para>
- To test the server, you can use any Z39.50 client.
+ To test the server, you can use any &acro.z3950; client.
For instance, you can use the demo command-line client that comes
- with YAZ:
+ with &yaz;:
</para>
<para>
<screen>
</para>
<para>
- The default retrieval syntax for the client is USMARC, and the
+ The default retrieval syntax for the client is &acro.usmarc;, and the
default element set is <literal>F</literal> (``full record''). To
try other formats and element sets for the same record, try:
</para>
<note>
<para>You may notice that more fields are returned when your
- client requests SUTRS, GRS-1 or XML records.
+ client requests &acro.sutrs;, &acro.grs1; or &acro.xml; records.
This is normal - not all of the GILS data elements have mappings in
- the USMARC record format.
+ the &acro.usmarc; record format.
</para>
</note>
<para>