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
The ACFHP database consist of three primary data tables, joined within SQL Server, a relational DBMS: 1. The Bibliographic table provides information on over 500 selected documents and data sources on Atlantic coastal fish species and habitats. 2. The Assessment table provides information on habitat condition indicators, threats, and conservation actions. 3. The Geospatial table provides location references for information recorded in the Bibliography and Assessment tables. In addition, a separate table enables the many-to-many relationship between bibliographic entries and locations.
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.
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):
- 2009-01-01 00:00:00 - The GIS base layer was developed in ArcGIS, and is subdivided into four zones - watersheds, estuaries, nearshore marine, and offshore marine. It is based on NOAA's Coastal Assessment Framework (CAF), including estuarine waterbodies and their associated watersheds. The Coastal Assessment Framework is a set of digital GIS layers, with lineage back to an earlier data atlas known as the National Estuarine Inventory (NOAA 1985). The NEI and CAF further subdivide estuarine waters into salinity zones (tidal fresh, mixing, and seawater), but these subdivisions were not used for the ACFHP spatial framework. Additional polygons were added for both State and Federal marine waters, based on legally-vetted boundary layers in the Multipurpose Marine Cadastre (MMC). State waters extend to the 3 nautical mile limit, and Federal waters extend to the 200 nmi Exclusive Economic Zone (EEZ). Regional breaks were selected at Cape Cod, Cape Hatteras, and Cape Canaveral, creating four regions: North Atlantic, Mid-Atlantic, South Atlantic, and South Florida, consistent with generally accepted biogeographic classifications. The estuarine, watershed, and marine polygons were merged into a single polygon layer - 195 polygons total, preserving their attributes for region, state, zone (watershed, estuarine, marine), and waterbody name. (Citation: NOAA's Coastal Assessment Framework)
(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.
- 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.
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.
Hardcopy tech memo or other documentation, or custom spreadsheet versions of data are available upon request from: David Moe Nelson NOAA N/SCI-1 1305 East-West Hwy, 9th Floor Silver Spring MD 20910 phone 301-713-3028 x154 email firstname.lastname@example.org; Tech. Memo. pdf, and bibliographic and assessment information may be downladed directly from the homepage at the URL provided. Electronic spreadsheet versions may be requested from: David Moe Nelson NOAA N/SCI1 1305 East-West Hwy, 9th Floor Silver Spring MD 20910 phone 301-713-3028 x154 email email@example.com; go to http://www8.nos.noaa.gov/bhv/spatbibindex.html . The links to the left launch these three query modules: Bibliographic Query - using a set of sequential parameters in pull-down menus, this query generates a list of documents and data sources pertaining to a particular water body. Output includes standard bibliographic information such as Title, Year, Authors, Organization, and Publication Info - as well as Habitat Type, Information Type, and Web Location (if an item is available, a "Click Here" link is provided). Assessment Query generates a list of indicators (measures of habitat condition), threats (or stressors), and/or actions (conservation recommendations), for a specified waterbody or watershed, with sources cited. Geospatial Query provides a GoogleMaps interface to launch a query of either the bibliographic or assessment information.;
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.