https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32019 Nick Clemens <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Signed Off --- Comment #7 from Nick Clemens <nick@bywatersolutions.com> --- (In reply to Katrin Fischer from comment #6)
Sorry, ending up with some questions here:
0) Terminology
I have several terminology issues here in the GUI, but also in the code, we are still horribly inconsistent all over. Please update at least the note on the form and use . for ending sentences :)
What statuses would remain untouched? It's used several times as an explanation, but I am not sure what is meant actually.
I added some explanation and added periods - it is wierd here because we are not really doing a normal check in - we are just moving the item to old issues. By not affecting statuses I mean that normal check in things won't happen - we don't see if check in is allowed, we don't update fines, we don't change shelving location or holding branch
1) I assume we skip here, because they will be re-indexed when the job is processed later on?
+ skip_record_index => 1, + skip_holds_queue => 1,
If we don't update the index, the item would still show as checked out in the result list.
The reindex happens to all items affected by batch mod in a single operation at the end
2) Options on the form are misaligned in the form in the new staff interface design.
Should be improved
3) Why the empty setting? Wouldn't it make sense to preset to 'No'?
Ok
4) You said this is to allow the library to delete the item.
"Eventually, after the patron has paid, or after some time, the library may wish to delete the item. When doing so, they do not wish to check the item in and affect any statuses"
Why not add this option to the item batch delete form then?
While that is one use, I don't think it is the only use - some libraries simply want the option to get these items off a patrons account without triggering all the things a check in does. If a library chooses not to 'MarkLostItemsReturned' they have no way to recreate that action later. This is to fill that gap -- You are receiving this mail because: You are watching all bug changes.