Comments on: Moodle 2: File Import from and Export to Cloud Apps http://mfeldstein.com/moodle-2-file-import-from-and-export-to-cloud-apps/ What We Are Learning About Online Learning...Online Sun, 05 Feb 2012 04:42:18 +0000 hourly 1 By: darcusblog » Blog Archive » Content Ownership and Sharing in an LMS - geek tools and the scholar http://mfeldstein.com/moodle-2-file-import-from-and-export-to-cloud-apps/#comment-1843 darcusblog » Blog Archive » Content Ownership and Sharing in an LMS - geek tools and the scholar Sat, 17 Jul 2010 00:13:43 +0000 http://mfeldstein.com/?p=1600#comment-1843 [...] Feldstein has a post on the new Repository API in Moodle, and explains that it enables easy import and export of content [...] [...] Feldstein has a post on the new Repository API in Moodle, and explains that it enables easy import and export of content [...]

]]> By: Jason Shao http://mfeldstein.com/moodle-2-file-import-from-and-export-to-cloud-apps/#comment-1842 Jason Shao Tue, 29 Jun 2010 21:13:03 +0000 http://mfeldstein.com/?p=1600#comment-1842 Yeah, it's funny, but in a lot of regards, PLE models our elearn 1.0 workflow - email the prof a word doc, since I keep my own copy. I guess in a lot of scenarios the question is how to get back that personal ownership and multiple versioned workflow - since it's not like we're on 1.2MB floppies anymore. It does make me wonder - in terms of content creation whether LMSs should be less focused on enabling content, and more focused on archiving content created elsewhere and comment/discussion/grading workflows around it - which sounds an awful lot like an ePortfolio ;) Yeah, it’s funny, but in a lot of regards, PLE models our elearn 1.0 workflow – email the prof a word doc, since I keep my own copy. I guess in a lot of scenarios the question is how to get back that personal ownership and multiple versioned workflow – since it’s not like we’re on 1.2MB floppies anymore.

It does make me wonder – in terms of content creation whether LMSs should be less focused on enabling content, and more focused on archiving content created elsewhere and comment/discussion/grading workflows around it – which sounds an awful lot like an ePortfolio ;)

]]> By: Anze Sparovec http://mfeldstein.com/moodle-2-file-import-from-and-export-to-cloud-apps/#comment-1841 Anze Sparovec Tue, 29 Jun 2010 21:03:51 +0000 http://mfeldstein.com/?p=1600#comment-1841 Jason. The Chalk & Wire ePortfolio does a similar workflow to what you describe. We are an assessment ePortfolio so key tasks get submitted through our interface. Once a task is submitted it is versioned, as is any feedback or re-submissions. At not time are pages locked down. We currently have a Moodle integration, although it looks like there will be options to expand this with Moodle 2.0....very cool stuff. Jason. The Chalk & Wire ePortfolio does a similar workflow to what you describe. We are an assessment ePortfolio so key tasks get submitted through our interface. Once a task is submitted it is versioned, as is any feedback or re-submissions. At not time are pages locked down. We currently have a Moodle integration, although it looks like there will be options to expand this with Moodle 2.0….very cool stuff.

]]> By: Jason Shao http://mfeldstein.com/moodle-2-file-import-from-and-export-to-cloud-apps/#comment-1840 Jason Shao Wed, 23 Jun 2010 01:05:12 +0000 http://mfeldstein.com/?p=1600#comment-1840 Seems like LMSs could learn from DVCS and with promiscuous copying and revisioning everyone could own a copy - e.g. the user owns the original copy, which gets branched to the course, professor provides feedback/edits, merged back into the users private copy - then everyone owns different snapshots of the document/work depending on when it was released, and as it evolves. Seems like LMSs could learn from DVCS and with promiscuous copying and revisioning everyone could own a copy – e.g. the user owns the original copy, which gets branched to the course, professor provides feedback/edits, merged back into the users private copy – then everyone owns different snapshots of the document/work depending on when it was released, and as it evolves.

]]>