Implement checkin field-scanning

The idea behind this is to add secondary "stations" at a conference
checkin which can off-load the main check-in. Typical example can be a
desk for handing out t-shirts separate from the registration.

Each checkin-field is tied to one of the dynamic reporting fields
implemented earlier, and once the "store" button is clicke on the
checkin dialog, the date of it being done is stored in the field.

Unlike regular check-in, this the check-in field scanning is done off
the *badge* not the ticket. This makes it more like the sponsor badge
scanning, and therefor we have to add a new landing page that can handle
the case when the same person is both a sponsor scanner and a check-in
scanner. It will then just prompt the user for which one.

This merges the two separate but extremely similar web scanner apps used
for checkin and badge scaninng into one, that is driven by parameters.
There's enough complexity there that we don't want two independent
ones...

In passing, support for old-style tokens (prior to 074e324, almost a
year ago) is removed to simplify the code. That means that tickets or
badges issued before 074e324 was deployed can no longer be scanned, but
given how long ago it is this should not happen.

Per original idea from Vik Fearing with input from several more people
over time.

Author: mhagander

docs/confreg/configuring.md

@@ -205,6 +205,13 @@ Dynamic properties
    to each registration. These fields are used for custom reporting
    and similar functions, and are not visible to the end user.
 
+Scanning properties
+:  List of dynamic properties that can be used as part of the scanning
+   system. For [check-in processors](tickets#scanningfields) this allows
+   them to perform secondary scanning of badges to mark other items.
+   The list here must be a subset of the *Dynamic properties* above, or
+   empty.
+
 Registration open
 : If regular registration is open.
 

docs/confreg/tickets.md

@@ -90,14 +90,30 @@ check-in can be performed. Once the check-in is performed, it's stored
 when and by who, so it the same attendee tries to check in again (or a
 different one with the same ticket...), it will be clearly shown.
 
+### Scanning fields
+
+Scanning fields allows the check-in process to be split into multiple
+steps, where different things are scanned at different times. A
+typical use for this is to have conference t-shirts handed out
+separately from the main check-in. The permissions are integrated with
+the check-in system, so the same people will have permissions on
+it. However, instead of scanning the ticket, they will be scanning
+attendee badges, to bring up approximately the same information.
+
+The scanning fields are configured as a subset of the
+[dynamic properties](reports#dynamic) used in reporting, and for each
+scanning field the timestamp when it was stored will be registered in
+the dynamic property (and an entry will be written to the registration
+log).
+
 ### Check-in processors
 
 The people processing the check-ins will get a link on their
 registration page that goes to the check-in information page.
 
 This page will contain a link (both directly and as a QR code) to the
-check-in app, and the ability to have the link sent to them by email
-(because it's a convenient way to get the link onto a device).
+check-in app. If multiple scanning fields are used, indepdendent links
+will be provided for each of them.
 
 The check-in app itself does *not* require the user to be logged in,
 so this link can easily be copy/pasted.

media/css/badgescan.css

@@ -3,28 +3,33 @@ body {
     padding-bottom: 60px;
 }
 
-dl.checkin_list dt {
+dl.found_list dt {
     background-color: lightgray;
     padding: 3px;
     padding-left: 5px;
     border-radius: 3px;
 }
 
-dl.checkin_list dd {
+dl.found_list dd {
     margin-bottom: 3px;
     padding: 3px;
 }
 
-dl.checkin_list dd.checkin_dyn_warn {
+dl.found_list dd.found_dyn_warn {
     background-color: darkred;
     color: white;
 }
 
-dl.checkin_list dd ul {
+dl.found_list dd ul {
     padding-left: 15px;
     margin-bottom: 0;
 }
 
+dl.found_list dd textarea {
+    width: 100%;
+    height: 7em;
+}
+
 #completed_div {
     display: none;
 }