This page describes the use of Canvas within Fontys ICT and the structure that has been set up to ensure that the use of Canvas runs smoothly.

1. Introduction

Institute-wide implementation of the Learning Management System (LMS) Canvas was completed in the academic year 2019-2020. This means that the entire educational implementation is supported with Canvas.

2. Governance

Within the organisation there are various requirements and wishes for the design of the Learning Management System (LMS). Governance has been explained in more detail at four levels.

2.1. Change Control Board

To place duties and powers within the LMS at the right place in the organisation, the Change Control Board (CCB) Education Programme Team is responsible. The IT Governance page discusses this in more detail.

2.2. Functional management

Functional management is responsible for the interpretation and design of Canvas. The following tasks are roughly defined:

  • Maintaining and exploiting the functionality of the LMS as much as possible;
  • Identifying needs or demands within the organisation about Canvas;
  • Translating this question into solutions by means of further interpretation or change of Canvas;
  • Determining and issuing assignments to ICT suppliers related to Canvas and managing, monitoring and evaluating the execution of these assignments;
  • The communication to the user, management, suppliers and technical management.

2.3. Application and technical management

This is carried out by the team II&A and includes:

  • Creating empty master courses in accordance with the naming conventions specified by Functional Management;
  • Cloning master classes and linking cloned master classes to classes;
  • 1st line support issues via HELP button;
  • Contact point for supplier Structure in case of technical issues (after escalation; 3rd line support);
  • Assigning users to Canvas courses (students via the Student Desk; developers through the team leaders; lecturers via Project Leader Programme Implementation (PLOU)) via Functional management;
  • Solving content issues at the request of Functional Management;
  • Setting up Canvas on request/indication of Functional management.

2.4. Other stakeholders

2.4.1. ​PLOU / PLOO

  • The Project Leader Programme Development (PLOO) / Project Leader Programme Implementation (PLOU) is responsible for the content of the courses in Canvas;
  • The PLOU / PLOO must ensure that courses are developed, requested (via the Canvas portal) and that they are ready on the day that the education requires them;
  • The PLOU / PLOO secures the digital accessibility of the courses.

2.4.2. Developers

  • By order of the PLOU / PLOO, develop a course based on the standard template, taking into account digital accessibility for students;
  • Check that there are no more errors in a course before it goes into production (user test).

2.4.3. Students

  • Make use of the functionalities of Canvas;
  • Students follow education within their classes and courses.

2.4.4. Lecturers

  1. Make use of the functionalities of Canvas;
  2. Students follow education within their classes and courses;
  3. Lecturers assess students within their classes and courses.

2.4.5. iCoP

  • Innovation according to roadmap;

3. MinMax functionality

The MinMax course has been developed in order to achieve maximum profit with Canvas in a short period of time. The MinMax course ensures that every course starts with a uniform intro page with at least one: welcome to the course, learning objectives, learning activities, planning, assessment and a link to the semester guide and a page describing adjustments from a previous implementation. The module page is used to provide insight into the student's learning path. Within the module page, there are also assignments where students can submit their work, so that this can then be provided with feedback using Feedpulse / SpeedGrader.

4. MoreMax functionality

The MoreMax course offers more insight into 'advanced' functionalities, such as peer review, conferences and scheduler. It is not mandatory to use MoreMax functionalities of Canvas, but recommended.

5. Mastercourse versus Production course

There are different types of courses.

  1. Master Course;
  2. Production Course;
  3. Public Course Index.

In the master course (MC), the educational resources are developed. For the execution of the course, the master course will be cloned to different production courses (PC's). A production course is created for each class for the specific semester of implementation (TERM). It is also possible to create a multiple class course (CMK). This allows teachers to find their teaching material, post announcements, give feedback and have discussions with students, among other things. The name of the course shows whether it is a master course (-MC) or a production course (e.g. a production course. -A7). A PCI course will be created upon request to clone a master course for a production course. This course is open to both students and teachers. This gives you the opportunity to look up what will be discussed in a different period of education.

6. Communication structure

Communication has been streamlined as follows: Lecturer > developer (often a vakeigenaar). Questions can be asked by creating a ticket in Topdesk. Every week a Canvas tip of the week will be shared via the Fontys ICT Update. This informs teachers about developments around Canvas.

7. Rights

Developers have teacher rights to the MasterCourse (MC) and can invite third parties for review. With teacher rights you can change the content. Developers receive these rights formally through the existing organisation. When the developer has finished developing and testing, he gives the MC to the PLOU / PLOO. After acceptance, the MC will be cloned, provided with teachers and classes, and the teachers will be given rights as Teacher. With these rights they may only make the following changes to Canvas:

  • Set deadlines;
  • Create groups;
  • Create sections;
  • Add lecturers.

To make other adjustments, they must first contact the PLOU. The PLOU / PLOO is responsible for linking the right TERM to the PC and thus ensuring that the right students are linked to the PC (synchronisation with SVS) and that the PC is given a 'frozen' status at the end of the TERM. This frozen status is important to serve as input for the Assessment files in Canvas. A so-called PCI is also made of each PC, which is a copy of the PC Course but only of the 'content'. This ensures that teachers can view the content of each Course, thus removing the option of being able to request rights for all Canvas Courses and changing this in Canvas' authorisation.

8. Naming convention

When designing and using Canvas, the policy surrounding the naming convention of Fontys ICT should be taken into account]].

9. Files in Canvas and on the Fontys ICT Portal

It has been agreed that semester guides, presentations and other documentation of your choice (to be assessed by the PLOU) will not be embedded in Canvas. These files are kept on the Fontys ICT Portal, where a folder structure has been created (this can be found here ), which follows the naming conventions for canvas courses. This will take care of a number of matters:

  • A course always refers 1 on 1 to the corresponding files. When a course is archived, the references remain valid (“living links”).
  • For those who are not enrolled in a course it is still possible to consult courseware via the Fontys ICT Portal.
  • A not unimportant advantage is that this construction makes it possible to make small changes, errata, addenda, etc. in the files on the Fontys ICT Portal, without having to mutate them in all clones.

II&A has set up a complete document library (called LMC) per semester for all canvas and education related files. When archiving, this library will be placed in Canvas at the same time as the corresponding TERM, so that the relationship between Canvas and the Fontys ICT Portal will remain intact in the future.

10. Test and Beta environment

Every three weeks a complete copy is made from the production environment to a test environment. In this test environment you can try things out on real live data and here you can also create your own course with your own name. Everything that is placed here is really gone after a maximum of three weeks. The test environment is not backed up. In the Beta environment the latest updates of Canvas are placed. Here, new features in Canvas (which are not yet in production) are tested. The Beta environment is reset every week.