Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:47176 | 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
Bearded seals (Erignathus barbatus) are one of the most important subsistence resources for the indigenous people of coastal northern and western Alaska, as well as key components of Arctic marine ecosystems. Yet, relatively little about their abundance, seasonal distribution, migrations, or foraging behaviors has been documented scientifically. Ice-associated seal populations may be negatively impacted by offshore oil and gas development as well as by climate change. Our ability to predict impacts, however, is limited by inadequate knowledge of seal population structure and foraging ecology. By working cooperatively with Alaska Native subsistence hunters we developed methods for live- capturing bearded seals in the Chukchi Sea using nets set in the shallow coastal waters where bearded seals were foraging. Capture efforts were based out of Kotzebue and various locations in the North Slope Borough from Wainwright to Barrow in June and July from 2009 to 2012. In all, 7 seals were caught (2 adults and 5 sub-adults; 4 males and three females; ranging in length and weight from 159 cm and 116 kg to 216 cm and 253 kg), all from Kotzebue Sound. Each seal was released with two different types of bio-logging devices: the SPOT5, attached to a rear flipper, provided information on the timing of hauling out and on the seal’s location for up to three years. The MK10, glued to the top of a seal’s head, provided the same information as well as data on the timing and depths of dives. MK10 deployments remained active up to ten months and were shed from the seal during the annual molt.
The data files within this dataset represent the 'raw' data obtained from the Wildlife Computers data portal. Each deployment (unique tag id + animal id combination) is provided as a zipped archive. The root folder also includes additional documentation. The various files and detailed column descriptions are described in the 'Spreadsheet-File-Descriptions.pdf' which was downloaded from Wildlife Computers (https://wildlifecomputers.com/support/downloads/). The '00_kotzeb0912_get_data.Rmd' file is an RMarkdown file that provides code and documentation of the data retrieval process. The corresponding '00_kotzeb0912_get_data.hml' file is autogenerated from the RMarkdown file.
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.
Bering Sea, Chukchi Sea, Beaufort Sea, Arctic Ocean
W: -174, E: -143, N: 74, S: 59Notes: 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:
During June and July of 2009-20012, NOAA researchers and Alaska Native hunters captured, instrumented and released 7 adult or sub-adult bearded seals with satellite-linked dive records in Kotzebue Sound, Alaska. Capture efforts also occurred near Wainwright, Peard Bay, and Utqiaġvik. Adult age class animals were targeted. Although, there is uncertainty associated with field classification of age in seals. Satellite telemetry devices were attached to the hair of the back of the seals using fast-setting epoxy and to the rear inter-digital flipper webbing with two posts and holes.
All data provided are included as zipped archives that contain a variety of files processed on the Wildlife Computers Data Portal. The specific files included are dependent upon the tag hardware, firmware, and programming options selected. The files and column heading descriptions are provided in the 'Spreadhseet-File-Descriptions.pdf' which was downloaded from the Wildlife Computers web site (https://wildlifecomputers.com/wp-content/uploads/manuals/Spreadsheet-File-Descriptions.pdf) on May 20 2019.
The programming specifications and tag details are provided in either a *.htm or *.rpt file. These are the files created at the time the tag was programmed.
The included '00_kotzeb0912_get_data.Rmd' is an R Markdown file that describes the process for downloading and renaming files from the Wildlife Computers Data Portal. The '00_kotzeb0912_get_data.html' file is created when this R Markdown file is run
Process Steps:
- The included R Markdown file '00_kotzeb0912_get_data.Rmd' and the corresponding HTML file '00_kotzeb0912_get_data.html' provide the R code and inline documentation describing the process by which the data were obtained from the Wildlife Computers Data Portal
(describe or provide URL of description):
Limited quality control procedures have been employed. This dataset is an archive of the processed output from the Wildlife Computers data processing software. These tags were deployed on free-ranging, wild animals in challenging environments. In all cases, additional quality control procedures and evaluation from experts familiar with the tags, programming and species will be required.
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)
(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 is intended to be archived with the US Animal Telemetry Network and the Data Observation Network for Earth (DataONE). Once the archival process is complete and verified, the data set will be publicly available.
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.
The data set is intended to be archived with the US Animal Telemetry Network and the Data Observation Network for Earth (DataONE). Once the archival process is complete and verified, the data set will be publicly available.
data not automatically processed
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.