Who must submit?
Data sets from ARC-supported scientific research should be deposited in long-lived and publicly-available archives appropriate for the specific type of data collected (such as the NSF supported Arctic Data Center at http://arcticdata.io). Metadata for projects, regardless of where they are archived, should be submitted to this Arctic Data Center for improved access and discoverability.
For all ARC supported projects:
- Complete metadata must be submitted to a national data center or another long-lived publicly accessible archive within two years of collection or before the end of the award, whichever comes first.
- All data and derived data products that are appropriate for submission to a national data center or another long-lived publicly accessible archive, must be submitted within two years of collection or before the end of the award, whichever comes first.
For all ARC supported Arctic Observing Network projects:
- Real-time data must be made publicly available immediately. If there is any question about what constitutes real-time data, please contact the appropriate program officer.
- All data must be submitted to a national data center or another long-lived publicly accessible archive within 6 months of collection, and be fully quality controlled.
- All data sets and derived data products must be accompanied by a metadata profile and full documentation.
For reference, see the full ARC-programs data policy, including special conditions for Arctic Social Sciences Awards. Exceptions exist for sharing social science data that is ethically or legally sensitive or at risk of decontextualization. In these cases, we acknowledge the need to only preserve metadata and we accept such an approach. Please contact your NSF Program Manager or write to email@example.com with any questions.
All data and metadata will be released under either the CC-0 Public Domain Dedication or the Creative Commons Attribution 4.0 International License, with the potential exception of social science data that have certain sensitivities related to privacy or confidentiality. In cases where legal (e.g., contractual) or ethical (e.g., human subjects) barriers to data sharing exist, requests to restrict data publication must be requested in advance and in writing and are subject to the approval of the Director, who will ensure compliance with all federal, university, and Institutional Review Board policies on the use of restricted data. As a repository dedicated to helping researchers increase collaboration and the pace of science, this repository needs certain rights to copy, store, and redistribute data. By uploading data, metadata, and any other content to this repository, you warrant that you own any rights to the content and are authorized to do so under copyright or any other right that might pertain to the content. Data and facts themselves are not covered under copyright in the US and most countries, since facts in and of themselves are not eligible for copyright. That said, some associated metadata and some particular compilations of data could potentially be covered by copyright in some jurisdictions. By uploading content, you grant this repository and UCSB all rights needed to copy, store, redistribute, and share data, metadata, and any other content. By marking content as publicly available, you grant this repository, UCSB, and any other users the right to copy the content and redistribute it to the public without restriction under the terms of the Creative Commons Attribution 4.0 International License license or the CC-0 Public Domain Dedication, depending on which you choose at the time of upload.
Preparing data and metadata
To prepare for upload, it’s good to have your files in order. You might want to take a look at some best practices for managing your data files. For a given project, perhaps you have 6 data files, and one document that describes the methods that you used to collect or analyze your data. Collect these files into a single directory, and name them with short but descriptive names. Try to avoid spaces in your file names, but rather use dashes “-” or underscores “_”.
Use any file format.
While the Arctic Data Center supports the upload of any data file format, sharing data can be greatly enhanced if you use ubiquitous, easy-to-read formats. For instance, while Microsoft Excel files are commonplace, it’s better to export these spreadsheets to Comma Separated Values (CSV) text files, which can be read on any computer without having Microsoft products installed. Data submitted in Excel workbooks will undergo conversion to CSVs by our staff before being made public. Other proprietary formats will also be converted to plain-text formats when possible.
For image files, use common formats like PNG, JPEG, TIFF, etc. Most all browsers can handle these.
GIS data can be exported to ESRI shapefiles, and data created in Matlab or other matrix-based programs can be exported as NetCDF (an open binary format).
Finally, gather together metadata that describes your data, including information about the name and identity of the data, the geospatial coordinates where it was collected, when it was collected, and by whom. For people, you’ll want to have their names and contact information, and an ORCID identifier for them. You’ll want to have a good complete set of text describing the methods used to collect the data, as well as experimental design and sampling layouts. Finally, you’ll need the data files themselves. Once you’ve gathered this information, choose a data submission tool and get started!
Publishing with a DOI
Once data have been submitted to the Arctic Data Center, our metadata staff will review and provide suggestions for improvement. Once everything is set, we will make the data publicly accessible and publish it with a DOI. This will allow you and other researchers to cite the data set directly in NSF reports, publications, and other venues. The DOI is registered with DataCite using the EZID service, and will be discoverable through multiple data citation networks, including DataONE and others.
Once you have published your data with the Arctic Data Center, it can still be updated by providing an additional version which can replace the original, while still preserving the original and making it available to anyone who might have cited it. To update your data, return to the data submission tool used to submit it, and provide an update.
Any update to a data set qualifies as a new version and therefore requires a new DOI. This is because each DOI represents a unique, immutable version, just like for a journal article. DOIs and URLs for previous versions of data sets remain active on the Arctic Data Center (will continue to resolve to the dataset landing page for the specific version they are associated with), but a clear message will appear at the top of the page stating that “A newer version of this dataset exists” with a hyperlink to the latest version. With this approach, any past uses of a DOI (such as in a publication) will remain functional and will reference the specific version of the dataset that was cited, while pointing users to the newest version if one exists.
Data Submission Tools
On the web
Developers: REST API
In addition to our web and data tools shown above, the Arctic Data Center provides the ability to access and submit data via the DataONE REST API. This allows the community to use many programming languages to add data and metadata to the repository, search for and access data, and automate any process that might otherwise be highly time consuming. Most useful to groups with repetitive tasks to perform, such as submitting many data files of the same type, the REST API can be a real time saver. For more details, please contact us at firstname.lastname@example.org.
If you have a large volume of files to submit or the total size of your data is too large to upload via the web form, please submit your complete data set description (metadata) and write to email@example.com to arrange another method for data transfer. We have multiple options for transferring large amounts of data, including via Google Drive or our SFTP.