Tracking+-+TTD

<--back =Non-Technical=
 * write up paper
 * talk to Paul/send draft re: tracking proposal; confirm that
 * we can use the license generator to insert a placeholder
 * we should be asking content owners if they wish to be enabling tracking
 * if we need to be doing anything with the license to have content re-users acknowledge the tracking code
 * other strategies for mitigating risk that tracking is seen as infringement on
 * figure out what is the best way to survey the OER community about the issue of using tracking code, specifically whether it is ok to receive data back from unwitting re-users (e.g. students of someone who has reused someone else's content.) Is simply anonymizing the last 3 digits of their IP address a good enough approach?

=Coding / Development=

License Generator
> after the license
 * as part of the redevelopment of the BC Commons license generator, add an optional step - "Would you like to insert a tracking code in your content so that you can see how often and where else your content is being used?"
 * insert


 * **QUESTION:** easiest to do this on the BC Commons license. Should we simply start there, or should we also offer it for the CC license
 * if we do the later, then we need to not just send people off to the CC site
 * **QUESTION:** are any modifications to the license required?

Tracking Generator
> > > > for file located at /bigstore/dev_tle41filestore/Institutions/bcc/Attachments/39/295a1c49-f8f8-2b34-c1b7-7b57f5bff9cc/1/tracking_site_test.zip/tracking_site_test/index.htm > > siteURL will be http://solr-dev.bccampus.ca:8001/bcc/items/ + /bigstore/dev_tle41filestore/Institutions/bcc/Attachments/**/_this string_** > > e.g. where /xml/lom/general/identifier/entry like '295a1c49-f8f8-2b34-c1b7-7b57f5bff9cc%' > > http://helen.bccampus.ca/piwik?module=API&method=SitesManager.addSite&siteName=_fetched-via-equella-api_&urls[0]=http://solr-dev.bccampus.ca:8001/bcc/items/295a1c49-f8f8-2b34-c1b7-7b57f5bff9cc/1/ > > http://127.0.0.1:8888/piwik/?module=API&method=SitesManager.getSitesIdFromSiteUrl&url=_resourceURL_ > > (though may not need to do this, maybe addSite returns siteID) then get tracking code to insert with > > http://127.0.0.1:8888/piwik/?module=API&method=SitesManager.getJavascriptTag&idSite=2&format=Html&token_auth=anonymous >
 * In order to generate the tracking code after the files are deposited in SOL*R, must crawl the filestore, find .htm files, locate the string
 * and then call the piwik api using the following formula:
 * fetch the site_name via equella API
 * create new tracking site with
 * fetch siteID with
 * N.B.** one issue with this command currently - how do we run it so that the anonymous account automatically has access to the resulting reports
 * This can be run as a cron job.

Modifications to Piwik/Workarounds

 * piwiki currently requires javascript to work; would be good if we could either implement the workaround Nick proposed to use a proxy for the javascript, or else even better simply complete the open project task on piwik to have the method implemented
 * on the Actions - Pages reports, would be good instead of simply displaying the directory name in which the content is found, if it could display the full URL of the server (cf code in plugins/Actions in piwik)

Report Generator
Finally, we need to be able to
 * point the content owner to a report of the stats
 * ideally we aggregate together Equella reporting per/resource with the piwik reports on one page
 * produce a master dashboard