dom: accept type="adelete" (accept bad deletes)

[idzebra-moved-to-github.git] / doc / marc_indexing.xml

diff --git a/doc/marc_indexing.xml b/doc/marc_indexing.xml
index a949a4b..597e7a6 100644 (file)
--- a/doc/marc_indexing.xml
+++ b/doc/marc_indexing.xml
@@ -1,38 +1,37 @@
 <?xml version="1.0" encoding="iso-8859-1" standalone="no" ?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" 
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook &acro.xml; V4.2//EN" 
  "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
 
-<!-- $Id: marc_indexing.xml,v 1.3 2006-02-15 11:07:47 marc Exp $ -->
 
 <book id="marc_indexing">
 <bookinfo>
- <title>Indexing of MARC records by Zebra</title>
+ <title>Indexing of &acro.marc; records by &zebra;</title>
  <abstract>
-  <simpara>Zebra is suitable for distribution of MARC records via Z39.50. We
-       have a several possibilities to describe the indexing process of MARC records.
+  <simpara>&zebra; is suitable for distribution of &acro.marc; records via &acro.z3950;. We
+       have a several possibilities to describe the indexing process of &acro.marc; records.
        This document shows these possibilities.
   </simpara>
  </abstract>
 </bookinfo>
 
 <chapter id="simple">
- <title>Simple indexing of MARC records</title>
+ <title>Simple indexing of &acro.marc; records</title>
 <para>Simple indexing is not described yet.</para>
 </chapter>
 
 <chapter id="extended">
- <title>Extended indexing of MARC records</title>
+ <title>Extended indexing of &acro.marc; records</title>
 
-<para>Extended indexing of MARC records will help you if you need index a
+<para>Extended indexing of &acro.marc; records will help you if you need index a
 combination of subfields, or index only a part of the whole field,
-or use during indexing process embedded fields of MARC record.
+or use during indexing process embedded fields of &acro.marc; record.
 </para>
 
-<para>Extended indexing of MARC records additionally allows:
+<para>Extended indexing of &acro.marc; records additionally allows:
 <itemizedlist>
 
 <listitem>
-<para>to index data in LEADER of MARC record</para>
+<para>to index data in LEADER of &acro.marc; record</para>
 </listitem>
 
 <listitem>
@@ -44,24 +43,24 @@ or use during indexing process embedded fields of MARC record.
 </listitem>
 
 <listitem>
-<para>to index linked fields for UNIMARC based formats</para>
+<para>to index linked fields for UNI&acro.marc; based formats</para>
 </listitem>
 
 </itemizedlist>
 </para>
 
 <note><para>In compare with simple indexing process the extended indexing
-may increase (about 2-3 times) the time of indexing process for MARC
+may increase (about 2-3 times) the time of indexing process for &acro.marc;
 records.</para></note>
 
 <sect1 id="formula">
 <title>The index-formula</title>
 
 <para>At the beginning, we have to define the term <emphasis>index-formula</emphasis>
-for MARC records. This term helps to understand the notation of extended indexing of MARC records
-by Zebra. Our definition is based on the document <ulink url="http://www.rba.ru/rusmarc/soft/Z39-50.htm">"The
-table of conformity for Z39.50 use attributes and RUSMARC fields"</ulink>.
-The document is available only in russian language.</para>
+for &acro.marc; records. This term helps to understand the notation of extended indexing of MARC records
+by &zebra;. Our definition is based on the document <ulink url="http://www.rba.ru/rusmarc/soft/Z39-50.htm">"The
+table of conformity for &acro.z3950; use attributes and R&acro.usmarc; fields"</ulink>.
+The document is available only in Russian language.</para>
 
 <para>The <emphasis>index-formula</emphasis> is the combination of subfields presented in such way:</para>
 
@@ -69,7 +68,7 @@ The document is available only in russian language.</para>
 71-00$a, $g, $h ($c){.$b ($c)} , (1)
 </screen>
 
-<para>We know that Zebra supports a Bib-1 attribute - right truncation.
+<para>We know that &zebra; supports a &acro.bib1; attribute - right truncation.
 In this case, the <emphasis>index-formula</emphasis> (1) consists from 
 forms, defined in the same way as (1)</para>
 
@@ -79,7 +78,7 @@ forms, defined in the same way as (1)</para>
 71-00$a
 </screen>
 
