[Bug 26295] New: Merge bib records - rebuild Zebra
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26295 Bug ID: 26295 Summary: Merge bib records - rebuild Zebra Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs@lists.koha-community.org Reporter: fiona.borthwick@ptfs-europe.com QA Contact: testopia@bugs.koha-community.org https://koha-community.org/manual//20.11/en/html/cataloging.html#merging-rec... There is a paragraph that reads: "Important It is important to rebuild your zebra index immediately after merging records. If a search is performed for a record which has been deleted Koha will present the patrons with an error in the OPAC." One of our customers queried this as obviously having to rebuild the zebra index following one simple merge is not very efficient. It would appear that standard indexing deals with the merged records as standard now. A catalogue search on the terms in question (to locate the two records) will now only find the master record following the merge and there is no retrieval of the second record that has been merged. If a rebuild is no longer required, then it might be a good idea to remove this warning from the manual? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26295 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |Manual --- Comment #1 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- I believe this might have been badly phrased not meaning "full reindex", but the normal incremental one. And maybe dating back to times where this was not done by the indexer (almost immediately), but could take up to a view minutes? I think I'd just delete the part about the importance of indexing - every change requires an index to take effect in search and deleting of records is not different to a merge... pointing it out here explicitly doesn't seem necessary. What do you think? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26295 --- Comment #2 from Fiona Borthwick <fiona.borthwick@ptfs-europe.com> --- (In reply to Katrin Fischer from comment #1)
I believe this might have been badly phrased not meaning "full reindex", but the normal incremental one. And maybe dating back to times where this was not done by the indexer (almost immediately), but could take up to a view minutes?
I think I'd just delete the part about the importance of indexing - every change requires an index to take effect in search and deleting of records is not different to a merge... pointing it out here explicitly doesn't seem necessary. What do you think?
I agree Katrin! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26295 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|NEW |RESOLVED Assignee|koha-bugs@lists.koha-commun |katrin.fischer@bsz-bw.de |ity.org | --- Comment #3 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- I've submitted a merge request to the manual for this change. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26295 --- Comment #4 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- https://gitlab.com/koha-community/koha-manual/-/merge_requests/387 -- You are receiving this mail because: You are watching all bug changes.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org