LT_NSCAN_ATTENDANCE

Hi Simon,

Here’s a bit of technical background.

1.       When N-Scan first scans a ticket in, that barcode creates a row in LT_NSCAN_ATTENDANCE. For the purpose of future scans of the same barcode number, LT_NSCAN_ATTENDANCE, and the procedure that writes to it (LRP_NSCAN_TICKET_INFO) uses that original row as a “control record” to compare to. This row has a ticket_update status of “Y”, an exit_mode status of “N” and an exit_logged status of “N” (the default for any barcode).

2.       When you exit-scan a barcode that has already been scanned in, a new row is  created in LT_NSCAN_ATTENDANCE with a ticket_update status of “Y”, an exit_mode of “Y” and an exit_logged of “Out.”

a.       in addition to/ this new record, the procedure also updates  the exit_dt of the control record with the update_dt of the new row and sets the exit_logged status of the control record to “Out.”

3.       If the same barcode is scanned back in, then a new row is written to LT_NSCAN_ATTENDANCE with a ticket_update status of “Y”, an exit_mode of “N” and an exit_logged of “In.”

a.       At the same time, the control record – the original barcode – is updated with an exit_dt equal to the update_dt of the row for barcode being scanned back in, and its exit_logged status is changed to “In”.  

b.      It’s possible to see this happening by looking at the update_dt of the in/out scan records and comparing those to the exit_dt of the original scan:

select ticket_no,update_dt,ticket_ok,ticket_msg,ticket_updated,exit_mode,exit_dt,

exit_logged from lt_nscan_attendance

               where ticket_no in (select ticket_no from lt_nscan_attendance where exit_logged = 'Out')

               order by ticket_no, update_dt

This is why you can have a record that appears to have contradictory information (exit_mode = ‘N’ but exit_logged = ‘Out’). In short, what you want to look at is the exit_logged status – if it’s ‘N’, that was a ticket that scanned in and never left; if it’s ‘In’, it’s a ticket that was scanned in, left and came back; an ‘Out’ scanned in, left and was not scanned back in.

I should note that for attendance-counting purposes, reports in Tessitura don’t count scans out and back in as depleting or adding to the number attending. If you want “total scans in, net of scans out” you’ll have to do a real-time calculation of the number of unique barcodes with exit_logged status of ‘N’ or ‘In’ less the unique number of barcodes with exit_logged status of ‘Out.’  

Hope this helps!

Jonathan