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:
Vallisneria 2003-2004
1.2. Summary description of the data:

We compared nekton use of Vallisneria americana Michx. (submerged aquatic vegetation, SAV) with marsh shoreline vegetation and subtidal nonvegetated bottom (SNB) using a 1-m2 drop sampler in the oligohaline area of Barataria Bay, Louisiana. Mean densities of most abundant species were significantly different among six habitat types. Harris mud crab Rhithropanopeus harrisii, Ohio shrimp Macrobrachium ohione, blue crab Callinectes sapidus, daggerblade grass shrimp Palaemonetes pugio, white shrimp Litopenaeus setiferus (fall), rainwater killifish Lucania parva, naked goby Gobiosoma bosc, code goby Gobiosoma robustum (fall), speckled worm eel Myrophis punctatus (fall), and gulf pipefish Syngnathus scovelli (spring), were much more abundant, and species richness also was greater, in Vallisneria than over SNB. Vallisneria supported densities of most species that were similar to those in marsh vegetation, although naked goby and gulf pipefish were more abundant in Vallisneria, and speckled worm eel and saltmarsh topminnow Fundulus jenkinsi were more abundant in marsh. Within the Vallisneria bed, densities of Harris mud crab, rainwater killifish, and speckled worm eel were higher at sites near the marsh (SAV Inside Edge) than at sites more distant from the marsh (SAV Outside Edge), and Ohio shrimp (fall) densities were higher in the interior of the bed than along the edges. The mean size of blue crab was larger in marsh than Vallisneria and larger in Vallisneria than SNB. White shrimp did not differ in size among habitat types. Vallisneria beds may provide an important nursery habitat for young blue crab and white shrimp that use oligohaline estuarine areas. These SAV beds can provide an alternative structural habitat to emergent vegetation during periods of low water, because Vallisneria occurs in the subtidal and generally persists throughout the year on the Gulf coast. Species whose young thrive in low-salinity waters and also depend on structure would benefit most from Vallisneria habitat in estuaries.

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:
2003 to 2004
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: -90.22225, E: -90.20159, N: 29.52891, S: 29.52784

Gulf Of Mexico

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: YSI Model 51B meter American Optical temperature-compensated refractometer meter stick HF Scientific Model DRT100B turbidimeter
Platform: N/A
Physical Collection / Fishing Gear: 1.14 m diameter drop trap
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:
Lawrence P Rozas
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:
No information found
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:
Lawrence P Rozas
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
4.2. Approximate percentage of the budget for these data devoted to data management (specify percentage or "unknown"):
0

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:

  • After sample collection, field data were entered into an Excel spreadsheet or database file (DBF) using database manager software. A text file was created to describe these data and associated variables. Entered data were checked against the field sheets by two biologists to minimize entry errors. Samples were processed in the laboratory, sorted, specimens identified and measured, and information was entered into an Excel spreadsheet or DBF file. Files were printed out and compared against original data sheets by two biologists for data entry errors. Corrections were made at this time, the electronic file was saved, and a back-up copy made. Hard copies of the QCd files were printed and stored in the project folder along with the original field and laboratory data sheets. The electronic file was also sorted and examined by the Lab Supervisor or other project personnel in a variety of ways to look for outliers, missing data, and other potential errors. Verified data files were then saved electronically on the Galveston Laboratory server and backed-up as needed.
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):

Each sample was assigned a unique identification code. Field collected samples were tagged redundantly (e.g. one label inside of the collection vessel and a matching label attached to the outside of the vessel). The identifier and its associated information (e.g. date, location, habitat) was recorded on field data sheets. Once a sample arrived at the laboratory, the label remained with the sample throughout the various stages of sample processing. After data were entered into an Excel spreadsheet or similar database file, the information was printed out and compared against the field data sheets by two biologists. Corrections were made at this time and saved. The electronic file was also sorted and examined by the Lab Supervisor or other project personnel in a variety of ways to look for outliers, missing data, and other potential errors.

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:

  • 2.4. Point of Contact Email
  • 8.3. Approximate delay between data collection and submission to an archive facility
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:
Southeast Fisheries Science Center (SEFSC)
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
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:

The data will be available from a public web server once an access methodology has been developed.

7.4. Approximate delay between data collection and dissemination:
365
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):
Southeast Fisheries Science Center - Miami, FL
 
Location Of The Main Office Of The South East Fisheries Science Center
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

The data resides on a secure government network requiring multi-factor authentication for network access.

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