Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:80243 | Published / External
InPort now supports a dedicated Data Management Plan Catalog Item type, which is up-to-date with the latest NOAA DMP template. The ability to generate Data Management Plans from Data Sets will be discontinued in a future release. For more information, consult the help guides on the new Data Management Plan as well as how to convert this Legacy DMP to the new format.
Data Management Plan
DMP Template v2.0.1 (2015-01-01)
Please provide the following information, and submit to the NOAA DM Plan Repository.Reference to Master DM Plan (if applicable)
As stated in Section IV, Requirement 1.3, DM Plans may be hierarchical. If this DM Plan inherits provisions from a higher-level DM Plan already submitted to the Repository, then this more-specific Plan only needs to provide information that differs from what was provided in the Master DM Plan.
1. General Description of Data to be Managed
Common thresher shark EFH is defined using a combination of data sources described in the FMP as well as expert opinion. While common thresher sharks may occur in shallow water <12 m, they occur primarily in deeper waters, seaward of 12 m, and these shallow regions including enclosed bays and estuaries are not considered essential. Including all age classes, common thresher shark EFH includes the U.S. West Coast EEZ from the U.S.-Mexico border to the U.S.-Canada border, to approximately 100 nautical miles offshore, seaward of the 12 m depth contour. While small schooling fish appear to be their preferred prey, diets vary temporally and spatially and include squid and crustaceans. The high productivity and presence of diverse small schooling fish, squid and crustacean species and relatively warm shallow shelf waters make the California Current, out to approximately 100 nautical miles, a suitable habitat for feeding and growth to maturity for common thresher sharks.The Magnuson-Stevens Fishery Conservation and Management Act (MSA) requires that regional management councils describe EFH in their fishery management plans (FMPs), that they minimize to the extent practicable adverse effects on EFH from fishing activities, and that federal agencies consult with the National Marine Fisheries Service on activities that may adversely affect EFH, among other things. Actions that occur outside of EFH, but that may adversely affect EFH, also warrant an EFH consultation. EFH means those waters and substrate necessary to fish for spawning, breeding, feeding, or growth to maturity (50 CFR 600.10). FMPs must describe and identify EFH in text that clearly states the habitats or habitat types determined to be EFH for each life stage of the managed species, if possible. The text descriptions are ultimately determinative of the limits of EFH. Those text descriptions of HMS EFH can be found in the HMS FMP available on the Pacific Fishery Management Council (Council) website: https://www.pcouncil.org/. In addition, FMPs must include maps that display, within the constraints of available information, the geographic locations of EFH or the geographic boundaries within which EFH for each species and life stage is found (50 CFR 600.815(a)(1)(v)(A)). This Geographic Information System (GIS) data which depicts the EFH of HMS within the EEZ off the U.S. West Coast, was developed to meet that requirement.
Notes: Only a maximum of 4000 characters will be included.
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.
Notes: All time frames from all extent groups are included.
Notes: All geographic areas from all extent groups are included.
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
(e.g., satellite, airplane, unmanned aerial system, radar, weather station, moored buoy, research vessel, autonomous underwater vehicle, animal tagging, manual surveys, enforcement activities, numerical model, etc.)
2. Point of Contact for this Data Management Plan (author or maintainer)
Notes: The name of the Person of the most recent Support Role of type "Metadata Contact" is used. The support role must be in effect.
Notes: The name of the Organization of the most recent Support Role of type "Metadata Contact" is used. This field is required if applicable.
3. Responsible Party for Data Management
Program Managers, or their designee, shall be responsible for assuring the proper management of the data produced by their Program. Please indicate the responsible party below.
Notes: The name of the Person of the most recent Support Role of type "Data Steward" is used. The support role must be in effect.
4. Resources
Programs must identify resources within their own budget for managing the data they produce.
5. Data Lineage and Quality
NOAA has issued Information Quality Guidelines for ensuring and maximizing the quality, objectivity, utility, and integrity of information which it disseminates.
(describe or provide URL of description):
Lineage Statement:
HMS GIS data was developed using one or more of the following: 1) existing species distributions in the eastern North Pacific from published sources including the initial EFH descriptions, 2) expert opinion and 3) a review of fisheries data
GIS data used to guide and establish boundaries for EFH data creation include:
1) Western extent:
100 nm westward of the -12 meter contour depth line
(measurement conducted in GIS utilizing buffering geoprocessing tool)
2) Eastern extent:
A -12 meter contour depth was developed from NOAA's National Centers for Environmental Information (NCEI) Coastal Relief Models;
Vol. 6: Southern California (2003) Vol. 7: Central Pacific (2003) and Vol.8: Northwest Pacific (2003)
Data Source: Coastal Relief Model (CRM) - Download Date 8/2024
https://www.ncei.noaa.gov/products/coastal-relief-model
3) At the mouth of San Francisco Bay (for applicable HMS species in this area: Albacore Tuna, Blue Shark, Common thresher shark, Pacific bluefin tuna, Shortfin mako shark, Swordfish),
the COLREGS Demarcation Line was used as the eastern extent.
Data Source: Marine Cadastre
https://hub.marinecadastre.gov/datasets/eeec3469795243f7bf91861e00fb6f40_0/about
(describe or provide URL of description):
6. Data Documentation
The EDMC Data Documentation Procedural Directive requires that NOAA data be well documented, specifies the use of ISO 19115 and related standards for documentation of new data, and provides links to resources and tools for metadata creation and validation.
Missing/invalid information:
- 1.3. Is this a one-time data collection, or an ongoing series of measurements?
- 1.4. Actual or planned temporal coverage of the data
- 1.7. Data collection method(s)
- 4.1. Have resources for management of these data been identified?
- 4.2. Approximate percentage of the budget for these data devoted to data management
- 5.2. Quality control procedures employed
- 7.1. Do these data comply with the Data Access directive?
- 7.1.1. If data are not available or has limitations, has a Waiver been filed?
- 7.1.2. If there are limitations to data access, describe how data are protected
- 7.2. Name of organization of facility providing data access
- 7.2.1. If data hosting service is needed, please indicate
- 7.3. Data access methods or services offered
- 7.4. Approximate delay between data collection and dissemination
- 8.1. Actual or planned long-term data archive location
- 8.2. Data storage facility prior to being sent to an archive facility
- 8.3. Approximate delay between data collection and submission to an archive facility
- 8.4. How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?
(describe or provide URL of description):
7. Data Access
NAO 212-15 states that access to environmental data may only be restricted when distribution is explicitly limited by law, regulation, policy (such as those applicable to personally identifiable information or protected critical infrastructure information or proprietary trade information) or by security requirements. The EDMC Data Access Procedural Directive contains specific guidance, recommends the use of open-standard, interoperable, non-proprietary web services, provides information about resources and tools to enable data access, and includes a Waiver to be submitted to justify any approach other than full, unrestricted public access.
Notes: The name of the Organization of the most recent Support Role of type "Distributor" is used. The support role must be in effect. This information is not required if an approved access waiver exists for this data.
Notes: This field is required if a Distributor has not been specified.
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
Notes: This field is required if applicable.
8. Data Preservation and Protection
The NOAA Procedure for Scientific Records Appraisal and Archive Approval describes how to identify, appraise and decide what scientific records are to be preserved in a NOAA archive.
(Specify NCEI-MD, NCEI-CO, NCEI-NC, NCEI-MS, World Data Center (WDC) facility, Other, To Be Determined, Unable to Archive, or No Archiving Intended)
Notes: This field is required if archive location is World Data Center or Other.
Notes: This field is required if archive location is To Be Determined, Unable to Archive, or No Archiving Intended.
Long Beach, CA
Notes: Physical Location Organization, City and State are required, or a Location Description is required.
Discuss data back-up, disaster recovery/contingency planning, and off-site data storage relevant to the data collection
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.
