[Koha-bugs] [Bug 10382] collection not returning to null when removed from course reserves

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Tue Oct 9 16:37:31 CEST 2018


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

--- Comment #77 from Christopher Brannon <cbrannon at cdalibrary.org> ---
(In reply to Marcel de Rooy from comment #76)
> (In reply to Christopher Brannon from comment #74)
> > It should be returned to the exact state it was originally.  It should not
> > be modified in any way by this module when inactive.  If it was null before,
> > is should be returned to null.  If it was a blank entry, it should be
> > returned to a blank entry.
> 
> Well, thats a point in my qa comment.
> So theoretically you are right, but pragmatically we could move into the
> right direction with these changes.

Yes, you COULD do that here, but it is not the function of this module to
correct mistakes.  Otherwise, we are opening the door for people to correct
mistakes everywhere else in Koha, and it would be more complicated to track
down where changes are being made.  Those types of issue (blank or null
entries) should be addressed at time of edit.

If it is an issue for course reserves, then we have the option to have course
reserves refuse to touch a record that is incomplete, or give the option to
correct the record manually before adding to course reserves.  In my opinion, I
don't think course reserves should be silently 'fixing' things.

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


More information about the Koha-bugs mailing list