The OpacLocationBranchToDisplay system preference essentially serves the purpose of hiding or showing columns in the items table in the record details page on the OPAC, namely the home library column and the current library column. Since we now have Administration > Table settings that we can use to show or hide columns, is this system preference still useful?
I think it is because the location shows below the library on a new line and the pref decides if it shows below the home library or below the current library - so the column settings don't work there. BUT: the pref description is totally wrong at the moment? :(
I just tested it and the preference is about the column display, holdingbranch, homebranch or both. I'll change the bug description, I believe this should be moved into column settings.
(In reply to Katrin Fischer from comment #1) > I think it is because the location shows below the library on a new line and > the pref decides if it shows below the home library or below the current > library - so the column settings don't work there. > You're thinking of OpacLocationOnDetail, which is a different one. :) Currently Administration > Table settings > OPAC > holdingst has the option to show/hide item_current_location (holding library) and item_home_location (home library), but if we try to show/hide on of the columns using table settings, it doesn't change anything. But if we hide both using table settings, it works. To test: 1. Set OpacLocationBranchToDisplay to both home and holding library 2. Go to a bibliographic record with an item in the OPAC --> Both columns should show 3. Go to Administration > Table settings > OPAC > holdingst and check "Is hidden by default" for item_home_location, save 4. Go to the OPAC and refresh the page --> Both columns are still visible 5. Go back to table settings and check also item_current_location (both current and home should now be checked), save 6. Go back to the OPAC and refresh the page --> No columns are visible
If we convert OpacLocationBranchToDisplay to a table setting we should also move the value defined in OPACHoldingsDefaultSortField
(In reply to Owen Leonard from comment #4) > If we convert OpacLocationBranchToDisplay to a table setting we should also > move the value defined in OPACHoldingsDefaultSortField Indeed, that would be logical.