Data Management Plan
GUID: gov.noaa.nmfs.inport:28005 | 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
Depth data from archival tags on northern rock sole (Lepidopsetta polyxystra) were examined to assess whether fish used tidal currents to aid horizontal migration. Two northern rock sole, out of 115 released with archival tags in the eastern Bering Sea, were recovered 314 and 667 days after release. Both fish made periodic excursions away from the bottom during mostly nighttime hours, but also during particular phases of the tide cycle. One fish that was captured and released in an area of rotary cur rents made vertical excursions that were correlated with tidal current direction. To test the hypothesis that the fish made vertical excursions to use tidal currents to aid migration, a hypothetical migratory path was calculated using a tide model to predict the current direction and speed during periods when the fish was off the bottom. This migration included limited movements from July through December, followed by a 200-km southern migration from January through February, then a return northward in March and April. The successful application of tidal current information to predict a horizontal migratory path not only provides evidence of selective tidal stream transport but indicates that vertical excursions were conducted primarily to assist horizontal migration.
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:
Two NRS were recovered from among 115 released with attached electronic data storage tags in the eastern Bering Sea between 4 June and 26 July 2003. Release locations were approximately 200 km northeast of St. Paul Island (northern fish) and 18 km northwest of Unimak Island (southern fish) (Fig. 1). Fish were initially captured with a bottom trawl, tagged and released during the course of the annual eastern Bering Sea bottom trawl survey (Acuna and Lauth, 2008). The two recovered fish, both captured by commercial trawlers, were a 34 cm TL (at release) female at liberty for 314 days (northern fish) and a 40 cm TL (at release) female at liberty for 667 days (southern fish).
The fish were tagged with Lotek Wireless LTD-1100 data storage tags. Tags were attached to the eyed-side, just below the anterior end of the dorsal fin using 0.5 mm stainless-steel wire. The wire was inserted through two points on the tag, through the fish’s muscle, and affixed on the blind side using oval plastic backing. The two wire ends were fastened on the outside of the backing with a crimped connector sleeve.
Tag data, including depth and temperature, were recorded at 0.5- or 1-hr time intervals. Depth had a resolution of 0.58 m when fish remained in less than 150 m and 1.2 m thereafter if the fish exceeded 150 m; temperature had an accuracy of + 0.3 ¿C. The northern tag recorded for the entire 314 days the fish was at liberty, whereas the southern tag recorded for 620 of 667 days at liberty before the battery died.
(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.