Data Management Plan
GUID: gov.noaa.nmfs.inport:25525 | 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 National Marine Fisheries Service (NMFS) has conducted shore-based counts of the Eastern North Pacific stock of gray whales (Eschrichtius robustus) 26 years from 1967 to 2008 at Granite Canyon (or nearby at Yankee Point), 13 km south of Carmel, in central California. Convenient access to the Granite Canyon research station (owned by NOAA but operated by the State of California Department of Fish and Game) and the narrowness of the whales' migratory corridor in this area permitted an efficient counting process at this site. All counts were conducted during the 2-month southbound migration (mid-December to late February) rather than the protracted 3-month northbound migration. The routine nature of these counts and the consistency in research protocol lend themselves to inter-annual trend analyses. Research protocol has been based on single observers independently searching for whales and recording data on environmental conditions and the time, location, count, and direction of travel for each sighting. The counting system and observer performance has been tested through paired, independent observational effort; aerial surveys; thermal imagery; radio-tagging of whales; systematic observations through high-powered (25x) binoculars; and teams of observers tracking specific whale pods through the viewing area.
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.
Granite Canyon and Yankee Point, California
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):
Process Steps:
- For years since 1987, observers checked their hand-written data sheets the day of collection, filling in redundant information (such as the header on the data form) and corrected obvious errors (such as misspellings in comments). Each observer then entered their data into a computer database (ERAbund). The database entry program had built-in boundaries for each data field (e.g., a logical date, a list of possible observer initials, and a range of possible entries for visibility, Beaufort state, etc.) to eliminate common data-entry errors.
- Preferably within a day or two of the original data entry, NMML observers worked in pairs to compare all of the handwritten data sheets to printouts of the corresponding records in the database. This provided a check of the accuracy of data transfer from handwritten logs to the database, and gave two more people a chance to review the data, watching for possible illogical errors (e.g., only gray whale sightings have data in columns for location and pod size; keeping environmental condition records in chronological order; starting and ending watches with the appropriate codes).
(describe or provide URL of description):
See descriptions of methods at http://www.afsc.noaa.gov/nmml/software/eranalysis.php
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.
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.
At this time data can be downloaded from the Alaska Fisheries Science Center website: http://www.afsc.noaa.gov/nmml/software/eranalysis.php
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.