Table: PDC_HEADERS
Entity (ENT) | Southeast Fisheries Science Center (SEFSC)GUID: gov.noaa.nmfs.inport:5405 | Updated: August 9, 2022 | Published / External
-
View As
- Full List View
- Printable Form
- EXPORTS
- InPort XML
- View in Hierarchy
Summary
The Header Information from the Pelagic Dealer LOgbook forms.
DescriptionThe Header Information from the Pelagic Dealer LOgbook forms.
Entity Information
Entity Type
Data Table
Data Attribute / Type | Description |
---|---|
PDC_HEADER_KEY
NUMBER |
Primary Key of This Table |
PC_ARTIFICIAL_KEY
NUMBER |
This is the artificial key to link the Header , vessel and purchase tables on the old PC SDC system. This column was generated as records were added. |
BATCH_YEAR
VARCHAR2 |
Year Of The schedule.This column is derived from the 4 digit year of the BEGIN_DATE.This column is necesssary because there were some years in which the Schedule NUmbers were recycled for the year before, so to get a unique key it was necessary to use Year and Schedule. |
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 systemThe actual unique key is SCHEDULE + BATCH_YEAR. |
SE_PERMIT_NUMBER
VARCHAR2 |
This is the permit number issued by the Southeast Regional Office for Swordfish and Shark dealers. It is comprised of 4 letters, up to 4 numbers, followed by 2 digits for the year, e.g., DLR-LA-1234-01. Only the center numbers of the permit (e.g., 1234) are entered in the permit files provided by the SE office, as well as into the Swordfish Compliance Program. Updated dealer permit numbers are downloaded and saved in n:\sdc\dbf\dlr_new.dbf.If a Swordfish or Shark dealer (indicated by a SE permit number) also has a Tuna dealer permit (indicated by a NE permit number), it would be helpful if the NE number was automatically entered with the SE permit number. These dealers with both NE and SE issued permits are currently linked in the above mentioned file, dlr_new.dbf. |
NE_PERMIT_NUMBER
VARCHAR2 |
This is the permit number issued by the Northeast Regional Office for Tuna dealers. It was once a 5 digit number, zero filled. Now it ranges from 3-4 digits, and not zero filled. |
NMFS_STATE_CODE
VARCHAR2 |
NMFS State code corresponing to the Dealerlocation.Thiscolumn is filled in on data entry. |
NMFS_COUNTY_CODE
VARCHAR2 |
NMFS County code corresponing to the Dealerlocation.Thiscolumn is filled in on data entry. |
ALPHA_STATE_CODE
VARCHAR2 |
Two letter state abbreviation corresponing to the Dealerlocation.Thiscolumn is filled in on data entry. |
BEGIN_DATE
DATE |
This is the date that the reporting period begins. This date is often the first or the 16th of each month. |
END_DATE
DATE |
This is the date that the reporting period ends. This date is often the 15th or the last day of each month. |
FACILITY_LOCATION
VARCHAR2 |
The port of landing of the vessel |
PHONE_NUMBER
VARCHAR2 |
This is the number that a person at the dealer facility can be reached in case of questions. This field may be blank. This field is entered in by the vendor, but is not being entered by SEFSC staff. |
SCAN_ID
VARCHAR2 |
Date entered by vendor |
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 iss |
PURCHASE_FISH
VARCHAR2 |
This is a yes/no field. If the dealer did not purchase any highly migratory species during the 2 week period, the 'no' is checked. |
FISH_IMPORTED
VARCHAR2 |
Indicates whether or not the data reported included imports in addition to domestic purchases. |
VESSEL_DATA
VARCHAR2 |
A vestigal column from old PC System which indicated whether or not there was vessel data on the logbook form. |
EDIT_DATA
VARCHAR2 |
A vestigal column from old PC System which indicated whether or not data had to be corrected due to judgment of data manager. |
WEIGH_OUT
VARCHAR2 |
his indicates whether or not tally sheets (weigh out data) were provided with the HMS form. This aids in locating weigh out sheets upon request. |
TIF_NUMBER
VARCHAR2 |
The scan images provided by the vendor |
ID_NUMBER
VARCHAR2 |
Assigned By Vendor Software During Data Entry |
RECEIVED_DATE
DATE |
Date Logbook Form was received. |
POSTMARK_DATE
DATE |
Date in which envelope containing the logbook form was post marked. |
Child Items
No Child Items for this record.
Contact Information
No contact information is available for this record.
Please contact the owner organization (SEFSC) for inquiries on this record.
Item Identification
Title: | Table: PDC_HEADERS |
---|---|
Short Name: | PDC_HEADERS |
Status: | Completed |
Abstract: |
The Header Information from the Pelagic Dealer LOgbook forms. |
Notes: |
Loaded by batch 1703, 10-15-2007 10:13 |
Entity Information
Entity Type: | Data Table |
---|---|
Active Version?: | Yes |
Schema Name: | FLS |
Description: |
The Header Information from the Pelagic Dealer LOgbook forms. |
Data Attributes
Attribute Summary
Name | Type | Description | ||
---|---|---|---|---|
100
|
PDC_HEADER_KEY | NUMBER | Primary Key of This Table | |
100
|
PC_ARTIFICIAL_KEY | NUMBER | This is the artificial key to link the Header , vessel and purchase tables on the old PC SDC system. This column was generated as records were added. | |
100
|
BATCH_YEAR | VARCHAR2 | Year Of The schedule.This column is derived from the 4 digit year of the BEGIN_DATE.This column is necesssary because there were some years in which the Schedule NUmbers were recycled for the year before, so to get a unique key it was necessary to use Year and Schedule. | |
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 systemThe actual unique key is SCHEDULE + BATCH_YEAR. | |
100
|
SE_PERMIT_NUMBER | VARCHAR2 | This is the permit number issued by the Southeast Regional Office for Swordfish and Shark dealers. It is comprised of 4 letters, up to 4 numbers, followed by 2 digits for the year, e.g., DLR-LA-1234-01. Only the center numbers of the permit (e.g., 1234) are entered in the permit files provided by the SE office, as well as into the Swordfish Compliance Program. Updated dealer permit numbers are downloaded and saved in n:\sdc\dbf\dlr_new.dbf.If a Swordfish or Shark dealer (indicated by a SE permit number) also has a Tuna dealer permit (indicated by a NE permit number), it would be helpful if the NE number was automatically entered with the SE permit number. These dealers with both NE and SE issued permits are currently linked in the above mentioned file, dlr_new.dbf. | |
100
|
NE_PERMIT_NUMBER | VARCHAR2 | This is the permit number issued by the Northeast Regional Office for Tuna dealers. It was once a 5 digit number, zero filled. Now it ranges from 3-4 digits, and not zero filled. | |
100
|
NMFS_STATE_CODE | VARCHAR2 | NMFS State code corresponing to the Dealerlocation.Thiscolumn is filled in on data entry. | |
100
|
NMFS_COUNTY_CODE | VARCHAR2 | NMFS County code corresponing to the Dealerlocation.Thiscolumn is filled in on data entry. | |
100
|
ALPHA_STATE_CODE | VARCHAR2 | Two letter state abbreviation corresponing to the Dealerlocation.Thiscolumn is filled in on data entry. | |
100
|
BEGIN_DATE | DATE | This is the date that the reporting period begins. This date is often the first or the 16th of each month. | |
100
|
END_DATE | DATE | This is the date that the reporting period ends. This date is often the 15th or the last day of each month. | |
100
|
FACILITY_LOCATION | VARCHAR2 | The port of landing of the vessel | |
100
|
PHONE_NUMBER | VARCHAR2 | This is the number that a person at the dealer facility can be reached in case of questions. This field may be blank. This field is entered in by the vendor, but is not being entered by SEFSC staff. | |
100
|
SCAN_ID | VARCHAR2 | Date entered by vendor | |
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 iss | |
100
|
PURCHASE_FISH | VARCHAR2 | This is a yes/no field. If the dealer did not purchase any highly migratory species during the 2 week period, the 'no' is checked. | |
100
|
FISH_IMPORTED | VARCHAR2 | Indicates whether or not the data reported included imports in addition to domestic purchases. | |
100
|
VESSEL_DATA | VARCHAR2 | A vestigal column from old PC System which indicated whether or not there was vessel data on the logbook form. | |
100
|
EDIT_DATA | VARCHAR2 | A vestigal column from old PC System which indicated whether or not data had to be corrected due to judgment of data manager. | |
100
|
WEIGH_OUT | VARCHAR2 | his indicates whether or not tally sheets (weigh out data) were provided with the HMS form. This aids in locating weigh out sheets upon request. | |
100
|
TIF_NUMBER | VARCHAR2 | The scan images provided by the vendor | |
100
|
ID_NUMBER | VARCHAR2 | Assigned By Vendor Software During Data Entry | |
100
|
RECEIVED_DATE | DATE | Date Logbook Form was received. | |
100
|
POSTMARK_DATE | DATE | Date in which envelope containing the logbook form was post marked. |
Attribute Details
PDC_HEADER_KEY
Seq. Order: | 1 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | Yes |
Primary Key: | Yes |
Precision: | 10 |
Scale: | 0 |
Status: | Active |
Description: |
Primary Key of This Table |
General Data Type: | NUMBER |
PC_ARTIFICIAL_KEY
Seq. Order: | 2 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 10 |
Scale: | 0 |
Status: | Active |
Description: |
This is the artificial key to link the Header , vessel and purchase tables on the old PC SDC system. This column was generated as records were added. |
General Data Type: | NUMBER |
BATCH_YEAR
Seq. Order: | 3 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 4 |
Required: | Yes |
Primary Key: | No |
Status: | Active |
Description: |
Year Of The schedule.This column is derived from the 4 digit year of the BEGIN_DATE.This column is necesssary because there were some years in which the Schedule NUmbers were recycled for the year before, so to get a unique key it was necessary to use Year and Schedule. |
General Data Type: | VARCHAR2 |
SCHEDULE
Seq. Order: | 4 |
---|---|
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 systemThe actual unique key is SCHEDULE + BATCH_YEAR. |
General Data Type: | VARCHAR2 |
SE_PERMIT_NUMBER
Seq. Order: | 5 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 5 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This is the permit number issued by the Southeast Regional Office for Swordfish and Shark dealers. It is comprised of 4 letters, up to 4 numbers, followed by 2 digits for the year, e.g., DLR-LA-1234-01. Only the center numbers of the permit (e.g., 1234) are entered in the permit files provided by the SE office, as well as into the Swordfish Compliance Program. Updated dealer permit numbers are downloaded and saved in n:\sdc\dbf\dlr_new.dbf.If a Swordfish or Shark dealer (indicated by a SE permit number) also has a Tuna dealer permit (indicated by a NE permit number), it would be helpful if the NE number was automatically entered with the SE permit number. These dealers with both NE and SE issued permits are currently linked in the above mentioned file, dlr_new.dbf. |
General Data Type: | VARCHAR2 |
NE_PERMIT_NUMBER
Seq. Order: | 6 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 5 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This is the permit number issued by the Northeast Regional Office for Tuna dealers. It was once a 5 digit number, zero filled. Now it ranges from 3-4 digits, and not zero filled. |
General Data Type: | VARCHAR2 |
NMFS_STATE_CODE
Seq. Order: | 7 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 2 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
NMFS State code corresponing to the Dealerlocation.Thiscolumn is filled in on data entry. |
General Data Type: | VARCHAR2 |
NMFS_COUNTY_CODE
Seq. Order: | 8 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 3 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
NMFS County code corresponing to the Dealerlocation.Thiscolumn is filled in on data entry. |
General Data Type: | VARCHAR2 |
ALPHA_STATE_CODE
Seq. Order: | 9 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 2 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Two letter state abbreviation corresponing to the Dealerlocation.Thiscolumn is filled in on data entry. |
General Data Type: | VARCHAR2 |
BEGIN_DATE
Seq. Order: | 10 |
---|---|
Data Storage Type: | DATE |
Max Length: | 7 |
Required: | Yes |
Primary Key: | No |
Status: | Active |
Description: |
This is the date that the reporting period begins. This date is often the first or the 16th of each month. |
General Data Type: | DATE |
END_DATE
Seq. Order: | 11 |
---|---|
Data Storage Type: | DATE |
Max Length: | 7 |
Required: | Yes |
Primary Key: | No |
Status: | Active |
Description: |
This is the date that the reporting period ends. This date is often the 15th or the last day of each month. |
General Data Type: | DATE |
FACILITY_LOCATION
Seq. Order: | 12 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 20 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The port of landing of the vessel |
General Data Type: | VARCHAR2 |
PHONE_NUMBER
Seq. Order: | 13 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 20 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This is the number that a person at the dealer facility can be reached in case of questions. This field may be blank. This field is entered in by the vendor, but is not being entered by SEFSC staff. |
General Data Type: | VARCHAR2 |
SCAN_ID
Seq. Order: | 14 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 20 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Date entered by vendor |
General Data Type: | VARCHAR2 |
BATCH_NUMBER
Seq. Order: | 15 |
---|---|
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 iss |
General Data Type: | VARCHAR2 |
PURCHASE_FISH
Seq. Order: | 16 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This is a yes/no field. If the dealer did not purchase any highly migratory species during the 2 week period, the 'no' is checked. |
General Data Type: | VARCHAR2 |
FISH_IMPORTED
Seq. Order: | 17 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Indicates whether or not the data reported included imports in addition to domestic purchases. |
General Data Type: | VARCHAR2 |
VESSEL_DATA
Seq. Order: | 18 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A vestigal column from old PC System which indicated whether or not there was vessel data on the logbook form. |
General Data Type: | VARCHAR2 |
EDIT_DATA
Seq. Order: | 19 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A vestigal column from old PC System which indicated whether or not data had to be corrected due to judgment of data manager. |
General Data Type: | VARCHAR2 |
WEIGH_OUT
Seq. Order: | 20 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
his indicates whether or not tally sheets (weigh out data) were provided with the HMS form. This aids in locating weigh out sheets upon request. |
General Data Type: | VARCHAR2 |
TIF_NUMBER
Seq. Order: | 21 |
---|---|
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 |
ID_NUMBER
Seq. Order: | 22 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 10 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Assigned By Vendor Software During Data Entry |
General Data Type: | VARCHAR2 |
RECEIVED_DATE
Seq. Order: | 23 |
---|---|
Data Storage Type: | DATE |
Max Length: | 7 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Date Logbook Form was received. |
General Data Type: | DATE |
POSTMARK_DATE
Seq. Order: | 24 |
---|---|
Data Storage Type: | DATE |
Max Length: | 7 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Date in which envelope containing the logbook form was post marked. |
General Data Type: | DATE |
Catalog Details
Catalog Item ID: | 5405 |
---|---|
GUID: | gov.noaa.nmfs.inport:5405 |
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:11+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 |