Stock authority control set should assert 148/448/548 relationships

Bug #2013102 reported by Galen Charlton
40
This bug affects 8 people
Affects Status Importance Assigned to Milestone
Evergreen
Confirmed
Medium
Unassigned
3.10
New
Undecided
Unassigned
3.11
New
Undecided
Unassigned
3.9
Won't Fix
Medium
Unassigned

Bug Description

For the stock "LoC" control set, the authority.control_set_authority_field table does not assert the relations between the 148/448/548 fields in the authority record and the corresponding "chronological_term" heading types.

With the advent of the patch for bug 2007351, this makes a difference: the Angular bib editor no longer knows how to look up chronological term authority records to link to bib 648 fields.

Quoting Mieke Stroo's comment on that bug:

  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)
Changed in evergreen:
importance: Undecided → Medium
status: New → Confirmed
tags: added: cat-authority
Revision history for this message
Mackenzie Johnson (mtjohnsonupei) wrote :

This is an aside to the issue, but while I recognize the need to ensure any given fresh install of EG asserts these relations by itself, hypothetically speaking I could manually update authority.control_set_authority_field with the appropriate authority.heading_field IDs as a local interim fix, could I not?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.