Search Help Show/Hide Menu

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.

URL of higher-level DM Plan (if any) as submitted to DM Plan Repository:
Always left blank

1. General Description of Data to be Managed

1.1. Name of the Data, data collection Project, or data-producing Program:
Saipan Coral Nursery Fragment Growth and Parent Colony Fragmentation with the Saipan Coral Nursery Pilot Project (SCNPP) in the Northern Mariana Islands (CNMI) since 2019
1.2. Summary description of the data:

The data described here result from parent colony fragmentation collection and the monitoring of the fragment growth in the coral nursery through the Saipan Coral Nursery Pilot Project (SCNPP). Parent colony survey data includes genus and species identification, collection site information including: latitude, longitude, reef name, reef zone, depth, and tag number.

Fragment growth data from the nursery includes: the nursery identifier, parent colony identifier, fragment code, genus and species name, presence/absence, and growth data.

Scoping surveys were conducted at potential parent colony collection sites around Saipan to confirm the presence of healthy target coral species for collection. Surveys were conducted in both Forereef and Lagoon reef types. Fragments were collected using an appropriate cutting tool from parent colonies of five target coral species including: Acropora. pulchra, A. globiceps, A. aspera, A. abrotanoides, and A. muricata. Wild abundance and nursery capacity determined the number of parent colonies collected for each species.

Coral fragments were, and continue to be measured by following a three-dimensional survey design, tagged with a unique identifier, and transported immediately to the nursery site where they are attached to the nursery structures using monofilament fishing line. Each nursery tree has a PVC backbone with 10 fiberglass arms, each containing 10 holes, holding a total of 100 corals per tree with monofilament line. The trees are secured to the sea floor by duckbill anchors.

All nursery fragments are monitored for growth, survival and health status through measurement utilizing athree-dimensional survey design and visual surveys. All parent colonies are surveyed at least once after fragment collection to assess the healing process.

The data from the Saipan Coral Nursery Pilot Project can be accessed online via the NOAA National Centers for Environmental Information (NCEI) Ocean Archive.

Taken From: Item Identification | Abstract
Notes: Only a maximum of 4000 characters will be included.
1.3. Is this a one-time data collection, or an ongoing series of measurements?
One-time data collection
Taken From: Extents / Time Frames | Time Frame Type
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.
1.4. Actual or planned temporal coverage of the data:
2019-06-06 to 2020-06-29, 2019-06-06 to 2020-12-02
Taken From: Extents | Time Frame - Start, Time Frame - End
Notes: All time frames from all extent groups are included.
1.5. Actual or planned geographic coverage of the data:
W: 145.725903, E: 145.726103, N: 15.240542, S: 15.240342

The Saipan Coral Nursery - ID: SCN_01 in the data

W: 145.68493, E: 145.79035, N: 15.27333, S: 15.10417

Parent colony fragmentation sites area

Taken From: Extents | Geographic Area Bounds, Geographic Area Description
Notes: All geographic areas from all extent groups are included.
1.6. Type(s) of data:
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
Table (digital)
1.7. Data collection method(s):
(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.)
No information found
1.8. If data are from a NOAA Observing System of Record, indicate name of system:
Always left blank due to field exemption
1.8.1. If data are from another observing system, please specify:
Always left blank due to field exemption

2. Point of Contact for this Data Management Plan (author or maintainer)

2.1. Name:
Steven McKagan
Taken From: Support Roles (Metadata Contact) | Person
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.
2.2. Title:
Metadata Contact
Always listed as "Metadata Contact"
2.3. Affiliation or facility:
Taken From: Support Roles (Metadata Contact) | Organization
Notes: The name of the Organization of the most recent Support Role of type "Metadata Contact" is used. This field is required if applicable.
2.4. E-mail address:
steven.mckagan@noaa.gov
Notes: The email address is taken from the address listed for the Person assigned as the Metadata Contact in Support Roles.
2.5. Phone number:
670-234-0004
Notes: The phone number is taken from the number listed for the Person assigned as the Metadata Contact in Support Roles. If the phone number is missing or incorrect, please contact your Librarian to update the Person record.

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.

3.1. Name:
Steven McKagan
Taken From: Support Roles (Data Steward) | Person
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.
3.2. Position Title:
Data Steward
Always listed as "Data Steward"

4. Resources

Programs must identify resources within their own budget for managing the data they produce.

4.1. Have resources for management of these data been identified?
Yes
4.2. Approximate percentage of the budget for these data devoted to data management (specify percentage or "unknown"):
Unknown

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.

5.1. Processing workflow of the data from collection or acquisition to making it publicly accessible
(describe or provide URL of description):

Lineage Statement:
The parent colony fragmentation methodology and coral fragment growth monitoring three-dimensional survey method, employed by the Saipan Coral Nursery Pilot Project team since 2019.

