http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7684
--- Comment #64 from Jonathan Druart <[email protected]> --- (In reply to mathieu saby from comment #62) > Same test, but only showing callnumber between 130593/5/1 and 166026/1962/2 > (my callnumber are numeric, sometimes with a slash after the main number) > 0 results > => KO for this kind of callnumbers It is not introduce by this patch, it was the previous behavior. Maybe a fix could be added later. Currently the selection is done with the sql query (itemcallnumber < ? and itemcallnumber > ?) > It looks better than before, but > - why not a column on "withdrawn" status, as it is one of the possible > filters? It could be added later too if needed. > - wot sure the callnumber filter is working well. Bug 9456 introduces a sort on callnumber values, but it is not pushed for now. > Could you remind me when the column "Problem" is supposed to show something? There are 4 possible problems: * wrong place: the item should not have been scanned * missing: if the "compare barcodes list to results" has been checked, the alert is raised if the item does not appear in the results list. * change status: if an item has been scanned with a non-matching notforloan value * not scanned: the opposite of "missing". -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] 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/
