Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:28408 | 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 (Theragra chalcogramma) abundance and distribution in midwater were assessed between 9 June and 7 August 2009 using acoustic-trawl techniques aboard the NOAA ship Oscar Dyson. The survey also assessed walleye pollock in the Cape Navarin area of Russia. Results showed that ocean conditions were cold in 2009, as in the previous three years, compared to 2001-2005. Fewer pollock were observed east of 170¿W than in 2008, and a larger percentage of those were inside the Steller sea lion Conservation Area (SCA) than outside the SCA (79% in 2009, 70% in 2008). The majority of the pollock biomass in the U.S. Exclusive Economic Zone (EEZ) was located to the west and northwest of the Pribilof Islands between the 100 m and 200 m isobaths. Estimated pollock abundance in midwater (between 16 m from the surface and 3 m off bottom) in the U.S. EEZ portion of the Bering Sea shelf was 8.08 billion fish weighing 0.924 million metric tons (t); in the Russian EEZ, there were 9.67 million fish weighing 0.005 million t (0.6% of the total midwater biomass). East of 170¿W, (9.6% of total biomass) the predominant length mode was 55 cm both inside and outside of the SCA. In the U.S. west of 170¿W (89.8% of total biomass) dominant modal lengths were 13, 31, and 23 cm, respectively. In Russia, modal lengths were 43, 51, and 29 cm, with proportionally more adults and fewer juveniles than in the adjacent western U.S. EEZ. Age results indicated that inside the U.S. EEZ, juvenile walleye pollock (ages-1, -2, and -3) were dominant numerically (64%, 10%, and 21%, respectively) and represented 63% of the total biomass. Adult pollock (ages 4+) totaled 6% of the population numerically and 37% of the total biomass. Vertical distribution analyses indicated that 93% of adult biomass was within 40 m of the seafloor. Juveniles were found both near the seafloor and higher in the water column; 17% of juvenile biomass was within 50 m of the surface. Three dimensional size and shape patterns of the juveniles are described using data collected with a calibrated multibeam sonar, and variability in these patterns are explored as a function of ontogeny. Finally, a new euphausiid index of abundance computed from backscatter at 4 frequencies (18, 38, 120, and 200 kHz) is described.
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.