Nuclear Research Data System

NRDS accepts all file formats, which allows you flexibility in how you organize and upload your datasets. You’ll need to complete metadata, including licensing information, for every dataset you upload.

If you don’t have a digital object identifier, NRDS will assign it regardless of file type. For data to be useful, supplementary information should be co-located with the dataset to provide context about how the experiment was conducted, facility specifications, and any other context needed to understand and reproduce results. Use your best judgment on what to include.

DOE recognizes that many datasets will be quite large. NRDS has storage in place to accommodate extremely large datasets.

 What to include:

• The raw dataset itself, in an open, machine-readable format where possible.
• A README file explaining the dataset’s contents and how to use it.
• Documentation of methods/procedures — how the experiment was conducted, instrument or facility specifications, calibration details.
• Related software, code, or tools needed to process or interpret the data.
• Any necessary data protections — de-identification, redaction of confidential or proprietary information.

Here are some possible types of reports, data, and data products you might include:

 Project documentation

• Statement of work, if available.
• Experimental Plan/Design – include specifications used for the experiment.
• Final reports and Milestone reports.
• Student theses/dissertations.
• Experimental plans.
• Journal articles copyrighted by the PI.
• Pre-print or open-access journal articles.
• Conference presentations.
• CAD files of the facility, including equipment used, model numbers, configurations, and sensor locations.

 Experimental and research data

• Raw and/or processed experimental data files containing the primary data generated during the experiment – for example materials characterization data (microstructural imaging, mechanical testing, irradiation testing), sensor/instrumentation logs, nuclear/radiological data, or analytical chemistry data.
• Simulation and modeling outputs, including source code, input/output files, and model validation datasets.
• Calibration and benchmark data used to verify instrument or model accuracy.
• Supplementary information on how to interpret raw data files, including column name descriptions and formatting notes.
• For processed data, the name and version of any software used for processing and analysis, a description of data processing steps (so the process is reproducible), and any scripts needed to repeat the processing.

 What Not to Include

Some information should never be uploaded to NRDS including anything that may be legally restricted, could compromise security, privacy, or intellectual property, or items that simply don’t belong in what will become a finished, public dataset. When in doubt, check with NEUP before uploading.

Do not upload:

• Export-controlled information
• Classified or national security information
• Controlled Unclassified Information (CUI)
• Personally identifiable information (PII)
• Proprietary or intellectual-property-sensitive data
• Data restricted by third-party agreements (e.g., confidentiality or licensing terms with a vendor or partner institution)
• Informal or unfinished notes not meant for public release
• Duplicate or outdated versions of a dataset, which can confuse users about which version is authoritative

Required Metadata Fields

The following fields are collected when entering a dataset on the NRDS Portal:

• Title (required) – a descriptive title that the dataset will be released as on the main NRDS website.
• Description (required) – useful information about the data, similar to a project abstract.
• Instruments – the device(s) used to collect or generate the data, including model numbers.
• Tags – keywords that describe the dataset and can be used as search filters.
• License (required) – the copyright license this dataset will be released under; a Creative Commons License can be selected in the NRDS system if no license has been created for the dataset.
• Project Association (required) – the project that this data was collected as part of and funded by.
• Embargo Expiration (required) – the date the data associated with this dataset will be released to the public; setting an embargo date allows the system to automatically release the data on that date. Note this is set at the dataset level, not the project level.
• Authors (required) – the author(s) of the dataset to be listed on the main NRDS website.
• Statement of Credit (required) – the statement others will use to cite your work.
• Dataset DOI – enter any DOI related to the project; If you don’t have a digital object identifier, NRDS will assign it regardless of file type.