Checkin takes too long

[GoogleCodeExporter]

At TXLF, where SCALEreg was in use, there were two people doing 'check-in',
resulting in really long lines there and then quick pickup after the
printers had done their job and printed out the badges.

I think check-in could be faster: Produce unique URLs or registration codes
that you give to the attendees as QR-codes or barcodes so that the human
checkers just have to scan them (which is quick!) instead of asking for
names to be spelled or etc.  If the URLs are also encrypted cookies,
they'll also serve as identity verification (since they'd be mailed to the
user upon pre-registration and payment).

Original issue reported on code.google.com by [email protected] on 21 Apr 2010 at 6:33

[GoogleCodeExporter]

Check in took too long because you didn't have computer kiosks where you can do 
self check-in.

We can probably do QR codes, and it's not hard to put a checksum in the QR 
codes that can be used to validate the QR code. However, this is only helpful 
if you have equipment that can scan the QR codes, and maybe interface with the 
computer to check users in.

Original comment by [email protected] on 13 Aug 2010 at 5:41

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Agree with Lei on this one.  The other slow down at TLF in 2010 was we were 
using slow printers and only had 2 check in stations.  TXLF 2011 saw some great 
speed improvements, from using Kiosks and faster printers.  

Lei, do you want to keep this ticket open to track the feature regarding QR 
code scanning? 

Original comment by [email protected] on 17 Sep 2011 at 4:34