...
Publishing/subscriptions configuration
Module | Publish/subscribe | Event type | Payload |
---|---|---|---|
mod-feesfines | publish | PATRON_FEE_FINE_BALANCE_CHANGE_EVENT | { |
mod-circulation | publish | ITEM_CHECK_OUT_EVENT | { |
mod-circulation | publish | ITEM_CHECK_IN_EVENT | { |
mod-circulation | publish | ITEM_DECLARED_LOST_EVENT | { |
mod-circulation | publish | LOAN_DUE_DATE_UPDATE_EVENT | { |
mod-automatedblocks | subscribe | PATRON_FEE_FINE_BALANCE_CHANGE_EVENT |
DB
Using the info from events mod-automated-blocks is subscribed to, we need to maintain one object per patron in the DB:
Code Block |
---|
{ "patronId": string, "outstandingFeeFineBalance": numeric, "numberOfOpenFeesFinesForLostItems": numeric, "numberOfLostItems": numeric, "openLoans": [ { "loanId": string, "dueDate": string, "recall": boolean } ] } |
API
mod-automated-blocks will provide one endpoint to