[OPEN-ILS-DEV] Fwd: Local System Admin. - Library Settings
Bill Erickson
erickson at esilibrary.com
Sun Feb 22 11:10:00 EST 2009
On Tue, Feb 10, 2009 at 1:38 PM, John Fink <john.fink at gmail.com> wrote:
<snip>
>
>
> ---------- Forwarded message ----------
> From: "Betty Ing" <ingbe at univmail.cis.mcmaster.ca>
> To: conifer-discuss at googlegroups.com
> Date: Thu, 22 Jan 2009 16:12:46 -0500
> Subject: [conifer-discuss]
>
> Hello,
>
> I am documenting the Local System Admin. functionality using Dwarf
> build-rel_1_4 and have noticed the following:
>
> Selecting Library Configuration and then the Library Settings Editor, I
> see a screen with the title Organization Unit Settings. Are we
> standardizing on Library Settings or Organization Unit?
>
Library Settings seems more staff friendly. However, Organization Unit is
more.. correct, since settings can be applied at all levels of the
organizational hierarchy, many of which would not be called a "library".
For what it's worth, from the developer perspective, we generally use
Organization Unit. From the staff perspective, is it better to be friendly
or correct?
>
>
> Proceeding to the function - Change reshelving status interval (not
> inherited from the parent org unit at run time) - the Context drop-down
> list box is empty. This is most likely affecting the ability to edit
> and save changes to values.
>
>
> Also, the Value field can accept units like seconds, hours, and day.
> Where are the units entered?
>
For intervals, the text is all entered into the value field. "2 hours", "5
years", etc.
>
>
> What needs to be done to enable the desired functionality?
>
This is a permission issue. In Evergreen 1.4, org unit settings permissions
are granular, so staff can be given the permission to change individual
settings at different levels of the org hierarchy. The permission names
look like UPDATE_ORG_UNIT_SETTING.<setting_name>. In this example, the
permission is "UPDATE_ORG_UNIT_SETTING.circ.reshelving_complete.interval"
Permissions for org unit settings are not automatically created at install
time (which will be remedied), which means the permission will have to be
created before it can be applied.
>
>
> Thanks for any input.
>
> Betty
>
Thanks, Betty.
-b
--
Bill Erickson
| VP, Software Development & Integration
| Equinox Software, Inc. / The Evergreen Experts
| phone: 877-OPEN-ILS (673-6457)
| email: erickson at esilibrary.com
| web: http://esilibrary.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20090222/c9679698/attachment.htm
More information about the Open-ils-dev
mailing list