The term "Learning Content" has different meanings depending on the user: according to subject, tradition or teacher its meaning may vary from content to module or learning progress. Even its respective size (granularity) or its processing regarding the use of mulitmedia can differ considerably.
In order to be able to create your learning content according to your personal needs OLAT offers you the following possibilities:
You can generate your learning content externaly (outside of OLAT).
Pictures, movies, and Flash contents cause no problems at all when including them in your learning content.
The granularity of your learning content is up to you.
Subject to some condition is the fact that your learning content or part of it has to be stored as HTML file, in IMS-CP format (Instructional Management Systems Content Packaging Format, version 1.1.2) or in SCORM format (Sharable Courseware Object Reference Model, version 1.2).
The following section - Learning Content - will help you and give further information on the advantages of the IMS-CP format.
You can create your learning content with any editor you like (HTML, XML, or text).
OLAT provides you with a basic Open Source editor called TinyMCE. This TinyMCE editor is suitable for generating simple HTML pages, e.g., an introductory page with lots of text. In order to create complex learning contents you may want to use an external editor (for example Dreamweaver or GoLive).
Attention: HTML files created with an external editor should neither be opened nor edited by means of the TinyMCE editor. Already when opening your file certain HTML tags will be overwritten; your file will not be readable any more.
Attention: Safari does not support TinyMCE. If you have a Mac and want to use the OLAT editor you should set up the Firefox browser first.
It does not matter if your learning content contains a single page or Content Packaging: learning contents are single or several HTML documents referencing media files, containing links or even Java scripts. How you design your learning content is up to you. The way you store your files in OLAT is binding. You have two options:
Store your HTML document as a single page along with its corresponding files (e.g. pictures) in your course's storage folder. This can certainly be an index page referencing other single HTML documents. By means of the element "Single file" you link this single file to your course.
Pack your HTML pages with its corresponding files in a Content Packaging. Then import it to your learning resources. The element "CP learning content" will link your Content Packaging to your course.
In general, you can include simple HTML elements (e.g. media files) in your learning content to be displayed in OLAT. Java scripts can be included as well, e.g., in order to generate a pop-up window or if you want to control the presentation of your page via your own CSS definitions. If you want to include Java scripts or use CSS you have to pay regard to certain characteristics in OLAT discussed in this chapter.
There are different kinds of navigation on different levels that are important when presenting your learning content:
Course navigation: maps the processing of your event. You can link your learning content to single course elements of this course or any other existing courses. Further information can be found via the context- sensitive Help in each element on the tab "Description" using the item "Link this course element".
Navigation of single learning modules: Content Packaging, SCORM: navigation results from the composition of your module. Content Packaging offers different possibilities to structure your module, e.g., index page -> subchapter 1 -> page 1, page 2, etc. This navigation is based on its definite data structure. You decide which navigation elements should be used when creating your module in OLAT; use the item "Presentation, presentation options" within the regarding course element in order to be able to configure your navigation.
Navigation within learning contents: e.g. from one page of your Content Packaging to another one within the same Content Packaging.
Each Content Packaging is a self-contained package. It can be exchanged between learning platforms supporting its standard. In order to to be able to guanrantee this interchangeability you cannot set a link from one Content Packaging to another.
Pictures in Content Packaging: You have already created your HTML page having a structured folder containing HTML documents and media data such as pictures (.gif, .jpg). The reload editor helps you to generate your Content Packaging. Your pictures will be packed into that Content Packaging along with relevant HTML files. Further information regarding Content Packaging can be found at: "What possibilities are there to create an IMS Content Package (CP)?"
Pictures on a single page: Store your HTML document referencing pictures in the course storage folder or resource folder along with your picture files (.gif, .jpg). Within your course this HTML document has to be linked from the element "Single page".
Movies in Content Packaging: You have already created your HTML page having a structured folder containing HTML documents and media files such as movies (.mov). The reload editor assists you in generating your Content Packaging. Movies will be packed along with your HTML files in that Content Packaging. For further information have a look at: Creating a CP Manully Using Standard Software Step By Step.
Movies on a single page: Store your HTML document referencing movies in your course storage folder or the resource folder along with those movie files (.mov). Within your course this HTML document has to be linked from the element "Single page".
Flash files in Content Packaging: You have already created your HTML page having a structured folder containing HTML documents and media data such as Flash files (.swf). The reload editor assists you in generating your Content Packaging. Your Flash files will be packed along with those HTML files in Content Packaging. For further information go to: "What possibilities are there to create an IMS Content Package (CP)?".
Flash files on a single page: Store your HTML document referencing Flash files in your course storage folder or resource folder along with those Flash files (.swf). Within your course that HTML file has to be linked from the element "Single page".
"Learning contents" offers you different possibilities to include JavaScript:
in Content Packaging
on a single page.
JavaScript can be added to the contents of a HTML page. When adding JavaScript to the head of a page please note that OLAT will organize what belongs to the head differently. If, e.g., JavaScript (in the head of a single page) generates a pop-up window in a new HTML document you will have to separate the following tags by apostrophes: Script, Head, Body, and Onload since OLAT must not identify these tags (writeln(' <html><he'+'ad>');). This is to prevent OLAT from interpreting the head tag from the head of the main document. That tag should only be interpreted in the pop-up window.
Questions of comprehension: The JavaScript code generated by the test and questionnaire editor in order to pose such a question can be added wherever it is possible.
CSS in Content Packaging: Your CSS files are packed in a Content Packaging along with ordinary HTML files. For further information go to: Creating a CP Manully Using Standard Software Step By Step.
CSS on a single page: Store your CSS definitions in the storage folder of your course along with your single page.
How does OLAT react when dispaying a HTML page referencing CSS? In order to be able to display this HTML page within OLAT the system has to reorganize this page. OLAT will show that HTML page as contents. Style definitions set for the tags of body and HTML on that page will no longer have any effect. If there are CSS definitions for elements within those body tags they will be applied.
Tip: If you want to display your document along with some background colour just create a table around the contents of your HTML page (everything between the body tags); then define your colour for that table.
Your learning content has to be an IMS Content Package in order to be suitable for an OLAT course.
Content Packaging (CP) is a standard format of IMS (IMS Global Learning Consortium). Further information can be found at IMS Content Packaging This standard represents an open specification for learning contents and thus enables an exchange of these IMS CP compliant learning contents between different learning management systems.
Storing data as IMS Content Package is easy. You only have to add an extra file to your learning contents (HTML, PDF, pictures, etc.). This so-called description file has the name "imsmanifest.xml" and can be created by means of external editors automatically. Then zip this file along with your learning contents which means converting it to IMS CP format in order to be ready for import into OLAT.
Learning contents more complex than a single file (PDF document or single picture) should be collected and managed in a standardized way. The IMS standard can achieve this with its open, re-usable, and exchangeable Content Packaging format.
A Content Package consists of a data collection in one or more different formats (HTML, pictures, movies, PDF, etc.) tied together and managed by a description file (imsmanifest.xml). This file contains the entire information of that Content Package.
In order to create such a Content Package you do not need special software. The tools required are generally installed on your computer. However, you may want to use additional software to provide you with better results.
Advantages of collecting and describing learning contents via Content Packaging standard format:
A Content Package represents a clear unit that can easily be navigated by the user (e.g. a student).
The reusability of such a Content Package is guaranteed for learning platforms (LMS) supporting IMS CP standard.
Learning units can be better managed and modified via revision control and meta information.
The author is responsible for contents; the standard defines navigation, presentation, and meta information.
You can convert your learning content to a Content Package (CP) using different kinds of software. Either your create your CP by means of a text editor, HTML editor, and a compression utility or you convert your learning content to a CP using special tools such as a combination of a HTML editor and a description file editor (reload editor) or a specific plug-in for the HTML editor Dreamweaver. The following three sections will provide further information.
In this context, standard software means: HTML editor, text editor, and compression utility. Create your learning content using a HTML editor. The description file "imsmanifest.xml" is generated manually by means of a text editor. Then store all files in an archive (zip).
Its advantage is that you will have access to all the necessary tools on almost any PC in order to modify your CP whenever you want to.
Its disadvantage is that a manual creation or modification of the description file "imsmanifest.xml" tends to be error-prone because you have to acquaint yourself with that file's structure first.
The commercial HTML editor Dreamweaver by Macromedia is suitable for a professional design of web pages.
Dreamweaver offers a plug-in to generate Content Packages. This means that you can create your HTML learning content and the description file "imsmanifest.xml" at the same time before packing them into a zip file.
Starting at version 1.1.0, this plug-in operates successfully. You may download it here. Activate the section "Learning" and select "Content Packager for IMS".
The description file editor "Reload" assists you in creating the description file "imsmanifest.xml" via graphic user interface as well as it helps you to modify your contents. You create your learning content using any HTML editor avoiding the reload editor.
You get this reload editor for free. Just download it here and install on your computer.
We suggest that you use this reload editor since it operates simply and safely.
We do not recommend creating a CP manually; using the reload editor or the Dreamweaver plug-in is more efficient. If you want to write your CP nevertheless please find below a short explanation.
You learn how a CP and the description file "imsmanifest.xml" is organized in order to be able to generate such a file yourself. Then you can summarize it along with your HTML pages and pictures to get your own Content Package.
The tools you will need are the following: a HTML editor,e.g., (Mozilla Composer), a text editor as well as a compression utility (ZIP format).
Download our example CP and unpack it. You will find that example with the title beispielcp.zip in the folder "CP File Beispiel" to be selected from the menu on the left. After unzipping you will see the following files in your archive:
In order to include your own content you have to substitute those HTML documents and the folder "supp" (containing pictures) for your own HTML learning contents. The file "imsmanifest.xml" consists of the necessary content information regarding links and description. The files *.xsd are scheme references that should not be deleted (going into details is not necessary here). Opening the file "imsmanifest.xml" via your text editor will show you a XML file hierarchically structured containing three principal nodes: "metadata", "organisations", "resources". You can also open the file "imsmanifest" via your browser but editing will not be possible there.
The node "metadata" contains information on author, version, language, etc.
The node "organisations" consists of elements regarding contents; these elements contain a reference to physical resources.
The node "resources" contains entries on each resource (here: HTML pages).
Substituting HTML files and pictures for your own and adapting the file "imsmanifest" to your elements will enable you to create ordinary CPs in best time. The only important thing is to allocate the elements in "organisations" correctly to your resources in the folder "resources".
If you want to have a look at your Content Packaging from the user's perspective you will have to zip all files (HTML files, unchanged *.xsd files, and the file "imsmanifest") to your archive, upload this new Content Packaging in OLAT learning resources before running your CP.
Pictures not visible when Content Packaging is running in OLAT: Please make sure that your pictures relate to their physical location. If not, those pictures still point to the directory structure of your local computer. The field "Image location" should not contain entries referring to the entire path on your computer. The Mozilla Composer solves this problem when selecting the option "URL is relative to page location".
Error when running a Content Packaging in OLAT: Most of the time the file "imsmanifest.xml" contains an error. Try opening that file via your Mozilla browser or the Internet Explorer: if this is possible without receiving an error message the file "imsmanifest" is o.k. If you do get an error message the browser's report will show you where the problem is to be found in your "imsmanifest" file.
The commercial HTML editor Dreamweaver by Macromedia offers a functional plug-in since October 2004 in order to be able to generate Content Packages. Just download that plug-in here.
In order to install Dreamweaver extensions do the following: Commands -> Manage Extensions (Macromedia Extension Manager) -> File -> Install Extension -> Restart Dreamweaver
How to create a new Content Package:
In the menu, open the command -> "Content Packager for IMS..." -> "New", fill in the necessary information in the window "Enter Course Properties" (see picture) and confirm your entry by clicking OK.
Now you can structure your CP according to your needs ("Add Container...") as well as add resources ("Add Module...")
In the window "Create or Edit Course Manifest" you can add a new element to your CP's hierarchical structure ("Add Container...") or add more content ("Add Module...").
Module ID: definite identifier
Module Title: name displayed within navigation
Files: displayed resources
"New..." creates new HTML files that can easily be edited later on via your Dreamweaver. Attention: if you add more than one resource only the first will be displayed; therefore, the following resources have to be linked to each other.
In oder to generate a new description file you have to choose "Create Course"; if you want to save your modifications select "Update Course".
In order to pack all your files as CP (zip format) finally select "Package".
Further details concerning the Dreamweaver Content Packager can be found when using the plug-in help function: Dreamweaver -> Commands -> Content Packager for IMS... -> Help.
The reload editor that is obtainable for free assists you in creating a Content Package; it supports the creation as well as modification of the description file "imsmanifest.xml" by means of a graphical user interface. In addition, it offers you the option "Preview". You can download this software here. The editor is written in Java and available for all operating systems. It simplifies the process of generating Content Packagings and should be used as often as possible.
However, this editor does not assist you in creating your learning content. After assembling your learning contents in a folder and loading all your pictures in the subordinate folder called "supp" start the reload editor. Then select File -> New -> IMS Content Package from the menu and indicate your folder containing your learning contents.
Now the editor will present itself like the following:
The structure on your right will show you your HTML files as well as the "imsmanifest" file generated automatically. First you should add a meta data element to your manifest file by clicking the right mouse button.
After adding meta data you can edit them by clicking the right mouse button. Indicate important fields such as author or version. Afterwards close the meta data editor and select "ok". Then add your contents elements (e.g. HTMLpages) to your resources using "drag and drop". Drag your elements to the icon "Resources". Now your editor looks like this:
As soon as you have stored all your resources you can begin with structuring them by means of the node "organisations". You can also create sub-nodes and even add more subordinate elements to those sub-nodes. This structure will be displayed later on in your browser. How you name your elements is up to you.
By assigning elements (items) to a reference (referenced element) you link them to a resource.
The preview will show you the following result (click icon representing a green book):
After storing and merging all necessary information you can now zip it (File -> Zip Content Package...) and transfer it as learning resources into OLAT.