Skip to content

good practice and innovation
about us infoKits Tools & Techniques Publications Events
You are here: Home » infoKits » Creating an MLE » technology-options » What projects have done

5.6. What projects have done?

5.6.1 Introduction

This section briefly identifies what each of the projects in the MLEs in Higher Education programme did. There is an overall description of each project followed by a description of the systems that they integrated. Further details are then supplied in the key resources and more resources section.

This section draws heavily on the work of Paul Browning and his report 'Technical review of the JISC MLE in HE programme'.

5.6.2 Brief description of the projects

De Montfort University

The aims of the project were to assess the technical and organisational feasibility of integrating multiple technologies into a single managed learning environment at DMU, to develop a model of integration capable of generalisation to other institutional contexts, and to disseminate this to the UK educational community.

The available technologies were assessed. Information was gathered on data flows, user needs, interface requirements using a variety of methods. A prototype system was developed using Java and XML. Users are able to connect to an MLE server via an ordinary Web browser. The MLE server authenticates them and provides them with secure, personalised view of various data-sets and applications, including the University's student information system (course, module and personal information), timetable data, assessment results, news/messages, and key University documents.

User evaluation studies were carried out, and independent experts provided usability and accessibility assessments. Various revisions were made to the system in the light of these.

Assessments were made of the organisational requirements for successful implementation, the ethical and legal implications of extending student access to information, the resulting technical security requirements, and costs and benefits.

When Version 2 of uPortal (an open source portal development toolkit) became available, DMU's in-house system was ported to this. Both systems use similar technologies and architecture, while uPortal offers a more robust, sustainable platform.

The findings of the project were publicised via a Workshop, and through participation in JISC conferences and events. Detailed reports and executive summaries have been produced for each aspect of the work. These are available via the project Web site.

Writtle College GIMIS Project

The project aims to improve the output and dissemination of Management Information Systems (MIS) information throughout the College, reinforcing the College's Information Strategy by providing the ability to create intrinsic streams of information flow.

The primary objective is to create an information distribution system to make available information currently held in disparate systems. Also, the creation of Electronic Data Interchanges (EDI) where appropriate between the main College MIS systems which have little or no inter-system communication.

The production of a 'middleware architecture' and web based front portal called 'StaffNet' and 'StudentNet', will allow for a cost effective solution, ease of access and independence from the underlying system components, ensuring that any required changes, developments or upgrades are effected with minimum disruption to the Generic Integrated Management Information System (GIMIS).

To date, any consolidation of data from these systems is done manually or in a partially automated series of macros. The result is an inefficient use of both time and staff resources. Even if such systems work perfectly, there is a time lag between the data extraction and the final results, and there are no easy ways to verify the results or "automatically" refresh the data.

The primary role of the GIMIS project is to link these systems, to facilitate seamless communication and data sharing. Although the primary aim is to simplify the existing data and management information needs of the college staff and students, this development will inevitably lead to new uses for the data that is held. For further information follow this link to the GIMIS project.

St Andrews University INSIDE Project

The Universities of St Andrews and Durham are currently in the process of responding to the growing need for user-centric campus information services. Staff and students are individuals who play particular roles and hold specific responsibilities within their institutions. Yet they are faced with ploughing through multiple unconnected data repositories in order to satisfy simple queries and accomplish routine tasks. Even then there is no guarantee of a successful outcome. Inappropriate access control mechanisms and the lack of client software deters even the most persevering online users. Numerous ad hoc record systems developed at Departmental level replicate work that is being done centrally, but are not co-ordinated with each other or Central Services.

Perhaps the distinguishing feature of INSIDE within the Building MLEs in HE programme is its recognition that information maintained by Departments, and the work involved in doing so, are important components in the overall institutional information base.

INSIDE has three general goals:

  • development of a model of University information flows and processes based on analyses and formal modeling techniques

  • the generation of user-centric portals for staff based on their institutional roles and responsibilities

  • the piloting the of value-added services based on the analyses of existing processes.

For further information follow this link to the INSIDE project.

University of East Anglia MARTINI Project

MARTINI will provide an integrated information delivery service for students. It will deliver what the students need, where and when they need it. As such it will be the focus of student access to institutional information systems.

Students will have direct, seamless and secure access to all personal data held about them on university databases, combined with easily navigable links to related data of interest to them. A student will be able, for example, enquire about marks gained for course units they have completed, check the timetable for courses on which they are currently registered, view the range of course options open to them and sign up for their preferred options.

MARTINI will develop a web based front end and a set of tools, which will allow the integration of a range of institutional information systems. This information will also be presented to users through a web interface and in text form for persons with special needs.

The system will be database driven to include both static data (e.g. course guides) and dynamic data (e.g. course marks, accommodation information etc.).

In addition to having access to the range of institutional databases, links will be provided to University wide information. It will be possible for users to tailor the front end to their personal preferences. The range of preferences will be decided in collaboration with the students as part of the user involvement in the project. For further information follow this link to the MARTINI project.

University of Sunderland SMILE Project

The project takes the University's learning support systems and its administrative systems and links them together to provide, for our users, a single system that will help students in their studies, tutors in their teaching and administrators in their management.

Ravensbourne College TISR Project

TISR's objective, achieved, was to develop 'a meta-system capable of integrating different software applications that could also work across different platforms and offer the capability of integrating any other arbitrary system resulting from new additional data sources.'

The validating example of the TISR project is a model of the student record. The project shows how a student record can be embodied as an LDAP directory entry, and, using the TISR API, how the LDAP directory can be populated with student records whose individual components are derived from different sources.

5.6.3. What are the projects integrating?

De Montfort University

  • Student Information System,

  • Timetabling System,

  • Key documents (eg. Student Handbook, Regulations),

  • News/messaging system

Writtle College

The College's four primary databases:

  • Finance Resource 32000 (Oracle platform on a DEC Alpha server [True 64 UNIX])

  • Library Dynix (running on an AIX server)

  • Student Records HEMIS (Oracle platform on a DEC Alpha server [True 64 UNIX])

  • Timetabling Facility CMIS (Access platform on a Novell server) In addition to the above, circa twenty five ancillary databases and discrete data sources used throughout the College are also being integrated within the GIMIS core e.g. Locations database, FE Attendance et al.

St Andrews University

School Systems and Centrally Maintained Systems. In particular the exchange and management of data about students and modules. Integrating VLE with IS to form MLE.

University of East Anglia

The system will be database driven to include both static data (e.g. course guides) and dynamic data (e.g. course marks, accommodation information etc.) and will provide access will be provided to the following systems:

  • Student records,

  • Unit enrolments and marks,

  • Course data, down to unit level.

Accommodation records, Debtors and payments data, Library borrower information, IT Service use data, and Timetabling information (when available).

University of Sunderland

  • A Virtual Learning Environment (WebCT) and

  • student records system (SITS) within a portal.

Ravensbourne College

TISR is a lazy meta directory. Its action is to integrate disparate data sources that make up the student record. We have developed sample data providers to this end including: JDBC, LDAP, EJB and XML. In short TISR will integrate whatever you want.

More detailed information on these projects can be found in the Key Resources folder.

Follow this link for key resources for this section (these open in a new window)

Follow this link for more resources for this section (these open in a new window)


Bookmark and Share
If you can read this text, it means you are not experiencing the Plone design at its best. Plone makes heavy use of CSS, which means it is accessible to any internet browser, but the design needs a standards-compliant browser to look like we intended it. Just so you know ;)