Skip to content
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

Closed
3 tasks done
cbellone opened this issue Sep 5, 2019 · 1 comment
Closed
3 tasks done

Allow multiple check-ins for a ticket #742

cbellone opened this issue Sep 5, 2019 · 1 comment
Assignees
Milestone

Comments

@cbellone
Copy link
Member

cbellone commented Sep 5, 2019

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

  • upon first check-in, the check-in station prints the badge of the attendee, which will contain the QR Code with an ID of the ticket
  • on the following days, the attendee will show their badges, and they'll be counted as "visitor" for that day
  • if an attendee enters the venue more than once in the same day, the operator will receive a warning. We'll log the badge scan anyway, for statistical purposes

This modification impacts:

  • Alf.io
  • Alf.io Scan
  • Alf.io-PI
@cbellone cbellone self-assigned this Sep 5, 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
syjer pushed a commit that referenced this issue Sep 6, 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 integration test

* #742 front-end backoffice for M1

* #742 add ticket validity check for badge scan
cbellone added a commit that referenced this issue Sep 7, 2019
include badge scanning auditing in the check-in log
cbellone added a commit that referenced this issue Sep 7, 2019
syjer pushed a commit that referenced this issue Sep 12, 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 integration test

* #742 front-end backoffice for M1

* #742 add ticket validity check for badge scan
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
@cbellone
Copy link
Member Author

implemented

@cbellone cbellone added this to the 2.0-M2 milestone Sep 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant