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