A Hosted Repository provides groups with an easy-to-use data and metadata repository, web-based submission and metadata editing, assignment of a citable DOI in your own DOI prefix, and many other features. You can deposit datasets, documents, software, and other research artifacts, and assign a DOI to each. This is all operated on our infrastructure, minimizing the time that you need to spend on maintaining and securing computing systems, and on maintaining the repository software. You are in full control of the data curation for the data you upload to your hosted repository, and we make sure the service is stable and secure. This service is intended for institutions or projects that want to maintain a long-term repository presence.
What if I don’t want a Hosted Repository, but still want to use DataONE to store my data?
You can deposit data in one of the open DataONE repositories and then you can use the DataONE Plus service to build your own customizable data portal describing your project. DataONE Plus provides a customizable data portal where you control the pages and content via a web form, and can present a custom catalog populated with datasets from any of the member repositories in the DataONE network.
Can we set up a dataset curation/review process for submitted datasets?
Yes. Dataset curation can be as intensive as desired. Some Hosted Repositories have extensive review processes, whereas others allow dataset creators to publish datasets immediately without review. Curation can involve either editing and annotating metadata records via the API, or simply checking for errors. Generally, repositories that have a curation process tend to only allow members of their curation teams to assign DOIs and make datasets public.
Can datasets be privately viewable by certain groups and remain publicly invisible?
Yes, access to datasets can be controlled by DataONE’s Access Policy system. This access system can serve as a metadata curation and/or temporary publication embargo state prior to a wider release.
Does DataONE accept sensitive data?
DataONE’s mission is to make data more discoverable, accessible, and usable. While some of our member repositories may accept sensitive data, our Hosted Repository service is not intended for highly sensitive data, such as that which is subject to: 1) statutory restrictions such as HIPAA, FERPA, or other export control restrictions, or 2) classified information or other federally designated sensitive category.
We promote the long-term preservation of data with an intention of open data sharing. If you are unsure whether your data is appropriate for hosting, please contact support@dataone.org where our team members can help.
Where are DataONE's services hosted?
Our main services are hosted in the University of California, Santa Barbara (UCSB) North Hall Data Center. A second copy of the data is stored at an off-campus facility in downtown Santa Barbara, and a third copy is stored in a dark archive in the Amazon Glacier cloud storage system, primarily intended for disaster recovery. Other copies may be stored as replica objects at participating network member repositories across the world.
Are DataONE's software and infrastructure secure?
DataONE maintains an open source software stack built with modern security defect scanning and a defense in-depth security strategy supported by our University of California, Santa Barbara (UCSB) campus security. Our cyberinfrastructure has been reviewed by Trusted CI, the NSF Cybersecurity Center of Excellence, to strengthen our coding standards and ensure a strong baseline of our repository software. To learn more about related security policies and documentation, please visit the UCSB security policies page.
Has DataONE undergone a SOC 2 audit?
DataONE has not undergone a SOC 2 audit at this time and does not currently plan to pursue one.
Can the curation team or dataset owner reserve a DOI in order to publish later?
Yes. Repositories can be configured to be able to reserve DOI identifiers for datasets even while those datasets remain private (e.g. for embargo or other purposes). Contact your repository administrator to inquire about this setting.
What is a node name and how does it differ from a URL?
A node name is a unique identifier used in DataONE that refers to a specific repository. Users may not interact with this name much unless they are using the API, but it is used widely around our systems and power users may encounter it when they need to refer to a repository (“node”) within DataONE. We usually suggest that repositories use their primary name or acronym for this value; for example, the Arctic Data Center is urn:node:ARCTIC and the KNB is urn:node:KNB. “URN” stands for Uniform Resource Name, which is another way of saying that it is a unique value that refers specifically to the repository, in a similar way to that of a URL (“Uniform Resource Locator”). URNs are machine-readable links within DataONE systems, whereas URLs are links within broader internet systems.
Why should I consider DataONE Plus instead of a Hosted Repository?
DataONE Plus is ideal for projects that want to establish a data catalog and web presence, but may be shorter-term and do not want to maintain a complete data repository. This system provides a customizable data portal where you control the data content and web pages, and can present a custom catalog with content from any of the member repositories in the DataONE network.
How can I make changes to my portal?
If you have permissions to edit the portal, you can do it via our system. For a better tutorial, visit out Portals How-To Page.
Can we limit permissions to specific members and/or groups for certain portals?
Yes, each portal can be configured with customized permissions. This includes control over which users and groups can view the portal, edit its content, and manage its permissions. For more details, visit our Portals Tutorial or see our FAQ answers below.
What are DataONE's access controls and what do they mean?
Access control refers to the level of permissions a certain user has over an object. Individual and group access to objects in DataONE is controlled by a three-tiered permissions system consisting of viewers, editors, and owners. Viewers can see but not edit datasets, editors can view and edit but not share, and owners can do all of that plus grant access to others (and sometimes publish, depending on the repository). Repository rules sometimes limit dataset owners to only be able to edit datasets, and reserve sharing and/or publishing rights of datasets to a group of super-users such as a curation team.
Can I grant view, edit, or publish permissions to another person for my dataset?
Yes, if the repository allows it. Many repositories allow you to change view, edit, and publish permissions to your co-authors and reviewers for each dataset you submit using their ORCiD ID. Those repositories that do not allow authors to change dataset permissions themselves generally have a data curation team that can. To add someone as an editor to your dataset, look for the “Share” button at the top of the file list in the metadata editor (labeled 1) and for individual files (labeled 2): The resulting dialog box will then allow you to add viewers, editors, and owners using a search function (by ORCiD ID, name, email, or the name of a group of users):
