🐬
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
  • Main/Points of Contact
  • Main/Abstract
  • Metadata/Metadata Contacts
  • Associated
  • Associations in mdEditor
  • Associations in ScienceBase

Was this helpful?

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

Sub-project of CASC Project

PreviousSub-project of FWS Region or Program ProjectNextCo-funded Protocol

Last updated 4 years ago

Was this helpful?

USGS CASC have their own metadata requirements. If your project is a sub-project of a CASC project, complete a unique metadata record with the following requirements. Products of a sub-project can be entered as described in .

If the SA and CASC contributions cannot be teased apart into project and sub-project, then follow the instead.

Main/Points of Contact

Add the CASC as a “collaborator.”

Main/Abstract

Add the following text as the last sentence:

“This project is a sub-project of the [X] Climate Adaptation Science Center project described here [insert hyperlink to CASC ScienceBase URL].”

  • Example: “This project is a sub-project of the South Central Climate Adaptation Science Center project described here.”

Metadata/Metadata Contacts

Default is USFWS, if Service is lead on the project, as “publisher.”

Collaborating CASCs do not need to be listed here.

Associated

Since the CASC metadata is outside the SA communities in ScienceBase, you must manually associate the CASC projects both in the mdEditor Associated tab and directly in ScienceBase.

Associations in mdEditor

Manually associate the CASC project as a “subProject” relationship in the Associated tab.

  1. Populate the association type as “subProject”.

  2. Enter the appropriate resource type.

  3. Copy the CASC’s project title to the title field.

  4. Enter the CASC as the “administrator” in the Responsible Parties section.

  5. Add the CASC ScienceBase item URL in the Online Resource field. This is important to provide discovery and access to items outside of the SA Science Catalog.

  6. Add the ScienceBase Identifier of the CASC project.

The CASC associated items will not appear in the Science Catalog as standalone items, but will appear as links in SA records in the Science Catalog. The assumption here is that the sub-project metadata contains all SA-relevant information and contributions and the CASC project record is essentially not needed.

Associations in ScienceBase

The only associations that ScienceBase currently recognizes from mdJSON are parentProject/product relationships. ScienceBase will not recognize the “subProject” association created in mdEditor, so this association must be added directly in ScienceBase.

  1. Log in to your ScienceBase account to edit the appropriate ScienceBase item.

  2. Click “Associate an Item” from the right side column of the ScienceBase page.

  3. Add a “subprojectOf” association to the CASC ScienceBase item.

Product Entry Guidance
co-funded protocol