Table: FLS_INT_SCANNED_HEADERS

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 link to the other tables in the system are not broken.It is at this point when the logbook enters the Fisheries Logbook System and it is assigned a LOGBOOK_KEY that will uniquely identify it withing the application.Validation:Managed by the database. Each row in the table must have a unique value.

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 link to the other tables in the system are not broken.It is at this point when the logbook enters the Fisheries Logbook System and it is assigned a LOGBOOK_KEY that will uniquely identify it withing the application.Validation:Managed by the database. Each row in the table must have a unique value.

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

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.

When the completed logbooks sent back by the permit holders are collected at the post office, they are stamped with unique numbers by SFD staff. These numbers are called schedule number.When the data are loaded, the program asks for a range of schedule numbers for the batch. Validation: - This field must be within a range of schedule numbers provided. - Schedule Numbers must be consecutive ( there are no gaps ). - Schedule Numbers can not be duplicated.This field is mandatory, that is, it cannot be left empty.

The ID of the vessel for which the logbook has been completed. Validation:The vessel ID is programmatically checked againt the the FLS_VESSEL_LIST table, which is a list of unique valid vessel id numbers summarized from the permit file compiled by SERO.This field is mandatory, that is, it cannot be left empty.

Name of the vessel that performed the fishing activity and for which the logbook was sent.Validation:The vessel name is used to assist in locating the correct vessel id when it is invalid or missing. Even though the spelling of the vessel id may change, it can be used to give the data manager a list of vessels from which to choose.(Note: The vessel name should be checked against FLS_VESSEL_LIST to make sure it matches the name provided for the ID)

Phone Number to Call Vessel

Unload or landing date reported on the logbook report.Validation:The data must be a valid date.

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

