Slide Menu
Search Help Show/Hide Menu

Item Identification

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

Table Holding Information On Logbook Received

Notes:

Loaded by batch 2103, 02-28-2008 14:10

Entity Information

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

Table Holding Information On Logbook Receibed

Data Attributes

Attribute Summary

Rubric Score Primary Key? Name Type Description
100
Primary Key LOGBOOK_KEY NUMBER Sequence number automatically generated by the system to uniquely identify each row in the table. Since these keys are not data dependent, if any element of data is changed, the links to the other tables in the system are not broken.Validation:Managed by the database. Each row in the table must have a unique value.
100
SCHEDULE_NUMBER VARCHAR2 A number stamped on each logbook form.Note: For the Pelagic Logbook, this number represents the trip number which in 1996 replaced the BATCH SEQUENCE NUMBER.Validation:A validation program ensures that the schedule number is unique within the interim tables and between the interim and master tables.
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 1994.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.Validation:None.
100
ID_NUMBER VARCHAR2 A reference number used by the data entry contractors that enables them to uniquely identify each record.Validation:None. The column is optional.
100
VESSEL_ID VARCHAR2 The ID of the vessel for which the logbook has been completed.Validation:A foreign key between this table and FLS_VESSEL_LIST ensures that only valid vessel ids can be entered into this table.The column is mandatory and may not be left empty.
100
DEPARTURE_DATE DATE Date when the vessel left port to begin the fishing activity. This field is now called START DATE on the form.Validation:The date must be a valid date as enforced by the DATE data type. A check constraint ensures that the departure date is less than the landing date.This column may be left empty, however, if days away from port and landing date are supplied, the system will calculate the departure date.
100
LANDING_DATE DATE Date when the catch was unloaded at a dealer. This field is now called UNLOAD DATE on the form. If the catch was unloaded at more than one dealer, this date represents the date when the catch was unloaded at the first dealer.Validation:The date must be a valid date as enforced by the DATE data type. Several Check constraints ensure that the Landing Date is greater than or equal to departure date, and that post mark date and opened date, are less than sent to data entry date.This column may not be left empty, because this date is used to determine if a vessel has met its reporting requirement for a given month.
100
UNLOAD_DATE DATE Date when the vessel unloaded the catch at the landing site.Validation:The date must be valid and cannot be null. The unload date must be greater than or equal to start date (i.e. departure date) A warning is issued if the unload date is less than the landing date.
100
OPENED_DATE DATE Date stamped on the logbook report. The RMD stamps this date on the form when they are retrieved from the post office and opened.Validation:The data must be a valid date.
100
DAYS_AWAY_FROM_PORT NUMBER Number of days spent away from port. Includes traveling time to and from the fishing area. Any fraction of a day counts as a whole day. If a vessel left in the morning and returned any time before midnight, fishers are instructed to report 1 day away from port.Validation:Must be a valid number.This column may be left empty, however, if departure date and landing date are supplied, the system will calculate the days away from port.
100
LOAD_DATE DATE Date on which the file was loaded into the Fisheries Logbook System.Validation:The date validation is enforced by the date type 'DATE'. Only valid dates can be entered into this column.
100
ACTIVITY_TYPE VARCHAR2 Distinguishes between fishing and no fishing reports. This column is set automatically by the loading program, depending on the menu selection made by the user.Validation:The domain ACTIVITY TYPE allows only two choices Fishing or No Fishing. Null is not a valid entry because the column is mandatory.
100
POST_MARK_DATE DATE Date that is stamped by the post office on the logbook. It is unlikely that this column will be used. If it is used, it must be entered by the data managers.Validation:A valid data is ensured by the use of a DATE type column. Several check constraints ensure that Post Mark date is greater than or equal to Landing Date, greater than Opened Date, and less than Sent to Data Entry
100
RETURNED_TO_PERMIT_HOLDER VARCHAR2 Reason why the data managers returned a logbook to a permit holder. This column must be entered by the person sending the logbook back.Validation:A domain called REASON_FOR_RETURN ensures that only valid reasons are entered. The column is not mandatory and may be left blank.
100
RETURNED_TO_PERMIT_HOLDER_DATE DATE Date on which a logbook is returned to the permit holder for corrections. Sometimes the fishers omit important information from the form that cannot be corrected by the data managers. There are also errors that can only be corrected by the permit holder. In this case, the logbook is mailed back to the permit holder with a letter indicating what is wrong with the logbook and an envelop to return the corrected form.Validation:A valid date is ensured by the use of a 'DATE' type column. In addition, several check constraints ensure that the Returned to Permit Holder Date is less than the Returned by Permit Holder Date and greater than or equal to Opened Date.
100
RETURNED_BY_PERMIT_HOLDER_DATE DATE Date on which the permit holder returned a logbook that needed corrections. This date must be entered by the data manager that received the logbook and adds it to a batch for processing.Validation:A valid date is ensured by the use of a DATE type column. A check constraint ensures that the Returned by Permit Holder Date is greater than the Returned to Permit Holder Date.
100
SENT_TO_DATA_ENTRY_DATE DATE Date on which the logbook forms were sent to the data entry contractor for scanning.Validation:A valid date is ensured through the use of the "DATE" data type. The field is optional and may be left blank. Three check constraints ensure that the Sent to Data Entry date is greater than or equal to Landing Date, Opened Date and Post Mark Date.
100
RETURNED_FROM_DATA_ENTRY_DATE DATE Date when the files of data scanned by the contractor were received at the SEFSC.Validation:A valid date is ensured by the use of the DATE data type of the column.
100
MOVED_TO_MASTER_DATE DATE Date on which the data has been completely validated and edited and moved into the master tables. When data are first scanned by the data entry contractor, they are loaded into Scanned Data tables that have a format less restrictive than the master tables. After editing, the data are distributed to the Master tables.This date is inserted automatically by the loading programs.Validation:Since the date is loaded by the program using the system date, this data is always correct. If a data manager were to change it, the 'DATE' data type of the column would prevent invalid dates from being inserted.
100
LOGBOOK_IMAGE_FILE VARCHAR2 The legacy pc field, tif_no, is called logbook_image_file in the FLS master tables.When data are scanned, two products are obtained: data files, where the image is converted to characters and numbers that can be loaded into tables and queries, and the actual image or picture of the logbook as written out by the permit holder.This image can be accessed on line by the data managers to assist in editing logbooks with invalid data. Sometimes the human eye is a more efficient tool at discerning handwritten data. For example, it is very difficult for the scanner to distinguish between a handwritten letter O and a hand written zero.Validation:None. This column may be left empty.
100
SOURCE_FILE VARCHAR2 Data_Source and Source_File are the same field.Name of the file that is loaded into the system.Validation:This name is entered by the user at the time the date are loaded. It is validated before entry begins to ensure that the data from this source file have not already been loaded. The source file name is then copied into this table for each reacord so that a batch of data can beeasily identified.
100
TRIP_TICKET VARCHAR2 Trip Ticket Number Assocaited WIth Landings Portion Of related record

