Slide Menu
Search Help Show/Hide Menu

Item Identification

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

This shows the months and permit type for which a permit holder has sent a report. The screen View Logbooks by Vessel on the Track Logbooks menu shows a limited number of fields to easily show which reports were submitted for each vessel.

Notes:

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

Keywords

Theme Keywords

Thesaurus Keyword
UNCONTROLLED
None compliance
None reporting

Entity Information

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

This shows the months and permit type for which a permit holder has sent a report. The screen View Logbooks by Vessel on the Track Logbooks menu shows a limited number of fields to easily show which reports were submitted for each vessel.

Data Attributes

Attribute Summary

Rubric Score Primary Key? Name Type Description
100
Primary Key REPORTING_ACTIVITY_KEY NUMBER A unique identifier generated by the system.Validation:Information in the column must be numeric. The column is mandatory and cannot be left empty.
100
LOGBOOK_KEY NUMBER Foreign key to the FLS_LOGBOOKS_RECEIVED table.
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
ASSIGNED_MANAGEMENT_UNIT VARCHAR2 The permit type that applies to the logbook sent. Sometimes a single logbook can satisfy the reporting requirements of several of the permits held by the user.Validation:The domain PERMIT_TYPE on the table FLS_LOGBOOKS_RECEIVED ensures that only the values that are in the domain can be entered. Therefore, the permit types in this table are also valid.
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 enforce by the DATE data type. Several Check constraints ensure that the Landing Date is greater than or equal to departure date, post mark date, opened date, and 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
REPORTING_YEAR NUMBER The year when the catch was landed or unloaded. When we receive the logbook at SEFSC, we consider that the reporting requirement for the year has been met.If a vessel departed the year before they landed or unloaded the catch, the permit holder gets credit for both years and intervining months. The records that are added because of this are flagged in the column CREDITS_PREVIOUS_MONTH.Validation:The field is derived from LANDING_DATE on the table FLS_LOGBOOKS_RECEIVED and is assumed to be correct. The column is mandatory.
100
REPORTING_MONTH NUMBER The month when the catch was landed or unloaded. When we receive the logbook at SEFSC, we consider that the reporting requirement for the LANDING DATE month has been met.If a vessel departed the month or several months before it landed or unloaded the catch, the permit holder gets credit for all months between departure and landing date. The records that are added because of this are flagged in the column CREDITS_PREVIOUS_MONTH.Validation:The field is derived from LANDING_DATE on the table FLS_LOGBOOKS_RECEIVED and is assumed to be correct. The column is mandatory.
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
CREDITS_PREVIOUS_MONTH VARCHAR2 If a vessel departed the month or several months before it landed or unloaded the catch, the permit holder gets credit for all months between departure and landing date. The records that are added because of this are flagged in the column CREDITS_PREVIOUS_MONTH.Validation:Only yes and no are valid choices. Null is not acceptable because the column is mandatory.(Note: The column should be validated using the YES_NO domain.)
100
RECORD_COUNT NUMBER Record Count
100
PERMIT_CATEGORY VARCHAR2 General categories under which the SERO permits are grouped. The PERMIT_CATEGORY closely matches the Fisheries Management Units, except that in the Fisheries Management Units, the Sharks are broken down into Shark Unclassified, Small Coastal Shark, Large Pelagic Shark, and Large Coastal Shark.This classification is used by the Resporting Status portion of the FLS system to report on the logbooks that have been received by each permit category.
100
REPORTING_DATE DATE The first day of the reporting_month in the reporting year. This simplifies looking at reporting activity over different time periods.
100
ONLINE_ENTRY VARCHAR2 Set to 'Y' if the user was manually cleared by a data manager before records pass through the system. This is sometimes done when a fisherman tries to clear up a denied permit by faxing in a missing logbook that is hand checked and manually approved before the logbook gets sent to data entry for scanning.
100
REPORTING_PERMIT_CATEGORY VARCHAR2 The reporting permit category is 'SF' for Swordfish reporting requirements, and 'NSF' (Non-SwordFish) for all other distinct accountable permit categories. Presently, the reporting requirements for Gulf Reef Fish and Snapper Grouper are combined into the NSF reporting permit category.

