Student, Member and Session Attendance
Features available when configuring codeREADr as your attendance tracking app.
Click here for the Eastern Michigan University Case Study, including how they leverage the collected data, and here for a detailed article about their process and the value to both students and university.
A short video showing screenshots of the app is shown below. It is also available as a PDF here.
Note: This article discusses the most common service type for attendance, namely validating IDs against a database. However, if you simply want to record IDs (or names) without first validating IDs you can instead create an online or on-device (i.e. offline) ‘Record Scan’ service type.
Overview for Validate Scans
- The first step for a validation service is to create a database of your students, members, attendees or employees and optionally any ‘associated’ content for each ID. So, for example, the ID might be ‘A12345’ and the associated data ‘John Smith’. See Database instructions here.
- The resulting database needs to be uploaded to our servers on the codeREADr.com ‘Databases’ page. [Developers can our use Postback URL or DSU (Direct Scan to URL) to keep this database on their own servers.]
- If you don’t already have barcodes, you’ll need to embed these IDs in barcodes (see Barcodes below). When you create & authorize app Users to scan with the codeREADr app, it will confirm the ID as valid and show the associated text or image.
- For attendance applications, you may want to collect additional data. This can be done using the Questions feature which enables you to have the app user enter data after each scan. For example, you might want to collect course, location or arrival & departure times. You can do this with a Question, e.g. ‘Is this a Check-In or Check-Out?’ answered by the app user via form entry or multiple choice. Since each scan includes a time-stamp, you’ll be able to calculate total time for that class, lesson, event, etc. in Excel, Google Sheets or other database programs. Since Questions show up after every scan, it may be more convenient to simply create two different Services, i.e. one for Check-In and the other for Check-Out and then calculate the difference in the time-stamp for your reports. Alternatively, if you are not concerned about exactly how long the person was at the location, then one Service will suffice and you won’t need any Questions.
- Now comes the easy part – creating a validation Service. Here you’ll need to associate your Database, Users and Questions to the Service you created.
- When you’ve finished scanning you can use the Scans page to view, filter, share and export your scan records.
- Advanced – Photo Verification. You can present the app-user with a photo of the ID holder if you include a link in the database hosting the photo (Webify). You can even use the app to add that link automatically to the database (Photo Postback). Look here for more information on photo verification.
- Barcodes – Do the IDs you want to track already have barcodes on them?
- If YES, try scanning them with the codeREADr app. [Hint: for iOS devices, check the app’s barcode type settings for the barcode type you use.] If you cannot scan them with codeREADr’s standard scan engine, you may need to upgrade to codeREADr ‘SD PRO’ or use a scanning device or use codeREADr on a desktop/laptop with a USB scanning device.
- If NO, then you’ll need to create barcodes. You can create QR codes with codeREADr or use barcodes printed on your own or by card/label printers.
New: Simple Method to Track Session Attendance
What if you have a large number of sessions (or classes, events, etc) to track attendance for. You can accomplish that by creating a service for each one, or now you can now paste a full list of your sessions into codeREADr all at once. Your app users will choose the session they are scanning for, and then that session name/ID becomes part of the scan record for all subsequent scans until changed or cleared.
Please look at this Session Tracking article for instructions.
Self-scanning of barcodes and NFC tags and cards
In this 2-minute video, we show you scanning mobile and printed QR codes using the front camera of iOS and Android devices. Then we show you reading RFID/NFC objects (cards, FOBs, etc.) using Android devices connected to a dedicated reader (pcProx) and also using the built-in NFC reader of Android devices.
If you have 1D barcodes on your IDs or badges you can mount low-cost scanning accessories to quickly scan in unattended situations. We’ve written a blog article about that option, including a 12-second barcode scanner video, and listed the components used.
No Barcodes? Use text/voice search or RFID/NFC instead!
Scanning barcodes is fast. But, it’s not the only way to use codeREADr. You can read RFID/NFC tags (see video above) to capture IDs or use the app’s Manual Entry or Lookup options. Our Lookup feature is very useful in that you can search for the first few characters of an ID and then scroll the resulting list or you can search by name or other identifiers within the barcode or, importantly, within the associated Response text.
This Lookup feature is very commonly used when barcodes are not practical or the student or member forgot their ID. It is very fast and simple, especially when using voice.