...
Ramsons
Set the User record status to Inactive after the loan is closed so that such records can be filtered out using the existing functionality
Sunflower
Add a "Staff suppress" field to the user record schema (boolean, possible values on UI yes (true) / no (false)). When creating records for Fake Patron, this field should be true. The Users UI App should add a facet for selection and filtering. The filter "Staff suppress = no" is selected by default
Note: The logic and behavior are similar to how the Inventory UI App handles the "Staff suppress" and "Suppress from discovery" flags
Note: Data No data migration is not plannedplanned, instead, the software should interpret the absence of the flag as equivalent to having the flag with a value of no (false)
Note: the The flag of suppression can be re-used in situations where User records would need to be hidden from the Users UI App by default
...
Problem statement: Since the Fake Patron entry record in the Central tenant is a one-time entry use record in the current design, a new user record is created for each real request. Consequently, this leads to a continuous accumulation of records in the mod-users module table. Depending on the frequency of use and number of requests over a prolonged period, this may have negative consequences - growth in database size and its cost, slowing down database operations (insertion, search), and, as a result, slowing down the performance of the Users UI App (though it should be noted that the performance decline might be a gradual process).
...