🐬
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
  • Co-funded Protocol
  • When a CASC project is co-funded with the Service:
  • When a CASC product is co-funded with the Service:
  • Sub-Project Protocol
  • If a CASC project is a sub-project of a Service project:

Was this helpful?

  1. Co-funded Project Requirements
  2. Co-funded Protocol

CASC Responsibilities

PreviousFWS/CASC Projects & ProductsNextLCC Examples

Last updated 3 years ago

Was this helpful?

The CASCs will complete the following metadata responsibilities for the CASC records for co-funded projects and products, after being notified that a Service metadata record has been created with associations to the CASC ScienceBase records.

Co-funded Protocol

When a CASC project is co-funded with the Service:

CASC will add the following statement to the Summary in the CASC ScienceBase record:

  • “This project was co-funded by the [X, Y, Z] Climate Adaptation Science Centers and the USFWS [A, B, C] region program. An alternate reference to this project can be found here[insert SA ScienceBase URL].”

Example: “This project was co-funded by the South Central Climate Adaptation Science Center and the USFWS Gulf Coast Region. An alternate reference to this project can be found .”

The Service will include a parallel statement in the Summary field for their ScienceBase record, link back to the CASC record, and create the association in ScienceBase.

When a CASC product is co-funded with the Service:

CASC will add the following text to the Summary in the CASC ScienceBase record:

“This product was co-funded by USFWS [A, B, C] region and the [X, Y, Z] Climate Adaptation Science Centers. An alternate reference to this product can be found here[insert SA ScienceBase URL].”

Example: “This project was co-funded by USFWS Gulf Coast Region and the South Central Climate Adaptation Science Center. An alternate reference to this product can be found .”

The Service will include a parallel statement in the Summary field for their ScienceBase record, link back to the CASC record, and create the association in ScienceBase.

Sub-Project Protocol

If a CASC project is a sub-project of a Service project:

  1. Add the following text to the Summary in the CASC ScienceBase record: “This project is a sub-project of USFWS [X] region project described here[insert LCC ScienceBase URL].”

  2. Add the association in ScienceBase as a “subprojectOf” the SA metadata record.

here
here