[OPEN-ILS-DOCUMENTATION] [OPEN-ILS-GENERAL] Editing/deleting org units

[Turner, Jennifer M]

If it is, indeed, possible to delete org units through the staff client, perhaps it is time to revise - or expand on - the documentation?  The only documentation I could find was: http://docs.evergreen-ils.org/1.6/draft/html/serveradministration.html, which is from 1.6 and didn't seem to work for us on 2.2RC1.  I am copying DIG on this message...perhaps there is more recent documentation, but I'm just not finding it.  If someone has an update, I am sure DIG would be happy to include it in the 2.2 docs!

Regarding single org unit set-up: while it is possible to set up a single-OU tree, the argument I found for leaving the Consortium in place is that it allows the ability to add other branches or libraries in the future.  This is an older list conversation, but I believe it is still relevant: http://list.georgialibraries.org/pipermail/open-ils-dev/2009-January/004039.html.  I don't know that we're "expecting" to gain new branches, but can imagine scenarios in which this might happen, so elected to leave it as a possibility, especially since the OPAC can be limited to search only the single library.

Jenny (PALS)

-----Original Message-----
From: open-ils-general-bounces at list.georgialibraries.org [mailto:open-ils-general-bounces at list.georgialibraries.org] On Behalf Of Mike Rylander
Sent: Tuesday, June 05, 2012 9:52 AM
To: Evergreen Discussion Group
Subject: Re: [OPEN-ILS-GENERAL] Editing/deleting org units

On Tue, Jun 5, 2012 at 9:59 AM, Lazar, Alexey Vladimirovich <alexey.lazar at mnsu.edu> wrote:
> Is there any special reason why the org units are not modifiable through the staff client?

They are, including delete-able.  As there are many interdependencies, though, it can be difficult to get rid of everything you need to in order to effect the delete.  We could consider adding a big, scary "PURGE IT ALL" button, but the number of cases it would cover and the fact that it would be more like a foot-bazooka than a simple foot-gun makes me very leery of doing so.

>
> Also, is it the current recommendation to keep the consortium as the top org unit, even for one-library organizations?
>

You can trim the tree to a single org unit.  Several small libraries do exactly that.

--miker

> Thank you.
>
> Alexey Lazar
> PALS
> Information System Developer and Integrator
> 507-389-2907
> http://www.mnpals.org/
>
> On Jun 4, 2012, at 10:45 , Galen Charlton wrote:
>
>> Hi,
>>
>> On 06/04/2012 11:39 AM, Turner, Jennifer M wrote:
>>> This is a brand new install, so no, the org units are not in use.
>>> Thanks for the response, Galen!  We will look into using SQL...I was 
>>> trying to save the tech staff some work. :)
>>
>> Fair enough, but in this case I agree with the "Changing the Default Organizational Units and Types Using SQL" heading in the manual [1] that using SQL is the quickest wait to trim the OU tree in a fresh installation.
>>
>> [1] http://docs.evergreen-ils.org/2.1/html/serveradministration.html
>>
>> Regards,
>>
>> Galen
>> --
>> Galen Charlton
>> Director of Support and Implementation Equinox Software, Inc. / The 
>> Open Source Experts
>> email:  gmc at esilibrary.com
>> direct: +1 770-709-5581
>> cell:   +1 404-984-4366
>> skype:  gmcharlt
>> web:    http://www.esilibrary.com/
>> Supporting Koha and Evergreen: http://koha-community.org & 
>> http://evergreen-ils.org
>



--
Mike Rylander
 | Director of Research and Development
 | Equinox Software, Inc. / Your Library's Guide to Open Source
 | phone:  1-877-OPEN-ILS (673-6457)
 | email:  miker at esilibrary.com
 | web:  http://www.esilibrary.com