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

[Admin Site] Create separate page to facilitate participant check-in process #269

Open
3 of 6 tasks
Tracked by #266
samderanova opened this issue Jan 17, 2024 · 1 comment · Fixed by #367
Open
3 of 6 tasks
Tracked by #266

[Admin Site] Create separate page to facilitate participant check-in process #269

samderanova opened this issue Jan 17, 2024 · 1 comment · Fixed by #367
Assignees

Comments

@samderanova
Copy link
Contributor

samderanova commented Jan 17, 2024

The third step of the check-in construction is to create a new page on the admin site to provide check-in members with an easy way to check people in. It should contain a table view for participants containing the name, UID, status, and role obtained from #268, along with an actions menu where one can choose whether to promote the current user off the waitlist or check them in. Since we use Cloudscape for the admin portal at the moment, see the Cloudscape demo for an example on how to implement this. No need to provide a column for checkboxes because we'll be checking in one person at a time instead of checking multiple people in at once.

@taesungh taesungh changed the title Create separate page on admin site to facilitate check-ins [Admin Site] Create separate page to facilitate participant check-in process Jan 18, 2024
@taesungh
Copy link
Member

As noted in #315, only certain check-in leads will be allowed to promote users from the waitlist through the endpoint provided by #307/#316. We'll also want a feature to confirm attendance for non-hackers as noted in #318.

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

Successfully merging a pull request may close this issue.

2 participants