Member Node Requirements
DataONE's mission and funding orient it currently towards certain types of organizations, as characterized below, but this profile is not meant to be limiting. In deciding whether or not to establish a Member Node, it is useful to check the characteristics and general requirements of Member Nodes to see how closely your goals align. If unsure that your organization can benefit from joining the DataONE community as a Member Node, please contact us.
Characteristics of potential DataONE Member Node organizations
- Existing earth science domain repositories
- Existing Data Centers within the earth science domain
- Long-term projects and research activities wishing to preserve the their data products
- Organizations/Institutions establishing data infrastructures to manage scientific research data
- Organizations with computing and storage capabilities to augment the DataONE cyberinfrastructure
- Organizations/Institutions with expertise in eco- informatics research and applications
Maintain a preservation-oriented repository
Different repository products may take different approaches to data preservation, but in general:
- use persistent identifiers for data products
- ensure access to these data products over the long term
- ensure that metadata documents exist alongside the data products
Define Data Packages by persisting Resource Maps
Resource Maps provide a common format for describing the bidirectional relationship between a metadata object and the data object(s) it documents. DataONE expects all content submitted via your primary system to have associated Resource Maps. If your end-users will not be doing this alongside content submission, this should be a service you provide centrally.
Technical Information on Data Packages
Follow good data curation practices
Once published, end users expect the data product to remain the same over the long term. Curation practices should be compatible with data-preservation and data reproducibility ideals in mind. Specifically, content update and archiving activities should be transparent to DataONE end users.
Incorporate DataONE considerations into operational procedures
This is mostly notifying DataONE of (planned) system downtime, maintaining an accurate record of the services you offer and administrative contact information, and reporting and/or physically deleting illegal content. The goal here is improved services levels to end users.