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
|
<html><head><meta charset="ISO-8859-1"><title>3.Indexing and Retrieval Workflow</title><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="Zebra - User's Guide and Reference"><link rel="up" href="architecture.html" title="Chapter4.Overview of Zebra Architecture"><link rel="prev" href="architecture-maincomponents.html" title="2.Main Components"><link rel="next" href="special-retrieval.html" title="4.Retrieval of Zebra internal record data"></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">3.Indexing and Retrieval Workflow</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="architecture-maincomponents.html">Prev</a></td><th width="60%" align="center">Chapter4.Overview of <span class="application">Zebra</span> Architecture</th><td width="20%" align="right"><a accesskey="n" href="special-retrieval.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="architecture-workflow"></a>3.Indexing and Retrieval Workflow</h2></div></div></div><p>
Records pass through three different states during processing in the
system.
</p><p>
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
When records are accessed by the system, they are represented
in their local, or native format. This might be <acronym class="acronym">SGML</acronym> or HTML files,
News or Mail archives, <acronym class="acronym">MARC</acronym> records. If the system doesn't already
know how to read the type of data you need to store, you can set up an
input filter by preparing conversion rules based on regular
expressions and possibly augmented by a flexible scripting language
(Tcl).
The input filter produces as output an internal representation,
a tree structure.
</p></li><li class="listitem"><p>
When records are processed by the system, they are represented
in a tree-structure, constructed by tagged data elements hanging off a
root node. The tagged elements may contain data or yet more tagged
elements in a recursive structure. The system performs various
actions on this tree structure (indexing, element selection, schema
mapping, etc.),
</p></li><li class="listitem"><p>
Before transmitting records to the client, they are first
converted from the internal structure to a form suitable for exchange
over the network - according to the <acronym class="acronym">Z39.50</acronym> standard.
</p></li></ul></div><p>
</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="architecture-maincomponents.html">Prev</a></td><td width="20%" align="center"><a accesskey="u" href="architecture.html">Up</a></td><td width="40%" align="right"><a accesskey="n" href="special-retrieval.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.Main Components</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">4.Retrieval of <span class="application">Zebra</span> internal record data</td></tr></table></div></body></html>
|
