Page Comparison

...

1. Vessel
   The vessel element is the vessel ADF&G number.

   Data Type	Since Schema Version	Oracle Database Data Definition	Values
   integer	1.0	NUMBER(5,0)	Vessel is the ADF&G Number of the vessel. Vessel ADF&G numbers can be looked up on the CFEC website

   • The vessel element includes a name attribute, which contains the name of the vessel

     Data Type	Since Schema Version	Oracle Database Data Definition	Values
     text	1.0	VARCHAR2(50)	Vessel names can be looked up on the CFEC website, as above.

2. Crew_size
   The crew_size element is the number of crew onboard, including the skipper, but excluding any observers.

   Data Type	Since Schema Version	Oracle Database Data Definition	Values
   integer	1.0	NUMBER(3,0)	Crew size is the size of the crew including the skipper. Rules for crew size are documented by the eLandings business rules

3. Observers_onboard
   The observers_onboard element is the number of observers onboard the vessel for the trip.

   Data Type	Since Schema Version	Oracle Database Data Definition	Values
   integer	1.0	NUMBER(2,0)	Observers onboard is the number of observers. Rules for observers onboard are documented by the eLandings business rules

4. Port_of_landing
   The port_of_landing element is the ADF&G port code, as entered on fish tickets.

   Data Type	Since Schema Version	Oracle Database Data Definition	Values
   text	1.0	CHAR(3)	Port of landing is the eLandings port code. Valid values can be looked up on the eLandings website

   The port_of_landing element includes two attributes.
   • the name attribute contains the text name of the port or at-sea operation type

     Data Type	Since Schema Version	Oracle Database Data Definition	Values
     text	1.0	VARCHAR2(50)

     the ifq_port_code contains the

     Port of landing name is the city or location associated with the port code. Values can be looked up on the eLandings website, as above.

   • the ifq_port_code contains the numeric IFQ system port code, as used on IFQ reports. The IFQ port code appears even on reports that do not include IFQ. It is merely an attribute of the alphabetic port code and its presence does not imply IFQ reporting.
5. Delivery_port_region
   The port and region for IFQ crab deliveries.
6. Gear
   The gear element is the ADF&G gear code, as entered on fish tickets.
   • then gear element includes a name attribute, which contains the name of the gear type.
7. Proc_code_owner
   The proc_code_owner element identifies the entity that purchases or otherwise controls the fish, and is equivalent to the proc code embossed on paper fish tickets.
   • Proc_code
     The proc_code element is the ADF&G intent to operate processor code, also known as the F-code. The

     Data Type	Since Schema Version	Oracle Database Data Definition	Values
     integer	1.0	NUMBER(3,0)	IFQ port code is the numeric code used on the IFQ system. It is associated with the eLandings port code, and can be looked up on the eLandings website. The IFQ port code appears on IFQ receipts.

8. Delivery_port_region
   The port and region for IFQ crab deliveries.

   Data Type	Since Schema Version	Oracle Database Data Definition	Values
   text	1.6	VARCHAR2(3)	The Delivery Port Region is the IFQ system port or region code used on some IFQ landings. Valid values can be looked up on the eLandings website

9. Gear
   The gear element is the ADF&G gear code, as entered on fish tickets.

   Data Type	Since Schema Version	Oracle Database Data Definition	Values
   integer	1.0	NUMBER(3,0)	Gear is the eLandings gear code. Valid values can be looked up on the eLandings website

   • then gear element includes a name attribute, which contains the name of the gear type.

     Data Type	Since Schema Version	Oracle Database Data Definition	Values
     text	1.0	VARCHAR2(25)	Gear name is the description of the gear associated with the gear code. Values can be looked up on the eLandings website, as above.

10. Proc_code_owner
    The proc_code_owner element identifies the entity that purchases or otherwise controls the fish, and is equivalent to the proc code embossed on paper fish tickets.
    • Proc_code
      The proc_code element is the ADF&G intent to operate processor code, also known as the F-code.

      Data Type	Since Schema Version	Oracle Database Data Definition	Values
      text	1.0	VARCHAR2(6)	Proc code owner is the processor code of the processor who is buying the catch.

      • The proc_code element includes a processor attribute, which contains the name of the processor, as listed on their intent to operate application.

        Data Type	Since Schema Version	Oracle Database Data Definition	Values
        text	1.0	VARCHAR2(50)	Proc code owner processor is the name of the processor who is buying the catch.

