LOVD 2.0

Welcome to the LOVD 2.0 bug tracking system. Please note that this bug tracking system is not for LOVD 3.0!

If you have any issues, please read the documentation and Frequently Asked Questions.
Please note that you need to register before you can submit bugs or feature requests.

Information By default, all closed tasks are hidden from view.
Click here to see all tasks.

Tasklist

FS#52 - Support for Google Analytics

Attached to Project: LOVD 2.0
Opened by Raymond Dalgleish (rwmd) - Thursday, 06 October 2011, 16:07 GMT+1
Last edited by Ivo F.A.C. Fokkema (ifokkema) - Tuesday, 18 October 2011, 15:14 GMT+1
Task Type Feature Request
Category Backend / Core → Config area
Status Delayed until 3.0
Assigned To Ivo F.A.C. Fokkema (ifokkema)
Operating System All
Severity Low
Priority Normal
Reported Version 2.0-33
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

I use Google Analytics to track hits to my two LOVD installations. I do this by embedding the tracking code into the bottom of the file inc-bot.php. It's not an ideal solution because any change to inc-bot.php in future builds will mean having to edit the tracking code back into the file again. Indeed, there might be a better file into which to paste the code, but the present solution does work. In addition, my solution is feasible only because I host the two installations on my own server and can edit the inc-bot.php file. Curators whose sites are hosted at LUMC do not (presumably) have this luxury.

Would it be possible to provide direct support for Google Analytics by providing a box into which the tracking code could be pasted by the database curator. Some thought might need to be given for the situation where a single shared-installation hosts genes which need to be tracked individually because these genes belong to different curators. A single-installation wide solution is not the answer, but neither is one which does it gene by gene.
This task depends upon

Comment by Ivo F.A.C. Fokkema (ifokkema) - Monday, 10 October 2011, 10:32 GMT+1
Thank you for your suggestion. If a curator has to have access to this feature, the only solution for them would be tracking by gene. Anyway tracking by gene in LOVD 2.0 is easier than in LOVD 3.0, which includes patient views, screening views, genomic variant views, all independent of genes. By gene tracking is easy to activate in LOVD 2.0: just fill in the necessary javascript code in the page header or footer of your gene database.
We have been planning hit counters for a while now, both system wide and by gene, available for all logged in users, but I'm wondering what kind of features you are looking for? We have of course no plans to duplicate a system like Google Analytics.
Comment by Raymond Dalgleish (rwmd) - Friday, 14 October 2011, 18:24 GMT+1
Many thanks for the suggestion about embedding the necessary javascript code in the page header or footer. That would certainly avoid the problem of the possibility of inc-bot.php being updated in future builds. In addition, I can have tracking on a gene by gene-by-gene basis by modifying the headers for each gene with customised javascript tracking code.

I think that building hit counters into LOVD may be a waste of effort. Google Analytics does the job already and in a sophisticated manner. It would be better to provide support for Google Analytics, rather than trying to re-invent the wheel.
Comment by Ivo F.A.C. Fokkema (ifokkema) - Tuesday, 18 October 2011, 15:06 GMT+1
I have copied the feature request to the LOVD 3.0 BTS:
https://humgenprojects.lumc.nl/trac/LOVD3/ticket/2

Loading...