Batch Check-In Should Not Update Circactive Date
Batch check-in is a necessary component of debt write-off and system maintenance. Running this process updates the patron account circulation activity date (CIRCACTIVE) even though this is a system-generated process and not initiated by the patron.
We use the CIRCACTIVE date when reporting on card usage, and as an indicator of when to delete inactive cards. Because the date is updated through batch check-in, we have to do a lot of clean-up work to understand actual patron usage and behavior.
Ideally, batch check-in should not update CIRCACTIVE. It would be fine for the account UPDATED date to be updated.
This may apply to other batch, administrative tasks that are completed by the library and not the actual patron.
Lisa Motschke
shared this idea
The product team will review this idea for consideration for a future release.
-
Eileen Keller
commented
Knowing when our patrons use their cards is an important part of our patron retention. System functions like batch check in should not update the Circ Active field.
-
Nicole Castellano
commented
This is a good idea. We do plenty of batch check-ins, and this will mess up our circactive patron stats.
-
Lisa Motschke
commented
Batch check-in is a necessary component of debt write-off and system maintenance. Running this process updates the patron account circulation activity date (CIRCACTIVE) even though this is a system-generated process and not initiated by the patron.
We use the CIRCACTIVE date when reporting on card usage, and as an indicator of when to delete inactive cards. Because the date is updated through batch check-in, we have to do a lot of clean-up work to understand actual patron usage and behavior.
Ideally, batch check-in should not update CIRCACTIVE. It would be fine for the account UPDATED date to be updated.
This may apply to other batch, administrative tasks that are completed by the library and not the actual patron.