https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10060
--- Comment #36 from David Cook <[email protected]> --- (In reply to Christopher Brannon from comment #35) > (In reply to Katrin Fischer from comment #33) > > (In reply to Christopher Brannon from comment #30) > > I totally understand the requirement for consortia, but wondering why you > > say this affects your stats. Can you explain how you solved it now or where > > this effect comes from? > That software is no longer an option, so going to Koha's self check, we have > to use the auto login since most library self checks don't have a keyboard > connected. But we only have the option to use one account to login to with > the auto login. So, we can capture stats per branch. As Christopher mentions here, a lot of libraries use AutoSelfCheckID to log into the self-checkout. Since there can only be one AutoSelfCheckID, all checkouts at all the different branches will be checked out from that user. In the stats, this means the branch associated with checkout will always be the same. I've verified this in my own production installs. (Back in 2013, Liz mentioned even worse issues like the circ rules being applied based on the self-checkout user and not the patron. I haven't looked into that, but that's worth looking at too.) -- Locally, we create "Local" system preferences of "AutoSelfCheckID" suffixed with a branchcode, which allows different branches to have different "AutoSelfCheckID". This is a workaround which won't work so well in the Koha community I think. The best place to put it would probably be the "branches" table, but we'll have to consider the security/permissions ramifications of that, since the current permission required is "manage_sysprefs" and it would move to "manage_libraries". Arguably an understandable change but one worth documenting at the very least. Additionally, each branch must startup their self-checkout using a ?branch= parameter. After that initial visit, the branch parameter gets moved into hidden inputs, but a better place to put it would be in the login session of the self-checkout user. It could be nice to require an additional unguessable code as well so that patrons couldn't manipulate the URL to manipulate the branch used. -- You are receiving this mail because: 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/
