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

Summary

Abstract

This entity represents the offload of a vessel which is observed by the observer assigned to the processing plant. The data comes from ATL_Offload, and does not include offloads recorded by vessel observers.

Description

This entity represents the offload of a vessel which is observed by the observer assigned to the processing plant. The data comes from ATL_Offload, and does not include offloads recorded by vessel observers.

Entity Information

Entity Type
Data Table

Data Attribute / Type Description
T_TABLE
varchar2
Identifier of Source Table
OFFLOAD_JOIN
number
Surrogate FK to offload if salmon record is so derived Composed of concatenation of cruise, permit and offloadl_seq.
DELIVERY_VESSEL_ADFG
varchar2
ADFG number which may be entered by the plant observer without validation, this value is not internally validated at the time of entry.
CDQ_CODE
varchar2
Unique AlphaNumeric code representing a CDQ or research group
PGM_CODE
varchar2
Unique Identifier of a valid catcher vessel landing management program.
LANDING_REPORT_ID
number
The region uses the landing report id off the electronic fish ticket as a join column for the catch accounting system. The value is printed on the lower quadrant of every ER fish ticket. Landing_Report_ID is unique to an offload.
OFFLOAD_SEQ
number
Sequence generated unique identifier for an offload record
CRUISE
number
Sequence generated by Norpac and supplied to the observer as an unique identifier for a processing plant observer cruise record
PERMIT
VARCHAR2
Unique Code identifying a vessel or Processor - inherited from the NORPAC data set and created by the RAM division in Juneau
OFFLOAD_NUMBER
NUMBER
Unique offload for an observer cruise entered by the observer. The number must be unique within a cruise/permit combination.
PLANT_SEQ
NUMBER
Sequence generated unique identifier for a processing plant.
PLANT_CODE
VARCHAR2
VessPlnt code from old NORPAC system plus new plants recorded in ATL_LOV_Plant. This code may ultimately be retired, but is essential to the transitional ETL from Atlas to Inseason and Domestic.
PLANT_NAME
VARCHAR2
GEAR_TYPE_CODE
NUMBER
Numeric value from Norpac Domestic Gear that combined with the Form defines the unique identifier for a gear record
NMFS_AREA
VARCHAR2
NMFS Reporting Area
DELIVERED_WEIGHT_IN_KG
NUMBER
Identifies the total weight of all species delivered recorded in kilograms or lbs.
TOTAL_POLLOCK_WEIGHT_IN_KG
NUMBER
Identifies the total weight of pollock delivered recorded in kilograms or lbs.
DELIVERY_END_DATE
DATE
Date the delivery was complete.
LAST_MODIFIED_DATE
DATE
Everytime an offload record from the production schema is processed the the obsint.load_DEBRIEFED_offload the processing datetime is recorded here. This does not necessarily mean the DEBRIEFED offload record was modified as the program processes every offload within a cruise permit when initiated.
FISHING_START_DATE
DATE
Fishing start date is defined as the first haul deployment of a trip. If the deployment date is null due to unverifiable observer data then the trip start date is used; if null the default is a mandatory value haul retrieval date.
OFFLOAD_HASH
VARCHAR2
The offload hash is utilized by AKRO to identify changes to an offload record. The hash is created every time that a record is created or updated. Only critical data columns are referenced and change is denoted by a change in the hash value.
SALMON_HASH
VARCHAR2
The salmon hash is utilized by AKRO to identify changes to a salmon retention record. The hash is created every time that a record is created or updated. Only critical data columns are referenced and change is denoted by a change in the hash value.

Child Items

No Child Items for this record.

Contact Information

No contact information is available for this record.

Please contact the owner organization (AFSC) for inquiries on this record.

Item Identification

Title: DEBRIEFED OFFLOAD
Short Name: DEBRIEFED_OFFLOAD
Status: In Work
Abstract:

This entity represents the offload of a vessel which is observed by the observer assigned to the processing plant. The data comes from ATL_Offload, and does not include offloads recorded by vessel observers.

Purpose:

Provides a flattened and denormalized view of debriefed offload observer data for use by status of stocks authors and other researchers.

Keywords

Theme Keywords

Thesaurus Keyword
UNCONTROLLED
None AFSC
None DEBRIEFED
None DOMESTIC
None FMA
None GROUNDFISH
None HAKE
None NORPAC
None OBSERVER
None OBSINT
None POLLOCK

Temporal Keywords

Thesaurus Keyword
UNCONTROLLED
None CONTINUOUS

