Prepare for Data Preservation and Sharing

Before data can be shared and reused, it must be robustly stored and ultimately preserved beyond the lifetime of the project. Data governance rules, which specify who can have access and for what purpose, may change throughout the lifecycle of the data. At the end of the project, teams are expected to publish data to appropriate community repositories as well as preserve pre-publication artifacts for their own future reuse by depositing these artifacts in a repository with the appropriate access controls.

The Genesis Mission recognizes open science as an accelerant of scientific discovery as well as the need to protect sensitive, proprietary information, and US competitiveness. The Genesis Mission is developing streamlined and efficient mechanisms to determine how data generated through the mission will be shared, as well as clear metadata and documentation to describe the rules for access and reuse.

Teams are encouraged to openly share as much of their research artifacts as possible and to do this in ways that are FAIR and machine actionable. Publishing reusable, machine actionable data adds value to the overall mission by growing the corpus of scientific data ready for AI-training. They also add value to the authors by increasing the potential for citation and impact.

Identify Appropriate Repositories

Identify appropriate repositories for data generated by the project that support data preservation and long-term stewardship as well as the required data sharing, publication and/or protection. The DOE recommends using repositories that align with the Desirable Characteristics of Data Repositories for Federally Funded Research. Many repositories already exist to support domain-specific data.

Understand if your program or participating institutions already have required or recommended repositories. Plan early in your project for any effort related to preparing the repository for your data or preparing your data for the repository.

• Repository Map: An interactive tool to identify scientific data repositories by discipline and Genesis Mission grand challenge area. It seeks to capture, for each one, the characteristics of the data it holds, whether it is domain-specific or a generalist repository, the possible costs to deposit and to access data, if it curates public and/or non-public products, and how it aligns with the Genesis Mission RFA topics and National S&T Challenges. The repository map represents a resource and not a requirement. Inclusion is not an endorsement, recommendation, or preference, and teams may use unlisted repositories, public and non-public. Teams should contact their program manager for any questions about repository selection.

  Teams are encouraged recommend additional repositories for potential inclusion in the Repository Map using the "Suggest a Repository" button on the interactive map homepage. Users of the map should verify each repository against their own requirements.

  • The interactive map is available at: https://data-repositories-map-718ecc.gitlab.io

Ensure Data are Reviewed Before Sharing

Ensure all digital objects are appropriately reviewed before sharing outside the originating collaboration. Many institutions and programs have specific data review requirements and processes. Understand your project's participating institutions' processes and timelines early on in the project and build these dependencies into your project plan. If there are questions about federal and DOE data release and sharing requirements, please work with research compliance staff, including post award administration and tech transfer offices, for clarification.

Consult with your institution's sponsored research, publications, and/or tech transfer office to ensure compliance with policies and procedures for reviewing publications, Scientific and Technical Information release, reporting intellectual property, invention and copyright disclosures, and reviewing export control, security, and other public release checkpoints.

Follow DOE Acknowledgement Guidance

The Department of Energy provides specific language for acknowledging federal support in research artifacts: https://science.osti.gov/Funding-Opportunities/Acknowledgements

For teams wishing to acknowledge the Genesis Mission, the following language is recommended:

This work was supported by the U.S. Department of Energy, [enter appropriate Office, e.g. Science, etc., Office of [insert the sponsoring Program Office, e.g., Advanced Scientific Computing Research], [Add any additional acknowledgements or information requested by the sponsoring Program Office] [optional: under award/contract number XXXXXX], in alignment with DOE's Genesis Mission.

"This material is based upon work supported by the U.S. Department of Energy, Office of Science, Office of [insert the SC Program Office funding the award, e.g., Basic Energy Sciences], [Add any additional acknowledgements or information requested by the sponsoring SC Program Office] under Award Number(s) [Enter the award number(s)]."

• Suggested language for use in the additional acknowledgement section above for U.S. Department of Energy, Genesis Mission products:

• For products from explicitly funded Genesis Mission activities, advise use of this templated approach:

  • [Program Office] as part of the Genesis Mission National Science and Technology Challenges [under Award Number(s)…]

• For products and teams who use Genesis Mission public resources in their own research, but were not funded under an explicit Genesis Mission program line, advise use of this templated approach:

  • This work utilized resources made available by the U.S. Department of Energy’s Genesis Mission

Next Section: Contribute to a FAIR, Machine-Actionable Web of Science