Attribute Details

REPORTING_ACTIVITY_KEY

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

A unique identifier generated by the system.Validation:Information in the column must be numeric. The column is mandatory and cannot be left empty.

General Data Type: NUMBER

LOGBOOK_KEY

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

Foreign key to the FLS_LOGBOOKS_RECEIVED table.

General Data Type: NUMBER

VESSEL_ID

CC ID: 27324
Seq. Order: 3
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

ASSIGNED_MANAGEMENT_UNIT

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

The permit type that applies to the logbook sent. Sometimes a single logbook can satisfy the reporting requirements of several of the permits held by the user.Validation:The domain PERMIT_TYPE on the table FLS_LOGBOOKS_RECEIVED ensures that only the values that are in the domain can be entered. Therefore, the permit types in this table are also valid.

General Data Type: VARCHAR2

LANDING_DATE

CC ID: 27326
Seq. Order: 5
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 enforce by the DATE data type. Several Check constraints ensure that the Landing Date is greater than or equal to departure date, post mark date, opened date, and 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

REPORTING_YEAR

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

The year when the catch was landed or unloaded. When we receive the logbook at SEFSC, we consider that the reporting requirement for the year has been met.If a vessel departed the year before they landed or unloaded the catch, the permit holder gets credit for both years and intervining months. The records that are added because of this are flagged in the column CREDITS_PREVIOUS_MONTH.Validation:The field is derived from LANDING_DATE on the table FLS_LOGBOOKS_RECEIVED and is assumed to be correct. The column is mandatory.

General Data Type: NUMBER

REPORTING_MONTH

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

The month when the catch was landed or unloaded. When we receive the logbook at SEFSC, we consider that the reporting requirement for the LANDING DATE month has been met.If a vessel departed the month or several months before it landed or unloaded the catch, the permit holder gets credit for all months between departure and landing date. The records that are added because of this are flagged in the column CREDITS_PREVIOUS_MONTH.Validation:The field is derived from LANDING_DATE on the table FLS_LOGBOOKS_RECEIVED and is assumed to be correct. The column is mandatory.

General Data Type: NUMBER

ACTIVITY_TYPE

CC ID: 27329
Seq. Order: 8
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

CREDITS_PREVIOUS_MONTH

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

If a vessel departed the month or several months before it landed or unloaded the catch, the permit holder gets credit for all months between departure and landing date. The records that are added because of this are flagged in the column CREDITS_PREVIOUS_MONTH.Validation:Only yes and no are valid choices. Null is not acceptable because the column is mandatory.(Note: The column should be validated using the YES_NO domain.)

General Data Type: VARCHAR2

RECORD_COUNT

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

Record Count

General Data Type: NUMBER

PERMIT_CATEGORY

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

General categories under which the SERO permits are grouped. The PERMIT_CATEGORY closely matches the Fisheries Management Units, except that in the Fisheries Management Units, the Sharks are broken down into Shark Unclassified, Small Coastal Shark, Large Pelagic Shark, and Large Coastal Shark.This classification is used by the Resporting Status portion of the FLS system to report on the logbooks that have been received by each permit category.

General Data Type: VARCHAR2

REPORTING_DATE

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

The first day of the reporting_month in the reporting year. This simplifies looking at reporting activity over different time periods.

General Data Type: DATE

ONLINE_ENTRY

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

Set to 'Y' if the user was manually cleared by a data manager before records pass through the system. This is sometimes done when a fisherman tries to clear up a denied permit by faxing in a missing logbook that is hand checked and manually approved before the logbook gets sent to data entry for scanning.

General Data Type: VARCHAR2

REPORTING_PERMIT_CATEGORY

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

The reporting permit category is 'SF' for Swordfish reporting requirements, and 'NSF' (Non-SwordFish) for all other distinct accountable permit categories. Presently, the reporting requirements for Gulf Reef Fish and Snapper Grouper are combined into the NSF reporting permit category.

General Data Type: VARCHAR2

Catalog Details

Catalog Item ID: 7166
GUID: gov.noaa.nmfs.inport:7166
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