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:
Large Pelagic Carcass Weights (Vessels)
1.2. Summary description of the data:

Swordfish have been a commercially caught species since the early 1800s. During this early stage of the fishery, harpoon was the principal gear and the fishing was limited to the northeastern coast of the United States during the summer and fall months. In the early 1960s, Norwegian and Japanese vessels began fishing these areas with surface longline gear. U.S. fishermen soon began using longline gear and the fishing quickly spread to the western North Atlantic and became a year-round fishery. Landings of swordfish steadily increased from this region while the fishing moved south as new vessels entered the fishery in areas from North Carolina southward to Florida and the Gulf of Mexico. Surface longline gear soon became the predominant gear and now accounts for about 98 percent of the U.S. commercial swordfish catch in the North Atlantic. Before the mid-1980s, only limited data on the fishing activities from the U.S. pelagic longline fleet were collected. Data were collected by various state agencies, Fishery Management Councils, and university biologists from 1978 to 1983. These data consisted of weights for individual swordfish (headed, gutted and tailed) recorded on the weigh-out receipts (tally sheets) for the sales to vessels for an individual trip. In 1984, this database became the responsibility of the National Marine Fisheries Service, Southeast Fisheries Center (SEFSC). As part of this transition, the data were standardized and entered into a computer database. In order to expand the coverage, biologists at the SEFSC contacted vessel captains/owners and fish dealers and requested that they voluntarily submit their tally sheets to the SEFSC for use in scientific investigations of the swordfish fishery. All of the data are coded and stored for the individual vessel that caught the fish. Quality control procedures established to compare with data previously entered to avoid duplication. Although swordfish were the primary commercial species caught and recorded on the sales receipts, the weights of other species were also listed on the tally sheets. Prior to 1985, the weigh-out data for the other (non-swordfish) species were not recorded. Beginning in 1986, the SEFSC began to enter all the weigh-out data for all species listed on the tally sheets received. The individual dress weights of other species listed on tally sheets from earlier years were entered as well. Each record includes a vessel code, date of landing, state and port landed, code of the dealer purchasing the catch, gear fished, data source, location code of general fishing area, total hooks fished, days of actual fishing, total number of sets, and a species code along with the individual carcass weights for each species. All records from a specific trip are identified by their respective vessel codes and date of landing. Prior to 1986, effort (hooks, days fished, number of sets) information was recorded from personal vessel logbooks voluntarily submitted by vessel captains/owners. Beginning in 1986, all pelagic longline vessels that actively fished are required to submit daily logbook set records for each trip. Based upon this information, fishing effort is determined and, subsequently, added to the longline database. The database contains information from the early 1960s (limited data) to the present and is almost exclusively comprised from data collected from the U.S. domestic pelagic longline fishery. Other gear types (harpoon, gillnet, handline, rod and reel, etc.) have been recorded from vessels voluntarily submitting the information or that were mandated to report by regulations in the past years. This database is continually updated as new information becomes available.

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:
1986 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: -100, E: -40, N: 30, S: 0

Gulf Of Mexico, Caribbean Sea, And Atlantic Ocean, North

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:
Matt Maiello
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:
Matthew.Maiello@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:
305-361-4574
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:
Matt Maiello
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"):
70

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:

  • Forms submitted by fishermen to SEFSC staff through paper logbooks. Data entry is done by an offsite contractor. SEFSC staff Q/C data into database housed in Miami.
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?
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.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: 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?
Yes
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:
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:

Read and sign System Access Application (see URLs) Contact DBA Daniel Leon at daniel.leon noaa.gov for userid password.

7.4. Approximate delay between data collection and dissemination:
60
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)
TO_BE_DETERMINED
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:
365
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