http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15174 Martin Stenberg <martin@bugs.koha-community.org.xinxidi.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Patch complexity|--- |Small patch Assignee|koha-bugs@lists.koha-commun |martin@bugs.koha-community. |ity.org |org.xinxidi.net -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15174 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katrin.fischer@bsz-bw.de --- Comment #2 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Hi Martin, I am not sure about this change - Koha uses the patron's home category in a lot of places. Can you describe the use case for this? -- You are receiving this mail because: You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15174 --- Comment #4 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Hm, what about handling the overdues? Isn't the "chosen patron category" lost after checking out? So it would only be used for the loan period? -- You are receiving this mail because: You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15174 Viktor Sarge <viktor.sarge@regionhalland.se> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |viktor.sarge@regionhalland. | |se --- Comment #6 from Viktor Sarge <viktor.sarge@regionhalland.se> ---

I am not sure about this change - Koha uses the patron's home category in a lot of places. Can you describe the use case for this?

We developed this one as a bit of a favor to Luleå who have been in need of this feature (though I think they will change their rules now instead). It's quite common for libraries here to have multiple accounts for the same patron depending on in which role they use the library. We have lots of integrated libraries that are both the school and community library at the same time. That means that the same library will serve the same patrons as both students/teachers and as ordinary child/adult accounts. One solution might be to switch library but that will mess up shelving since there's actually only one library and is also impractical when the public can access the library during school hours. This patch would mean that it's a bit easier to handle that type of problems without ugly hacks. When discussing this development Martin did identify a whole lot of places expecting a single code (73 I think), but we suspect that checkout and overdue notices/fees may be enough for the scope of this problem. Before doing further development I think that we need to see that others would find this useful and that it has a fighting chance to get accepted. -- You are receiving this mail because: You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15174 --- Comment #8 from Viktor Sarge <viktor.sarge@regionhalland.se> ---

currently the patron category would be only used at checkout time - so overdues/notices, renewals, etc. would still be those of the initial category as after the checkout there is no trace of the switched category. That's why I feel quite uncomfortable with the idea to be honest. The only thing it will work for is determining the initial loan period.

I knew we would not be able to ignore all the other places the category is used :) You are quite right of course Katrin - renewals is another place that we would have to take into account to make this happen. Since there is no desperate need for this patch and the scope is growing to include all those places we suspected I propose that we leave this in discussion for the time being. There´s other development that needs to happen, but if someone would find it highly useful we might pick it up again. I think the current patch is great for trying out the concept and get a feel of the proposed change if anyone would want to try the suggested workflow. I still think the idea is worthwhile, but the development cost is currently looking to high for us compared to the payoff. -- You are receiving this mail because: You are watching all bug changes.