OLNet+-+BCcampus+Use+Case

= =

back to main page
=Use Case for Tracking Content from BCcampus Contributors=

Content contributors are asked to create and embed license as part of their content creation process. They visit the BC Commons license generator site (http://solr.bccampus.ca/bcc/BCcommons/publish/publish.html) to do so. The license generator will ask as one of the questions if the content owner wishes to receive tracking data of views of the content after it has been downloaded from SOL*R. If they answer yes, in addition to the regular license code that is generated to paste into their documents, the license generator will also paste in a distinct comment to the effect that tracking should be enabled.

Later on, the content contributor deposits this content in SOL*R (http://solr.bccampus.ca:8001/bcc/access/home.do). Based on the unique ID assigned by SOL*R (e.g. 44055c53-85ca-c32f-c67d-5356660a361a) in the contribution process, a script on the server will
 * Search the content in the file store that has been recently added and identify those that have the distinct tracking comment in them
 * Look up the system generated UUID for that content (in the case of SOL*R this is contained in the directory name in which the folder is contained)
 * •Via the API, send a query to the Piwik analytics password using the UUID to generate a new tracking code, and retrieve the code to be inserted in the content
 * Find and replace the distinct tracking comment with the unique tracking code from piwik

Once the content has been uploaded, both views “in place” (e.g. within the repository itself, in ‘preview’ mode) as well as views of the content after it has been downloaded will generate the following tracking data:


 * How many times the content has been viewed
 * The referring location of the URL that led to the content
 * The IP address of the user viewing the content