[DRAFT] Renewal Procedure

Summary

The goal of this page is to establish what actions should be done on the FOLIO or Locate side in the renewal procedure for LoC pre-registration flow.

Solution Options

Option	Renewal in FOLIO	Renewal in FOLIO/Locate

Option	Renewal in FOLIO	Renewal in FOLIO/Locate
Description	FOLIO has a scheduled procedure to find expired patron records. FOLIO notifies expired patrons of account renewal with a link to the Locate web form	FOLIO provides API to find expired patron records. Locate has a scheduled procedure that uses this API. Locate notifies expired patrons of account renewal with a link to the Locate web form
Pros	It might be reused as is for other libraries	Consistency. All email notifications from LoC would come from one source Separation of concerns. FOLIO only provides API for expired users.
Cons	LoC/Locate specific information is stored in FOLIO. Particularly renewal web form base URL(Locate), LoC email template Requires to provide a mechanism to synchronize one-time URL between FOLIO and Locate Locate is the end-user-facing system. and Locate already sends ALL the notifications, it should send this email as well	Renewal is not a part of the Locate patron account lifecycle
Work Breakdown	Implement scheduled job to fetch expired patron records from the database Implement code that creates a one-time renewal link and sends email notifications through mod-email/mod-notifications	Implement scheduled job to fetch expired patron records from FOLIO API Implement code that creates a one-time renewal link and sends email notifications through mod-email/mod-notifications
Estimation	L tshirt size. (~12 man days) (Tentative module changes - mod-event-config, mod-users-bl/mod-patron, mod-template-engine)

Questions

Does an account expiration in FOLIO mean a patron should have limited access to Requests through Locate?