Resource Tracking for UKOER


Published on

A summary of different approaches that may be used for tracking the release, use/reuse, and commentation of open education resources. Basis for an online seminar for the UKOER programme on 19-Nov-2009. (

1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Resource Tracking for UKOER

  1. 1. Resource Tracking for UKOER <ul><li>Phil Barker <> </li></ul><ul><li>R. John Robertson <> </li></ul><ul><li>Lorna M Campbell <> </li></ul><ul><li> </li></ul>We will start at 2:00pm, if you’re early please bear with us while we sort ourselves out. Feel free to try out the technology while you wait. Warning: person-to-person chat is visible to moderators.
  2. 2. Session Outline <ul><li>Intro (me): what? </li></ul><ul><li>Overview of programme requirements and other related activities: why? </li></ul><ul><li>Discussion of technical options for tracking: how? </li></ul><ul><li>Session Rules </li></ul><ul><li>Discussion please, not just presentations! (please) </li></ul>
  3. 3. Resource tracking? <ul><li>Monitoring </li></ul><ul><li>Number of resource released </li></ul><ul><li>Use / reuse of resources </li></ul><ul><li>Comments and ratings about resources </li></ul><ul><li>Impact (partial) </li></ul><ul><li>through technical means. </li></ul>
  4. 4. Programme level perspective
  5. 5. Monitoring number of OERs released <ul><li>Count what is represented in the Jorum? </li></ul><ul><li>Discuss </li></ul><ul><ul><li>Issues of granularity? </li></ul></ul><ul><ul><li>Timing? </li></ul></ul>
  6. 6. Monitoring Use / reuse <ul><li>Usage stats from host site </li></ul><ul><li>Google Analytics </li></ul><ul><li>URL redirects </li></ul><ul><li>Web search on a unique key </li></ul><ul><li>Web bugs </li></ul>
  7. 7. Usage stats from host site <ul><li>HTTP access log analysis </li></ul><ul><ul><li>Number of downloads </li></ul></ul><ul><li>Count of number of “views”/embeds on web 2.0 host </li></ul><ul><ul><li>often available through the API </li></ul></ul>
  8. 8. Google Analytics <ul><li>Similar sort of stats analysis to HTTP log analysis, but better </li></ul><ul><li> </li></ul>
  9. 9. Google Analytics: who uses it <ul><li>Hands up </li></ul><ul><li>1 : if you know about GA </li></ul><ul><li>2 : if you use GA on some project </li></ul><ul><li>3 : if you use GA on an OER project </li></ul>
  10. 10. URL redirects <ul><li>Replace direct URLs with indirect ones which </li></ul><ul><ul><li>Redirect the browser to the required URL </li></ul></ul><ul><ul><li>Acquire stats in the process </li></ul></ul><ul><ul><li>e.g. and </li></ul></ul><ul><li>Similar tricks used by Google and many online catalogues / repositories </li></ul><ul><li>Example uses (not all recommended) </li></ul><ul><ul><li>If you OER project has a catalogue </li></ul></ul><ul><ul><li>Monitoring use through specific dissemination channels, e.g. RSS </li></ul></ul><ul><ul><li>Links from OERs to other sites </li></ul></ul>
  11. 11. Who uses URL redirects <ul><li>Hands up </li></ul><ul><li>1 : if you know about URL redirects </li></ul><ul><li>2 : if you use URL redirects on some project </li></ul><ul><li>3 : if you use URL redirects on an OER project </li></ul>
  12. 12. Web search on a unique key <ul><li>Put a unique phrase/tag/identifier into the text of your resource </li></ul><ul><li>Release it into the wild </li></ul><ul><li>Search Google for that phrase </li></ul><ul><li>. . . and find where your resource has been re-used </li></ul><ul><li>(at least on the open web) (if the key hasn’t been edited out) </li></ul><ul><li>The unique key could be an identifier for the resource which links via a URL redirect to more info about that resource </li></ul><ul><li>e.g. “for more info on this resource see” </li></ul><ul><li>(But please do search Google for this for an illustration of a problem with case-sensitivity) </li></ul>
  13. 13. Who uses web search on key <ul><li>Hands up </li></ul><ul><li>1 : if you know about it </li></ul><ul><li>2 : if you use it on some project </li></ul><ul><li>3 : if you use it on an OER project </li></ul>
  14. 14. Web bugs <ul><li>See </li></ul><ul><li>“ A Web bug is an object that is embedded in a web page or e-mail and is usually invisible to the user but allows checking that a user has viewed the page or e-mail. ... Alternative names are Web beacon , tracking bug , tracking pixel , pixel tag , 1×1 gif , and clear gif .” </li></ul><ul><li>Causes a HTTP request to be sent to some defined URL whenever the resource is opened; information can be gathered through that request. </li></ul><ul><li>Used by  & Google analytics (JavaScript) </li></ul>
  15. 15. Who uses web bugs of their own <ul><li>Hands up </li></ul><ul><li>1 : if you know about them </li></ul><ul><li>2 : if you use them on some project </li></ul><ul><li>3 : if you use them on an OER project </li></ul>
  16. 16. Monitoring comments <ul><li>Comment & rating aggregation </li></ul>
  17. 17. Comment & rating aggregation <ul><li>Many host sites allow users to add comments and do star ratings </li></ul><ul><li>Some of these are available for aggregation through the site’s API. </li></ul><ul><li>Is anyone doing this? </li></ul>
  18. 18. <ul><li>This work is licensed under the Creative Commons Attribution 2.5 UK: Scotland Licence. To view a copy of this licence, visit or send a letter to Creative Commons, 171 Second Street, Suite 300, San Francisco, California 94105, USA. </li></ul>