[OPEN-ILS-DOCUMENTATION] Documentation issue or client set-up issue? Local Sys Admin permissions

[Ben Shum]

Hi Jenny,

Looking to 2.0 beta4, I think I was able to get some ideas about what
permissions are "missing" from 1.6.1.x in order to get this working
properly.

There are three permissions present in 2.0 that seem related to getting
this working:

ADMIN_GROUP_PENALTY_THRESHOLD
VIEW_GROUP_PENALTY_THRESHOLD
VIEW_STANDING_PENALTY

You have to add these missing permissions to a 1.6.1.x list in the table
permission.perm_list, then creating an entry to grant this permission to
the user groups you want to give editing rights for.  Looks like the
permission for "VIEW_STANDING_PENALTY" must be applied at consortium
depth 0, the other two can be set at system or branch level depth to
control to what extent they can adjust group penalties.

I wouldn't recommend adding these permissions unless you really feel
you'll need them.  Else, waiting for 2.0 release is probably better.  Or
perhaps this is worthy of being a new bug ticket and the missing
permissions should be added back to the next 1.6.1.x release.

Cheers and good luck,

-- Ben

On 12/07/2010 02:09 PM, Turner, Jennifer M wrote:
> Thanks for following up on this!  Now I need to find out from the SITKA folks how they modified the settings - because that's what we want.  :)
>
> I am working with a clean install for the moment, so if I run across any other discrepancies, I'll pass those along.
>
> Jenny
>
> -----Original Message-----
> From: open-ils-documentation-bounces at list.georgialibraries.org [mailto:open-ils-documentation-bounces at list.georgialibraries.org] On Behalf Of Soulliere, Robert
> Sent: Monday, December 06, 2010 12:39 PM
> To: Documentation discussion for Evergreen software
> Subject: Re: [OPEN-ILS-DOCUMENTATION] Documentation issue or client set-up issue? Local Sys Admin permissions
>
> Jenny,
>
> This is an error with the DIG documentation. I grabbed the information from the SITKA documentation which had their customized settings and not the default out-of-the-box settings. I did not have a clean database to test against.
>
> There may be other discrepancies so I will remove the table at: http://docs.evergreen-ils.org/1.6/draft/html/admin-staff_accounts.html until I can verify the out of the box settings.
>
> Thanks for lbringing this to our attention.
>
> Robert
>
>
>
> Robert Soulliere, BA (Hons), MLIS
> Systems Librarian
> Mohawk College Library
> robert.soulliere at mohawkcollege.ca
> Telephone: 905 575 1212 x3936
> Fax: 905 575 2011
> ________________________________________
> From: open-ils-documentation-bounces at list.georgialibraries.org [open-ils-documentation-bounces at list.georgialibraries.org] On Behalf Of Turner, Jennifer M [jennifer.turner at mnsu.edu]
> Sent: December 6, 2010 1:10 PM
> To: Documentation discussion for Evergreen software     (open-ils-documentation at list.georgialibraries.org)
> Subject: [OPEN-ILS-DOCUMENTATION] Documentation issue or client set-up issue? Local Sys Admin permissions
>
> Hello DIG'ers,
>
> I am not sure if an issue I'm having with testing documentation is an issue with the documentation itself or with how the default/non-customized staff client is set up, but thought I would ask the smaller list first...
>
> The documentation (I'm assuming SITKA-contributed, because it mirrors what is available on SITKA's site) mentions that Local System Administrators should be able to edit/create Group Penalty Thresholds for their organizations (http://docs.evergreen-ils.org/1.6/draft/html/lsa-group-penalty.html).  In my experience, the only login that is able to edit these is the "superadmin" or System Account Administrator.  When I attempt to create another admin user and give this user "Local System Administrator" permissions, he/she is unable to select a "Context Location" from the dropdown menu and, therefore, unable to create any Group Penalty Thresholds.
>
> When I first encountered this issue, I was using a slightly customized set of permissions and figured that might be the issue.  However, I am now testing it using a fresh install with the default set of permissions and am still unable to perform certain administrative functions using anything by the super-administrator login (which we would like to NOT give out to our local library administrators).
>
> I have similar issues with other administrative functions, but this is a good example of the problem.  What do we not have set correctly?  Or is there an error in the documentation?
>
> Thanks for any insight - especially from the SITKA folks!
>
> Jenny
>
> ==============================
> Jennifer Turner
> PALS, A Program of the Minnesota State Colleges and Universities Minnesota State University, Mankato ML 3022 Mankato, MN 56001
> 507-389-2000
>
> * Through Our Work, Knowledge Grows *
>
>
> This E-mail contains privileged and confidential information intended only for the individual or entity named in the message.  If the reader of this message is not the intended recipient, or the agent responsible to deliver it to the intended recipient, you are hereby notified that any review, dissemination, distribution or copying of this communication is prohibited.  If this communication was received in error, please notify the sender by reply E-mail immediately, and delete and destroy the original message.
> _______________________________________________
> OPEN-ILS-DOCUMENTATION mailing list
> OPEN-ILS-DOCUMENTATION at list.georgialibraries.org
> http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation
> _______________________________________________
> OPEN-ILS-DOCUMENTATION mailing list
> OPEN-ILS-DOCUMENTATION at list.georgialibraries.org
> http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation
>

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