|
[
Permalink
| « Hide
]
Martin Dougiamas added a comment - 08/Jan/07 03:43 PM
Can we please put some priority on this?
Ideally it would be most effective if the SCORM and IMS packages did not have to be unzipped and loaded into Moodle at all.
What we would like is the ability to point to a manifest via a URL (eg. http://host.domain/imsmanifest.xml Cheers, Right. If the file is a plain manifest then there's no need to unzip (but it still has to be downloaded so Moodle can process it).
Any progress at all on this Maximino?
I don't know any LMS which process the imamanifest.xml outside the .zip package. I think it's out of the standard. The .zip is the "package" so it has to be an only one element. I'm not sure at 100% but it has logic.
We could say we have already done a 70% of the task.
Right now, the first task is already finished. So we can add a SCORM package entering its URL. We can also update the SCORM activity manually, even though the package is remote. In this case, we should check if the package has been changed and if it has, it should be dowloaded and unpacked again. It works for SCORM zip files, but not when the URL is a manifest (eg. http://host.domain/imsmanifest.xml  ), because that is what we understood from the wording of the task. However, after reading Martin's comment, we think it has to accept URL of remote manifests like the one of the example and not only SCORM files, right?
At the moment, we are working on the second subtask. The additional menu with the update remote packages options is already added and we have modified the scorm table to store this value. We are modifying the scorm_cron function to update every day the packages which are configured like that. These updates will be done at the time set in the SCORM module configuration. We are modifying the scorm_view_display function for the update of the modules when they are configured to be updated every time they are used. These last modifications are not uploaded to the CVS yet because we are debugging them. Regarding the second subtask we have a doubt that Bobo suggested some days ago which is that we don't know very well what the option "update the package whenever it changes" means. Does the change occurs when the user edits the SCORM activity of Moodle or we have to configure the cron to check periodically if the remote SCORM packages have been changed? After the last update of the SCORM module in the CVS the options "Update this package every time it's used" and "Update this package every day" are working correctly for the remote packages. Only the last option, "Update this package whenever it changes", is left to finish the second subtask, but we have doubts about its meaning.
We are not sure about what is wanted to be done when the remote package is deleted. Now, when the option "Update this package every time it's used" is selected a message which says "notfound" is shown when we try to view the activity whereas if "Update this package every day" is selected, we can see the last version of the package before it was deleted. This feature has been completed
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
New Feature
Closed
Critical
Allow SCORM module to handle external scorm packages
 |
|
