https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31744
--- Comment #2 from David Cook <[email protected]> --- This one seems a bit intimidating because there are different modes for the inventory and no one uses the inventory tool that much I think. When you provide barcodes, I think that you end up with an output that is either output to screen or to a CSV output. (This type of inventory can be evaluated against only itself or against "results" which are determined based on the other filters?) But if you don't provide a barcode list, then there is an interactive mode based off the "results" of the filters... and this list fetches all matches into a DataTable. I suppose both modes would be amenable to background processing. In terms of database schema, I think we'd need to store the items in the "results" with a column for problems? Maybe a "batch" table would have some reporting columns for barcodes read and items modified. That's my interpretation at a glance. There might be other scenarios to take into account... -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://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/
