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:
La Parguera, Puerto Rico (2001 - Present) and Guanica, Puerto Rico (2012) fish assessment and monitoring data: 2012
1.2. Summary description of the data:

This fish and benthic composition database is the result of a multifaceted effort described below. The intent of this work is five fold: 1) To spatially characterize and monitor the distribution, abundance, and size of both reef fishes and macro-invertebrates (conch, lobster, Diadema); 2) To relate this information to in-situ data collected on associated benthic composition parameters; 3) To use this information to establish the knowledge base necessary for enacting management decisions in a spatial setting; 4) To establish the efficacy of those management decisions; and 5) To work with the National Coral Reef Monitoring Program to develop data collection standards and easily implemented methodologies for transference to other agencies and to work toward standardizing data collection throughout the US states and territories. Toward this end, the Center for Coastal Monitoring and Assessment's Biogeography Branch (BB) has been conducting research in Puerto Rico and the US Virgin Islands since 2000 and 2001, respectively. It is critical, with recent changes in management at both locations (e.g. implementation of MPAs) as well as proposed changes (e.g. zoning to manage multiple human uses) that action is taken now to accurately describe and characterize the fish/macro-invertebrate populations in these areas. It is also important that BB work closely with the individuals responsible for recommending and implementing these management strategies. Recognizing this, BB has been collaborating with partners at the University of Puerto Rico, National Park Service, US Geological Survey and the Virgin Islands Department of Planning and Natural Resources. To quantify patterns of spatial distribution and make meaningful interpretations, we must first have knowledge of the underlying variables determining species distribution. The basis for this work therefore, is the nearshore benthic habitats maps (less than 100 ft depth) created by NOAA's Biogeography Program in 2001 and NOS' bathymetry models. Using ArcView GIS software, the digitized habitat maps are stratified to select sampling stations. Sites are randomly selected within these strata to ensure coverage of the entire study region and not just a particular reef or seagrass area. At each site, fish, macro-invertebrates, and benthic composition information is then quantified following standardized protocols. By relating the data collected in the field back to the habitat maps and bathymetric models, BB is able to model and map species level and community level information. These protocols are standardized throughout the US Caribbean to enable quantification and comparison of reef fish abundance and distribution trends between locations. Armed with the knowledge of where "hot spots" of species richness and diversity are likely to occur in the seascape, the BB is in a unique position to answer questions about the efficacy of marine zoning strategies (e.g. placement of no fishing, anchoring, or snorkeling locations), and what locations are most suitable for establishing MPAs. Knowledge of the current status of fish/macro-invertebrate communities coupled with longer term monitoring will enable evaluation of management efficacy, thus it is essential to future management actions. Starting in 2010, the regular La Parguera survey area was extended eastward to encompass the Guanica Bay region. The purpose of this modification was to conduct a baseline assessment of fish, macro-invertebrates (conch, lobster, Diadema) and benthic communities in support of Guanica Bay watershed restoration, and then to monitor changes over time. A watershed management plan was developed in 2008 by the Center for Watershed Protection, in cooperation with various Divisions of Puerto Rico DNER and NOAA, to identify priority management recommendations and implementation strategies for the Guanica watershed based on input from local experts, observations from on-the-ground assessments, and a comprehensive review of existing studies and applicable local rules and regulations. The Guanica watershed was selected for the watershed planning project because it is a priority of the Commonwealth for conservation of the near shore coral reef habitat, which has been steadily declining in condition during the past several decades. Information collected during this survey will provide critical baseline information for the watershed and adjacent coral reefs which will be used to evaluate the effectiveness of the restoration project implemented. More information on the Guanica Bay project can be found at: http://ccma.nos.noaa.gov/ecosystems/coralreef/guanica.aspx.

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:
2001-01 to 2012-09
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: -67.14, E: -66.86, N: 17.98, S: 17.88
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.)
No information found
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:
NCCOS Scientific Data Coordinator
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:
NCCOS.data@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:
No information found
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:
NCCOS Scientific Data Coordinator
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?
No information found
4.2. Approximate percentage of the budget for these data devoted to data management (specify percentage or "unknown"):
No information found

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):

