https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31608 Caroline Cyr La Rose <caroline.cyr-la-rose@inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |11175 See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=30327 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11175 [Bug 11175] Show the parent record's component parts in the detailed views -- 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=31608 --- Comment #2 from Caroline Cyr La Rose <caroline.cyr-la-rose@inlibro.com> --- (In reply to Katrin Fischer from comment #1)

Hi Caroline, same issue with Elasticsearch/Zebra?

I did this with ES on my local installation and with Zebra on a BW sandbox. -- 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=31608 Magnus Enger <magnus@libriotech.no> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|enhancement |normal CC| |magnus@libriotech.no --- Comment #4 from Magnus Enger <magnus@libriotech.no> --- So the question then is perhaps if this was never implemented with UseControlNumber, or if it was implemented and some bug snuck in and made it not work any more? In t/db_dependent/Koha/Biblio.t there is a set of subtests labeled "get_components_query", which seems to be testing with UseControlNumber both off and on. And the tests pass. The original bug 11175 has this patch: https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=126882 "Taking the code in bug 15851 as inspiration this patch also adds proper handling for UseControlNumber vs EasyAnalytics style 773 linking and ensures we only return analytic component parts and no other records containing 773's." Sounds to me like it should work. I'm changing this from "enh" to "normal bug". -- 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=31608 Esther Melander <esther.melander@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |esther.melander@bywatersolu | |tions.com --- Comment #6 from Esther Melander <esther.melander@bywatersolutions.com> --- ShowComponentRecords appeared to be working in 23.05 but does not seem to be working in 23.11. To replicate: 1. Ensure the 773 tag is available in the framework. 2. Ensure the system preference EasyAnalyticalRecords is set to don't show 3. Ensure UseControlNumber is set to use. 4. Configure ShowComponentRecords for staff interface 4. Add a serial record, ensure the Leader space 7 is a serial. 5. From the new serial record, Edit - Add new child record. 6. Add the child record and ensure the 773 $w has the 001 control number from the host/parent record. Also ensure the Leader space 7 is a serial component part. 7. Add another child record. The child record should have an "In: Serial Title" link in the bibliographic record detail view. Click on this link to return to the parent record. See that the Component tab is missing from the holdings table of the parent record. -- 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=31608 Lari Taskula <lari.taskula@hypernova.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lari.taskula@hypernova.fi --- Comment #8 from Lari Taskula <lari.taskula@hypernova.fi> --- It works in 24.05 and Elasticsearch. First off, when UseControlNumber is enabled and host record has both 001 and 003 filled in, the component records are loaded into the host record by the following search query: (((rcn:"Host001" AND cni:"Host003") OR rcn:"Host003 Host001") AND (bib-level:a OR bib-level:b)) For example: (((rcn:"011193623" AND cni:"FI-MELINDA") OR rcn:"FI-MELINDA 011193623") AND (bib-level:a OR bib-level:b)) If you are having problems displaying the component records with UseControlNumber and ShowComponentRecords on, try narrowing down the problem by first searching: ((rcn:"Host001" AND cni:"Host003") OR rcn:"Host003 Host001") (fill in Host001 and Host003 values) If you get no results, then it could be that the child 773$w != host 001 or child 003 != host 003. If they are correct and you still get no results with the narrowed down query, check your Elastic mappings for rcn and cni. On the other hand if you do get the component records as results, then your child's leader character position 7 is not really "a" or "b". Leader's pop-up editor can be misleading when viewing the values. To reproduce: 1. Click "New child record" from the host 2. Fill in other mandatory fields but do not touch the leader 3. Save the child record 4. Edit the child record 5. Edit the leader 6. Observe 7- Bibliographic level shown as "a" 7. Close leader (do not save) editor pop-up 8. Count leader characters manually until position 7 (starting from 0) 9. Observe it being empty! This can be very misleading and is caused by "a" being the default select option. So you always have to edit the leader manually for it to work, or use a different MARC framework with default values for component records. Enhancement: Could "New child record" button automatically populate char position 7 of the child to avoid this problem? In fact I assumed this was already the case but it seems it is not. Checklist: - UseControlNumber ON - ShowComponentRecords ON - Make sure rcn (record-control-number => 773w) and cni (control-number-identifier 003) are mapped in Elastic mappings (bibliographic records tab) - Host 001 and child 773$w are equal - Host 003 and child 003 are equal - Child's leader character position 7 is truly "a" or "b" (count character positions manually - do not trust the editor's drop-down value). Keeping these things in mind it should work in 24.05. -- 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=31608 Lucas Gass (lukeg) <lucas@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lucas@bywatersolutions.com -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31608 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |rel_24_11_candidate --- Comment #10 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Hm, indeed I can't get this to work with Zebra in 24.11 with UseControlNumber ON. If UseControlNumber is turned off, it works. 003 match. 773 and 001 match. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.