Search Help Show/Hide Menu
Summary
Item Identification
Keywords
Physical Location
Entity Info
Data Attributes
Support Roles
Extents
Access Info
Catalog Details

Summary

Abstract

To collect trip-level data for every fishing trip made by a Federally permitted vessel issued a permit with mandatory reporting requirements.

Description

FVTR trip level information. Level 1 in hierarchial data model that contains information about individual fishing trips (e.g., vessel permit number, date sailed, date landed, etc.)

Entity Information

Entity Type
Data Table

Data Attribute / Type Description
DOCID
NUMBER
Internal primary key generated at scanning. Based on date and time sailed & vessel id. Link to IMAGES table. Each DOCID represents one trip.
NRPAGES
NUMBER
Number of pages in document. Vessels fishing in more than one statistical area or using more than one gear type are required to complete a separate page for each gear or statistical area.
VESSEL_ID
NUMBER
Internal vessel identification number. Link to VESSELS table. This field is used when analyses on individual vessels are needed but the identity of the vessel is confidential or not important to the analysis.
DATE_SAIL
DATE
Date and time vessel left the dock.
DATE_LAND
DATE
Primary date and time vessel docked.
TRIPCATG
NUMBER
Type of trip: Commercial (1), Party (2), Charter (3), Research Set-Aside (RSA)/ Experimental Fishing Permit (EFP) (4).
CREW
NUMBER
Number of crew, including captain.
NANGLERS
NUMBER
Number of anglers (party/charter only, excluding crew).
PORT1
VARCHAR2
First port where product are landed. Link to VLPORTSYN table (concatenate with State1).
PORT2
VARCHAR2
Second port where product is landed. Link to VLPORTSYN table (concatenate with State2).
PORT3
VARCHAR2
Third port where product is landed. Link to VLPORTSYN table (concatenate with State3).
STATE1
VARCHAR2
First state where product is landed; 2-letter state postal abbreviation.
STATE2
VARCHAR2
Second state where is landed; 2-letter state postal abbreviation.
STATE3
VARCHAR2
Third state where is landed; 2-letter state postal abbreviation.
DATELND2
DATE
Secondary date and time vessel landed. Used when a vessel lands and offloads fish on different dates for a single fishing trip. This may happen when a vessel offloads a portion of its catch at one port and the remainder at a second port.
DATELND3
DATE
Third date and time vessel landed. Used when a vessel lands and offloads fish on different dates for a single fishing trip. This may happen when a vessel offloads a portion of its catch at one port and the remainder at a third port.
OPERATOR_NUM
NUMBER
Operator permit number.
OPERATOR_NAME
VARCHAR2
Operator name as provided on the operator permit application.
DATE_SIGNED
DATE
Date form was signed by operator.
ENTRY_COMP
NUMBER
Data entry complete flag: Yes (1); No (0).
FISHED
NUMBER
Indicates fishing activity or negative report: Fishing activity (0); Negative report (1).
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.
VESSEL_PERMIT_NUM
NUMBER
Federally issued 6-digit vessel permit number.
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: DOCUMENT
Short Name: DOCUMENT
Status: Completed
Abstract:

To collect trip-level data for every fishing trip made by a Federally permitted vessel issued a permit with mandatory reporting requirements.

Purpose:

To store FVTR information by trip, including date sail, date land, type of trip, port of landing & number of crew. Linked to the IMAGES table via DOCID (tripid).

Notes:

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

Supplemental Information:

Server: NERO; Schema: NOAA; Table: Document

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 trip level information. Level 1 in hierarchial data model that contains information about individual fishing trips (e.g., vessel permit number, date sailed, date landed, etc.)

Data Attributes

Attribute Summary

Rubric Score Primary Key? Name Type Description
100
Primary Key DOCID NUMBER Internal primary key generated at scanning. Based on date and time sailed & vessel id. Link to IMAGES table. Each DOCID represents one trip.
100
NRPAGES NUMBER Number of pages in document. Vessels fishing in more than one statistical area or using more than one gear type are required to complete a separate page for each gear or statistical area.
100
VESSEL_ID NUMBER Internal vessel identification number. Link to VESSELS table. This field is used when analyses on individual vessels are needed but the identity of the vessel is confidential or not important to the analysis.
100
DATE_SAIL DATE Date and time vessel left the dock.
100
DATE_LAND DATE Primary date and time vessel docked.
100
TRIPCATG NUMBER Type of trip: Commercial (1), Party (2), Charter (3), Research Set-Aside (RSA)/ Experimental Fishing Permit (EFP) (4).
100
CREW NUMBER Number of crew, including captain.
100
NANGLERS NUMBER Number of anglers (party/charter only, excluding crew).
100
PORT1 VARCHAR2 First port where product are landed. Link to VLPORTSYN table (concatenate with State1).
100
PORT2 VARCHAR2 Second port where product is landed. Link to VLPORTSYN table (concatenate with State2).
100
PORT3 VARCHAR2 Third port where product is landed. Link to VLPORTSYN table (concatenate with State3).
100
STATE1 VARCHAR2 First state where product is landed; 2-letter state postal abbreviation.
100
STATE2 VARCHAR2 Second state where is landed; 2-letter state postal abbreviation.
100
STATE3 VARCHAR2 Third state where is landed; 2-letter state postal abbreviation.
100
DATELND2 DATE Secondary date and time vessel landed. Used when a vessel lands and offloads fish on different dates for a single fishing trip. This may happen when a vessel offloads a portion of its catch at one port and the remainder at a second port.
100
DATELND3 DATE Third date and time vessel landed. Used when a vessel lands and offloads fish on different dates for a single fishing trip. This may happen when a vessel offloads a portion of its catch at one port and the remainder at a third port.
100
OPERATOR_NUM NUMBER Operator permit number.
100
OPERATOR_NAME VARCHAR2 Operator name as provided on the operator permit application.
100
DATE_SIGNED DATE Date form was signed by operator.
100
ENTRY_COMP NUMBER Data entry complete flag: Yes (1); No (0).
100
FISHED NUMBER Indicates fishing activity or negative report: Fishing activity (0); Negative report (1).
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
VESSEL_PERMIT_NUM NUMBER Federally issued 6-digit vessel permit number.
100
ORIGIN VARCHAR2 Identifies origin of a record as being entered from a paper VTR (CID origin) or an electronic VTR (FVTR)

