Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:47908 | 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
In fall 2001, researchers from the Wells National Estuarine Research Reserve, Virginia Institute of Marine Science, and the NOAA Office for Coastal Management conducted a project to map benthic habitats in the York and Webhannet rivers in southern Maine. The team completed two weeks of fieldwork in September 2001, collecting sediment profile images at 382 stations and sediment grab samples at 93 stations. This data set represents the information gathered from sediment profile imagery sampling.
Original contact information:
Contact Name: Dr. Michele Dionne
Contact Org: Wells National Estuarine Research Reserve
Phone: (207) 646-1555
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.
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):
Process Steps:
- 2001-09-01 00:00:00 - Field Methods: SPI images were collected from 4 to 10 September at a total of 382 stations. A Hulcher model sediment profile camera was deployed with a modified frame that was lightened for use from a small vessel. Fujichrome 100 ASA professional color slide film was used. Tests were done frequently onboard in order to ensure camera function and mark stations. Laboratory Methods: All sediment images were analyzed visually by projecting the images and recording all features seen into a preformatted standardized spreadsheet file. Images were then digitized using a Nikon LS2000 scanner and analyzed using the Adobe PhotoShop and NTIS Image programs. Steps in the computer analysis of each image were standardized and followed the basic procedures in Viles and Diaz (1991). Data from each image were sequentially saved to a spread sheet file for later analysis. Details of how these data were obtained can be found in Diaz and Schaffner (1988) and Rhoads and Germano (1986). References: 1) Viles, C. and R.J. Diaz. 1991. Bencore, an image analysis system for measuring sediment profile camera slides. School of Marine Science, Virginia Institute of Marine Science, College of William and Mary, Gloucester Pt. VA. 13 pp. 2) Diaz, R.J. and L.C. Schaffner. 1988. Comparison of sediment landscapes in the Chesapeake Bay as seen by surface and profile imaging. p. 222 240. In: M. P. Lynch and E. C. Krome, eds. Understanding the estuary; Advances in Chesapeake Bay research. Chesapeake Res. Consort. Pub. 129, CBP/TRS 24/88. 3) Rhoads, D.C. and J.D. Germano. 1986. Interpreting long-term changes in benthic community structure: a new protocol. Hydrobiologia 142:291-308.
- 2004-05-01 00:00:00 - Data from field samples was entered into an Access database for the Wells, Maine benthic SPI survey. A query was developed to review sediment data from all grab sampling stations. See Entity and Attribute section for more information on data collected. A shapefile was created using the field data in the Access database to show spatial trends in benthic community distribution in the two rivers.
(describe or provide URL of description):
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
- 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
- 5.2. Quality control procedures employed
- 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.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
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.
Alternately, the data can be obtained by contacting the Wells National Estuarine Research ReserveAddress: 342 Laudholm Farm RoadWells, Maine 04090 Phone: (207) 646-1555;
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.