LoC Staging registration Contract

GET /patron-registration-status/{emailId}

• Regarding the error responses. I was expecting a response like the following. Sending 404 as part of the response body seems redundant.

• Do we need to have 3 different 404 messages.

  • Inactive

  • Expired

  • Not Found

POST /patron

• Do we need to allow the status to be set via this call ? Can you think of any reason where this would be used to set the patron to anything other than TIER-1 ?

• We will be using this endpoint for submitting the following. How will the required fields be different when submitting just Tier 1 data ?

  • Tier 1 data

  • Tier 2 data

  • Tier 1 + Tier 2 data

• I am going to assume that we can call POST /patron any number of times. Each time it gets called, it overwrites existing data, correct?

Hi @Vijay Gopalakrishnan ,
Below are the responses for the POST /patron API questions -
1. Yes, it is necessary to allow the status to be set via this API call. According to the staging user registration flow, a user can be added to the staging table in either TIER-1 or TIER-2 (Kiosk) scenarios. Furthermore, an existing user may be edited under either circumstance. Setting the status through the API ensures that we maintain accurate status values in FOLIO for reporting purposes, I believe.
2. The common required fields, as mentioned above, are firstName, lastName, and email. The remaining fields are optional, except for the isEmailVerified and Status fields. If values for these fields are not provided, they will default to false for isEmailVerified and TIER-1 for the Status field, respectively.
3. Yes correct.
CC :@Kapil Verma1 @Kalibek Turgumbayev @Vignesh Kalyanasundaram

Hi @Vijay Gopalakrishnan
Please find the response regarding the GET /patron-registration-status/{emailId} API.

• As per the current edge-patron code, the ErrorMessage class has a code property that accepts only an integer status code. This is why we followed the current approach. However, we can certainly customize the implementation based on your above suggestion only for this API.

• We currently handle three distinct error scenarios:

  1. Multiple active records found in FOLIO – returns 400 Bad Request.

     {     "code": "MULTIPLE_USER_WITH_EMAIL",     "errorMessage": "Multiple users found with the same email" }

  2. Record found in FOLIO but inactive – returns 404 Not Found

     {     "code": "USER_ACCOUNT_INACTIVE",     "errorMessage": "User account is not active" }

  3. Record not found in FOLIO – returns 404 Not Found

     {     "code": "USER_NOT_FOUND",     "errorMessage": "User does not exist" }

I have updated the error messages as per your suggestion. Please let us know if you're okay with these changes, and we will proceed with implementing the adjustments in the code.

cc : @Kalibek Turgumbayev @Gurleen Kaur1 @Kapil Verma1