Data Management Plan
GUID: gov.noaa.nmfs.inport:17088 | Published / External
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 cruise began when the ship departed Dutch Harbor on October 1, 2011 at 1500 ADT. Sampling commenced at collection site 1E, which corresponds to Station 1. Station number reflects the order of site occupation (see Cruise Report Table 1, Figures 1 and 2). All but one of the Semidi grid sites were successfully occupied by 10 October. Site 2B was not occupied successfully because the midwater trawl was torn by bottom contact and we chose to forgo sampling there in favor of running to the next station while the deck crew removed the tangled trawl from the net reel. Unfortunately, removing the net took about 12 hrs because the net became tangled on the reel. Only 17 of the 32 Kodiak grid sites were successfully occupied (Table 1). This was largely due to an overly ambitious cruise plan. Overall, samples were successfully collected to address cruise objectives (no. sites, gear type): time series (n=26 sites, midwater Stauffer trawl), resource selection models (RSM, n=35 sites, 3-m plumb staff beam trawl), potential prey (n=9 sites, 60-cm bongo, epibenthic sled, Van Veen grab infauna), and juvenile fish production (relevant data were collected at all sites). At nine sites, including Station 39, the sea floor was too rough to sample on bottom so only a midwater sample was collected. This additional sampling was to supplement collections made for the GOA-Integrated Ecosystem Research Program (RHeintz, see above Samples Collected) and for a study of otolith element composition. Sampling concluded after three unsuccessful attempts to obtain a sediment composition sample at Site 27G (Station 56) at approximately 03:25 on 14 October 2011.
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.
Western coastal Gulf of Alaska; Shumagin to Kodiak islands
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:
See InPort entries 26275, 26373 and 26570.
(describe or provide URL of description):
See InPort entries 26275, 26373 and 26570.
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. Name of organization of facility providing data access
- 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.
There are no legal restrictions on access to the data. They reside in public domain and can be freely distributed.
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.
Contract Distrubutor
human examination of samples required.
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
local and off site backups
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.