Join David Rivers for an in-depth discussion in this video Handling lessons for credit vs. not for credit, part of Up and Running with SCORM and Tin Can API.
- When creating SCORM-compliant courses…that are going to be published to an LMS,…you want to make sure that your LMS…is communicating properly with your lessons.…So when it comes to scoring,…you need to determine whether or not the course…is going to be submitted for credit or not,…and you need to match up with your LMS.…So let's talk about setting those options here in Captivate,…as we continue with our KE_Orientation project.…I'm using KE_Orientation2.…That's what you can open up from the chapter three folder…of your exercise files, if you're skipping to this movie.…
We've already added our graded interaction.…It's a question that's not necessarily…a test or quiz question,…but it allows us to have that reporting,…so we can be SCORM-compliant.…Now, are we reporting properly?…Let's go up to the quiz menu,…and from there select quiz preferences.…So, if this course is going to be taken by learners,…but it's not for credit,…we can go directly to our status representation section…and make sure incomplete/complete is selected.…
This course introduces the what, why, and how of SCORM, and the tools for creating SCORM-compliant content. Author David Rivers also covers the second generation of compliance integration, the Tin CAN API (aka the Experience API), which allows for learning events to be recorded and analyzed.
- What is SCORM?
- Why is SCORM important?
- Publishing to an LMS with tools like Adobe Captivate and Lectora Inspire
- Keeping SCORM-compliant by reporting scores
- Understanding the Tin Can API