Active/Inactive was discussed with RA on 8/26/2019 and UM on 8/28/2019. The consensus was that it was desirable to have active/inactive, but at this time, we have not developed concrete use cases that merit working on it as part of the MVP process.
So the UM SIG would like to have the buggy behavior addressed (UIU-913) and set it so that patrons can either be inactive / expired, active / unexpired, or active / no expiration date.
This effectively makes the active/inactive state mirror expired/unexpired, until further development can be done.
====
Patron records have expiration dates, but also active / inactive values. We want to have clear documentation / expectations about how this functions and what we expect to happen for accounts that exist in one of the four states.
Use cases:
- Patron has lost a card or wants access temporarily suspended for some reason.
- Seasonal / temporary staff (who may come in through the bulk loader, or may be manually added)
- Operator login to the system should be disabled
Expiration Date | Active / Inactive Status | |
---|---|---|
Active Status | Inactive Status | |
In the Past (Account Expired) | This state should not happen. |
|
In the Future / No Value (Account Not Expired) | Patron can get all services they are entitled to at the library, by patron group or other library policy. This is normal functioning for active library users. |
|