Forum Discussion
Everything we know about Cornerstone on Demand and Storyline!
You are correct in all of that Will. When you reversion, you have to go back through and reset all of your catalog settings (i.e. the new version does not inherit the old version's settings). After that we ran that same report and had to proxy enroll those "In Progress" and "Registered" as you said. For "In Progress" progress is lost.
How you go about that last part really comes down to why the reversion was done. If the new version doesn't need to go to existing users, all the messing around with proxy enrollments, etc is unnecessary. Any users registered after the new version is activated will receive the new version, (provided the availability was properly set in the catalog).
However, if the reversion was to correct a major defect or content error, and everyone needs that version then running through the proxy enrollment process becomes necessary.
All of that rigmarole, is why if I can just do a file update instead of a full on reversion, I do. File update pushes out to all users of your existing version immediately. The hazard being file update can totally corrupt a course, if the changes are more than a minor adjustment to course content.
I think that one way to avoid corrupting a Storyline course when updating the files may be to delete all of the files from the CSOD publication first, and then upload the new .zip file, rather than letting Cornerstone's file manager try and reconcile the differences. So on the update publication page instead of just uploading a new zip file the procedure would be:
- Click Get Directory List.
- Click the topmost checkbox to select all files in the existing directory.
- Click Delete (to delete ALL files in the publication).
- Close the pop-up window.
- Click Choose file and pick the replacement zip.
- Click Upload.
- etc.... (same procedure from here on out)
In my experience when I re-publish a Storyline module, it seems like the component's filenames are not identical to what they were the last time I published it. So a file that was named zxczxsedf.swf may now be named qwerqwer.swf, and so on. So if you let Cornerstone try and replace the files by comparing the new and old files, my theory is that it will leave several old files in its directory, and there may be some caching going on and other mayhem that confuses Cornerstone's file manager. It seems to me just better to take the extra step of deleting all of the existing files first. This is what I would do when I had to manage files myself in an LMS where I had to FTP everything myself.
I've tried this solution a few times. It works more often than not, but occasionally I'll just have to create a whole new publication.
Will, out of curiosity, do you have FTP access to your content in CSOD? I only get my reports, but it'd sure be nice to be able to access everything.
This E-mail and any of its attachments may contain Regis Corporation proprietary information, which is privileged, confidential, or subject to copyright belonging to the Regis Corporation. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.I don't have FTP access to our content files. I agree it would be nice though.
I would echo James's sentiment that I have deleted existing course files before uploading the new ones and found that to be successful most of the time. I have also gone through and located old files that did not overwrite by upload date and deleted them if a course went wonky. Also just as James noted, I too have fully blown up a course by deleting the files and replacing (that one had an odd folder structure from our old LMS so that may have been just an oddity.
I have also noticed that while CSOD indicates the course has been updated, it is rarely, if ever immediately available to the end user. Typically, following multiple browser restarts and cache clears I will see the noted changes. (for this reason I typically put a version/update number at the beginning of slide 1 so I know when updates have made it to end user).
Long story short, I haven't typically needed to clear the existing files pre update. Usually I have just had to wait for the entire update to reach end users. (sometimes 30 minutes to several hours)
To your other point. I believe it is possible to download the course files from CSOD. There is a download setting available to the superadmins I believe that allows for downloading of these files, but full on FTP function I don't believe is available.
