1 |
878
|
berkley
|
<!--
|
2 |
|
|
* Metacatdb.html
|
3 |
|
|
*
|
4 |
|
|
* Authors: Jivka Bojilova
|
5 |
|
|
* Copyright: 2000 Regents of the University of California and the
|
6 |
|
|
* National Center for Ecological Analysis and Synthesis
|
7 |
|
|
* For Details: http://www.nceas.ucsb.edu/
|
8 |
|
|
* Created: 2000 April 5
|
9 |
|
|
* Version: 0.01
|
10 |
|
|
* File Info: '$Id$'
|
11 |
|
|
*
|
12 |
|
|
* October Meeting SDSC, 2000
|
13 |
|
|
-->
|
14 |
|
|
<HTML>
|
15 |
|
|
<HEAD>
|
16 |
|
|
<TITLE>Metacat</TITLE>
|
17 |
|
|
<link rel="stylesheet" type="text/css" href="@docrooturl@default.css">
|
18 |
|
|
</HEAD>
|
19 |
|
|
<BODY>
|
20 |
|
|
<table width="100%">
|
21 |
|
|
<tr>
|
22 |
|
|
<td class="tablehead" colspan="2"><p class="label">Metacat Database</p></td>
|
23 |
|
|
<td class="tablehead" colspan="2" align="right">
|
24 |
|
|
<a href="./metacat.html">Back</a> | <a href="./metacattour.html">Home</a> |
|
25 |
|
|
<a href="./metacatdom.html">Next</a>
|
26 |
|
|
</td>
|
27 |
|
|
</tr>
|
28 |
|
|
</table>
|
29 |
|
|
|
30 |
|
|
<P>The Metacat Database stores the structure and data of any arbitrary
|
31 |
|
|
xml document. Metacat DB uses the DOM
|
32 |
|
|
approach to store XML documents as a hierarchy of nodes. All nodes are stored
|
33 |
|
|
as records in database tables. The hierarchical relationship between the nodes
|
34 |
|
|
is saved to preserve the structure of the documents.</p>
|
35 |
|
|
|
36 |
|
|
<p>The database Entity Relationship Diagram (ERD) currently looks like this:</p>
|
37 |
|
|
<img alt="Entity Relationship Diagram of the Metacat Database" src="metacatdb.gif">
|
38 |
|
|
<br><br>
|
39 |
|
|
<b>Table Descriptions</b>
|
40 |
|
|
<ul>
|
41 |
|
|
<li><b>xml_documents</b> contains document level information. It
|
42 |
|
|
stands as a tie in to xml_nodes with the rootnodeid field.</li>
|
43 |
|
|
<li><b>xml_nodes</b> contains all of the data needed to recreate an
|
44 |
|
|
XML document that has been inserted into the system. Each document's xml tree
|
45 |
|
|
is represented by the node pointers in the table. </li>
|
46 |
|
|
<li><b>xml_index</b> contains indexing information for the paths in
|
47 |
|
|
xml_nodes. This is data that has been denormalized for performance reasons.
|
48 |
|
|
xml_index allows the fast searching of paths within an xml document.</li>
|
49 |
|
|
<li><b>xml_revisions</b> contains the document information (including the
|
50 |
|
|
rootnode pointer) to any document that has been deleted (either by an explicit
|
51 |
|
|
delete or by an update). This ensures that a complete lineage of any document
|
52 |
|
|
is traced.</li>
|
53 |
|
|
<li><b>xml_replication</b> contains the list of Metacat servers that this
|
54 |
|
|
server replicates to or from.</li>
|
55 |
|
|
<li><b>xml_relation</b> contains any relation information inserted by a
|
56 |
|
|
<a href="./packages.html">Package</a> document.</li>
|
57 |
|
|
<li><b>xml_access</b> contains all Access Control List (ACL) information
|
58 |
|
|
relevent to a document.</li>
|
59 |
|
|
<li><b>xml_catalog</b> contains catalog information that represents DTDs
|
60 |
|
|
and XSL stylesheets that are registered with the system.</li>
|
61 |
|
|
</ul>
|
62 |
|
|
|
63 |
|
|
<br>
|
64 |
|
|
<a href="./metacat.html">Back</a> | <a href="./metacattour.html">Home</a> |
|
65 |
|
|
<a href="./metacatdom.html">Next</a>
|
66 |
|
|
</BODY>
|
67 |
|
|
</HTML>
|