Bug 26413 - Allow changing privacy settings for reading history from the staff interface
Summary: Allow changing privacy settings for reading history from the staff interface
Status: RESOLVED DUPLICATE of bug 20605
Alias: None
Product: Koha
Classification: Unclassified
Component: Patrons (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-08 20:41 UTC by Esther Melander
Modified: 2023-03-20 19:12 UTC (History)
3 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Esther Melander 2020-09-08 20:41:51 UTC
Currently reading/circulation history tracking is controlled by settings in the Patron Categories with the Default Privacy options. Setting the Default Privacy setting to 'Default' means that keeping a reading history becomes an opt-out where a patron has to turn it off in their patron account from the OPAC. Setting the Default Privacy setting to 'Never' means that keeping a reading history becomes an opt-in where a patron has to turn it on through their patron account. 

This becomes a problem either way when working with patrons who are unable or unwilling to login to their patron account to select their preferred option. It would be nice to have an option in the patron account details that allows a staff member to flip the switch for the patron.
Comment 1 Katrin Fischer 2022-07-02 23:03:13 UTC
I believe the original intention here was to leave the choice up to the patrons only, without having the staff interfere. But maybe this could be a preference.
Comment 2 Esther Melander 2023-03-14 17:57:42 UTC
A system preference would be ideal. Our library deals with many patrons that are technology challenged and do not feel confident in using a computer. Current work around is to still adjust the setting for the patron by logging into their patron account. Very often they do not know their password either, so that has to be reset. The entire scenario takes much longer than it should.
Comment 3 Andrew Fuerste-Henry 2023-03-20 19:12:45 UTC

*** This bug has been marked as a duplicate of bug 20605 ***