Summary
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.

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.

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.

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.

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.

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

• First- and second-line support issues via HELP button;
• Contact point for supplier Structure in case of technical issues (after escalation; 3rd line support);
• Solving content issues at the request of Functional Management;
• Setting up Canvas on request/indication of Functional management.

• Is the only person authorised to submit a proposal for a new master’s course.
• Submits the proposal for the master’s course via the Canvas Factory under the Fontys ICT Hub.
• Ensures the name is correct in accordance with the naming convention.
• Adds the Topic Owner(s) who will be co-developing the course to the Master’s course.
• Remains responsible for the content of the Master’s course, so that the quality of the production courses is guaranteed.

• Has no authorisation to request master courses.
• Responsible for developing and maintaining the master course.
• Responsible for adding and removing developers.
• Has the authority to request a production course via the master course settings.
• When requesting a production course, adds the classes, lecturers (and DLO coordinator)

• Is responsible for populating classes in the student tracking system before these classes can be added to a production course.
• Ensures that sections are created within the production course where necessary

• Use the features of Canvas;
• Students receive education within their classes and courses;

• Use the features of Canvas;
• Students receive education within their classes and courses;
• Lecturers assess students within their classes and courses.

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.

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.

There are various types of courses.

1. - Master Course (Blueprint for a PC)
2. - Production Course (Course for programme implementation)
3. - Public Course Index (Open course containing course content only)

Teaching materials are developed within the Master Course (MC). From a digital accessibility perspective, we work with a standardised, mandatory template. To deliver the course, the Master Course is cloned into a Production Course.

⚠️ The Master Course takes precedence:

Changes are always made in the MC. Copying from a Production Course to a Master Course is not supported.

A production course (PC) is created for each run of a Topic, containing multiple sections for the classes. Here, lecturers can, amongst other things, find their teaching material, post announcements, provide feedback and engage in discussions with students. The course name indicates whether it is a master course (-MC) or a production course (-CMK). When requesting to clone a master course into a production course, the option for a PCI course is supported. This course contains only the course content and is accessible to all ICT students and lecturers.

Communication has been streamlined as follows: Lecturer > developer (TO). 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.

Curriculum Owners (CO) have the right to request MasterCourses (MC) via the Fontys ICT Hub within Canvas. They then add the Topic Owners, who will help develop the course, to the MasterCourse. The Curriculum Owner remains ultimately responsible for the content of the MasterCourse.

The Topic Owner (TO) does not have the authority to create a MasterCourse, but does have the authority to create a Production Course via the MC settings. The Topic Owner is also responsible for adding and removing developers within the MC. The Topic Owner ensures that an up-to-date Production Course has been requested before the start of a semester, to which all target group students have been added.

When requesting the Production Course, the Topic Owner is responsible for linking it to the correct TERM, so that it is given a ‘frozen’ status at the end of the TERM. This frozen status is important so that it can serve as input for the assessment files in Canvas. A PCI is created for each PC; this is a copy of the PC Course, but comprising only the ‘content’. This ensures that lecturers can view the content of each Course, thereby removing the option to request access rights for all Canvas Courses, and this change is reflected in the Canvas authorisation settings.

The DLO manager has general rights within a Production Course and is responsible for populating the classes within SVS before they can be added to a Production Course. The DLO manager also ensures that sections are created for each group where necessary.

When designing and using Canvas, the policy surrounding the Codes and naming information systems should be taken into account.

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.