Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:28313 | 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
Eastern Bering Sea shelf walleye pollock (Gadus chalcogrammus) midwater abundance and distribution were assessed from Bristol Bay in the United States, to Cape Navarin, Russia, between 12 June and 13 August 2014 using acoustic-trawl survey methods aboard the NOAA ship Oscar Dyson. Water column temperatures were warm in 2014 compared with the cold temperatures of the past several survey years (2006-2012). Most walleye pollock biomass was distributed relatively evenly across the shelf from a region north of Unimak Island to Navarin Canyon, between roughly the 50 m and 1,000 m isobaths. Estimated pollock biomass in midwater (between 16 m from the sea surface and 3 m off bottom) in the U.S. EEZ portion of the Bering Sea shelf was 3.439 million metric tons (t), nearly twice the 2012 estimate (1.843 million t) and the highest that has been observed since 2002. Pollock biomass east of 170° W was 1.425 million t (40% of the total shelf-wide), with 2-year-old pollock (26 cm modal fork length (FL)) comprising 55% of that biomass. Pollock biomass in U.S. waters west of 170° W was 2.013 million t (57% of total shelf-wide biomass), consisting primarily of pollock aged 1, 2, and 4-6 years (15, 26, and 38 cm dominant modal FL, respectively). Two-year-old pollock were more abundant east than west of 170° W and contributed to an eastward shift in distribution of U.S. pollock biomass compared with recent years. Estimated numbers of 2-year-old pollock also surpassed the numbers estimated for the strong 2008 year class in 2010, although the 2008 year class was still evident in the population. In Russia (104 thousand t, 3% of total biomass), primarily 4-year-old fish (38 cm modal FL), were observed, with proportionally fewer 1- and 2-year-olds than observed west of 170° W in the United States. The preliminary spatial distribution of euphausiid backscatter is presented, but analyses are still in progress
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.
Bering Sea: http://www.marineregions.org/gazetteer.php?p=details&id=4310
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:
Acoustic data were recorded at the five split-beam frequencies using ER60 software and, as a backup, acoustic telegram data were logged with Myriax EchoLog 500 software. Acoustic measurements were collected from 16 m below the sea surface to within 0.5 m of the sounder-detected bottom or a maximum of 1,000 m in deep water. Data were analyzed using Myriax Echoview post-processing software. See National Marine Fisheries Service (NMFS) 2013. NOAA protocols for fisheries acoustics surveys and related sampling (Alaska Fisheries Science Center), 23 p. Prepared by Midwater Assessment and Conservation Engineering Program, Alaska Fish. Sci. Center, Natl. Mar. Fish. Serv., NOAA. Available online: http://www.afsc.noaa.gov/RACE/midwater/AFSC%20AT%20Survey%20Protocols_Feb%202013.pdf
(describe or provide URL of description):
These data were collected in accordance NOAA protocols for fisheries acoustics surveys and related sampling (Alaska Fisheries Science Center), 23 p. Prepared by Midwater Assessment and Conservation Engineering Program, Alaska Fish. Sci. Center, Natl. Mar. Fish. Serv., NOAA. Available online: http://www.afsc.noaa.gov/RACE/midwater/AFSC%20AT%20Survey%20Protocols_Feb%202013.pdf
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)
- 7.2.1. If data hosting service is needed, please indicate
(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.
Go to https://www.ngdc.noaa.gov/mgg/wcd/ or email Anderson, Charles (charles.anderson@noaa.gov)
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.