Bug 20380 - [OMNIBUS] Email consent patron opt-in tracking for anti-spam legislation
Summary: [OMNIBUS] Email consent patron opt-in tracking for anti-spam legislation
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Patrons (show other bugs)
Version: master
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on: 31533 31503
Blocks:
  Show dependency treegraph
 
Reported: 2018-03-13 00:29 UTC by Agnes Rivers-Moore
Modified: 2022-10-11 11:11 UTC (History)
6 users (show)

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


Attachments
Your consents (175.09 KB, image/jpeg)
2022-09-02 08:43 UTC, Marcel de Rooy
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Agnes Rivers-Moore 2018-03-13 00:29:39 UTC
An email consent opt-in field is something that many libraries need to accommodate, with recent legislation in US, Europe, and Canada (which may be the most strict yet).
Please comment / add suggestions.

Useful features would be:
- Email Consent field with Authorised Values drop down allowing multiple choices to allow for different legislation e.g. Yes/No, radio button or tick box,
- If Yes, then mandatory date from calendar picker
- Preference to make this mandatory/non mandatory for new patron and/or at patron renewal (if mandatory it would need Yes/No rather than radio/tick box)
- Preference to set mandatory/non-mandatory for OPAC self-registration (with "Yes I consent..." opt-in wording)
- Ability to export data (SQL report?) based on consent choices and consent date or timestamp (for upload to mailer program)

Also nice to have:
- Additional separate library-set categories for Yes to receive library messages, library newsletter, new titles list, book club updates, library events etc. (each with y/n, tick box...)
- Timestamp recorded when any consent field changes (to yes or from yes to no). The date picker might be enough for initial consent but legislated requirements may vary in different countries.

Libraries are using 'additional attributes' as a workaround but lack the date recorded (or timestamp) for changes to the consent status, and ability to differentiate permission for core library service messages and news/marketing messages.
Comment 1 Marcel de Rooy 2022-08-31 14:33:12 UTC
This is still interesting for us.
We had a custom opt-in checkbox for library newsletters and service mails on the messaging tab of the opac account page. (And a timestamp for the consent saved in a separate table.)

But the field should probably better be moved to Your consents on the account page (independent of enhanced messaging prefs). And could be extended with things described above? Bit more generic.
Comment 2 Marcel de Rooy 2022-09-01 09:32:05 UTC
I am making this report an omnibus to allow multiple developments.
Adding some groundwork for this on bug 31503.
Comment 3 Marcel de Rooy 2022-09-02 08:42:17 UTC
(In reply to Marcel de Rooy from comment #2)
> Adding some groundwork for this on bug 31503.

Bug 31503 is ready for testing, folks.
It became a bit more than groundwork. But it does not implement all things mentioned in the description here.
It allows you to add various consents to the OPAC consents page. It is controlled by Authorised values. And adds content (slightly experimental) via the Additional contents feature.
Comment 4 Marcel de Rooy 2022-09-02 08:43:05 UTC
Created attachment 140086 [details]
Your consents
Comment 5 Marcel de Rooy 2022-09-08 07:15:20 UTC
Added another report for opt-in/opt-out on bug 31533. It still needs a bit of user feedback too.
But we will definitely have to get the other one in first before I may commit some time there..
Comment 6 Marcel de Rooy 2022-10-11 11:11:05 UTC
(In reply to Marcel de Rooy from comment #3)
> (In reply to Marcel de Rooy from comment #2)
> > Adding some groundwork for this on bug 31503.
> 
> Bug 31503 is ready for testing, folks.
> It became a bit more than groundwork. But it does not implement all things
> mentioned in the description here.
> It allows you to add various consents to the OPAC consents page. It is
> controlled by Authorised values. And adds content (slightly experimental)
> via the Additional contents feature.

Bug 31503 didnt make it for now. It may need some more thought and time :)