https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17505
--- Comment #19 from Tomás Cohen Arazi <[email protected]> --- (In reply to Lari Taskula from comment #18) > I'm open to simplifying, but some thoughts behind the current patch that I > think should not be forgotten (most handled in the current patch): > > For building a selection list client-wise, user should know which messaging > transport types they are able to select. > * Which transport types are enabled in Koha, and which transport types are > available for a particular message type? > * Does patron have defined a valid contact information to select the > transport type (it does not make sense to provide sms selection as transport > type if patron has no smsalertnumber)? > * Is digest available for this transport type? What if a library wants to > force digest ON for some messages? > * Is days in advance available for this message? > > Combine above with patron's current settings. Or do you want another > endpoint for checking what options are available and another for displaying > patron's current selections? > > Also consider checking the same restrictions when PUTting data. > > Some of these thoughts are probably outside of scope of this Bug but my main > point is that we should announce the available configuration options to API > consumer, not just the current selections for this patron. Maybe there's room for a separate endpoint, I'd say. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
