Data Management Plan
GUID: gov.noaa.nmfs.inport:39578 | Published / External
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
The National Marine Sanctuary Program (NMSP) updates and revises the management plans for each of its 13 sanctuaries. This process, which is open to the public, enables each site to revisit the reasons for sanctuary designation and assess whether they are meeting their goals, as well as to set new goals consistent with the mandates of the National Marine Sanctuaries Act. Issues raised by the public during this process are evaluated and a determination is made as to whether they will be incorporated into the updated plan. Many of these issues focus on topics such as the implementation of marine zoning or sanctuary boundary adjustments, both of which require information on the distribution of resources within and around the sanctuary. Recognizing this, NMSP and NOAA's National Centers for Coastal Ocean Science (NCCOS) formalized an agreement to collaborate in the revision process by developing such information through a series of biogeographic assessments conducted in selected sanctuaries. The resulting products are then supplied to sanctuary managers and staff for use in the policy and decision making process. This collaborative effort began along the west coast of the U.S. with the Cordell Bank, Gulf of Farallones, and Monterey Bay national marine sanctuaries, and is herein centered on the Channel Islands National Marine Sanctuary (CINMS).
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):
Process Steps:
- 2005-01-01 00:00:00 - The substrate data ranges from Washington to the U.S.-Mexico border (32o-48.5o latitude) and from 50-200 km from the shoreline (excluding estuaries). Benthic substrate data for California encompasses nearly 165,000 km2 of the continental shelf and slope and are classified into approximately 33 different habitat types. The level of spatial resolution varies across the dataset based on the quantity and quality of the original data sources used to construct this substrate map. As such, fine scale inaccuracies may exist throughout the range of the data. In addition to assessing the distribution of substrate types throughout the southern California region, the map was used as an input for deterministic habitat suitability models (HSM) for a select group of fishes and invertebrates. Linking the 33 classes of habitat types to species life history information from scientificliterature was difficult; thus, a separate substrate attribute was used for habitat suitability modeling which defined the substrate as either hard or soft. Model results for invertebrates were reviewed in June 2004 by a panel of experts. They expressed concern that the map underestimated the amount of hard bottom, most notably at depths between 0-30 m along the mainland south of Point Conception and around the Channel Islands. Additionalhard substrate data were then provided by scientists from UCSB who converted non-digital substrate maps developed by the Minerals Management Service (MMS) into a format suitable for use within a GIS. These data extend from Morro Bay to the U.S.-Mexico border and were combined with the NMFS substrate data, resulting in a better estimation of hard substrate in southern California. (Citation: Moss Landing Marine Laboratory - Substrate data)
(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.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.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.
None
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.
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.