I am quite curious about the ongoing development of this project. I have tested the existing code and found it be as promised - with the exception of "logging events of each user".

That comment was taken from the main project page yet I found no mechanism to do that. Have you continued in the effort or has development been discontinued in light of some other solution?

thanks

Comments

icametoplay-1’s picture

icametoplay-1 commented

My apologies. On further investigation I found the module is in fact storing data about activity within the DB in a table = scorm_scoes_track.

However, I do not see an obvious way to expose any of this data to the user - nor to administrators.

How are you currently going about doing that?

Thanks

pgerling’s picture

pgerling commented

I just thought about pointing you to scorm_scoes_track in the database! ;o)
Currently, there is only the 'results'-tab if the corresponding scorm event is returned by the scorm unit (cmi.core.score.max, cmi.core.score.raw, cmi.objectives%.score.max, cmi.objectives%.score.raw). If the scorm unit does not return the score in this format, the SCORM module is not able to display the resluts - during my last attempt on this issue I noticed that a lot of different scorm units are returning different events.. :-(

We are thinking about a way to display all user events to the site administrator (a simple table or sth.), but because we are only able to spend limited resources on the SCORM module development (currently, only I am taking care of it - and I am just a student worker).

If you continue your effort on logging - and how to display the logged information - it would be great if you share your thoughts with us.

icametoplay-1’s picture

icametoplay-1 commented

Again, sorry. I should have looked a little closer before posting.

I do indeed intend to create a way to expose this information in a meaningful way - and of course I will be happy to share what we end up with. Frankly, it seems like it should not be too difficult considering the data is in fact there.

When you say 'results tab' what exactly are you referring to? My current test package is not firing anything other than complete - which I can see in the _track table. Are you suggesting if there were other events that my SCORM node would have a 'Results' tab?

Thanks

pgerling’s picture

pgerling commented

You are welcome - the SCORM module is still confusing me as well from time to
The 'results tab' should be located at '%DRUPAL%/node/%NID%/result' - if your scorm unit is firing the correct events.
I can share the scorm unit we used for testing if want to, just leave me your email/skype id.

icametoplay-1’s picture

icametoplay-1 commented

Thanks - i contacted you through your drupal.org profile.

dirk.westrup’s picture

dirk.westrup commented
Assigned: Unassigned » pgerling
fuzzy76’s picture

fuzzy76 commented

subscribing :) I'd love to add scorm support to certify

webservant316’s picture

webservant316 commented

Wow, way cool!!

we want to build an LMS and I've been looking at Moodle which would require learning to admin a whole new system. LMS modules for Drupal seem in short supply, but a SCORM player could be one simple Drupal add on that could easily turn Drupal into a complete LMS.

I am very curious myself.

Is there a page or document that describes what remains to be completed and the time line for this module to be production quality? Also curious what the SCORM compliance goals are? There are 3 levels of SCORM 1.2 compliance listed at www.adlnet.gov and SCORM 2004 versions 2, 3, and 4. What level of SCORM compliance are you aiming for and what do you have now?

Thanks for your work on this module!!

pgerling’s picture

pgerling commented

Currently the SCORM compliance goals are the same as for the Moodle SCORM module ( http://docs.moodle.org/20/en/SCORM_module ). We do not aim to provide more SCORM functionality. Currently there is no timeline, but we will have a release candidate that could be used soon (we are already using SCORM in a productive environment).
There are just a few bug fixes and minor updates left on our internal schedule.

dirk.westrup’s picture

dirk.westrup commented
Version: 6.x-1.0-beta13 » 6.x-1.0-rc1
Status: Active » Closed (fixed)

Closed. Question seems to be answered. More than 1 week with no activity.