Hey April,
Our consortium is currently in the process of overhauling our permissions
as well, using yall as a base.
After looking over it, I wonder if the UPDATE_COPY permission might the the
culprit here. It is the only permission in the Circulator group that looks
like it may be the cause
Thank you both. This has given us more to talk about and consider.
Elizabeth
From: Open-ils-general
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Aubrey
Area Library
Sent: Tuesday, November 19, 2019 12:29 PM
To: Evergreen Discussion Group
Subject: Re:
Hi all,
I wanted to ask for feedback on an issue we recently uncovered. We recently
upgraded from Evergreen 3.1 to 3.3 and implemented a complete revamp of our
permission structure to include a strict requirement that anyone who
creates/deletes items or bibs must pass cataloging assessments.
We also implemented auto renew in late February this year (we are also the
other library Geoff mentioned). It was a little rocky at first, being the
test library for implementation, but once we worked out the kinks it has
been smooth sailing.
Overall patrons have been very happy with it though we
Hi All,
As one half of the Evergreen 3.5 Co-RM team (along with Chris Sharp), I'd
like to kick off the new release cycle with a call for 3.5 roadmap
entries. We have started a roadmap page here:
https://wiki.evergreen-ils.org/doku.php?id=faqs:evergreen_roadmap:3.5
If you are working on a
I would like to add that if you currently send out pre-due notices that it’s
probably ideal to stop those as the auto-renew notifications serve the same
purpose in general. Jordan touched on that briefly there, but it was something
we dealt with as well and I wanted to state it outright since
Thanks Bill!
For the Feb Feedback fest, I propose Feb 17-21.
For Bug Squashing, I propose March 16-20.
(I am available to help those two weeks!)
Terran McCanna, PINES Program Manager
--
Georgia Public Library Service | University System of Georgia
2872 Woodcock
