http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8723
--- Comment #3 from Paul Poulain <paul.poul...@biblibre.com> --- (In reply to comment #2) > The problem is that the hold is 'item specific' - not a hold on the next > available and so you end up with an orphaned hold because the reserves table > still has a hold on that itemnumber, but the wrong biblionumber - so if this > instance the hold should be moved to the right biblionumber or the > itemnumber should be removed from the hold and the hold made on the bib > level instead of item specific. That would solve the technical problem. But the library will still have to explain that the user placed a hold on 'the two towers' and get '50 shades of grey'. Well, the use case for moving an item is also that you've duplicate biblio records, so maybe the use case 'I place a hold on the 2 towers and get 50 shades of grey' is rare enough to be managed manually. do you agree ? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
