🐬
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
  • Applicability
  • Metadata Responsibility
  • Funding/Other Contacts

Was this helpful?

  1. Co-funded Project Requirements

Collaboration Protocol

PreviousCo-funded Project RequirementsNextSub-Project Protocol

Last updated 4 years ago

Was this helpful?

Applicability

Refer to this protocol if:

  • Multiple regions, programs, etc. collaborate on a single project where only one region provided funding (this funding region is the lead). There can only be one lead region per project.

Metadata Responsibility

The lead region data manager is responsible for project and product metadata. There should only be one metadata record for each collaborating project and product. These records will publish and be searchable in the Science Catalog for each collaborating regions identified in the metadata.

If the project is collaborative between multiple regions but neither provides direct funding allocations, the regions should determine who will be the lead region and be responsible for entering the metadata.

In addition to metadata requirements described in , enter the following for projects with multiple Service regional or program collaborators:

Funding/Other Contacts

Include the lead region and/or program in other funding Contacts as 'administrator' (see ).

Project Entry Guidance
Contact Entry Guidance