...
...
...
...
| 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
...
The Auto Batching tool in the Agency Workstation allows ADF&G ADFG staff to assign batching information to fish tickets fishtickets efficiently within the eLandings Systemsystem. You can create a batch of up to 200 fish tickets for processing within this Agency Workstation 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 the ADF&G 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.
...
Just as a reminder, Alaska Wildlife Troopers and even ADF&G 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 signaturesignature
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.
...
Pre-Batching paper fish ticket processing procedures
Sort conventional ADF&G fish ticket ADFG fishticket reports from the electronically generated eTicket reports, as each ticket type needs to be processed separately.
Conventional fish ticket 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.
...
...
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, 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.
...
- 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.
...
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.
...
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 these tickets first.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.
...
| 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:
...
| 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. |
...
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.
...
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 Report ID listed in the search results.
...