Hi,
I'm trying to work out the logic and meaning behind some of the fields in LT_NSCAN_ATTENDANCE, as some of the data in our table doesn't seem to make sense. In particular, does anyone know the logic behind the ticket_updated and exit_logged fields?
If ticket_updated is 'Y' does that mean that this physical database row has been updated, so if exit_logged now says 'Out' did it previously say 'In'? Also if exit_mode is 'N' then how can exit_logged still be set as 'Out'?
If anyone is able to help, or point me in the direction of some documentation, it would be greatly appreciated!
Does it have anything to do with people exiting the venue mid-performance, being scanned on the way out, and then perhaps re-scanned when they come back in? I believe we do that for emergency purposes so that we have a constantly updated count of people who are actually in the venue. Some people will arrive, get scanned in, but then have to leave early, or they exit the venue to get some refreshments, so we scan them out….those who do not come back are never scanned back in, those who come back in later are re-scanned as being in the venue.
Not sure…just some random ideas…
Penny Tabor
IT Manager
Midland Center for the Arts
Midland, MI 48640
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Simon Davidson Sent: Wednesday, July 25, 2012 4:05 PM To: Tabor, Penny Subject: Re: [Tessitura Technical Forum] LT_NSCAN_ATTENDANCE
Thanks Caryl,
I have tried to track through like that and some seem to make sense, however there are other cases where it doesn't. Case in point, The ticket_update on one line says 'Y', the exit_mode is 'N', but the exit_logged is 'Out'. How can it scan 'Out' if it isn't in exit_mode?!?
Its important that I get accurate figures so that we can monitor attendance at General Adminission events so we don't go over our insurance / H&S occupancy limit...
From: Caryl Jones <bounce-caryljones3976@tessituranetwork.com> Sent: 7/25/2012 9:04:43 AM
I think Exit Mode just refers to what state the scanner was in when the ticket was scanned.
I would look at a specific ticket number that has the info on there to see the pattern of what is happening. This is what I did to try and understand the logic when I was writing some reports for FOH.
From memory, it writes a new line to that table for each event that happens, so you will get a line for the first scan in, a line for the scan out, and a line for the scan back in again.
Caryl
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!