Cloudworks is no longer accepting new user registrations, and will be closing down on 24th June 2019. We hope to make a read-only archive of the site available soon after.
TRACK OER - Project Plan
Cloud created by:
10 October 2012
The project plan aas set out in the proposal is structured on a development plan that will start immediately the project is funded to establish the code base, review use case and engage with the developer community. The majority of work in the development cycle will take place later to fit with planned availability of development effort which has been agreed with line management prior to submission of this proposal. There will be two parallel strands.
Strand 1: Track OER – web-bug tracker
- At the heart of most Web analytics systems, including Google Analytics, Piwik, ComScore and the analytics part of CaPRéT is what is termed a web-bug – code attached to an image, often a one-pixel by one-pixel ‘hidden’ image. By virtue of it’s inclusion or embedding in a host Web page it can be used to log data about the host page, the visitor, and the visitor’s browsing software. The image link can pass back information, taking the form for example:
- <img src= "http://track.example.org/tracker.gif?host=host.example.com&path=path/to¶mA=X&..." alt="" />
Strand 1: Development steps
Strand 2 CaPRéT++
- As the name suggests Cut and Paste Reuse Tracking (CaPRéT) is designed to add attribution and license meta-data, and to track the informal copying and pasting of OERs. It has been developed by Tatemae and MIT Office of Educational Innovation and Technology, and the code is available via Github (http://capret.mitoeit.org & http://github.com/tatemae/capret).
Strand 2: Development steps
- Currently CaPRéT does not appear to track when an individual image or multimedia resource is copied from within an OER. This limitation can be reduced using HTML5 DOM extensions within CaPRéT. (10 days)
- Moodle version of CaPRéT: As part of the project, a CaPRéT plugin will be written for Moodle to go through acceptance testing for full inclusion in OpenLearn/LabSpace. (10 days/5days testing)
- Overall testing and documentation in accordance with requirements (10 days)