Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:27874 | Published / External
This is an outdated version of the NOAA Data Management Plan template. 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. Please see the Data Management Plan Help Guide to learn more.
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
Benthic communities are structured by dynamically interacting factors that determine habitat quality. Since benthic macrofauna demonstrate strong and often narrowly defined affinities, forces altering (or disturbing) the environment will be of considerable importance to their distribution and abundance. Commercial fishing with mobile gear, such as bottom trawls and dredges, and the physical disturbance that results, is widespread in continental shelf areas. Because of its prevalence and the potential for adverse effects, there have been numerous attempts to quantify sea-floor exposure at various spatial scales. The well documented development of commerical fisheries in the eastern Bering Sea (EBS) since 1954 presents a unique opportunity for studying trawling impacts. The Crab and Halibut Protection Zone 1 (CHPZ1; also known as management area 512), located north of the Alaska Peninsula in Bristol Bay, has a long and complex history of trawl prohibitions that extend from 1959 to the present. Using detailed accounts of closures and fishing activity, it is possible to reconstruct historical effort and identify essentially pristine areas immediately adjacent to areas that have been heavily fished with bottom trawls. This physical arrangement permits an examination of chronic disturbance by bottom trawls, without confounding environmental effects that result from geographic separation. Sampling locations were preselected on the basis of historical fish effort. Starting positions for commercial bottom trawls (n=392 743 through July 1996) were spatially joined with a 1 nm2 grid to calculate total number of trawls per nm2, and thus identify heavily fished (HF) and unfished (UF) areas along the boundary of the CHPZ1 (NORPAC fishery observer database maintained at the NMFS Alaska Fisheries ScienceCenter, Seattle, Washington). HF and UF cells on opposite sides of the boundary line were paired a priori on the basis of spatial proximity and were generally separated by 1 nm to allow for prior navigational discrepancies. A total of 42 pairs was identified at the northeastern corner of the CHPZ1. In 1997, 54 grab samples were obtained using a 0.05 m^2 Sutar van Veen (SvV) sampler deployed from the FV Golden Dawn at many, but not all, of the paired sites in the sandy, high-current northeast corner of management area 512. An additional 28 grabs were acquired in the central region of management area 512 as part of a completely different BACI project while sampling protocols were being ironed out in the early stages of the effort. This point file contains the weights (g) of various infauna obtained from 83 grab samples.
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:
- Ship targeted the center of a 1nm trawl block and stopped to deploy Sutar van Veen sampler
- 1997-08-09 00:00:00 - Infauna samples were sieved through 1 mm mesh and the invertebrates were fixed in buffered formalin, stained, and transferred to 50% isopropyl alcohol prior to sending to the University of Alaska Fairbanks.
- 1999-04-20 00:00:00 - Laboratory processing followed a priority listing provided to UAF by the AFSC. Processing each infauna sample included identification to at least the family level of taxonomy, counting, and wet weighing (blotted dry). The 1990 NODC code was used for all taxonomic data. All data was entered onto a PC computer and 100 percent verified.
- 2009-01-01 00:00:00 - Excel file was converted to text file and data were imported into ArcGIS as point features.
(describe or provide URL of description):
see Abstract, process steps
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)
(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.
unknown
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
IT Security and Contingency Plan for the system establishes procedures and applies to the functions, operations, and resources necessary to recover and restore data as hosted in the Western Regional Support Center in Seattle, Washington, following a disruption.
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.