Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:28004 | 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
Atka mackerel Pleurogrammus monopterygius were captured and tagged with depth and temperature recording devices (archival tags) on 23 July 2000 in Seguam Pass, Aleutian Islands, Alaska. Nine of the 117 tagged fish were recovered in Seguam Pass during September 2000, and an additional 5 fish recovered thereafter (14 total). In addition, 413 tags were released in Tanaga Pass in 2002, with 10 recoveries. Fish were tagged externally just below the dorsal fin. Atka mackerel displayed strong diel behavior, with vertical movements away from the bottom occurring almost exclusively during daylight hours and little to no movement at night. Vertical movements occurred when light levels at 150 m were greater than 7.31 × 10–5 µmol photons m–2 s–1, or approximately between 08:00 and 23:00 h Alaska Daylight Time (ADT; GMT – 8) during August. Daytime vertical movements were correlated with light intensity, time of day and current velocity. The occurrence of vertical movements tended to increase with increasing light during the morning and early afternoon, but then decrease with increasing hour of the day after 13:00 h ADT. The magnitude of surface-directed vertical excursions was reduced during spring tide periods, when current velocities are highest. By comparison, the magnitude of slope-directed excursions was greater during spring tide periods and reduced during neap tide periods. Eight fish were at liberty for 42 to 44 d and 1 for 65 d. Two of the tagged males displayed nest guarding behavior for the majority of their time at liberty. Depths for these 2 males (115 to 117 m) were much deeper than previously observed for Atka mackerel spawning grounds. Given that Atka mackerel are more likely to be on the bottom during the night and less likely during the day, the variance of abundance estimates from bottom trawl surveys may be reduced by accounting for these diel differences.
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.
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:
Atka mackerel were initially captured during two bottom trawl tows made on 23 July 2000 aboard the chartered F/V Morning Star in Seguam Pass, Alaska. Tow durations were kept short (< 15 min) in order to minimize injury to fish. Fish were held briefly in tanks plumbed with a continuous flow of fresh seawater. A total of 117 fish were tagged with archival tags and released on 23 July 2000; 66 fish from the first tow (Haul 4) at 119 m bottom depth and 51 fish from the second (Haul 7) at 110 m bottom depth. Fish were measured to the nearest cm fork length (FL) and released within 3.1 km of the capture location. Archival tags were externally attached just below the anterior section of the dorsal fin. Fish were secured in a V-shaped cradle and paired 18 gauge hypodermic needles were inserted through the fish. Stainless-steel wire (0.02 gauge, 0.5 mm diameter) was fed through the tag and then through the open end of the hypodermic needles. After removing the hypodermic needles, the stainless-steel wire ends were fed through a pink plastic oval and secured with stainless-steel connector sleeves. This procedure took approximately three minutes per fish. A tag reward program was implemented to retrieve tagged fish. This program was conducted in association with an ongoing spaghetti tag project for Atka mackerel in Seguam Pass (See Susanne McDermott).
Publication: Nichol, D.G. and Somerton D.A. Diurnal vertical migration of the Atka Mackerel Pleurogrammus monopterygius as shown by archival tags. Mar. Ecol. Prog Ser. 239:193-207.
(describe or provide URL of description):
unknown
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
(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.
unknown
No delay
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.