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

Summary

Abstract

Main view for purchase report data. Joins main purchase report tables and useful look-up tables. Replaces annual tables generated by DRS.

Description

Main view for purchase report data. Joins main purchase report tables and useful look-up tables. Replaces annual tables generated by DRS.

Entity Information

Entity Type
Data View

Data Attribute / Type Description
purchase_report_id
bigint
Identifies a unique purchase report.
data_source_code
varchar
Code that is abbreviation of data source. Example: Dealer Report System, code = DRS; Online Dealer Reports, code = ODR.
report_type_code
varchar
Code assigned to report type. Example: Tuna Handline Trip Report, code = TUNA; Cash Sales Report, code = CS, Purchase Report, code = P.
dealer_licensee_id
bigint
Identifies dealer who purchased catch for dealer reports, or the fisher who sold catch for Cash Sales Reports. For Cash Sales Reports, the fisher is also the dealer, therefore dealer_licensee_id = view_purchases.fisher_licensee_id.
dealer_license_number
int
Commercial marine dealer license number assigned to dealer by HDAR.
dealer_name
varchar
Full name of individual holding dealer license.
dealer_business_name
varchar
Name of business holding the license.
fisher_licensee_id
bigint
Identifies fisher who sold the catch listed on the purchase report.
fisher_license_number
int
Commercial marine fishing license number assigned to fisher by HDAR.
fisher_name
varchar
Full name of individual holding fishing license.
report_date
date
Date of purchase.
received_date
date
Date dealer submitted report online, or date staff received the paper report from the dealer.
vessel_id
varchar
Hawaii State (HA) or U.S. Coast Guard (UCSG) vessel registration/documentation number. Field will not be reported if a vessel was not used when fishing. Note: HA vessel registration number suffix indicates vessel use. Recreational use is denoted by letters 'A' through 'F'. Commercial fishing is denoted by 'CF'. Commercial passenger is denoted by 'CP'.
vessel_name
varchar
Name of fishing vessel that dealer purchased from. Vessel name is registered with State Division of Boating & Ocean Recreation. Field will not be reported if a vessel was not used when fishing. Was manually entered in DRS. ODR automatically fills this in based on vessel_id.
purchase_type_code
int
Code assigned to a purchase type.
purchase_type_name
varchar
Name of purchase type. Example: Initial Sale, Resale, etc.
purchase_report_comments
varchar
Comments submitted online through ODR regarding purchase. Different from view_purchases.purchase_comments, which are comments regarding purchases at the individual species level before ODR existed.
validation_status
enum
Validation status when adding report to ODR. Values include: Approved, Pending, Approved - No Response. Originally, meant to be used for tracking communication with dealers who appeared on Error Reports. A value of Approved would clear the dealer from the error report. However, due to a design flaw, the validation status is not currently being used in ODR.
trip_number
varchar
Number generated by UFA and FIF dealers who buy from fishers on purchase reports. Different from view_catch.logbook_number, which is number printed on NWHI Bottomfish Trip Daily Log sheet.
trip_type_code
varchar
Code for fishing trip type. Example: Handline, code = H; Longline, code = L, etc.
trip_type
varchar
Name of fishing trip type. Example: Bottomfish, Handline, Longline, etc.
purchase_id
bigint
Identifies a unique purchase record.
species_id
int
Code representing species that was purchased.
food_species_code
int
Codes associated with species collected for food from all HDAR forms except Aquarium forms. Different from view_purchases.aquarium_species_code, which are codes associated with species collected for aquarium. Note: food_species_code and view_purchases.aquarium_species_code have overlapping species but species codes are unique to each column, meaning the same fish can have a different code in each column. Example: Achilles Tang, food_species_code = 85 and view_purchases.aquarium_species_code = 103.
aquarium_species_code
int
Codes associated with species collected for aquariums. Codes are from HDAR Aquarium Fish Trip Report. Different from view_purchases.food_species_code, which are codes associated with species collected for food. Note: view_purchases.food_species_code and aquarium_species_code have overlapping species but species codes are unique to each column, meaning the same fish can have a different code in each column. Example: Achilles Tang, view_purchases.food_species_code = 85 and aquarium_species_code = 103.
food_name
text
Comma delimited list of names associated with a given species_id sold for food. Example: species_id = 2, food_name = Skipjack.
aquarium_name
text
Comma delimited list of names associated with a given species_id that are sold for aquariums. Example: species_id = 83, aquarium_name = Achilles Tang.
local_name
text
Comma delimited list of local names associated with a given species_id. Example: species_id = 2, local_name = Aku, Otado, Otaru.
display_name
mediumtext
Primary name displayed by applications and reports. Name come from species_common_name.name where species_common_name_type_code = 5 (Display Name). If no records where species_common_name_type_code = 5, species.scientific_name is used.
rank
varchar
Name of taxonomic ranking. Example: Kingdom, Subkingdom, Phylum, Subphylum, Class, etc.
scientific_name
varchar
Normally the binomial name, which consists of a generic name (the genus name) and the specific name (the species name). If species cannot be identified to the species level, it will be identified to the highest known taxonomic ranking, such as its phylum, class, infraclass, order, suborder, family, or subfamily. A genus name followed by 'spp.' refers to multiple species within that genus. A genus name followed by 'sp.' refers to one species. The scientific name for species identified at the rank of family or higher will be the name followed by the rank in parentheses. Example: Thunnus thynnus, Nerita spp., Scombridae (family), Anthozoa (class), etc. Different from common name.
species_category
varchar
Name of the category marine species falls under. Example: Shells, Seaweed, Freshwater fish, Bait Only, etc.
species_condition_code
varchar
Condition of the species when purchased. Used to estimate the number of pounds sold (whole weight). Required field for Cash Sales from OFR. Not required for ODR. List merges conditions from both OFR and ODR.
species_condition
varchar
Description of marine life condition when purchased. Example: Belly Only, Damage, Whole, etc.
pounds_bought
decimal
Weight (pounds) of each species purchased. Required unless species is exempt from reporting weight.
pieces_bought
decimal
Number of pieces purchased. If purchased in quantities such as akule, number of fish may have been estimated. Required unless species is exempt from reporting pieces.
total_value
decimal
Amount paid for marine life (US dollars).
exported
tinyint
If sold outside the state of Hawaii, value = 1; if not, value = 0. Only applicable to Aquarium Cash Sale Reports.
purchase_comments
varchar
Comments regarding the individual purchase before ODR existed. Different from view_purchases.purchase_report_comments, which are comments regarding the purchase from ODR.

