https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43894
Bug ID: 43894
Summary: AddIssue stores UpdateNotForLoanStatusOnCheckout after
enqueuing the record reindex
Initiative type: ---
Sponsorship ---
status:
Product: Koha
Version: Main
Hardware: All
OS: All
Status: NEW
Severity: minor
Priority: P5 - low
Component: Circulation
Assignee: [email protected]
Reporter: [email protected]
QA Contact: [email protected]
CC: [email protected], [email protected]
Target Milestone: ---
When an item is checked out, AddIssue stores the item (onloan,
holdingbranch, issues...) without skip_record_index, which enqueues the
reindex of the bibliographic record. Later in the same function, it
applies UpdateNotForLoanStatusOnCheckout with a second store, this time
with skip_record_index => 1.
If the indexing daemon (es_indexer_daemon.pl) processes the job between
the two stores, the record is indexed with the old notforloan value and
nothing reindexes it again. For example, with
UpdateNotForLoanStatusOnCheckout set to "-1: 0", an item that was
"Ordered" can keep being shown as "Ordered" in the search results after
the checkout. The window is small (both stores happen in the same
request), but it exists, and the item is written twice.
Nothing between the two stores reads notforloan, so the rule can be
applied to the item object before the first store, and a single store
writes everything. The holds queue is not affected: the second store
was the only one updating it, but AddIssue already enqueues the holds
queue update at the end when RealTimeHoldsQueue is enabled.
--
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.
_______________________________________________
Koha-bugs mailing list -- [email protected]
To unsubscribe send an email to [email protected]
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