11. Proc_code_processor
    The proc_code_processor element identifies the custom processor, if there was one. This element is present only if custom processing took place.
    • Proc_code
      The proc_code element is the ADF&G intent to operate processor code, also known as the F-code.

      Data Type	Since Schema Version	Oracle Database Data Definition	Values
      text	1.0	VARCHAR2(6)	Proc code processor is the processor code of the processor who is receiving and the catch, in cases of custom processing.

      • The proc_code element includes a processor attribute, which contains the name of the processor, as listed on their intent to operate application.
12. Proc_code_processor
    The proc_code_processor element identifies the custom processor, if there was one. This element is present only if custom processing took place.
    • Proc_code
      The proc_code element is the ADF&G intent to operate processor code, also known as the F-code.
      • The proc_code element includes a processor attribute, which contains the name of the processor, as listed on their intent to operate application.
13. Date_fishing_began
    The date_fishing_began element is the date the gear went in the water.
14. Days_fished
    The days_fished element is the number of days the vessel was actually fishing. This element may not be present.
    • • operate application.

        Data Type	Since Schema Version	Oracle Database Data Definition	Values
        text	1.0	VARCHAR2(50)	Proc code processor processor is the name of the processor who is receiving and the catch, in cases of custom processing.

15. Date_fishing_began
    The date_fishing_began element is the date the gear went in the water.

    Data Type	Since Schema Version	Oracle Database Data Definition	Values
    date	1.0	DATE	Date fishing began is the date that the gear first went in the water.

16. Days_fished
    The days_fished element is the number of days the vessel was actually fishing. This element may not be present.

    Data Type	Since Schema Version	Oracle Database Data Definition	Values
    integer	1.0	NUMBER(3,0)	Days fished is the number of days between the date fishing began and the date of landing when gear was in the water and fishing was taking place. The business rules for days fished are on the eLandings website

17. Date_of_landing
    The date_of_landing element is the date the offload completed. The date_of_landing actually a date and time. Time of landing is only used in salmon fisheries, but the element's definition requires the time component always be present. For non-salmon landings, or salmon landings where time of landing is not captured, the time component will be set to the eLandings default value, 12:00:01. When provided time for salmon landing reports, the resolution of time is in minutes. The seconds portion of time will always be 00. The 01 seconds of the default value is the indication that time should be ignored.

    Data Type	Since Schema Version	Oracle Database Data Definition	Values
    dateTime	1.0	DATE	Date of landing is the date upon which the offload from the catcher vessel was completed.

18. Partial_delivery
    The partial_delivery element is a flag indicating whether the landing report was for a partial delivery or not.
19. Last_delivery_for_trip
    The last_delivery_for_trip element is a flag indicating that the landing is the last for the trip.
20. Multiple_ifq_permits
    The multiple_ifq_permits element provides historic compatibility with fish tickets.
21. Manual_ifq_report
    The manual_ifq_report element indicates that the IFQ reporting for this landing was done by contacting the NMFS Enforcement data clerks by telephone and making the IFQ reports manually to them. If the manual_ifq_report element is set to true then no IFQ reports will be included in the landing report XML file.
22. Nearest_bay_or_headland
    The nearest_bay_or_headland element contains a text description of the area fished. It is not used for IFQ crab or groundfish, but is used for salmon.
23. Federal_processor_number
    The federal_processor_number is the federal_processor_permit number for the processor who submitted the report. It is typically omitted from salmon reports. The federal_processor_number element includes three attributes:
    • name - the name of the processing company, plant, or at-sea processing vessel
    • at_sea_proc - a boolean flag indicating the permit is a federal fisheries permit for an at-sea processor. This attribute is omitted from landing reports exported from eLandings.
    • license_year - the most recent year for which the processor was licensed. This attribute is omitted from landing reports exported from eLandings.