Attribute Details

LOGBOOK_KEY

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

Sequence number automatically generated by the system to uniquely identify each row in the table. Since these keys are not data dependent, if any element of data is changed, the links to the other tables in the system are not broken.Validation:Managed by the database. Each row in the table must have a unique value.

General Data Type: NUMBER

SCHEDULE_NUMBER

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

A number stamped on each logbook form.Note: For the Pelagic Logbook, this number represents the trip number which in 1996 replaced the BATCH SEQUENCE NUMBER.Validation:A validation program ensures that the schedule number is unique within the interim tables and between the interim and master tables.

General Data Type: VARCHAR2

BATCH_NUMBER

CC ID: 27253
Seq. Order: 3
Data Storage Type: VARCHAR2
Max Length: 10
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 1994.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.Validation:None.

General Data Type: VARCHAR2

ID_NUMBER

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

A reference number used by the data entry contractors that enables them to uniquely identify each record.Validation:None. The column is optional.

General Data Type: VARCHAR2

VESSEL_ID

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

The ID of the vessel for which the logbook has been completed.Validation:A foreign key between this table and FLS_VESSEL_LIST ensures that only valid vessel ids can be entered into this table.The column is mandatory and may not be left empty.

General Data Type: VARCHAR2

DEPARTURE_DATE

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

Date when the vessel left port to begin the fishing activity. This field is now called START DATE on the form.Validation:The date must be a valid date as enforced by the DATE data type. A check constraint ensures that the departure date is less than the landing date.This column may be left empty, however, if days away from port and landing date are supplied, the system will calculate the departure date.

General Data Type: DATE

LANDING_DATE

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

Date when the catch was unloaded at a dealer. This field is now called UNLOAD DATE on the form. If the catch was unloaded at more than one dealer, this date represents the date when the catch was unloaded at the first dealer.Validation:The date must be a valid date as enforced by the DATE data type. Several Check constraints ensure that the Landing Date is greater than or equal to departure date, and that post mark date and opened date, are less than sent to data entry date.This column may not be left empty, because this date is used to determine if a vessel has met its reporting requirement for a given month.

General Data Type: DATE

UNLOAD_DATE

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

Date when the vessel unloaded the catch at the landing site.Validation:The date must be valid and cannot be null. The unload date must be greater than or equal to start date (i.e. departure date) A warning is issued if the unload date is less than the landing date.

General Data Type: DATE

OPENED_DATE

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

Date stamped on the logbook report. The RMD stamps this date on the form when they are retrieved from the post office and opened.Validation:The data must be a valid date.

General Data Type: DATE

DAYS_AWAY_FROM_PORT

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

Number of days spent away from port. Includes traveling time to and from the fishing area. Any fraction of a day counts as a whole day. If a vessel left in the morning and returned any time before midnight, fishers are instructed to report 1 day away from port.Validation:Must be a valid number.This column may be left empty, however, if departure date and landing date are supplied, the system will calculate the days away from port.

