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.
...
| Page Properties | ||
|---|---|---|
| ||
This page is linked from the Agency Web app autoBatching.html → Help Menu → Online Help option. Please update the application link and the /wiki/spaces/et/pages/526450711 if you change the page location. |
Table of Contents
Introduction
In a given year ~204,000 salmon fish tickets are created. Each year more and more of those tickets originate in eLandings. ADFG staff had difficulty keeping up with salmon ticket batching due to the volume of tickets. In an effort to make this easier, the Auto Batching tool was created for Salmon tickets.
The Auto Batching tool in the Agency Workstation allows ADFG staff to assign batching information to fishtickets efficiently within the eLandings system. You can create a batch of up to 200 fish tickets for processing within this Agency Web 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 ADFG 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 ADFG 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 ADFG fishticket reports from the electronically generated eTicket reports, as each ticket type needs to be processed separately.
Conventional fishticket 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.
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, although this is not necessary for auto-batching to work. 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.
| Note | ||
|---|---|---|
| ||
Be aware that you may receive duplicate, unlabeled fish tickets without signatures. If this is occurring, please contact the local seafood processing facility and ask them to label the fish ticket copies and send only the signed Fish and Game copy to the local office. As a general practice, if you receive unsigned eTickets, set these tickets aside and determine if a signed copy is present. Also review the duplicate copies to determine if a correction or modification in the fish ticket has occurred. If so, then staple the modified ticket to the signed copy. If the unsigned duplicate copy is nothing more than a duplicate, then it can be discarded. |
Auto Batching Procedures
In order for a ticket to move from eLandings to the ADFG Fish Ticket Database (i.e. Zephyr), the ticket must have batch information assigned to it. The ticket will also need harvest code information assigned to it.
| Note |
|---|
Typically salmon tickets have one harvest code = “11 – State managed fishery” and this is the default setting. |
The Auto Batching tool allows you to enter a list of tickets and assign batching information to them all. The benefit is that you do not have to open each ticket individually when assigning the batching information.
- 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 default to 11 – 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.
| Note |
|---|
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. |
| Note |
|---|
The Fish Ticket Numbers will default with a prefix of EYY (where YY is the current year), allowing you to enter only the six digit fish ticket number. In this example, you would enter 181164 and then hit the enter key. The EYY on this ticket = E15 indicating a ticket from 2015.
|
In a few cases, a processor will fail to download the current year of tLandings and it generates fish tickets with the prior year date. The ticket(s) should be batched with the current year’s fishery. Just change the prefix on the ticket. Remember to change the prefix back to the current year when you have completed processing of the ticket(s). Again, enter the pre-printed fish ticket number, omitting the leading alpha letter (the E) and the year.
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.
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.
The Fish Ticket Numbers will default with a prefix of EYY (where YY is the current year), allowing you to enter only the six digit fish ticket number. In this example, you would enter 181164 and then hit the enter key. (See below for an example Fish Ticket Number)
In a few cases, a processor will fail to download the current year of tLandings and it generates fish tickets with the prior year date. The ticket(s) should be batched with the current year’s fishery. Just change the prefix on the ticket. Remember to change the prefix back to the current year when you have completed processing of the ticket(s). Again, enter the pre-printed fish ticket number, omitting the leading alpha letter (the E) and the year.
Entering non-sequential fish ticket numbers
Once you have entered the fish ticket number, click Enter to add the fish ticket number to the batch table.
Entering a second single fish ticket number:
Entering sequential fish ticket numbers
If you have a group of fish tickets with the pre-printed fish ticket in sequence, enter the first number in the range and then the last ticket number in the range. When you select the enter key, all the ticket numbers within this range are loaded in the Batching Table. The sequence can be in the forward or reverse order.
Ascending order tickets
Reverse order tickets
- data fields.
On the Auto Batching screen enter the following data:
- 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.
| Note | ||
|---|---|---|
| ||
Note that the upper limit of tickets the system will let you batch is 250. If you try to batch more than 250 tickets, you will get a hard error that will not let you proceed until you reduce the number of tickets to below 250. |
Add tickets in Sequence:
- 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 same batch information.
| Warning |
|---|
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. |
To add the next sequence:
- Type 997799 into the Start Fish Ticket # field.
- Press the Tab Key to move to the next field.
- Type 997799 into the End Fish Ticket # field.
- While the field focus is on the End Fish Ticket # field, press the Enter Key or "-" hyphen key.
| Tip |
|---|
The Auto Batching feature also allows you to apply batching information in the reverse order – in other words, in ascending or descending number sequences. In the example above, the |
...
Seq. |
...
Ticket Range is from |
...
Modifying the code assignments on fish tickets
You can easily modify the codes on individual fish tickets or a sequence of tickets within the batch. Simply change the default value assignment(s).
You can also add and modify the fishing period or locale code for all the tickets in a batch or a portion of the tickets in a batch.
Save, Load and Validate the tickets
Note the ‘Save Entry’ and ‘Load Entry’, which allows you to save your ticket batching work to your local machine. If you have poor bandwidth or expect interruptions during the auto-batching process, use these features to save your work.
Before I batch the tickets, I can select validate to determine if any of the fish ticket numbers I have entered will fail validation. I click validate and an error message appears. Ticket E 15 163989, item 15 does not match any record in the eLandings database.
I realize that I incorrectly keyed this number. The number was 163988.
I close the error message dialog box and double click on item 15. I can easily correct the record in the dialog box for this item.
You can continue to correct individual tickets in the batching table until all pass validation and are ready to batch.
Please validate the tickets you wish to batch prior to selecting Batch.
Batch Uploading (Batching)
I can upload the tickets in the batch table at any time; I do not need to complete the entire range of tickets within the batch. In the example above, I still have eight tickets numbers left in the batch.
The ‘Batch’ button assigns the fish ticket numbers currently listed in the Batch Table with the batching information and the values entered into the Harvest, Fishing Period and/or Locale Code. The batch year, office code, batch number, harvest code, fishing period, local code, and seq. ticket number range are assigned when this group of tickets is uploaded, and the upload process is initiated by selecting the batch button.
Again, the Auto Batching feature of the Agency Interface application does allow you to enter a range of tickets with a specific assignment of harvest, period or locale code, and within the same batch, assign a new value to any or all of these data fields. (Please remember that you do not need to assign a value period or locale code, but the harvest code always requires a numeric code value.)
When all tickets in the batch have been uploaded the Next Seq Ticket Number box will be empty, indicating that you have used all the sequence ticket numbers for that batch. The batch is complete.
Once the batch has been uploaded the assignments are visible in the Agency Interface for individual reports.
...
997799 to 997800, but it could have been done in the reverse just as easily. |
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.
| Tip |
|---|
Notice the "Next Seq. Ticket Number" field. It now shows "5". This indicates that if you were to add another ticket to the list, it would be assigned seq ticket number 5.
|
Add Non-Sequential Tickets
We can now enter fishtickets E18 007157 and 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 and repeat the process.
| Tip |
|---|
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
| Tip |
|---|
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. |
| Warning |
|---|
Please validate the tickets you wish to batch prior to selecting Batch as it will give you an opportunity to address any problems before writing to the database. |
Batch the tickets
| Note |
|---|
The tickets in the batch table can be uploaded at any time. It is not necessary to complete the entire range of tickets within the batch before uploading. |
- Click the Batch button.
If there are errors with the batching process you will see a message like this:
At this point you can correct any errors or edit the tickets to address the problems. (In this case deleting the two tickets that have already been batched after making sure they were correctly batched previously → although it would have been better to catch this through Validating the batch first).
If there were no errors and the system successfully batched the tickets, you will receive the message:
INFO 2290: 6 fish tickets batched 
| Note |
|---|
For more information on this process see the documentation for the Agency Desktop. Most of the material is applicable: |
View Batch Information
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 to return to the Welcome Page.
When you've returned to the Welcome Page, enter the fishticket E18 045572 into the "Search by Fish Ticket" field and click the Search button.
The system will go to the Landing Report Search Screen and enter the search criteria to find a landing report with this fish ticket number and automatically run the search. The results of the search will display in the table below the Search button.
- Click on the landing Report ID listed in the search results.
Looking at the resulting report we can see the batch information has been applied to the ticket as we expected.
Error Messages
You may receive error messages when you validate a group of tickets in the batching table.
...
- Sort tickets, conventional and electronic. Electr
- onic Electronic tickets can be auto batched.
- Create a batch within Zephyr for the entire group of eTickets.
- Sort the tickets within this batch by harvest, period, or locale code (if needed) to increase efficiency.
- If tickets present in numeric sequences, ascending or descending, you can enter a range of ticket numbers.
- Enter the values that represent the code assignments for the first group of tickets.
- Enter the next range of fish ticket numbers, or individual fish ticket numbers, if the fish ticket numbers are out of sequence. Press the enter key to populate the batch table.
- You can validate tickets during the data processing of an individual group of tickets or at the end of the entire batch.
- Correct any tickets that do not pass validation.
- Once all tickets have been entered into the batching table, validated and batched the Auto Batching feature will message back that all tickets in this batch have been processed.
...