Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:24251 | Published / External
This is an outdated version of the NOAA Data Management Plan template. 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. Please see the Data Management Plan Help Guide to learn more.
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 project examines an eastern Pacific fish assemblage associated with a 2.5 hectare coral reef located within the boundaries of Coiba National Park, Panama. From 1980 to 2010, consistent, quantitative coral reef and fish survey monitoring methods have been applied at Uva Island reef, which lies in area that has received virtually no fishing pressure or watershed development over the past 80 years. Data stored in Excel files.
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.
Uva Island reef, Panama
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):
Process Steps:
- 2011-05-01 00:00:00 - Coral monitoring. Assessment of coral cover on the Uva reef began in 1974 (Glynn 1976) and has continued to 2010. This was accomplished by chain transects and by sampling fixed 1 m2 plots (n = 10) as well as a single 4 x 5 m2 plot bordering the fish transects. The 4 x 5 m plot was established by R.H. Richmond immediately following the 1982-83 ENSO event when coral cover on the fore-reef was reduced to near-zero values. For this study, percent coral cover was determined only from the 4 x 5 m fixed plot. Benthic composition of 1 m2 sections were drawn by divers underwater and then digitized in the lab using a flatbed scanner, Adobe Photoshop and ImageJ software. Percent coral cover was determined by dividing the number of pixels representing coral within a quadrat by the total number of pixels in that quadrat. For each year, all 20 1 m2 quadrats within the 4 x 5 m plot were averaged to determine the total mean percent coral cover. Fish monitoring. Fish species numbers and abundances were quantified via snorkeling along the NW (seaward) side of the Uva Island patch reef. The surveys were conducted along 20 x 40 m transects with the longest axis oriented in the NW-SE direction, i.e., along the depth gradient and perpendicular to the zonation of fore-reef corals. The shallow ends of the transects were located in abundant pocilloporid growth (with scattered reef frame blocks) of relatively high relief; the central sections were dominated by live stands of Pocillopora spp. of low relief; the deep ends contained mostly coral rubble with a few isolated patches of massive corals. These substrate zonation patterns characterized the transect areas when sampling was first conducted. Live coral cover returned gradually from near complete loss following the 1982-83 El Ni¿o to pre-disturbance levels as of March 2010. All surveys were conducted at or near high tide. At this time, the shallow ends of the transects were 3-4 m deep and their deep ends 5-7 m. The spring tidal range in this area is 3.3 m. Surveys were conducted when the lateral visibility was =10 m. Snorkeling was carried out along the major axis of transects in a straight line pattern to permit a clear view of the transect boundaries. Fish counts were made by snorkeling slowly, avoiding quick movements or splashing, down the long axis of the transect. Species and abundance of individuals > 15 cm total body length present within the transects were recorded on a slate. Sampling time was standardized at 8 minutes per transect (per 800 m2). The sides of adjacent transects were separated by 3 m and the time interval between successive visual sampling was approximately 5 minutes. Fishes did not seem to be either attracted or repelled by the observer. (Citation: LONG-TERM PATTERNS OF DIVERSITY AND ABUNDANCE IN AN EASTERN PACIFIC REEF FISH ASSEMBLAGE: REEF FISH RESPONSE TO CORAL RECOVERY )
(describe or provide URL of description):
Samples were taken over various days and times to ensure that values observed were not influenced by date or time or observer/recorder of the data
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)
(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.
All data Set files are present in downloadable zip file
The files format of the data files are defined in the metatdata.
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.
NCEI archive
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
It is already archived
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.