Chris, If you don't specify the SCO user in the sysprefs, you have to manually log in as that user on the workstations you are designating as SCO. This is then subject to timeout, I believe. So, if you don't mind maintaining the distinct logins on your workstations manually, you're in good shape, no new code required. It would only be a project if you wanted to enable auto-login for that set of users. -Ian On Thu, May 10, 2012 at 4:02 PM, Chris Nighswonger < cnighswonger@foundations.edu> wrote:
On Thu, May 10, 2012 at 3:54 PM, David Schuster <dschust1@gmail.com>wrote:
OK here is how we have it setup, and I just verified it still works that way with 3.06.04.
AutoSelfCheckAllowd - Don't Allow
The librarian logs into the sco using a "user" setup as lmsxxx/password - xxx is the location
All transactions there are associated with the user's location.
Granted that forces you to setup 67 users and someone has to open that up, but it has been working well for us for 4 years.
Does that make sense? I don't want to auto login as you note somehow the system needs to know where you are from to track stats and route books correctly.
This is too easy to be true.... ;-) Let me see if I understand correctly:
At Branch A:
1. Log into the staff client using Branch A's SCO account. 2. Navigate to the sco interface.
At Branch B:
1. Log into the staff client using Branch B's SCO account. 2. Navigate to the sco interface.
Please tell me it works this way and save me lots of hours of coding... ;-)
Kind Regards, Chris
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/