Implementing RSVP verification

[MrSunshyne]

Description

A user USER_A is able to login on the frontend.mu website via google. Given that login is successful: A record of USER_A is created in the backend of frontend.mu USER_A is assigned the role ROLE_SSO

Current RSVP process

When USER_A visits an event and completes the RSVP process for that event An entry is upserted into the RSVP table for that RSVP action.

RSVP Table

USER_ID | EVENT_ID | PREFERENCES | NAME | PROFILE_PICTURE | VERIFIED

Permissions

A user is allowed to update his own preferences and view all of his columns Another user is allowed to see the NAME, PROFILE_PICTURE and VERIFIED of all users A user is not allowed to update his own VERIFIED column. (for now)

How could verfication work?

The VERIFIED column is currently unused.

This boolean field would be allowed to be updated by ROLE_ADMIN.

Ideas subsequently unlocked:

1. RSVP to older meetups Allowing RSVP to older meetups could lead to abuse or fake data. Using the VERIFIED column, we could identify/verify who actually attended because organizers have a list of past attendees.

2. Counting attendence in current and future meetups When a user USER_B comes to a meetup, a person with ROLE_ADMIN can then update the VERIFIED column of USER_B in the RSVP table. This can be done manually, but of course it would be nicer to have some kind of QR code scanning process that makes this happen under 5 seconds. [Elaborated further in section "Expanding on RSVP Verification"]

3. Badges on user avatars Verified users can have a badges on their profile picture to show which meetups they really attended.

Expanding on RSVP Verification

If we are able to implement the "Attendee Ticket" feature, we could include a QR code that contains the USER_ID and EVENT_ID in the ticket. Then we read these information to identify which column to update in the RSVP table, and then update the VERIFIED field for that row.