Webtops, Wikis, and Widgets (Feb. 2009)


Published on

The future of learning technologies in higher education, including instructional or learning management systems.

Published in: Education, Technology
  • Be the first to comment

  • Be the first to like this

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

No notes for slide

Webtops, Wikis, and Widgets (Feb. 2009)

  1. 1. Wikis, Widgets, and Webtops(The Future of IMS for Higher Ed) Lesley BlickerRSP/ITEACH ConferenceFebruary 27, 2009http://lesleyblicker.efoliomn2.com/<br />
  2. 2. Instructional Technologies – Predictions through 2013 <br /><ul><li>Continued development of Web 2.0 tools and “apps”
  3. 3. Continued exploration in immersive virtual worlds as learning environments
  4. 4. Growth in number of products which have 3D “engines” built in (e.g., Second Life, Lively, 3B, EON Reality)
  5. 5. More 3D modeling, robotics, holographic software used in education and sharing of 3D objects
  6. 6. Ivestigative use of Webtops for education (PageFlakes, NetVibes, iGoogle)
  7. 7. Repurposing of the IMS* as we know it
  8. 8. Emergence of startups with radically different IMS concept, not enterprise-ready
  9. 9. ~10-15% of faculty experimenting with tools outside of IMS to accomplish more student centered learning and digital content creation
  10. 10. Attempt to layer interactive tools on top of IMS
  11. 11. No let up in plea for open APIs and interoperability
  12. 12. 7-8 years – primary Web interface begins morphing to 3D; 2D lives alongside 3D or in it for a while
  13. 13. Increasing use of Open Source IMSs
  14. 14. Increasing of “computing in the clouds” </li></ul>* Instructional Management System © Lesley Blicker<br />
  15. 15. Current State of the Current IMS Products<br />Categories of IMS for higher education:<br />Large enterprise systems which all have the same basic tools (assessment, discussion, quizzes/exams, gradebook, etc) and which scale and integrate with key administrative systems (email, ISRS)<br /><ul><li>Proprietary (e.g., D2L, eCollege, Blackboard)
  16. 16. Open Source (e.g., Sakai, Moodle)</li></ul>Small to mid-size traditional IMS products – same tools, maybe little more flexible, scalability unknown, untested (Web Study, CourseCruiser)<br />Small innovative IMSs, designed for individual course level, not likely to go enterprise, but are integrating with lots of social technologies, act and feel more like social technology (UDUTU, LearnHub)<br />
  17. 17. Current IMS (CMS) – What’s the Beef?<br />IMS 1.0: Unilateral publication formats<br />Labeled as false start; replicated existing classrooms<br />Assumes more passive consumer of information – one-way send<br />Monolithic and they don’t play well with others (API’s not truly open) – lack of interoperability <br />Scott Leslie’s Video: The Future CMS slide 34 – 35 http://www.edtechpost.ca/gems/TheFutureCMS3.htm<br />
  18. 18. Current State of the Large Commercial Enterprise IMSs<br />In the 3rd Phase of Add-Ons and Bundling<br />Adding more tools in general as well as limited and sometimes their own Web 2.0-like tools <br />Reliable, scalable, and able to be integrated with core administrative systems (SIS, LDAP, email) <br />Going some measure towards integration with other software or increasing interoperability via open APIs, but very slowly <br />Lack sufficient agility for early adopters who think the current IMS format is too limiting<br />
  19. 19. Current State of the Current IMS Products<br />Agility, act more like social systems, allowing student created content<br />Reliability, integrations<br />Small innovative applications developed primarily for the course level, more open API. Do not expect to grow to enterprise systems or be able to integrate with administrative systems anytime soon or in the foreseeable 3-5 years<br />Reliable, scalable, enterprise systems, integrate or interface with key administrative applications, flexibility and customization quite limited without additional work order; no programming allowed (D2L, BB, eCollege, Angel)<br />Open Source systems, more open APIs, community of developers building and sharing customizations; also need programmers <br />
  20. 20. Characteristics of Innovative IMSs<br />Newcomers are starting to emerge with radically different IMS designs: <br /><ul><li>Built-in Web 2.0 (widget) functionality
  21. 21. Boundaries going well beyond the course space
  22. 22. Integration with dozens if not hundreds of applications through pre-loaded and customizable widgets (open APIs)
  23. 23. Social networking is matter-of-fact
  24. 24. Multiple-way sends are matter-of-fact</li></li></ul><li>So Why?<br />Wikis<br />Widgets<br />Webtops<br />
  25. 25. Wikis – why?<br />Two-way send<br />Students populate their own content in web pages<br />Has ability to change assignments from paper submission or discussion posting to interactive multi-media web pages<br />Social software – profile aspect<br />
  26. 26. Widgets, Gadgets – Why?<br />Examples of software chock full of widget integration<br />iPhone<br />Wikis (WetPaint)<br />Blogs<br />Facebook<br />Easy integration with YouTube, Flickr, Google maps, etc.<br />http://lblicker.wordpress.com/<br />
  27. 27. Webtops – Why?<br />
  28. 28. Quick Definition Webtop<br />A virtual desktop on the web, running in a web browser <br />Examples: NetVibes, PageFlakes, iGoogle<br />http://www.google.com/ig<br />
  29. 29. The Webtop Phenomenon to Create a Personal Learning Environment<br />A Portal to Media Literacy, M. Wesch<br />http://www.youtube.com/watch?v=J4yApagnr0s – min 28<br />
  30. 30. My Predictions for the Future IMS<br />Nothing too innovative anytime soon<br />The enterprise application - a mix of systems for tracking learning experiences: <br />Running side-by-side with more flexible and interoperable approaches. Faculty will invent their own PLEs (personal leaning environment) I.e., g, M. Wesch using NetVibes, others using Wikis)<br />Receding in importance as the primary unit of the virtual course site and will morph to an LMOS (Learning Management Operating System), maintaining administrative functions for enterprise systems (e.g., SIS integration, managing grades) and would provide the backbone for layering (instructional software living on top of the IMS)<br />Not likely do it all (incorporate enough open API/integration with other technologies and remain reliable and able to integrate with SIS, core technologies needed for student integration)<br />Greater adoption of Open Source IMSs as the mid-ground<br />