https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31503 --- Comment #28 from Marcel de Rooy <m.de.rooy@rijksmuseum.nl> --- (In reply to Martin Renvoize from comment #27) Thx for taking a look. Good questions.
1) I think I expected these new consent options to appear in the self-registration form alongside the existing gdpr processing consent.. or for something to direct the user to consent to them immediately after registration?
I treated GDPR as a special one (for historic reasons and when enforced, it rather aggressively asks for consent). Yes, I thought also of adding them on self reg, but later moved away from it. A future extension is allowing to specify opt-in or opt-out. In that case we should add implicit consents for opt-out when finishing a self reg. And think of the best way to communicate that to the user. Apart from GDPR the other consents are now handled as opt-in and not (yet) enforced in some way. The omnibus report also mentions a 'mandatory' type. To keep it simple here, I did not add them.
2) I find the exposure of the AV code a on the page a little strange.. Some AV's have been abused to use 'Staff' and 'OPAC' or 'Title' and 'Description'.. perhaps this might be a suitable resolution?
AV was actually my fallback. I wanted it on Additional contents but we need to make that a bit more flexible before moving. So I considered this a bit as temporary measure to get it moving. We could do as you say but it is also a bit confusing..
I've not dug to deeply yet.. but is there any notification going on anywhere when a consent is later removed? I could imagine a newsletter consent being removed but that being missed by librarians?
This need is mentioned too on the omnibus. I was thinking of the Reporting module first here. But you could have a job that exports them etc. If newsletter processing is in Koha, you could simply check real-time. -- You are receiving this mail because: You are watching all bug changes.