JISC: Tools Integration Project
Final report (draft v.1.5)
Author: Howard Noble (comments and enquiries welcome)
Last edited: July 20, 2005
Recent updates:
31/5/2005: feedback from ExcelSoft India during implementation
The project would like to thank the JISC DeL eTools Programme for funding and supporting the project.
The project was a collaboration between six groups:
We would like to thank the following individuals: Ernie Ghiglione, James Dalziel, Ajay Kulkani, Tejaswi VK, I. Prabha Haran , Robert Gilks, Katharine Lindsay, Joseph Talbot, Andrew Logue, Gustav Delias, Alex Smith, Meghadri Ghosh, Tim Torgenrud, Jalshan Sabir, Vivien Sieber, Robert Sheratt, Richard McKenna and Steve Jeyes.
The JISC E-Learning Framework (ELF) is a mechanism for coordinating the effort of software developers in the creation software that supports learning and teaching. The ELF provides a vocabulary for talking about technical implementations and a technical framework for supporting e-learning software developments. The framework recommends open source development and the use of interoperability specifications.
Development teams should use specifications such as those distributed by IMS, NISO and OASIS to enable the software they are creating to exchange data objects (e.g. IMS content packaging specification) and expose and consume services according to the concepts behind the web service model.
The Tools Integration Project (TIP) focused on integrating software according to this software development paradigm. Specifically the project has integrated:
This practical exploration to building integration points between software components has allowed the teams to better understand how to move forward with this general approach to providing and consuming services between software artefacts.
Such integrated environments will allow teachers and learners to develop coherant diversity (Scott Wilson, 2005) in their use of technology.
This integrated environment will be evaluated during the JISC eLISA project.
The project will integrate software from three existing projects: AMSTOIA, LAMS and Bodington. Each software system provides functionality that can support a broad range of learning scenarios.
By allowing practitioners to use the different systems as an integrated suite of tools we will be able to support a more diverse range of learning scenarios and teaching styles.
The authorisation environment and web services we develop will allow other institutions to use the TOIA and LAMS web applications from within their own VLE environment(s).Here we outline some of the core services that each system provides internally, the goal of this project is to see how these systems can expose a programming interface to allow other systems to consume these services.
The free (to UK educational institutions) version of the AMSTOIA system supports the following services:
Creation of assessments according to the IMS QTI specification with 9 questions types:
Assignment of assessments to groups of individuals for formative and summative examination (secure environment).
Schedule assessments
Grade assessments
Analyse statistics of questions after an assessment has been taken
Export an assessments as IMS QTI 1.1 compliant files
The LAMS system currently supports the following services:
A tool box that implements a API which exposes the following faciltities:
(For more information about these tools and the rest of the LAMS system download the documentation here).
LAMS allows authors to create sequences that consume these facilities and then assign the sequences to groups of learners.
The LAMS monitoring envionment allows for the orchestration of a sequence by the teacher, this includes participation in discussions and other activities.
The Bodington software is a secure, scalable and open secure environment that provides the following online facilities:
The following summarises the list of acceptance criteria that were defined in the Quality Plan:
The project did evolve from its inception during the proposal writing stage and we document this in the implementation section below.
The project iterated through design and build phases generating use case and functional design documents. We developed use case and UML activity diagrams to focus discussion and arrive at technical designs.
Software was developed on a development version of the latest software builds for each solution. Each partner managed their own development environment. In the case of Oxford developments we published the Bodington code to TIP sourceforge.net periodlically, AMSTOIA have published to the TOIA web site and the LAMS foundation their site with the installers.
The key consideration was on implementing interoperability specifications (e.g. IMS LD, IMS QTI, SRW) and using the web services paradigm to allow LAMS, Bodington and AMSTOIA to provide and consume each others services.
Effective communication has been a top priority during the project because of the large network of related projects that needed to work together. We have used blogs, wikis, email, messenger/ chat, telephone and voice-over-IP (Skype) to form and share ideas. (Open source development is a highly gregarious venture!)
(The short time scales have not allowed us to do formal system testing).
(April 26, 2005 - this section is still under development and we expect to deliver all code by end May 2005).
The project was managed according to a schedule of work packages. Here we outline what has been done by the different groups during each of these activities.
![]() |
LAMS source code is distributed under the GPL open source license and can be downloaded from LAMS International web site . LAMS is a learning design system but is not yet fully compliant with the IMS Learning Design specification. This project has developed the code necessary to export designs compiant with IMS LD Level A. This screen shot also shows how the AMSTOIA software can be integrated into a LAMS sequence. This uses a 'Tools API' that the LAMS foundation are developing. To find out more visit the LAMS foundation web site. |
The goal of this work package was to abstract the authentication and authorisation mechanism away from LAMS. This means that LAMS can be configured to use systems external to itself to provide these services. During this project we implemented the open source WebAuth single sing-on (SSO) authentication mechanism and openLDAP authorisation software to provide these services.
| Documentation | LAMS SSO documentation |
| Code distribution | To be confirmed* |
* The code will be distributed by Oxford University.
ExcelSoft India and the LAMS foundation staff collaborated to build a web service between AMSTOIA and LAMS.
The implementation used a generic tools API specification that the LAMS foundation are currently developing. This specification is being designed to allow more tools to be exposed within the LAMS interface toolbox.
This work has similarities with the IMS Tools Interoperability specification, the OKI OSID work and Business Process Execution Language (BPEL).
| Documentation | LAMS AMSTOIA integration documentation |
| Code distribution | Through main LAMS distribution site. |
Reflection and building a portfolio of artefacts that demonstrate a learners achievements are important aspects of the overall learning experience.
This work package built the facility to export a learners contribution to a LAMS activity sequence as an HTML file.
This artefact could be used as part of a reflective exercise and the exported HTML could be stored in an ePortfolio system to provide evidence of achieving a specific skill level.
| Documentation | LAMS ePortfolio documentation |
| Code distribution |
LAMS was inspired by the Learning Design work that came from the Open University of the Netherlands (OUNL) and is now distributed as the IMS Learning Design specification.
It is important that the other Learning Design authoring and runtime environments (e.g.RELOAD and CopperCore) can inter-operate with LAMS so that they can support the practice of collaborative authoring and sharing designs.
This work package allowed the LAMS foundation to map their activity sequence XML schema onto IMS Learning Design Level A.
The LAMS team have also produced a mapping for levels B and C but further discussion is required with other Learning Design communities to agree on the interpretation of the specification.
The project has engaged with the UNFOLD project and will test how the LAMS IMS LD Level A export works with other software such as the RELOAD Learning Design editor and player.
| Documentation | LAMS LD documentation |
| Code distribution | Through main LAMS distribution site. |
![]() |
Bodington is a secure and scalable virtual learning environment (VLE). Staff and students can create (depending on the permissions assigned to them) multiple choice tests, documents, upload images and text and a range of other resources. To find out more visit the Bodington web site.
|
The Remote Question Protocol (RQP) consists of an interface definition and a web services client-server model SOAP 1.1 RPC binding for the remote processing of assessment items. A fully RQP compliant system must use the specified binding but the interface definition may be used with a different binding in which case the system is said to be only RQP/X compliant, where X is the alternative binding. Indeed the interface definition could also be used as an application programming language for (local) plug-ins to an application.
RQP operates at the single assessment item level but there is limited support for packages of items. The protocol aims to provide a standard item engine interface for clients such as assessment systems, authoring tools, virtual learning environments, etc. to use items in formats which they do not support natively by using the appropriate (possibly remote) item engines. It has therefore been designed to allow for many different item formats with different feature sets. Some extensibility is also provided for through the use of fields identified by URIs so that cooperating systems may use additional features not in core RQP functionality.
Support for item templates is provided and, where appropriate, the production of item clones from them.
(York University's Draft RQP specification currently here.)
This work package implemented the RQP specification in collaboration with York University. The goal was to create a facility within Bodington that allows authors to create content and embed single questions within the content.
This work has also allowed us to look at how we can abstract tools from the Bodington VLE and create a more generic application program interface (API) that can be used to plug other tools into the Bodington environment (in a similar way to the MITs OSID, LAMS toolbox and the IMS Tools Interoperability specification).
(Note: the RQP specification and assessment services that render questions are currently under development so demonstration of the RQP service is not possible as this stage - April 26, 2005).
| Documentation | TIP sourceforge site |
| Code distribution | TIP sourceforge site |
This work package made a simple integration between LAMS and Bodington. Users are able to pass from Bodington to LAMS using the WebAuth system to authenticate and a query to Bodington's user information to perform authorisation.
Authors are able to move to the LAMS authoring environment, create a sequence and get a URL hyperlink pertaining to their sequence that can be pasted into Bodington. Learners will click this link and move directly to LAMS and start the sequence.
| Documentation | TIP sourceforge site |
| Code distribution | TIP sourceforge site |
This work package made a simple integration between Bodington and AMSTOIA.
It exploits the WebAuth mechanism of authorisation and authentication.
Authors can pass from Bodington to AMSTOIA to create an assessment or search for an existing one. They can then copy and paste a URL pertaining to the assessment back into Bodington for the Learner to use to take the assessment.
| Documentation | TIP sourceforge site |
| Code distribution | TIP sourceforge site |
This work package was managed by the Oxford Medical department. The goal was to demonstrate the LAMS and AMSTOIA systems to learning technologists and authors to gain feedback on their design and how they could be used in different contexts.
| Documentation | Workshops and findings |
The designs for learning web resource was built to provide a registry of software tools and facilities that can be used by teachers to support learning activities.
This web resource will be used at Oxford to allow learning technologist to create a registry of tools and designs for learning that can be shared between teachers.
The tools registry allows technical experts and other registered users to collaborate in sharing intelligence on a particular type of software. The community of practice can edit the entries for a tools in the same way that a wiki works to arrive at consensus about software. Users can also create individual annotations and ratings.
The learning designs entry form is one simple mechanism for authors to represent a lesson plan. The approach taken here was to create a form that could be used to capture the detail required to create an IMS Learning Design.
| Documentation | See the site itself |
| Code distribution | TIP sourceforge site |
![]() |
The AMSTOIA software has well designed wizards for creating online questions and assessments. AMSTOIA also allows teachers to set formative and summative assessments and to analyze the results after learners have completed the tests. To find out more visit the TOIA web site. |
This work package allows LAMS to integrate with AMSTOIA. LAMS authors can drag an AMSTOIA activity from the LAMS toolbox into their sequence and then either:
If the author creates a new assessment AMSTOIA will produce a unique URL to the assessment that can be copied and pasted back into LAMS.
| Documentation | Technical documentation |
| Code distribution | To be confirmed |
Search and Retrieve Web Service (SRW) and Search and Retrieve URL Service (SRU) are Web Services-based protocols for querying databases and returning search results. SRW and SRU requests and results are similar, their difference lies in the ways the queries and results are encapsulated and transmitted between client and server applications. (SRW site: http://www.loc.gov/z3950/agency/zing/srw/).
The ExcelSoft India team implemented the API to allow SRW queries to search and retrieve assessment/ assessment question metadata from the AMSTOIA database (repository).
| Documentation | see here |
| Code distribution | To be confirmed (available end May 2005) |
The goal of this work package is to allow AMSTOIA users to preview question types that are not native to the AMSTOIA system. The main reason for this is that many mathematical questions cannot be described using the QTI 1.2 specification (which is native to the free to UK educational institutions AMSTOIA version).
The logical next steps to this work is to:
| Documentation | RQP in TOIA |
| Code distribution | To be confirmed (available end May 2005) |
*This work package was originally documented here (this is the York University JISC Serving Math Moodle instance). As can be seen we have had to change the scope because of the issue that AMSTOIA renders and scores questions on the local machine.
In line with the RQP work the goal of this work package was to expand the types of assessment questions that can be managed using the AMSTOIA system. In this way AMSTOIA can be used as a generic type of assessment repository.
In line with the SRW work AMSTOIA will be able to be cross-searched for any type of question thus making it possible for schools and universities to collaborate in the expensive task for creating good assessments.
| Documentation | To be confirmed (available end May 2005) |
| Code distribution | To be confirmed (available end May 2005) |
To be completed end May 2005.
List any references to the work of others you have cited (e.g. articles, reports, studies, standards), and any explanatory notes. Provide URLs for any materials available on the web.
Include any appendixes that readers will find helpful to understand the work described or the results. For example, include a questionnaire if you conducted a survey, or technical details that support technical development carried out. A glossary of acronyms and technical terms is often helpful.