Data Management Plan
GUID: gov.noaa.nmfs.inport:58444 | Published / External
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 feature class resides within the BIOLOGY Feature Data Set of the Great Lakes - St. Clair / Detroit River System - 2019 ESI Geodatabase. It contains vector polygons representing FISH data for the St. Clair / Detroit River System in southeastern Michigan.
The study area includes a small portion of southern Lake Huron at its outlet, the St. Clair River (which flows out of Lake Huron), Lake St. Clair, the Detroit River (which flows into Lake Erie), a small portion of western Lake Erie, and adjacent lands and waters. These data sets contain sensitive biological resource data for freshwater fish species. Vector polygons, lines, and points in these data sets represent fish distribution, concentration areas, and spawning areas.
Species-specific abundance, seasonality, status, life history, and source information are stored in associated data tables (described in Entity Attribute Overview below) designed to be used in conjunction with this spatial data layer. This data set is a portion of the ESI data for the Great Lakes - St. Clair / Detroit River System.
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.
Bounding box for the St. Clair - Detroit River System area of interest in southeastern Michigan.
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:
Sources and Process Steps cited below in this metadata record include those used for two distinct areas of the Great Lakes: the Straits of Mackinac in northern Michigan, and the St. Clair / Detroit River System in southeastern Michigan. This is because these two study areas were initially combined into a single ArcGIS geodatabase, before being separated for publication. Some sources and process steps were used in both study areas, but there may be others that pertain to one study area and not the other. As a final procedural step to prepare the geodatabases for publication, the spatial data data corresponding to each respective area were clipped in ArcGIS according to the two distinct geographic study areas.
Process Steps:
- 2019-09-23 00:00:00 - Two main sources of data were used to depict fish distribution and seasonality for the FISH data layer: 1) personal interviews with resource experts from Bay Mills Indian Community, Chippewa Ottawa Resource Authority (CORA), Grand Traverse Band of Ottawa and Chippewa Indians, Little Traverse Bay Bands of Odawa Indians, Michigan Department of Natural Resources (DNR), Sault Ste. Marie Tribe of Chippewa Indians, U.S. Fish and Wildlife Service (USFWS), and U.S. Geological Survey (USGS) and 2) numerous published and unpublished reports and datasets. Fish species depicted in this atlas include species of conservation interest, or species of commercial, recreational, or ecological importance.
- 2019-09-23 00:00:00 - General distributions (FISH layer) – Fish general distributions were mapped using expert knowledge collected during workshops. Species included were determined by the experts for each of the basins in the study area. In Lakes Michigan and Huron, fish general distributions were mapped according to bathymetry. Polygons were created for the following depth zones: 0-10 m, 10-40 m, and >40 m, and species assemblages and appropriate life history stages and seasonalities were mapped in each zone. In the St. Clair – Detroit River System study area, fish general distributions were mapped according to geography. Species assemblages and appropriate life history stages and seasonalities were mapped to the following individual areas: St. Clair River, St. Clair Flats, Lake St. Clair, upper Detroit River, lower Detroit River, and western Lake Erie. Expert knowledge for mapping of fish general distributions was supplemented with information from reports and publications.
- 2019-09-23 00:00:00 - Concentration areas and tributaries (FISH layer) – Concentrations areas of various species were mapped using expert knowledge collected in workshops. Experts were asked to identify concentrations areas for any of the mapped species, and the species were mapped with a concentration of “HIGH” in polygons covering each of these areas. Experts also provided species lists and life history stages present in the tributaries of Lakes Michigan and Huron. Fish in larger tributaries were mapped as polygons, and fish in smaller tributaries and streams were mapped as lines.
- 2019-09-23 00:00:00 - One main source of data was used to depict fish distribution and seasonality for the FISHL data layer: personal interviews with resource experts from Grand Traverse Band of Ottawa and Chippewa Indians, Little Traverse Bay Bands of Odawa Indians, Michigan Department of Natural Resources (DNR), Sault Ste. Marie Tribe of Chippewa Indians, and U.S. Fish and Wildlife Service (USFWS). Experts provided species lists and life history stages present in the tributaries of Lake Michigan. Fish in larger tributaries were mapped as polygons, and fish in smaller tributaries and streams were mapped as lines.
- 2019-09-23 00:00:00 - Two main sources of data were used to depict fish point distribution and seasonality for the FISHPT data layer: 1) personal interviews with resource experts from Bay Mills Indian Community, Chippewa Ottawa Resource Authority (CORA), Grand Traverse Band of Ottawa and Chippewa Indians, Little Traverse Bay Bands of Odawa Indians, Michigan Department of Natural Resources (DNR), Sault Ste. Marie Tribe of Chippewa Indians, U.S. Fish and Wildlife Service (USFWS), and U.S. Geological Survey (USGS) and 2) numerous published and unpublished reports and datasets. Spawning locations – Point locations of spawning sites were provided by Great Lakes Aquatic Habitat Framework (GLAHF). Additional spawning point locations were included from documents, publications, and maps provided by DNR, Michigan SeaGrant, and USGS, and from personal communication with resource experts.
- 2019-09-23 00:00:00 - The above digital and/or hardcopy sources were compiled by the project biologist to create the FISH, FISHL, FISHPT data layers. Depending on the type of source data, three general approaches are used for compiling the data layers: 1) information gathered during initial interviews and from hardcopy sources are compiled onto U.S. Geological Survey 1:50,000 topographic quadrangles and digitized; 2) hardcopy maps are digitized at their source scale; 3) digital data layers are evaluated and used "as is" or integrated with the hardcopy data sources. 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 FISH, FISHL, and/or FISHPT data layers are made based on the recommendations of the resource experts, and final hardcopy maps and digital data are created.
- 2020-09-30 00:00:00 - Sources and Process Steps cited in this metadata record include those used for two distinct areas of the Great Lakes: the Straits of Mackinac in northern Michigan, and the St. Clair / Detroit River System in southeastern Michigan. This is because these two study areas were initially combined into a single ArcGIS geodatabase, before being separated for publication. Some sources and process steps were used in both study areas, but there may be others that pertain to one study area and not the other. As a final procedural step to prepare the geodatabases for publication, the spatial data data corresponding to each respective area were clipped in ArcGIS according to the two distinct geographic study areas.
- 2020-09-30 00:00:00 - Sources and Process Steps cited above in this metadata record include those used for two distinct areas of the Great Lakes: the Straits of Mackinac in northern Michigan, and the St. Clair / Detroit River System in southeastern Michigan. This is because these two study areas were initially combined into a single ArcGIS geodatabase, before being separated for publication. Some sources and process steps were used in both study areas, but there may be others that pertain to one study area and not the other. As a final procedural step to prepare the geodatabases for publication, the spatial data data corresponding to each respective area were clipped in ArcGIS according to the two distinct geographic study areas.
(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.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.