Child Items

No Child Items for this record.

Contact Information

No contact information is available for this record.

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

Item Identification

Title: view_purchases
Status: Completed
Abstract:

Main view for purchase report data. Joins main purchase report tables and useful look-up tables. Replaces annual tables generated by DRS.

Entity Information

Entity Type: Data View
Active Version?: Yes
Schema Name: hawaii_dar_frds
Description:

Main view for purchase report data. Joins main purchase report tables and useful look-up tables. Replaces annual tables generated by DRS.

Data Attributes

Attribute Summary

Rubric Score Primary Key? Name Type Description
100
purchase_report_id bigint Identifies a unique purchase report.
100
data_source_code varchar Code that is abbreviation of data source. Example: Dealer Report System, code = DRS; Online Dealer Reports, code = ODR.
100
report_type_code varchar Code assigned to report type. Example: Tuna Handline Trip Report, code = TUNA; Cash Sales Report, code = CS, Purchase Report, code = P.
100
dealer_licensee_id bigint Identifies dealer who purchased catch for dealer reports, or the fisher who sold catch for Cash Sales Reports. For Cash Sales Reports, the fisher is also the dealer, therefore dealer_licensee_id = view_purchases.fisher_licensee_id.
100
dealer_license_number int Commercial marine dealer license number assigned to dealer by HDAR.
100
dealer_name varchar Full name of individual holding dealer license.
100
dealer_business_name varchar Name of business holding the license.
100
fisher_licensee_id bigint Identifies fisher who sold the catch listed on the purchase report.
100
fisher_license_number int Commercial marine fishing license number assigned to fisher by HDAR.
100
fisher_name varchar Full name of individual holding fishing license.
100
report_date date Date of purchase.
100
received_date date Date dealer submitted report online, or date staff received the paper report from the dealer.
100
vessel_id varchar Hawaii State (HA) or U.S. Coast Guard (UCSG) vessel registration/documentation number. Field will not be reported if a vessel was not used when fishing. Note: HA vessel registration number suffix indicates vessel use. Recreational use is denoted by letters 'A' through 'F'. Commercial fishing is denoted by 'CF'. Commercial passenger is denoted by 'CP'.
100
vessel_name varchar Name of fishing vessel that dealer purchased from. Vessel name is registered with State Division of Boating & Ocean Recreation. Field will not be reported if a vessel was not used when fishing. Was manually entered in DRS. ODR automatically fills this in based on vessel_id.
100
purchase_type_code int Code assigned to a purchase type.
100
purchase_type_name varchar Name of purchase type. Example: Initial Sale, Resale, etc.
100
purchase_report_comments varchar Comments submitted online through ODR regarding purchase. Different from view_purchases.purchase_comments, which are comments regarding purchases at the individual species level before ODR existed.
100
validation_status enum Validation status when adding report to ODR. Values include: Approved, Pending, Approved - No Response. Originally, meant to be used for tracking communication with dealers who appeared on Error Reports. A value of Approved would clear the dealer from the error report. However, due to a design flaw, the validation status is not currently being used in ODR.
100
trip_number varchar Number generated by UFA and FIF dealers who buy from fishers on purchase reports. Different from view_catch.logbook_number, which is number printed on NWHI Bottomfish Trip Daily Log sheet.
100
trip_type_code varchar Code for fishing trip type. Example: Handline, code = H; Longline, code = L, etc.
100
trip_type varchar Name of fishing trip type. Example: Bottomfish, Handline, Longline, etc.
100
purchase_id bigint Identifies a unique purchase record.
100
species_id int Code representing species that was purchased.
100
food_species_code int Codes associated with species collected for food from all HDAR forms except Aquarium forms. Different from view_purchases.aquarium_species_code, which are codes associated with species collected for aquarium. Note: food_species_code and view_purchases.aquarium_species_code have overlapping species but species codes are unique to each column, meaning the same fish can have a different code in each column. Example: Achilles Tang, food_species_code = 85 and view_purchases.aquarium_species_code = 103.
100
aquarium_species_code int Codes associated with species collected for aquariums. Codes are from HDAR Aquarium Fish Trip Report. Different from view_purchases.food_species_code, which are codes associated with species collected for food. Note: view_purchases.food_species_code and aquarium_species_code have overlapping species but species codes are unique to each column, meaning the same fish can have a different code in each column. Example: Achilles Tang, view_purchases.food_species_code = 85 and aquarium_species_code = 103.
100
food_name text Comma delimited list of names associated with a given species_id sold for food. Example: species_id = 2, food_name = Skipjack.
100
aquarium_name text Comma delimited list of names associated with a given species_id that are sold for aquariums. Example: species_id = 83, aquarium_name = Achilles Tang.
100
local_name text Comma delimited list of local names associated with a given species_id. Example: species_id = 2, local_name = Aku, Otado, Otaru.
100
display_name mediumtext Primary name displayed by applications and reports. Name come from species_common_name.name where species_common_name_type_code = 5 (Display Name). If no records where species_common_name_type_code = 5, species.scientific_name is used.
100
rank varchar Name of taxonomic ranking. Example: Kingdom, Subkingdom, Phylum, Subphylum, Class, etc.
100
scientific_name varchar Normally the binomial name, which consists of a generic name (the genus name) and the specific name (the species name). If species cannot be identified to the species level, it will be identified to the highest known taxonomic ranking, such as its phylum, class, infraclass, order, suborder, family, or subfamily. A genus name followed by 'spp.' refers to multiple species within that genus. A genus name followed by 'sp.' refers to one species. The scientific name for species identified at the rank of family or higher will be the name followed by the rank in parentheses. Example: Thunnus thynnus, Nerita spp., Scombridae (family), Anthozoa (class), etc. Different from common name.
100
species_category varchar Name of the category marine species falls under. Example: Shells, Seaweed, Freshwater fish, Bait Only, etc.
100
species_condition_code varchar Condition of the species when purchased. Used to estimate the number of pounds sold (whole weight). Required field for Cash Sales from OFR. Not required for ODR. List merges conditions from both OFR and ODR.
100
species_condition varchar Description of marine life condition when purchased. Example: Belly Only, Damage, Whole, etc.
100
pounds_bought decimal Weight (pounds) of each species purchased. Required unless species is exempt from reporting weight.
100
pieces_bought decimal Number of pieces purchased. If purchased in quantities such as akule, number of fish may have been estimated. Required unless species is exempt from reporting pieces.
100
total_value decimal Amount paid for marine life (US dollars).
100
exported tinyint If sold outside the state of Hawaii, value = 1; if not, value = 0. Only applicable to Aquarium Cash Sale Reports.
100
purchase_comments varchar Comments regarding the individual purchase before ODR existed. Different from view_purchases.purchase_report_comments, which are comments regarding the purchase from ODR.

