[Koha-bugs] [Bug 30106] New: Items silently moved to serial record without updating search index
bugzilla-daemon at bugs.koha-community.org
bugzilla-daemon at bugs.koha-community.org
Tue Feb 15 10:39:38 CET 2022
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30106
Bug ID: 30106
Summary: Items silently moved to serial record without updating
search index
Change sponsored?: ---
Product: Koha
Version: master
Hardware: All
OS: All
Status: NEW
Severity: major
Priority: P5 - low
Component: Serials
Assignee: koha-bugs at lists.koha-community.org
Reporter: katrin.fischer at bsz-bw.de
QA Contact: testopia at bugs.koha-community.org
This is quite a confusing bug:
1) Create a serial description with 'create items on receive'
2) Receive multiple issues and add items with barcodes
3) Verify your items show on the detail page of you serial record.
4) In a new tab, search for another record.
5) Attach one of your items to this record.
6) Both detail pages and result lists should reflect the change correctly.
7) Go to your subscription and switch to the "Serial collection" page
8) Make sure that the issue for your reattached item is "checked" in the list
9) Click Edit serials
10) Receive the newest issue, leave your old issue unchanged
Now the surprise:
11) Check the detail pages of both your records:
The item has been reattached to the original record.
12) Verify via zebraqueue table and result list that the index has not been
updated. The result list still shows the item on the second record.
Problem:
* There should be no silently wandering items...?
* The index is out of sync causing additional confusion.
Use case:
In some cases serials that have volumes with unique titles (yearbooks are an
example) will be catalogued with separate records for the volumes according to
German cataloguing rules. So wanting to reattach the item created for the
serial to the volume record created after the item was received is a common use
case.
--
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.
More information about the Koha-bugs
mailing list