Bug 32940

Summary: [Bug 30280 follow-up] Subject-heading-thesaurus-conventions search field missing in Zebra
Product: Koha Reporter: Janusz Kaczmarek <januszop>
Component: MARC Authority data supportAssignee: Bugs List <koha-bugs>
Status: NEW --- QA Contact: Testopia <testopia>
Severity: major    
Priority: P2 CC: frank.hansen
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 Janusz Kaczmarek 2023-02-10 13:22:06 UTC
In the bug 30280 a new searchfield Subject-heading-thesaurus-conventions has been introduced for ElasticSearch (indexing 040 $f of an authority record).  This searchfield is used in C4::Heading::_search with an alias thesaurus-conventions (introduced with the same bug and defined only in Koha/SearchEngine/Elasticsearch/QueryBuilder.pm).

At the same time, neither Subject-heading-thesaurus-conventions nor thesaurus-conventions are defined for Zebra.  As a result, while performing a linking (with link_bibs_to_authorities.pl for instance) of a biblio 6XX field with 2nd indicator == 7 and proper $2 (e.g. 650 _7 $a Ekonomia $2 DBN) with Zebra engine we get:

error: Unsupported Use attribute (114) thesaurus-conventions Bib-1

On the other hand, according to the stable Zebra configuration (for 15 years or so) Koha inserts 040 $f into the Subject-heading-thesaurus index, as goes there 008/11 byte, transformed in the following way:

a => lcsh
b => lcac
c => mesh
d => nal
k => cash
n => notapplicable
r => aat
s => sears
v => rvm

So, maybe ES should go the same way?  If for some reasons no, the Koha part should be modified accordingly.

It seems that changes made in Koha in favour of the ES should always be very carefully checked in Zebra context... Now the linking feature in Zebra does not work in most cases (also described in the bug 32916).

Seeing the comment at https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30280#c58, I understand that the enhancement is still not mature enough. So, I am wondering that it has been accepted in the released version (22.11.00)... Was this not by mistake?