Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The following functionality covers the case when a patron comes to LoC registration desk without prior creation of Tier 1/2 Locate account. The Kiosk should be implemented in Locate as a separate form allowing patrons to directly fill in Tier 2 registration data and proceed with registration without e-mail address verification.

Drawio
custContentId
mVer2
simple0
zoom1simple0
inComment0
470089734pageId418218140
lboxcustContentId1470089734
diagramDisplayNameOnsite.Registration.Kiosk.v1.drawio
lbox1
contentVer12
revision12
baseUrlhttps://folio-org.atlassian.net/wiki
diagramNameOnsite.Registration.Kiosk.v1.drawio
pCenter0
width11241152
links
tbstyle
height932615

Work Breakdown Structure

  1. Create a staging table with fields:

    1. First name

    2. Last name

    3. Email

    4. Tier: 1,2

    5. Status: describes if the patron has verified their email address (true/false)

    6. Etc. fields from Tier 2 registration form

  2. Add (edge) GET API to check the registration status in users table:

    1. When the record is found in FOLIO

      • Return 200 - If active

      • Return 404 - If inactive (With a message indicating that it's expired)

    2. When the record is NOT found in FOLIO

      • Return 404 - (With a message indicating that it's NOT FOUND)

  3. Modify (edge) POST API to store data in the staging table and accept:

    1. Tier 1 data (insert): only store First/Last name and email address

    2. Tier1 data (update): the record is activated on Locate side

    3. Tier 2 data (update): store full data

  4. Create GET API for staging table to search/filter data by email/first name/last name

  5. Create UI for staging table to search/filter data by email/first name/last name

  6. Create PUT API to link patron record with staging record

    1. Create a patron record if not present in user table and move it from staging to user table

    2. Update existing patron record with staging record and remove staging record

  7. Create UI dialog to:

    1. Confirmation to update existing patron record with staging data

    2. Dialog to choose one of the existing patron records and update it with staging data

    3. Go to user app with the selected patron record

...