24. Registered_buyer_number
    The registered_buyer_number the buyer identification for IFQ halibut and sablefish. It is typically omitted from salmon reports. This element includes two attributes.
    • name - the name of the processing company, plant, or at-sea processing vessel
    • license_year - the most recent year for which the buyer was licensed. This attribute is omitted from landing reports exported from eLandings.
25. Registered_crab_receiver_number
    The registered_crab_receiver_number identifies the receiver for IFQ crab. It is the RCR number issued by NMFS. This element will be omitted for groundfish and salmon landings. This element includes two attributes.
    • name - the name of the processing company, plant, or at-sea processing vessel
    • license_year - the most recent year for which the buyer was licensed. This attribute is omitted from landing reports exported from eLandings.
26. Discard_report
    The discard_report element indicated that the processor either did or did not receive the discard report blue sheets from the fisherman. It is required for groundfish, but will be omitted for salmon and crab reports. The values for discard_report are:

    Value	Description
    RC	Received
    NC	Not received
    NP	Not required, vessel not federally permitted
    NL	Not required, vessel less than 60 feet

    The discard_report element includes a desc attribute, with the text value of the discard report code.
27. Tender_vessel
    The tender_vessel element contains the ADF&G number of the tender that took the delivery that generated the landing report. It is omitted for non-tender deliveries.
    • The tender_vessel element includes a name attribute, which contains the name of the vessel.
28. chill_type
    The chill_type element is used to indicate the refrigeration method used aboard the catcher vessel for salmon reports. It is omitted for non-salmon landings. The values for chill_type are:

    Value	Description
    CSW	Circulating seawater
    FAS	Frozen at sea
    ICE	Ice
    LIV	Fish were delivered or pumped live
    RSW	Refrigerated seawater
    SLH	Slush ice

    The chill_type element includes a desc attribute, with the text value of the chill type code.
29. Rsw_temp
    The rsw_temp element is used to record the temperature of the fish or the chill system aboard the catcher vessel. The term rsw temp is a misnomer, the actual chill type is specified in the chill_type element and does not have to be RSW. The rsw_temp element can repeat up to 3 times, to allow for storage of sample data on unsubmitted reports. However, when the landing report is submitted the temperatures are averaged, and only one temperature is stored and returned on landing reports exported from eLandings. Rsw_temp is omitted if the report does not include chill_type.
30. Dock_delivery
    The dock_delivery element is a boolean flag that indicates if a tender delivery took place at a tender tied up at the processing plant dock. It is omitted for landings that are not dock deliveries.
31. Buying_station_name
    The buying_station_name element contains the operation name if the operation that submitted the report is a buying station operation, and can be so identified from the permit numbers and processor codes on the landing report. In some cases the operation cannot be determined, so this element may not be present even if the originating operation was a buying station. If the originating operation was not a buying station this element will be omitted.
32. Agency_header_data
    The agency_header_data element is used internally by the eLandings system. It will not be seen in export files.
