Difference between revisions of "Checkpoints"
Jump to navigation
Jump to search
Sfrancisco (talk | contribs) (Edited source) |
Sfrancisco (talk | contribs) (Edited patlet) |
||
| Line 14: | Line 14: | ||
}} | }} | ||
Create regular "checkpoints" in social, non-linear MOOCs where participants approach activities in a different pace in order to help synchronize the course flow, catch up on social vibe and notice recent highlights.<ref name="Mor2015"/><ref name="Mornd"/>. | |||
==Context== | ==Context== | ||
Revision as of 11:31, 21 June 2016
| Checkpoints | |
| Contributors | |
|---|---|
| Last modification | June 21, 2016 |
| Source | Mor and Warburton (2015)[1]; Mor and Warburton (n.d.)[2] |
| Pattern formats | OPR Alexandrian |
| Usability | |
| Learning domain | |
| Stakeholders | |
Create regular "checkpoints" in social, non-linear MOOCs where participants approach activities in a different pace in order to help synchronize the course flow, catch up on social vibe and notice recent highlights.[1][2].
Context
Problem
Forces
Solution
Consequences
Benefits
Liabilities
Evidence
Literature
Discussion
Data
Applied evaluation
Related patterns
Example
References
- ↑ 1.0 1.1 Mor, Y. & Warburton, S. (2015). Practical Patterns for Active and Collaborative MOOCs: Checkpoints, FishBowl and See Do Share. eLearning Papers (42).
- ↑ 2.0 2.1 Mor, Y., & Warburton, S. (n.d.). Design patterns-MOOC Design Patterns. Retrieved from http://www.moocdesign.cde.london.ac.uk/outputs/patterns June 7, 2016.