Slide Menu
InPort and its associated services will be under maintenance and unavailable for the deployment of InPort Release 5.2.3. Downtime Schedule Tuesday, November 29, 2022 12:00pm - 1:30pm Eastern / 10:00am - 11:30pm Pacific / 7:00am - 8:30pm Hawaii Impacted Areas - InPort Website: https://www.fisheries.noaa.gov/inport - InPort WAF: https://www.fisheries.noaa.gov/inportserve/waf What's...
View All
Search Help Show/Hide Menu

Item Identification

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

pre-validation table for the vessel data in PDC System. This table is loaded with data from PDC_INT_ACCESS_VESSELS and data from this table goes into the table PDS_VESSELS

Notes:

Loaded by batch 1703, 10-15-2007 10:13

Entity Information

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

pre-validation table for the vessel data in PDC System. This table is loaded with data from PDC_INT_ACCESS_VESSELS and data from this table goes into the table PDS_VESSELS

Data Attributes

Attribute Summary

Rubric Score Primary Key? Name Type Description
100
ID_NUMBER VARCHAR2 Sequential Number Assigned By Vendor Software During Data Entry
100
TIF_NUMBER VARCHAR2 The scan images provided by the vendor
100
SCHEDULE VARCHAR2 This is a number handwritten by FSB at the top right of the form. This is a unique number and was used to associate the form with the computer record in the header.dbf file in the PC SDC systemIn the INT files we programatically check to see that a cobination of teh e Year of The BEGIN_DATE and thiu column are unique.
100
DATE_LANDED VARCHAR2 Dta vessel landed
100
VESSEL_NAME VARCHAR2 Vessel Name
100
VESSELID VARCHAR2 The corrected vessl information. This will often be the same as the repoerted vessel information. Though in some cases it will correct a typographical error.
100
PORT_LANDED VARCHAR2 Port Landed
100
STATE_LANDED VARCHAR2 State Landed
100
BATCH_NUMBER VARCHAR2 When logbooks are picked up at the post office, they are processed together in batches. Each piece of paper is stamped with a unique schedule number. These pieces of paper may be in different formats because although new logbooks are issued every year to each permit holder, we may get information written on logbooks printed as early as 1992.When this batch of records are sent to the contractor that enters them, since there records are entered using an electronic scanner, the logbooks must be culled by year so that the scanner can correctly interpret the image it is reading. Hence, for each year, we have a separate file.All of the files that form part of a batch are loaded together so that the schedule numbers can be checked. If any are missing or out of bounds, an error is reported during validation. Validation:None.
100
OP_NAME VARCHAR2 A Vendor Supplied field
100
OP_DATE VARCHAR2 A Vendor Supplied field
100
OP_VALUE VARCHAR2 A Vendor Supplied field
100
SOURCE_FILE VARCHAR2 Source file used to load this data
100
REP_VESSELID VARCHAR2 The vessel information reported on the form

Attribute Details

ID_NUMBER

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

Sequential Number Assigned By Vendor Software During Data Entry

General Data Type: VARCHAR2

TIF_NUMBER

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

The scan images provided by the vendor

General Data Type: VARCHAR2

SCHEDULE

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

This is a number handwritten by FSB at the top right of the form. This is a unique number and was used to associate the form with the computer record in the header.dbf file in the PC SDC systemIn the INT files we programatically check to see that a cobination of teh e Year of The BEGIN_DATE and thiu column are unique.

General Data Type: VARCHAR2

DATE_LANDED

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

Dta vessel landed

General Data Type: VARCHAR2

VESSEL_NAME

CC ID: 16938
Seq. Order: 5
Data Storage Type: VARCHAR2
Max Length: 30
Required: No
Primary Key: No
Status: Active
Description:

Vessel Name

General Data Type: VARCHAR2

VESSELID

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

The corrected vessl information. This will often be the same as the repoerted vessel information. Though in some cases it will correct a typographical error.

General Data Type: VARCHAR2

PORT_LANDED

CC ID: 16936
Seq. Order: 7
Data Storage Type: VARCHAR2
Max Length: 30
Required: No
Primary Key: No
Status: Active
Description:

Port Landed

General Data Type: VARCHAR2

STATE_LANDED

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

State Landed

General Data Type: VARCHAR2

BATCH_NUMBER

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

When logbooks are picked up at the post office, they are processed together in batches. Each piece of paper is stamped with a unique schedule number. These pieces of paper may be in different formats because although new logbooks are issued every year to each permit holder, we may get information written on logbooks printed as early as 1992.When this batch of records are sent to the contractor that enters them, since there records are entered using an electronic scanner, the logbooks must be culled by year so that the scanner can correctly interpret the image it is reading. Hence, for each year, we have a separate file.All of the files that form part of a batch are loaded together so that the schedule numbers can be checked. If any are missing or out of bounds, an error is reported during validation. Validation:None.

General Data Type: VARCHAR2

OP_NAME

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

A Vendor Supplied field

General Data Type: VARCHAR2

OP_DATE

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

A Vendor Supplied field

General Data Type: VARCHAR2

OP_VALUE

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

A Vendor Supplied field

General Data Type: VARCHAR2

SOURCE_FILE

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

Source file used to load this data

General Data Type: VARCHAR2

REP_VESSELID

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

The vessel information reported on the form

General Data Type: VARCHAR2

Catalog Details

Catalog Item ID: 5413
GUID: gov.noaa.nmfs.inport:5413
Metadata Record Created By: Lee M Weinberger
Metadata Record Created: 2007-10-15 10:13+0000
Metadata Record Last Modified By: SysAdmin InPortAdmin
Metadata Record Last Modified: 2022-08-09 17:10+0000
Metadata Record Published: 2021-05-06
Owner Org: SEFSC
Metadata Publication Status: Published Externally
Do Not Publish?: N
Metadata Last Review Date: 2021-05-06
Metadata Review Frequency: 1 Year
Metadata Next Review Date: 2022-05-06