Date when the vessel set sail to begin the trip. It is also referred to as Departure Date.Validation:The date must be valid. For the Gulf Reef and Snapper/Grouper logbooks, the column became required starting in 1999, so it cannot be null. There must be a consistent relationship betwee departure date, landing date and days away.If start (i.e., departure) date is not null, landing date must be greater than or equal to departure date.The format of the date is YYYYMMDD, which is the standard format of all character fields that contain dates (this is done to simplify sorting by 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.The format of the date is YYYYMMDD, which is the standard format of all character fields that contain dates (this is done to simplify sorting by date.)

Date Form Was Recieved By NMFS

Number of days from, departure to landing, the vessel was away from port that are reported on the form.Validation: The information must be numeric and up to three digits long.

Crew size reported on the form.Validation:The information must be numeric and up to 2 digits long.

Unique identifier for each dealer. On the form, the dealer name is used. The scanning process takes the name and converts it to a code using a list provided by RMD.

A dealer code in the old coding dealer coding system. This is used for reference by FSB personnel.

Dealer name

County of landing reported on the form.Validation:This field must contain a valid code which is checked against the FLS_COUNTY_CODES_NMFS table.

The County Name Associated With The County Landed (Code)

State of landing reported on the form.Validation:This field must contain a valid code which is checked against the FLS_STATE_CODES_NMFS table.

The State Name Associated With The State Landed (Code)

Filler

First Area Fished reported on the logbook report. Historically, up to three areas could be specified on the form. Currently, the form allows for as many areas as catches reported. This field is usually blank in current data.Validation:The information must be numeric and up to four digits long.

Second Area Fished reported on the logbook report. Historically, up to three areas could be specified on the form. Currently, the form allows for as many areas as catches reported. This field is usually blank in current data.Validation:The information must be numeric and up to four digits long.

Third Area Fished reported on the logbook report. Historically, up to three areas could be specified on the form. Currently, the form allows for as many areas as catches reported. This field is usually blank in current data.Validation:The information must be numeric and up to four digits long.

Indicates whether traps were used.Validation: If this column is marked, a corresponding configuration gear must be indicated. Also the DLS_INT_SCANNED_CATCHES is checked to ensure that at least one record with gear type 'T' is reported . Since the column is optional, null is also a valid value

Number of traps fished.

Number of traps hauled reported on the form.Validation:If this field is entered, the corresponding gear column ( WERE_TRAPS_USED) must have data.The information must be numeric and up to four digits long.

Time the trap was in the water.Validation:If this field is entered, the corresponding gear column ( WERE_TRAPS_USED) must have data.The information must be numeric and up to six digits long.

First mesh measurement reported on the logbook.Validation: If this field is entered, the corresponding gear column ( WERE_TRAPS_USED) must have data.The information must be numeric and up to four digits long.

Second mesh measurement reported on the logbook.Validation: If this field is entered, the corresponding gear column ( WERE_TRAPS_USED) must have data.The information must be numeric and up to four digits long.

Third mesh measurement reported on the logbook.Validation: If this field is entered, the corresponding gear column ( WERE_TRAPS_USED) must have data.The information must be numeric and up to four digits long.

Fourth mesh measurement reported on the logbook.Validation: If this field is entered, the corresponding gear column ( WERE_TRAPS_USED) must have data.The information must be numeric and up to four digits long.

Indicates if fisher reported the use of longlines.Validation:If this column is marked, a corresponding configuration gear must be indicated. Also, the table FLS_INT_SCANNED_CATCHES is checked to ensure that at least one record with gear type 'L' is reported . Since the column is optional, null is also a valid value.

Number of longline sets reported.Validation: If this field is entered, the corresponding gear column ( WERE_LONGLINES_USED) must have data. The information must be numeric and up to four digits long.

Number of hooks per line reported.Validation: If this field is entered, the corresponding gear column ( WERE_LONGLINES_USED) must have data. The information must be numeric and up to four digits long.

Length of the longline reported by the fisher.Validation: If this field is entered, the corresponding gear column ( WERE_LONGLINES_USED) must have data. The information must be numeric and up to six digits long.

Time longlines were fished.Validation: If this field is entered, the corresponding gear column ( WERE_LONGLINES_USED) must have data. The information must be numeric and up to five digits long.

Indicates whether buoys were used.Fishers were required to report buoys catches on logbook forms between 1992 and 1994. In historical data, this gear is identified with a 'B.' Although this information no longer appears on the logbooks, it has been kept to load and review historical data.

Indicates how many buoys were used.Fishers were required to report buoys catches on logbook forms between 1992 and 1994. In historical data, this gear is identified with a 'B.' Although this information no longer appears on the logbooks, the column has been kept to load and review historical data.

How many hooks were attached to each buoy line.Fishers were required to report buoys catches on logbook forms between 1992 and 1994. In historical data, this gear is identified with a 'B.' Although this information no longer appears on the logbooks, the column has been kept to load and review historical data.

Time the buoy was fished.Fishers were required to report buoys catches on logbook forms between 1992 and 1994. In historical data, this gear is identified with a 'B.' Although this information no longer appears on the logbooks, the column has been kept to load and review historical data.

Indicates whether the fisher reported using gillnets.Validation:If this column is marked, a corresponding gear configuration must be indicated. Also the FLS_INT_SCANNED_CATCHES is checked to ensure that at least one record with gear type 'G' is reported .Since the column is optional, null is also a valid value

Length of the gillnet.Validation:If this field is entered, the corresponding gear column ( WERE_GILLNETS_USED) must have data.The information must be numeric and up to four digits long.

Depth of the gillnet.Validation:If this field is entered, the corresponding gear column ( WERE_GILLNETS_USED) must have data.The information must be numeric and up to four digits long.

Meshsize of the gillnet.Validation:If this field is entered, the corresponding gear column ( WERE_GILLNETS_USED) must have data.The information must be numeric and up to five digits long.

Time gillnet was in the water.Validation:If this field is entered, the corresponding gear column ( WERE_GILLNETS_USED) must have data.The information must be numeric and up to five digits long.

Indicates whether the fisher reported the use of handlines.Validation: If this column is marked, a corresponding gear configuration must be indicated. Also the table FLS_INT_SCANNED_CATCHES is checked to ensure that at least one record with gear type 'H' is reported . Since the column is optional, null is also a valid value

Number of handlines used.Validation:If this field is entered, the corresponding gear column ( WERE_HANDLINES_USED) must have data.The information must be numeric and up to four digits long.

Number of hooks per handlines used.Validation:If this field is entered, the corresponding gear column ( WERE_HANDLINES_USED) must have data.The information must be numeric and up to four digits long.

Hours the handline was fished.Validation:If this field is entered, the corresponding gear column ( WERE_HANDLINES_USED) must have data.The information must be numeric and up to four digits long.

Indicates whether the fisher reported trolling.Validation: If this column is marked, a corresponding gear configuration must be indicated. Also the table FLS_INT_SCANNED_CATCHES is checked to ensure that at least one record with gear type 'TR' is reported . Since the column is optional, null is also a valid value

Indicates whether the fisher reported trolling.Validation: If this column is marked, a corresponding gear configuration must be indicated. Also the table FLS_INT_SCANNED_CATCHES is checked to ensure that at least one record with gear type 'TR' is reported . Since the column is optional, null is also a valid value

Number of hooks per troll lines used.Validation:If this field is entered, the corresponding gear column ( WAS_BOAT_TROLLING) must have data.The information must be numeric and up to four digits long.

Total time spent trolling.Validation:If this field is entered, the corresponding gear column ( WAS_BOAT_TROLLING) must have data.The information must be numeric and up to five digits long

Indicates whether divers used spears.Validation:If this column is marked, a corresponding gear configuration must be indicated. Also the table FLS_INT_SCANNED_CATCHES is checked to ensure that at least one record with gear type 'S' is reported .Since the column is optional, null is also a valid value

Number of divers involved in the catch who used spears.Validation:If this field is entered, the corresponding gear column ( DIVERS_USED_SPEARS ) must have data.

How much time was spent diving using spears.Validation: If this field is entered, the corresponding gear columns ( DIVERS_USED_SPEARS ) must have data.

Indicates whether the divers used powerheads.Validation: If this column is marked, a corresponding gear configuration must be indicated. Also the table FLS_INT_SCANNED_CATCHES is checked to ensure that at least one record with gear type 'P' is reported .Since the column is optional, null is also a valid value

Number of divers involved in the catch who used powerheads.Validation:If this field is entered, the corresponding gear column ( DIVERS_USED_POWERHEADS ) must have data.

How much time was spent diving using powerheads.Validation: If this field is entered, the corresponding gear columns ( DIVERS_USED_POWERHEADS ) must have data.

Any other gear used. Regardless of the gear entered by the fisher on the form, this is always coded as 'Other.'Validation:If this column is marked, a corresponding gear configuration must be indicated. Also, the table FLS_INT_SCANNED_CATCHES is checked to ensure that at least one record with gear type 'O' is reported .Since the column is optional, null is also a valid value

Indicates if cast nets were used.Validation:If this column is marked, a corresponding gear configuration column must be indicated. Also, the table FLS_INT_SCANNED_CATCHES is checked to ensure that at least one record with gear type 'CN' is reported .Since the column is optional, null is also a valid value

This is a place holder in the record structure where gillnets used to be stored.Validation:If this field is entered, the corresponding gear columns (OTHER_GEAR_USED or WERE_CAST_NETS_USED ) must have data.(Note: I don't think so...)

Type of other gear used.Validation: If this field is entered, the corresponding gear columns (OTHER_GEAR_USED or WERE_CAST_NETS_USED ) must have data.

Time spent fishing with the other gear.Validation: If this field is entered, the corresponding gear columns (OTHER_GEAR_USED or WERE_CAST_NETS_USED ) must have data.The information must be numeric and up to five digits long.

Was there an edit to the associated vessel record

Vessel integrated

Was there an edit to the associated Gear Record

Gear integrated

Target

Target Fishery

Is This a no fishing record

Indicates whether there were any rows with errors in this table. When data are validated, if the validation program detects any errors in the current row of the table, this flag is set to show that the row must be corrected. When the data are corrected using the Editing programs, the flag is reset to show that the record has now passed validation and can be distributed to the master tables. Before the data are distributed, the distribution program checks to make sure that all data have been corrected. If not, the manager is notified and must make the necessary corrections.Validation:The domain ERRORS_IN_THIS_TABLE ensures that only predefined values are accepted into the system.(Note: This column should not be optional)

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 be easily identified.

Has form been returned to fisher due to missing/inconsistant information

Trip Ticket Number

Were Electricreels Used?

Number Of Electriclines

Number Of Hooks Per Electriclines

Electricline Time Fished

Control Column to indicate version of form used for data entry

Data Entry Operator Name (Control column)

Data Entry Operator Number (Control Column)

Were Fish Traps Used

Were Other Traps Used

Total trap soaktime

Were bottom longlines used

Were pelagic Longlines Used

Were Other Longlines Used

Total Longline Time Fished

Were strike gillnets used

Were drift gillnets used

Were anchor gillnets used

Were other gillnets used

Number Of gillnet sets

Total Gillnet Soak Time

Other Target Fishery Description

Other Gear Descriptions