Data Management Plan (Deprecated)

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.

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.

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

Look-up tables and checks for large and small pounds and price by fisher, species. Posted to US Caribbean by SEFSC.

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.

User id and password