[OPEN-ILS-GENERAL] question about library hierarchy

[Roma Matott]

Thank you very much for all of this information.  It really helps.  And I will dig into the archives, too!

Roma
PLS
----- Original Message -----
From: "Jason Etheridge" <jason at esilibrary.com>
To: "Evergreen Discussion Group" <open-ils-general at list.georgialibraries.org>
Sent: Tuesday, February 10, 2009 3:47:54 PM GMT -05:00 US/Canada Eastern
Subject: Re: [OPEN-ILS-GENERAL] question about library hierarchy

> Thank you for the information.  I have few other questions if you don't mind.

Sure.  I may punt on some of these to others and re-order the questions a bit.

> Does library workstation designation have any affect on the permissions when you are logged in?  Or is it strictly the home library of the login that determines permissions?
> How is the library designation in the workstation registration actually used by Evergreen?  It seems to affect item search by defaulting to the workstation library designation.  Does it do anything else?

In later versions of Evergreen it's specific working locations that
determine the scope of permissions.  In earlier versions, it's home
library.   The workstation library tends to control display behavior
and circulation behavior (an item is being checked in where?  checked
out where?  Is transiting where?)

> Along the same vein...on a regular basis, I find I need to login to the automation system as the member library sees it.  Does this mean I will need to have a host file with specific entries for all of my member libraries?

Another option (not yet documented) is to append -profilemanager to
the end of the xulrunner invocation (if using Windows, within the
Properties/Target field of the appropriate shortcut).

The development version of Evergreen also has a drop-down menu of all
server hostnames that have been used, which would be useful if you do
prefer the host file method.

Some folks have also resorted to installing the staff client into
multiple locations with multiple shortcuts.  I think -profilemanager
would work best.

> If I want to have a usergroup that has access to all member library items/patrons, is setting up a GlobalAdmin user with the ApplicationPermission group_application.user.staff.admin.global_admin & EVERYTHING permission enabled, the best way to facilitate it?

The EVERYTHING permission lets you do any and everything.  I wouldn't
recommend giving that to more than one person.

I don't think Evergreen comes with a default group called GlobalAdmin
out of the box, but I could be mistaken.  Are you testing against
demo.gapines.org?  Those groups have been modeled after what PINES
uses, but you could do something simpler or more complex.  The groups
and permissions determine what a person can do, but the Work Locations
determine where they can do it.  So, using the User Perm Editor, give
your staff access to all libraries in the Working Location section.

> Or should I include the System level in the hierarchy as a parent of all the member libraries (Consortium -> System -> Member Library) and make these global admin users workstation and home library designations the System?  Essentially, I am trying to find a way that searching all libraries can be the default instead of a specific library.

No, it's best for workstation library to be as specific and "physical"
as possible.  Use Work Locations.

> P.S.  Is there a way to search past postings to this mailing list?  I looked for this information in the Evergreen DokuWiki and found some answers but not all.  I thought if I could search an archive of past posts, it might help as well.  Thanks again for all your help.

Yes, it's hidden in a paragraph in the mailing list section on the
website: http://georgialibraries.markmail.org/search/?q=

Good luck!

-- 
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