https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15851
Katrin Fischer <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|"Analytics: Show analytics" |"Analytics: Show analytics" |showing regardless of |showing regardless of |whether they have |whether they have analytics |analytics. | --- Comment #27 from Katrin Fischer <[email protected]> --- Trying to summarize and epxlain... sorry it got long: I think we need to be careful here in general as we have multiple ways of handling analytics in Koha right now, that cannot be mixed (afaik). The best write-up about this we have is: https://wiki.koha-community.org/wiki/Multipart_Bibliographics 1) Links between records using $w (7xx $w => 001) The links here are only on record level. There is no effect on item visibility. 2) Links between records and items using EasyAnalytics feature (773 => $9 $0 $w) $0 = biblionumber of parent record ยง9 = itemnumber of parent item $w = (003)001 of parent record The links here involve records and items. One existing physical item can be displayed on multiple records. This makes it really interesting for bound items. I've not been able to use this feature in our union catalog setting as it adds 773 entries to the records and we'd kill them with our regular updates :( -- Joubu's attached patch suggests using the analytics_flag, but this will only give results for 2) and never display the link for libraries using 1). You can also see here, that it relies on an itemnumber. The link here is more between a host item and related records, than between records. opac-detail.pl: my $countanalytics = C4::Context->preference('EasyAnalyticalRecords') ? GetAnalyticsCount($item->{itemnumber}) : 0; if ($countanalytics > 0){ $analytics_flag=1; $item->{countanalytics} = $countanalytics; } Maybe we could improve Joubu's patch by also checking the EasyAnalyticalRecords pref - then it could work for case 2). To my knowledge there were issues using 1) and 2) together - maybe libraries can tell if that's still the case (or testing could). The wiki lists UseControlNumbers and EasyAnalyticalRecords as mutually exclusive. What Hugo suggests could work, if I understand correctly, it would do about this: - Find all records with 773 - Look for matching linked records using the available standard identifiers: - If EasyAnalyticalrecords is used: - $9 = biblionumber - $0 = itemnumber - Also: - $w = 001 Control number - $x = 020 ISBN - $z = 022 ISSN Deduplicate bilbionumbers and add their count (or maybe the full relationship information? 773, host biblionumber, linked biblionumber) to a table. Then we could look up that information and push it to the XML like Joubus patch does with the flag. Even more: We could show the exact number of linked records. I'd like to make following suggestions: - Use a separate table for storing information about record relationships (count of records linked) - Make it generic enough it could be expanded for other relationships beyond 773 (volumes in a set, volumnes in a series.. etc.) - Have a way to update the counter when adding/deleting/editing a record in the GUI. People might get irritated if the link doesn't show when saving their records. - Give the script the option to run incrementally, either for all records stored in a database (starting out) or only looking at records added or changed since x. ago. It could be too 'expensive' to fully run it on a big database over and over. -- 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/
