|
1
|
<!--
|
|
2
|
* metacatread.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: metacatread.html 878 2001-12-18 18:11:42Z berkley $'
|
|
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">Reading a Document
|
|
23
|
from the Database</p></td>
|
|
24
|
<td class="tablehead" colspan="2" align="right">
|
|
25
|
<a href="./metacatquery.html">Back</a> | <a href="./metacattour.html">Home</a> |
|
|
26
|
<a href="./saxparser.html">Next</a>
|
|
27
|
</td>
|
|
28
|
</tr>
|
|
29
|
</table>
|
|
30
|
<p>Metacat allows clients to read a document in several different ways,
|
|
31
|
depending on how the client wants the document returned and how the client
|
|
32
|
wants to specify the requested document. </p>
|
|
33
|
<P> <img alt="architecture diagram of the Metacat read process"
|
|
34
|
src="metadataread.gif"> </p>
|
|
35
|
<p>The documents are requested by <b>docid</b> servlet parameter:
|
|
36
|
<ul>
|
|
37
|
<li> By docid alone as: <br>
|
|
38
|
<i>docid=NCEAS.54</i></li>
|
|
39
|
<li> By Metacat URL as: <br>
|
|
40
|
<i>docid=metacat://server.domain.com/metacat?docid=NCEAS.54</i></li>
|
|
41
|
<li> By HTTP URL: <br>
|
|
42
|
<i>docid=http://otherserver.domain.com/filename</i></li>
|
|
43
|
</ul>
|
|
44
|
</p>
|
|
45
|
<p>There are two different output formats that a client can request from
|
|
46
|
Metacat: HTML or XML. This is specified by the <b>qformat</b> parameter. <br>
|
|
47
|
If more than one document is requested, the qformat does not matter,
|
|
48
|
instead the documents are zipped together and retrieved to the client. <br>
|
|
49
|
When <b>abstractpath</b> parameter along with docid parameter is
|
|
50
|
specified as a XPath expression of the location of abstract data within
|
|
51
|
XML document, the abstract data only are read and retrieved in XML format.
|
|
52
|
|
|
53
|
<p>For example, if a user wanted to request document NCEAS.54 and have it
|
|
54
|
returned as HTML, the servlet call would look like this: <br>
|
|
55
|
<i>http://server.domain.com/knb/servlet/metacat?action=read&qformat=html&docid=NCEAS.54</i>
|
|
56
|
<br>
|
|
57
|
Another way to request a document is by Metacat URL. the URL would look like: <br>
|
|
58
|
<i>http://server.domain.com/knb/servlet/metacat?
|
|
59
|
action=read&qformat=xml&docid=metacat://server.domain.com/metacat?docid=NCEAS.54</i>
|
|
60
|
<br>
|
|
61
|
Note that this url requests that the document be delivered in xml instead of html.
|
|
62
|
</p>
|
|
63
|
<p>
|
|
64
|
Metacat URLs as in the second example become useful when more than one Metacat
|
|
65
|
server is being run at one site or a bunch of sites are replicating between each
|
|
66
|
other and you want to specify a document at a precise location.
|
|
67
|
<!-- <a href="./packages.html">Package</a>
|
|
68
|
files exclusively use Metacat URLs for document identification. -->
|
|
69
|
</p>
|
|
70
|
|
|
71
|
<br>
|
|
72
|
<a href="./metacatquery.html">Back</a> | <a href="./metacattour.html">Home</a> |
|
|
73
|
<a href="./saxparser.html">Next</a>
|
|
74
|
|
|
75
|
</BODY>
|
|
76
|
</HTML>
|
|
77
|
|
