-
-
Notifications
You must be signed in to change notification settings - Fork 356
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow multiple check-ins for a ticket #742
Comments
cbellone
added a commit
that referenced
this issue
Sep 6, 2019
cbellone
added a commit
that referenced
this issue
Sep 6, 2019
fix logged event (use BADGE_SCAN instead of CHECK_IN)
cbellone
added a commit
that referenced
this issue
Sep 6, 2019
cbellone
added a commit
that referenced
this issue
Sep 6, 2019
cbellone
added a commit
that referenced
this issue
Sep 7, 2019
include badge scanning auditing in the check-in log
syjer
pushed a commit
that referenced
this issue
Sep 14, 2019
* #742 - model and backend code for supporting multiple check-ins * #742 - cast ZonedDateTime to timestamp in order to truncate it fix logged event (use BADGE_SCAN instead of CHECK_IN) * #742 - add check-in strategy to category_with_currency * #742 - add integration test * #742 - fix test * #742 add ticket validity check for badge scan * #742 include check-in strategy in the encrypted payload for Alf.io-PI include badge scanning auditing in the check-in log * #742 include ticket validity start/end (if present) in the encrypted payload for Alf.io-PI * fix test * #744 - M2 backoffice
implemented |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A better way to measure attendance
For multi-day events is sometimes useful to know how many people there were in the venue on each day.
This is particularly useful for trade shows, where the total number of visitors is given by the sum of the visitors for each day, regardless of when their badge was actually printed.
Introducing Category Check-in Strategy
For backwards compatibility, an organizer must explicitly set a category to allow multiple check-ins.
We will define a "Check-In Strategy" for each Category, with the following values:
ONCE_PER_EVENT
default, retro-compatible. Attendees can check-in only once, using their ticket
ONCE_PER_DAY
Extends ONCE_PER_EVENT by adding the possibility to validate the access by using the printed badge.
IMPORTANT: additional check-ins can be done only using the printed badge. This ensures that a badge is printed only once
How the process works
This modification impacts:
The text was updated successfully, but these errors were encountered: