<html>
<body>
Hello
Xertians......Xertetians......XerteGurus......Xertites.....??<br><br>
<br>
We are using desktop Xerte 2 to produce many SCOs that we will put
together into a SCORM 2004 content package using the ADL Reload Editor.
<br><br>
<br>
Right now when you select Package SCORM 2004, it seems you get a SCORM
content package made up of a single SCO that comes with a manifest file
and lots of other files that an individual SCO doesn't need.
<br><br>
<br>
What we'd like to do is to generate only the files the SCO needs, along
with a metadata file to make the SCO retrievable. We've looked at
the Xerte source code a bit but would rather not modify it if it's not
necessary.<br><br>
<br>
Has anyone dealt with this issue who can offer any advice on the most
efficient approach? Are there any shortcuts or tricks - like
changing or removing files from C:\Program Files\Xerte\publish\scorm2004
before packaging the SCO? <br><br>
<br>
We're going to be creating lots and lots of SCOs so any time we save will
be multiplied by a large factor. <br><br>
<br>
Thanks!<br>
ma<br><br>
<br>
p.s.<br>
Here's what I was able to find in the archives: <br><br>
From Sept 2009<br><br>
</u></b>Q: Are the pages that we create as part of LO called assets
or SCOs? or is the entire LO (with all the pages ) an
asset?? <br><br>
A: The package you produce is a SCO. It is really the launching
HTML page. Everything else are assets (in SCORM speak). The scorm
manifest Xerte produces contains one organisation, with one resource, the
html page. You can create more complex manifests with
Reload,<br><br>
</body>
</html>