[DG: Teaching & Learning] Fwd: SCORM in Sakai

[John Norman]

It seems James got a message bounce, so I am forwarding to the list on his behalf.

John

On 30 Aug 2010, at 01:29, James Dalziel wrote:

> Hi John and Sakai colleagues,
> 
> If you want to use Sakai 3 tools to run external standards-based content,
> then the Sakai 3 tools will need the features anticipated by the relevant
> standards. For SCORM and IMS CP this is relatively simple, but for IMS
> Learning Design (LD), this brings some additional features that you might
> not build into the Sakai 3 tools natively.
> 
> In Learning Design, an instructor can create a sequence of learning
> activities which include embedded instructions and tool configurations that
> are central to the pedagogical intent of the sequence (eg, "At Step 2, show
> a forum with a thread named 'Your initial reflections on climate change' and
> allow students only one posting of no more than 500 words").
> 
> As the key goal of Learning Design is to be able to share effective designs
> among instructors (including at different locations), what you want is for
> your tools to be able to "receive" these kinds of "tool instantiation
> directions" about their behaviour, and self-configure accordingly. 
> 
> So if I build a Climate Change sequence for my course that includes a Step 2
> like the one above, then I export this sequence and share it with an
> instructors at another institutions, when they load it into their LMS, the
> hope is that the tools in their LMS are able to self-configure accordingly.
> 
> The problem is that most LMS tools were not built with the idea that they
> could be configured by some external process - so they don't know how to
> receive the command "set up a thread with the name "Your initial
> reflection...".
> 
> Going further, there may be functional requirements for the tools that a re
> expected by the Learning Design, like limit the Forum posting to only one
> post of no more than 500 words. If the LMS tools lack these features, then
> part of the design may be lost when transferred.
> 
> Those of you who know our work on LAMS will be aware we've worked on these
> problems for many years now, and they are not simple. My key observation for
> Sakai 3 here is for tool developers to think about the kind of generic
> features that a tool needs to support, and whether these features include
> the ability to be configured by a separate process.
> 
> For those who are interested, we got all this to work with Moodle tools
> running with LAMS, even to the point of having Moodle tools pass data to
> LAMS (such as quiz scores) which LAMS is able to use to make decision (eg,
> branching). More details and animations at
> http://wiki.lamsfoundation.org/display/lams/Moodle+Tool+Adapter
> 
> Hope this helps!
> 
> James
> 
> -----Original Message-----
> From: pedagogy-bounces at collab.sakaiproject.org
> [mailto:pedagogy-bounces at collab.sakaiproject.org] On Behalf Of John Norman
> Sent: Friday, 27 August 2010 11:56 PM
> To: Hugo Jacobs
> Cc: Teaching & Learning Sakai Group; Sakai Dev List
> Subject: Re: [DG: Teaching & Learning] Fwd: SCORM in Sakai
> 
> This would be my preference for several reasons.
> 
> But I also think our design process needs to include a review of native
> formats in other open-source projects in case interoperability via
> interchange standards causes useful concepts to be lost unnecessarily... We
> should also use the experience to feed back at least to IMS.
> 
> John
> 
> On 25 Aug 2010, at 16:20, Hugo Jacobs wrote:
> 
>> Hi all,
>> [...]
>> For Sakai 3 it might be a different matter. Instead of playing SCORM, IMS
> CC, IMS LD we could regard it as an exchange format,.. and play the content
> natively with Sakai tools in all their glory.
>> Parties who want to import a CC, SCORM, LD learning component should build
> a bridging module. Same goes for export of components in these formats
> (depending if you would regard Sakai as an authoring and staging
> environment)
> 
> _______________________________________________
> pedagogy mailing list
> pedagogy at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/pedagogy
> 
> TO UNSUBSCRIBE: send email to pedagogy-unsubscribe at collab.sakaiproject.org
> with a subject of "unsubscribe"
>