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:
Commercial Landings Data monthly summaries (Dealers)
1.2. Summary description of the data:

This data set contains pounds and value for all seafood products that are landed and sold by established seafood dealers and brokers in the SE Region of the US mainland. In the US Caribbean, the landings are reported by permitted fishers. These types of data, referred to as the general canvass landings statistics, have been collected by the NOAA Fisheries Service, National Marine Fisheries Service and its predecessor agency, the Bureau of Commercial Fisheries. These data are available on computer since the mid 1920s. The quantities and values that are reported in this data set include monthly landings that were initiated in 1972. Between 1926 and 1971, data were collected annually and not monthly. Mixed annual and monthly data occur from 1972-1976 according to State and year. The general canvass landings include quantities and value for all commercially caught marine species and are identified by species or species group. These data are collected from or reported by every seafood dealer or broker that is licensed by each state in the Southeast Region (North Carolina through Texas). In addition, information on the gear and area of capture is available for most of the landings statistics in the data set except for Florida 1977-1996 and Louisiana 1992-1999. However, because these data are summaries, they do not contain information on the quantities of fishing effort or identifications of the fishermen or vessels that caught the fish or shellfish. In early years, these data were collected by field agents employed by the Southeast Fisheries Science Center and assigned to local fishing ports. These individuals would canvass the seafood dealers and record the quantity and value for each species or species category from the sales receipts maintained by the seafood dealers. Based on their detailed knowledge of the fishing activity in the area, the agents would estimate the type of fishing gear and area where the fishing was likely to have occurred. It should be noted that landings by gear and water body (fishing area) does not reside in the monthly landings data set for Florida for the years, 1977-1995, Louisiana 1990-1999, and Texas (for gear) from 1993 to present (this is subject to change for years 2008 and more recent). Annual landings by gear, water body and distance from shore are available in the Annual General Canvass data for Florida. More detailed information on the caveats associated with these data is provided in the Issues section. In more recent years, the states in the Southeast Region began to implement trip ticket programs that required the licensed seafood dealer/brokers to report the landings of all seafood products. A trip ticket program was initiated in Florida in 1985, in North Carolina in 1994, in Louisiana in 1999, in Alabama in 2000, and in Texas in 2007. In addition to the quantities of these landings, the states require dealers to report the price, the type of gear and the fishing area for each trip. Through cooperative agreements with each of the states, monthly summaries of the states trip ticket programs are provided to the Southeast Fisheries Science Center (SEFSC) and are included in the general canvass landings data set. In addition, summarized data are extracted from the NOAA-SEFSC Gulf Shrimp System for commercial landings of shrimp species that are landed at port in the coastal area of the Gulf of Mexico.

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?
Ongoing series of measurements
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:
1972 to Present, 1960 to Present, 1960 to Present, 1960 to Present
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: -98, E: -72, N: 37, S: 24

The Southern US Atlantic coastal waters from North Carolina to the Florida Keys (Monroe County) out to 200 nautical miles and the US Gulf of Mexico coastal waters from Monroe County, FL through Texas out to 200 nautical miles. The 200 mile limit is the outer boundary of the US Exclusive Economic Zone.

W: -100, E: -40, N: 30, S: 0

Gulf Of Mexico And South Atlantic Ocean

W: -100, E: -40, N: 30, S: 0

Gulf Of Mexico And South Atlantic Ocean

W: -100, E: -40, N: 30, S: 0

Gulf Of Mexico And South Atlantic Ocean

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:
Jade Chau
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:
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:
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:
Jade Chau
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?
4.2. Approximate percentage of the budget for these data devoted to data management (specify percentage or "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:
Dealers supply invoices, either mailed, or collected by port agent (historical) or electronically (current) to State partner agencies. States process data and submit either to NOAA-SEFSC directly or through GSMFC or ASMFC. Data are then checked by NOAA and posted.

Process Steps:

  • Data are summarized trip level data data. Data are presented at the dealer and month level. Data are collected by states and made available to this system through the Gulf States Marine Fisheries Commission or through the Atlantic Coastal Cooperative Statistics Program. Data are summarized and loaded to the Accumulated Landings System at SEFSC.
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):

Range checks and validation against historical distributions.

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?
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:
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?
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?
7.1.2. If there are limitations to public data access, describe how data are protected from unauthorized access or disclosure:

Waiver Needed

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

These standards and procedures apply to all employees of the SEFSC that need access to confidential fisheries statistics. This includes full time or term employees, contractors, volunteers, and or other employees associated with the SEFSC, but not directl

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

Confidentiality. This data is currently wavered under the current NOAA guidelines for relational databases.

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)
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:
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 database server only accessible through the NMFS network requiring separate multi-factor authentication for both network and database 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