Data Management Plan
GUID: gov.noaa.nmfs.inport:69088 | 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 Northwest Fisheries Science Center's (NWFSC) Salmon Population Summary (SPS) database provides public access to demographic data compiled for ESA-listed salmonid populations as part of the NWFSC's technical recovery planning efforts. The database contains data collected by co-managers (WDFW, ODFW, IDFG, and Tribes) and compiled in cooperation with NWFSC staff for: spawning abundance, age structure of wild spawners, fraction of natural spawners that are of wild origin, and the reduction in spawning abundance due to harvest. For some populations, additional data fields are also available. The data correspond to the populations identified by the NMFS Technical Recovery Teams, and are used in part to assess population and ESU-level recovery criteria for many listed ESUs. Most importantly, this data is critical for informing 5 year ESA salmon reviews, and makes 5 year status review data available to the public.
Abundance of ESA-listed salmonids.
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.
Salmonid extents within Washington, Oregon, and 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.
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:
The data were compiled by NMFS West Coast Region staff from various data sources.
Process Steps:
- NMFS Northwest Regional Office staff compiled data from multiple sources.
(describe or provide URL of description):
All of the Pacific Northwest TRTs spent considerable time and effort developing spawning abundance data for the populations they identified within ESUs. In almost all cases these estimates are derived from state, tribal, or federal monitoring programs. The raw information on which the spawning abundance estimates were developed consist of numerous types of data including redd counts, dam counts, carcass surveys, information on prespawning mortality, and spawning distributions within populations that the TRTs used to develop estimates of natural-origin spawning abundance. It is important to recognize that spawning abundance estimates and related information such as the fraction of spawners that are of natural origin are not known with certainty. Rather, they are estimates based on a variety of sources of information, some known with greater precision or accuracy than others. Ideally these estimates would be characterized by a known level of statistical uncertainty; however, for the most part such a statistical characterization is either not possible or has not been attempted.
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)
- 4.1. Have resources for management of these data been identified?
- 7.1.1. If data are not available or has limitations, has a Waiver been filed?
- 7.3. Data access methods or services offered
- 7.4. Approximate delay between data collection and dissemination
- 8.1. Actual or planned long-term data archive location
- 8.3. Approximate delay between data collection and submission to an archive facility
- 8.4. How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?
(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.
None. The data is available to the public.
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.
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
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.