Process Steps:

  • 2012-09-01 00:00:00 - Once in the field, the boat captain navigates to previously selected sites using a handheld GPS unit. On-site, divers are deployed and maintain contact with each other throughout the entire census. One diver is responsible for collecting data on the fish communities utilizing the belt-transect visual census technique over an area of 100m2 (25m length X 4m width). The belt-transect diver obtains a random compass heading for the transect prior to entering the water and records the compass bearing (0-360o) on the data sheet. Visibility at each site must be sufficient to allow for identification of fish at a minimum of 2m away. Once reasonable visibility is ascertained, the diver attaches a tape measure to the substrate and allows it to roll out for 25m while they are collecting data. Although the habitat should not be altered in any manner by lifting or moving structure, the observer should record fish seen in holes, under ledges and in the water column. To identify, enumerate, or locate new individuals, divers may move off the centerline of the transect as long as they stay within the 4m transect width and do not look back along area already covered. The diver is allowed to look forward toward the end of the transect for the distance remaining (i.e. if the diver is at meter 15, he can look 10 meters distant, but if he is at meter 23, he can only look 2 meters ahead). On-site, no attempt to avoid structural features within a habitat such as a sand patch or an anchor should be made as these features affect fish communities and are "real" component of the habitats. The only two instances where the transect should deviate from the designated path is to stay above 110 ft (limitations imposed by diving) or while surveying mangrove habitats. In mangrove areas, the diver swims close to the prop roots and looks as far into the mangroves as possible; up to 2m and then out to the edge of the mangrove overhang such that the total area surveyed is still 100m2. In this case, some of the survey may necessarily fall on seagrass habitat. This is allowed as the mangrove habitat is defined as a transition zone habitat. The transect should take 15 minutes regardless of habitat type or number of animals present. This allows more mobile animals the opportunity to swim through the transect, and standardizes the samples collected to allow for comparisons. Data are collected on the following: 1) Logistic information - diver name, dive buddy, date, time of survey, site code, transect bearing. 2) Taxa presence - as the tape roles out at a relatively constant speed, the diver records all fish species to the lowest taxonomic level possible that come within 2m of either side of the transect. To decrease the total time spent writing, four letter codes are used that consist of the first two letters of the genus name followed by the first two letters of the species name. In the rare case that two species have the same four-letter code, alternate four-letter codes are used to distinguish between the species. These alternate codes contain the first two letters of the genus, the first letter of the species and then the first letter in the species name that differs from the other code. If the fish can only be identified to the family or genus level then this is all that is recorded. If the fish cannot be identified to the family level then no entry is necessary. 3) Abundance and size - the number of individuals per species is tallied in 5cm size class increments up to 35cm using visual estimation of fork length. If an individual is greater than 35cm, then an estimate of the actual fork length is recorded. 4) Photos - individuals too difficult to identify or unique in some manner may be photographed for later clarification. (continued...)
  • 2012-09-01 00:00:00 - (continued from above) Data Caveats: Overtime, some changes were made to the stratified random site selection process as follows: 1) Habitat strata initially consisted of hard bottom, sand, and seagrass. Sand and seagrass strata were subsequently combined into one soft bottom strata at all three locations (Puerto Rico, St. Croix, and St. John). This action was taken after the February 2002 mission to Puerto Rico. In Puerto Rico, mangroves are sampled in addition to the above strata. 2) In addition to the habitat strata, Puerto Rico originally contained three strata representing levels of protection from waves and currents. These strata were the Bank Shelf, Outer Lagoon and Inner Lagoon. This was changed beginning with the December 2002 mission to simply Protected and Unprotected. After the January 2005 mission, strata of Protected and Unprotected was removed leaving only habitat strata. 3) A small subset of sites were resampled during each mission through June 2002 in Puerto Rico. These station names contain the letter 'P' indicating they are permanent stations. 4) Starting in 2010, the survey area was extended further east to encompass the Guanica Bay region. The study area was divided into five regions based on a combination of the regular Parguera survey area and three Guanica strata previously designated by CCMA for contaminant and nutrient sampling. As such, 2010 and 2011 sites prefixed by 1-3 are located within the La Parguera study area, while those prefixed by 2-5 are located within the Guanica study area. Process_Date 200101 - 201209 (end continuation)
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):
No information found

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.6. Type(s) of data
  • 1.7. Data collection method(s)
  • 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?
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?
No information found
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 information found
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:
No information found
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:
No information found
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:
No information found
7.4. Approximate delay between data collection and dissemination:
No information found
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)
No information found
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):
National Centers for Coastal Ocean Science - Silver Spring, MD
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:
No information found
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
No information found

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