-<note><para>The original MARC record may be without some elements, which included in <emphasis>index-formula</emphasis>.</para>
+<note><para>The original &acro.marc; record may be without some elements, which included in <emphasis>index-formula</emphasis>.</para>
 </note>
 
 <para>This notation includes such operands as:
@@ -92,7 +91,7 @@ forms, defined in the same way as (1)</para>
 
 <varlistentry>
  <term>-</term>
- <listitem><para>The position may contain any value, defined by MARC format.
+ <listitem><para>The position may contain any value, defined by &acro.marc; format.
  For example, <emphasis>index-formula</emphasis></para>
 
 <screen>
@@ -132,21 +131,21 @@ forms, defined in the same way as (1)</para>
 </varlistentry>
 </variablelist>
 
-<note><para>All another operands are the same as accepted in MARC world.</para>
+<note><para>All another operands are the same as accepted in &acro.marc; world.</para>
 </note>
 </para>
 </sect1>
 
 <sect1 id="notation">
-<title>Notation of <emphasis>index-formula</emphasis> for Zebra</title>
+<title>Notation of <emphasis>index-formula</emphasis> for &zebra;</title>
 
 
 <para>Extended indexing overloads <literal>path</literal> of
-<literal>elm</literal> definition in abstract syntax file of Zebra
+<literal>elm</literal> definition in abstract syntax file of &zebra;
 (<literal>.abs</literal> file). It means that names beginning with
-<literal>"mc-"</literal> are interpreted by Zebra as
+<literal>"mc-"</literal> are interpreted by &zebra; as
 <emphasis>index-formula</emphasis>. The database index is created and
-linked with <emphasis>access point</emphasis> (Bib-1 use attribute)
+linked with <emphasis>access point</emphasis> (&acro.bib1; use attribute)
 according to this formula.</para>
 
 <para>For example, <emphasis>index-formula</emphasis></para>
@@ -172,7 +171,7 @@ mc-71.00_$a,_$g,_$h_(_$c_){.$b_(_$c_)}
 
 <varlistentry>
 <term>.</term>
-<listitem><para>The position may contain any value, defined by MARC format. For example,
+<listitem><para>The position may contain any value, defined by &acro.marc; format. For example,
 <emphasis>index-formula</emphasis></para>
 
 <screen>
@@ -232,7 +231,7 @@ includes</para>
 </para>
 
 <note>
-<para>All another operands are the same as accepted in MARC world.</para>
+<para>All another operands are the same as accepted in &acro.marc; world.</para>
 </note>
 
 <sect2>
@@ -265,7 +264,7 @@ elm mc-ldr[7] Bib-level   !
 elm mc-008[0-5] Date/time-added-to-db !        
 </screen>
 
-<para>or for RUSMARC (this data included in 100th field)</para>
+<para>or for R&acro.usmarc; (this data included in 100th field)</para>
 
 <screen>
 elm mc-100___$a[0-7]_ Date/time-added-to-db !
@@ -277,14 +276,14 @@ elm mc-100___$a[0-7]_ Date/time-added-to-db !
 
 <para>using indicators while indexing</para>
 
-<para>For RUSMARC <emphasis>index-formula</emphasis>
+<para>For R&acro.usmarc; <emphasis>index-formula</emphasis>
 <literal>70-#1$a, $g</literal> matches</para>
 
 <screen>
 elm 70._1_$a,_$g_ Author !:w,!:p
 </screen>
 
-<para>When Zebra finds a field according to <literal>"70."</literal> pattern it checks
+<para>When &zebra; finds a field according to <literal>"70."</literal> pattern it checks
 the indicators.  In this case the value of first indicator doesn't mater, but
 the value of second one must be whitespace, in another case a field is not 
 indexed.</para>
@@ -293,9 +292,9 @@ indexed.</para>
 
 <listitem>
 
-<para>indexing embedded (linked) fields for UNIMARC based formats</para>
+<para>indexing embedded (linked) fields for UNI&acro.marc; based formats</para>
 
-<para>For RUSMARC <emphasis>index-formula</emphasis> 
+<para>For R&acro.usmarc; <emphasis>index-formula</emphasis> 
 <literal>4--#-$170-#1$a, $g ($c)</literal> matches</para>
 
 <screen>