Bug 41874 - Display the label and not the code of the value if a subfield is controlled by an authorized value
Summary: Display the label and not the code of the value if a subfield is controlled b...
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-02-18 12:54 UTC by Mathieu Saby
Modified: 2026-02-20 12:54 UTC (History)
1 user (show)

See Also:
GIT URL:
Initiative type: ---
Sponsorship status: ---
Comma delimited list of Sponsors:
Crowdfunding goal: 0
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mathieu Saby 2026-02-18 12:54:00 UTC
If a MARC subfield is controlled by an authorized value in the cataloging framework, Koha displays the code of the authorized value and not its label, except for certain specific fields (libraries, locations, etc.).

Koha should systematically display the label and not the code of the value.
Comment 1 Katrin Fischer 2026-02-18 15:36:38 UTC
Can you detail which pages/places you mean?

For example in the XSLT driven views in OPAC and staff the label will display (or at least it should if nothing was broken)

Same for the cataloguing form of the normal editor, where it shoudl display a pull down and the label as well.
Comment 2 Mathieu Saby 2026-02-19 14:05:11 UTC
I should have been more specific : our use case was a item field, to be displayed in the holding table under the record.
Let's say we want to use an authorized value to control the value of "internal note". In the framework for the 995 field (in Unimarc) we can tell that the subfield ($z) must use an authorized value, but in the holding table only the code will be displayed.
Comment 3 Katrin Fischer 2026-02-20 12:54:38 UTC
OK, I'd suggest making a file specific for this or at least for "item fields linked to authorised values". It will require template changes in lots of places probably to make it work.