Search Help Show/Hide Menu
Metadata Rubric
100%
6 / 6
View Report
GARFO Metadata Library > _Analysis and Program Support Division (APSD) M... > Vessel Logbook Reporting > Fishing Vessel Trip Report (FVTR) > Vessel Logbook Database >

Table: CATCH

Entity (ENT)  |  Greater Atlantic Regional Fisheries Office (GARFO)
GUID: gov.noaa.nmfs.inport:17031  |  Updated: August 9, 2022  |  Published / External 
Summary
Item Identification
Keywords
Physical Location
Entity Info
Data Attributes
Support Roles
Extents
Access Info
Catalog Details

Summary

Abstract

The Catch Table contains the primary catch information by species as reported by the vessel operator.

Description

FVTR catch information

Entity Information

Entity Type
Data Table

Data Attribute / Type Description
CATCH_ID
NUMBER 		Internal primary key. Oracle generated sequence.
IMGID
NUMBER 		FVTR image identification number. Link to IMAGES table.
SPECIES_ID
VARCHAR2 		Species name abbreviation. Link to VLSPPSYN table.
KEPT
NUMBER 		Amount kept. Commercial = pounds; Party/Charter = count.
DISCARDED
NUMBER 		Amount discarded. Commercial = pounds; Party/Charter = count.
DEALER_NUM
NUMBER 		Federally issued dealer catch was sold to. Link to PERMIT.DEALER table.
DATE_SOLD
DATE 		Date catch was sold.
PORT_LANDED
VARCHAR2 		Port(city) where catch was landed.
STATE_LANDED
VARCHAR2 		State where catch was landed.
PORT_NUMBER
VARCHAR2 		Port Number identifying the port name and state where catch was landed.
LEGACY_PORT
NUMBER 		Defines the origin of port data for the catch. 0 = actual port data captured at the catch level. 1 = port data was derived from legacy data derived at the trip level from the document table. NULL indicates data is still undefined as no port value has been entered.
DE
DATE 		Date record was loaded into table.
UE
VARCHAR2 		User loading data into table.
DC
DATE 		Date of most recent update(s) to record.
UC
VARCHAR2 		User making most recent update(s) to record.
ORIGIN
VARCHAR2 		Identifies origin of a record as being entered from a paper VTR (CID origin) or an electronic VTR (FVTR)

Child Items

No Child Items for this record.

Contact Information

Point of Contact
James R St Cyr
james.stcyr@noaa.gov
978-281-9369

Extents

Time Frame 1
2010-05-01 - Present

Weekly reporting began for vessels issued Federal Northeast Multispecies permits.

Time Frame 2
2011-06-30 - Present

Vessels participating in the multispecies catch share program or in the cooperative reseach program may use Fisheries Logbook Data Recording Software (FLDRS) to submit electronic VTRs

Time Frame 3
2011-09-28 - Present

Weekly reporting began for vessels issued Federal Northeast Atlantic Herring permits.

Time Frame 4
1978 - Present

Beginning in 1978, participation in the surf clam fishery became conditional upon a set of requirements including detailed logbook reporting. In the early 1980's ocean quahog vessels became subject to the same detailed logbook reporting requirements.

Time Frame 5
1994 - Present

The FVTR data collection program was implemented in 1994, to monitor the geographic distribution of fishing effort and catches of federally regulated species in the region. All Northeast Region federally permitted vessels must submit a VTR for each trip taken regardless of where the trip took place or species targeted. The one exception to this is for vessels that are only permitted for American Lobster. Beginning May 1, 2010, any vessel issued a Federal Northeast Multispecies or Atlantic Herring permit must submit VTRs on a weekly basis. Weekly reports are due by midnight Tuesday for all trips taken during the previous week. All other vessels must submit their VTR?s on a monthly basis. Monthly reports are due by the 15th day of the month following the month in which the trip occurred.

Item Identification

Title: Table: CATCH
Short Name: CATCH
Status: Completed
Abstract:

The Catch Table contains the primary catch information by species as reported by the vessel operator.
Purpose:

