Observer and At Sea Monitor Database (OBDBS)

The Northeast Fisheries Observer Database System (OBDBS) contains data collected on commercial fishing vessels by observers from 1989 - present and at-sea monitors from 2010 - present. The data include detailed gear, effort, catch, bycatch of finfish and protected species as well as biological samples of priority and protected species. Data is collected by trained fishery observers and at-sea monitors for scientific and fisheries management purposes.

Observer Data is a vital component of the fishery management process. Observer data is used to monitor bycatch, monitor seasonal quotas, track the effectiveness of gear modifications, determine whether appropriate conservation measures are in place for commercial fisheries to reduce bycatch of marine mammals, identify fishing patterns, identify ways for fishermen to efficiently reduce unwanted bycatch, document interactions between marine mammals and determine severity of injuries.

Oracle database server on the NEFSC network

NEFSC Data Access Procedure:

1. Formal request in writing usually to the data owner/contact or Center Director;

2. Requester is contacted by data owner to review and verify the request content and details for data delivery options.

3. If data is confidential then owner will determine if the data may be released to the requester;

4. If data can be released, the data is downloaded and packaged for delivery electronically; or the requester may be directed to where the data is available online.

NEFSC Data Access Constraint:

Access as allowed by Magnuson-Stevens Fisheries Conservation and Management Act to only NMFS staff, Council staff, State Fisheries staff or other Federal staff responsible for fisheries management and enforcement.

If data is stored on an internal NEFSC network, the requester may not have direct access to query the data unless they are also authorized for network access.

Data can only be released to the general public in an aggregated format in order to protect the identity and business practices of the vessel/permit owner.

Oracle database, centralized data management

Data are collected as a combination of self reported data from captains such as trip costs and unmeasureable gear characterstics and measurable variables like locations, effort, environment. Catch weights are collected using hand held and platform scales whenever possible.

Some data elements are required, most are optional with a high degree of full completion.

Data validation at data entry, audits by internal editors, follow up debriefings, data validation/audits prior to database load and database integrity constraints.

Archival of source data preserving unaltered collected data, Scheduled backups, Remote storage backups, Password protection

Fishery observers and at sea monitors record trip, haul, and catch data on observed fishing trips using defined protocols. Preliminary observer data and sector catch data is entered electronically, complete observer data is entered on paper logs. Observers are debriefed by data debriefers. Data recorded manually is entered by the Training and Data Quality Branch. Entered data is verified and extensively audited by the Training and Data Quality Branch prior to database load.