Interoperability - LTI and Experience API (Formerly TinCan)

26
INTEROPERABILITY STANDARDS 2014 Webinar Series James Ballard Victoria Simpson

description

A webinar looking at the differences between SCORM, LTI and the Experience API (TinCan) within a Learning Management System environment. Presented by James Ballard, Senior Analyst at Nine Lanterns. Listen to the presentation: https://attendee.gotowebinar.com/recording/3218434722750502146

Transcript of Interoperability - LTI and Experience API (Formerly TinCan)

Page 1: Interoperability - LTI and Experience API (Formerly TinCan)

INTEROPERABILITY STANDARDS

2014 Webinar Series

James Ballard

Victoria Simpson

Page 2: Interoperability - LTI and Experience API (Formerly TinCan)

0-5 mins •Welcome and Orientation

5-10 mins •Session Introduction

10-40 mins•Presentation•Screen share

40-55 mins•Questions•Discussion

55-60 mins •Conclusion

Session OutlineWhat you can expect

Page 3: Interoperability - LTI and Experience API (Formerly TinCan)

15th

Jul - Responsive Design

29th

Jul - Open Badges

12th

Aug - ScaffoldLMS Administration

9th

Sep – LTI / TinCan (xAPI)

7th

Oct – e-Portfolios

11th

Nov - Assessment

IntroductionScaffoldLMS Webinar Series 2014

Page 4: Interoperability - LTI and Experience API (Formerly TinCan)

INTRODUCTION POLL

Activity 1

Page 5: Interoperability - LTI and Experience API (Formerly TinCan)

1. Introduce interoperability standards

What are interoperability standards?

Why have they changed?

2. Using LTI and xAPI

Why are these useful to learning?

Ideas for good practice

3. Integrating in ScaffoldLMS

Using LTI activities in ScaffoldLMS

Understanding the new log store through xAPI

ObjectivesWhat we hope you will get out of the session

Page 6: Interoperability - LTI and Experience API (Formerly TinCan)

UNDERSTANDING INTEROPERABILITY STANDARDS

Section 1

Page 7: Interoperability - LTI and Experience API (Formerly TinCan)

SCORMPackaged content modules

Page 8: Interoperability - LTI and Experience API (Formerly TinCan)

When to use SCORM

SCORM

Content with a relatively long shelf life that requires delivery and tracking via an LMS especially where the same content is delivered to different clients or different parts of an organisation.

Examples• Scenario-based simulations• Compliance training• Product training• Introducing new content

Benefits• Improved learning experience• Greater efficiencies and cost savings• Reduced risk

Content Package

“The e-Learning Standard”

Page 9: Interoperability - LTI and Experience API (Formerly TinCan)

ChallengesChanging social and technological milieu

1. Rigid Data Model

SCORM’s rigid data model restricts access to data from outside of the LMS and does not permit multiple ways for the LMS and courseware to exchange data.

Page 10: Interoperability - LTI and Experience API (Formerly TinCan)

ChallengesChanging social and technological milieu

2. Single Learner Model

SCORM is defined on a single learner model, with data that only describes an individual. This generally excludes scope for social, informal and self-directed learning as well offering poor support for technologies such as virtual worlds and social media.

Page 11: Interoperability - LTI and Experience API (Formerly TinCan)

ChallengesChanging social and technological milieu

3. Complex training softwareMany simulations, games, and complex data processors are not web-based or dynamically change between sessions, especially full-scale simulators. SCORM’s static data model is not defined to extend to this type of data.

Rescue

Medical Services

Page 12: Interoperability - LTI and Experience API (Formerly TinCan)

ChallengesChanging social and technological milieu

4. Non-content Package

SCORMs data model makes it difficult to support ‘non-content package’ methods of training that are especially presented by emerging technologies within mobile apps and augmented reality.

Biology

Natural History Interactive Learning

Page 13: Interoperability - LTI and Experience API (Formerly TinCan)

AUDIENCE QUESTION

Activity 2

• Are there any other types of learning you are trying to integrate?

Page 14: Interoperability - LTI and Experience API (Formerly TinCan)

LTI OR XAPISection 2

Page 15: Interoperability - LTI and Experience API (Formerly TinCan)

IMS LTI

Solution

Standard, extendable way of

integrating rich learning applications

Applications and content are

web-based, externally hosted

Grade and outcome data

can be returned to the LMS

ADL xAPI (formerly TinCan)

Experience tracking integration

utilising activity streams

Can support online or offline

activity - session-less

communication

Content can exist in any system

(i.e. outside of the LMS)

Two new standards

Page 16: Interoperability - LTI and Experience API (Formerly TinCan)

IMS LTILearning Tools Interoperability

Page 17: Interoperability - LTI and Experience API (Formerly TinCan)

LTI AppsIncreasing list of educational apps supporting LTI

https://www.edu-apps.org/index.html

Page 18: Interoperability - LTI and Experience API (Formerly TinCan)

• Existing tool• Bespoke

commission

Develop

• Configure

integrationDeploy

• Teacher can add to

LMS course as

activityUtilise

LTI WorkflowBasic implementation plan

Features

• Tool can be written in any coding language as long as it is web-based;

• LMS upgrades have no impact on the external tool reducing risk;

• External content can contain social interactions, simulations, and games

• Teachers can deploy different tools relevant to their programme

• Detailed reporting or analytics are provided within the external tool and not constrained by LMS or static data model

Page 19: Interoperability - LTI and Experience API (Formerly TinCan)

ADL xAPIExperience API (formerly known as TinCan)

Recording Experience

Statement freedom: lets you record almost any activity

History freedom: share data and transcripts across systems

Device freedom: any enabled device without need for constant network connection

Workflow freedom: your content isn’t tied to an LMS.

Page 20: Interoperability - LTI and Experience API (Formerly TinCan)

xAPI AppsIncreasing list of educational apps supporting xAPI

http://tincanapi.com/adopters/

Page 21: Interoperability - LTI and Experience API (Formerly TinCan)

• Existing tool• Bespoke

commission

Develop

• Integrate Learning

Record Store (LRS)Deploy

• Analyse LRS

activity dataUtilise

xAPI WorkflowBasic implementation plan

Features

• Requires a Learning Record Store (LRS) – a database of experience;

• LMS may be used as a LRS or they can be independent;

• External content can contain social interactions, simulations, and games

• Teachers can analyse different learning experiences

• Detailed reporting or analytics are provided within the LRS

Page 22: Interoperability - LTI and Experience API (Formerly TinCan)

LTI

Limitations

xAPI

Managing expectations for what the standards offer

No support for non web-based

activities

External tool must be

launched via LMS

Learning data may be distributed

across several platforms

Integration with non-browser

applications may become complex

Distinguishing claimed from actual

experiences

Capturing information from systems

that do not support the API 

The scale/context of experience is lacking

in the statement based approach 

Privacy issue tracking users in their

personal time/space. 

Page 23: Interoperability - LTI and Experience API (Formerly TinCan)

SCAFFOLDLMS DEMO

Section 3

• Configuring LTI (external tool)

• Creating an LTI activity

• Using the new logstore as an LRS

Page 24: Interoperability - LTI and Experience API (Formerly TinCan)

Q&A DISCUSSIONActivity 2

Page 25: Interoperability - LTI and Experience API (Formerly TinCan)

CLOSING POLLActivity 3

Page 26: Interoperability - LTI and Experience API (Formerly TinCan)

THANK YOUScaffoldLMS Webinar Series 2014

More information:

http://www.ninelanterns.com.au/

@scaffoldlms

https://www.linkedin.com/company/scaffoldlms