To store the FVTR catch data including species, pounds kept, pounds discarded, dealer(s) the fish was sold to & the date it was sold. Linked with the Images table via IMGID.
Notes:

Loaded by batch 3737, 11-16-2012 09:32
Other Citation Details:

This table is linked to the Images table using the key attribute "IMGID".
Supplemental Information:

Server: NERO; Schema: NOAA; Table: Catch

Keywords

Theme Keywords

Thesaurus Keyword
UNCONTROLLED
None logbook

Temporal Keywords

Thesaurus Keyword
UNCONTROLLED
None 1978-present

Spatial Keywords

Thesaurus Keyword
UNCONTROLLED
None new england

Stratum Keywords

Thesaurus Keyword
UNCONTROLLED
None commercial fishing

Physical Location

Organization: Greater Atlantic Regional Fisheries Office
City: Gloucester
State/Province: MA
Country: USA
Location Description:

Fisheries Data Services Division (FDSD)

55 Great Republic Drive

Entity Information

Entity Type: Data Table
Active Version?: Yes
Schema Name: NOAA
Description:

FVTR catch information

Data Attributes

Attribute Summary

Rubric Score Primary Key? Name Type Description
100
 Primary Key CATCH_ID NUMBER Internal primary key. Oracle generated sequence.
100
 IMGID NUMBER FVTR image identification number. Link to IMAGES table.
100
 SPECIES_ID VARCHAR2 Species name abbreviation. Link to VLSPPSYN table.
100
 KEPT NUMBER Amount kept. Commercial = pounds; Party/Charter = count.
100
 DISCARDED NUMBER Amount discarded. Commercial = pounds; Party/Charter = count.
100
 DEALER_NUM NUMBER Federally issued dealer catch was sold to. Link to PERMIT.DEALER table.
100
 DATE_SOLD DATE Date catch was sold.
100
 PORT_LANDED VARCHAR2 Port(city) where catch was landed.
100
 STATE_LANDED VARCHAR2 State where catch was landed.
100
 PORT_NUMBER VARCHAR2 Port Number identifying the port name and state where catch was landed.
100
 LEGACY_PORT NUMBER Defines the origin of port data for the catch. 0 = actual port data captured at the catch level. 1 = port data was derived from legacy data derived at the trip level from the document table. NULL indicates data is still undefined as no port value has been entered.
100
 DE DATE Date record was loaded into table.
100
 UE VARCHAR2 User loading data into table.
100
 DC DATE Date of most recent update(s) to record.
100
 UC VARCHAR2 User making most recent update(s) to record.
100
 ORIGIN VARCHAR2 Identifies origin of a record as being entered from a paper VTR (CID origin) or an electronic VTR (FVTR)

Attribute Details

CATCH_ID

CC ID: 78189
Seq. Order: 1
Data Storage Type: NUMBER
Max Length: 22
Required: Yes
Primary Key: Yes
Precision: 18
Scale: 0
Status: Active
Description:

Internal primary key. Oracle generated sequence.
General Data Type: NUMBER

IMGID

CC ID: 78197
Seq. Order: 2
Data Storage Type: NUMBER
Max Length: 22
Required: Yes
Primary Key: No
Precision: 16
Scale: 0
Status: Active
Description:

FVTR image identification number. Link to IMAGES table.
General Data Type: NUMBER

SPECIES_ID

CC ID: 78195
Seq. Order: 3
Data Storage Type: VARCHAR2
Max Length: 10
Required: Yes
Primary Key: No
Status: Active
Description:

Species name abbreviation. Link to VLSPPSYN table.
General Data Type: VARCHAR2

KEPT

CC ID: 78204
Seq. Order: 4
Data Storage Type: NUMBER
Max Length: 22
Required: No
Primary Key: No
Precision: 8
Scale: 0
Status: Active
Description:

Amount kept. Commercial = pounds; Party/Charter = count.
General Data Type: NUMBER

DISCARDED

