1 / 16

How to use IMS Learning Design and SCORM 2004 together OUNL

How to use IMS Learning Design and SCORM 2004 together OUNL. written by C. Tattersall, D. Burgos, H. Vogten, H. Martens, R. Koper and presented by G.W. van der Vegt Educational Technology Expertise Centre Open University of the Netherlands SCORM 2006 Taipei. Contents. About us

field
Download Presentation

How to use IMS Learning Design and SCORM 2004 together OUNL

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. How to use IMS Learning Design and SCORM 2004 togetherOUNL written by C. Tattersall, D. Burgos, H. Vogten, H. Martens, R. Koper and presented by G.W. van der Vegt Educational Technology Expertise Centre Open University of the Netherlands SCORM 2006 Taipei

  2. Contents • About us • IMS-LD / SCORM 2004 similarities • IMS-LD / SCORM 2004 differences • Together, two possible integration paths • Using SCORM from within IMS-LD

  3. About Us, the Department Otec Educational Technology Expertise Center • Research (fundamental educational research) • 4CID model • Development (product oriented research) • Products like IMS-LD & CopperCore • Currently developing products for ‘Learning Networks’ • Implementation (end-user / faculty oriented) • Traditional multi-media productions • Educational Design Support for faculties

  4. Similarities • Standards for developing e-learning courses • Both use content packaging • LOM is used for metadata • Consist of a server and a client or player part

  5. SCORM 2004 reference model describing content and runtime behavior has an API for server interaction (LMS) simple to implement single user plenty platforms support it IMS-LD single specification for both content and its runtime interactions between users no restrictions on actual content no standard interface with server more complex to implement growing support can model complex interactions designed to link other specifications Is multi-user and supports roles Sequencing activities is a integral part of the specification. Differences

  6. Integration paths • Paths for integrating IMS-LD and SCORM2004 • SCORM orchestrates and uses IMS-LD as content/resources • IMS-LD orchestrates and uses SCORM SCO's as content/resources

  7. Connecting users and roles • SCORM to IMS-LD and back User #1 User #1 User #2 User #2 Role #1 User #3 User #3 Role #2 User #4 User #4 IMS-LD SCORM2004 SCORM2004

  8. User#1 Role #1 Role #1 User#2 Role #2 Role #2 User#3 User#4 IMS-LD SCORM2004 IMS-LD Connecting users and roles • IMD-LD to SCORM and back

  9. Using a SCO from inside IMS-LD #1 Hardcode url's to SCORM player as web resources:

  10. Drawbacks #1 • Two distinct servers -> single logon problems • No communication between the IMS-LD and the SCO • Url of SCO has to be known before IMS-LD can be published

  11. Using SCO from inside IMS-LD #2 Use single content package for both IMS-LD and SCO's to solve url problems. Drawbacks #2 • Two servers -> single logon problems • No communication between the IMS-LD and the SCO. • Some preprocessing is needed to split and publish the CP into separate content packages for the two runtime systems.

  12. Where to put a SCO inside IMS-LD • IMS-LD has an Item model that permits linking to file resources packed into the content package • That file may be another content package • The file may be another CP containing a SCO.

  13. How to solve the lack of interaction problem? Incorporate the server part of SCORM2004 into a IMS-LD system, for both launching SCO's and SCO data storage. • Use the packaging mechanism of option #2 • Store SCO runtime data in the IMS-LD database so the UOL can read/write them too. • Make arrangements on the mutual property names and their meaning. • This could all be implement through the CopperCore CCSI (CopperCore Service Integration) dispatcher.

  14. CCSI

  15. Linking with interaction

  16. Questions?

More Related