LMS image

Why work with us?

Our digital learning team has over 50 years’ experience of delivering leading digital learning platforms with expertise in HE and FE. We have been managing Moodle platforms for over 10 years and helping to improve Moodle and non-Moodle user platforms by offering support, consultation, application development, project work and much more.

Our base service provides a hosted and supported installation of the software. The software is based on a recent, stable release of the open-source learning management system known as Moodle. The service provider has extended and enhanced the core Moodle product with a range of additional tools to improve teaching, learning and administration. We offer a stable platform which can be combined with a wealth of third party plug-ins, themes and support options, enabling you to customise your LMS to meet your specific institutional needs.

We have extensive experience supporting our clients with integration of vital systems including student information systems such as SITS: Vision and iSams, Office 365, Single Sign On (SSO) such as CAS, Shibboleth and Microsoft Azure Active Directory.

Where an existing solution is not available, our team of developers have implemented API & web service developments to support bespoke integration between Moodle and a range of third-party and proprietary software packages. We have also developed Moodle plugins such as OCM to extend Moodle assignment to supporting multiple markers and blind and double marking.

Whatever your learning management system, the digital learning team at CoSector - University of London are here to help with support and advice on a range of products and services that enrich learning and education.

Products and Services

The DevBox service enables the customer to engage in development and customisation of its Moodle service in a dedicated environment securely and reliably hosted by CoSector. The service provides a separate LMS environment which can be regularly synchronised with the code from the main production environment. Within the DevBox environment, the customer may add, remove or modify plugin and theme code as well as make any configuration changes as part of developing new plug-ins and themes for the production service under the provisions of the private theme and tailored service options.

The Pre-Production service enables the customer to provide end users with a preview of upcoming changes to the service. An entirely separate instance of the software is hosted alongside the production service. CoSector will make all changes and deploy all new releases to the Pre-Production instance prior to making them to the production instance. This enables customers to perform a number of key activities including User Acceptance Testing (UAT), training and familiarisation. The service provides a realistic replica of the production service including regular synchronisation of data and learning content.

The Enhanced Reporting service provides sophisticated capabilities for the customer to undertake analysis of, and gain valuable insights from the extensive dataset created by a learning management system. Access to the data is provided via reports accessible through the service or triggered by web service calls. Remote SQL-level access to the underlying database is also provided for more customised reporting requirements.The service separates the data source for reporting and analysis from the production environment so that even the heaviest of reporting needs do not impact the performance of the Enhanced Reporting Service provided to end users.

The Mahara service provides a hosted and supported installation of Mahara Software. The Mahara Software is configured so that it integrates with any Moodle-based service hosted by CoSector.

The Disaster Recovery Service provides an enterprise-class level of assurance with regards to the long-term availability of the service in the event of a disaster that severely affects CoSector’s ability to run services out of its primary date centre in London. If a disaster occurs and the recover process is invoked, the service is backed by a Recovery Time Objective (RTO) of three (3) hours and a Recovery Point Objective (RPO) of twenty-four (24) hours.