Org Unit updates shouldn't require direct back-end access

Bug #1902541 reported by Terran McCanna
This bug affects 4 people
Affects Status Importance Assigned to Milestone

Bug Description

Currently, a system administrator has to run AutoGen whenever a library adds a new org unit or updates org unit info such as the name, short (policy) name, opac-visibility, etc.

Since these changes are made within the staff client, they should be able to be handled by a global admin without the involvement of a system administrator.

Possible approaches could be to a) automatically perform the necessary updates that autogen does every time an org unit is modified, or b) add a button in the org unit interface that runs autogen (or a modified version that doesn't touch as many things are does), or c) ... other?

Revision history for this message
Jason Stephenson (jstephenson) wrote :

c) Other: eliminate the need for

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.