Spatial Keywords

Thesaurus Keyword
UNCONTROLLED
None AI
None ALASKA
None BS
None BSAI
None GOA
None NORTH PACIFIC

Stratum Keywords

Thesaurus Keyword
UNCONTROLLED
None DEMERSAL
None FIXED
None MOBILE
None OCEANIC
None PELEGIC

Physical Location

Organization: Alaska Fisheries Science Center
City: Seattle
State/Province: WA
Country: USA

Entity Information

Entity Type: Data Table
Alias: debriefed_haul
Schema Name: obsint
Description:

This entity represents the offload of a vessel which is observed by the observer assigned to the processing plant. The data comes from ATL_Offload, and does not include offloads recorded by vessel observers.

Data Attributes

Attribute Summary

Rubric Score Primary Key? Name Type Description
100
T_TABLE varchar2 Identifier of Source Table
100
OFFLOAD_JOIN number Surrogate FK to offload if salmon record is so derived Composed of concatenation of cruise, permit and offloadl_seq.
100
DELIVERY_VESSEL_ADFG varchar2 ADFG number which may be entered by the plant observer without validation, this value is not internally validated at the time of entry.
100
CDQ_CODE varchar2 Unique AlphaNumeric code representing a CDQ or research group
100
PGM_CODE varchar2 Unique Identifier of a valid catcher vessel landing management program.
100
LANDING_REPORT_ID number The region uses the landing report id off the electronic fish ticket as a join column for the catch accounting system. The value is printed on the lower quadrant of every ER fish ticket. Landing_Report_ID is unique to an offload.
100
OFFLOAD_SEQ number Sequence generated unique identifier for an offload record
100
CRUISE number Sequence generated by Norpac and supplied to the observer as an unique identifier for a processing plant observer cruise record
100
PERMIT VARCHAR2 Unique Code identifying a vessel or Processor - inherited from the NORPAC data set and created by the RAM division in Juneau
100
OFFLOAD_NUMBER NUMBER Unique offload for an observer cruise entered by the observer. The number must be unique within a cruise/permit combination.
100
PLANT_SEQ NUMBER Sequence generated unique identifier for a processing plant.
100
PLANT_CODE VARCHAR2 VessPlnt code from old NORPAC system plus new plants recorded in ATL_LOV_Plant. This code may ultimately be retired, but is essential to the transitional ETL from Atlas to Inseason and Domestic.
67
PLANT_NAME VARCHAR2
100
GEAR_TYPE_CODE NUMBER Numeric value from Norpac Domestic Gear that combined with the Form defines the unique identifier for a gear record
100
NMFS_AREA VARCHAR2 NMFS Reporting Area
100
DELIVERED_WEIGHT_IN_KG NUMBER Identifies the total weight of all species delivered recorded in kilograms or lbs.
100
TOTAL_POLLOCK_WEIGHT_IN_KG NUMBER Identifies the total weight of pollock delivered recorded in kilograms or lbs.
100
DELIVERY_END_DATE DATE Date the delivery was complete.
100
LAST_MODIFIED_DATE DATE Everytime an offload record from the production schema is processed the the obsint.load_DEBRIEFED_offload the processing datetime is recorded here. This does not necessarily mean the DEBRIEFED offload record was modified as the program processes every offload within a cruise permit when initiated.
100
FISHING_START_DATE DATE Fishing start date is defined as the first haul deployment of a trip. If the deployment date is null due to unverifiable observer data then the trip start date is used; if null the default is a mandatory value haul retrieval date.
100
OFFLOAD_HASH VARCHAR2 The offload hash is utilized by AKRO to identify changes to an offload record. The hash is created every time that a record is created or updated. Only critical data columns are referenced and change is denoted by a change in the hash value.
100
SALMON_HASH VARCHAR2 The salmon hash is utilized by AKRO to identify changes to a salmon retention record. The hash is created every time that a record is created or updated. Only critical data columns are referenced and change is denoted by a change in the hash value.

Attribute Details

T_TABLE

CC ID: 180005
Seq. Order: 1
Data Storage Type: varchar2
Max Length: 20
Required: Yes
Primary Key: No
Status: Active
Description:

Identifier of Source Table

OFFLOAD_JOIN

CC ID: 180006
Seq. Order: 2
Data Storage Type: number
Max Length: 20
Required: Yes
Primary Key: No
Status: Active
Description:

Surrogate FK to offload if salmon record is so derived Composed of concatenation of cruise, permit and offloadl_seq.

