Russell Boyatt's slides from his entry, "Preserving a MOOC", for the Repository Fringe 2013 Developer Challenge. Russell was awarded the top prize in the Challenge and presented his entry to the full event audience on Friday 2nd August 2013.

1. “Preserving a MOOC”
Developer Challenge
Repository Fringe 2013
Russell Boyatt, University of Warwick
russell.boyatt@warwick.ac.uk
@russellb

2. MOOCs
● MOOC: “Massive Open Online Courses”
● Large numbers of students, potentially huge amounts of activity.
● Useful to gather this information for institutional archives, review by
participants and future research.
● Institutions spending large amounts of money developing content.
● From a repository point of view – you've already met and are probably
already preserving some of the content!

3. Capturing MOOC activity
● Reach into the (open) platforms to identify content and retrieve
activity.
● Web scrapers for other platforms and to gather associated
resources.
● Capture social media interactions (e.g. using Twitter streaming
API)
● Identify content already present in your institutional repository.
● Build a package of material including XML representations of
content.
● Push into a repository (with SWORD)

4. MOOC Preservation Toolkit
OpenMOOC
Visualisation of activity

5. Social media
● Twitter – streaming API, capturing all activity to
a #mymooc hashtag.
● Blogs – EU FP7 Blogforever project is building
a toolset for capturing and preserving blog data.
● Capture this data and preserve in repository
alongside learning resources.

6. Preservation
● Learning resources developed for a MOOC can be captured
and stored in a repository.
● Opportunity to explicitly state licensing information.
● Hold resources in standard platform and formats rather than
rapidly developing MOOC platforms.
● Route to collecting learning resources in a form suitable for
OER.
● Preserving a representation of learning activity on the MOOC.