Since bug 37238 brought item search into table settings, it would be great to flesh out some of the other item data fields like lost_on, damaged_on, or withdrawn_on. Because it is now a configurable table, libraries would be able to hide or expand those columns as needed.
The three fields you mention are all datetimes rather than just dates and most of the options here are just checking = / !=. That seems like it will confuse people -- they'll search for itemlost_on='2024-12-11' and not find anything because the actual value is '2024-12-11 14:39:24.' We could add a hint here that suggests one might want to use % after a date. Or we could make the search just compare to the date alone, ignoring the time. The former seems more accurate. The latter seems more friendly to a novice user. Thoughts?
I did ponder the complication of the datetime issue. Which is to say - I initially thought of it as simply adding the columns to the display without making it a search parameter for that reason. But to be added as a search parameter, I think only searching the date would be the most librarian-friendly, with folks who need more granularity there able to do so from report.
(In reply to hebah from comment #2) > I did ponder the complication of the datetime issue. > > Which is to say - I initially thought of it as simply adding the columns to > the display without making it a search parameter for that reason. > > But to be added as a search parameter, I think only searching the date would > be the most librarian-friendly, with folks who need more granularity there > able to do so from report. Oh! I misunderstood your request; lemme look at getting those columns available in results.
If we just want this in the results table, awesome. I do think it would be beneficial to be able to search ON those fields also, like datelastborrowed currently. I filed this: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38681 I think having a datepicker is nicer for staff and also make it easier to deal with datetime.
On further thought, though it wasn't the original scope of my idea, I do think searching by lost_on etc would be helpful - a common library workflow is to review items lost longer than X time, and with batch modification from item search now, it would be fab to be able to find these really old lost items and batch end checkouts/withdraw etc.
*** This bug has been marked as a duplicate of bug 38331 ***