| Summary: | Possibly unreasonable condition for showing "Set" row in biblio marc detail template (checking character in leader field instead of presence of 773 field) | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Michał <schodkowy.omegi-0r> |
| Component: | Templates | Assignee: | Owen Leonard <oleonard> |
| Status: | CLOSED INVALID | QA Contact: | Testopia <testopia> |
| Severity: | minor | ||
| Priority: | P5 - low | ||
| 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
Michał
2023-11-22 08:49:18 UTC
There are different use cases for 773. In this case we are not talking about an article, but about a part/volume record. The 773 in this case doesn't contain $t and we handle it accordingly by using a part of the 245 for display. For an article we create a link with the label In: and check for other markers. The check is there fully intentionally and required. Look for other occurences of 773 for articles. If you records are missing the markers, consider adding them. Koha will work better if your leaders are correct. If this is not an option, adaption the XSLT for your data might be another. You can have your own custom XSLT files. |