[Bug 38098] New: Field visibility persists despite unchecking staff interface visibility in framework
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38098 Bug ID: 38098 Summary: Field visibility persists despite unchecking staff interface visibility in framework Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs@lists.koha-community.org Reporter: esther.melander@bywatersolutions.com QA Contact: testopia@bugs.koha-community.org CC: m.de.rooy@rijksmuseum.nl To replicate: 1. Have a sample record that displays the 082 in the staff interface, bibliographic detail view in the default framework. Ensure the record has data in the 082. 2. Edit the default framework and uncheck the box for staff interface visibility in the appropriate subfields. 3. Refresh the bibliographic detail view and see the 082 is still visible in the bibliographic detail view. I think the visibility of this field and many others are controlled by the XSLTDetailsDisplay rather than the visibility settings in the Framework. The XSLT style sheet is not accessible to the end user unless they have backend access. I would expect the visibility settings in the Framework to control the display, as implied by having the option in the first place. It would be much simpler for the end user to be able to adjust visibility in the framework and to have that setting actual do what it says. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38098 Lucas Gass (lukeg) <lucas@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lucas@bywatersolutions.com -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38098 --- Comment #1 from Lucas Gass (lukeg) <lucas@bywatersolutions.com> --- I don't think framework visibility ever intended to show/hide subfields in the OPAC/staff interface detail page. It show shows/hides the field in the MARC view ( OPAC or staff ). I think what we need here is a hint/tooltip to make that clear. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38098 --- Comment #2 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- (In reply to Lucas Gass (lukeg) from comment #1)
I don't think framework visibility ever intended to show/hide subfields in the OPAC/staff interface detail page. It show shows/hides the field in the MARC view ( OPAC or staff ).
I think what we need here is a hint/tooltip to make that clear.
It actually works for the OPAC detail page, have never used it for staff I believe. The fields are filtered from the XSLT (record processor...). It used to be MARC view only, you are right about that. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38098 --- Comment #3 from Lucas Gass (lukeg) <lucas@bywatersolutions.com> --- (In reply to Katrin Fischer from comment #2)
(In reply to Lucas Gass (lukeg) from comment #1)
I don't think framework visibility ever intended to show/hide subfields in the OPAC/staff interface detail page. It show shows/hides the field in the MARC view ( OPAC or staff ).
I think what we need here is a hint/tooltip to make that clear.
It actually works for the OPAC detail page, have never used it for staff I believe. The fields are filtered from the XSLT (record processor...). It used to be MARC view only, you are right about that.
If I added a new arbitrary field to a framework, 952$k for example, and set visibility to 'Staff interface' and 'OPAC' I should expect it to show up in the OPAC/Staff interface detail pages? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38098 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tomascohen@gmail.com --- Comment #4 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- (In reply to Lucas Gass (lukeg) from comment #3)
(In reply to Katrin Fischer from comment #2)
(In reply to Lucas Gass (lukeg) from comment #1)
I don't think framework visibility ever intended to show/hide subfields in the OPAC/staff interface detail page. It show shows/hides the field in the MARC view ( OPAC or staff ).
I think what we need here is a hint/tooltip to make that clear.
It actually works for the OPAC detail page, have never used it for staff I believe. The fields are filtered from the XSLT (record processor...). It used to be MARC view only, you are right about that.
If I added a new arbitrary field to a framework, 952$k for example, and set visibility to 'Staff interface' and 'OPAC' I should expect it to show up in the OPAC/Staff interface detail pages?
Yes and no. 952 is not that arbitrary as it's an item field. There is currently no code for showing these fields in the item/holdings table. But it will show up in the items tab on the MARC view (not the MARC preview in the record, but the tab/separate page). If it was 799 or so, you could expect it to be part of the XSLT send to the template and then you could use it in the XSLT. If you didn't check OPAC visibility, it would not even be part of the XSLT as it would be filtered out before being sent to XSLT for processing. Adding Tomas as I believe he worked on this in the past. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org