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 data set, in the table ALS.ALS_LANDINGS7278 contains annual and monthly quantities and values for all seafood products that are landed within the Southeast Region and sold by established seafood dealers and brokers. It complements the table ALS.ALS_LANDINGS. These types of fishery-dependent 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 and more recently by our State partner agencies under the Cooperative Statistics Program. These data are available on computer since the early 1960's. The quantities and values that are reported in this data set include the annual and monthly landings that were initiated in 1972. Between 1962 and 1971, the data for were collected annually and not monthly. See the sections on Links for the reference to the annual general canvass landings.
The general canvass landings from 1972-1976 include quantities and values for all marine commercial landings and are identified by species (usually the local or common name). 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). Information on the gear and area of capture is available for most of the landings statistics in the data set (please see Issues for exceptions); however, they are summary records and do not contain information on the quantities of fishing effort or identify the fishermen or vessels that caught the fish or shellfish. This table contains data from FL-TX for the years 1972-1976. The ALS.ALS_LANDINGS table contains data for GA-NC for the same period as well as all the more recent monthly data.
In the early years, the data in this data set were collected by field agents employed by the Southeast Fisheries Science Center and assigned to local fishing ports. The field agents canvassed the seafood dealers and recorded the quantity and value for each species or species category from the dealer?s receipts. Based on interviews with dealers and fishermen as well as their own detailed knowledge of the fishing activity in the area, the agents would determine the type of fishing gear and area where the fishing occurred.
In addition, summarized data are extracted from the NOAA-SEFSC Gulf Shrimp System for commercial landings of shrimp species that are landed at ports in the coastal area of the Gulf of Mexico.
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.
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.
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.
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):
Data were from dealer invoices or landings reports submitted to NOAA-SEFSC, either by mail or collected by port agents. Data entered to digital table on computer and visually proofed. Also lookup tables were used for codes.
(describe or provide URL of description):
Visual proofing, look-up tables for codes
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.
- 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.
Password restricted. To access confidential data under Magnuson-Stevens Act) a completed non-disclosure agreement must be on file with NOAA-SEFSC. Otherwise Data that are submitted as confidential can be released to the public under the following circumstances:
1. Combined or aggregated data. Confidential data can be released if the data are aggregated or summarized in a manner that prevents the identification of the person or organization that submitted the data. The "rule of three" and identification of majority allocations" are the primary data suppression methods.
2. Obscure (scramble) or remove the data identifier. For some types of data, confidential data Can be released as non-confidential if the identity of the person, vessel, company, etc. that submitted the data is not included or is scrambled as part of the data that are released.
3. Submitter. Confidential data collected under federal authority Can be released to the original entity (person, vessel, business, etc.) that sUbmitted the data.
4. Confidential data waived. The protection of confidential data can be waived by the person or business that submitted the data.
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.
Read and sign for NOAA Administrative Order 216-100
Read and sign System Access Application (see URLs)
Data are complete
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.
75 Virginia Beach Drive Miami, FL 33149
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
userid, password, Oracle Grants by DBA
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.