[OPEN-ILS-GENERAL] Unexpected results changing Organisational Units through Staff Client in EG 2.0 alpha4

[Ben Shum]

Repke brings up a solid point about scaring off new users trying out
Evergreen with the awkwardness experienced with trying to change org
units in the current defaults of Evergreen.  I bring this up again
because the issue with changing/deleting the default org units has come
up again on the IRC, so it's not just a few isolated incidents.

While documentation might help to address some of this, I wonder if
maybe it was hasty to change how the organization units are structured
in the default shipping of Evergreen?  I think the change was helpful if
the plan was only to edit the existing structure, but it seems that
others may just want to delete things and start from scratch.

Maybe we should approach this like what has been suggested for the
default options for permission groups and advocate some sort of option
for a "blank" org units tree (like maybe have only 1 for Default
Consortium, which you can edit) during the installation process.

-- Ben

On 10/22/2010 04:30 PM, Repke de Vries wrote:
> Thanks Jason, Ben and Mike.
>
> Mike: the command-line autogen extra step solved the "not picking up" 
> in the staff client pages. Confusing that the wiki page you referred
> to is part valid, part much outdated 'cause instead of the cgi-bin
> scripts for example we now have the Staff Client. Well, Robert
> Soulliere and others in DIG are working on "official" = "most up to
> date - please read this folks" docs.
>
> Jason and Ben: this explains that you can't delete or at least not
> easily from the staff client but should rather revert to direct
> database operations - which by the way might scare off lost of
> organisations wanting to experiment with and evaluate Evergreen.
>
> Yours, Repke, IISH
>
> Op 22-okt-2010, om 21:22 heeft Jason Stephenson het volgende geschreven:
>
>> Just as a followup, I've been working on scripts for our migration
>> next year. In those scripts, I delete all of the org units and org
>> unit information except for the consortium. I also update the entry
>> for the consortium entry with our information and then create the
>> org_units in the script. I don't use the client for this at all. It
>> works rather well if you're good with SQL.
>>
>> HtH,
>> Jason
>
>

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