Extend patron expire date with activity
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
Wishlist:
Automatically extend a patron's expire date if the patron is using the system. "Using the system" can be defined as having entries in actor.usr_activity, which captures the simplest patron activity (e.g. logging in to the catalog, via SIP, etc.), which is important for patrons that may never actually enter a library, but are clearly using it.
Providing a way to avoid updating certain groups (e.g. a bool on permission.
The update interval would be the perm_interval on permission.grp_tree or potentially a static configured value.
I could see this happening in a nightly process or in real time, assuming the real-time version doesn't cause any delays. I'd lean toward nightly batches, because it's not an urgent process. IOW, if the patron can log in, and thus have not expired, updating the expire date *right now* serves little purpose.
tags: | added: patrons wishlist |
tags: |
added: patron removed: patrons |
tags: |
added: circulation removed: wishlist |
Is it part of the plan to add hooks to circ and hold biz logic to insert entries on those actions? AFAICT, there are no activity types for those, though they're supported by the ENUM that constrains the table. Then we'd pretty much only have to look at that table to decide on "active-ness".