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
In May of 2006, scientists from the Alaska Fisheries Science Center
participated in a pilot outreach program in Sand Point, Alaska. At the meetings,
fishermen raised a number of concerns about the adequacy of walleye pollock
(Theragra chalcogramma) assessment. The issues appeared to be related to the contrasting
observational scales of fishermen and National Marine Fisheries Service (NMFS) scientists
responsible for conducting assessment surveys and population modeling. NMFS resource
assessment surveys have a large spatial scale (i.e., the entire Gulf of Alaska) and occur
infrequently as they are biennial summer bottom trawl and acoustic-trawl surveys, with annual
or biennial winter acoustic-trawl surveys targeting key spawning
areas(von Szalay, et al. 2010; Guttormsen and Yasenak, 2007; Guttormsen and Jones, 2010).
The stock assessment model for pollock estimates stock abundance for the central and western
Gulf of Alaska (Dorn et al., 2011). In contrast, the observational scale of fishermen is spatially
restricted but temporally extensive, since they are on the water fishing throughout the year.
Fishermen questioned whether NMFS assessment activities were appropriately designed
to monitor the status of pollock in their area. They noted that additional surveys
in different seasons and a more comprehensive acoustic-trawl survey effort in winter
could help address seasonal issues such as movement between spawning and feeding areas.
Cooperative research projects with the Sand Point fishing community were identified
as a potential approach for addressing some of these issues, but fishermen wanted
the assurance that their investment of time and effort will lead to improvements
in stock assessment. The acoustic-trawl surveys described in this report resulted
from collaboration between NMFS scientists, the Aleutian East Borough, and local
fishermen to address issues raised during the outreach program. Acoustic-trawl
surveys were conducted from a local fishing vessel in the western Gulf of Alaska
during 2007-2013. To some extent, the surveys carried out during this period reflected
shifting program objectives. The initial objective was simply to demonstrate the
feasibility of using local fishing vessels to conduct acoustic-trawl surveys and
to collect acoustic and biological information sufficient to estimate walleye pollock
biomass and spatial pattern. Once this was demonstrated, the focus of the project expanded
to include other objectives. Specific objectives of the project
were the following:
Evaluate the feasibility of conducting acoustic-trawl surveys
of pollock using local fishing vessels.
Evaluate the quality of acoustic data collected from the Simrad ES60 echosounder.
Evaluate the appropriateness of the design of the current NMFS acoustic-trawl surveys
in the western Gulf of Alaska. Specific issues to be addressed included 1) transect density
in bathymetrically complex regions in the western Gulf of Alaska, 2) day/night differences
in pollock density, and 3) temporal variability of pollock density during replicate transects.
Evaluate the timing of the NMFS survey (mid-February) in Sanak Trough
by conducting a survey in January prior to the NMFS survey.
Evaluate relationships between adult pollock density, young-of-the-year pollock density,
euphausiid density, and the distribution of foraging humpback whales (Megaptera novaeangliae).
The estimates of abundance and distribution of walleye pollock were developed for
areas covered by cooperative acoustic-trawl surveys conducted aboard a fishing vessel
during alternate Septembers and Januarys between 2007-2013. Physical oceanographic
and biological composition observations, initial findings from ancillary data collections
of marine mammal observations, and dual-frequency differencing techniques to discriminate
different types of acoustic backscatter were also developed.
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.
Shumagin Islands to Sanak Islands, AK
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.
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):
View metadata record as uploaded FGDC record.
(describe or provide URL of description):
See method in uploaded FGDC view.
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.
- 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.
The data set has been analyzed and is available for distribution. Contact the Point Of Contact.
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.
Contact point of contact.
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.