33. Permit_worksheet
    At least one permit_worksheet element will be present in landing report files exported from eLandings. Each permit worksheet element allows a CFEC permit to be specified, so multiple worksheet items indicate permit stacking.
    1. Item_number
       The item_number element is just the sequential permit item number for the report. However, item numbers may have a break in their sequence if a report is submitted, and then a permit item is deleted.
    2. Cfec_permit
       The cfec_permit element is the entire CFEC permit information needed to identify the permit.
       • Fishery
         The fishery element is the fishery code on the CFEC permit card.
       • Permit_number
         The permit_number element is is the unique permit number on the CFEC card. It is a five digit number followed by one alphabetic check character.
       • Year_seq
         The year_seq element is is the year and card sequence from the CFEC card. It is a two digit year, a two digit sequence number, and one alphabetic check character.
    3. Mag_stripe_read
       The mag_stripe_read element identifies identifies whether the CFEC permit date was read into the eLandings system by swiping the magnetic stripe on the CFEC permit card.
    4. Management_program
       The management_program element identifies the management program under which the fishing took place.
       • Program
         The program element is the management program abbreviation such as IFQ, CDQ, AFA, or OA.
       • Program_id
         The program_id element is participant identifier. It will be present if the management program has participant IDs. CDQ numbers for CDQ and Co-op numbers for AFA, are examples of program ids. If the management program has no participant numbers, such as ADAK, then this element will be omited.
    5. Percent
       The percent element is is used by the eLandings system when allocating line items to stacked permits. The percents on the permit worksheet elements will add up to 100. Percent may be specified as zero.
    6. Fish_ticket_number
       The fish_ticket_number element contains the fish ticket number for the permit.
    7. Fish_ticket_sequence
       The fish_ticket_sequence element is the internal agency batch sequence for the fish ticket. It will be omitted for XML files seen by processors and third party systems.
    8. Batch Year
       The batch_year element is the internal agency batch year for the fish ticket. It will be omitted for XML files seen by processors and third party systems.
    9. Batch Office Code
       The batch_office code element is the internal agency office code of the office that data enters the the fish ticket receipt data. It will be omitted for XML files seen by processors and third party systems.
    10. Batch_number
        The batch_number element is the internal agency batch identifier for the fish ticket. It will be omitted for XML files seen by processors and third party systems.
    11. Ifq_permit_worksheet
        The ifq_permit_worksheet element is used for IFQ permit information. Multiple ifq_permit_worksheet elements may be provided for each CFEC permit, allowing multiple IFQ permits to be stacked on each CFEC permit.
        1. Item_number
           The item_number element is just the sequential item number for the ifq permit. However, item numbers may have a break in their sequence if a report is submitted, and then an ifq permit item is deleted.
        2. Ifq_permit_number
           The ifq_permit_number element is the IFQ system permit identfier.
        3. Nmfs_person_id
           The nmfs_person_id element is the unique ID issued by NMFS to each person authorized to fish for IFQ species, whether a permit holder or a hired skipper. The nmfs_person_id will be the same for all ifq_permit_worksheet elements associated with a single CFEC permit.
        4. Species
           The species element is the ADF&G species code associated with the permit.
        5. Fishery_area
           The fishery_area element is used by the eLandings system when allocating line items to permits. The fishery area elements specifies the area or fishery where the permit has quota, and is used to allocate itemized catch from that area or fishery to the permit. This element is typically used in conjunction with the pounds element to "max out" a permit.
        6. Pounds
           The pounds element is used by the eLandings system when allocating line items to permits. The pounds element specifies an amount of IFQ quota pounds to allocate to that permit. This is typically used to "max out" a permit that is close to the end of its quota.
        7. Ipq_permit_number
           The ipq_permit_number is conditionally required for crab landings. It will not be present for groundfish landings. If the IFQ permit is a class A permit, then an IPQ number will be present. The IPQ permit will be associated with the RCR number specified in the header.
34. Stat_area_worksheet
    The stat_area_worksheet element is not always present. If it is not provided then each line item will have a stat_area specified.
    More that one stat_area_worksheet elements may be specified.
    1. Item_number
       he item_number element is just the sequential item number for the stat area worksheet item. However, item numbers may have a break in their sequence if a report is submitted, and then a stat area worksheet item is deleted.
    2. Stat_area
       The stat_area element always present This is the ADF&G statistical area. For groundfish and crab it will be the 6 digit groundfish statistical area. For salmon it will be the 5 digit salmon statistical area.
    3. Percent
       The percent element will always be present. The total of percents for all stat_area_worksheet elements will equal 100.
    4. Effort
       The effort element will be present for IFQ crab. It is the number of pot lifts in the associated statistical area. For groundfish, this element is omitted.
    5. Count
       The count element is not used on landing reports, and will always be omitted.
35. Dual_permit
    The dual_permit element is a boolean flag that when true indicates that two or more CFEC permit holders were present on the vessel when the fishing occurred. This flag is typically used for Salmon. This flag may not be applicable in all fisheries and is subject to regulation. The presence of multiple permits on the fish ticket increases fishing limits. When dual permit is used, only one CFEC permit is recorded on the fish ticket.
