Org Unit updates shouldn't require direct back-end access
Bug #1902541 reported by
Terran McCanna
This bug affects 5 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Evergreen |
New
|
Wishlist
|
Chris Sharp | ||
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 autogen.sh does), or c) ... other?
Revision history for this message
| Jason Stephenson (jstephenson) wrote | #1 |
| Changed in evergreen: | |
| assignee: | nobody → Chris Sharp (chrissharp123) |
To post a comment you must log in.
c) Other: eliminate the need for autogen.sh.