Versions Compared

Version Old Version 9 New Version 10
Changes made by

Kalibek Turgumbayev

Kalibek Turgumbayev

Saved on

Key

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

...

Attribute

Registration with non-circulating patron group

Registration with staging table

1

Security

Unfinished registration records can lead to potential security issues

Possibility to create big amount of registration in users table is isolated to staging table only

2

Performance

Unfinished registration records can lead to performance degradation as users table is already used for storing patron and users information

Patron records in FOLIO users only appear after id confirmation onsite

3

Analytics

Information on Tier 1 registration is available in Locate. And only information on Tier 2 registration will be in FOLIO

Information on Tier1 and Tier2 registration is available in FOLIO

4

Estimation

Medium: mostly reuses existing FOLIO implementations and mechanisms

FOLIO side is already implemented

Extra Large: Requires additional UI and implementation of staging table

Reuqires rework on the implemented option

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?