Attribute Details

purchase_report_id

CC ID: 1273892
Seq. Order: 1
Data Storage Type: bigint
Required: Yes
Primary Key: No
Precision: 19
Scale: 0
Status: Active
Description:

Identifies a unique purchase report.

Default Value: 0

data_source_code

CC ID: 1273893
Seq. Order: 2
Data Storage Type: varchar
Max Length: 4
Required: Yes
Primary Key: No
Status: Active
Description:

Code that is abbreviation of data source. Example: Dealer Report System, code = DRS; Online Dealer Reports, code = ODR.

report_type_code

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

Code assigned to report type. Example: Tuna Handline Trip Report, code = TUNA; Cash Sales Report, code = CS, Purchase Report, code = P.

dealer_licensee_id

CC ID: 1273895
Seq. Order: 4
Data Storage Type: bigint
Required: No
Primary Key: No
Precision: 19
Scale: 0
Status: Active
Description:

Identifies dealer who purchased catch for dealer reports, or the fisher who sold catch for Cash Sales Reports. For Cash Sales Reports, the fisher is also the dealer, therefore dealer_licensee_id = view_purchases.fisher_licensee_id.

Default Value: 0

dealer_license_number

CC ID: 1273896
Seq. Order: 5
Data Storage Type: int
Required: No
Primary Key: No
Precision: 10
Scale: 0
Status: Active
Description:

