https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33484 --- Comment #125 from Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> --- (In reply to ayoung from comment #123)
Could I get more clarity on why the holdings table was excluded from this new feature? I was excited for this feature specifically because of this table!
I see in the comments that it wasn't possible because of search filters not transferring across bibs correctly...would it be possible to have the option to only save the configuration state and not the search state on page change?
Part of it is also that the holdings table is more complicated than the rest, because it automatically hides a column if there are no visible items that have data in that column. The problem is that the table can't tell the difference between a column that was auto-hidden because it was empty, and a column that you hid on purpose - it just "knows" which columns were hidden and which ones were showing the last time it was used. So, for example, if some of your titles have Materials Specified but many do not, then the Materials Specified column would get secretly hidden when you loaded a title that didn't have Materials Specified, and then it would not show again even when it should unless you noticed it was missing and turned it back on manually. (Or worse, say the first 20 items on a record were missing their call number - then the call number column would get hidden until you noticed it was missing and turned it back on.) I think the long-term goal is to find a way to solve that problem and add the feature back to the item holdings table, but it's tricky and there are a lot of moving pieces, so we had to remove the feature from the item holdings table to avoid secretly hiding columns the user doesn't want hidden in the meantime. -- You are receiving this mail because: You are watching all bug changes.