feature-8957: Store and Retrieve check in and out data on server

[nnhathung]

Fixes #8957

Short description of what this resolves:

• Store and Retrieve check in and out data on server

Changes proposed in this pull request:

• implement 2 apis post and get detail user check in data

Checklist

• I have read the Contribution & Best practices Guide and my PR follows them.
• My branch is up-to-date with the Upstream development branch.
• The unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

• All the functions created/modified in this PR contain relevant docstrings.

[nnhathung]

API for #8958

User Check in [/v1/user-check-in]

• Request Method: POST

• Request

  • Header

      Accept: application/vnd.api+json
    
      Authorization: JWT <Auth Key>
    

  • Body (this station_type is 'check in', attendee with id 1 with check in this session 1)

     {
         "data": {
             "attributes":{},
             "relationships": {
                 "station": {
                     "data": {
                         "type": "station",
                         "id": "1"
                     }
                 },
                 "session": {
                     "data": {
                         "type": "session",
                         "id": "1"
                     }
                 },
                 "ticket_holder": {
                     "data": {
                         "type": "attendee",
                         "id": "1"
                     }
                 }
             },
             "type": "user_check_in"
         }
     }
    

• Response 201 create success (application/vnd.api+json)

      {
           "data": {
               "type": "user_check_in",
               "id": 13,
               "attributes": {
                   "message": "Attendee check in successful.",
                   "success": true
               },
               "links": {
                   "self": "/v1/user-check-in/13"
               }
           },
           "links": {
               "self": "/v1/user-check-in/13"
           },
           "jsonapi": {
               "version": "1.0"
           }
       }
  

• Response 422 UNPROCESSABLE ENTITY (application/vnd.api+json)

       {
           "errors": [
               {
                   "status": 422,
                   "source": {
                       "attendee": 1,
                       "session ": 1
                   },
                   "title": "Unprocessable Entity",
                   "detail": "Attendee already checked in."
               }
           ],
           "jsonapi": {
               "version": "1.0"
           }
       }
  

[mariobehling]

Error: Multiple Migration Heads
Compare: https://circleci.com/gh/fossasia/open-event-server/24680

[norbusan]

This should be 3b784f9c98c7 since another migration was included.

[norbusan]

Why do you have two migration files in one PR?
Please merge those into one, with the fix for the correct last revision in development mentioned above

[nnhathung]

Hi @norbusan
because this feature have the dependency with #8958, so another migration file is from that PR.
I will fix it when #8958 is merged.

[mariobehling]

#8958 is merged now. Thanks

[mariobehling]

Please resolve conflicts.

[cweitat]

@nnhathung there's the type in your user check in body. what are the types?

is it this?

[nnhathung]

Hi @cweitat ,
user_check_in in data of request body is api type, not station type. user_check_in type did not have any logic.
user check in and check out based on a station_id.

[cweitat]

@nnhathung is it the same for registration? because registration has no session

[nnhathung]

Hi @cweitat , the same type 'user_check_in' for registration and daily.
and one note that registration and daily can only check in one time per day.

{ "errors": [ { "status": 422, "source": { "ticket": null, "station ": 1 }, "title": "Unprocessable Entity", "detail": "Attendee already registered." } ], "jsonapi": { "version": "1.0" } }

[cweitat]

@nnhathung so I remove session from post body if is type registration/daily?
and if i include session means its session checkin?

[cweitat]

@nnhathung also can i check if

 "ticket_holder": {
                 "data": {
                     "type": "attendee",
                     "id": "1"
                 }
             }

is using ticket id or attendee id? because same attendee can have multiple tickets

[nnhathung]

Hi @cweitat ,
As discussed, session from request is no need for station_type is registration/daily.

and if I include session means its session checkin?
-> check in/out is based on station_type.

is using ticket id or attendee id? because same attendee can have multiple tickets
-> "ticket_holder" from request is ticket_id, accordingly with ticket_holders from database.

FYI: @lthanhhieu