LOC Analysis or Rough Breakdown

UXPROD-4663: LoC Remote patron registrationIn Progress

Option 1. Online registration Tier 1, Tier 2

Sequence Diagram Step no	TIER	API	Module	ESTIMATION 16SP WORK + 4SP BUFFER = 20SP	Return	Description	Request/Response Payload	Question/Comments/Doubt @Kalibek Turgumbayev / @Gurleen Kaur1 I also have questions in this columns. Pls reply as confluence comment.

Sequence Diagram Step no	TIER	API	Module	ESTIMATION 16SP WORK + 4SP BUFFER = 20SP	Return	Description	Request/Response Payload	Question/Comments/Doubt @Kalibek Turgumbayev / @Gurleen Kaur1 I also have questions in this columns. Pls reply as confluence comment.
2	Tier-1	GET:/Patron-registration-status	edge-patron mod-patron mod-users	3SP	200: if Active 404: if inactive (with error code or msg) 404: if not found (with error code or msg)	To check if email is already exist in USER table.	Request Response	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 mod-users	6SP	201 if record created or update. 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	200: if updated 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-1 Tier-2	POST/UPDATE/UPSERT: /patron	edge-patron mod-patron mod-users	4SP	201 if record created or update. 4XX/5XX: if something else (???)	To store patron Tier-2 data.		Will this be stored in staging table only?

Onsite registration completion

Sequence Diagram Step no	TIER	API	Return	Description	Question/Comments/Doubt

Sequence Diagram Step no	TIER	API	Return	Description	Question/Comments/Doubt
3	Tier-2	GET/Patron with pagination	return patron	return patron from staging	6
7	Tier-2	GET/check-email-exist	return patron/boolean if email exist in user table	return patron from user table via email	6
8	Tier-2	POST/UPDATE/UPSERT/user-patron	201 if user created in user table		4
		PUT/merge api from staging to user table			6SP
17	Tier-2	DELETE:staging-patron	delete patron from staging stable		2
18		Folio hit locate api to notifuy user record created/updated
19		return saved record from 8
20		PUT/update-photo	Will utilise existing upload photo api since record in user table.
21		PUT/patron-group and activation