| Summary: | Display the label and not the code of the value if a subfield is controlled by an authorized value | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Mathieu Saby <mathsabypro> |
| Component: | Cataloging | Assignee: | Bugs List <koha-bugs> |
| Status: | NEW --- | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | m.de.rooy |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| 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: | |||
|
Description
Mathieu Saby
2026-02-18 12:54:00 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. 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. 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. |