Navigation Menu+

Checking In

The Checkin system is designed to track admission to events. It was first implemented for recruitment, as a device to get prospects involved in coming to open houses and other campus events.

The system has six steps.

  1. An event is set up in the back-end.
  2. Prospects are assigned an ID number, added to the database, and sent a promotional/reminder email about the event. The email gives a customized link and invites them to visit the TLTC web site to download and print out their Fast Pass.
  3. As the links are clicked, the prospects are marked in the database as “printed.”
  4. When the prospects attend the event, they drop their printed out Fast Passes in a box.
  5. Afterwards, staff scans the QR code on each using a handheld device.
  6. Then, they upload the results to the server, where attendance is tabulated and immediately visible.

The events are set up and managed using this form:
event_setup_screen

When attendees click on their link, they see something like this:
fast_pass_screen

Though when they go to print it out, print stylesheets take over and format it nicely for one 8 1/2 x 11 sheet, within minimal coverage and no color.
ticket_print

Events are then managed from here. Notice the two columns of numbers — for tickets viewed, and tickets collected. Before the event the tickets collected number would be zero.
event_list

Clicking on either begins a download of a text file containing the list of people.
download_event_csv

The application is completely self-documenting, by the way.
documentation

At The Event

We’ve threaded a needle with a particular match of software products we use, on a set of dedicated Samsung Galaxy Tabs, though any Android device would work. We weren’t able to get anything working on iOS or Windows Phone devices.

The answer lies in using the QuickMark QR code scanner, which allows for really fine-grained control over what elements within the code are stored, and how they are saved. Incredibly, most QR readers don’t let you save your scans at all, let alone as a file you can manipulate.

The other part is using the Opera Mobile browser. Part of the process is uploading the file of results, but all the other browsers on Android only allow you access to a few folders — usually Pictures, Music and the like. Quick Mark stores its results further down into the file system, in the /mnt/sdcard directory. Opera lets you find files from all over your device.

When one of our volunteers logs into the (bookmarked, of course) Fast Pass site, they log in and start working.
20140305_164004

Then fire up Quick Mark:
20140305_164252

Which is already set to the proper configurations, and start scanning codes.
20140305_164238

Once they’re done with their stack of tickets, they can get ready for the upload. On the mobile device (using responsive design) all the documentation is readily available just like on the desktop version.
20140305_164157

Just go to the upload screen, and click the file button:
20140305_164136

And navigate to the file location where the scans are stored.
20140305_164409

Technologies

Lamp stack on the server side.
Dreamweaver
Twitter Bootstrap, with responsive design and print extensions
jQuery, with

  • Date Picker
  • Modernizr
  • Table Sorter
  • Validate
  • Print Element

PHP
PHP QRcode extension by Dominik Dzienia
LDAP