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 goal of the tidal-fluvial estuary study is to determine the estuary's contribution to the spatial structure and life history diversity of Columbia River salmon stocks and the implications for estuary restoration. The study targets salmon use of tidal-fresh habitats in the estuary from Rkm 75 to Bonneville Dam, and addresses four primary objectives:
1. Characterize the temporal and spatial distribution of Chinook salmon genetic stock groups throughout the estuary (March 2010 - March 2012).
2. Determine stock-specific habitat use, life histories, and performance of juvenile salmon in key habitat complexes to fill data gaps in the tidal fluvial reaches of the estuary (2012-2016).
3. Monitor juvenile salmon life histories and their contributions to adult returns in selected estuary tributaries, including tributary examples where tidal habitats have been restored (2012-2018).
4. Evaluate estuary restoration needs for recovery of all salmon ESUs and account for projected effects of climate change through application of a salmon life-cycle model (2011-1015).
The study, funded by the U.S. Army Corps of Engineers, involves a large team of researchers organized by NOAA Fisheries, including researchers from the Oregon Health and Sciences University, University of Washington, and Washington Department of Fish and Wildlife. The study addresses critical uncertainties identified in the research, monitoring, and evaluation (RME) program for the Federal Columbia River Estuary Program (FCREP). The Estuary Program is intended to conserve and restore the estuary ecosystem to improve the performance of listed salmonid populations. Products from the tidal-fluvial study will include:
1. Descriptions of stock-specific temporal and spatial distributions of Chinook salmon throughout the estuary.
2. Estimates of variations in Chinook salmon stock composition and stock-specific growth, food habits, consumption rates, and bioenergetic efficiencies within selected tidal-fluvial habitats.
3. Estimated contributions of estuarine life histories among returning adult Chinook salmon from selected populations throughout the Columbia River Basin.
4. A hydrological model quantifying the dynamics of rearing habitat opportunities for juvenile salmon at estuary reach and habitat scales.
5. Improved life-cycle models to account for the estuarine life histories of juvenile salmon and estimating the potential effectiveness of estuary restoration actions on the recovery and viability of selected salmon stocks. These results will directly address information needs to support estuary actions specified in the Federal Columbia River Power System (FCRPS) Biological Opinion for the Columbia River. The tidal-fluvial estuary study is part of an ongoing estuary research program initiated in 2002. The current study expands upon earlier research conducted in the lower 100 km of the estuary from 2002 to 2008. Although all objectives will be addressed by 2018 to correspond with a review of progress implementing the FCRPS Biological Opinion, some sampling activities may extend beyond this date to allow brood-year reconstruction of estuary contributions to adult returns in selected streams (Objective 3).
PIT detection data (residence time, travel time) in estuary wetland channels from juvenile salmon tagged by this project and other projects.
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.
Point Adams Field Station
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.)
Platform: Sea Floor based Platform, Water based Platforms - Watercraft - Manned Watercraft - Boat
Physical Collection / Fishing Gear: Animal and Plant Collection Device
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.
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):
Some field collected data are manually entered to software at time of observation. Other data are imported into Access and then uploaded to regional database called PTAGIS.
(describe or provide URL of description):
Access database has some quality control measures. Data uploaded to PTAGIS undergo quality control measures maintained by the database manager. These data were collected and processed in accordance with established protocols and best practices under the direction of the project’s Principal Investigator. Contact the dataset Data Manager for full QA/QC methodology.
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.
(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.
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.
Majority of these data are already available via the regional database, PTAGIS.org
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
Ptagis.org has protection and back up measures in place.
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.