Track OER - midweek status, 16 August
Cloud created by:
16 August 2012
Subtitle: To script or not to script...
This resulted in an initial OER license-tracker, which currently supports OpenLearn-LearningSpace and LabSpace URLs. It makes requests over the Web for RDF files from OpenLearn, and queries the Piwik API.
Note, there is the potential to extend the OER license-tracker form to, for example, support OER Commons URLs as input, with the resulting license-tracker snippet referencing the source URL at MIT for example.
Which leads to my question - "To script, or not to script...?"
Comment 1 by Tony Hirst
3:46pm 21 August 2012
For js/no-js, is it worth considering different regimes?
eg I can think of at least the following:
- the content is syndicated into a reader environment that strips js.
- someone shares a link to a resource via social media or eg email. In this case, I'm wondering whether tracking information might also be minted into a a shared URL that could be picked up from a location.href lookup? eg campaign tracking codes. These allow you to learn more about the source of the click that loaded the resource page (ie they are metadata on the link that detail how it was minted when it was shared. You could imagine two links on the same page to the same resource (eg one wrapping text, one wrapping an image) that differ ito campaign tracking metadata that can be picked up when the detsination page is loaded?).
One way of tracking PDFs is to include links in them that carry a campaign code associated with that PDF. In the simplest case, if i own example.com/resource, I could embed example.com/resource?foo=bar.pdf in bar.pdf and then if anyone clicks on that link I know they came from bar.pdf from campaign tracking analytics on example.com.
This sort of thing also works if you share links by email, or twitter - generate a sharelink with tracking info. (ie this lets us explore not just that a resource is accessed, but also feeds in data about where the link that provided the access came from...)