I want to search

MENU

Deployment Routes

MN Software Implementation Choices

DataONE cyberinfrastructure's flexible architecture and software products actively support a variety of ways to implement Member Node services that should suit any organization’s starting point. Most repository options are released under open source licensing, and DataONE has a flexible deployment process supported by community expertise to help ensure a successful deployment.

Use an existing Member Node repository product

This route is good for those wanting a turn-key solution for managing and preserving their data products. Two Member Node products currently exist: Metacat and the Generic Member Node (GMN).

Member Node products

Integrate a repository with GMN

GMN, one the existing Member Node products, can also be configured to interoperate with an existing repository, providing most functionality except data object storage. This route may be appropriate for organizations with a third-party repository that cannot be extended.

Generic Member Node overview

Extend an existing repository with custom development

Implementing the Member Node API can be done incrementally or all at once. DataONE maintains several code libraries and compilation units that can be used to simplify custom development projects.

Custom Development Overview

Level of Implementation (Tiers)

Member Nodes may select a Tier level for implementation to determine how much of the DataONE Member Node API to implement. DataONE has defined several tiers, each of which designates a certain level of functionality exposed through the MN API.

Tier 1: Read, public objects (MNCore and MNRead APIs)

Provides read-only access to publicly available objects (Science Data, science metadata, and Resource Maps), along with core system API calls for monitoring and logging.

Tier 2: Access control (MNAuthentication API)

Allows the access to objects to be controlled via access control list (ACL) based authorization and certificate-based authentication.

Tier 3: Write (MNStorage API)

Provides write access (create, update and archive objects). Allows using DataONE interfaces to create and maintain objects on the MN.

Tier 4: Replication target (MNReplication API)

Allows the DataONE infrastructure to use available storage space on the MN for storing copies of objects that originate on other MNs, based on the Node Replication Policy.