Minor ticket scanning improvements
We've been using the ticket scanning feature daily since 9/29. Since then, I've noticed that each day there were tickets purchased, but not scanned. After looking into it closer, I discovered that while scanning multiple tickets in a row, occasionally there is a one to three second lag. During this time, if the screen is not being watched closely, it one or more of the tickets will not actually get inputted. I have started training the volunteers to match the ticket number on the screen with the paper ticket, which seems to help.
However, a simple design change may resolve the problem. It would be great to have a visual and audio cue to communicate when a ticket number has been accepted (in addition to the green arrow, which always looks the same except for the tiny ticket number). Consistently I've seen staff rely on the beep that the scanner makes rather than the visual cue on the screen to verify a ticket was successfully scanned. Would it be possible to have a unique beep made by Altru once a ticket is scanned?
Another feature that would help is a list of the last ten tickets scanned - it could scroll as additional tickets are scanned - that would give ticket takers something to look at to ensure each number is going in and being recorded.
I mostly want to impress that the ticket scanning has been challenging to keep consistent, I've created a custom query showing unscanned tickets purchased today that I reconcile with the paper tickets collected to ensure none were missed. So far, there hasn't been a day we've had 0 tickets missed...