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
This is an ongoing Bonneville Power Administration funded project to annually collect, PIT tag, and release wild Chinook salmon parr in up to 15 streams of the Salmon River drainage in Idaho and subsequently monitor these fish through in-stream monitoring sites and downstream dams. The overall study objectives are to assess the migrational characteristics and estimate parr-to-smolt survival for Snake River wild spring/summer Chinook salmon smolts at Lower Granite Dam, characterize parr and smolt survival and movement out of natal rearing areas of selected streams and examine the relationships between fish movement, environmental conditions within the streams, and weather and climate data. This project also collects parr-to-smolt growth information on previously PIT-tagged wild Chinook salmon parr at the Lower Granite Dam sort-by-code PIT detection system each spring. A goal of this study is to characterize run-timing of wild fish to determine if consistent patterns are apparent and to provide daily information for real-time management decisions during the smolt out-migrations.
Up to 6 water quality parameters collected hourly in 16 streams of the Salmon River basin in Idaho.
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.
Bear Valley Creek: Upper Middle Fork Salmon River, IdahoW: -114.8537, E: -114.8537, N: 45.1036, S: 45.1036
Big Creek (lower): Lower Middle Fork Salmon River, IdahoW: -114.9313, E: -114.9313, N: 44.2218, S: 44.2218
Valley Creek: Upper main Salmon River, IdahoW: -115.7034, E: -115.7034, N: 44.6564, S: 44.6564
South Fork Salmon River: Upper South Fork Salmon River, IdahoW: -115.8099, E: -115.8099, N: 45.2149, S: 45.2149
Secesh River: South Fork Salmon River drainage, IdahoW: -115.3311, E: -115.3311, N: 45.1012, S: 45.1012
Big Creek (upper): Lower Middle Fork Salmon River, IdahoW: -122.3062, E: -119.0532, N: 47.6449, S: 46.2086
Elk Creek: Upper Middle Fork Salmon River, IdahoW: -115.1693, E: -115.1692, N: 44.3963, S: 44.3962
Marsh Creek: Upper Middle Fork Salmon River, IdahoW: -115.1895, E: -115.1895, N: 45.3875, S: 45.3875
West Fork Chamberlain Creek: Tributary in main Salmon River, IdahoW: -114.8064, E: -114.8064, N: 44.6021, S: 44.6021
Loon Creek: Tributary in Middle Fork Salmon River, IdahoW: -115.9023, E: -115.9023, N: 45.2594, S: 45.2594
Lake Creek: South Fork Salmon River drainage, IdahoW: -114.5013, E: -114.5013, N: 44.8301, S: 44.8301
Camas Creek: Lower Middle Fork Salmon River, IdahoW: -115.1696, E: -115.1696, N: 44.3953, S: 44.3953
Cape Horn Creek: Upper Middle Fork Salmon River, IdahoW: -115.3723, E: -115.3723, N: 44.5333, S: 44.5333
Sulphur Creek: Upper Middle Fork Salmon River, IdahoW: -122.3062, E: -119.0532, N: 47.6449, S: 46.2086
Herd Creek: Upper East Fork Salmon River, IdahoW: -115.1875, E: -115.1875, N: 45.3731, S: 45.3731
Chamberlain Creek: Tributary in the main Salmon River, Idaho
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.
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):
Use sonde-based software to download data. Data is emailed to data coordinator for upload.
(describe or provide URL of description):
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.
- 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.
Anyone can register to obtain a user name and password to access the data
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.
Request user ID and password. At this time, contact the Data Manager for information on obtaining access to this data set. In the near future, the NWFSC will strive to provide all data resources as a web service in order to meet the NOAA Data Access Policy Directive (https://nosc.noaa.gov/EDMC/PD.DA.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
The Northwest Fisheries Science Center facilitates backup and recovery of all data and IT components which are managed by IT Operations through the capture of static (point-in-time) backup data to physical media. Once data is captured to physical media (every 1-3 days), a duplicate is made and routinely (weekly) transported to an offsite archive facility where it is maintained throughout the data's applicable life-cycle.
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.