> I’m in the phase of our project where we need to update all our SCORM 1.2 content to 2004 and add metadata to the content package itself and for each SCO (I don’t think we’ll go down to the asset level yet). There isn’t much, if any, metadata in the original manifests and I’m not sure where to start. Do you happen to have any good examples of manifests with lots of embedded metadata (especially 2004 conformant packages)? We are planning on filling in info on all of the mandatory fields, but our customer also wants to be able to store information on SCO dependencies, source files, and/or related SCOs. I have no idea where to store this information under. Maybe you know a good starting point for us? We’re using the latest RELOAD 2004 editor.
> Any help would be great.
My advice would be to quickly get started by entering meta-data using the latest version of RELOAD 2004 editor. I don’t know of any content examples (SCORM 2004) that are rich in meta-data –even the beginning ADL content examples were admittedly weak in this regard.
I have been using Reload Editor to enter Meta-data into the manifest, as you’re describing. I found it as easy to use as copying/pasting information out of an Excel spreadsheet into a web form. A little cumbersome, but definitely not difficult. Certainly better than hand-cranking XML.
There are a number of places to put the SCO dependencies, source files and other information. I think what you’ll want to look at it is putting that information under the
As far as related SCOs, there’s a lot of ways to implement this. One way I would employ (being that I’m a big fan of emergent systems) is to utilize the
Good questions, Angela. I hope this helps get you started.