Table of Contents
Auto Batching Procedures
The Auto Batching tool in the Agency Workstation allows ADF&G staff to assign batching information to fish tickets efficiently within the eLandings System. You can create a batch of up to 200 fish tickets for processing within this Agency Workstation feature. We suggest a limit of 200 paper fish tickets to a batch, as that is approximately how many paper fish ticket forms can be inserted into a standard manila envelope.
All fish ticket reports submitted to the ADF&G should be reviewed for completeness and accuracy, prior to the batching process. If an eTicket is submitted with incorrect information (incorrect statistical area(s), incorrect number of fish/average weights), contact the processor and request that they correct the fish ticket within eLandings. Provide them with the landing report or E-ticket number for reference. They can access the ticket(s) within the eLandings system and correct the data. Once corrected, the processor or you can reprint the fish ticket and staple the corrected copy to the copy of the fish ticket with the signatures.
The primary purpose of auto batching tickets is to create a retrievable archive. Once processed, fish ticket records are not frequently accessed. Auto batching provides a balance between rapid and efficient data processing and source document retrieval. The batching process also validates that fish tickets have been reviewed by staff for completeness and accuracy. Once batched, tickets are then copied to the fish ticket database.
Just as a reminder, Alaska Wildlife Troopers and even ADF&G staff seldom need to access the original signed copy of the fish ticket. An electronic copy of the fish ticket is easily available within the Agency Interface application for re-printing, in the original and edited version.
Original ticket without signature
Edited ticket without signature
Unless specifically requested by Alaska Wildlife Troopers or receipt of a court order for the original copy with signature, a copy of the landing printed from the Agency Interface will suffice, in most cases.
| Note |
|---|
If you auto batch daily and keep batches small, retrieval of the source document ticket is relatively easy. Using this procedure eliminates stamping each ticket with a sequence ticket number. |
Pre-Batching paper fish ticket processing procedures
Sort conventional ADF&G fish ticket reports from the electronically generated eTicket reports, as each ticket type needs to be processed separately.
Conventional fish ticket reports are data entered into Zephyr. eTickets are processed within the eLandings Agency Desktop application. Batched eTickets are pulled into the Zephyr system every 15 minutes.
Only eTickets can be auto batched.
We suggest you sort the eTickets by period, locale code or harvest (if you plan to modify the default code 11), if you plan to assign any of these values. You will expedite auto-batching if the pre-printed ticket numbers are in numeric sequence. eTickets from a specific processor’s tender and from a unique opener are most likely to be in sequential order. It is not required that you sort tickets, unless requested by the local area management biologist. Some local management biologists want tickets to be sorted by processor and by vessel name. If not required by your supervisor, sorting by processor, tender vessel and pre-printed fish ticket number is the most efficient procedure to expedite batching.
In all situations, count the number of eTickets for the batch. You do not need to stamp the tickets with a sequence fish ticket number, but some ADF&G staff find assigning a sequence ticket number helpful. If you do not stamp a sequence fish ticket number on each ticket, you will need to adjust your ticket stamper for subsequent sequence ticket numbers.
Within the fish ticket application, Zephyr, create a batch. You do not need to wait until all the conventional fish tickets have been processed to create a batch of eTickets. Conventional fish ticket batches and eTicket batches can be comingled in the Zephyr Batch & Ticket Log, but again, create separate batches for each category of tickets.
- Count the tickets and record the number of tickets for the batch, or
- Establish the ticket range within Zephyr.
- Record the batch and ticket sequence number on the exterior of the manila envelope.
Again, the individual fish eTicket reports do not need to be stamped with the sequence ticket number, but you may find this helpful.
Auto Batching
Login to the Agency Web application (if you need help with this please see the Agency Web Users Manual).
Select Auto Batching from the Reports drop down menu.
Batch Year will default to the current year and Harvest Code will be defaulted to 11, traditional state managed fishery, additionally the Start Fish Ticket # field will default based on the Batch Year displayed. Though defaulted, these fields can be modified to meet your coding requirements. As an example, if you have a ticket with a pre-printed fish ticket number for the previous year, simply change the default year. The harvest code default can be easily modified, as well.
To begin the auto-batching process, enter batching information:
- Office Code
- Batch Number and Sequence Ticket Range (as established from Zephyr)
- You can enter the Fishing Period, the Locale Code and modify the Harvest Code as necessary, for the entire batch, or within the batch for a sub-set of tickets, but they are not required data fields.
Auto Batching Procedures
The Auto Batching tool in the Agency Workstation allows ADF&G staff to assign batching information to fish tickets efficiently within the eLandings System. You can create a batch of up to 200 fish tickets for processing within this Agency Workstation feature. We suggest a limit of 200 paper fish tickets to a batch, as that is approximately how many paper fish ticket forms can be inserted into a standard manila envelope.
All fish ticket reports submitted to the ADF&G should be reviewed for completeness and accuracy, prior to the batching process. If an eTicket is submitted with incorrect information (incorrect statistical area(s), incorrect number of fish/average weights), contact the processor and request that they correct the fish ticket within eLandings. Provide them with the landing report or E-ticket number for reference. They can access the ticket(s) within the eLandings system and correct the data. Once corrected, the processor or you can reprint the fish ticket and staple the corrected copy to the copy of the fish ticket with the signatures.
The primary purpose of auto batching tickets is to create a retrievable archive. Once processed, fish ticket records are not frequently accessed. Auto batching provides a balance between rapid and efficient data processing and source document retrieval. The batching process also validates that fish tickets have been reviewed by staff for completeness and accuracy. Once batched, tickets are then copied to the fish ticket database.
Just as a reminder, Alaska Wildlife Troopers and even ADF&G staff seldom need to access the original signed copy of the fish ticket. An electronic copy of the fish ticket is easily available within the Agency Interface application for re-printing, in the original and edited version.
Original ticket without signature
Edited ticket without signature
Unless specifically requested by Alaska Wildlife Troopers or receipt of a court order for the original copy with signature, a copy of the landing printed from the Agency Interface will suffice, in most cases.
| Note |
|---|
If you auto batch daily and keep batches small, retrieval of the source document ticket is relatively easy. Using this procedure eliminates stamping each ticket with a sequence ticket number. |
Pre-Batching paper fish ticket processing procedures
Sort conventional ADF&G fish ticket reports from the electronically generated eTicket reports, as each ticket type needs to be processed separately.
Conventional fish ticket reports are data entered into Zephyr. eTickets are processed within the eLandings Agency Desktop application. Batched eTickets are pulled into the Zephyr system every 15 minutes.
Only eTickets can be auto batched.
We suggest you sort the eTickets by period, locale code or harvest (if you plan to modify the default code 11), if you plan to assign any of these values. You will expedite auto-batching if the pre-printed ticket numbers are in numeric sequence. eTickets from a specific processor’s tender and from a unique opener are most likely to be in sequential order. It is not required that you sort tickets, unless requested by the local area management biologist. Some local management biologists want tickets to be sorted by processor and by vessel name. If not required by your supervisor, sorting by processor, tender vessel and pre-printed fish ticket number is the most efficient procedure to expedite batching.
In all situations, count the number of eTickets for the batch. You do not need to stamp the tickets with a sequence fish ticket number, but some ADF&G staff find assigning a sequence ticket number helpful. If you do not stamp a sequence fish ticket number on each ticket, you will need to adjust your ticket stamper for subsequent sequence ticket numbers.
Within the fish ticket application, Zephyr, create a batch. You do not need to wait until all the conventional fish tickets have been processed to create a batch of eTickets. Conventional fish ticket batches and eTicket batches can be comingled in the Zephyr Batch & Ticket Log, but again, create separate batches for each category of tickets.
- Count the tickets and record the number of tickets for the batch, or
- Establish the ticket range within Zephyr.
- Record the batch and ticket sequence number on the exterior of the manila envelope.
Again, the individual fish eTicket reports do not need to be stamped with the sequence ticket number, but you may find this helpful.
Auto Batching
Login to the Agency Web application (if you need help with this please see the Agency Web Users Manual).
Select Auto Batching from the Reports drop down menu.
Batch Year will default to the current year and Harvest Code will be defaulted to 11, traditional state managed fishery, additionally the Start Fish Ticket # field will default based on the Batch Year displayed. Though defaulted, these fields can be modified to meet your coding requirements. As an example, if you have a ticket with a pre-printed fish ticket number for the previous year, simply change the default year. The harvest code default can be easily modified, as well. The auto batching page asks for the batch year, office code and batch number. Optionally, you can enter the harvest code, fishing period and locale code here.
To begin the auto-batching process, enter batching information:
- Office Code
- Batch Number and Sequence Ticket Range (as established from Zephyr)
- You can enter the Fishing Period, the Locale Code and modify the Harvest Code as necessary, for the entire batch, or within the batch for a sub-set of tickets, but they are not required data fields.
...
Enter the following
Start Seq. Ticket Range: 1
End Seq Ticket Range: 6
We have 6 tickets that we would like to assign batch information too.
E18 046023
E18 046024
E18 997799
E18 997800
E18 007157
E18 045572
We can see that we have a run of four consecutive numbers E18 046023 to E18 046024 and E18 997799 to E18 997800.
We will enter those first.
Type 046023 into the Start Fish Ticket # field.
Press the Tab Key to move to the next field.
Type 046024 into the End Fish Ticket # field.
While the field focus is on the End Fish Ticket # field, press the Enter Key or "-" hyphen key. 
The enter key or hyphen key will add this range of tickets to the list to be batched.
Notice that each ticket is listed with the some batch information.
The tickets are not batched yet. This list shows what they system will try to do, when you click the blue "Batch" button later on.
You can remove items from the list that don't belong, or edit individual records if needed.
Type 997799 into the Start Fish Ticket # field.
Press the Tab Key to move to the next field.
Type 997800into the End Fish Ticket # field. 
The enter key or hyphen key will add this range of tickets to the list to be batched. 
We entered a seq ticket range of 1 to 6. We have assigned 1-4 of this range to these four landing reports.
Notice the "Next Seq. Ticket Number" field. It shows "5". 
This indicates that if you were to add another ticket to the list, it would be assigned seq ticket number 5.
We can now enter:
E18 007157
E18 045572
In the Start Fish Ticket # field type:
007157 
With the field focus on Start Fish Ticket # field, press the Enter key to add the fish ticket number to the list 
Now enter 045572 into the Start Fish Ticket # field
With the field focus on Start Fish Ticket # field, press the Enter key to add the fish ticket number to the list 
Notice that the Next Seq. Ticket Number is now blank. We have used all 6 sequence ticket numbers in the range. There are no more to use.
At this point we can review the list and make any corrections needed. We could edit individual tickets or delete them from the list.
There are two buttons at the bottom of the page: Batch and Validate
The Validate button allows you to ask the system to review your list and tell you if it sees any problems. The validate button does not make any edits to the landing reports.
The Batch button will try to assign the batch information to the individual tickets in the way you have listed here.
Click the Batch button.
If there were no errors, you will receive the message:
INFO 2290: 6 fish tickets batched 
For more information on this process see the documentation for the Agency Desktop. Most of the material is applicable:
https://elandings.atlassian.net/wiki/spaces/AgencyIf/pages/32866345/ADF+G+Batching+and+Data+Processing+Procedures+-Salmon?preview=/32866345/142216883/AUTO%20BATCHING%20IN%20THE%20AGENCY%20WORKSTATION.docx
We can go look at one of these fish tickets and look at the batching information that was just added.
We will look for:
E18 045572
Click on the Agency Button
In the Welcome page, enter E18 045572 into the Search by Fish Ticket field and click the search button. 
The system will go to the Landing Report Search Screen, enter the search criteria to find a landing report by this fish ticket number and run the search.
Click on the landing report id listed in the search results.
We can see the batch information has been applied to the ticket
...
NOTE: You may use the TAB key to navigate through each field. Once you enter a fish ticket number, press enter to populate the batching table. To enter a sequential range, enter the first number, tab, and then enter the second number, followed by selecting the enter key.
...