You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 14, 2020. It is now read-only.
Registration is the thing that competitors do online before a competition. (They'll pick the events they're interested in, maybe pay for those events, and may volunteer to judge and scramble, and may say they're going to bring guests.)
Check-in is something that AFAIK, happens at every competition. This is when competitors show up and pay for the events they registered for but didn't pay for, and score cards are possibly filled out, or reorganized. When we get around to Phase 2, this may be when we give competitors their id card for the competition =).
@jbcm627's addition of a Registration collection is designed to handle registration. However, in order to enter times for a competitor, we need there to be an document in the Results collection for them. Registration does not place a competitor in any Results collection. Check-in will copy competitors from Registration to Results so that a competitor's list of registered events will equal the list of events they're "checked in for".
Here's a rough sketch of what the check-in table will look like:
Name
333
444
Jeremy
X
Check in button
Jim
X
X
Check in button
Devin
X
Check in button
Each row corresponds to a competitor. Every cell is a checkbox that is checked if the competitor is registered for that event (if an organizer clicks this checkboxes, it will togger the competitor's registration for that event). If registered != checked-in for any cell, then we color the background of the cell red to draw attention.
If a competitor's registered events != their checked in events, we show either a "Check in!" button, or an "Update check in" button according to whether they've already checked in.
NOTE: In the interest of not ever deleting data without it being very obvious beforehand, we will disable checkboxes corresponding to events for which times have already been entered.
The text was updated successfully, but these errors were encountered:
First off, some definitions:
Registration is the thing that competitors do online before a competition. (They'll pick the events they're interested in, maybe pay for those events, and may volunteer to judge and scramble, and may say they're going to bring guests.)
Check-in is something that AFAIK, happens at every competition. This is when competitors show up and pay for the events they registered for but didn't pay for, and score cards are possibly filled out, or reorganized. When we get around to Phase 2, this may be when we give competitors their id card for the competition =).
@jbcm627's addition of a Registration collection is designed to handle registration. However, in order to enter times for a competitor, we need there to be an document in the Results collection for them. Registration does not place a competitor in any Results collection. Check-in will copy competitors from Registration to Results so that a competitor's list of registered events will equal the list of events they're "checked in for".
Here's a rough sketch of what the check-in table will look like:
Each row corresponds to a competitor. Every cell is a checkbox that is checked if the competitor is registered for that event (if an organizer clicks this checkboxes, it will togger the competitor's registration for that event). If registered != checked-in for any cell, then we color the background of the cell red to draw attention.
If a competitor's registered events != their checked in events, we show either a "Check in!" button, or an "Update check in" button according to whether they've already checked in.
NOTE: In the interest of not ever deleting data without it being very obvious beforehand, we will disable checkboxes corresponding to events for which times have already been entered.
The text was updated successfully, but these errors were encountered: