[OPEN-ILS-GENERAL] Issues with new user accounts and languagesin the OPAC

[Linda Skolkova]

Dear Jason,

 

Thank you for your thorough explanation! We shall try to set the permissions
according to your hints :-)!

 

Linda

 

**************************************************************

Linda Skolkova, M.A.

E-mail: linda.skolkova at ff.cuni.cz, skolkova at chello.cz 

 

Instutite of Information Studies and Librarianship

Faculty of Arts, Charles University, Prague

http://uisk.ff.cuni.cz/ 

**************************************************************

Paths are made by walking. Franz Kafka

 

 

-----Original Message-----
From: open-ils-general-bounces at list.georgialibraries.org
[mailto:open-ils-general-bounces at list.georgialibraries.org] On Behalf Of
Jason Etheridge
Sent: Wednesday, April 08, 2009 4:57 PM
To: Evergreen Discussion Group
Subject: Re: [OPEN-ILS-GENERAL] Issues with new user accounts and
languagesin the OPAC

 

> 1) We are not sure which permissions we should set for the circ user who
is

> supposed to create new user records (accounts). The user who now has circ

> permissions cannot set the user type during registration (the whole

> registration process works, however, it is not possible to select the user

> type and to proceed with registration). It works when local admin and
admin

> accounts are used. Does anyone have any idea about this?

 

Hi Linda,

 

If you look in the staff client under Admin -> Server Settings,

Permission Groups, and browse through the different permission groups

listed, you'll see that each has a field called Editing Permission (in

older interfaces this was called the Application Perm).

 

A given staff member (or staff permission group) will need that

permission for each group they need to be able to add someone to.

They'll also need every Editing Permission that occurs in ancestor

permission groups.

 

For example, let's say part of your permission hierarchy looks like this:

 

Users -> Patrons -> Outreach

 

And the Editing Permissions for each of those happen to be

group_application.user, group_application.user.patron, and

group_application.user.patron.outreach, respectively.

 

And you want staff in your Users -> Staff -> Circulators group to be

able to register Outreach patrons.  Then in the Group Permissions tab

for Circulators, they would need these listed as permissions:

 

group_application.user

group_application.user.patron

group_application.user.patron.outreach

 

Otherwise, the Outreach "profile" would be grayed out in the patron editor.

 

Does this help?

 

The actual names of the permissions are arbitrary and by convention,

so you can change and/or remove values in the Editing Permission field

to simplify things.

 

-- 

Jason Etheridge

 | VP, Community Support and Advocacy

 | Equinox Software, Inc. / The Evergreen Experts

 | phone:  1-877-OPEN-ILS (673-6457)

 | email:  jason at esilibrary.com

 | web:  http://www.esilibrary.com

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://libmail.georgialibraries.org/pipermail/open-ils-general/attachments/20090409/d521a584/attachment-0001.htm