[OPEN-ILS-GENERAL] ***SPAM*** Re: Re: Open-ils-general Digest, Vol 74, Issue 41

[Ben Shum]

Hi Erik,

Have you tried granting the base permission as well, such as 
'group_application.user' to the Volunteers group?  I can't remember if 
you need that as well.

The editing permission that you see in the Permission Groups Editor 
refers to the permission for editing that group.  So each group has its 
own editing permission value.  And then you grant that permission to the 
other groups you want to give powers to edit them.

-- Ben

On 08/21/2012 04:25 PM, Erik Stevens wrote:
> Thanks Ben,
>
> "you have to give 'group_application.user.patron' as a permission to the
> Volunteer staff group you're creating to allow them to edit patrons
> associated with the 'Patrons' group."
>
> I think this must be the problem (since volunteer can edit its own 
> patron record, just not others), but I still cannot seem to fix it. 
> Perhaps I am just not implementing this correctly?
>
> In the Permission Groups Editor, I go to the first tab for the 
> Volunteer group (to which I am assigning my volunteer login account), 
> and set the field Editing Permission to group_application.user.patron 
> (I have also tried user.staff, and of course I am careful to save and 
> verify and even try autogen just in case).
>
> This did not help though, so I tried going into the second tab in 
> the Permission Groups Editor and tried adding new mappings for 
> the group_application.user.patron, and group_application.user.staff 
> permissions. That didn't help either.
>
> Is there somewhere else that the editing permission level can be set?
>
>
>
>     Hi Erik,
>
>     I think what Thomas was trying to say in his reply is that you need to
>     grant the associated user permission to the staff patron group you're
>     setting up.
>
>     So for example, 'group_application.user.patron' is the name of the
>     'application_perm' for the default 'Patrons' group.  So that means you
>     have to give 'group_application.user.patron' as a permission to the
>     Volunteer staff group you're creating to allow them to edit patrons
>     associated with the 'Patrons' group.  If you have any other groups
>     they
>     need to be able to edit, you'd need to check the application_perm for
>     those other groups.
>
>     We use this extensively in our consortium with additional custom
>     application_perms to restrict editing between various staff
>     groups, etc.
>
>     -- Ben
>
>     On 08/17/2012 03:02 PM, Thomas Berezansky wrote:
>     > Each permission group has a permission assigned to it that you would
>     > need to grant for people to be able to edit those patrons. You
>     can see
>     > what is assigned by looking at the permission/profile groups
>     themselves.
>     >
>     > MVLC has a "patron" group, for example, that we assign "patron staff
>     > members" to. Only our central site staff can edit that group,
>     ensuring
>     > that desk staff and volunteers don't change the passwords of other
>     > staff members.
>     >
>     > Thomas Berezansky
>     > Merrimack Valley Library Consortium
>     >
>     >
>     > Quoting Erik Stevens <technology at haineslibrary.org
>     <mailto:technology at haineslibrary.org>>:
>     >
>     >> Hi Evergreen Community,
>     >>
>     >> I have a noobish question/problem about permissions that I'm
>     sure has an
>     >> easy answer:
>     >>
>     >> We have a Volunteer login for the staff client that is limited
>     in its
>     >> permissions. One thing it currently cannot do is edit patron info
>     >> using the
>     >> Edit tab in the patron record pages.
>     >>
>     >> We are trying to allow this account to save edits to patron records
>     >> but I
>     >> cannot seem to make this work (the save buttons are disabled).
>     I have
>     >> tried
>     >> giving the account the CREATE_USER and UPDATE_USER permissions,
>     with the
>     >> editing permission level set to staff or patron-level (and then
>     running
>     >> autogen), but this doesn't do it. The volunteer account can
>     only save
>     >> changes to its own patron record, not anyone else's.
>     >>
>     >> What am I missing here? What has to be enabled to allow saving
>     >> changes to
>     >> other patron records? We are running Evergreen 2.1.
>     >>
>     >> Many Thanks,
>     >>
>     >> --
>     >> Erik Stevens
>     >> Technology Coordinator
>     >> Haines Borough Public Library
>     >>
>     >
>     >
>     >
>
>     --
>     Benjamin Shum
>     Open Source Software Coordinator
>     Bibliomation, Inc.
>     32 Crest Road
>     Middlebury, CT 06762
>     203-577-4070, ext. 113 <tel:203-577-4070%2C%20ext.%20113>
>
>
>

-- 
Benjamin Shum
Open Source Software Coordinator
Bibliomation, Inc.
32 Crest Road
Middlebury, CT 06762
203-577-4070, ext. 113

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-general/attachments/20120821/bf75b6f5/attachment.htm>