Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:28315 | 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
Aerial surveys were flown during the spring of 2012 and 2013 as part of the Bering Okhotsk Seal Surveys (BOSS) project to gather data on distribution and abundance of ice-associated seals in the eastern Bering Sea. The distributions of these seals are broad and patchy, resulting in surveys that cover large areas and encounter rapidly changing environmental conditions. Surveys were flown using a fixed-wing aircraft with a paired system of digital cameras and thermal imagers operated by observers and mounted in the belly port. Flight tracks were recorded with an attitude and heading reference system (AHRS) that also recorded location information at one second intervals. A secondary flight track was recorded with a GPS which was used to supplement location information when there was a glitch with the AHRS. BOSS on-effort flight tracks were used to calculate total distance and area flown for estimating seal abundance, in addition to georeferencing digital and thermal imagery collected in flight. On-effort flight tracks (survey effort) were initially determined by the observer based on environmental conditions and later refined based on aircraft attitude and imagery review. The spatial data are provided in the geographic (epsg:4326) coordinate reference system.
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:
BOSS on-effort flight tracks were recorded with an AHRS and a secondary flight track was recorded with a GPS that was used to supplement location (lat/long) information when there was a glitch in the AHRS data recording. Supplemental location information was interpolated. Post-processing of BOSS on-effort flight tracks was derived from a combination of inflight observations (based on environmental conditions) and later refined by reviewing aircraft attitude and imagery. Any flight track segments that were determined to be “off-effort” were not used to calculate total distance/area flown for seal abundance estimates and were not included in the database.
(describe or provide URL of description):
Flight tracks were collected in the field and post-processed to determine accurate survey effort in order to calculate the total distance and area covered. Two sets of flight tracks were collected to ensure location accuracy. Feedback from aerial survey observers informs the evaluation of what is considered to be “on-effort”, in addition to aircraft attitude and imagery review.
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 in the process of being archived with the NOAA National Centers for Environmental Information. 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 in the process of being archived with the NOAA National Centers for Environmental Information. Once the archival process is complete and verified, the data set will be publicly available.
data were 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.