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

[Speelmon, Lance Day]

I find this line of questioning very engaging, and have given it a  
fair bit of thought.  The conclusion I am reaching is that it is  
largely out-of-scope (at least in the context of a Sakai 2 -> 3  
migration).  It is an important discussion to be had, but perhaps in a  
more generalized import/export context?

My hopes are that work done in the Sakai 2->3 migration effort will  
support and perhaps even deliver on some goals for the general export/ 
import concerns.  If agreeable, maybe we should continue this  
discussion in a different wiki context (i.e. other than 2->3  
migration)?  Thanks, L


Lance Speelmon
Scholarly Technologist

On Sep 17, 2009, at 4:30 AM, 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"