Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:78312 | 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
Coastal managers in Delaware examined whether biochar input from prescribed burns restores ecosystem services after removal of Phragmites australis, an invasive grass species.
The Project
Phragmites australis is an invasive grass species that affects many marshes along the U.S east coast, often displacing native grasses. Removing Phragmites has been a decades-long management goal as managers seek to restore native high marsh habitat and ecosystem functions and services. Phragmites removal and restoration efforts have proven beneficial for habitat and biodiversity. However, its removal has potentially negative impacts on water quality and carbon storage, as Phragmites stores nitrogen and phosphorus and accumulates organic carbon more effectively than native marsh vegetation. Tidal wetland managers are left with uncertainties about these tradeoffs of Phragmites removal and their implications for achieving marsh restoration goals. A potential approach for managing tradeoffs associated with Phragmites removal is to use prescribed fire. While prescribed fire is a common method for vegetation removal, there has been limited research on the biogeochemical benefits provided by burned biomass or "biochar". Biochar may increase soil nitrogen removal and carbon and phosphorus storage, which can help to counteract losses in ecosystem services due to Phragmites removal.
Collaborating with regional coastal managers, this project team compared salt marshes with and without a history of prescribed burns at Delaware National Estuarine Research Reserve and area marshes to better quantify how fire impacts marshes and their ecosystem services. The team collected and analyzed salt marsh sediment cores at multiple sites and found that the marshes that were more frequently burned had enhanced carbon storage. They also used biochar amendments to learn more about other biogeochemical metrics, like denitrification potential and phosphorus storage, and found that biochar's impact on these metrics were limited.
The project convened an Advisory Committee that held productive discussions on current and potential Phragmites management practices, prescribed burn practices, and climate-adaptive decision-making procedures, in the context of the project's findings. These conversations helped inform a comprehensive report on the impacts of prescribed burns on tidal marsh ecosystem services. This report will allow for easier transfer of knowledge among the project's partners, including Delaware NERR, Delaware Natural Resources and Environmental Control, U.S. Fish and Wildlife Service, Center for the Inland Bays, Partnership for the Delaware Estuary, and Delaware Wild Lands.
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.
Dover, DE NERR
W: -75.6008, E: -75.5839, N: 39.4361, S: 39.4169Townsend, DE NERR
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.
