Authority popup empty in Angular in fields 600 - 651 and 655 in EG 3.7.3 and higher

[Mieke Stroo]

In the traditional view all authorities work perfectly. New authorities can be made and retrieved from a bibliographic record.

In the Angular view most authorities (100, 110, 648, 650, 700, 710, 830) work but not fields 600, 651 and 655-fields. Linking an authority with a 100$a works fine as it shows the authority list in a popup. But linking an authority with a 600$a field (or 651 or 655) shows an empty authority list in the popup.

This issue already existed already in Evergreen 3.73. I noticed it in Evergreen 3.10

We're on EG 3.10 and use Chrome as our browser
OpenSRF 3.2.2 op Ubuntu 20.04.5 LTS
OpenILS 3.10.0 op Ubuntu 20.04.5 LTS
PostreSQL Ubuntu 10.23-1.pgdg20.04+1

[Carol Witt (carolwitt)]

I tested this in Angular on our development server (3.10) with the same results as Mieke, even when it's an identical name in the 100, 600, and 700 fields. I can create new authority records in the affected fields, but their authority lists will still be empty after that.

I then tested it in Angular on our live server (3.7.3) and it happened there too, so it doesn't seem to be a new issue. The authority lists appeared as expected when using the traditional catalogue on both servers. We're also using Chrome.

[Galen Charlton (gmc)]

A patch is available in user/gmcharlt/lp2007351_fix_heading_linking_in_cat_editor / https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/gmcharlt/lp2007351_fix_heading_linking_in_cat_editor

[Beth Willis (willis-a)]

I first looked at this bug on our production (EG 3.7.2) and test (EG 3.9.1) servers to familiarize myself with the issue. I saw what both Mieke and Carol reported. I tested the fix on the Mobius server.

I imported a new record (#353) that includes both a 100 and a 600 field. In the MARC edit screen, I chose to create an authority link from the 100 field. A list of potential authority record matches displayed as expected. The same was true when creating an authority link from the 600 field.

Please see attached screenshot (prince_600_mobius.png).

I also chose to create authority links from the 655 field in a different bib record (#77) and a list of potential authority record matches displayed in this case, as well.

Please see attached screenshot (sibelius_655_mobius.png).

Unless I have misunderstood the initial bug report, this fix appears to work great. Do either of the original posters have additional comments?

[Beth Willis (willis-a)]

Added second screenshot.

[Carol Witt (carolwitt)]

Hi Beth,

Thanks for testing it. I've just tested it on Mobius and it resolved all of the issues I had found.

I have tested this code and consent to signing off on it with my name, Carol Witt and my email address, <email address hidden>.

[Galen Charlton (gmc)]

Pushed down to rel_3_9. Thanks, Beth and Carol!

[Mieke Stroo (mst-iisg)]

It seems that this patch disturbed the working of the 648-field. It worked perfectly before the patch was added. Now it has the same issue as the above mentioned fields in this bug report.

This is a screenshot from our log:

open-ils.pcrud 2023-03-20 11:26:02 [INFO:1712602:osrf_application.c:1075:16793079628061820] CALL: open-ils.pcrud open-ils.pcrud.search.acsbf.atomic "ANONYMOUS",{"tag":"648","authority_field":{"in":{"select":{"acsaf":["id"]},"from":"acsaf","where":{"heading_field":{"!=":null}}}}},{"flesh":1,"flesh_fields":{"acsbf":["authority_field"]}}

[Galen Charlton (gmc)]

Mieke: confirmed. I've tracked down the cause and opened a separate bug for the underlying issue: bug 2013102