Since LORS doesn't provide an interface, I created a separate package (that enhances the original random-package; first interface to LORS. LORSm puts together the LORS functions to import, export, manage and deliver IMS Content Packages, IMS Metadata and SCORM compliant packages.
-
To import a content into LORS, you will need to have admin rights to a class/community and the LORSm applet installed (see installation instructions for details). In your class/community admin screen, you will a link to LORS Management Administration:
-
Once you click there, you are presented with all different courses that have been already being uploaded into your class/community instance.
Here, you can manage all courses and see all their resources:
-
+
On Course Structure, you can see the instrinsic characteristics of the package. These characteristic include the type of package, its metadata, the actual file-storage folder where the course is places (and you can access it, just as you would do with any file-storage folder), whether the course contains submanifests, the organizations -their metadata, and the tree(s) of items that belong to each organization.
Note that all items that have references to resources have their correspondent hyperlink to the file(s) described in the resource(s).
. -
+
Hopefully all courses will contain as much metadata as possible, as that makes the course findable and reusable. In order to see the content of the course and its details, LORSm incorporates a very versatily metadata viewer that shows all nine metadata sections as described in the IMS Metadata specifications. (Note version 0.1d does not include online editing of metadata, that will come a bit later).
Although the picture only shows the metadata for the manifest (course) we can browse and view metadata for all elements that are part of the manifest: manifest, organizations, items, resources, and files.
-
+
@@ -100,4 +100,4 @@Using the structure of the IMS/SCORM package, we provide a pseudo course delivery feature that renders the contents of the code to the learner.
Acording to the organizations, items and subitems, we create a tree of hierarquical order similar to an index that the learner can use to browse thru the content. A set of frames that permit easy navigation (although, I don't quite like the frames though) is rendered. The top frames provides the user with information about the course he/she is taking as well as an exit button. On the left, LORSm renders the actual index based on the structural information of the course (again, given by the organizations, items, subitems and their correspondent links to the resources). The central frame is where the content is display when the learner clicks on the item on the left frame (index). And finally the bottom frame shows information about the delivery tool (and hopefully a set of sequencing buttons will be display so items can be automatically sequenced without the need to click on the index).
-
+
cvs: $Id$