🐬
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
  • Use Limitation
  • Legal
  • Security Constraints

Was this helpful?

  1. Product Entry Guidance

Constraints Tab: Product

THIS SECTION IS UNDER REVIEW FOR FOIA, RECORDS MANAGEMENT, AND PRIVACY POLICY GUIDANCE; MAJOR CHANGES ARE FORTHCOMING.

PreviousDistribution Tab: ProductNextDictionaries Tab: Product

Last updated 4 years ago

Was this helpful?

The Constraint tab allows you to enter information into the metadata about how the resource can and cannot be used.

Quick Reference: Product Constraints Tab

Required?

Use Limitation

Optional

Legal

Required

Security Constraints

Best Practice

Use Limitation

Identify concerns over how people should or should not use the product.

If your product is licensed, let people know here. Typically files used will be public domain, but not always.

Legal

  • Access Constraints: Access constraints are applied to assure the protection of privacy or intellectual property and any special restrictions or limitations on obtaining the resource.

  • Use constraints: How the product should be used.

  • Other constraints: This is a place to put standard disclaimers.

Access Constraints are limited to Open, Limited Access, Sensitive/Protected, and Restricted

Open Access

http://www.usa.gov/publicdomain/label/1.0/
https://creativecommons.org/publicdomain/zero/1.0/

Limited Access

Sensitive/Protected Access

Restricted Access

Security Constraints

A place to describe constraints or restrictions pertaining to security of the resource. Choose classification from the drop-down menu. For products without restrictions, best practice is to indicate 'unclassified' from the security classification dropdown menu.

Classification is the class of security (e.g., top secret, public access).

Data and content created by government employees within the scope of their employment are not subject to domestic copyright protection under . Government works are by default in the U.S. Public Domain. If no other open license applies, the following URL should be used in the license field.

The default U.S. Public Domain status of U.S. Government Works is limited to the jurisdiction of the United States. A public domain status is applicable internationally for works produced by government employees, by using a worldwide public domain dedication such as . This assures users of U.S. Government Works that they have full permission to freely use the work internationally. When Creative Commons Zero has been applied, the following URL should be used for in the license field.

17 U.S.C. § 105
Creative Commons Zero
Example legal constraint entry for U.S. Government Works open license