I've searched for all info containing "Sakai" and there are no threads from within a year and only a second that is 5 years old. So I'm a nervous newbee suspicious that few are using Captivate+SCORM+Sakai together. I hope someone has done so (preferably recently)!
We are in the initial architectural decisioning regarding an eLearning module that enables students to analyze three-dimensional models in a three.js virtualized space (I am not referring to a VR space). The students will be able to navigate the three-dimensional model to look at objects from all directions, to measure characteristics in the model, capture and recall the measurements, etc.
This is the core functionality being delivered.
The learning module is useful to several learning environments, so it is important to build it in a universally portable package. SCORM seems to be a good candidate.
The initial LMS is Sakai. So we're assuming the Sakai SCORM player will be the manner to use the module in the first user env.
SCORM + Sakai info seems scarce. Seems Sakai is not in full embrace with SCORM. Maybe my searches are poorly crafted.
Mobile users would be nice to have, but the use case does not translate well to the small screen and coarse touch navigation. So mobile devices are only a "Nice to have".
We will surround the three.js interactive model activities with traditional eLearning content: multi branch concept "slides", quizzes, recorded video demos, etc...leveraging the traditional eLearning content technology.
We want to leverage student roles and authentication from the LMS, and automate any other feeds available (e.g. Gradebook and/or Student Progress).
Any warnings? Encouragement?
Good source of documentation (I really have looked)?
2
Replies
AdChoices