DELIVERY_VESSEL_ADFG

CC ID: 180007
Seq. Order: 3
Data Storage Type: varchar2
Max Length: 6
Required: No
Primary Key: No
Status: Active
Description:

ADFG number which may be entered by the plant observer without validation, this value is not internally validated at the time of entry.

CDQ_CODE

CC ID: 180008
Seq. Order: 4
Data Storage Type: varchar2
Max Length: 3
Required: No
Primary Key: No
Status: Active
Description:

Unique AlphaNumeric code representing a CDQ or research group

PGM_CODE

CC ID: 180009
Seq. Order: 5
Data Storage Type: varchar2
Max Length: 8
Required: No
Primary Key: No
Status: Active
Description:

Unique Identifier of a valid catcher vessel landing management program.

LANDING_REPORT_ID

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

The region uses the landing report id off the electronic fish ticket as a join column for the catch accounting system. The value is printed on the lower quadrant of every ER fish ticket. Landing_Report_ID is unique to an offload.

OFFLOAD_SEQ

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

Sequence generated unique identifier for an offload record

CRUISE

CC ID: 180012
Seq. Order: 8
Data Storage Type: number
Max Length: 9
Required: No
Primary Key: No
Status: Active
Description:

Sequence generated by Norpac and supplied to the observer as an unique identifier for a processing plant observer cruise record

PERMIT

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

Unique Code identifying a vessel or Processor - inherited from the NORPAC data set and created by the RAM division in Juneau

OFFLOAD_NUMBER

CC ID: 180014
Seq. Order: 10
Data Storage Type: NUMBER
Max Length: 9
Required: No
Primary Key: No
Status: Active
Description:

Unique offload for an observer cruise entered by the observer. The number must be unique within a cruise/permit combination.

PLANT_SEQ

CC ID: 180015
Seq. Order: 11
Data Storage Type: NUMBER
Max Length: 9
Required: No
Primary Key: No
Status: Active
Description:

Sequence generated unique identifier for a processing plant.

PLANT_CODE

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

VessPlnt code from old NORPAC system plus new plants recorded in ATL_LOV_Plant. This code may ultimately be retired, but is essential to the transitional ETL from Atlas to Inseason and Domestic.

PLANT_NAME

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

GEAR_TYPE_CODE

CC ID: 180018
Seq. Order: 14
Data Storage Type: NUMBER
Max Length: 3
Required: No
Primary Key: No
Status: Active
Description:

Numeric value from Norpac Domestic Gear that combined with the Form defines the unique identifier for a gear record

NMFS_AREA

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

NMFS Reporting Area

DELIVERED_WEIGHT_IN_KG

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

Identifies the total weight of all species delivered recorded in kilograms or lbs.

TOTAL_POLLOCK_WEIGHT_IN_KG

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

Identifies the total weight of pollock delivered recorded in kilograms or lbs.

DELIVERY_END_DATE

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

Date the delivery was complete.

LAST_MODIFIED_DATE

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

Everytime an offload record from the production schema is processed the the obsint.load_DEBRIEFED_offload the processing datetime is recorded here. This does not necessarily mean the DEBRIEFED offload record was modified as the program processes every offload within a cruise permit when initiated.

FISHING_START_DATE

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

Fishing start date is defined as the first haul deployment of a trip. If the deployment date is null due to unverifiable observer data then the trip start date is used; if null the default is a mandatory value haul retrieval date.

OFFLOAD_HASH

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

The offload hash is utilized by AKRO to identify changes to an offload record. The hash is created every time that a record is created or updated. Only critical data columns are referenced and change is denoted by a change in the hash value.

SALMON_HASH

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

The salmon hash is utilized by AKRO to identify changes to a salmon retention record. The hash is created every time that a record is created or updated. Only critical data columns are referenced and change is denoted by a change in the hash value.

Catalog Details

Catalog Item ID: 22441
GUID: gov.noaa.nmfs.inport:22441
Metadata Record Created By: Doug Turnbull
Metadata Record Created: 2014-11-05 13:36+0000
Metadata Record Last Modified By: SysAdmin InPortAdmin
Metadata Record Last Modified: 2022-08-09 17:11+0000
Metadata Record Published: 2016-05-18
Owner Org: AFSC
Metadata Publication Status: Published Externally
Do Not Publish?: N
Metadata Last Review Date: 2016-05-18
Metadata Review Frequency: 1 Year
Metadata Next Review Date: 2017-05-18