Comments on: Imagining a WeLE http://mfeldstein.com/imagining-a-wele/ What We Are Learning About Online Learning...Online Fri, 18 May 2012 06:39:00 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Joël Fisler http://mfeldstein.com/imagining-a-wele/#comment-1395 Joël Fisler Tue, 21 Apr 2009 10:33:42 +0000 http://mfeldstein.com/?p=998#comment-1395 Thanks for your clarifications. Sounds interesting, I am curious to see how this versioning and roll-back will be implemented in Sakai 3. Implementing Versioning is always a kind of "balancing act" between geeky user-unfriendly software like CVS or SVN that does everything and simple but not very powerful features like Wiki versioning. Good luck for those who are working on this task. Thanks for your clarifications. Sounds interesting, I am curious to see how this versioning and roll-back will be implemented in Sakai 3. Implementing Versioning is always a kind of “balancing act” between geeky user-unfriendly software like CVS or SVN that does everything and simple but not very powerful features like Wiki versioning. Good luck for those who are working on this task.

]]> By: Michael Feldstein http://mfeldstein.com/imagining-a-wele/#comment-1394 Michael Feldstein Fri, 17 Apr 2009 20:05:20 +0000 http://mfeldstein.com/?p=998#comment-1394 Stephen is right. The versioning and roll-back, for which at least the underlying capabilities will exist in Sakai 3, take this to the next level. Also, one feature highlighted in the demo is the ability not only to link to internal tools but to embed them directly into a free-form, WYSIWYG-editable HTML page. That, as far as I know, is also new. And finally, the proposed ability to open up viewing and editing rights to the students and even people not logged into the system, while not critical to what I would call a WeLE, certainly is an important advancement to the idea. This is about more than just adding an internal linking plugin to TinyMCE. Stephen is right. The versioning and roll-back, for which at least the underlying capabilities will exist in Sakai 3, take this to the next level. Also, one feature highlighted in the demo is the ability not only to link to internal tools but to embed them directly into a free-form, WYSIWYG-editable HTML page. That, as far as I know, is also new. And finally, the proposed ability to open up viewing and editing rights to the students and even people not logged into the system, while not critical to what I would call a WeLE, certainly is an important advancement to the idea.

This is about more than just adding an internal linking plugin to TinyMCE.

]]> By: Stephen Marquard http://mfeldstein.com/imagining-a-wele/#comment-1393 Stephen Marquard Fri, 17 Apr 2009 19:49:48 +0000 http://mfeldstein.com/?p=998#comment-1393 Joel, the screencast does not show the concept of a "WeLE". It shows flexible site composition with embeddable tool functionality inside html pages (in the last minute or so), but it's built as a demo on the 2.x version of Sakai. What makes the envisaged Sakai 3.0 more like a WeLE is that the content store uses JCR, which has built-in versioning. Joel, the screencast does not show the concept of a “WeLE”. It shows flexible site composition with embeddable tool functionality inside html pages (in the last minute or so), but it’s built as a demo on the 2.x version of Sakai.

What makes the envisaged Sakai 3.0 more like a WeLE is that the content store uses JCR, which has built-in versioning.

]]> By: Joël Fisler http://mfeldstein.com/imagining-a-wele/#comment-1392 Joël Fisler Fri, 17 Apr 2009 09:52:37 +0000 http://mfeldstein.com/?p=998#comment-1392 Michael, I found a big discrepancy between what I read in your blog and what I did see in the screencast. The features presented for Sakai 3 like dragging portlets around, an integrated HTML-Editor with the possibility to link to internal tools and to use templates is nothing new at all. HTML-templates have been around since 10 or 15 years. Also I did not see anything about the fine-tuned permission settings you talk about. All I did see was a "normal" HTML-editor separated from the LMS-Tools. What I do agree is that this is probably mistakenly labeled as “content authoring” :-) I am biased because I work for the University of Zurich and we use another LMS called OLAT. As Sakai OLAT is also a Java-based open source LMS but celebrating its 10th anniversary this year it is a bit older than Sakai. OLAT does integrated the same open source HTML-Editor (I believe its TinyMC) shown in the screencast and OLAT does also offer the possibility to directly link to internal tools. This has been around for many years in OLAT. The permission settings allow you to open courses only for a subset of students (e.g. Biology students or a defined group), for all students that have an LMS-Account or for the whole world. Nothing revolutionary here in my opinion. But maybe I am missing the point?? The only thing you list that I never did see in an LMS is true versioning with an easy rollback feature but this is not planned for Sakai 3, is it? Well I am curious to see if you vision of a collaboratively authored learning environment will come true. At least at our University I can see that authors/tutors are sometimes already overstrained with creating a simple course in an LMS. It would be interesting to see what happens if students - who generally know a lot more about an LMS than tutors - would also get the write-access to start manipulating courses and altering them :-) Might be a bit confusing but maybe also inspiring? Michael, I found a big discrepancy between what I read in your blog and what I did see in the screencast. The features presented for Sakai 3 like dragging portlets around, an integrated HTML-Editor with the possibility to link to internal tools and to use templates is nothing new at all. HTML-templates have been around since 10 or 15 years. Also I did not see anything about the fine-tuned permission settings you talk about. All I did see was a “normal” HTML-editor separated from the LMS-Tools. What I do agree is that this is probably mistakenly labeled as “content authoring” :-)

