Ask Your Question

Revision history [back]

DataONE Member Nodes must faithfully implement the Member Node REST interface in order to interoperate with the other members of DataONE. This common REST service interface allows a Member Node to communicate with other Member Nodes, with client tools like R, and with the Coordinating Nodes at DataONE. Member Node services are categorized in 4 tiers (Tiers 1-4), and nodes can choose to implement the services at Tier 1 or above.

The simplest way to implement the interfaces in Java is to utilize our DataONE Client Library, which provides Java methods for calling and responding to each of the DataONE REST services. We have an overview of How To use the DataONE Java Client Library in your application, as well as JavaDoc APIs for the libclient library and our DataONE Common library.

As an implementation is developed, it can be tested using our Member Node API testing service. There are multiple versions of the tester listed there, each of which tests against different released versions of the software stack. Generally you'll want to use the most recent one.

The overall process of becoming a Member Node is described in our MN Checklist.

For development assistance, you can contact us on IRC at irc.ecoinformatics.org on channel #dataone, or via our email list at developers@dataone.org.

DataONE Member Nodes must faithfully implement the Member Node REST interface in order to interoperate with the other members of DataONE. This common REST service interface allows a Member Node to communicate with other Member Nodes, with client tools like R, and with the Coordinating Nodes at DataONE. Member Node services are categorized in 4 tiers (Tiers 1-4), and nodes can choose to implement the services at Tier 1 or above.

The simplest way to implement the interfaces in Java is to utilize our DataONE Client Library, which provides Java methods for calling and responding to each of the DataONE REST services. We have an overview of How To use the DataONE Java Client Library in your application, as well as JavaDoc APIs for the libclient library and our DataONE Common library.

As an implementation is developed, it can be tested using our Member Node API testing service. There are multiple versions of the tester listed there, each of which tests against different released versions of the software stack. Generally you'll want to use the most recent one.

The overall process of becoming a Member Node is described in our MN Checklist.

For development assistance, you can contact us on IRC at irc.ecoinformatics.org on channel #dataone, or via our email list at developers@dataone.org.