Digital Workshop

Having been assured by a client that they did not require SCORM, I have completed 95% of a pub comprising 9 Flex modules designed to be watched in series, a quiz and a quickloading menu. Now, of course, it turns out the client was mistaken. It looks like I can retrofit SCORM by changing the properties of the pub, but this doesn't create the neat set of script (master), initialize and exit pages that would be there if I had started in SCORM Flex to begin with.
Will it be safer to...
> create a new launch module which then launches the first module, the first module then launching the second, etc. or
> create a new launch module for each of the existing modules or
> not worry and simply change the properties of each and fill in the manifest?
Any suggestions?

Adrian --

I would first start a new Pub with it set to be "SCORM." The blank/empty Pub will have a Master Script Page, an Initialization Page, and an Exit Page. All three Pages have specialized Scripts.

Next, I would make a copy of your existing project (always a good idea when experimenting), then go to Edit -> Publication Properties -> Type, where you'd change the copy to "Opus SCORM" Publication. SCORM Pubs are limited to what you can do compared to a full OPUS Pub. You may find some of your effort will not work using SCORM. Sorry!

I'd then copy the three SCORM pages and paste them into your old Pub, PLUS you'll have to create by hand, 18 Variables (CLOCK, CLOCK_VAR, etc) in the Edit -> Publication Properties -> Variables section. If you haven't seen this, OPUS v7 now has the ability to "hide" all the system variables, which means you'll only see the NEW variable you need to exactly create in your old Pub to make the Scripts work.

You'll have to highlight and change all your Pages to use the SCORM Master Script Page, which means if you are using a Master Page already, you'll have to copy/paste everything into the SCORM Master Page...

Testing is the ONLY way you'll know if this is going to work. I am guessing you'll have to do some customization to completely match everything with your LMS.

I'm glad Fred picked-up on answering your SCORM dilemma.
That's an area I want to learn, but not taking it up yet.


Hey guys, there's an easier way... OpusPro has a method for exporting variables.
In the Properties/Variables tab for a Publication or Page (each Page perhaps) --- simply select the variables you want or need and on the right sidebar there is an 'Export' button. Simply name the file so you can keep track of where these belong.

Importing is similar and simple.

Thanks for reminding me about OPUS' ability to export variables from the Edit -> Publication Properties -> Variables table. I believe that feature first appeared in v6.

If you don't regularly use an OPUS feature, you can end up forgetting about it.