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
During the period of 2011-2012 a new series of logbook forms were developed for Puerto Rico and the US Virgin Islands. These forms were designed as the first step in providing improved commercial landings catch and effort data for the US Caribbean. They are multi-species trip-based forms with the Puerto Rico form divided by species groupings, and the USVI forms divided by gears with the primary species caught by each gear listed for each gear type. A new set of tables was created in 2011 to house US Caribbean Commercial Landings (CCL) data. These tables are separate from the Accumulated Landings System (ALS) data tables for the landings, although the data are currently passed on to the ALS tables on a regular bi-weekly basis from the CCL. The data in the CCL begins on January 1, 2012 for Puerto RIco and July 1, 2011 for the USVI. The tables are designed to house information from 4 different surveys, each having its own multi-species reporting form: 1 from Puerto Rico, 2 from St. Thomas/St. John (traps, other gear groups), and 1 from St. Croix (all gears). They also house data from a monthly 'no-fishing' form from Puerto Rico.
These logbook forms are used to record data for catch (landed catch) and effort for fishing trips made by commercially permitted fishers in Puerto Rico and the USVI. The catch and effort data for the entire trip are reported on a single form (i.e., one form per trip). The types of information required on this trip form include permit holder name, license number, vessel registration number, information on the quantity (reported in pounds) caught for each species, the area and depth of catch, the type and quantity of gear, the landing date (return date), location of landing (unloading of catch), an estimate of the fishing time, and the number of crew are included on this form.
The Puerto Rico form collects ex-vessel price information. The USVI forms do not collect price information. The Puerto RIco logbook form generally follows the historical format; however, there is now only one trip recorded per form. The new USVI forms are a significant departure from the previous format in that gear types and species specific names are pre-printed on the forms and there is only 1 trip recorded per page where the historical forms included the entire month of trips on a page. There are also spaces on all new forms where discard information may be recorded.
In addition the data set houses look-up tables for species and families, dialects, gear and gear groups, fishing areas, and permit holders. An online application was designed to allow for entry of data from each form type according to customized screens.
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 bounds include territorial waters and waters in the Exclusive Economic Zone for Puerto Rico and the US Virgin Islands as displayed on the log report look-up maps for those islands. Some areas falling within the general boundaries (British Virgin Islands waters for example), are not included. Boundaries specific to each form are recorded separately.
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):
Industry generated logbook report from fisher goes to US Caribbean Fishing Agency for processing and entry into web based application. Edit checks on entry by look-up tables. Edit Checks and feedback as well as compliance report made available to agency by SEFSC
(describe or provide URL of description):
Look-up tables and checks for large and small pounds and price by fisher, species. Posted to US Caribbean by SEFSC.
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.
To access sensitive data a completed non-disclosure agreement must be on file with NOAA-SEFSC. Otherwise Data that are submitted as sensitive can be released to the public under the following circumstances:
1. Combined or aggregated data. Sensitive 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, sensitive data Can be released as non-sensitive 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. Sensitive data collected under federal authority Can be released to the original entity (person, vessel, business, etc.) that submitted the data.
4. Sensitive data waived. The protection of sensitive 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.
These standards and procedures apply to all employees of the SEFSC that need access to sensitive fisheries statistics. This includes full time or term employees, contractors, volunteers, and/or other employees associated with the SEFSC, but not directly employed by either organization. Any SEFSC employee that needs or desires access to sensitive data must have read NOA 216-100 and submitted a signed nondisclosure statement to the Director, Information Resources Management Division (IRMD). The non-disclosure statement must be approved by the Director of IRMD and maintained on file by IRMD. It is the responsibility of the Director of IRMD to certifY upon request, that a person or organization that requests access to sensitive data is authorized access to those data. All employees that have access to and/or use sensitive data (federal and nonfederal) are responsible to protect those data from unauthorized access or release. Contractors or grantees that have an agreement with NMFS can be granted
access to sensitive data as an authorized user (See NOA 216-100 1 Section 6.03e). It should be clearly understood that sensitive data cannot be released simply by an individual signing a nondisclosure statement. There must be a clear and demonstrable need for the sensitive data that are requested as part of a contract or grant. Sensitive data can only be released for the specific contract or grant. Upon completion of the contract or grant, the recipient must either return the data or state that it has been destroyed. The contractor or grantee cannot use the data for any purpose other than the uses stated in the agreement. The Contracting Officers Technical Representative (COTR) or the Technical Monitor (TM) that has been assigned to the contract or grant, respectively, has the following? responsibilities:
1. The COTR/TM has the responsibility to determine whether the contractor/grantee is eligible to receive the sensitive data that are requested in the agreement.
2. The COTR/TM has the responsibility to assure that all persons included in the agreement have read NOA 2l6-l00 and have signed a nondisclosure statement. A statement must be signed by each person that will have access to the sensitive data under the agreement, i.e., a blanket statement cannot be used for the company or firm. The COTR/TM also has the responsibility to make sure that the Director, IRMD has signed and approved the nondisclosure statement and the statement is on file with IRMD.
3. The COTR/TM has the responsibility to assure that sensitive data are not released in any publication, report, oral presentation, or other means to the public by the contractor or grantee.
Fishers have 60 days to submit report entry time possibly delayed due to manpower of US Caribbean Agencies.
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.
In SECPR Oracle database
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
User id and password
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.