The process of creating a Learning Design, or "Unit of Learning" (UoL), in the Reload Learning Design Editor is as follows:
The Editing Process
An example Project folder looks like this:
An example Project Folder
The key thing to remember when you use the Editor is that you are not editing the final "imsmanifest.xml" file. There are a number of reasons for this:
<manifest>
<organizations>
<learning-design identifier="ld" level="A" uri="http://www.reload.ac.uk>
<learning-objectives>
<title>My LO</title>
<item identifier="item1" identifierref="resource1"
/>
</learning-objectives>
...
</learning-design>
</organizations>
<resources>
<resource identifier="resource1" type="webcontent"
href="my_file.html">
<file href="my_file.html" />
<file href="assets/image1.gif" />
<file href="assets/image2.gif" />
<file href="assets/bkgrd.jpg" />
<file href="file2.html" />
<file href="file3.html" />
</resource>
</resources>
</manifest>
Note that in the <learning-objectives> element, the <item>
element points, via the "identifierref" attribute
to the <resource> element which has been parsed for
its <file> elements, and which in turn points to the file called "my_file.html".
If you were to edit "my_file.html", by changing, removing or adding
any new links or image files, the resource would have to parsed all over
again.
This is the reason why the Reload Learning Design Editor does not directly edit the imsmanifest.xml file, but instead creates an interim file where the absolute file references are stored. The file parsing is done in the "Export" stage to allow for possible changes in the the content files.
See also:
Reload Learning Design Editor Concepts
Projects View