[Building Sakai] Moodle export/import suitability for Sakai 3

Mon Sep 21 06:15:51 PDT 2009

IMS-CC is very good at what it does:  provide a very well defined 
container for material to be published and distribute in inter-operable, 
compatible manner.  To do this, the CC committee created a limited 
subset of capability and made extensions NON-COMPLIANT.  I think Sakai 
should support the CC spec, including 3.x, but we should acknowledge 
that it is unlikely to provide comprehensive support, much less be the 
basis of migration.

- Mark

Michael Feldstein wrote:
> For the cross-system use cases, I would lean heavily toward IMS Common 
> Cartridge, not because it's technically better than the alternatives 
> (I have no idea if it is or not), but because some of the bigger 
> players are putting resources into developing support for it, which 
> means it has a better chance of being a successful exchange format. 
> D2L has announced that they support CC (import only at the moment), 
> Blackboard (via Ray Henderson) has committed to full import and export 
> of CC, it's on the road map for Moodle 2.0, and Pearson has been 
> throwing resources into it.
>
> - m
>
>
> John Norman wrote:
>> Sean set me on a different line of thinking. Who would we be building  
>> export/import for?
>>
>> Institution:
>> - as part of a year to year migration (export key elements from this  
>> years course and reimport them to set up the outline of next years  
>> course). This feels like we could/should handle it better with some  
>> other solution
>> - as part of a migration from one system to another. In this case we  
>> care about matching to the other system. This was in my mind when I  
>> suggested we should look at Moodle, Bb and CC formats
>> - as part of a sharing initiative. Something like opencourseware, but  
>> where the intent is that the visitor can download and use the course  
>> in their system
>>
>> Publisher:
>> - as a way of publishing a 'pre-canned' course to multiple  
>> institutions running multiple systems (our interest is primarily  
>> import, but see below)
>> Individual
>> - as a way of 'taking their course with them' as they move from  
>> institution to institution
>> - as a way of 'adopting' a course created by someone else at a  
>> different institution (here the individual sharing is in a similar  
>> position to the publisher above)
>>
>> Other???
>>
>> It strikes me that the amount and nature of what needs to move changes  
>> according to circumstance. It might be worth describing which  
>> scenarios we feel it is important to support.
>>
>> John
>>
>> On 17 Sep 2009, at 07:26, John Norman wrote:
>>
>>   
>>> Several thoughts here. You don't say so, but I hope we are talking  
>>> about Moodle as an export option (alongside IMS Course Cartridge and  
>>> Native). I would hate to think we would loose information  
>>> transferring from one Sakai to another because we use an export  
>>> format that does not contain all of our concepts. Then in  
>>> contemplating secondary formats for interchange with other systems,  
>>> we need to consider how stable/how fast they change and the  
>>> maintenance burden.
>>>
>>> I suspect it would be a lot of work, but it would be great to have a  
>>> comparison that compared Bb export formats with Moodle with CC. I  
>>> wonder if the IMS folk have this..?
>>>
>>> John
>>>
>>> On 16 Sep 2009, at 21:35, Speelmon, Lance Day wrote:
>>>
>>>     
>>>> I could use a second pair of eyes on the Moodle backup format.  I  
>>>> managed to get the latest build of Moodle up and running and then  
>>>> created a sample backup zip file.  We are trying to determine  
>>>> suitability of their format as an export/import format for Sakai  
>>>> 3.  Grab the sample below and provide any feedback you have on the  
>>>> wiki page.  Thanks, L
>>>>
>>>> http://confluence.sakaiproject.org//x/ERLtAw
>>>>
>>>>
>>>> Lance Speelmon
>>>> Scholarly Technologist
>>>>
>>>> On Aug 17, 2009, at 4:53 PM, Speelmon, Lance Day wrote:
>>>>
>>>>       
>>>>> As we prepare to start working on a Sakai 2 -> Sakai 3 migration  
>>>>> effort, I would like to help organize community contributions.   
>>>>> There are a number of roles and skills that need to be filled and  
>>>>> your participation would be highly valued.
>>>>>
>>>>> What can be done immediately:
>>>>>
>>>>> 1) Collaborate on defining the migration project plan.
>>>>> 2) Investigate LTI as an underlying mechanism for exposing Sakai 2  
>>>>> tools within the Saki 3 portal.
>>>>> 3) Investigate Moodle's export/import architecture and file formats.
>>>>> 4) Develop a Sakai 2 Resources (i.e. ContentHosting) to Sakai 3  
>>>>> JCR data conversion.
>>>>>
>>>>> If any of these tasks sound interesting or you have other ideas  
>>>>> you would like to share, please use the wiki space below.  Please  
>>>>> take the time to declare your area of interest on the Contributors  
>>>>> page.
>>>>>
>>>>> http://confluence.sakaiproject.org/display/KERNDOC/Migration
>>>>>
>>>>> Thanks!  L
>>>>>
>>>>>
>>>>> Lance Speelmon
>>>>> Scholarly Technologist
>>>>>
>>>>> _______________________________________________
>>>>> sakai-dev mailing list
>>>>> sakai-dev at collab.sakaiproject.org
>>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>>>
>>>>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org 
>>>>>  with a subject of "unsubscribe"
>>>>>         
>>>> _______________________________________________
>>>> sakai-dev mailing list
>>>> sakai-dev at collab.sakaiproject.org
>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>>
>>>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org 
>>>>  with a subject of "unsubscribe"
>>>>       
>>> _______________________________________________
>>> sakai-dev mailing list
>>> sakai-dev at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>
>>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org 
>>>  with a subject of "unsubscribe"
>>>     
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>>   
>
> -- 
>
>
> Oracle <http://www.oracle.com>
> Michael Feldstein | Principal Product Manager | +1.818.817.2925
> Oracle Academic Enterprise Solutions Group
> 23A Glendale Road, Glendale, MA 01229
> ------------------------------------------------------------------------
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"