Comment 13 for bug 1527342

Galen: I don't see that issue in practice and I certainly handle enough
front line complaints.

Like Kathy I don't see a need for circ_lib and checkin_lib but I'm not
opposed to them.

On Wed, Dec 30, 2015 at 12:15 PM, Bill Erickson <email address hidden> wrote:

> Force-pushed a fix to support deleting circ history on user purge.
>
> --
> You received this bug notification because you are subscribed to
> Evergreen.
> Matching subscriptions: evergreenbugs
> https://bugs.launchpad.net/bugs/1527342
>
> Title:
> Maintain patron reading history in a dedicated table.
>
> Status in Evergreen:
> New
>
> Bug description:
> Evergreen all versions circa 2.9.
>
> This bug was derived from discussion in bug #1497335.
>
> Patron reading history is derived directly from action.circulation.
> This creates a number of complications and privacy concerns:
>
> 1. It complicates the circ aging process, since we cannot age circs
> that represent entries in an active reading history.
>
> 2. Circs that persist for reading history are accessible via API and
> appear in staff interfaces when they otherwise would not. The goal of
> reading history is to allow patrons to see their own history, but as
> is, it also allows staff to see a patron's reading history. There are
> some protections in place here, but they are not applied universally
> and are easily and sometimes unintentionally bypassed via API.
>
> 2. Patrons cannot (truly) remove specific items from their history,
> since they have no way of deleting circulations, short of disabling
> all reading history. (See also bug #1312699).
>
> I propose we track patron reading history in a separate database
> table. The table (or materialized view) may be similar to action
> circulation, though likely with much fewer columns.
>
> More to follow. Comments appreciated.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/evergreen/+bug/1527342/+subscriptions
>