LOC Analysis or Rough Breakdown

2

TIER-1

GET:/Patron-registration-status

edge-patron

mod-patron

3SP

1. 200: if Active

2. 404: if inactive (with error code or msg)

3. 404: if not found (with error code or msg)

To check if email is already exist in USER table.

What if a record not found(404) in user table but exist in staging table? In post/patron do we insert the record in staging table?

What if a record 404(inactive expired) in user table but not exist in staging table? In post/patron do we insert the record in staging table? if yes, then what we have to do for the expired record in users table?

Why we are checking email existance status from users table however we are doing post/update in staging table initially? eg if user email not exist in users and we created a record in staging and user stops here, later again he comes and use status api to check it will only check in user table not from staging table even if it exist in staging?

4

TIER-1

POST/UPDATE/UPSERT: /patron

edge-patron

mod-patron

6SP

1. 201 if record created or update.

2. 4XX/5XX: if something else (???)

Create or update patron Tier-1 data in Staging table.

Where should be create the table in mod-patron or mod-user module?

What will be exact table name? staging, user-staging or staging-user?

Will there be jsonb column like mod-users?

WHAT IF 404 WITH INACTIVE found in step-2? Do we create new record in staging table since users table is already having it?

10

TIER-1

POST/UPDATE/UPSERT: /activate-patron

edge-patron

mod-patron

3SP

1. 200: if updated

2. 4XX: if something else (???)

To activate the patron.

In which table we will mark ststus activate?

Record still be there in staging table after activated?

Patron will activated even before T2 registration flow?

15

TIER-2

POST/UPDATE/UPSERT: /patron

edge-patron

mod-patron

4SP

1. 201 if record created or update.

2. 4XX/5XX: if something else (???)

To store patron Tier-2 data.

Will this be stored in staging table only?

TIER-1

TIER-1

TIER-1

TIER-2