Data Management Plan
GUID: gov.noaa.nmfs.inport:17834 | 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
1) The purpose of this project is to document juvenile salmon habitat occurrence in the Lower Columbia River and estuary, and examine how habitat conditions influence their distribution, health, and abundance. We also want to monitor habitat conditions and indicators of salmon health in these environments. Parameters measured include habitat conditions such as vegetation, water temperature, and dissolved oxygen; salmon diet and prey availability; weight, length, growth rate, lipid content, genetic stock, and chemical contaminant exposure.
2) Lyndal Johnson (NFWSC FTE) is the project lead, and other primary staff involved are Sean Sol and Paul Olson (NWFSC FTEs) and Kate Macneale (NWFSC term employee), but the project also involves other NWFSC FTEs, other term employees, contractors, and staff from other programs (Environmental Chemistry) and Divisions (FE, CB), as well as staff from collaborating agencies (i.e, the Lower Columbia River Estuary Partnership, USGS, PNNL, OHSU).
3) The project involves field surveys in which parameters measured include habitat conditions such as vegetation, water temperature, and dissolved oxygen; salmon diet and prey availability; weight, length, growth rate, lipid content, genetic stock, and chemical contaminant exposure.
4) Specific products include annual reports for the Lower Columbia Estuary Partnership, and manuscripts in peer-reviewed journals.
5) Specific audiences include (but are not limited to) the Bonneville Power Administration and other federal, state, and local agencies involved with salmon recovery and environmental management in the Columbia Basin (e.g., EPA, Washington Department of Ecology, Oregon Department of Environmental Quality, the City of Portland); the NMFS regional office, and other agency and academic scientists.
6) This is a stand-alone project, but it is also a component of a larger monitoring program overseen by the Estuary Partnership in which other tasks are conducted by collaborators in USGS, PNNL, and OHSU.
7) This is an ongoing project with a soft completion deadline; however, there are no final deadlines with specific tasks to be completed on a yearly basis.
Prey composition in diet samples and water column tows at Lower Columbia River sites.
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.
Welch Island: Welch Island, Lower Columbia River and Estuary
W: -123.515, E: -123.515, N: 46.2525, S: 46.2525Iwaco Slough: Ilwaco Slough, Lower Columbia River and Estuary
W: -122.3062, E: -122.3062, N: 47.6449, S: 47.6449Campbell Slough: Campbell Slough, Lower Columbia River and Estuary
W: -122.3062, E: -122.3062, N: 47.6449, S: 47.6449Franz Lake: Franz Lake, Lower Columbia River and Estuary
W: -122.3062, E: -122.3062, N: 47.6449, S: 47.6449Whites Island: Whites Island, Lower Columbia River and Estuary
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:
These data were collected and processed in accordance with established protocols and best practices under the direction of the projects Principal Investigator. Contact the dataset Data Manager in section 3 for full QA/QC methodology.
(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 projects Principal Investigator. Contact the dataset Data Manager in section 3 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.
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.
Data are housed in password protected databases behind a firewall.
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, contact the Data Manager for information on obtaining access to this data set. In the near future, the NWFSC will strive to provide all non-sensitive data resources as a web service in order to meet the NOAA Data Access Policy Directive (https://nosc.noaa.gov/EDMC/PD.DA.php).
No Delay
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.