36. Tender_trip_number
    The tender trip number is an optional element. This element was added for use in the Tender Trip Management page in the eLandings web site. The Tender Trip Management page was created to allow processors to manage salmon landings delivered by tender and summaries these landings within an Excel workbook. Processors can use the Tender Trip Management web page to assign a tender trip number to a list of landing reports. The Tender Trip Management page allows processors to export all the landings of a given tender trip number to a worksheet in an Excel workbook. In this way many trips can be appended to a workbook as individual worksheets. The tender trip number and the Tender Trip Management web page together serve as a stopgap measure for processors who managing their fish tickets in excel workbooks, or are moving from Excel to a more full featured third-party management toolset.
37. Total_tare
    The fishing period element is an optional field. This element is used in Bristol Bay Salmon fisheries with mixed salmon landings. Due to the rapid execution of these fisheries, in some cases Bristol Bay area managers allow processors to report initial fish tickets containing unsorted or mixed salmon. As a result these tickets have a single line item and single grading and pricing item of mixed salmon.
    Tare weight is the weight of the container holding the item during the weighing process. In weighing fish, we would subtract the tare weight from the total weight to get the actual weight of the fish.
    It is not uncommon for vessels in Bristol Bay to use a standard bags, brailer, or tote to while weighing the fish.  As a result the tare weight of the bag, brailer or tote can easily be calculated ahead of time and reused for all fish weightings.
     Some tenders find it faster to weight all of the fish to get a total weight including tare. The tenders count the number of uniform totes and multiply this by the know weight of a these standard totes to get the total tare. The tender can then subtract the ¿total tare¿ from the ¿total weight including tare¿ to arrive at the ¿total weight of the fish¿.
    The total_tare field in the landing report xml is used as a place holder value in the tLandings system. Upon submission to the eLandings database, tLandings Processor Tender Interface (PTI) runs the calculation to calculate the ¿total weight of the fish¿ on the ticket and discards the ¿total_tare¿ value. Once the total_tare has been applied it is not reversible to its original state. Total_tare is not stored in the eLandings database.
38. Fishing_period
    The fishing period element is an optional field. This element is primarily used in Salmon fisheries.
    A fishing period is a two digit number used by some ADFG fisheries area managers to identify a commercial fishery opener. Harvest may or may not have occurred during the opener, dependent upon weather and processor/buyer availability.
    In some fisheries, such as herring, there may be multiple periods within a day.  Periods are sequential and increase incrementally through the last opening of the season, but harvest records may not be associated with some openers.  The first annual opening of the season begins with # 01.
39. Out_of_state
    The out of state element is a Boolean flag used for internal use only. It is provided to the International Pacific Halibut Commission (IPHC) at their request. The IPHC uses this field to indicate that the IPCH data entered the landing report data in outside the state of Alaska. All other users should ignore this field.
40. Tender_batch
    The tender batch element is optional and can hold a six character alpha-numeric value. This element is primarily used in Salmon fisheries. Processors using the tLandings Processor Tender Interface (PTI) and insert (or submit) a list or batch of salmon fish tickets, delivered by a tender, to the eLandings database. At the time of insertion (or submission), the processor user can create an arbitrary name to be associated with all of the landing reports included in this insertion. Later, the user can query the eLandings database for tickets based on the user defined tender batch number to make further mass edits. Specifically, processors use this field to prepare a list of tickets to apply mixed salmon updates to.
41. Tally_invoice
    The tally invoice element is optional and can hold a six character alpha-numeric value. This element is primarily used in Salmon fisheries. Processors may request that tenders data enter the pre-printed tally invoice number assigned to tally sheets and dock slips which was used by the tender to record the landing weights. This element was provided at the request of processors to help processors audit landings by connecting the paper tally sheet on deck or at the dock to an electronic ticket.
42. Floating
    The floating element is an optional Boolean flag that when true indicates that fish were floating freely in the haul. Fish can be crushed, bruised or improperly refrigerated when they are packed so tightly into the hold that they cannot float freely. This element was provided at the request of processors to help them track fish quality.This element is primarily used in Salmon fisheries.
43. Slide
    The slide element is an optional Boolean flag that when true indicates that a fish slide was used to load fish into the hold. A fish slide is used to protect fish meat from bruising. This element was provided at the request of processors to help them track fish quality. This element is primarily used in Salmon fisheries.

...