As we add more options to item search the output gets more crowded. Adding column configuration would let the library choose to hide some of the columns in item search results.
Question: Should this make the "Export results to CSV" option obsolete? The "Export results to CSV" button automatically exports all results. The DataTables export button exports only visible results.
I think exporting all results on demand is nice and removing it without replacement might be seen as a regression :( If we can't achieve this with the datatables, maybe we should relabel the current option and still offer it?
This has proved to be more difficult than I anticipated. The item search results table has column filters in the header, added via the jquery.dataTables.columnFilter.js plugin. As far as I can tell this plugin uses the index of the column to define the scope of the search. It looks like hiding columns changes the structure of the table in a way that the plugin can't keep track of which column is which.
I don't know where this plugin came from... I've found older versions online, and slighly newer forks, but nothing up to date with the latest DataTables. I haven't dug into the plugin's code, so I don't know how difficult it would be to address the column index problem.
(In reply to Owen Leonard from comment #0)
> Question: Should this make the "Export results to CSV" option obsolete? The
> "Export results to CSV" button automatically exports all results. The
> DataTables export button exports only visible results.
A lot of our librarians use this to manage the collections.
Showing all results before exporting may take a long time and end in timeout.
*** Bug 27156 has been marked as a duplicate of this bug. ***