I've just been taking a look at the manual again ( http://manual.koha-community.org/3.12/en/patscirc.html#patronattributetypes) and I'm not really understanding what the 'Allow password: Check to make it possible to associate a password with this attribute.' option is actually meant to do when creating a new patron attribute type? I thought it would allow the creation of additional login (username:password) combinations for a user to login to the opac but it doesn't appear to do this (if it was meant to, surely it would need to only be available when the attribute is also set to be unique). Anywho, if that is it's purpose, then I'll report a bug, but if it's not the purpose could anyone explain what is was meant to do? -- Martin Renvoize Software Engineer, PTFS Europe Ltd Content Management and Library Solutions Skype: Landline: 0203 286 8685 Mobile: 07725985636 http://www.ptfs-europe.com
Hi, On Thu, Aug 1, 2013 at 10:56 AM, Martin Renvoize < martin.renvoize@ptfs-europe.com> wrote:
I thought it would allow the creation of additional login (username:password) combinations for a user to login to the opac but it doesn't appear to do this (if it was meant to, surely it would need to only be available when the attribute is also set to be unique).
Anywho, if that is it's purpose, then I'll report a bug, but if it's not the purpose could anyone explain what is was meant to do?
I can definitively state that allowing the library to set up multiple login credentials per patron is exactly the purpose of that attribute option. However, there is no code that actually implements such an authentication mode. Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org
participants (2)
-
Galen Charlton -
Martin Renvoize