Forum Discussion
SCORM packages not reading as complete in Brightspace
Hello,
My SCORM projects imported to D2L Brightspace are not reading as completed by Brightspace even though the learner has completed all slides and requirements. I have tried publishing packages with several different combinations of LMS reporting and tracking settings
1. Complete 'when the learner has viewed 100% of the slides' with a report status 'complete/incomplete'
2. Complete 'when the learner completes a quiz' with a report status 'passed/incomplete'.
The activity on the left of the image is a SCORM package published with option 1 and the activity on the right of the image is a SCORM package published with option 2.
It seems that with option 1, nothing appears in the gradebook. With option 2, it appears as complete in the gradebook, but does not check off associated competencies. The image below shows that the learner who has scored 100% on the activity in the gradebook appears with 0 assessment in the competencies.
Does anyone have suggestions for the right combinations of settings?
Shonelle
Hi Shonelle!
Sorry to hear course completion status is not being reported accurately by your LMS!
I would recommend testing how the course behaves in a different LMS environment, to confirm if the behavior you're experiencing is LMS-specific. SCORM Cloud is the best tool for this! If you aren't able to replicate the behavior in SCORM Cloud, there's a chance that the issue might be due to a setting or configuration in your LMS; in which case you'll need to work with your LMS administrator to find a fix.
If you can replicate the behavior in SCORM Cloud, please share a copy of your project file here or in private by opening a support case so we can take a closer look!
In the meantime, I'll open the floor to our knowledgeable community who may also be using Brightspace LMS, to share additional insight!
Thank you for this information, Steven. Our content tests well; however, there is no way to test the competency connection layer through SCORM Cloud. The obvious conclusion is likely that the problem exists within the LMS. I've already opened a support ticket with them but they've been unsuccessful at finding a problem over several weeks, so I was hoping someone else in the community has had this problem and could direct me to a solution.
Kindly,
Shonelle
