Tracking Patron's Last Checkout/Renewal Date

I think this should have a setting to control the granularity of the data stored, i.e. down to the day, the month, or just the year.

And/or an option to enable the feature with it being disabled by default.

Some preference has been expressed in IRC for the former.

Including checkout and renewal (but not autorenewal?) activity in the user activity table would allow counting activity by unique patron. Counting circulation activity by unique patron is currently not possible for aged circulations as a unique identifier for the patron is not retained.

Michele, I think that's an awesome idea. As for autorenewal, it can be recorded with a separate activity type so it can be ignored as necessary. We'd probably want to track in-house-use and non-cat circs as well.

As it happens, the config.usr_activity_type already includes values for "circ", "hold", and "search", so a bit of of the infrastructure for this was anticipated.

If we add a column to config.usr_activity_type to specify the desired precision of the timestamp and sprinkle in the user activity logging calls in the right places, I think that would suffice. I think that the precision should be set at the activity type level rather than bothering with library settings -- and I think there's benefit in forcing a consortium to come to a consensus. Doing it that way would also make it a bit easier for a trigger to do the truncation of the timestamp.

I would advocate for the 'circ' and 'hold' event types to be both transient and inactive by default with the timestamp precision set to year and month by default.