Fundamental Science Practices Frequently Asked Questions
What USGS scientific information products must follow FSP?
How does USGS define peer review and what are the FSP peer review requirements?
How is approval granted and what documents at a minimum must be submitted to the approving official?
What is the foundation of FSP?
What Federal Government policies require the release of scientific data, and how does the USGS intend to meet these requirements?
What is considered USGS scientific software and what are the USGS requirements for releasing it?
What types of project progress information can be reported and why is that important?
The frequently asked questions (FAQs) represent a Bureau consensus to ensure interpretations of Fundamental Science Practices (FSP) policies are uniformly applied throughout the USGS. These FAQs provide further explanation of the FSP and related publishing policies, as well as describe the procedures and decision making necessary to meet the policy requirements.
FSP Background
FSP Background
Authorship
Authorship
Review
Review
Approval
Approval
USGS Publication Series
USGS Publication Series
Journal Publications
Journal Publications
Metadata
Metadata
Data
Data
Software
Software
Project Reporting and Cooperator Publications
Project Reporting and Cooperator Publications
Web Pages, Conferences, Abstracts, and Presentations
Web Pages, Conferences, Abstracts, and Presentations
Preprints
Preprints
The FAQs will be updated as necessary and changes in the form of additions or revisions are reflected by date (month/year) as they occur. Questions about the FSP that are not addressed here should be directed to gs_fspac@usgs.gov.
FSP Frequently Asked Questions
FSP Frequently Asked Questions
Filter Total Items: 217
How may external collaborators add to USGS software projects and maintain “credit” for their individual contributions to USGS products? [227] How may external collaborators add to USGS software projects and maintain “credit” for their individual contributions to USGS products? [227]
External collaborators may add to a USGS software project that has been made accessible as an open-source development project on the USGS Git Hosting Platform. [Read More]
How is a USGS scientific software information product cited? [226] How is a USGS scientific software information product cited? [226]
As defined in SM 502.11, USGS scientific software information products may be cited; however, the corresponding software project may not be cited or referred to within another information product. [Read More]
How can I enforce a USGS policy on external collaborators? [225] How can I enforce a USGS policy on external collaborators? [225]
As the lead author on a USGS scientific software information product, it is your responsibility to ensure all Fundamental Science Practices (FSP) requirements are satisfied before publishing the code. Including a contributing file, “CONTRIBUTING.md,” in your software repository can make clear the conditions under which the USGS will accept contributions from external collaborators. [Read More]
How is legacy software handled under current USGS policy? [224] How is legacy software handled under current USGS policy? [224]
Legacy software (specifically, software created prior to the release of SM 502.11) may remain as-is so long as it remains compliant with the policies governing its original publication. If an updated publication of legacy software is desired, the software project must be updated to comply with current policy.
What happened to the previous concept of a provisional software release? [223] What happened to the previous concept of a provisional software release? [223]
Software projects that were previously released as provisional software under OSQI IM 2019-01 are now considered open-source software development projects under the authority of the USGS Open Source Software Requirements.
May I use publicly available, third-party code – possibly developed by an external collaborator – to conduct USGS research? [222] May I use publicly available, third-party code – possibly developed by an external collaborator – to conduct USGS research? [222]
Yes. Publicly available, third-party code may be used to support USGS research as specified in SM 502.11. [Read More]
How do I document a review for a scientific software information product in the Information Product Data System (IPDS)? [221] How do I document a review for a scientific software information product in the Information Product Data System (IPDS)? [221]
USGS scientific software information product review and reconciliation documents may be attached to an IPDS record to document the process. [Read More]
How can I make a software project available for review by external reviewers prior to releasing e USGS scientific software product? [220] How can I make a software project available for review by external reviewers prior to releasing e USGS scientific software product? [220]
Two options exist: First, the approved USGS hosting platforms support external collaborator accounts. Second, the software project may be made publicly accessible as an open-source software development project. [Read More]
When and how should scientific software information products be reviewed? [218] When and how should scientific software information products be reviewed? [218]
Scientific software information products may be reviewed incrementally as part of the development process or in aggregate just prior to becoming public. [Read More]
May scientific software information products be released without first being publicly accessible as an open-source software project? [216] May scientific software information products be released without first being publicly accessible as an open-source software project? [216]
Yes. Scientific software information products may be released either concurrent with- or subsequent to- the corresponding open-source software project being made publicly accessible. However, all requirements of Federal Policy must be satisfied when doing so. [Read More]
May custom-developed software projects be publicly accessible? [215] May custom-developed software projects be publicly accessible? [215]
Yes. USGS software projects may be made publicly available as open-source software projects (refer to the SHARE IT Act) but are not citable by other USGS products.
My custom-developed source code does not rise to the level of a scientific software information product. Do I need to release my code as a USGS Scientific Software Release following SM 502.11? [214] My custom-developed source code does not rise to the level of a scientific software information product. Do I need to release my code as a USGS Scientific Software Release following SM 502.11? [214]
No. However, most custom-developed source code is still governed by ACIO Open Source Software requirements, and the SHARE IT Act, which have their own release requirements (but are outside of the scope of SM 502.11). [Read more]
What is the foundation of FSP? [001] What is the foundation of FSP? [001]
A set of fundamental principals that underlie USGS science practices including how research activities are planned and conducted and how the results of these research activities are appropriately reviewed, approved, and released. [Read More]
What USGS scientific information products must follow FSP? [002] What USGS scientific information products must follow FSP? [002]
All USGS scientific information products must follow FSP if the author has full time, part time, or volunteer (including emeritus) USGS affiliation or a shared affiliation such as between USGS and a university. [Read More]
Are there any alternatives, exceptions or exclusions to following the FSP review and approval requirement? [003] Are there any alternatives, exceptions or exclusions to following the FSP review and approval requirement? [003]
No. FSP review and approval requirements must be followed for all publicly released USGS science information products. [Read More]
What are the basic FSP requirements for review, approval, and release of scientific information products? [004] What are the basic FSP requirements for review, approval, and release of scientific information products? [004]
Scientific information products generally receive peer review, data review, names review, editorial review, and policy review, which are followed by approval and release of the product. [Read More]
Where is guidance available on disclaimer statements used in USGS scientific information products? [005] Where is guidance available on disclaimer statements used in USGS scientific information products? [005]
A list of various disclaimers is available at the link provided with this FAQ. [Read More]
Where is guidance available regarding advocacy and recommendations in USGS information products? [006] Where is guidance available regarding advocacy and recommendations in USGS information products? [006]
Guidance on advocacy and recommendations is available at the link provided with this FAQ and includes examples of acceptable and unacceptable statements. [Read More]
Under what circumstances may "personal (written or oral) communications" be cited in scholarly publications? [007] Under what circumstances may "personal (written or oral) communications" be cited in scholarly publications? [007]
The use of written or oral communications is permitted when referring to auxiliary information that is not essential to ensuring others can replicate the results or evaluate the validity of the data used to support the conclusions of the scholarly publication. [Read More]
How are FSP and the Science Publishing Network (SPN) requirements related? [008] How are FSP and the Science Publishing Network (SPN) requirements related? [008]
FSP requires that USGS scientific information products conform with established USGS publishing requirements and procedures for production and release; the SPN is the Bureau’s organizational unit that is the sole source for providing publishing support services and related needs. [Read More]
Where is guidance available that explains the general FSP review and approval procedures and responsibilities for scientific information product development? [009] Where is guidance available that explains the general FSP review and approval procedures and responsibilities for scientific information product development? [009]
Available guidance includes procedures, charts, workflow diagrams, FAQs, and training modules. [Read More]