Skip to main content
U.S. flag

An official website of the United States government

Fundamental Science Practices for release of approved versus provisional USGS scientific software, review and approval of software, disclaimers, versioning, software licenses, scripts and models, and digital object identifiers.

Filter Total Items: 17

What is the difference between approved and provisional software? [076]

In contrast to approved software, provisional or preliminary scientific software is subject to change and is not approved as a USGS information product but may be shared informally through a publicly accessible code repository following Science Center approval. [Read more]

link

What is the difference between approved and provisional software? [076]

In contrast to approved software, provisional or preliminary scientific software is subject to change and is not approved as a USGS information product but may be shared informally through a publicly accessible code repository following Science Center approval. [Read more]

Learn More

When is USGS scientific software ready for approval and public release? [077]

Scientific software is ready for approval and public release when a version of the software is no longer under development, includes the appropriate documentation, and has been reviewed in accordance with IM OSQI 2019-01 requirements. [Read more]

link

When is USGS scientific software ready for approval and public release? [077]

Scientific software is ready for approval and public release when a version of the software is no longer under development, includes the appropriate documentation, and has been reviewed in accordance with IM OSQI 2019-01 requirements. [Read more]

Learn More

What are the approval requirements for USGS scientific software releases? [078]

USGS scientific software releases are approved by the Science Center Director, the authoritative copy is maintained on a USGS hosting platform (e.g. code.usgs.gov). Nonauthoritative copies can be shared on externally hosted platforms but the DOI must point to the USGS hosting platform. [Read more]

link

What are the approval requirements for USGS scientific software releases? [078]

USGS scientific software releases are approved by the Science Center Director, the authoritative copy is maintained on a USGS hosting platform (e.g. code.usgs.gov). Nonauthoritative copies can be shared on externally hosted platforms but the DOI must point to the USGS hosting platform. [Read more]

Learn More

What are the requirements for publicly releasing USGS data and scientific software associated with a cooperator publication? [185]

The FSP requirements for release of USGS scientific data and software associated with scholarly publications also apply to cooperator publications. Data and software management, publishing, and curation responsibility should be specified in data management plans. [Read more]

link

What are the requirements for publicly releasing USGS data and scientific software associated with a cooperator publication? [185]

The FSP requirements for release of USGS scientific data and software associated with scholarly publications also apply to cooperator publications. Data and software management, publishing, and curation responsibility should be specified in data management plans. [Read more]

Learn More

Where can I find additional information about managing and releasing USGS software? [143]

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

link

Where can I find additional information about managing and releasing USGS software? [143]

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

Learn More

What hosting platforms are available for releasing USGS scientific software? [142]

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]

link

What hosting platforms are available for releasing USGS scientific software? [142]

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]

Learn More

What is the distinction in software release requirements between scripts used to prepare data for analysis or graphical visualizations and models or other packages of source code? [141]

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]

link

What is the distinction in software release requirements between scripts used to prepare data for analysis or graphical visualizations and models or other packages of source code? [141]

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]

Learn More

What are some reasons to not use a public repository for developing software? [140]

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]

link

What are some reasons to not use a public repository for developing software? [140]

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]

Learn More

Do software releases need a DOI? [139]

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]

link

Do software releases need a DOI? [139]

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]

Learn More

What is required to comply with Federal Source Code Policy? [138]

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]

link

What is required to comply with Federal Source Code Policy? [138]

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]

Learn More

My software release repository requires an open-source license. What can I use? What do I need to know about licenses? [137]

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

link

My software release repository requires an open-source license. What can I use? What do I need to know about licenses? [137]

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

Learn More

Can I contribute code to open source projects, and if so, how should I identify and document my contributions? [136]

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]

link

Can I contribute code to open source projects, and if so, how should I identify and document my contributions? [136]

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]

Learn More