1 |
2903
|
harris
|
<!--
|
2 |
|
|
* datafiles.html
|
3 |
|
|
*
|
4 |
|
|
* Authors: Chad Berkley
|
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: 2001 January 23
|
9 |
|
|
* Version:
|
10 |
|
|
* File Info: '$ '
|
11 |
|
|
*
|
12 |
|
|
*
|
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">Non-XML Data Files</p></td>
|
23 |
|
|
<td class="tablehead" colspan="2" align="right">
|
24 |
|
|
<a href="./replication.html">Back</a> | <a href="./metacattour.html">Home</a> |
|
25 |
|
|
<a href="./properties.html">Next</a>
|
26 |
|
|
</td>
|
27 |
|
|
</tr>
|
28 |
|
|
</table>
|
29 |
|
|
|
30 |
|
|
|
31 |
2905
|
harris
|
<p><br>
|
32 |
|
|
<a href="./replication.html">Back</a> | <a href="./metacattour.html">Home</a> |
|
33 |
|
|
<a href="./properties.html">Next</a> </p>
|
34 |
|
|
<p><br>
|
35 |
|
|
</p>
|
36 |
|
|
<p><u>What is an LSID:</u></p>
|
37 |
|
|
<p>LSID's were designed to be a globally-recognized short identifiers for a complex
|
38 |
|
|
entities that are both computer and human readable.</p>
|
39 |
|
|
<p> </p>
|
40 |
|
|
<p><u>Why LSID's are in Metacat:</u></p>
|
41 |
|
|
<p>We chose to incorporate LSID's in metacat so as to support a globally accepted
|
42 |
|
|
standard for identifying biological entities instead of using a proprietary
|
43 |
|
|
scheme.
|
44 |
|
|
By doing this we have exposed data and metadata stored in Metacat through
|
45 |
|
|
a variety of LSID clients. Additionally, the LSID support in Metacat has
|
46 |
|
|
been implemented as a series Simple Object Access Protocol (SOAP) interfaces
|
47 |
|
|
with the intent of providing an easily modifiable system.</p>
|
48 |
|
|
<p> </p>
|
49 |
|
|
<p><u>What you get with Metacat's LSID Support:</u></p>
|
50 |
|
|
<p>By enabling the Metacat LSID support you will be able to use the LSID clients
|
51 |
|
|
and notation to query Metacat for data and metadata. An example of an LSID
|
52 |
|
|
client is the <a href="http://lsid.sourceforge.net/">LSID Launchpad</a>. Furthermore,
|
53 |
|
|
one can use the LSID notation directly in the Metacat http query to access
|
54 |
|
|
data and metadata within a Metacat.
|
55 |
|
|
For example, a document (tao.12039.1) stored in a Metacat available at: http://qtz.homelinux.com:9999
|
56 |
|
|
can be accessed by the following http Metacat queries:</p>
|
57 |
|
|
<br>
|
58 |
|
|
|
59 |
|
|
<pre>http://qtz.homelinux.com:9999/authority/data?lsid=urn:lsid:sulphur.ecoinformatics.org:tao:12039:1</pre>
|
60 |
|
|
<pre>http://qtz.homelinux.com:9999/authority/metadata?lsid=urn:lsid:sulphur.ecoinformatics.org:tao:12039:1</pre>
|
61 |
|
|
<br>
|
62 |
|
|
|
63 |
|
|
<p>The first query returns the data associated with that document and the second
|
64 |
|
|
query returns the metadata. Notice that the periods in the Metacat document
|
65 |
|
|
ID have been replaced with colons. Also notice the host urn attribute
|
66 |
|
|
(urn:lsid:sulphur.ecoinformatics.org), this host needs to be set as a SRV record
|
67 |
|
|
as DNS entry on the DNS server for ecoinformatics.org. To use LSID support
|
68 |
|
|
in Metacat the Metacat administrator does need to have access to the DNS server
|
69 |
|
|
for the domain hosting the Metacat so that he/she can modify the SRV record(s).
|
70 |
|
|
The Metacat build.proprties LSID attributes for the above example are: </p>
|
71 |
|
|
<pre>authority.context=authority</pre>
|
72 |
|
|
<pre>config.lsidauthority=sulphur.ecoinformatics.org</pre>
|
73 |
|
|
<p>** the SRV record for sulphur.ecoinformatics.org points to qtz.homelinux.com
|
74 |
|
|
on port 9999</p>
|
75 |
|
|
<p> </p>
|
76 |
|
|
<p> </p>
|
77 |
|
|
<p> </p>
|
78 |
2903
|
harris
|
</BODY>
|
79 |
2905
|
harris
|
|
80 |
2903
|
harris
|
</HTML>
|