OSsite SIG Open-Source Software for Education in Europe

Skip to content.

SIGOSSEE / JOIN

Sections
Personal tools
active users

KN Fast Folders
SIGOSSEE Photos
More...
 

Technical sheet: Claroline 1.7.0

  Technical sheet
Functional features
Didactics/Learning flow management Claroline allows to create "Learning Paths" for the classroom. Each Learning Path can be done with a set of modules (or the entire group of modules) that are within the course. Once the modules are choosen, we can set up the order and the dependences among the included items in a way to realise the didactical approach desired.
Tests and assesment Tests cannot be imported but can be created within the system. Questions with single and multiple choice, with matching answers and with blank fields to be filled in are available . It's possible to track navigation and view tests statistiscs. Data for each object (available tool) can be seen. The same statistics are available for each user. From the version 1.7 tests created within Claroline can be exported in IMS-QTI standard format and used in a different IMS-QTI conformant platform.
Media formats/Authoring Content can be created within the system (it can be viewed as html file), and imported in whatever format (pdf, doc, txt, html, etc). SCORM modules are also supported, and from now on can be exported too. Content can be organized into folders or logically divided into categories. Users can be imported and enrolled to a course using import facilities: the data file (in cvs format) can follow the template provided or can be set up by the administrator.
Course monitoring Users can be enrolled by the the teacher/admin or can enroll by themselves. It's possible to track a lot of informations (particular objects, particular lerners or access time) and the data is presented in tables. Results can also be exported in a cvs format.
Communication The chat functionality is available for synchronous communications; internal email, forums and notes/files sharing can be used for asynchronous communications. Email can be sent also to external addresses. From version 1.7 it's available a new tool: the Wiki, with whom it's possible to realize "collaborative learning". From version 1.6 is available "Assignment" that can be done by student alone or by classroom, and allows to share notes and extra materials. Moreover it's available an RSS feed implementation that allows to provide news to the users.
General look and feel of the system The system makes use of css and it's possible to personalize almost everything, but customizations are at platform level (users cannot choose a different style or change it).
Permissions handling Permissions are handled in a role based style. There are 4 predefined roles: administrator, teacher, user and guest. It's not possible (in an easy way) to modify these roles or to create a new one. The users can be organized in groups.
Other features There are a lot of localizations (almost thirty, among them Arabc, Catalan, Chinese, Finnish, French, German, Italian, Japanese, Polish, Slovenian, Spanish, Swedish, Portugese, and many more) and LDAP is also supported with an extra module. With Assignment tool users can share notes and file among them and with teacher.
Maintainability
Quality of technical documentation There's a Wiki on the Official Claroline web site, where can be found a few useful material just to start the development process. In particular there are tips for coding conventions, how code must be structured, about Claroline libraries and about interface rules.
Scalability There are a lot of Institutions and Universities that are using Claroline. We can estimate that for one istallation more than 5 thousands users and 150 courses can be supported, but it's not clear if the system can easily grow horizontally. The system is very reliable.
Extensibility The code is quite clear and code conventions are normally respected; at the moment, APIs haven't been fully defined and there isn't a plug-in concept documented for functionalities extension (we would prefer a separation between the code in php and the GUI in html). User requirements and bugs are handled within the forum and there is a public CVS system. There are 8 stable versions released.
Adaptability/standard compliance The system is supporting SCORM 1.2 for packaging and even for runtime. It's possible to import and export SCORM contents and it's possible to export tests in a IMS-QTI standard format.
Usability
User documentation Documentation for the users it's available in a lot of languages but refer to old versions. For authors and administrators it's available an updated version that not covers all the aspects but it's quite good.
Generating content The system is really easy to use and it possible to create tests and contents within the environment, and to modify what we have done.
Level of expertise needed For all the system operations and for all the actors involved in the tool, no special level of expertise is required. Everything can be done in a simple way and without any training.
Other The system is easy to navigate, and customizations are possible at platform level. Materials available in the Internet, like SCORM modules, whatever type of document and HTML pages, can be used. The permissions system is not really flexible but it's easy to understand.
Support quality
Note It possible to get support regarding hosting searching for, on the web, the nearest provider, for other services and everything around Claroline it's possible to write to info mail address.
Total cost of ownership
Type of users Schools and Universities are the most predominant users, but also public administrations and companies are in the net. There are a lot of prestigiuos Universities that are using Claroline (the list is on the web site) and the number of users is quite big (many thousands).
Financial stability The project started in 2002 and the core team is composed of about 10 members (not eveybody fulltime employed) but there are a few developers all around the world. The team is funded by the Catholic University of Louvain and the Louvain Foundation.
One time cost There are no special hardware needs. The software requirements are: Apache, MySQL, PHP and some php module (mysql, zlib, preg). To set up a running system it's needed less than one day.
Recurring costs Periodical activities are the same for all web systems: patching the OS or the tools installed. Sometime a system reboot should be done.



Last modified 2005-09-05 02:09 PM
 


Powered by Plone

This site conforms to the following standards: