If your library has more than one register, you may have to select a different register constantly. I would suggest adding a dropdown in the cash_management permission setting for the user to select their default register from a list of registers for their library.
There now is a default setting by branch in newer versions. Does this work for you? It will also remember a previously selected cash register of a user if I am not mistaken, so you won't have to reset it all the time.
I wonder if the permission would be a good spot - It seems not the best place for a user specific setting. We might have a general need there, but maybe having it separately from the permissions (still using them for visilibity) would be good. I also think it might not work well for library staff moving between branches.
(In reply to Katrin Fischer from comment #1) > There now is a default setting by branch in newer versions. Does this work > for you? It will also remember a previously selected cash register of a user > if I am not mistaken, so you won't have to reset it all the time. This does not work. We have more than one desk at a branch, and each register is for a specific desk (hence specific float amounts). The current default setting is kind of useless. If you have a single register for your branch, then that is all you are going to see and use anyway. If you have more than one cash box, you need more than one register. But setting a default register doesn't work for that unless you can define the default per user, not branch. This really needs to be a setting in the user's permission where you give access to the register.
(In reply to Katrin Fischer from comment #2) > I wonder if the permission would be a good spot - It seems not the best > place for a user specific setting. We might have a general need there, but > maybe having it separately from the permissions (still using them for > visilibity) would be good. > > I also think it might not work well for library staff moving between > branches. Maybe the permission needs to be a list, like: borrowernumber : branch: registercode
I don't understand the request here.. you can set the register for your session (and override it at the time of the transaction). The default at branch level is indeed designed for the case where a register may be shared in which case logging in at that branch automatically selects the branch default register for the session. Do you're staff users always sit at the same desk then? Either way.. to improve this we need a clear specification against what currently happens in the latest release (as this would be an enhancement).. and I would not be able to commit to it without sponsorship
(In reply to Martin Renvoize from comment #5) > I don't understand the request here.. you can set the register for your > session (and override it at the time of the transaction). > > The default at branch level is indeed designed for the case where a register > may be shared in which case logging in at that branch automatically selects > the branch default register for the session. > > Do you're staff users always sit at the same desk then? > > Either way.. to improve this we need a clear specification against what > currently happens in the latest release (as this would be an enhancement).. > and I would not be able to commit to it without sponsorship In answer to your request for clarification... Our upstairs desk has a cash box. Our downstairs desk has a cash box. We have to setup a register for each. Both desks are at the SAME BRANCH. Staff at the downstairs desk log into Koha with one account at that desk, and the staff upstairs log into Koha with another account at that desk. TWO separate accounts at TWO different desks in the SAME BRANCH. It is currently IMPOSSIBLE to set a default for each user. I can only set a default per BRANCH. This makes it necessary for staff to at one of the desks to change the register for EVERY transaction. I see no setting for setting the register for a session. The POS does not remain on whatever register you choose. It always goes back to the default, which is not what is wanted for BOTH desks. If the register remaining unchanged during a session relies on session history, then that is a problem, because we specifically do not allow our browsers to retain history. It is PREFERRED that if you give a patron a permission to use the Point of Sale feature, that you could set which register at their branch is THEIR default at that time. Currently I work around this issue with jQuery, to see who is logged in, and set their register. I do not see this as a major project. Probably a new field in a table and a dropdown option next to the point of sale preference at most. I could be over simplifying it. But, there it is.