🐬
SA Metadata Creation Guide draft
  • Introduction
  • Roles & Responsibilities (draft)
  • Goals of SA Data Management
  • SA Science Metadata Catalog
  • Projects, Products, Contacts
  • Non Duplication Policy Guidance
  • Workflow
    • Metadata From Scratch
    • Metadata From ScienceBase
    • Metadata Editing / Re-Publishing
    • PTS Considerations
  • Settings
  • mdEditor Metadata File Management
    • Import
      • mdJSON
      • sbJSON
      • FGDC
    • Export
    • Copy Records
  • Metadata Requirements Checklist
  • Digital Object Identifier (DOI)
  • Project Entry Guidance
    • Main Tab: Project
    • Metadata Tab: Project
    • Keywords Tab: Project
    • Taxonomy Tab: Project
    • Extent Tab: Project
    • Documents Tab: Project
    • Funding Tab: Project
    • Associating Records: Project
  • Product Entry Guidance
    • Main Tab: Product
    • Metadata Tab: Product
      • data.gov Guidance
    • Keywords Tab: Product
    • Taxonomy Tab: Product
    • Extent Tab: Product
    • Lineage Tab: Product
    • Distribution Tab: Product
    • Constraints Tab: Product
    • Dictionaries Tab: Product
    • Documents Tab: Product
    • Associating Records: Product
  • Co-funded Project Requirements
    • Collaboration Protocol
    • Sub-Project Protocol
      • Sub-project of FWS Region or Program Project
      • Sub-project of CASC Project
    • Co-funded Protocol
      • FWS co-funded Projects
      • FWS/CASC Projects & Products
      • CASC Responsibilities
      • LCC Examples
  • Contact Entry Guidance
    • Summary Contact Requirements
    • Individual Contacts
    • Organization Contacts
  • Publish
    • Requirements for Publishing
    • Testing Publishing
    • How to Publish
    • Re-Publishing
  • Archiving Requirements
  • Trouble-shooting Tips
    • QA/QC Fixes
      • QA/QC Resources
  • Bulk Editing Resources
    • Injector Script: Funding
    • Injector Script: Distribution Links
  • Help
  • Glossary of Terms
  • Documentation Guide
Powered by GitBook
On this page
  • Non Duplication Policy
  • Guidance for Preventing Duplication of Research and Other Science Activities

Was this helpful?

Non Duplication Policy Guidance

PreviousProjects, Products, ContactsNextWorkflow

Last updated 3 years ago

Was this helpful?

Non Duplication Policy

Based on a 2017 OIG audit, minimal metadata fields are required to be published within 30-days of project funding. The purpose of this policy is to share information with partners regarding what science projects SA is supporting. This transparency helps to reduce duplication of efforts across funding agencies and allows partners to discover and engage in SA supported science as desired.

Quick Reference: Project metadata for Non Duplication Policy

Required

Basic Information: Title, Status

Required

Required

Description: Abstract

Required

Time Period

Required

Funding: Award Number, amount, source, fiscal year, recipients

Required

Below is a copy of the Non Duplication Policy guidance memo, in detail for reference:

Guidance for Preventing Duplication of Research and Other Science Activities

Background

On September 1, 2017, and December 7, 2017, the U.S. Fish and Wildlife Service (Service) issued memos detailing actions all Assistant Regional Directors, Science Applications (SA-ARDs), must take to prevent duplication of research across Science Applications and United States Geological Survey Climate Adaptation Science Centers (CASCs). This document provides further guidance for how to best comply with those memos, in addition to other measures that can be undertaken to prevent duplicative research across Science Applications, CASCs, and other federal programs. See this for a list of resources.

Summary of Required Actions

For all financial assistance and inter-/intra-agency agreements or contracts for research projects and other science activities you must do what is outlined in the list below. Unless otherwise specified, the following applies to all science projects funded with SA applications monies (1410, 1420, and 1430):

  1. First determine if the project is a research project or other science activity. Consider whether the project will result in a science product (e.g. survey, study, tool, assessment, publication, etc.).

a. If you decide that it IS NOT research or another type of other science activity, document your decision using and attach it to the official award file.

    1. If you decide that it IS research or another type of science activity, proceed with the steps outlined below.

  1. Add this language to the NOFO: ā€œApplicants must document literature searches (e.g. academic literature, industry publication, ScienceBase, and Data.gov). Applicants should explain why their project is non-duplicative and how it will augment existing knowledge.ā€

  2. Include peer review as part of project selection.

Required and Recommended Practices

As denoted by ā€œ(required)ā€ in the list below, only practices 2, 5, and 6 are required per policy; the others are recommended but are not required. Note: required actions are the same as those listed above in the Summary of Required Actions. Unless otherwise specified, the following applies to all science projects funded with SA applications monies (1410, 1420, and 1430).

1. Determine if the project is a research project or other science activity (required). Consider whether the project will result in a science product (e.g. survey, study, tool, assessment, publication, etc.).

    1. If you decide that it IS research or another type of science activity, proceed with the steps outlined below.

