On Wed, Jul 11, 2018 at 2:49 PM, Elaine Hardy <email address hidden>
wrote:
> I take that back. I just tested -- I can change the owning library but
> you have to do so in edit volume and not in the copy editor
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1781248
>
> Title:
> web client permissions to edit owning library
>
> Status in Evergreen:
> New
>
> Bug description:
> web client 3.0.9 - The XUL client allowed staff with System
> Administrator permissions to change the owning library of materials.
> The web client does not. Circ staff at our branches need to be able to
> change owning library and we don't want to give them cataloging
> permissions. Can we add permission to change the owning library to
> System Administrator?
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/evergreen/+bug/1781248/+subscriptions
>
I can't even do it in the volume editor. :(
Diane Disbro
Branch Manager/Circulation Coordinator
Union Branch
Scenic Regional Library
308 Hawthorne Drive
Union, MO 63084
(636) 583-3224
<email address hidden>
On Wed, Jul 11, 2018 at 2:49 PM, Elaine Hardy <email address hidden>
wrote:
> I take that back. I just tested -- I can change the owning library but /bugs.launchpad .net/bugs/ 1781248 /bugs.launchpad .net/evergreen/ +bug/1781248/ +subscriptions
> you have to do so in edit volume and not in the copy editor
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> web client permissions to edit owning library
>
> Status in Evergreen:
> New
>
> Bug description:
> web client 3.0.9 - The XUL client allowed staff with System
> Administrator permissions to change the owning library of materials.
> The web client does not. Circ staff at our branches need to be able to
> change owning library and we don't want to give them cataloging
> permissions. Can we add permission to change the owning library to
> System Administrator?
>
> To manage notifications about this bug go to:
> https:/
>