CC ID: 78199
Seq. Order: 5
Data Storage Type: NUMBER
Max Length: 22
Required: No
Primary Key: No
Precision: 8
Scale: 0
Status: Active
Description:

Amount discarded. Commercial = pounds; Party/Charter = count.
General Data Type: NUMBER

DEALER_NUM

CC ID: 78203
Seq. Order: 6
Data Storage Type: NUMBER
Max Length: 22
Required: No
Primary Key: No
Precision: 5
Scale: 0
Status: Active
Description:

Federally issued dealer catch was sold to. Link to PERMIT.DEALER table.
General Data Type: NUMBER

DATE_SOLD

CC ID: 78198
Seq. Order: 7
Data Storage Type: DATE
Max Length: 7
Required: No
Primary Key: No
Status: Active
Description:

Date catch was sold.
General Data Type: DATE

PORT_LANDED

CC ID: 78200
Seq. Order: 8
Data Storage Type: VARCHAR2
Max Length: 25
Required: No
Primary Key: No
Status: Active
Description:

Port(city) where catch was landed.
General Data Type: VARCHAR2

STATE_LANDED

CC ID: 78191
Seq. Order: 9
Data Storage Type: VARCHAR2
Max Length: 2
Required: No
Primary Key: No
Status: Active
Description:

State where catch was landed.
General Data Type: VARCHAR2

PORT_NUMBER

CC ID: 78201
Seq. Order: 10
Data Storage Type: VARCHAR2
Max Length: 6
Required: No
Primary Key: No
Status: Active
Description:

Port Number identifying the port name and state where catch was landed.
General Data Type: VARCHAR2

LEGACY_PORT

CC ID: 78202
Seq. Order: 11
Data Storage Type: NUMBER
Max Length: 22
Required: No
Primary Key: No
Precision: 38
Status: Active
Description:

Defines the origin of port data for the catch. 0 = actual port data captured at the catch level. 1 = port data was derived from legacy data derived at the trip level from the document table. NULL indicates data is still undefined as no port value has been entered.
General Data Type: NUMBER

DE

CC ID: 78193
Seq. Order: 12
Data Storage Type: DATE
Max Length: 7
Required: No
Primary Key: No
Status: Active
Description:

Date record was loaded into table.
General Data Type: DATE

UE

CC ID: 78190
Seq. Order: 13
Data Storage Type: VARCHAR2
Max Length: 8
Required: No
Primary Key: No
Status: Active
Description:

User loading data into table.
General Data Type: VARCHAR2

DC

CC ID: 78192
Seq. Order: 14
Data Storage Type: DATE
Max Length: 7
Required: No
Primary Key: No
Status: Active
Description:

Date of most recent update(s) to record.
General Data Type: DATE

UC

CC ID: 78194
Seq. Order: 15
Data Storage Type: VARCHAR2
Max Length: 8
Required: No
Primary Key: No
Status: Active
Description:

User making most recent update(s) to record.
General Data Type: VARCHAR2

ORIGIN

CC ID: 78196
Seq. Order: 16
Data Storage Type: VARCHAR2
Max Length: 4
Required: Yes
Primary Key: No
Status: Active
Description:

Identifies origin of a record as being entered from a paper VTR (CID origin) or an electronic VTR (FVTR)
General Data Type: VARCHAR2

Support Roles

Data Steward

CC ID: 81306
Date Effective From: 2012-02-01
Date Effective To:
Contact (Person): St Cyr, James R
Address: 55 Great Republic Drive
Gloucester, MA 01930
USA
Email Address: james.stcyr@noaa.gov
Phone: 978-281-9369

Point of Contact

CC ID: 81308
Date Effective From: 2012-02-01
Date Effective To:
Contact (Person): St Cyr, James R
Address: 55 Great Republic Drive
Gloucester, MA 01930
USA
Email Address: james.stcyr@noaa.gov
Phone: 978-281-9369

Process Contact

CC ID: 81307
Date Effective From: 2012-02-01
Date Effective To:
Contact (Person): Brosnan, Bethany
Address: 55 Great Republic Drive
Gloucester, MA 01930
USA
Email Address: Bethany.Brosnan@Noaa.gov

