Versions Compared

Key

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

...

Option 1. Online registration Tier 1, Tier 2

Drawio
mVer2
zoom1
simple0
zoominComment10
inCommentcustContentId0443744328
pageId418218140
custContentIdlbox4437443281
diagramDisplayNameVolaris-LoC-Registration-T1-2-V1.drawiolbox1
contentVer2
revision2
baseUrlhttps://folio-org.atlassian.net/wiki
diagramNameVolaris-LoC-Registration-T1-2-V1.drawio
pCenter0
width1171
links
tbstyle
height1163

...

  1. Create a staging table with fields:

    1. First name

    2. Last name

    3. Email

    4. Tier: 1,2

    5. Etc. fields from Tier 2 registration form

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

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

    2. Tier 2 data: store full data

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

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

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

    1. Create a patron record if not present in user table and link it

    2. Link existing patron record with staging record

  6. Create UI dialog to:

    1. Link a staging record with a patron record

    2. Show a list of patron records to choose from

    3. Go to user app with the selected patron record

Questions

  1. Do we need to keep invalid tier 2 data in the staging table?

  2. How do we update the records? How do we handle renewal? - no update

  3. How do we update the staging record if we update email updates in the users table?