Attribute Details

DOCID

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

Internal primary key generated at scanning. Based on date and time sailed & vessel id. Link to IMAGES table. Each DOCID represents one trip.

General Data Type: NUMBER

NRPAGES

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

Number of pages in document. Vessels fishing in more than one statistical area or using more than one gear type are required to complete a separate page for each gear or statistical area.

General Data Type: NUMBER

VESSEL_ID

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

Internal vessel identification number. Link to VESSELS table. This field is used when analyses on individual vessels are needed but the identity of the vessel is confidential or not important to the analysis.

General Data Type: NUMBER

DATE_SAIL

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

Date and time vessel left the dock.

General Data Type: DATE

DATE_LAND

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

Primary date and time vessel docked.

General Data Type: DATE

TRIPCATG

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

Type of trip: Commercial (1), Party (2), Charter (3), Research Set-Aside (RSA)/ Experimental Fishing Permit (EFP) (4).

General Data Type: NUMBER

CREW

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

Number of crew, including captain.

General Data Type: NUMBER

NANGLERS

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

Number of anglers (party/charter only, excluding crew).

General Data Type: NUMBER

PORT1

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

First port where product are landed. Link to VLPORTSYN table (concatenate with State1).

General Data Type: VARCHAR2

PORT2

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

Second port where product is landed. Link to VLPORTSYN table (concatenate with State2).

General Data Type: VARCHAR2

PORT3

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

Third port where product is landed. Link to VLPORTSYN table (concatenate with State3).

General Data Type: VARCHAR2

STATE1

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

First state where product is landed; 2-letter state postal abbreviation.

General Data Type: VARCHAR2

STATE2

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

Second state where is landed; 2-letter state postal abbreviation.

General Data Type: VARCHAR2

STATE3

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

Third state where is landed; 2-letter state postal abbreviation.

General Data Type: VARCHAR2

DATELND2

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

Secondary date and time vessel landed. Used when a vessel lands and offloads fish on different dates for a single fishing trip. This may happen when a vessel offloads a portion of its catch at one port and the remainder at a second port.

General Data Type: DATE

DATELND3

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

Third date and time vessel landed. Used when a vessel lands and offloads fish on different dates for a single fishing trip. This may happen when a vessel offloads a portion of its catch at one port and the remainder at a third port.

General Data Type: DATE

OPERATOR_NUM

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

Operator permit number.

General Data Type: NUMBER

OPERATOR_NAME

CC ID: 78218
Seq. Order: 18
Data Storage Type: VARCHAR2
Max Length: 35
Required: No
Primary Key: No
Status: Active
Description:

Operator name as provided on the operator permit application.

General Data Type: VARCHAR2

DATE_SIGNED

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

Date form was signed by operator.

General Data Type: DATE

ENTRY_COMP

CC ID: 78217
Seq. Order: 20
Data Storage Type: NUMBER
Max Length: 22
Required: No
Primary Key: No
Precision: 1
Scale: 0
Status: Active
Description:

Data entry complete flag: Yes (1); No (0).

General Data Type: NUMBER

FISHED

CC ID: 78216
Seq. Order: 21
Data Storage Type: NUMBER
Max Length: 22
Required: No
Primary Key: No
Precision: 1
Scale: 0
Status: Active
Description:

Indicates fishing activity or negative report: Fishing activity (0); Negative report (1).

General Data Type: NUMBER

DE

CC ID: 78226
Seq. Order: 22
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: 78228
Seq. Order: 23
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: 78206
Seq. Order: 24
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: 78227
Seq. Order: 25
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

VESSEL_PERMIT_NUM

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

Federally issued 6-digit vessel permit number.

General Data Type: NUMBER

ORIGIN

CC ID: 78229
Seq. Order: 27
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: 81303
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: 81305
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: 81304
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: 81406
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: 81418
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: 81430
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: 81386
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: 81396
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: 17032
GUID: gov.noaa.nmfs.inport:17032
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