2. Consider coordinating with other federal agencies prior to the project funding phase:

    1. You may consult informally during project development, or, when appropriate, invite staff from CASCs and other federal programs to be peer reviewers.

    2. When invited and able, consider participating in the project development and selection phases for other agencies’ research programs.

  1. Search ScienceBase.gov for potentially duplicative projects prior to funding (required):

    1. Do multiple searches (i.e. varying search terms and criteria) as necessary.

    2. Be expansive in your search – use a variety of search terms and limit the scope only as necessary. You should not limit your search to CASC communities.

  1. Insert this language in NOFO: ā€œApplicants must document literature searchers (e.g. academic literature, industry publication, ScienceBase, and Data.gov). Applicants should explain why their project is non-duplicative and how it will augment existing knowledge.ā€(required)

  2. Consult with CASCs once you have selected a project to fund, but prior to funding. Email Anna-Marie_York@fws.gov to obtain a link to a form to send to CASC directors (required).

    1. Use the results of ScienceBase searches, informal consultations, and/or serving on review panels to identify CASCs that have funded similar research. You may also consider any CASC in your project geography. Aim to be expansive.

    2. Consider sending the form to leadership from other federal agencies as well.

    3. Include a copy of the responses (spreadsheet) in the financial award file.

ScienceBase Guidance

    1. Title

    2. PI/funding recipient’s[1] name and contact info,

    3. PI/Funding recipient’s organization,

    4. start date,

    5. projected end date,

    6. abstract,

    7. award ID,

    8. funding sources and amounts.

  1. If you have a science activity that more than one FWS region contributed funds to, but there was a ā€œlead regionā€ that actually administered a single financial award / contract, then that lead region should create and maintain a single record in ScienceBase for the project and its products. The project record should list the total amount of Service funds in the financial / award contract (i.e., all regions combined).

  2. If you have a science activity with multiple financial awards / contracts, then each award / contract should have its own ScienceBase record (note: modifications ARE NOT considered new awards / contracts). Whichever region administered each financial award / contract should create and maintain project and product records in ScienceBase. Please include the ScienceBase URL(s) for the related projects in the abstract. Example language: ā€œthis project is part of a larger initiative; you can find related records here: URL 1, URL 2, ā€¦ā€).

[1] The memo itself uses the term ā€œproject leaderā€ instead of PI/funding recipient.

Point of Contacts (see )

2. Search for duplicative projects in ScienceBase (use the ).

You must document consultation with the appropriate CASC director(s). Send an email to Anna-Marie York () to obtain an electronic form to document consultation with CASC directors. The form link can be shared with anyone in the Department of the Interior and offers the ability to create a spreadsheet that summarizes responses, including a time stamp for when each respondent completed the form.

After consultation with CASCs is complete, the SA-ARD must provide a memo to the file () certifying that consultation occurred. (Note: for grants and cooperative agreements the ARD may instead certify consultation was done by checking the appropriate box and signing the New Award Checklist - FWS Form 3-2460). Include a copy of the spreadsheet of responses as part of the official award file.

7. Enter all project information into ScienceBase as soon as possible, but within 30 days of the agreement being in place (required per ). Provide as much information about projects as possible and update regularly, including adding entries for products within 30 days of receipt. See the ScienceBase Guidance section below for further details.

a. If you decide that it IS NOT research or another type of other science activity, document your decision using and attach it to the official award file (required).

a. Document your search of ScienceBase using the .

d. Include copies of and corresponding results (spreadsheet) in the financial award file.

1. Repeat Practice 2 at and any other relevant federal databases. You can use the to document these searches, though note that some of the instructions on the template are specific to ScienceBase.

Using google forms will allow us to download a spreadsheet of time-stamped responses. Email for a copy of the resulting spreadsheet.

After consultation with CASCs is complete, the SA-ARD must provide a memo to the file () certifying that consultation occurred. (Note: for grants and cooperative agreements the ARD may instead certify consultation was done by checking the appropriate box and signing the New Award Checklist - FWS Form 3-2460). Include a copy of the spreadsheet of responses as part of the official award file.

1. Enter all project information into ScienceBase as soon as possible, but within 30 days of the agreement being in place (required per ). Provide as much information about projects as possible and update regularly, including adding entries for products within 30 days of receipt. See the ScienceBase Guidance section below for further details.

to put basic information about the science projects you have funded since September 30, 2017; per policy this is required within 30 days of funding a project or receiving a product. Here is what’s required for each project/product:

You can use mdEditor to make the records if that is your preference, or do it directly in ScienceBase. Here is a showing how to enter directly on ScienceBase.

If you need ā€œeditingā€ access to your region’s ...email Jill ().

If you want a little more detail about what the ā€œScienceBaseā€ policy is…Start with Jill gave to the Data Management Working Group August 2018.

If you want all the details about the non-duplication policies... is your gateway.

If you read through the slides and other documents and still have questions, or just want to check to make sure you’re doing things right...Call or email Jill (; 703.358.1764).

dashboard
this template
ScienceBase search template
Anna-Marie_York@fws.gov
template here
September 2017 memo
this template
ScienceBase search template
ScienceBase search template
https://catalog.data.gov
ScienceBase search template
Anna_Marie_York@fws.gov
template here
September 2017 memo
Every region has folders in ScienceBase
video tutorial
ScienceBase folder
jillian_cohen@fws.gov
slides from a presentation
This dashboard
jillian_cohen@fws.gov
Main Tab: Project