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

Set Checkin-date on category #333

Closed
cbellone opened this issue Sep 6, 2017 · 2 comments
Closed

Set Checkin-date on category #333

cbellone opened this issue Sep 6, 2017 · 2 comments
Assignees
Labels
Projects
Milestone

Comments

@cbellone
Copy link
Member

cbellone commented Sep 6, 2017

Full support for multi-day events will come with v2.0 (along with other things)
For now we must at least support limited check-in, so that organizers can create multi-day events with combi tickets, or they can just create a special ticket for a fraction of the day.

To do that we should add "check-in-from" (default to event start at 00:00) and "check-in-to" (default to event end) to each category

Example1: three days conference

Day1 (2017-09-11): workshops
Day2 (2017-09-12): main event
Day3 (2017-09-13): other workshops / unconference / whatever

in this case the organizer should define the following categories:

  • "day1", check-in from: 2017-09-11 00:00 to 2017-09-11 23:59
  • "day2", check-in from: 2017-09-12 00:00 to 2017-09-12 23:59
  • "day3", check-in from: 2017-09-13 00:00 to 2017-09-13 23:59
  • "full monty", check-in from: 2017-09-11 00:00 to 2017-09-13 23:59

Example1: one day conference

Day1 - main event (2017-09-11 08:00 - 16:00)
Day1 - meet & greet (2017-09-11 16:00 - 20:00)

in this case the organizer should define the following categories:

  • "main event + meet & greet", check-in from: 2017-09-11 00:00 to 2017-09-11 20:00
  • "meet & greet", check-in from: 2017-09-11 16:00 to 2017-09-12 20:00
@cbellone cbellone added this to the 1.13 milestone Sep 6, 2017
@syjer syjer added this to TODO in 1.13 Sep 8, 2017
syjer added a commit that referenced this issue Sep 13, 2017
@syjer syjer moved this from TODO to In Progress in 1.13 Sep 13, 2017
@syjer
Copy link
Member

syjer commented Sep 13, 2017

TODO:

  • save date on creation/update of ticket category
  • update admin ui
  • add check on check in code (backend, frontend)
  • for alf.io-PI we need to change a little bit the data sent: attendee data has validCheckInFrom/To field added, on each ticket category modification, for each tickets within the ticket category, will have a new modification row added in the log, so the modificationSince mechanism for downloading the data will be able to handle it
  • modify alf.io-PI

syjer added a commit that referenced this issue Sep 14, 2017
syjer added a commit that referenced this issue Sep 14, 2017
…pport for set/update valid check in from/to
syjer added a commit that referenced this issue Sep 20, 2017
syjer added a commit that referenced this issue Sep 20, 2017
syjer added a commit that referenced this issue Sep 21, 2017
syjer added a commit that referenced this issue Sep 21, 2017
syjer added a commit that referenced this issue Sep 21, 2017
…pport for set/update valid check in from/to
syjer added a commit that referenced this issue Sep 21, 2017
syjer added a commit that referenced this issue Sep 21, 2017
syjer added a commit that referenced this issue Sep 22, 2017
* #333 checkin date for ticket category: db changes

* #333 fix mysql

* #333 valid checkin from/to: add property in java model

* #333 valid checkin from/to: mysql fix take2

* #333 valid check-in from/to for ticket category: backend: add insert/update support

* #333 valid check-in from/to for ticket category: admin web ui: add support for set/update valid check in from/to

* #333 check-in: add date check range from ticket category

* #333 add UPDATE_TICKET_CATEGORY event for auditing

* #333 fix query for mysql/pgsql

* #333 add valid check in from/to to offline payload

* #333 fix conditions
@syjer
Copy link
Member

syjer commented Sep 22, 2017

should be implemented

@syjer syjer closed this as completed Sep 22, 2017
@syjer syjer moved this from In Progress to Ready for testing in 1.13 Sep 22, 2017
@cbellone cbellone moved this from Ready for testing to Done in 1.13 Oct 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
1.13
Done
Development

No branches or pull requests

2 participants