Commercial marine dealer license number assigned to dealer by HDAR.

dealer_name

CC ID: 1273897
Seq. Order: 6
Data Storage Type: varchar
Max Length: 192
Required: No
Primary Key: No
Status: Active
Description:

Full name of individual holding dealer license.

dealer_business_name

CC ID: 1273898
Seq. Order: 7
Data Storage Type: varchar
Max Length: 64
Required: No
Primary Key: No
Status: Active
Description:

Name of business holding the license.

fisher_licensee_id

CC ID: 1273899
Seq. Order: 8
Data Storage Type: bigint
Required: No
Primary Key: No
Precision: 19
Scale: 0
Status: Active
Description:

Identifies fisher who sold the catch listed on the purchase report.

Default Value: 0

fisher_license_number

CC ID: 1273900
Seq. Order: 9
Data Storage Type: int
Required: No
Primary Key: No
Precision: 10
Scale: 0
Status: Active
Description:

Commercial marine fishing license number assigned to fisher by HDAR.

fisher_name

CC ID: 1273901
Seq. Order: 10
Data Storage Type: varchar
Max Length: 192
Required: No
Primary Key: No
Status: Active
Description:

Full name of individual holding fishing license.

report_date

CC ID: 1273902
Seq. Order: 11
Data Storage Type: date
Required: Yes
Primary Key: No
Status: Active
Description:

Date of purchase.

received_date

CC ID: 1273903
Seq. Order: 12
Data Storage Type: date
Required: No
Primary Key: No
Status: Active
Description:

Date dealer submitted report online, or date staff received the paper report from the dealer.

vessel_id

CC ID: 1273904
Seq. Order: 13
Data Storage Type: varchar
Max Length: 255
Required: No
Primary Key: No
Status: Active
Description:

Hawaii State (HA) or U.S. Coast Guard (UCSG) vessel registration/documentation number. Field will not be reported if a vessel was not used when fishing.

Note: HA vessel registration number suffix indicates vessel use. Recreational use is denoted by letters 'A' through 'F'. Commercial fishing is denoted by 'CF'. Commercial passenger is denoted by 'CP'.

vessel_name

CC ID: 1273905
Seq. Order: 14
Data Storage Type: varchar
Max Length: 255
Required: No
Primary Key: No
Status: Active
Description:

Name of fishing vessel that dealer purchased from. Vessel name is registered with State Division of Boating & Ocean Recreation. Field will not be reported if a vessel was not used when fishing. Was manually entered in DRS. ODR automatically fills this in based on vessel_id.

purchase_type_code

CC ID: 1273906
Seq. Order: 15
Data Storage Type: int
Required: Yes
Primary Key: No
Precision: 10
Scale: 0
Status: Active
Description:

Code assigned to a purchase type.

Default Value: 1

purchase_type_name

CC ID: 1273907
Seq. Order: 16
Data Storage Type: varchar
Max Length: 25
Required: No
Primary Key: No
Status: Active
Description:

Name of purchase type. Example: Initial Sale, Resale, etc.

purchase_report_comments

CC ID: 1273908
Seq. Order: 17
Data Storage Type: varchar
Max Length: 1024
Required: No
Primary Key: No
Status: Active
Description:

Comments submitted online through ODR regarding purchase. Different from view_purchases.purchase_comments, which are comments regarding purchases at the individual species level before ODR existed.

validation_status

CC ID: 1273909
Seq. Order: 18
Data Storage Type: enum
Max Length: 21
Required: No
Primary Key: No
Status: Active
Description:

Validation status when adding report to ODR. Values include: Approved, Pending, Approved - No Response. Originally, meant to be used for tracking communication with dealers who appeared on Error Reports. A value of Approved would clear the dealer from the error report. However, due to a design flaw, the validation status is not currently being used in ODR.

trip_number

CC ID: 1273910
Seq. Order: 19
Data Storage Type: varchar
Max Length: 32
Required: No
Primary Key: No
Status: Active
Description:

Number generated by UFA and FIF dealers who buy from fishers on purchase reports. Different from view_catch.logbook_number, which is number printed on NWHI Bottomfish Trip Daily Log sheet.

trip_type_code

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

Code for fishing trip type. Example: Handline, code = H; Longline, code = L, etc.

trip_type

CC ID: 1273912
Seq. Order: 21
Data Storage Type: varchar
Max Length: 50
Required: No
Primary Key: No
Status: Active
Description:

Name of fishing trip type. Example: Bottomfish, Handline, Longline, etc.

purchase_id

CC ID: 1273913
Seq. Order: 22
Data Storage Type: bigint
Required: No
Primary Key: No
Precision: 19
Scale: 0
Status: Active
Description:

Identifies a unique purchase record.

Default Value: 0

species_id

CC ID: 1273914
Seq. Order: 23
Data Storage Type: int
Required: No
Primary Key: No
Precision: 10
Scale: 0
Status: Active
Description:

Code representing species that was purchased.

Default Value: 0

food_species_code

CC ID: 1273915
Seq. Order: 24
Data Storage Type: int
Required: No
Primary Key: No
Precision: 10
Scale: 0
Status: Active
Description:

Codes associated with species collected for food from all HDAR forms except Aquarium forms. Different from view_purchases.aquarium_species_code, which are codes associated with species collected for aquarium. Note: food_species_code and view_purchases.aquarium_species_code have overlapping species but species codes are unique to each column, meaning the same fish can have a different code in each column. Example: Achilles Tang, food_species_code = 85 and view_purchases.aquarium_species_code = 103.

aquarium_species_code

CC ID: 1273916
Seq. Order: 25
Data Storage Type: int
Required: No
Primary Key: No
Precision: 10
Scale: 0
Status: Active
Description:

Codes associated with species collected for aquariums. Codes are from HDAR Aquarium Fish Trip Report. Different from view_purchases.food_species_code, which are codes associated with species collected for food. Note: view_purchases.food_species_code and aquarium_species_code have overlapping species but species codes are unique to each column, meaning the same fish can have a different code in each column. Example: Achilles Tang, view_purchases.food_species_code = 85 and aquarium_species_code = 103.

food_name

CC ID: 1273917
Seq. Order: 26
Data Storage Type: text
Max Length: 65535
Required: No
Primary Key: No
Status: Active
Description:

Comma delimited list of names associated with a given species_id sold for food. Example: species_id = 2, food_name = Skipjack.

aquarium_name

CC ID: 1273918
Seq. Order: 27
Data Storage Type: text
Max Length: 65535
Required: No
Primary Key: No
Status: Active
Description:

Comma delimited list of names associated with a given species_id that are sold for aquariums. Example: species_id = 83, aquarium_name = Achilles Tang.

local_name

CC ID: 1273919
Seq. Order: 28
Data Storage Type: text
Max Length: 65535
Required: No
Primary Key: No
Status: Active
Description:

Comma delimited list of local names associated with a given species_id. Example: species_id = 2, local_name = Aku, Otado, Otaru.

display_name

CC ID: 1273920
Seq. Order: 29
Data Storage Type: mediumtext
Max Length: 16777215
Required: No
Primary Key: No
Status: Active
Description:

Primary name displayed by applications and reports. Name come from species_common_name.name where species_common_name_type_code = 5 (Display Name). If no records where species_common_name_type_code = 5, species.scientific_name is used.

rank

CC ID: 1273921
Seq. Order: 30
Data Storage Type: varchar
Max Length: 20
Required: No
Primary Key: No
Status: Active
Description:

Name of taxonomic ranking. Example: Kingdom, Subkingdom, Phylum, Subphylum, Class, etc.

scientific_name

CC ID: 1273922
Seq. Order: 31
Data Storage Type: varchar
Max Length: 125
Required: No
Primary Key: No
Status: Active
Description:

Normally the binomial name, which consists of a generic name (the genus name) and the specific name (the species name). If species cannot be identified to the species level, it will be identified to the highest known taxonomic ranking, such as its phylum, class, infraclass, order, suborder, family, or subfamily. A genus name followed by 'spp.' refers to multiple species within that genus. A genus name followed by 'sp.' refers to one species. The scientific name for species identified at the rank of family or higher will be the name followed by the rank in parentheses. Example: Thunnus thynnus, Nerita spp., Scombridae (family), Anthozoa (class), etc. Different from common name.

species_category

CC ID: 1273923
Seq. Order: 32
Data Storage Type: varchar
Max Length: 40
Required: No
Primary Key: No
Status: Active
Description:

Name of the category marine species falls under. Example: Shells, Seaweed, Freshwater fish, Bait Only, etc.

species_condition_code

CC ID: 1273924
Seq. Order: 33
Data Storage Type: varchar
Max Length: 5
Required: No
Primary Key: No
Status: Active
Description:

Condition of the species when purchased. Used to estimate the number of pounds sold (whole weight). Required field for Cash Sales from OFR. Not required for ODR. List merges conditions from both OFR and ODR.

species_condition

CC ID: 1273925
Seq. Order: 34
Data Storage Type: varchar
Max Length: 100
Required: No
Primary Key: No
Status: Active
Description:

Description of marine life condition when purchased. Example: Belly Only, Damage, Whole, etc.

pounds_bought

CC ID: 1273926
Seq. Order: 35
Data Storage Type: decimal
Required: No
Primary Key: No
Precision: 17
Scale: 2
Status: Active
Description:

Weight (pounds) of each species purchased. Required unless species is exempt from reporting weight.

pieces_bought

CC ID: 1273927
Seq. Order: 36
Data Storage Type: decimal
Required: No
Primary Key: No
Precision: 17
Scale: 2
Status: Active
Description:

Number of pieces purchased. If purchased in quantities such as akule, number of fish may have been estimated. Required unless species is exempt from reporting pieces.

total_value

CC ID: 1273928
Seq. Order: 37
Data Storage Type: decimal
Required: No
Primary Key: No
Precision: 17
Scale: 2
Status: Active
Description:

Amount paid for marine life (US dollars).

exported

CC ID: 1273929
Seq. Order: 38
Data Storage Type: tinyint
Required: No
Primary Key: No
Precision: 3
Scale: 0
Status: Active
Description:

If sold outside the state of Hawaii, value = 1; if not, value = 0. Only applicable to Aquarium Cash Sale Reports.

Default Value: 0

purchase_comments

CC ID: 1273930
Seq. Order: 39
Data Storage Type: varchar
Max Length: 1024
Required: No
Primary Key: No
Status: Active
Description:

Comments regarding the individual purchase before ODR existed. Different from view_purchases.purchase_report_comments, which are comments regarding the purchase from ODR.

Catalog Details

Catalog Item ID: 65076
GUID: gov.noaa.nmfs.inport:65076
Metadata Record Created By: Bradley M Gough
Metadata Record Created: 2021-07-27 02:22+0000
Metadata Record Last Modified By: Bradley M Gough
Metadata Record Last Modified: 2023-09-23 00:43+0000
Metadata Record Published: 2023-09-23
Owner Org: PIFSC
Metadata Publication Status: Published Externally
Do Not Publish?: N
Metadata Review Frequency: 1 Year