We’ve recently had some fresh interest in the project, so I thought I’d take a look at the recent data.
We used and extended CaPRéT as one of two strands of work in the Track OER project. We experimented with Piwik and Google Analytics as alternative analytics back-ends, in place of the custom Node.js/ MongoDB/ Hummingbird one originally developed for CaPReT. This was because:
- The Open University staff who needed and wanted access to the analytics data were (are) already more familiar with Google Analytics;
- Piwik, written in PHP with MySQL is easier to install and maintain by developers at The OU (including myself) –- this was important given the short time-frame of the project;
- Piwik and Google Analytics are more flexible –- we could use them for the CaPReT strand, and the other strand in Track OER – tracking downloads;
You can see the CaPReT-Google Analytics side-block on the bottom-left in the Bridge to Success OER content on The Open University’s LabSpace site.
We use Google Analytics event tracking, and GA custom reports –- see “Useful links”
One year on, Google Analytics is still busily collecting data…
- 294 “copy” events across the Bridge to Success content on LabSpace this month (19 October to 18 November 2013);
- 1,937 “copy” events across B2S during the past 15 months (1 September 2012 to 18 November 2013);
- In the past month, there have been copy events from the Argentina, Armenia and Australia, through Ethiopia, India and Indonesia, to the United Arab Emirates, the UK, USA, Vietnam and Zimbabwe –- every continent appears to be represented, except Antarctica(!);
- We/ Google Analytics can’t always identify the institution that “copy” events came from, but some that we can identify are: “abu dhabi company for onshore oil operations”, “Adithya Inst. of Technology”, “cape peninsula university of technology”, “new brunswick department of education”, “rutgers university” and “university of durham”.
Additional screenshots are in this Google Doc (temporary measure – should be in Flickr or similar…).
You can find more background information on the Track OER project blog, on Cloudworks.
Developers can browse and fork the open source code on GitHub.