https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40420
Christopher Brannon <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from Christopher Brannon <[email protected]> --- Just to reiterate from the other bug, I don't know if this can be solved with a single switch. I could see the possibility of a mandatory setting for API in some situations and not others. It depends on its application. And having a single switch for something like this would lock it into one behavior and not make it usable for others. I know that there are attributes we don't want the patron to set when it comes to self registration, but we want staff to be able to do that. It makes sense to have this attribute set with a not mandatory setting if it is being addressed with self registration (adding a patron) through API. But what if we have some other 3rd party software creating patrons from a staff aspect, and they need to set that attribute? I don't even know if that exists, but we should approach this from both aspects, I think. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://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/