Extents

Extent Group 1

Extent Group 1 / Time Frame 1

CC ID: 81405
Time Frame Type: Continuing
Start: 2010-05-01
Description:

Weekly reporting began for vessels issued Federal Northeast Multispecies permits.

Extent Group 1 / Time Frame 2

CC ID: 81417
Time Frame Type: Continuing
Start: 2011-06-30
Description:

Vessels participating in the multispecies catch share program or in the cooperative reseach program may use Fisheries Logbook Data Recording Software (FLDRS) to submit electronic VTRs

Extent Group 1 / Time Frame 3

CC ID: 81429
Time Frame Type: Continuing
Start: 2011-09-28
Description:

Weekly reporting began for vessels issued Federal Northeast Atlantic Herring permits.

Extent Group 1 / Time Frame 4

CC ID: 81385
Time Frame Type: Continuing
Start: 1978
Description:

Beginning in 1978, participation in the surf clam fishery became conditional upon a set of requirements including detailed logbook reporting. In the early 1980's ocean quahog vessels became subject to the same detailed logbook reporting requirements.

Extent Group 1 / Time Frame 5

CC ID: 81395
Time Frame Type: Continuing
Start: 1994
Description:

The FVTR data collection program was implemented in 1994, to monitor the geographic distribution of fishing effort and catches of federally regulated species in the region. All Northeast Region federally permitted vessels must submit a VTR for each trip taken regardless of where the trip took place or species targeted. The one exception to this is for vessels that are only permitted for American Lobster. Beginning May 1, 2010, any vessel issued a Federal Northeast Multispecies or Atlantic Herring permit must submit VTRs on a weekly basis. Weekly reports are due by midnight Tuesday for all trips taken during the previous week. All other vessels must submit their VTR?s on a monthly basis. Monthly reports are due by the 15th day of the month following the month in which the trip occurred.

Access Information

Security Class: Confidential
Security Classification System:

Vessel trip reports are considered to be business confidential and may not be released without signed approval of the permit holder on record for the time period requested.
Data Access Policy:

Access to VTR data is governed by 50CFR600 - Confidentiality of Information. Access by state fishery management agency staff and Fisheries Management Council staff may be allowed through Memorandum of Understanding that are signed by the NE Regional Administrator and Directors of the State Agency or Councils that describe the need and uses of the data and list the individuals who will have access to the data. Contractors may be granted access provided they are working under contract to NOAA or a cooperating partner (state, Council, Commission) on a specific project under the oversight of a partner.
Data Access Procedure:

Contact POC to request access.
Data Access Constraints:

Access is restricted to personnel authorized in accordance with NOAA Administrative Order 216-100. A signed non-disclosure agreement must be on file for all authorized personnel. The APSD Data Request staff are the POC for non-disclosure forms.
Data Use Constraints:

Access to individual reports is restricted to NOAA employees and our partners who have signed non-disclosure agreements. Summary data may be made available based on the "rule of 3", i.e., there must be at least three entities included in a summary for the summary information to be made publically available. Data may be made available if there is no information included that could uniquely link the information to an individual entity (person, vessel operating unit, business, etc.). Individually identifiable information may not be released without written authorization from the provider or by court order.
Metadata Use Constraints:

There are no constraints on the use of the metadata associated with this program.

Catalog Details

Catalog Item ID: 17031
GUID: gov.noaa.nmfs.inport:17031
Metadata Record Created By: Denise A Washick
Metadata Record Created: 2012-11-16 09:32+0000
Metadata Record Last Modified By: SysAdmin InPortAdmin
Metadata Record Last Modified: 2022-08-09 17:11+0000
Metadata Record Published: 2016-02-29
Owner Org: GARFO
Metadata Publication Status: Published Externally
Do Not Publish?: N
Metadata Last Review Date: 2016-02-29
Metadata Review Frequency: 1 Year
Metadata Next Review Date: 2017-02-28