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:
Pacific Reef Assessment and Monitoring Program: Belt Transect Surveys of Corals at U.S. Pacific Reefs in 2008 (even size-class bins)
1.2. Summary description of the data:

The coral demographic data described here result from belt transect surveys conducted by the Pacific Islands Fisheries Science Center (PIFSC), Ecosystem Sciences Division (ESD)---formerly the Coral Reef Ecosystem Division---from January 27 to April 27, 2008 at coral reef sites in American Samoa and the Pacific Remote Island Areas as part of NOAA's Pacific Reef Assessment and Monitoring Program (Pacific RAMP), with funding from the NOAA Coral Reef Conservation Program (CRCP).

Surveys were conducted at fixed sites at depths ranging from 3-21 m. Sites were surveyed using belt transects to collect coral colony metrics. At each site, the surveyor listed and identified to the genus or species level, all coral colonies occurring within 0.5 sq. meters of each side of two, 25-m transect lines; and recorded the visually estimated size class to which the maximum diameter of each colony belonged (0-5 cm; 6-10 cm; 11-20 cm; 21-30 cm; etc. Size-class bins continue through 300 cm in 10-cm increments). These coral demographic data provide information on coral abundance (density, proportion occurrence, and total colony abundance), size distribution, and taxonomic richness.

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:
2008-02-18 to 2008-03-18, 2008-01-27 to 2008-02-09, 2008-03-26 to 2008-04-07
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: -171.092233, E: -168.13982, N: -11.04588, S: -14.559317

American Samoa, including Tutuila, Ofu and Olosega, Tau, Rose, and Swains.

W: -176.623989, E: -159.9731, N: 16.76325, S: -0.3818

Pacific Remote Island Areas, including Johnston, Kingman, Palmyra, Howland, Baker, and Jarvis.

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.)
Instrument: Not applicable
Platform: Not applicable
Physical Collection / Fishing Gear: Not applicable
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:
Annette M DesRochers
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:
annette.desrochers@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:
(808)725-5461
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:
Bernardo Vargas-Angel
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:
Belt transect survey method for corals, version B: even size-class bins, employed by the Ecosystem Sciences Division in 2008.

Process Steps:

  • At each site, benthic Rapid Ecological Assessment (REA) surveys of corals were conducted along dedicated transects lines deployed following a specific isobath. At each site, the surveyor listed and identified to the genus or species level, all coral colonies occurring within 0.5 sq.meters of each side of the transect lines; and recorded the visually estimated size class to which the maximum diameter of each colony belonged (0-5 cm; 6-10 cm; 11-20 cm, 21-30 cm; 31-40 cm; 41-50 cm; 51-60 cm; 61-70 cm; 71-80 cm; 81-160 cm; 81-90 cm; 91-100 cm; 101-110 cm; 111-120 cm; 121-130 cm; 131-140 cm; 141-150 cm; 51-160 cm; 161-170 cm; 171-180 cm; 181-190 cm ;191-200 cm; 201-210 cm; 211-220 cm; 221-230 cm; 241-250 cm; 251-260 cm; 261-270 cm; 291-300 cm). At Palmyra, site PAL-04, the protocol was amended to include all corals occurring within 1 sq. meter of each side of the transect lines
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):

Quality control of the data occurred at a few stages from data entry to data ingestion into the Oracle database. Observations, including species identification, were periodically checked during expeditions for consistency between and among divers, as well as verified against pictorial guides. Data entry was usually conducted on the same day as the surveys in an MS Access database. The data was quality controlled against the physical data sheets following data entry. Given the size of the data set, there remains some possibility of typographical or other errors.

Data was later migrated from the MS Access database to the PIFSC Oracle database.

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?
Yes
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:
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 Fisheries Science Center - Honolulu, HI
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 in several locations: physical data sheets, MS Access cruise databases, and the PIFSC Oracle database. The physical data sheets are housed at PIFSC. The MS Access cruise databases were regularly backed up by the cruise data manager while at sea. The PIFSC Oracle database is 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.

Always left blank