...
Module | Publish/subscribe | Event type | Payload |
---|
mod-feesfines | publish | FF_BALANCE_CHANGE | { "accountId": string, "userId": string, "balance": numeric, "feeFineId": string, "status": string }
Example: { "accountId": "82d804b9-8a73-4d9d-bf9b-78f751758420", "userId": "4f0e711c-d583-41e0-9555-b62f1725023f", "balance": 15, "feeFineId": "95df458a-5a01-4f9a-99e1-64d5657d8379", "status": "Open" } |
mod-circulation | publish | ITEM_CHECK_OUT_EVENT | { "patronId": string, "loanId": string, "dueDate": string } |
mod-circulation | publish | ITEM_CHECK_IN_EVENT | { "patronId": string, "loanId": string, "returnedDate": string } |
mod-circulation | publish | ITEM_DECLARED_LOST_EVENT | { "patronId": string, "loanId": string } |
mod-circulation | publish | LOAN_DUE_DATE_UPDATE_EVENT | { "patronId": string, "loanId": string, "dueDate": string, "recall": boolean } |
mod-automatedblocks | subscribe | PATRON_FEE_FINEFF_BALANCE_CHANGE_EVENT ITEM_CHECK_OUT_EVENT ITEM_CHECK_IN_EVENT ITEM_DECLARED_LOST_EVENT LOAN_DUE_DATE_UPDATE_EVENT |
|
DB
Using the info from events mod-automated-blocks is subscribed to, we need to maintain one object per patron in the DB:
...