Summary: | allow the same OPAC login for different users at different branches | ||
---|---|---|---|
Product: | Koha | Reporter: | Melia Meggs <melia> |
Component: | Authentication | Assignee: | Galen Charlton <gmcharlt> |
Status: | CLOSED INVALID | QA Contact: | Ian Walls <koha.sekjal> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | dpavlin |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: | http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1861 | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
Melia Meggs
2012-04-02 21:37:08 UTC
Hi Melia, I was going through old bugs today and 1861 seems relevant in this context. Thinking about it, I am not sure how this can work. How will Koha know wich user is the right one? What happens when both persons choose the same password? We don't ask for the branch on login. What happens when the user moves and the patron record is changed to be at the same branch as the other person of the same name? Making this field non-unique would create many, many more problems than it solves. I recommend against it. Like with any site, usernames are subject to availability. Adding a namespace prefix or suffix per branch would keep the field unique, but allow different branches to use the same root name. Ex: smith@CPL v. smith@AFPL Thanks everyone. That makes sense, and thanks Ian for your suggestion of branch prefix or suffix. |