Upgrade to Pro — share decks privately, control downloads, hide ads and more …

It Wouldn’t Be the Same without You: MOOC Design that Supports User-Contributed Content, Interaction and Teamwork

houshuang
October 03, 2015

It Wouldn’t Be the Same without You: MOOC Design that Supports User-Contributed Content, Interaction and Teamwork

Presentation at Learning with MOOCs 2015, Columbia NYC. Video: https://www.youtube.com/watch?v=r0tJsAfp5OQ&feature=youtu.be

houshuang

October 03, 2015
Tweet

More Decks by houshuang

Other Decks in Education

Transcript

  1. Stian Håklev, Open.UToronto MOOC Design Workshop, June 11, 2014 It

    Wouldn’t Be the Same without You: MOOC Design that Supports User-Contributed Content, Interaction and Teamwork Photo by Bestarns @ Deviantart
  2. Technology choice • CSCL: Interface matters for the kinds of

    interactions you are having (Daniel Suthers and many others) • Tech: The kind of stack you choose matters for the kind of interface you end up building
  3. LTI vs xBlocks • xBlocks, the way to extend EdX.

    But cannot be used on edx.org • Specific to EdX, needs to use specific programming languages and interfaces • Can integrate much more deeply with host platform/ data
  4. LTI • IFrame or full page • All requests have

    unique ID (like 3420-49324j) • Full page loads can also carry EdX ID and email (user has to give permission) • Has no access to any other data on EdX platform (can return a grade) • Not specific to EdX • Can do anything, including integrating with non-LTI enabled sites • Immediate access to analytics data
  5. LTI • IFrame or full page • All requests have

    unique ID (like 3420-49324j) • Full page loads can also carry EdX ID and email (user has to give permission) • Has no access to any other data on EdX platform (can return a grade) • Not specific to EdX • Can do anything, including integrating with non-LTI enabled sites • Immediate access to analytics data
  6. APIs • EdX has very limited APIs, LTI + submitting

    grading • No access to cohorts • Writing/reading to forum • Live analytics data
  7. • New(ish) but built on Erlang foundations • Highly scalable

    • Very fast (many requests per second, low latency) • Strong support for web sockets • Rich support for background workers, mail servers, etc. • Ecosystem still growing
  8. • New(ish) but built on Erlang foundations • Highly scalable

    • Very fast (many requests per second, low latency) • Strong support for web sockets • Rich support for background workers, mail servers, etc. • Ecosystem still growing
  9. Problems: - difficult to design - keep track of changes

    - boilerplate before analysis/ graphing
  10. • 1. Describe a typical classroom where this lesson might

    be enacted. • 2. Describe the major theme of the lesson. • 3. What are the learning goals of the technology-enhanced lesson? • 4. Some aspects of the design (complete any that are relevant) • 4a. Student-Centered Design • 4b. Peer Collaboration • 4c. Use of Handheld or Mobile Computers • 4d. Supporting Equity and Diversity • 5. What is the activity structure of the lesson? • 6. Assessment notes. • 7. Enactment notes. • 7a. Ethics or enactment concerns Capstone team based project (no-credit)
  11. Conclusion • At the panel, they all talked about making

    MOOCs more social, interactive • People in CSCL, distance ed, HCI have worked on this for decades - great examples to learn from
  12. Conclusion More deep research (and documentation/sharing) about student experiences, supporting

    MOOC collaboration, sync/async, multi- channel (web, mobile, email, notifications, chat, video) Make it easier to innovate and integrate (APIs, apps, document ideas, libraries) How to best share technology - libraries, xBlocks, social-as-a- service, LTI components, …