CopperCore
From Bazaar Wiki
Type of application / System Requirements
We describe here mainly the CopperCore Run Time environment.
It is a desktop application.
The tool is multiplatform. Binaries are available for different Windows and different Unix, including Linux. The source code is available and since it is based on Java it could be easily compiled for other platforms.
In order to use it, the Java 2 Standard Edition SDK version 1.4.2_xx has to be installed in the computer.
The JAVA_HOME environment must be set to point to this installation directory. The JAVA_HOME environment variable can be set as follows:
1) For the Windows platform start the System application from the control panel and select the Advanced tab. Click the ’Environment Variables’ button and add the JAVA_HOME entry.
2) Linux users may add the JAVA_HOME to the .profile file. Add the following commands to the end of this file: set JAVA_HOME=<<location where J2SE SDK was installed>> export $JAVA_HOME
The player module of CopperCore requires Microsoft Internet Explorer 6 or newer. Firefox can also be used, but there might be some small issues.
Purpose
CCRT (CopperCore Run Time) environment allows users to experience IMS Learning Design. In order to be used as a Learning Design server, to enable the execution of Units of Learning (UoLs) with learners, it has got: a database with the information of UoLs and users (learners, teachers); an engine that process the files of the UoL; a player that presents the Unit to the user. Let us remark that different roles (learner, teacher,...) have different visions of the same Unit.
CopperCore is also an IMS Learning Design engine upon which other tools can be built; for instance, Sled, which is described in another sandbox.
The developers remark that CCRT is not intended to be used in a real life deployment, but should be considered an introduction to the possibilities of IMS LD and CopperCore.
What it does
CCRT allows the user to validate and import IMS Learning Design packages (or otherwise said, Units of Learning, UoLs) which can be played as well through an integrated web player.
It is convenient to understand the concept of run, which takes place when a Unit of Learning is executed for a group of students. For example: a Unit such as “ENGLISH: PRESENT PERFECT” could have currently two runs: one for testing, and one for real students, while the next edition of the course, probably with different students and teachers, would need another run
CopperCore provides: - a web page to upload new UoLs, and validate them - a command tool (clicc) to create runs, users and add users to runs - the Learning Design engine itself - a default player
Let us explain this with a bit more of detail.
The process starts from an existing Unit of Learning, created, for instance, with the Reload editor, which is described in another sandbox. The resulting file, which is of zip format, can be validated through CCRT, that is, the correctness of the UoL can be checked; if it is not correct, the “mistakes” appear. If the UoL is not correct, the user can edit it, correcting the “mistakes” by means of RELOAD; and validate it again.
Once it has been validated it can be imported. This results in the Unit of Learning being “published”, which means that now a user could follow the Unit of Learning – that is, perform all the learning activities.
However, before the user can follow the Unit of Learning, one needs to define the users, the roles of the users, … CCRT includes a tool for this process, CLICC. When a set of users, in pre-defined roles, follow a Unit of Learning, this is denominated a run.
How can it be used for creation of OERs
CCRT is not used for creating Units of Learning or content.
How can it be used for consumption of OERs
CCRT is precisely created to “consume” Units of Learning. After the process described above is performed, a Unit of Learning can be run.
How can it be used for reuse of OERs
Units of Learning can only be played through CCRT; the re-use comes from the re-use of the Units of Learning; for example, editing them through an editor such as Reload.
License support
The tool is licensed under the GNU General Public License.
Standards / Compatibility
The tool accepts the Units of Learning based on the IMS Learning Design specification. Recent versions allow to include QTI based material as services - demonstrating the support for services.
HOW TO USE IT
How to install and use CCRT can be found at http://coppercore.sourceforge.net/documentation/ccrt.shtml.
We suggest to go there through the CopperCore project page: http://www.coppercore.org
This is the best description, and would be updated if the tool changes.
Links / examples / Who is using it
As we have indicated, the main page of the project is : http://www.coppercore.org
The project is a SourceForge project too: http://sourceforge.net/projects/coppercore.
The main contributor has been the Open University of the Netherlands (OUNL). We suggest to go to the project site to get updated information of different developments.
The GTI of the Universitat Pompeu Fabra has been developing tools on top of CopperCore. For instance, a more usable web-based interface for managing UoLs, users, runs, … Contact them through http://gti.upf.edu.
CopperCore has been developed through several projects, where one could name the EU funded Alfanet, a JISC funded project, and the UNFOLD and TenCompetence projects might be relevant as well.
Sandbox
CopperCore can be downloaded from http://www.coppercore.org or http://sourceforge.net/projects/coppercore.
We have indicated above some hints about Java pre-installation. The full CCRT ready to install can be downloaded from http://www.coppercore.org or http://sourceforge.net/projects/coppercore and the installation is very easy. The use of CLICC … is more complex.
Comments / Discussion
The main reference for following CopperCore is the site http://www.coppercore.org, where references to IMS, Learning Design, CopperCore itself, … can be found.
While CCRT provides a way of experiencing IMS Learning Design, the tools it provides are not very user friendly.
Sled provides a more user friendly way of experiencing IMS Learning Design, and it is discussed in another sandbox.
