Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:30856 | Published / External
This is an outdated version of the NOAA Data Management Plan template. InPort now supports a dedicated Data Management Plan Catalog Item type, which is up-to-date with the latest NOAA DMP template. The ability to generate Data Management Plans from Data Sets will be discontinued in a future release. Please see the Data Management Plan Help Guide to learn more.
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
Removal of two dams on the Elwha River, Washington will help restore natural sediment processes to the coastal environment near the river mouth. We are interested in the responses of fish associated with shallow subtidal and intertidal habitats because they function as spawning and rearing habitat for many fish species including the ecologically important forage fish and federally protected species of Pacific salmon. Since 2006, we have been collecting species composition and size distribution of the intertidal/subtidal fish community in the Eastern and Central Strait of Juan de Fuca. Potential reference site and treatment sites (where sediment changes are expected to occur) were sampled on a monthly basis from April to September using a beach seine. We found over 45 species of fish, mostly juvenile stages, using this portion of the Strait of Juan de Fuca representing two groups- fish occurring in the water column and those living on or near the bottom. The water column species tended to be very abundant and included both migrants (e.g., juvenile salmon) and residents (surf smelt). Although the same species tended to be present each year, they often exhibited dramatic between year variability in abundance. This suggests the importance of using multiple years of data to evaluate changes resulting from dam removal. Treatment and reference areas exhibited some significant differences and we found seasonality in the fish assemblage structure. Our results suggest that some promising bio-indicators of short and long term change in sediment processes are: 1) numbers of species, 2) species diversity, 3) composition and sizes of benthic species, 4) abundance by life history stage of surf smelt, and 5) presence of migratory species like juvenile salmon. We will continue this work following dam removal to track the changes due to dam removal.
For this project, the data was stored in .xls and access files.
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.
Sequim, WA: Elwha Nearshore
W: -122.3062, E: -122.3062, N: 47.6449, S: 47.6449Port Angeles, WA: Elwha Nearshore
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:
Data was entered into access/xls files from datasheets. 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 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)
- 3.1. Responsible Party for Data Management
(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.
NA
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.
https://www.webapps.nwfsc.noaa.gov/apex/parr/elwha_dam_removal_neashore_monitoring_field_details/data/page/
https://www.webapps.nwfsc.noaa.gov/apex/parr/elwha_dam_removal_neashore_monitoring_lab_results/data/page/
https://www.webapps.nwfsc.noaa.gov/apex/parr/elwha_dam_removal_neashore_monitoring_net_setting_information/data/page/
https://www.webapps.nwfsc.noaa.gov/apex/parr/elwha_dam_removal_neashore_monitoring_of_substrate/data/page/
https://www.webapps.nwfsc.noaa.gov/apex/parr/elwha_dam_removal_neashore_monitoring_sites/data/page/
https://www.webapps.nwfsc.noaa.gov/apex/parr/elwha_dam_removal_neashore_monitoring_species/data/page/
https://www.webapps.nwfsc.noaa.gov/apex/parrdata/inventory/datasets/dataset/19530
https://www.webapps.nwfsc.noaa.gov/apex/parrdata/inventory/tables/table/elwha_dam_removal_neashore_monitoring_catch_information
https://www.webapps.nwfsc.noaa.gov/apex/parrdata/inventory/tables/table/elwha_dam_removal_neashore_monitoring_field_details
https://www.webapps.nwfsc.noaa.gov/apex/parrdata/inventory/tables/table/elwha_dam_removal_neashore_monitoring_lab_results
https://www.webapps.nwfsc.noaa.gov/apex/parrdata/inventory/tables/table/elwha_dam_removal_neashore_monitoring_net_setting_information
https://www.webapps.nwfsc.noaa.gov/apex/parrdata/inventory/tables/table/elwha_dam_removal_neashore_monitoring_of_substrate
https://www.webapps.nwfsc.noaa.gov/apex/parrdata/inventory/tables/table/elwha_dam_removal_neashore_monitoring_sites
https://www.webapps.nwfsc.noaa.gov/apex/parrdata/inventory/tables/table/elwha_dam_removal_neashore_monitoring_species
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.