Fundamental Science Practices Frequently Asked Questions

The overall project work plan of every research project must include a DMP. [Read more]

DMP examples from various institutions can be found at https://dmptool.org/.

The USGS Data Management website provides guidance on developing DMPs and understanding data management best practices. [Read more]

Yes. Some centers have developed guidance for data management. It is important that project-specific details are captured in the DMP. [Read more]

A data management plan (DMP) is helpful for staff in your program or center thinking about and become committed to data management responsibilities before a project begins. You may need data management input from other staff and experts. If data management details change, your DMP should be updated to reflect those changes. [Read more]

Science Center Directors or their designees ensure compliance with data management requirements for data produced in their centers or offices and consult with other managers, scientists, and staff as needed with regard to carrying out data management activities, including ensuring the development of data management plans. [Read more]

Scientific software is a discrete package of computer code and documentation that contains source code implementing scientific algorithms or producing scientific data. All USGS scientific software products intended for public release are reviewed and approved in accordance with USGS FSP requirements. [Read more]

Because software may be further developed and subsequently updated after the original version is released, all revised software should be released with a new version number. Although the approach to version numbering can vary, revised software releases can be grouped into three general categories: major revision, minor revision, and patch. [Read more]

Yes. Software produced by the USGS and released publicly is in the public domain. However, some software may be partially or wholly owned by a non-Federal partner (e.g., university) and may elect to apply a license, including an open source license that includes restrictions. USGS employees have several options to navigate these circumstances. [Read more]

The software developer needs to have an understanding of the repository’s open source licensing requirements; several licensing options may be considered. [Read more]

Generally, source code associated with USGS software releases must be made available at minimum for Federal Government-wide reuse. Source code for USGS software releases must include an appropriate open-source license or secured re-use rights; be included in the USGS source code inventory; be accompanied by documentation to facilitate reuse and participation by third parties. [Read more]

Yes. Approved USGS software releases must be assigned a DOI with the 10.5066 prefix using the USGS Digital Object Identifier (DOI) Creation Tool. Software release products should be assigned a meaningful resource type in the DOI metadata such as software, model, workflow, or another appropriate term. The DOI metadata must appropriately describe the software product. [Read more]

Department of the Interior, including USGS, applies strict requirements and platform authorizations for sharing software in public repositories. To avoid potential violations, policy-compliant and secure internal code repositories are available for sharing and releasing software. [Read more]

Author should work together with their supervisor and Science Center Director to determine if a set of source code is appropriate for release as a USGS scientific software release or if the algorithms or statistical methods would alternatively be more appropriate for inclusion in an associated manuscript or the metadata of a data release. [Read more]

The authoritative (or reference) copy of an approved USGS scientific software release must be distributed through a “.gov” server to comply with USGS open access requirements. USGS Git hosting platform is available, including USGS OpenSource GitLab, or USGS InnerSource GitLab, which can be restricted to a specific group of collaborators. [Read more]

Refer to the Software Management website for additional information, including best practices and guidance related to the management and release of USGS software.

Inform your supervisor, Center Director, and BAO to expedite review and approvals; BAOs may be able to move the product up in their queues. Manuscripts that will be posted online as soon as they are received by the journal should obtain Bureau approval prior to submission. To avoid these situations, discuss the USGS FSP process with coauthors before a manuscript is sent to a journal. [Read more]

The IPDS serves as an archive for short-term, temporary records. In the event the journal does not provide free public access, the accepted manuscript that is placed in the IPDS can be provided to the public through the USGS Publications Warehouse. This will ensure the USGS meets the OSTP public access requirement for federally funded research. [Read more]

These limited-use publication series products are prepared when directed by USGS management in concert with or independent of a request from a U.S. Government agency, foreign government or agency, or international entity funding partner. RFFIRs are directed and (or) requested when investigations involve threatened or endangered species or are in support of confidential negotiations or litigation.

A letter report is one possible format for a Restricted-File Federal Interagency Report (RFFIR). An optional template for RFFIRs is available. [Read more]

A printed copy of each Restricted-File Federal Interagency Report (RFFIR) must be sent to the USGS Library (Reston) for the Library’s limited-access storage. Another copy of the RFFIR should be maintained with other project material in accordance with the Department’s policy regarding official records. [Read more]