Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:78316 | Published / External
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. For more information, consult the help guides on the new Data Management Plan as well as how to convert this Legacy DMP to the new format.
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
Water quality monitoring experts, scientists, and estuary caretakers built a long-term collaborative monitoring strategy for estuary nutrients and phytoplankton dynamics at the headwaters of Lake Superior.
The Project
The St. Louis River Estuary, located at the headwaters of Lake Superior, is nearing a major milestone: its anticipated delisting as a Great Lakes Area of Concern by 2030. Yet even as remediation and restoration successes are celebrated, new environmental stressors, particularly harmful algal blooms, raise concerns about the estuary's long-term water quality health. In response, a group of local, state, federal, and tribal partners who have long worked in and cared for the estuary began calling for a science-based monitoring strategy that could respond to emerging threats and support ongoing stewardship beyond delisting. Together, they shaped a shared vision: a comprehensive program of observations, analyses, and public reporting that would protect remediation and restoration investments and inform future decision-making.
To advance this vision, this group of partners who had long advocated for a coordinated monitoring effort, collaborated closely with the Lake Superior National Estuarine Research Reserve to launch the project. The Reserve brought together a scientific team that included collaborators from the University of Minnesota's Natural Resources Research Institute, who contributed expertise in phytoplankton and bloom dynamics. The partners co-authored the proposal and remained actively engaged throughout the project, helping select sites, shape the study design, and review statistical analysis and draft recommendations. Together, the partners and project team developed a research approach that combined strong scientific design to build foundational understanding of phytoplankton dynamics with a focus on generating practical, actionable insights for a shared long term monitoring strategy. Eight high-priority sites were intensively sampled in 2023 and 2024, focusing on areas vulnerable to nutrient enrichment, low oxygen, and bloom formation. The study also prioritized public relevance by targeting restoration areas, heavily used public zones, and capturing rarely collected wintertime data.
The project successfully identified predictors of cyanobacteria biovolume in the estuary and actionable monitoring strategies to improve bloom detection and efficient water quality monitoring in the future. Important predictors of blooms included low nitrogen, warm temperatures, low dissolved organic carbon, and high pH. In addition, the team observed significant year-to-year differences in bloom composition and intensity suggesting bloom dynamics are highly responsive to variations in hydrology and nutrient stoichiometry which are driven by precipitation patterns. Further analysis evaluated the efficiency of different monitoring designs by assessing redundancy across space, sampling frequency, and parameters. These findings informed a science-based strategy that identified periods and locations of elevated bloom risk while accounting for the real-world capacity of agencies and partners. The resulting recommendations include a reduced set of priority sites and a tiered approach to sampling. This strategy is designed to be flexible with available funding and effort, while ensuring that high-risk bloom locations are monitored as a minimum standard. The project's result is not only a clearer picture of what drives blooms in the estuary, but also a durable and collaborative roadmap for long-term monitoring, co-created by the people who first called for a collaborative, comprehensive program.
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.
Data was primarily collected either within Douglas County, WI or St. Louis County, MN within the St. Louis River Estuary and nearshore Lake Superior
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:
This information is detailed within the project links.
Process Steps:
- N/A
(describe or provide URL of description):
This information is detailed within the project links.
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.6. Type(s) of data
- 1.7. Data collection method(s)
- 3.1. Responsible Party for Data Management
- 4.1. Have resources for management of these data been identified?
- 4.2. Approximate percentage of the budget for these data devoted to data management
- 7.1. Do these data comply with the Data Access directive?
- 7.1.1. If data are not available or has limitations, has a Waiver been filed?
- 7.1.2. If there are limitations to data access, describe how data are protected
- 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.2. Data storage facility prior to being sent to an archive facility
- 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
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.
