[Koha-bugs] [Bug 31256] Circ rules batch modification

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31256

--- Comment #11 from Caroline Cyr La Rose <caroline.cyr-la-rose at inlibro.com> ---
(In reply to Christopher Brannon from comment #10)
> (In reply to Caroline Cyr La Rose from comment #5)
> > Hi all, it's not an overall solution to batch edit rules (I honestly have no
> > idea what that would look like or what it would entail), but a lot of
> > schools might find this plugin useful to change hard due dates in batch
> > https://inlibro.com/en/koha-plugins/#rule-hard-due-date . It's not perfect,
> > as few plugins are imo, but a usable alternative to manually changing hard
> > due dates until it's possible to batch edit rule in the koha interface.
> 
> I just looked at this plugin, and it looks like it will affect ALL branches.
> I am not seeing an option to only make changes to specific branches.  Also,
> it affects items already in circulation.  Again, I don't want to touch stuff
> that was already given a due date.  So, it does not look like we can even
> use this as a work around.

Is it possible we're not talking about the same plugin? I'm talking about the
one called Rule Hard Due Date. (We have another one called Change Due Date that
affects checkouts that we had created before the tool was added to Koha during
the pandemic and that we still keep it around because the one in Koha is
missing some functionality that we had.) I don't want to hijack this bug report
to discuss the plugin, but I can confirm it can only affect specific branches
if you specify the branch in the form (you can specify library, itemtype and/or
patron category and it will only affect the rules that meet those criteria).
And it does not affect current checkouts. 
Our school libraries have been using this for many years, and as far as I know
it meets their need. Feel free to email me or the mailing list to further
discuss the plugin or concerns about it.  :)

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.