Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:28210 | 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
The eastern Bering Sea has experienced rapid and intensive development of commercial trawl fisheries. Because of good record keeping and the relatively brief history of fishing it is possible to reconstruct the spatial and temporal patterns of exploitation. Previously unfished (UF) areas can be identified and directly compared with heavily fished (HF) areas to investigate long-term consequences for the benthos. Using this approach, macrofauna populations in a shallow (48 m average) soft-bottom area were studied during 1996.
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:
- Macrofauna sampling was conducted aboard two identical 40 m chartered stern trawlers, the sister ships FV ??Aldebaran?? and FV ??Arcturus??. Each is powered by a 1525 hp main engine and fitted with a variable pitch propeller and propeller nozzle. Macrofauna were sampled with identical 83?112 eastern otter trawls, selected to ensure relatively large samples of patchily distributed organisms and to minimize clogging of the opening by large macrofauna (e.g. sea stars). These nets have a 25.3 m headrope and a 34.1 m footrope and have been the standard sampling gear used for annual NMFS groundfish-crab surveys in the EBS since 1982. The trawl was towed behind 1000 kg steel V-doors and 54.9 m paired dandylines. Each lower dandyline has a 0.61 m chain extension connected to the lower wing edge to improve bottom-tending characteristics. For this study, the standard trawl was modified to improve catchability and retention of macrofauna. It was equipped with a tickler chain and a hula skirt, and had a 3.8 cm liner covering both wings and the entire bottom body, with complete coverage top and bottom of the intermediate and codend. An acoustic net mensuration system and a mechanical bottom contact sensor were used to assess net configuration and collect performance data for area-swept and catch-per-uniteffort (c.p.u.e.) calculations. Each vessel sampled adjoining HF-UF stations (??pairs??) by towing the trawl through the centre of a 1 nm2 cell for 1.39 km (i.e., 3 knots for 15 min). Catches were fully processed in the field by sorting macrofauna to the lowest possible taxon and then weighed and enumerated separately. Weights were determined using a motion-compensated precision electronic balance. Biogenic substrate, such as empty gastropod and bivalve shells, and identifiable egg masses were also weighed, so as to provide a more complete characterization of the benthos. Prior to analysis, catch data were lumped into larger taxonomic groups to resolve classification differences between the vessels and to reduce the number of dependent variables. Bottom trawl catches (CPUE)are standardized according to area swept, as determined with Scanmar ascoustic system and GPS coordinates of vessel. Catch values are weights of organisms/hectare.
- Data were entered into a spreadsheet and converted to point features in ArcGIS.
- 1996-08-01 00:00:00 - Point features were converted to line features based on feature and vertex ID to represent the starting and ending locations of each trawl deployment. Catch and other environmental data, such as depth and temperature, were then spatially joined to each line segment based on a key field identifier from the original data.
(describe or provide URL of description):
see 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.