http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6610
Ian Walls <koha.sek...@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |In Discussion CC| |koha.sek...@gmail.com --- Comment #12 from Ian Walls <koha.sek...@gmail.com> --- Further complications: it can never be as simple as just inserting an ID into a syspref. First off, we'd have to have a syspref for each analytics tool we want to support, which would probably just be GA and Piwik to start. Not only would we need to record the ID, but both of these tools also have provisioning for Domains within the code (so you could track opac.library.tld and staff.library.tld on the same code, but with divisions in reporting). Addtionally, for GA, you need to manually specify your particular regional server, so that would either require complicated SWITCH statements, or another syspref. Both tools also allow for Javascript event recording, so we could record how many items are added to the Cart (as well as which ones they are, etc). The syntax to do this is different for each tool, and would again need to be coded up. We've have to decide on schema for how the data is collected, and probably add a series of sysprefs to govern various choices. I think the best way to handle this, really, is just continue to allow a block of arbitrary HTML to be placed in the OPAC or staff client, and let users copy/paste the code provided by their analytics tool of choice. We wouldn't get JS event recording this way, but it'd be the least invasive and complicated. -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org http://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/