[Koha-bugs] [Bug 32916] [Bug 30280 follow-up] Problems in linking authorities to biblio fields (MARC 21)

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Wed Mar 8 19:09:23 CET 2023


https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32916

--- Comment #9 from Frank Hansen <frank.hansen at ub.lu.se> ---
> 
> OK, I have tried your new proposal (BTW, there are two versions in the
> comment https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32916#c7 ?
> I was able to apply only the first one).  I seems that it does not change
> much -- from my supplied test set only the three '[Ff]eminism' and 'Subject
> lcsh' are linked correctly, and only under ES.  Nothing under Zebra and also
> under Elastic the rest of headings remains unlinked.  So -- no visible
> change.
> 
> I fully understand the need to distinguish between thesauri while linking
> but we should not fix one thing and at the same time make other aspects not
> function.
> 
> Earlier, under Zebra, there was no functionality to distinguish the thesauri
> nor other aspects of authority 008 field while linking therefor it should be
> fixed as well.
> 
> And we cannot assume not force users to use 008/11 ='a' for authorities
> intended for biblio fields =! 6XX -- especially when 008/15 = 'b', 008/11
> does not play any role.
> 
> Have you tested my second proposal?  Didn't it work for you?

Yes, I tested the second proposal on my testing docker. After adding the
syspref it worked in ElasticSearch. I also tried it with Zebra but
unfortunately I didn't succeed. But when i ran link_bibs_to_authorities.pl I
got those "oAuth error: Unsupported Use attribute (114)
Subject-heading-thesaurus Bib-1". I haven't had time do dig deeper into that. I
also have a kohadevbox available for testing. And I would like to test it on
the kohadevbox as well.

Regards,
Frank Hansen

-- 
You are receiving this mail because:
You are watching all bug changes.


More information about the Koha-bugs mailing list