Project

General

Profile

« Previous | Next » 

Revision 6878

Initial outline for DataONE chapter.

View differences:

docs/user/metacat/source/dataone.rst
1
DataONE Member Nodes
2
====================
1
DataONE Member Node Support
2
===========================
3 3

  
4
Chapter to be written.
4
DataONE_ is a federation of data repositories that aims to improve 
5
interoperability among data repository software systems and advance the
6
preservation of scientific data for future use.
7
Metacat deployments can be configured to participate in DataONE_. This 
8
chapter describes the DataONE_ data federation,  its architecture, and the 
9
way in which Metacat can be used to participate as a node in the DataONE system.
5 10

  
11
.. _DataONE: http://dataone.org/
12

  
13
What is DataONE?
14
----------------
15
The DataONE_ project is a collaboration among scientists, technologists, librarians,
16
and social scientists to build a robust, interoperable, and sustainable system for
17
preserving and accessing Earth observational data at national and global scales.  
18
Supported by the U.S. National Science Foundation, DataONE partners focus on
19
technological, finalncial, and organizational sustainability approaches to 
20
building a distributed network of data repositories that are fully interoperable,
21
even when those repositories use divergent underlying software and support different
22
data and metadata content standards. DataONE defines a common web-service service 
23
programming interface that allows the main software components of the DataONE system
24
to seamlessly communicate. The components of the DataONE system include:
25

  
26
* DataONE Service Interface
27
* Member Nodes
28
* Coordinating Nodes
29
* Investigator Toolkit
30

  
31
Metacat implements the services needed to operate as a DataONE Member Node, 
32
as described below.  The service interface then allows many different scientific 
33
software tools for data management, analysis, visualization and other parts of 
34
the scientific lifecycle to directly communicate with Metacat without being
35
further specialized beyond the support needed for DataONE.  This streamlines the
36
process of writing scientific software on both for servers and client tools.
37

  
38
The DataONE Service Interface
39
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
40
DataONE acheives interoperability
41
by defining a lightweight but powerful set of web services that can be
42
implemented by various data management software systems to allow those systems
43
to effectively communicate with one another, exchange data, metadata, and other
44
scientific objects.  This `DataONE Service Interface`_
45
is an open standard that defines the communication protocols and technical 
46
expectations for software components that wish to participate in the DataONE
47
federation. This service interface is divided into `four distinct tiers`_, with the 
48
intention that any given software system may implement only those tiers that are 
49
relevant to their repository; for example, a data aggregator might only implement
50
the Tier 1 interfaces that provide anonymous access to public data sets, while
51
a complete data management system like Metacat can implement all four tiers:
52

  
53
1. **Tier 1:** Read-only, anonymous data access
54
2. **Tier 2:** Read-only, with authentication and access control
55
3. **Tier 3:** Full Write access
56
4. **Tier 4:** Replication target services
57

  
58
.. _DataONE Service Interface: http://releases.dataone.org/online/d1-architecture-1.0.0
59

  
60
.. _four distinct tiers: http://releases.dataone.org/online/d1-architecture-1.0.0/apis/index.html
61

  
62
Member Nodes
63
~~~~~~~~~~~~
64

  
65
Coordinating Nodes
66
~~~~~~~~~~~~~~~~~~
67

  
68
Investigator Toolkit
69
~~~~~~~~~~~~~~~~~~~~
70

  
71
Metacat as a Member Node
72
------------------------
73

  

Also available in: Unified diff