Bug 20405 - enhanced messaging preference should always be on
Summary: enhanced messaging preference should always be on
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Staff interface (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks: 20396
  Show dependency treegraph
 
Reported: 2018-03-14 14:05 UTC by Gaetan Boisson
Modified: 2023-10-02 14:52 UTC (History)
5 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gaetan Boisson 2018-03-14 14:05:52 UTC
In order to be able to define "enhanced messaging preferences" for each patron category, and also each patron, a system preference needs to be activated. There is a separate system preference to de-activate it at the opac, which makes a lot of sense, but i think on the staff interface it should always be on, it is up to the administrator to set it up then, without having to find a system preference.
Comment 1 Katrin Fischer 2023-10-01 22:00:04 UTC
We now default  EnhancedMessagingPreferences to 1 for new installations.

I am not sure if there is a use case where showing the preferences always and by default would be bad. Should we remove the preference?
Comment 2 Aude Charillon 2023-10-02 09:46:44 UTC
I agree the messaging preferences should always be visible in the staff interface.

I think there's a case for them not being modifiable by all members of staff (so they don't stray from the patron category defaults) or for only some messaging preferences to be modifiable in the Opac... but those thoughts would be for other bugs!!
Comment 3 Caroline Cyr La Rose 2023-10-02 14:52:36 UTC
The only case I would see where it *could* be hidden would be a very small library who does not send emails/sms at all, it could clutter up the patron record. But I think those would be very few.

I checked our smallest clients (meaning the ones with fewest patrons), and in the ones with under 500 patrons, only one has the pref disabled, a small school. It's a client who has been with us for a while and it was probably before the pref was enabled automatically and we probably did not enable the pref ourselves either.