General Data Type: NUMBER

LOAD_DATE

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

Date on which the file was loaded into the Fisheries Logbook System.Validation:The date validation is enforced by the date type 'DATE'. Only valid dates can be entered into this column.

General Data Type: DATE

ACTIVITY_TYPE

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

Distinguishes between fishing and no fishing reports. This column is set automatically by the loading program, depending on the menu selection made by the user.Validation:The domain ACTIVITY TYPE allows only two choices Fishing or No Fishing. Null is not a valid entry because the column is mandatory.

General Data Type: VARCHAR2

POST_MARK_DATE

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

Date that is stamped by the post office on the logbook. It is unlikely that this column will be used. If it is used, it must be entered by the data managers.Validation:A valid data is ensured by the use of a DATE type column. Several check constraints ensure that Post Mark date is greater than or equal to Landing Date, greater than Opened Date, and less than Sent to Data Entry

General Data Type: DATE

RETURNED_TO_PERMIT_HOLDER

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

Reason why the data managers returned a logbook to a permit holder. This column must be entered by the person sending the logbook back.Validation:A domain called REASON_FOR_RETURN ensures that only valid reasons are entered. The column is not mandatory and may be left blank.

General Data Type: VARCHAR2

RETURNED_TO_PERMIT_HOLDER_DATE

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

Date on which a logbook is returned to the permit holder for corrections. Sometimes the fishers omit important information from the form that cannot be corrected by the data managers. There are also errors that can only be corrected by the permit holder. In this case, the logbook is mailed back to the permit holder with a letter indicating what is wrong with the logbook and an envelop to return the corrected form.Validation:A valid date is ensured by the use of a 'DATE' type column. In addition, several check constraints ensure that the Returned to Permit Holder Date is less than the Returned by Permit Holder Date and greater than or equal to Opened Date.

General Data Type: DATE

RETURNED_BY_PERMIT_HOLDER_DATE

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

Date on which the permit holder returned a logbook that needed corrections. This date must be entered by the data manager that received the logbook and adds it to a batch for processing.Validation:A valid date is ensured by the use of a DATE type column. A check constraint ensures that the Returned by Permit Holder Date is greater than the Returned to Permit Holder Date.

General Data Type: DATE

SENT_TO_DATA_ENTRY_DATE

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

Date on which the logbook forms were sent to the data entry contractor for scanning.Validation:A valid date is ensured through the use of the "DATE" data type. The field is optional and may be left blank. Three check constraints ensure that the Sent to Data Entry date is greater than or equal to Landing Date, Opened Date and Post Mark Date.

General Data Type: DATE

RETURNED_FROM_DATA_ENTRY_DATE

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

Date when the files of data scanned by the contractor were received at the SEFSC.Validation:A valid date is ensured by the use of the DATE data type of the column.

General Data Type: DATE

MOVED_TO_MASTER_DATE

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

Date on which the data has been completely validated and edited and moved into the master tables. When data are first scanned by the data entry contractor, they are loaded into Scanned Data tables that have a format less restrictive than the master tables. After editing, the data are distributed to the Master tables.This date is inserted automatically by the loading programs.Validation:Since the date is loaded by the program using the system date, this data is always correct. If a data manager were to change it, the 'DATE' data type of the column would prevent invalid dates from being inserted.

General Data Type: DATE

LOGBOOK_IMAGE_FILE

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

The legacy pc field, tif_no, is called logbook_image_file in the FLS master tables.When data are scanned, two products are obtained: data files, where the image is converted to characters and numbers that can be loaded into tables and queries, and the actual image or picture of the logbook as written out by the permit holder.This image can be accessed on line by the data managers to assist in editing logbooks with invalid data. Sometimes the human eye is a more efficient tool at discerning handwritten data. For example, it is very difficult for the scanner to distinguish between a handwritten letter O and a hand written zero.Validation:None. This column may be left empty.

General Data Type: VARCHAR2

SOURCE_FILE

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

Data_Source and Source_File are the same field.Name of the file that is loaded into the system.Validation:This name is entered by the user at the time the date are loaded. It is validated before entry begins to ensure that the data from this source file have not already been loaded. The source file name is then copied into this table for each reacord so that a batch of data can beeasily identified.

General Data Type: VARCHAR2

TRIP_TICKET

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

Trip Ticket Number Assocaited WIth Landings Portion Of related record

General Data Type: VARCHAR2

Catalog Details

Catalog Item ID: 7160
GUID: gov.noaa.nmfs.inport:7160
Metadata Record Created By: Lee M Weinberger
Metadata Record Created: 2008-02-28 14:10+0000
Metadata Record Last Modified By: Lee M Weinberger
Metadata Record Last Modified: 2021-05-06 22:24+0000
Metadata Record Published: 2021-05-06
Owner Org: SEFSC
Metadata Publication Status: Published Externally
Do Not Publish?: N
Metadata Next Review Date: 2022-05-07