https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16522
--- Comment #73 from Heather <[email protected]> --- Thank you SO much for all of this, Katrin! I'm going to go ahead and sign off because everything you say makes a lot of sense. Also, I followed the adapted test plan here: > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16522#c39 I imported an analytic record and its parent/host record; the child was linked to the parent (with the generated search using the record number in the $w of the child record to the 001 of the parent record). I deleted the $w from the 773 and the child remained linked to the parent because Koha then used the data in the 773 $t of the child record which retrieved the data in the 245 $a of the parent record. It does this even with the syspref "UseControlNumber" set to "Use" and "EasyAnalyticalRecords" set to "Don't Show." Maybe it shouldn't do this, but I like it--I like the fact that there is a fallback behavior when there is no Control Number (i.e. no $w) to use for searching. (And I will keep arguing that the "In:..." in the OPAC should be moved down to be consistent with other displays, but more folks in the community like it up near the title and author(s), then I'll probably start arguing to move it up there in the staff client!) I think this is a GREAT development, not at all minor, and will be of service to many libraries in getting to their users articles, chapters, papers, songs...all those great things that analytic records are used for. -- You are receiving this mail because: 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/
