Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:79367 | 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
This dataset includes records of coral and sponge catch identified in trawl hauls made during the West Coast Groundfish Bottom Trawl Survey (WCGBTS). The WCGBTS is conducted at water depths ranging from 55 - 1,280 meters off the U.S. West Coast, including the States of Washington, Oregon, and California. The WCGBTS is conducted annually by NOAA Fisheries' Northwest Fisheries Science Center. These catch records are included in NOAA's Deep-Sea Coral Research and Technology Program (DSCRTP) National Database for Deep-sea Corals and Sponges.
NOAA DSCRTP compiles a national database of the known locations of deep-sea corals and sponges in U.S. territorial waters and beyond. Demersal and benthic fish occurrences that were recorded along with coral and sponge surveys are also included. The database is comprehensive, standardized, quality controlled, and networked to outside resources. The database schema accommodates both linear (trawls, transects) and point (samples, observations) data. The structure of the database is tailored to occurrence records of all the azooxanthellate corals, a subset of all corals, and all sponge species. Records shallower than 50 m are generally excluded in order to focus on predominantly deep-water species the mandate of the DSCRTP. The intention is to limit the overlap with light-dependent (and mostly shallow-water) corals.
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.
Extent of coral and sponge catch from the West Coast Groundfish Bottom Trawl Survey, 2001-2025
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:
Catch records of corals, sponges, and sea pens, along with relevant attributes were extracted from the FRAM Data Warehouse via a structured query language (SQL) script. Further processing occurred in the R programming language (v.3.4) to validate scientific names in the FRAM Data Warehouse with the World Register of Marine Species (WoRMS).
Process Steps:
- 2026-03-06 00:00:00 - Data Type: Occurrence (measured); Units: count; Observation Type: catch record; Sampling Instrument: trawl; Sampling and Analyzing Method: Numerous methods were utilized.; Data Quality Information: Points were checked in GIS to ensure no records were on land or locations far outside of North America and United States Territories. Completeness of Fields: In general, each catch record includes as much information as possible from the source database. Taxonomic Fields: As part of the QA/QC process, records were checked individually to ensure consistent use of valid taxonomic names. Each taxon identified in the 'ScientificName' field was cross-checked with currently valid scientific names listed in the World Register of Marine Species (WoRMS; http://www.marinespecies.org). If the taxon name in the original source was a valid name (e.g., Lophelia pertusa), this was recorded in the 'ScientificName' field and the WoRMS AplhaID for that taxon was recorded in the 'WormsID' field. The Taxon Rank was recorded and higher taxonomic classification names for that taxon were filled in according to WoRMS. In cases where the taxon name recorded in the original source was not a currently accepted name (e.g., Lophelia prolifera), the currently accepted valid name was recorded in the 'ScientificName' field and the taxon name from the original source was recorded in the 'VerbatimScientificName' field. Derived fields: For historical records, certain fields were derived from information in other fields. For example, the identification of the 'VernacularNameCategory' or 'VernacularName' for a valid 'ScientificName' was derived from a review of the literature for that or taxon.
- 2026-03-06 00:00:00 - Catch records of corals, sponges, and sea pens, along with relevant attributes were extracted from the FRAM Data Warehouse via a structured query language (SQL) script. (Citation: The Northwest Fisheries Science Center's West Coast Groundfish Bottom Trawl Survey: History, Design, and Description)
(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:
- 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.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.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.
*** No Warranty*** The user assumes the entire risk related to its use of these data. NOAA Fisheries is providing these data "as is" and NOAA Fisheries disclaims any and all warranties, whether express or implied, including (without limitation) any implied warranties of merchantability or fitness for a particular purpose. No warranty expressed or implied is made regarding the accuracy or utility of the data on any other system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty. It is strongly recommended that careful attention be paid to the contents of the metadata file associated with these data to evaluate dataset limitations, restrictions or intended use. In no event will NOAA Fisheries be liable to you or to any third party for any direct, indirect, incidental, consequential, special or exemplary damages or lost profit resulting from any use or misuse of this data.
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.
Montlake Facility
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.
