https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31608
Lari Taskula <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #8 from Lari Taskula <[email protected]> --- 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. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
