Bug 38742 - C4::AuthoritiesMarc::merge should call ModBiblio only if really needed
Summary: C4::AuthoritiesMarc::merge should call ModBiblio only if really needed
Status: RESOLVED DUPLICATE of bug 34739
Alias: None
Product: Koha
Classification: Unclassified
Component: MARC Authority data support (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low minor
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-12-18 12:40 UTC by Janusz Kaczmarek
Modified: 2024-12-18 18:42 UTC (History)
1 user (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Janusz Kaczmarek 2024-12-18 12:40:42 UTC
Currently, the function C4::AuthoritiesMarc::merge calls ModBiblio for all bibliographic records linked to the modified authority record.  It could seem a just behavior but we know that this could lead to performance problems.  This is why AuthorityMergeLimit systempreference with merge_authorities.pl was introduced (earlier: dontmerge).

Although this partially solves the performance problems, for moderately large and large catalogs (500+ K) and authority records linked with a large number of bibliographic records, performance problems still occur, even with overnight processing with merge_authorities.pl.  This problem is particularly apparent when updating authority records from central databases, whose modifications are beyond our control.

It turns out, however, that many such modifications to authority records involve fields other than the heading field (1XX in MARC 21), so these updates in fact do not modify bibliographic records.  However, with the current merge function, every touch on an authority record forces a call to the ModBiblio function.  The number of relatively expensive ModBiblio calls could be reduced by checking whether there has been an actual change in the field associated with the authority record.

However, with IncludeSeeFromInSearches or IncludeSeeAlsoFromInSearches preferences enabled, the record should be refreshed in the search engine just in case (should the 4XX, 5XX fields have changed, which we don't know at this point).
Comment 1 Phil Ringnalda 2024-12-18 16:17:22 UTC
Bug 34739, no?
Comment 2 Janusz Kaczmarek 2024-12-18 17:34:12 UTC
(In reply to Phil Ringnalda from comment #1)
> Bug 34739, no?

Yes, sounds familiar...
Comment 3 Janusz Kaczmarek 2024-12-18 18:42:26 UTC

*** This bug has been marked as a duplicate of bug 34739 ***