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 data described here result from near-shore shallow water Conductivity-Temperature-Depth (CTD) casts conducted at select sites around the Hawaiian Archipelago as part of the ongoing National Coral Reef Monitoring Program (NCRMP). These surveys were conducted by the NOAA Pacific Islands Fisheries Science Center (PIFSC), Ecosystem Sciences Division (ESD; formerly the Coral Reef Ecosystem Division) during ESD-led NCRMP missions to the Hawaiian Archipelago from 2013 to 2021. The CTD casts provide vertical profiles (30-m max depth, downcast only) of water column conductivity, temperature, and pressure with calculated depth, salinity, and water density. From 2013 to March 2019, a Sea-Bird Electronics, SBE19-plus instrument was used to collect this data, while in July 2019 to 2021, a RBR Concerto3 CTD was utilized.
The CTD was deployed from a small boat using a hand line and held at approximately 1-m depth for 1 minute to cycle water through the instrument and tubing (SBE19) or equilibrate the internal thermistor with ambient seawater (RBR). Afterward, data were collected by raising the CTD to just under the surface and then lowering in profiling mode at an even pace (descent rate ~0.5 to 0.75 meters per second) to a maximum depth of 30 m. Data processing was performed using Sea-Bird Scientific SBE Data Processing Software, RBR Ruskin software, and the R package "oce".
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 CTD observations in the Hawaiian Archipelago in 2013, 2015, 2016, 2019 and 2021 across the Main Hawaiian Islands (MHI; Oahu, Niihau, Molokai, Maui, Lanai, Kauai, Kahoolawe, Big Island) and Northwestern Hawaiian Islands (NWHI; French Frigate, Kure, Lisianski, Maro, and Pearl & Hermes).
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):
Following a 1 minute soak, CTDs are usually deployed 5-10 feet above the reef at depths ranging from 0-30 m at permanent monitoring sites established by the NOAA Fisheries, Ecosystem Sciences Division.
- The CTD was deployed from a small boat using a hand line and held at approximately 1-m depth for 1 minute to cycle water through the instrument and tubing (SBE19) or equilibrate the internal thermistor with ambient seawater (RBR). Afterwards, the CTD is lowered in profiling mode, at an even, hand-over-hand pace (descent rate ~0.5 to 0.75 meters per second) to a depth roughly 5-10 feet above the reef (maximum depth of 30m). Once the target depth is reached, the CTD is immediately pulled back on board. A GPS waypoint is taken at the beginning of the cast to mark the position and time. (Citation: RK Hoeke, JM Gove, E Smith, P Fisher-Pool, M Lammers, D Merritt, OJ Vetter, CW Young, KB Wong & RE Brainard (2009) Coral reef ecosystem integrated observing system: In-situ oceanographic observations at the US Pacific islands and atolls, Journal of Operational Oceanography, 2:2, 3-14, DOI: 10.1080/1755876X.2009.12027737)
- Raw CTD profile data from the SBE19+ are downloaded as .HEX files, converted to .CNV files using Sea-Bird Scientific SBE Data Processing Software and instrument-specific calibration data, processed in R using the R package "oce", and saved as .CSV files. Raw CTD profile data from the RBR Concerto3 are downloaded as .RSK files, processed using RBR Ruskin Software and the R package "oce", and saved as .CSV files.
(describe or provide URL of description):
The data is quality controlled by NOAA PIFSC Ecosystem Sciences Division (ESD) personnel after the data is downloaded from the instruments, prior to and after the data are migrated to the PIFSC enterprise Oracle database, and once again when the data are submitted to the NOAA National Centers for Environmental Information.
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.
(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.
Data can be accessed online via the NOAA National Centers for Environmental Information (NCEI) Ocean Archive.
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
The data is captured in several locations: files stored on the cruise server during the mission and the PIFSC network, and data are imported post-cruise into the PIFSC enterprise Oracle database. The cruise server is regularly backed up by the cruise data manager while at sea, and the PIFSC network is maintained and regularly backed up by PIFSC ITS.
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.