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

Gating and Early Arrival outline addendum #934

Open
2 of 3 tasks
amotenko opened this issue Apr 29, 2018 · 2 comments
Open
2 of 3 tasks

Gating and Early Arrival outline addendum #934

amotenko opened this issue Apr 29, 2018 · 2 comments
Labels

Comments

@amotenko
Copy link
Member

amotenko commented Apr 29, 2018

This is a continuation to #768

Background

On Sunday morning, during the time in which the authorities do the rounds and the event receives its permit, a ticketing party takes place in Central Camp. At the ticketing party, all burners currently inside the city are being ticketed again, and receive a permanent bracelet instead of the early arrival paper bracelet. The ticketing party is not the end of early arrival phase. In fact, another batch of volunteers is scheduled to arrive that night, and those also has to be ticketed according to the early solution outline until the following day when the event officially opens.
In addition, during the whole early arrival phase up until the party, it is important to keep a counter of people inside the city that is separate from the regular counter. This counter is important for Production because immediately after the party, the number of people inside the city, and the number of people inside the city during early arrival should match.

Suggested Solution

  • In Event Admin Panel, implement a switch that toggles the event from Early Arrival ticketing logic, to normal ticketing logic (already implemented). This switch is used only once on Monday morning when the event is officially opened.
  • In Event Admin Panel, implement a switch that resets the state of all ticketed tickets. All tickets that were ticketed are now un-ticketed. Make sure that the state of those tickets is synced back to Drupal as well. This switch is used only once on Sunday morning, immediately before the ticketing party.
  • Implement a counter that counts burners during early arrival. This is a clicker kind of counter, and is also decremented when people leave, to always represent the current state of things. This counter is not reset once the tickets are reset, so it cannot be computed on the fly. Counter stops counting once early arrival phase is over.

Additional Notes

  • What is the best way to reset the tickets state? Simply delete tickets from database and resync? Iterate over all tickets and modify each? It is also possible that syncing back to drupal is not desired, this will have the benefit of people that used the ticket for early arrival to be unable to transfer it.
  • During ticketing party, the option to transfer tickets should be disabled.
@amotenko
Copy link
Member Author

@pandamichal , please approve this is in fact what you want.

@pandamichal
Copy link

I Approve :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants