3.2.2 Content Management Systems 

A Content Management System is a repository application used to organise and facilitate the 

collaborative creation of content. The main application of a CMS is often the management of 

web sites and web based content. Like Document Management Systems, CMS systems have 

the ability to store and retrieve electronic files. Functionality is also similar to DMS and 

includes automated workflows for publication processes, version control, powerful search 

engines and content editor.  

3.2.3 Learning Object Repositories 

A Learning Object Repository will often possess the functional qualities of a DMS or a CMS 

such as basic search, advanced search, preview and workflow. However the focus of a 

learning object repository is about the interoperability of the system itself and the content 

within it. This can be achieved through adopting interoperable metadata standards, such as 

the IEEE LOM, and IMS content packaging specifications. In addition the system must be 

able to harvest information from other repositories again using standard technologies such as 

OAI PMH, and ensure that its own content or information about it is exposed through similar 

methods.  

3.2.4 Learning Content Management Systems 

A Learning Content Management System is effectively a combination of a learning object 

repository and a content management system. Its objective is not just the storage and 

retrieval of content, but also the delivery, tracking and relationship management of the content 

and its users. Most LCMSs are vendors of Virtual Learning Environment platforms that have 

implemented learning repository functionality in the background. 

3.3 Why are the lines so blurred? 

Selecting the right commercial system for a learning repository project or initiative is not a 

simple process. Commercial vendors are naturally constantly striving to achieve a degree of 

competitive advantage over other vendors within their market. The area of repository software 

is a minefield of technical jargon. In addition standards and specifications, so essential to the 

objectives of a learning repository, particularly in JORUM's case, are often complex. As these 

standards and specifications are open to interpretation, vendors provide functionality based 

on their own interpretation, which in practice may not deliver systems which are fully 

interoperable. Events such as the CETIS codebashes in the UK help to give vendors the 

opportunity to test the interoperability of their systems behind closed doors, but there are still 

shortfalls with commercial solutions in terms of their . 

Learning Repository initiatives, like those discussed in section 2.3, have demonstrated that it 

is possible to provide a service based on any one of the repository types discussed in 3.2. 

Without a valid evaluation it is impossible to determine to what degree commercial vendors 

actually support standards and specification relevant to learning and teaching. Therefore the 

systems selected for the following section were chosen on their involvement with the 

academic sector and because of existing educational clients. However it is important to 

reiterate that all information was collected through internet research and vendor 

communication which does not form the basis for a true evaluation. 

Page 62 of 84