claroline : learning path development perspectives

Learning path :development perspectives

Sébastien PirauxDeveloper at CERDECAM

ACCU 2007 – Vigo (Es)Learning path : development perspectives


● Learning path 1.0Current version

● SCORMFrom 1.2 to SCORM 2004

● Learning path 2.0Objectives

Table of contentsTable of contents


Presentation● (put some little demo here)

Learning path 1.0Learning path 1.0


The good● Ease of use● Integration● Tracking● Import and export● SCORM



The bad● SCORM import● SCORM 2004 not really implemented● Old code, hard to maintain



The ugly● Navigation to the path● Navigation in the path viewer● Frames● Interface is not always 'Claroline' enough



Shareable Content Object Reference Model● Norm accepted as a standard by courses producers

and LMS● Defines information exchanges between LMS and

course● Defines a way to track courses ● http://www.adlnet.gov/

SCORMSCORM

http://www.adlnet.gov/


From 1.2 to 2004● 2004 introduce sequencing and navigation● More and more SCORM 2004 packages● 2004 is now finalized (september 2006)

SCORMSCORM


Objectives● Allow any module type to be a path item● Should be a module itself● Should rely on linker● Use ajax for viewer● More consistant interface



Objectives● Based on SCORM 2004● SCORM 1.2 support● More flexibility of 'blocking' condition● Object oriented programming● ...



... suggestions ? ... remarks ?

Now is the time !

Questions ?Questions ?


Thank you !

claroline : learning path development perspectives

Technology