I am biased because I work for the University of Zurich and we use another LMS called OLAT. As Sakai OLAT is also a Java-based open source LMS but celebrating its 10th anniversary this year it is a bit older than Sakai. OLAT does integrated the same open source HTML-Editor (I believe its TinyMC) shown in the screencast and OLAT does also offer the possibility to directly link to internal tools. This has been around for many years in OLAT. The permission settings allow you to open courses only for a subset of students (e.g. Biology students or a defined group), for all students that have an LMS-Account or for the whole world. Nothing revolutionary here in my opinion. But maybe I am missing the point?? The only thing you list that I never did see in an LMS is true versioning with an easy rollback feature but this is not planned for Sakai 3, is it?

Well I am curious to see if you vision of a collaboratively authored learning environment will come true. At least at our University I can see that authors/tutors are sometimes already overstrained with creating a simple course in an LMS. It would be interesting to see what happens if students – who generally know a lot more about an LMS than tutors – would also get the write-access to start manipulating courses and altering them :-) Might be a bit confusing but maybe also inspiring?

]]> By: Podcasting for Learning » Funde auf delicious fuer April 16th von 15:27 bis 15:39 http://mfeldstein.com/imagining-a-wele/#comment-1391 Podcasting for Learning » Funde auf delicious fuer April 16th von 15:27 bis 15:39 Thu, 16 Apr 2009 14:06:09 +0000 http://mfeldstein.com/?p=998#comment-1391 [...] Imagining a WeLE - Michael Feldstein ponders about a new learning environment [...] [...] Imagining a WeLE – Michael Feldstein ponders about a new learning environment [...]

]]> By: Tim Schlotfeldt http://mfeldstein.com/imagining-a-wele/#comment-1390 Tim Schlotfeldt Wed, 15 Apr 2009 09:12:02 +0000 http://mfeldstein.com/?p=998#comment-1390 Michael, i like the idea of a wiki'ed learning environment. For a more non-formal approach for some customers i used drupal for this. The content of a wbt was transferred to drupal and the users were able to adapt the wbt pages to there needs. -Tim Michael, i like the idea of a wiki’ed learning environment. For a more non-formal approach for some customers i used drupal for this. The content of a wbt was transferred to drupal and the users were able to adapt the wbt pages to there needs.

-Tim

]]> By: » OLDaily per Stephen Downes, 9 d’abril del 2009 TIC, E/A, FER / PER…: http://mfeldstein.com/imagining-a-wele/#comment-1389 » OLDaily per Stephen Downes, 9 d’abril del 2009 TIC, E/A, FER / PER…: Sat, 11 Apr 2009 09:10:33 +0000 http://mfeldstein.com/?p=998#comment-1389 [...] / WeLE.” Com un Wellington boot? Michael Feldstein, e-Literate (alfabetitzat digitalment) [L'enllaç] [Etiquetes: [...] [...] / WeLE.” Com un Wellington boot? Michael Feldstein, e-Literate (alfabetitzat digitalment) [L'enllaç] [Etiquetes: [...]

]]>