Setting a default library
(Koha 3.0 alpha, Gentoo Linux 2.6.24, MySQL 5.0.54) I really appreciate all the help so far. Here's another question: Our church has only a single library, so I defined just one under Koha Administration -> "Libraries, Branches and Groups". When I go to login to the Intranet site, I put in my username and password and note that the "Library" drop-down box has our library preselected. (It is, in fact, the only choice in the <select> box). Once logged in, however, the top-right corner of the screen shows "NO_LIBRARY_SET". Anything we want to do related to circulation redirects us to http://www.example.com/cgi-bin/koha/circ/selectbranchprinter.pl , where we have to set the library. (again, the <Select> box only has one choice next to "Choose Library") Shouldn't that information be automatically set during the login process? I'd like to avoid that redundant step of having to set the library manually every time following the login. Again, thanks for the help.
George Adams a écrit :
(Koha 3.0 alpha, Gentoo Linux 2.6.24, MySQL 5.0.54)
I really appreciate all the help so far. Here's another question:
Our church has only a single library, so I defined just one under Koha Administration -> "Libraries, Branches and Groups". When I go to login to the Intranet site, I put in my username and password and note that the "Library" drop-down box has our library preselected. (It is, in fact, the only choice in the <select> box).
Once logged in, however, the top-right corner of the screen shows "NO_LIBRARY_SET". Anything we want to do related to circulation redirects us to http://www.example.com/cgi-bin/koha/circ/selectbranchprinter.pl , where we have to set the library. (again, the <Select> box only has one choice next to "Choose Library")
Shouldn't that information be automatically set during the login process? I'd like to avoid that redundant step of having to set the library manually every time following the login.
Again, thanks for the help.
Hi, Normally, all you have to do is to add a new user super librarian. As on a linux box, you are supposed to be logged in with root access, in Koha, you are not supposed to get logged in with Superuser on the database. -- Henri-Damien LAURENT
Hi, Normally, all you have to do is to add a new user super librarian.
Ah, OK - I had missed that concept. I was just going to have all the staff login as "kohaadmin". Ok, I'll setup individual staff members with escalated privileges - thanks for the tip. _________________________________________________________________ Need to know the score, the latest news, or you need your Hotmail®-get your "fix". http://www.msnmobilefix.com/Default.aspx
George Adams <g_adams27@hotmail.com> wrote:
Ah, OK - I had missed that concept. I was just going to have all the staff login as "kohaadmin". Ok, I'll setup individual staff members with escalated privileges - thanks for the tip.
Small aside: I understand that letting all staff login as "kohaadmin" may violate privacy laws in some countries, because you may not be able to trace which librarian accessed which patron's personal data if there's a problem. This isn't a koha-specific matter, though. Regards, -- MJ Ray http://mjr.towers.org.uk/email.html tel:+44-844-4437-237 - Webmaster-developer, statistician, sysadmin, online shop builder, consumer and workers co-operative member http://www.ttllp.co.uk/ - Writing on koha, debian, sat TV, Kewstoke http://mjr.towers.org.uk/
MJ Ray wrote:
Small aside: I understand that letting all staff login as "kohaadmin" may violate privacy laws in some countries, because you may not be able to trace which librarian accessed which patron's personal data if there's a problem.
This isn't a koha-specific matter, though.
[off topic] Wow, that is a huge can of worms. I know that this is a problem w.r.t privacy, but was unaware that the privacy laws have caught up with this. Which countries do you know cover this? How many *nix systems do you know of (for example) where multiple and basically unidentified people have root access? And how many Windows systems have you encountered where everyone knows the admin password or worse yet everyone has admin access? My answer: almost every *nix system and Windows system I have ever worked on. cheers rickw -- ________________________________________________________________ Rick Welykochy || Praxis Services || Internet Driving Instructor The purpose of censorware is not to Protect The Children, but to get some people elected and keep other people employed. -- Daniel Rutter
On Tue, 4 Mar 2008, Rick Welykochy wrote:
MJ Ray wrote:
Small aside: I understand that letting all staff login as "kohaadmin" may violate privacy laws in some countries, because you may not be able to trace which librarian accessed which patron's personal data if there's a problem.
[off topic]
Wow, that is a huge can of worms. I know that this is a problem w.r.t privacy, but was unaware that the privacy laws have caught up with this. Which countries do you know cover this?
I've seen it with companies that operate in the USA - they state it's for audit compliance, and I just assumed it was related to Sarbanes-Oxley or something similar. Worse still, the people who administer their Unix servers (I was one of that group) weren't allowed to add accounts on them - that task was separated out and given to a "security team", who were also supposed to manage the root passwords.
How many *nix systems do you know of (for example) where multiple and basically unidentified people have root access?
Not many, personally - I've only ever seen that in smaller IT shops, though I can't speak for the Windows side. Most places I've worked recently (the past five years) the actual root passwords are very tightly controlled, and superuser-level access is gained by way of one-time keys or similar (RSA SecureID springs to mind). Some places use sudo; either way, we know who you are and what you did last summer... ;-) Cheers Richard
Rick Welykochy <rick@praxis.com.au> wrote:
MJ Ray wrote:
Small aside: I understand that letting all staff login as "kohaadmin" may violate privacy laws in some countries, because you may not be able to trace which librarian accessed which patron's personal data if there's a problem. This isn't a koha-specific matter, though. [off topic]
Wow, that is a huge can of worms. I know that this is a problem w.r.t privacy, but was unaware that the privacy laws have caught up with this. Which countries do you know cover this?
I'm pretty sure English law covers this and I expect the rest of the European Union will be similar. For example, "Good practice notes: Security of personal information" from the Information Commissioner's Office asks in its self-check: "Do staff have their own password and only use the system using their own and no-one else's?" and "If you have information that only certain people should see, do you control access to it?" Source: http://www.ico.gov.uk/Home/what_we_cover/data_protection/guidance/good_pract...
How many *nix systems do you know of (for example) where multiple and basically unidentified people have root access? And how many Windows systems have you encountered where everyone knows the admin password or worse yet everyone has admin access?
Far too many Windows ones and very few Unix-like ones. I think people are far more aware of information security these days and I think we should try to improve Koha in this direction over time. Hope that explains, -- MJ Ray (slef) Webmaster for hire, statistician and online shop builder for a small worker cooperative http://www.ttllp.co.uk/ http://mjr.towers.org.uk/ (Notice http://mjr.towers.org.uk/email.html) tel:+44-844-4437-237
participants (5)
-
George Adams -
Henri-Damien LAURENT -
MJ Ray -
Richard -
Rick Welykochy