Index: openacs-4/packages/lorsm/www/doc/creating_package.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/lorsm/www/doc/creating_package.html,v diff -u -r1.2 -r1.3 --- openacs-4/packages/lorsm/www/doc/creating_package.html 17 May 2005 17:03:41 -0000 1.2 +++ openacs-4/packages/lorsm/www/doc/creating_package.html 12 Dec 2006 00:24:48 -0000 1.3 @@ -50,69 +50,69 @@

Once you have open Reload, you have the chance to create a package using IMS Content Packaging 1.1.3 or ADL SCORM 1.2. For our example, we will create a SCORM package.

-

+

Once selected, Reload will prompt you for a directory where to put your course. I suggest you select a new blank directory as shown in the pic.

-

+

Create Metadata for your Course!

Creating basic metadata for your course is critical and a requirement as this information will later be used to determine your package structure as well as the provide information about your course. To do so, you can right-click on the manifest tag and select "Add Metadata"...

- +

But before you go about creating the metadata for your course, you need to provide the Metadata schema and version you will use. Since we are using SCORM packaging, we simply don't have to as there is only one choice. But if we would be using another metadata set, we would be prompt with choices.

- +

Same goes for the Metadata schema version:

- +

Once we added the schema and the version, let's add the course metadata using the Reload's excellent metadata editor:

- +

At bare minimum, add a title for your course. But the more information you can provide about your course, better you make your resources to be findable and, therefore, reusable!. If you have questions about what each of these fields mean, you can have a look at IMS Metadata specifications.

- +

Add Organizations

Now, let's add some organizations. Usually, unless you know why you want to have multiple organization, it is better to stick to one and only one organization. But again, it is upto you how you want to organize your course. Reload allows you to add multiple organizations and LORS also permits their use as well. So, if you are passionate about creating a multiple organization course, please go for it. Otherwise, just create one organization

- +

Add Items

Here's where the fun starts... you can use items to create the structure of your course. Say for example you want to structure your clases based on timeline, then you can create items that indicate the concepts to be learned thru the weeks that the course will take. If that is the case, then you can start creating an item and call it "Week 1"...

- +

And within the Week1 item you can have subitems specifing the concepts or units of learning to be gain that week.

- +

For our example, we have two subitems for Week 1: Lecture and Labs. Note that we can create more subitems within this subitems if required.

- +

You can keep adding Weeks as you please, as well as subitems. For sake of brevity, we'll continue with our example

Adding Resources

Ok, so now we have the structure of our course, but we need to link that structure to content (the actual files that explain those concepts in the structure).

For this, Reload also offers a very cool feature to import your content files all at once. Click on "File" and then proceed to "Import Resources"...

- +

An select the folder where all your resources are... and Reload will add those to the folder where the course is being created.

- +

Take into account that you can do this several times if your resources are scattered around the place.

Now, as you can see, we have added the "Course_Materials" folder to our course. But these have not being added as Resources as yet.

- +

If you just drag-and-drop the week1 folder into the Resources folder on the left box, you will see that Reload automatically links the files in the directory as resources:

- +

Linking Items to Resources

So to recap, we have added the structure of the course (by adding the items) and also the content files (as resources)... so that's all good, but now we need to link both, so we know which content file represents a unit of study (or lecture, or week, etc).

Hence, let's go back to the items that we created... In this case, we click on the Item "Lecture" and to link it to the resource "Course_Materials/week1/LectureNotes.pdf", we simply click on the Referenced element to select the resource that we need to link it to.
In plain English, we are telling Reload: "Ok, so this 'Lecture' Item has to be referenced to the 'Course_Materials/week1/LectureNotes.pdf' resource"

- +

Exporting your Course to a Package

Once we linked all the items we want to link to resources, then we are ready to export all your course structure and content to a single zipped file by clicking on "File" and then "Zip Content Package".!

- +

Choose the name of the file and location to be saved and...

- +

Voila... you have yourself a course


@@ -121,4 +121,4 @@ cvs: $Id$ - \ No newline at end of file + Index: openacs-4/packages/lorsm/www/doc/lors_overview.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/lorsm/www/doc/lors_overview.html,v diff -u -r1.2 -r1.3 --- openacs-4/packages/lorsm/www/doc/lors_overview.html 17 May 2005 17:03:41 -0000 1.2 +++ openacs-4/packages/lorsm/www/doc/lors_overview.html 12 Dec 2006 00:24:48 -0000 1.3 @@ -46,7 +46,7 @@

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.

-

+

LORS Management Features

@@ -65,32 +65,32 @@

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:

-

+

Course Management

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:

-

+

Course Structure

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).

. -

+

Metadata Viewer

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.

-

+

Course Delivery

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).

-

+
@@ -100,4 +100,4 @@ cvs: $Id$ - \ No newline at end of file + Index: openacs-4/packages/lorsm/www/doc/lorsm-rte.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/lorsm/www/doc/lorsm-rte.html,v diff -u -r1.1 -r1.2 --- openacs-4/packages/lorsm/www/doc/lorsm-rte.html 26 May 2005 18:33:19 -0000 1.1 +++ openacs-4/packages/lorsm/www/doc/lorsm-rte.html 12 Dec 2006 00:24:48 -0000 1.2 @@ -104,7 +104,7 @@

packages/lorsm/lib/user-lorsm.tcl
packages/lorsm/www/index.tcl

Design diagram

-

+

To do