idzebra-2.0-doc 2.0.59-1 / usr / share / doc / idzebra-2.0-doc / idzebra-2.0 / generic-ids.html

This file is indexed.

/usr/share/doc/idzebra-2.0-doc/idzebra-2.0/generic-ids.html is in idzebra-2.0-doc 2.0.59-1.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below. 

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>6. Indexing with General Record IDs</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="Zebra - User's Guide and Reference"><link rel="up" href="administration.html" title="Chapter 6. Administrating Zebra"><link rel="prev" href="file-ids.html" title="5. Indexing with File Record IDs"><link rel="next" href="register-location.html" title="7. Register Location"></head><body><link rel="stylesheet" type="text/css" href="common/style1.css"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">6. Indexing with General Record IDs</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="file-ids.html">Prev</a> </td><th width="60%" align="center">Chapter 6. Administrating <span class="application">Zebra</span></th><td width="20%" align="right"> <a accesskey="n" href="register-location.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="generic-ids"></a>6. Indexing with General Record IDs</h2></div></div></div><p>
    When using this method you construct an (almost) arbitrary, internal
    record key based on the contents of the record itself and other system
    information. If you have a group of records that explicitly associates
    an ID with each record, this method is convenient. For example, the
    record format may contain a title or a ID-number - unique within the group.
    In either case you specify the <acronym class="acronym">Z39.50</acronym> attribute set and use-attribute
    location in which this information is stored, and the system looks at
    that field to determine the identity of the record.
   </p><p>
    As before, the record ID is defined by the <code class="literal">recordId</code>
    setting in the configuration file. The value of the record ID specification
    consists of one or more tokens separated by whitespace. The resulting
    ID is represented in the index by concatenating the tokens and
    separating them by ASCII value (1).
   </p><p>
    There are three kinds of tokens:
    </p><div class="variablelist"><dl class="variablelist"><dt><span class="term">Internal record info</span></dt><dd><p>
	The token refers to a key that is
	extracted from the record. The syntax of this token is
	<code class="literal">(</code> <span class="emphasis"><em>set</em></span> <code class="literal">,</code>
	<span class="emphasis"><em>use</em></span> <code class="literal">)</code>,
	where <span class="emphasis"><em>set</em></span> is the
	attribute set name <span class="emphasis"><em>use</em></span> is the
	name or value of the attribute.
       </p></dd><dt><span class="term">System variable</span></dt><dd><p>
	The system variables are preceded by

	</p><pre class="screen">
	 $
	</pre><p>
	and immediately followed by the system variable name, which
	may one of
	</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">group</span></dt><dd><p>
	    Group name.
	   </p></dd><dt><span class="term">database</span></dt><dd><p>
	    Current database specified.
	   </p></dd><dt><span class="term">type</span></dt><dd><p>
	    Record type.
	   </p></dd></dl></div><p>
       </p></dd><dt><span class="term">Constant string</span></dt><dd><p>
	A string used as part of the ID &#8212; surrounded
	by single- or double quotes.
       </p></dd></dl></div><p>
   </p><p>
    For instance, the sample GILS records that come with the <span class="application">Zebra</span>
    distribution contain a unique ID in the data tagged Control-Identifier.
    The data is mapped to the <acronym class="acronym">BIB-1</acronym> use attribute Identifier-standard
    (code 1007). To use this field as a record id, specify
    <code class="literal">(bib1,Identifier-standard)</code> as the value of the
    <code class="literal">recordId</code> in the configuration file.
    If you have other record types that uses the same field for a
    different purpose, you might add the record type
    (or group or database name) to the record id of the gils
    records as well, to prevent matches with other types of records.
    In this case the recordId might be set like this:

    </p><pre class="screen">
     gils.recordId: $type (bib1,Identifier-standard)
    </pre><p>

   </p><p>
    (see <a class="xref" href="grs.html" title="Chapter 9. GRS-1 Record Model and Filter Modules">Chapter 9, <i><acronym class="acronym">GRS-1</acronym> Record Model and Filter Modules</i></a>
    for details of how the mapping between elements of your records and
    searchable attributes is established).
   </p><p>
    As for the file record ID case described in the previous section,
    updating your system is simply a matter of running
    <code class="literal">zebraidx</code>
    with the <code class="literal">update</code> command. However, the update with general
    keys is considerably slower than with file record IDs, since all files
    visited must be (re)read to discover their IDs.
   </p><p>
    As you might expect, when using the general record IDs
    method, you can only add or modify existing records with the
    <code class="literal">update</code> command.
    If you wish to delete records, you must use the,
    <code class="literal">delete</code> command, with a directory as a parameter.
    This will remove all records that match the files below that root
    directory.
   </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="file-ids.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="register-location.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5. Indexing with File Record IDs </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 7. Register Location</td></tr></table></div></body></html>

APT Browse - Built by Thomas Orozco.