Fundamental Science Practices Frequently Asked Questions

Yes. USGS scientific software information products must be assigned a DOI with the 10.5066 prefix. [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 original reference copy of all USGS scientific software information products must be maintained on an approved platform. As of the writing of this FAQ, these the two platforms options were (1) https://code.usgs.gov/ or (2) https://github.com/doi-usgs/. [Read more]

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]

Restricted-File Federal Interagency Reports (RFFIRs) are not public and cannot be cited, it may be worthwhile to publicly release these reports in other USGS series, such as Open File Report (OFR), once deemed appropriate to do so. A new IPDS record for OFR should be created, following the standard process for review, approval, and coordination with the Science Publishing Network. [Read more]

Restricted-File Federal Interagency Reports (RFFIRs) are not to be referenced, posted, or indexed on USGS public-facing web pages or included in a list of publications on individual staff profile pages. Because RFFIRs are not citable, they are not to be indexed in the USGS Publications Warehouse or included in a list of publications on individual staff profile pages.

The Restricted-File Federal Interagency Reports (RFFIR) series is to be used for confidential communication between USGS and a U.S. Government agency, foreign government or agency, or international entity funding partner. RFFIRs cannot be produced for private communications. [Read more]

Project progress reporting can involve noninterpretive scientific information, previously published interpretive scientific information, or new interpretive scientific. The type of content dictates how the FSP apply and whether tracking in the IPDS is required. [Read more]

Reports of project progress that contain non-interpretive or previously published interpretive information can be delivered in slides, summaries, correspondence, emails, or oral communications; conversely, new interpretive content must be tracked in IPDS and may include: (1) abstract, poster, presentation, exhibit, newsletter, (2) USGS publication series product, or (3) outside publication. [Read...

No. There is not a product type in the IPDS for reports of project progress.

Project progress reports with new interpretive information must include disclaimers indicating preliminary/provisional, deliberative, predecisional nature of information; requirement to not disclose or release information; and waiving of USGS and U.S. Government liability. These reports must be labeled “Preliminary Information Subject to Revision. Not for Citation or Distribution." [Read more]

If the project progress reports contain new interpretations, then the reports of project progress also require peer reviews, Bureau approval, and publication before being delivered to the greater community of stakeholders, steering councils, or cooperating groups who are not directly contributing to project activities. [Read more]

FSP review and approval of project progress depends on the content (new and interpretive findings versus noninterpretive or previously published information) and intended distribution of the report. [Read more]

Reports of project progress may be presented at a scientific conference, but sensitive, confidential, or proprietary information cannot be discussed. Peer review is at the discretion of the Science Center Director. FSP requirements for presentation materials that are left or not left at scientific meetings and conferences apply.

Reports of project progress are not related to the collaborator/partner courtesy reviews. While both types of reporting may contain new, interpretive content, a progress report discusses the status of project work and a draft of a final project report provided to collaborators for courtesy review discusses the results of the project. [Read more]

A nonendorsement disclaimer statement, if appropriate, is the only statement that may be needed in a report of project progress that is noninterpretive or that includes interpretations only from previously published sources. Note, however, that published sources must always be cited.