Summary: | Separate shelving location column in holdings table in staff interface | ||
---|---|---|---|
Product: | Koha | Reporter: | Sara Brown <sbrown> |
Component: | Staff interface | Assignee: | Bugs List <koha-bugs> |
Status: | RESOLVED DUPLICATE | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | andrew, gmcharlt, lucas, marjorie.barry-vila, patrick.robitaille, sbrown, tvandoren |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: |
Description
Sara Brown
2022-03-30 16:35:20 UTC
Because we have Table settings for this particular table I do not think we need another system preference like OpacLocationOnDetail. Both tables have table settings. I think if some libraries want to keep the location as showing below the homebranch, than a syspref would be good. It would also allow us to match the OPAC behavior in staff exactly: - Separate column that can be hidden via table configuration - Location showing below homebranch - Location showing below holdingbranch Can the developers make a column for Shelving location in the Holdings view, so the shelving location doesn’t display under Home library? (In reply to Teresa Van Doren from comment #3) > Can the developers make a column for Shelving location in the Holdings view, > so the shelving location doesn’t display under Home library? It already works for the staff interface, take a look at OpacLocationDetail and Administration > Table configuration. Table settings don't allow for a separate 'Shelving location' column in the staff interface - there isn't an option to select that as its own column. Yes, I changed the bug title to make clear this is about the staff interface. I left the note just in case. (In reply to Andrew Fuerste-Henry from comment #7) > Is this a dupe of bug 15461? I believe you are correct. *** This bug has been marked as a duplicate of bug 15461 *** |