How to tell if a ticket / barcode has been scanned or not?

Hi Allan!

The seat status in your orders won't change, but you can view attendance history within the Ticket History tab (it has its own radio button) of the constituent's account. If you want to pull some fun data bits with SSMS, the table you're looking for is called T_ATTENDANCE. You can check their attendance date/time, and see where (or by whom, depending on how you use your scanners) they were scanned in based on the device used. The table also does include ticket_no, so you can pull just one ticket at a time if need be. 

Best,

Darryl 

Awesome! Thanks so much Darryl! I wish the attendance history referenced the ticket numbers though (unless I'm missing it somewhere).. but I can grab that from T_Attendance.

Thanks,
-Allan

For gathering scanned data, what's the difference between T_ATTENDANCE and T_NSCAN_EVENT_CONTROL?  Perhaps one supersedes the other?

Thank you,

...Dave

David: 

T_NSCAN_EVENT_CONTROL tracks every scan attempt for every barcode and ticket number, whether successful or not. T_ATTENDANCE contains only "good" scans - those that result in a valid admission. So the data in T_ATTENDANCE is a subset of that in EVENT_CONTROL. 

To clarify, _EVENT_CONTROL tracks scanning of barcodes for the "Track Tickets" functionality. A partner table, T_NSCAN_AREA_CONTROL, tracks scans for special access areas. 

Jonathan,

On a related topic, is there an intention to look into updating the Attendance radio button on the ticket history tab so that if tickets are returned AFTER they have been successfully scanned in that they will be removed from the "good" count?

I was previously told that that was not a standard functionality for the screen, and I was curious what the value is of showing the attendance count on the customer tab for tickets that were scanned in if the customer returned/exchanged them shortly thereafter.

John

You can also see whether a specific ticket has been marked attended in the order itself, using the Order History tab of Order Details. Once a ticket's scanned, it gets an Attended record, sequenced after the Printed record, which does reference the specific ticket number. Only one Attended record gets written, based on the first successful scan for the ticket, so if you are allowing multiple scans per barcode, you will not see an Attended record in the application for each scan.

Thanks Jonathan, very helpful.  And timely.  We’re getting ready to start scanning using access areas for the first time and I wasn’t aware of T_NSCAN_AREA_CONTROL.

This will be extremely useful!

…Dave

Good morning John. I am not aware of, and so far as I've been able to determine from research, there is no development planned to mark returned or exchanged tickets "un-attended". The underlying logic is that since an exchange would create a new ticket number for the exchanged ticket, retaining the attendance record preserves data integrity because that specific ticket number DID attend the event. 
If the concern is about tracking real-time attendance at events where capacity is an issue, custom reporting against T_NSCAN_EVENT_CONTROL (evaluating entry/exit scans based on the same ticket number and determining the net status of any given ticket) is likely the most viable option.

Thanks for responding, Jonathan.

It makes sense that you would not want to mark that ticket as "un-attended" for data integrity purposes.  I have no objection there.

However, specifically talking about the Attendance Radio button on the Ticket History screen on a patron's account, it can look odd on a patron's account (and I have gotten questions from my staff about this) when the patron only has 3 total tickets to the event showing, but the attendance screen shows them as having 6 attended that event (since the other 3 were returned/exchanged after having been marked as scanned in).  This may seem unusual, but it does happen to us less infrequently than it might, for whatever reason.

Regarding real time reporting that makes sense, too.  It is mainly the patron history that is my qualm right now.

Thanks!

John