Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:51895 | 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
This data set contains sensitive biological resource data for federally and/or state endangered and threatened plants, rare state plants, and sensitive ecological communities in the New York/New Jersey Metro Area, Hudson River, and South Long Island region. Vector polygons in this data set represent federally and/or state endangered and threatened plant, rare state plant, and sensitive ecological community occurrences. Species-specific abundance, seasonality, status, life history, and source information are stored in associated data tables (described below) designed to be used in conjunction with this spatial data layer. This data set is a portion of the ESI data for the the NY/NJ Metro Area, Hudson River, and South Long Island region. As a whole, the ESI data characterize the marine and coastal environments and wildlife by their sensitivity to spilled oil, and include information for three main components: shoreline habitats, sensitive biological resources, and human-use resources.
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:
- 2015-11-01 00:00:00 - Threatened, endangered, and rare plants and rare plant communities were mapped primarily with data from the New York Natural Heritage Program (NY NHP) and the New Jersey Natural Heritage Program (NJ NHP). NJ NHP grid map contains cells that vary from 358-372 acres in size with a table of rare plant species and ecological communities that occur within each cell. Maritime holly forest, a globally rare forest type, was mapped on Fire Island and Sandy Hook using vegetation data provided by Fire Island National Seashore and Gateway National Recreation Area (GATE), respectively. The distribution of seabeach amaranth (NJ endangered, NY state and federally threatened) on Sandy Hook was mapped using information provided by GATE. Non-federally listed, state protected plant names were generalized to .Endangered Plant., .Threatened Plant., and .Rare Plant.. Although they do not have a listing status in NY, rare mosses were included as .Rare Plant. locations since they occur in wetlands and are vulnerable to oil spills. Small polygons (less than 123 m^2) representing plant locations in the NY NHP database were converted to points so that they would be visible on the ESI atlas maps. Critically imperiled, imperiled, and vulnerable wetland and upland plant community types were generalized as .Rare Upland Community. or .Rare Wetland Community. except for the maritime holly forest, vernal pool, and coastal dune woodland community types. There was a high degree of overlap of certain wetland community types in the NY NHP Communities data with ESI wetland polygons (see shoreline habitat section). NY NHP wetland types that were already represented in the ESI wetland polygon data were not included in the habitat feature class. Rocky summit, cliff, and talus upland community types were not mapped due to their low vulnerability to oil spills. Vernal pools provide important amphibian breeding habitat and these were mapped with NY NHP Communities data, NJ DEP Vernal Habitat data, and Scenic Hudson.s Vernal Pools data. The above digital sources were compiled by the project biologist to create the HABITATS data layer. Depending on the type of source data, two general approaches are used for compiling the data layer: 1) digital data layers are evaluated and used "as is" or integrated with the ESI base map features (ESIP, HYDROP, ESIL) 2) information gathered during initial interviews and from hardcopy sources are compiled and digitized using ESI base map features. See the Lineage section for additional information on the type of source data for this data layer. The ESI, biology, and human-use data are compiled into the standard ESI digital data format. A second set of interviews with participating resource experts are conducted to review the compiled data. If necessary, edits to the HABITATS data layer are made based on the recommendations of the resource experts and digital data are created.
(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)
- 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.2. Name of organization of facility providing data access
- 7.2.1. If data hosting service is needed, please indicate
- 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.
Data can be accessed by downloading the zipped ArcGIS geodatabase from the Download URL (see Distribution Information). Questions can be directed to the ESI Program Manager (Point Of Contact).
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.