https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17505 Mike <black23@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- QA Contact|testopia@bugs.koha-communit | |y.org | Assignee|lari.taskula@jns.fi |mail@jkozlovsky.cz CC| |black23@gmail.com Jiri Kozlovsky <mail@jkozlovsky.cz> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |In Discussion --- Comment #1 from Jiri Kozlovsky <mail@jkozlovsky.cz> --- Just to be clear about the implementation details .. For messaging preferences to work, there must be set EnhancedMessagingPreferences to Allow in order to let anyone change anything. This will ensure only staff can edit messaging preferences. For regular users to allow them editing those, EnhancedMessagingPreferencesOPAC must be also enabled. If is EnhancedMessagingPreferencesOPAC enabled, but EnhancedMessagingPreferences is not, no editing is allowed to anyone. API URL will be in this format: /api/v1/messaging_preferences/{borrowernumber} Next, I suppose, there will be GET & POST methods. No else. GET method only returns user's messaging prefs. User can view only it's own prefs, unless he has 'borrowers' rights. POST method updates user's messaging pref. User can update only it's own prefs, unless he has 'borrowers' rights. Both, GET & POST methods will send / receive JSON in this format: { item_due: { email: 0/1, digest_only: 0/1, do_not_notify: 0/1 } advance_notice: { days_in_advance: 0-30, email: 0/1, digest_only: 0/1, do_not_notify: 0/1 } hold_filled: { email: 0/1, do_not_notify: 0/1 } item_checkin: { email: 0/1, do_not_notify: 0/1 } item_checkout: { email: 0/1, do_not_notify: 0/1 } } Please someone take a look at this concept, if it is okay to implement this feature in this way. -- You are receiving this mail because: You are watching all bug changes.