Process Steps:

  • Fragmentation of Parent Colonies Using existing data on habitat type, coral cover, and community composition, we first developed maps of likely collection sites for staghorn corals within the Saipan lagoon and along the shallow forereefs of Saipan. Based on these data and maps, we conducted approximately 10 scoping surveys at potential collection sites to confirm the presence of suitable colonies of target species for collection. Fragment were then collected from parent colonies from 16 A. pulchra, eight A. globiceps, eight (putative) A. aspera, four A. abrotanoides, and four A. muricata parent colonies. The number of parent colonies collected for each species was dictated by abundance in the environment (i.e., ability to find colonies across collection sites) and nursery capacity. To capture as much of the local genetic diversity as possible, fragments were collected from parent colonies from 12 geographically disparate sites around Saipan. During collections, we took precautions to minimize potential negative impacts on wild populations, collected fragments, and reef habitat, by adhering to procedures based on best management practices developed over the last ten years in the Caribbean and Atlantic. Only healthy, “adult” (>10 cm diameter) colonies were selected as donors. Corals with any sign of disease, predation, or other ongoing stress, were not fragmented. No more than 10% of any individual parent colony was collected and fragments were collectured using an appropriate cutting tool for the size and shape of branch (e.g. wire cutters, small shears, chisel, etc.). Cuts were made as cleanly as possible to promote rapid lesion healing and recovery and fragments are cut between 3 cm to 5 cm in length. All parent colonies were tagged for future monitoring to assess impacts of fragmentation on parent colonies. Each parent colony is monitored post-sampling at least one time to assess health.
  • The Coral Nursery and Fragment Growth Monitoring After sampling the coral fragments from the parent colony, each fragment is immediately measured, tagged with a unique identifier, and transported immediately to the nursery site where they are attached to the nursery structures using monofilament fishing line. During transport, the fragments are kept submerged in seawater and protected from direct sunlight to maintain temperature and minimize stress. Three colony dimensions are measured: length (L; maximum colony diameter), width (W; maximum diameter perpendicular to the length axis), and height (H; maximum diameter of the plane perpendicular to the L/W plane). Individual branch lengths are measured as the length of the branch from the apex to the base, down the center axis of the branch (Johnson et al. 2011). All measurements are taken using a ruler or vernier calipers and recorded to the nearest 0.1 cm. This survey method is conducted initially during fragment sampling from the parent colony and is repeated over time, once the fragment is in the nursery, monitoring for growth, survival, and health status. Each nursery tree has a PVC backbone with 10 fiberglass arms, each containing 10 holes, holding a total of 100 corals per tree with monofilament line. The trees are secured to the sea floor by duckbill anchors. After installation, the nursery trees are cleaned monthly. Wire and plastic brushes are used to scrub algae off of all structures, and monofilaments lines are wiped cleaned with scouring pads or gloves. During each cleaning effort, all structures and hardware are checked thoroughly for any issues or needed repairs or maintenance.
5.1.1. If data at different stages of the workflow, or products derived from these data, are subject to a separate data management plan, provide reference to other plan:
Always left blank
5.2. Quality control procedures employed
(describe or provide URL of description):

Observers review all data, including metadata, on the day of collection and again at data entry to check for errors. Additional QC procedures are built in to the database and include formatting and value checks to minimize entry of erroneous information. A final check is conducted by the data manager.

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.

6.1. Does metadata comply with EDMC Data Documentation directive?
No
Notes: All required DMP fields must be populated and valid to comply with the directive.
6.1.1. If metadata are non-existent or non-compliant, please explain:

Missing/invalid information:

  • 1.7. Data collection method(s)
Notes: Required DMP fields that are not populated or invalid are listed here.
6.2. Name of organization or facility providing metadata hosting:
NMFS Office of Science and Technology
Always listed as "NMFS Office of Science and Technology"
6.2.1. If service is needed for metadata hosting, please indicate:
Always left blank
6.3. URL of metadata folder or data catalog, if known:
Always listed as the URL to the InPort Data Set record
6.4. Process for producing and maintaining metadata
(describe or provide URL of description):
Metadata produced and maintained in accordance with the NOAA Data Documentation Procedural Directive: https://nosc.noaa.gov/EDMC/DAARWG/docs/EDMC_PD-Data_Documentation_v1.pdf
Always listed with the above statement

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.

7.1. Do these data comply with the Data Access directive?
Yes
7.1.1. If the data are not to be made available to the public at all, or with limitations, has a Waiver (Appendix A of Data Access directive) been filed?
No
7.1.2. If there are limitations to public data access, describe how data are protected from unauthorized access or disclosure:

None

7.2. Name of organization of facility providing data access:
National Centers for Environmental Information - Silver Spring, Maryland (NCEI-MD)
Taken From: Support Roles (Distributor) | Organization
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.
7.2.1. If data hosting service is needed, please indicate:
Taken From: Data Management | If data hosting service is needed, please indicate
Notes: This field is required if a Distributor has not been specified.
7.2.2. URL of data access service, if known:
Taken From: Distribution Info | Download URL
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
7.3. Data access methods or services offered:

Data can be accessed online via the NOAA National Centers for Environmental Information (NCEI) Ocean Archive.

7.4. Approximate delay between data collection and dissemination:
Unknown
7.4.1. If delay is longer than latency of automated processing, indicate under what authority data access is delayed:

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.

8.1. Actual or planned long-term data archive location:
(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)
NCEI_MD
8.1.1. If World Data Center or Other, specify:
Taken From: Data Management | Actual or planned long-term data archive location
Notes: This field is required if archive location is World Data Center or Other.
8.1.2. If To Be Determined, Unable to Archive or No Archiving Intended, explain:
Taken From: Data Management | If To Be Determined, Unable to Archive or No Archiving Intended, explain
Notes: This field is required if archive location is To Be Determined, Unable to Archive, or No Archiving Intended.
8.2. Data storage facility prior to being sent to an archive facility (if any):
Pacific Islands Regional Office - Saipan, MP
 
The CNMI NOAA Field Office
Taken From: Physical Location | Organization, City, State, Location Description
Notes: Physical Location Organization, City and State are required, or a Location Description is required.
8.3. Approximate delay between data collection and submission to an archive facility:
Unknown
8.4. How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?
Discuss data back-up, disaster recovery/contingency planning, and off-site data storage relevant to the data collection

The data is captured on physical data sheets, then entered into an MS Access database, then data is exported and backed up onto google drive.

9. Additional Line Office or Staff Office Questions

Line and Staff Offices may extend this template by inserting additional questions in this section.

Always left blank