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
Diel epipelagic sampling for juvenile Pacific salmon (Oncorhynchus spp.), rockfish (Sebastes spp.), sablefish (Anoplopoma fimbria), and associated species was conducted in order to identify factors that may affect year-class success of these commercially important species. Sampling occurred in offshore marine habitats of the coastal northeast Pacific Ocean from 10-20 August 2005 and was conducted with a surface trawl fishing the upper 20 m of the water column along transects up to78 km offshore near 58 N. Three habitats were sampled along each transect over a 24-hr period: the continental shelf (<200 m depth), the continental slope (400-750 m depth), and the abyss (>2,000 m depth). A total of 38,747 fish and squid representing 24 species were sampled in 56 trawl hauls. Of the targeted juvenile fish species, a total of 587 salmon, 11 rockfish, and 70 sablefish were captured. Sampling during day (1500-1900) and night (2200-0200) periods indicated that biomass of fish and squid was 2-4 times higher at night at (each?)all habitat types pooled across transects. No distinct patterns between day or night occurrence were noted for juvenile pink salmon (O. gorbuscha), chum salmon (O. keta), sockeye salmon (O. nerka), or coho salmon (O. kisutch), however, juvenile Chinook salmon (O. tshawytscha) were encountered only at night. Catches of juvenile rockfish and juvenile sablefish were quite low in this study, and larger sample sizes of these fish are needed to adequately determine their diel distribution. Diel differences were apparent with forage species such as Pacific herring (Clupea pallasi), capelin (Mallotus villosus), and eulachon (Thaleichthys pacificus) that were almost exclusively sampled at night. The offshore distribution patterns of target species were distinctly different, with the most common occurrences of juvenile salmon over continental shelf habitats, juvenile sablefish over continental shelf and slope habitats, and juvenile rockfish over slope and abyss habitats. Pacific herring, capelin, eulachon, and Pacific sardines (Sardinops sagax) were found over continental shelf habitats, whereas small squid and myctophids occurred primarily at slope and abyssal habitats. The greatest overall catch biomass was of gelatinous species (jellyfish), which was consistently higher than that of all fish and squid combined, usually by an order of magnitude. Individual fish or squid species with highest average weight per haul were pomfret (Brama japonica), adult coho salmon, Humboldt squid (Dosidicus gigas), and blue sharks (Prionace glauca). The occurrence of the latter two warm-water species and Pacific sardines were of interest because this study occurred during an anomalously warm year and the capture of Pacific sardines and Humboldt squid represent northern range extensions for these species. Stomach content analysis of potential predator species of the target species showed that only adult coho salmon were predating on juvenile salmon and sablefish, and only pomfret were predating on juvenile rockfish. Further sampling of the target species is needed in these habitats during more normal environmental conditions to validate these observations.
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.
Gulf of Alaska
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):
For methodology see: Orsi, J. A., D. M. Clausen, A. C. Wertheimer, D. L. Courtney, and J. E. Pohl. 2006. Diel Epipelagic Distribution of Juvenile Salmon, Rockfish, Sablefish and Ecological Interactions with Associated Species in Offshore Habitats of the Northeast Pacific Ocean (NPAFC Doc. 956) Auke Bay Lab., Alaska Fish. Sci. Cen., Nat. Mar. Fish. Serv., NOAA, 11305 Glacier Highway, Juneau, AK 99801-8626, USA, 26 p.
- Contact POC for methodology
(describe or provide URL of description):
Contact the dataset POC for full QA/QC methodology
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)
- 7.2. Name of organization of facility providing data access
(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.
Contact the Point of Contact for data request form.
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.
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.