Bug 33218 - Should the 'Main contact method' field override the AutoEmailPrimaryAddress at patron-level?
Summary: Should the 'Main contact method' field override the AutoEmailPrimaryAddress a...
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Notices (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-03-13 20:28 UTC by Caroline Cyr La Rose
Modified: 2023-12-09 10:45 UTC (History)
2 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 Caroline Cyr La Rose 2023-03-13 20:28:59 UTC
While I was working on bug 33191 et al. I asked myself if the 'Main contact method' drop down was somehow linked to AutoEmailPrimaryAddress, as a way to override the system preference at patron level. I was told no, but I think it would make sense... If for example AutoEmailPrimaryAddress is set to 'home' (primary email), and a patron chooses their work email as their main contact method, there is no way to send email notices to their work email, is there?

I would see it as something like the CheckPrevCheckouts, where it is possible to override the syspref at the patron-level.

Not sure how it would work with custom values as introduced in bug 31498, however...
Comment 1 kch-tr.lhl-consortium@nhs.net 2023-09-27 10:43:31 UTC
Agree that adding a new value to the system preference AutoEmailPrimaryAddress to match up the option chosen by the user on the Main contact method dropdown would be sensible. 

As it stands the AutoEmailPrimaryAddress preference doesn't have primary_contact_method as a selectable value, which should allow Koha to send notices to the patron's preferred email.
Comment 2 Martin Renvoize 2023-09-27 14:26:49 UTC
I think I'd do this a little differently. I think we should have an option to enable/disable that picker option at the patron level rather than adding it to primary address options. Then use it whenever explicitly set by the patron or use the primary address option if they've not set it.

I also wonder where advanced patron messaging preferences should sit in regards to all this
Comment 3 kch-tr.lhl-consortium@nhs.net 2023-12-09 10:45:38 UTC

(In reply to Martin Renvoize from comment #2)
> I think I'd do this a little differently. I think we should have an option
> to enable/disable that picker option at the patron level rather than adding
> it to primary address options. Then use it whenever explicitly set by the
> patron or use the primary address option if they've not set it.
> 
> I also wonder where advanced patron messaging preferences should sit in
> regards to all this

If this works to prioritise the patron's preferred email choice, then I'd like to see it, would save our staff a lot of time manually swapping data between fields. Not sure what to say about messaging preferences, what are the possible impacts?