[OPEN-ILS-GENERAL] Displaying patron information for checked out books

[Mike Rylander]

I, too, am hesitant to move on this for all the reasons Rogan suggests.
However, to play devil's advocate, with the protection of separate view and
update permissions on the org unit setting, and the non-existence of those
permissions in stock, it should be safe from all but the admin superuser.
Sites wanting to use the feature would need to first add both permissions
and then give those permissions to appropriate staff accounts.  That sets
the bar pretty high.  One could even imagine an internal flag (which
requires database access to set) that would preclude the use of the setting
even if present and configured.

--
Mike Rylander
 | President
 | Equinox Software, Inc. / The Open Source Experts
 | phone:  1-877-OPEN-ILS (673-6457)
 | email:  miker at esilibrary.com
 | web:  http://www.esilibrary.com


On Wed, Feb 4, 2015 at 10:14 AM, Rogan Hamby <rogan.hamby at yclibrary.net>
wrote:

> I hadn't considered special libraries, I was thinking of academic and
> public.  Still, I would want some pretty tight safeguards.  Some
> consortiums allow some local admins to have access to org unit settings to
> customize behavior for their systems (in our case county).  The training
> and preparation of those local admin often varies with the county's
> resources.  Most mistakes can be recovered from without too much fuss but
> the bad impression this would leave ... well, it could be downright toxic.
> I admit, we in SC may be overly sensitive to privacy in some ways since our
> Dept of Revenue got hacked and folks in Eastern Europe got so much of our
> information but yeah, if this went into Evergreen as a patron viewable
> option it would have to be very controllable on a server level in a top
> down way or we would have to seriously re-evaluate a lot and it could end
> up with removing a lot of options from local systems.
>
>
>
>
> On Wed, Feb 4, 2015 at 10:06 AM, Galen Charlton <gmc at esilibrary.com>
> wrote:
>
>> Hi,
>>
>> On Wed, Feb 4, 2015 at 9:55 AM, Rogan Hamby <rogan.hamby at yclibrary.net>
>> wrote:
>> > I want to make sure I'm understanding you.  Do you mean to display it in
>> > TPAC for patrons to be able to see what other patrons have a book
>> checked
>> > out?  If so, at least for us in the United States* that would be a huge
>> > violation of patron privacy.  To be honest, it would be such a big
>> violation
>> > that I wouldn't even feel comfortable with that as an option in TPAC.
>> It
>> > would be like having a bomb waiting to blow up in case someone turned
>> it on
>> > by accident.
>>
>> I agree with Rogan that such an option is not one to be added to
>> Evergreen lightly, nor would I personally feel comfortable if an
>> academic or public library were to turn it on. However, as a data
>> point, such an option does exist in Koha (the OPACShowCheckoutName
>> system preference), and it is specifically for use by corporate
>> libraries.
>>
>> Regards,
>>
>> Galen
>> --
>> Galen Charlton
>> Manager of Implementation
>> Equinox Software, Inc. / The Open Source Experts
>> email:  gmc at 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
>>
>
>
>
> --
>
> Rogan Hamby, MLS, CCNP, MIA
> Managers Headquarters Library and Reference Services,
> York County Library System
>
> “You can never get a cup of tea large enough or a book long enough to suit
> me.”
> ― C.S. Lewis <http://www.goodreads.com/author/show/1069006.C_S_Lewis>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-general/attachments/20150204/dee5173a/attachment.html>