On the items table of the bibliographic record there are different behaviour conflicting with each others. First you have the admin settings that gives you the default visibility. Then you have the "hide the column if no data to display" behaviour, and finally you have the state that is saved. When visibility changes, the state changed and is saved for the next time. So, when you come back, what to do? Restore from the state but hide empty columns. But... you cannot know if the column has been hidden from the user or if the column was empty I guess we need an additional layer, and store the user's preference in a separate localStorage item, then merge and then hide if empty but it's getting complicated, for a single table, especially when I am trying to standardize our DT uses.
What do we do? One solution would be to prevent the state to be restored for this table and disable the option from the admin config page.
We also need to fix bug 38391 here.
*** This bug has been marked as a duplicate of bug 38436 ***
Won't actually be fixed on bug 38433.
On that note, as I understand this behavior hasn't been changed so far yet: > Then you have the "hide the column if no data to display" behaviour It would be nice if this was re-computed on every page change too. It's a bit confusing if going to page 2, and certain non-empty columns now remain hidden, because they keep the initial empty column hiding settings from page 1, I know this has confused some users. And currently the only dirty workaround is to increase how many items are loaded at once and cross fingers that all the used columns won't happen to be empty on page 1 then... But there are very often cases where just a single item would have some column populated in a very long item list, for one reason or another. And that fact would remain completely concealed to the librarian in the default view, even though it's visible in OPAC unbeknownst to them... If column visibility changing logic is to be re-coded in a more smart fashion, it would be very nice to fix that thing as well at the same time.
(In reply to Michał from comment #5) > On that note, as I understand this behavior hasn't been changed so far yet: > > > Then you have the "hide the column if no data to display" behaviour > > It would be nice if this was re-computed on every page change too. > > It's a bit confusing if going to page 2, and certain non-empty columns now > remain hidden, because they keep the initial empty column hiding settings > from page 1, I know this has confused some users. > > And currently the only dirty workaround is to increase how many items are > loaded at once and cross fingers that all the used columns won't happen to > be empty on page 1 then... But there are very often cases where just a > single item would have some column populated in a very long item list, for > one reason or another. And that fact would remain completely concealed to > the librarian in the default view, even though it's visible in OPAC > unbeknownst to them... > > If column visibility changing logic is to be re-coded in a more smart > fashion, it would be very nice to fix that thing as well at the same time. This will be fixed on 24.11.
Note that bug 38485 is now "storing" user preferences to have a consistent behaviour when pagination is used.