-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Store and Retrieve check in and out data on server #8957
Comments
FE: in the check in app. Not implement in eventyay app. |
Hi @cweitat @mariobehling @DonChiaQE |
@lthanhhieu For POST: Expected response: true/false BE uses station_id to get the station_type and do the checks:
BE should be able to: |
Hi @cweitat , could you help me clarify some question?
please help me with these 2 points. FYI: @lthanhhieu |
@nnhathung for registration is the ticket_id. for check session/daily, it will be badge id (VCF EVENTYAY id) ok; passing the session_id wont be an issue. |
yup, thanks @cweitat |
Response for Check in/check out case fail: badge id (VCF EVENTYAY id) = ticket_holder_id |
Currently check-in on the front end is done by updating the attendee profile with the date. We need proper data storage.
APIs required for check-in:
FE: On scan, ticket id and station id will be sent and check in type (registration/session) and the type like whether is it entering or leaving (in/out)
BE: To store the ticket id, datetime (with timezone), station_id, session details - if applicable (track name, session name and speaker name)
If user is already check-in for the session, API should returned that the user is already check in and don't create an entry unless:
If user is already check-in for the day, API should returned that the user is already check in and don't create an entry unless:
#8958 needs to be completed first
The text was updated successfully, but these errors were encountered: