A very popular question this time of year is ‘How do I get started with Canvas?’ a close second (especially from faculty new to Middlebury) – ‘What do I need to put on my syllabus?’ When the Provost’s office shared information about the basic syllabus and expectations for faculty, we took this information and integrated it into our Canvas templates.
What does this mean?
Specifically, we added an “About this Course” page to our Middlebury 12 week Canvas templates that includes all of the text in the syllabus template. In addition, we added the sample syllabus template .doc file to the Canvas templates. This means that you can replace place holder text with specifics for your course, but the structure for your course content is already in place.
What’s included in the Canvas templates?
You can see what the Canvas template looks like by visiting these links: (log in with your Middlebury credentials to view)
First you’ll need to create your blank Canvas site through the course hub. Follow these instructions to complete this step. Note: Do not edit this site until you’ve completed step 2. Any edits completed before importing the template will be overwritten.
Then follow these instructions to import the Canvas template into your course site. (Select the option to Import into Course when prompted.)
What did we miss?
Our hope is to continually improve these templates as we get feedback from faculty, students and staff about different ideas that would make course sites better for learning. So let us know! If you have an idea or suggestion to make these better please let us know by emailing email@example.com. We look forward to hearing from you and hope this helps to kickstart your semester on the right foot!
This is the 11th in a series of blog posts outlining the collaborative process of designing an online course for the first time from scratch. You can read the other posts here.
Meeting 11 was our first multi-day meeting week. During this session the team reviewed the list of questions and missing information compiled by Heather. Several items were placeholders for work that the faculty member was currently working on.
The team had a productive conversation about providing a means to make it easier for students to identify what work had been completed and what still needed to be done. It was determined that any available automated completion settings in Canvas could actually increase confusion, so the team settled on providing a Google sheet checklist that mirrored the components spreadsheet shared earlier in the course. The checklist was an optional support tool to help students familiarize themselves with a more self-directed learning environment. We are excited to collect feedback from students on this method to see if it is effective and helpful in the way that we hope it will be! (Initial feedback was VERY positive!)
At this meeting it was becoming apparent that the course design process was starting to draw to a conclusion which generated a sense of accomplishment in both team members. Although there were still a number of items we hoped to learn from the first participants in the course – we felt confident that we had done our best to try to anticipate sticky points and challenges and to mitigate those challenges.
As we wrapped up our final official meeting, we agreed to keep the lines of communication open, and Heather assured Anne that she would be available should any unexpected design concerns or questions arise.
Now we just had to wait for the start date — onward!
This is the 10th in a series of blog posts outlining the collaborative process of designing an online course for the first time from scratch. You can read the other posts here.
In this meeting we took the temp in terms of where we were in course development timeline and what additional work needed to be completed to get to our end point on time. Heather was able to do a thorough review of two modules so questions about those items were also addressed. The team revisited the checklist to confirm progress. We also submitted additional requests for assistance with:
Transcription of a recorded interview
Support for an in-person tech session
Help from a student intern to review course content
In preparation for the next meeting Heather spent the following week working her way through the course and came up with the following list of outstanding questions and to-do items. We considered this our first copy edit review of the course content.
Added links to assignment guideline docs from the About this Course grading section. – Is this ok?
What would you like to do about the Quest activity? (This activity was designed to take students on an active tour of the course where they had to discover different info in the course.)
Items at end of module 1 (This referred to additional content in draft format that were awaiting finalization of reading schedule.)
Module 4 exit ticket – how do you want this to be submitted? (via Canvas assignment?)
Consider suggesting to students that they start a new thread for each discussion group – Module 4 discussion
Items at end of module 5 (This referred to additional content in draft format that were awaiting finalization of reading schedule.)
Entrance ticket for module 7 is the assignment for module 6 – or is it supposed to be the wiki here? (Checking links is a crucial part of the final steps of hybrid course development.)
Needs to be done
Exit ticket for module 2
Add link to this reading in module 5 – Visualizing qualitative data in evaluation research. New Directions for Evaluation, 139, 53-71.
Figure out how the Storytelling with Data links and info (library resources) should be managed
This is the 9th in a series of blog posts outlining the collaborative process of designing an online course for the first time from scratch. You can read the other posts here.
In between meetings 8 & 9 the team re-connected with the media development specialist to fine tune the workflow for how videos could be edited with the support and advice of the media specialist. Video will be used minimally in the course so the team did not believe it would take up a great deal of time to do this. The minimal use was intentional given the time frame for development and launch of the course.
During meeting 9 Anne shared challenges she was continuing to face with getting access to an ebook for the course. The library believed it would have this accessible by the time the course began, however the faculty member felt that until this was confirmed as well as the ability for multiple students to access the ebook at once, she was tied into developing a mirrored reading/resource list that could be used if this option fell through. The team decided that a good interim step would be to place additional readings into a “supplemental resources” section within each module so that the work of locating the resources would still benefit the course even if they were not used as the core texts. Together the team also brainstormed using this section as an invitation for students to suggest other resources that they found over the course term.
Lastly, the team discussed the way in which course development had migrated from the faculty member’s core documentation in Google Drive to content being added directly into Canvas. There was some concern about not having this content in a non-Canvas format so Heather shared some export options including the ePub export which (at the time of this writing) was still in beta. Heather tested out the export which included an epub and a corresponding zip file which included other files that had been uploaded to the Canvas site.
This is the 8th in a series of blog posts outlining the collaborative process of designing an online course for the first time from scratch. You can read the other posts here.
During the session the team met with four other participants to test out the functionality of Zoom. Anne planned to use Zoom for a once-a-week in-person meeting with the course participants. Functionality that she hoped to test included how to raise hands, chat, share documents, break into break-out rooms, and return from the rooms.
During the course of the testing we learned about the importance of logging into Zoom before entering the room. (Without logging in you won’t have the facilitator controls!) Also – Anne was pleased with the ease with which she was able to move between break out rooms to check in on conversations.
During this session we also tried out using an external tool called PearDeck as a part of the Zoom session. After carefully reviewing the functionality against what was possible in Zoom, Anne decided that tools within Zoom would work best for the class’ needs.
By the end of the session Anne was feeling much more comfortable navigating in Zoom and managing the class through the interface. Heather used the session to construct a Zoom testing checklist to refer back to in future Zoom testing sessions with other faculty members. This process worked towards the Digital Pedagogy & Media group’s goal to systematize some functions of their work that would be repeated over the course of transitioning content into a new medium.
One last simple design task was integrating a link to Anne’s Zoom room into the side menu in Canvas. We did this using the redirect tool in Canvas. I’ve included a video tutorial below to explain how to do this. Please note that any external apps that require student interaction need to go through an ITS security review before they are used in the classroom.
This is the 7th in a series of blog posts outlining the collaborative process of designing an online course for the first time from scratch. You can read the other posts here.
The first item on our agenda was to iron out details about the grading scheme and assignment category setups to make sure that they would function as Anne was expecting. We found that Canvas grading schemes work very well with traditional percentage ‘buckets’. Below is an example of percentage buckets, however please note these were not used for Anne’s course:
Papers = 20%
Exams (3) = 60%
Participation = 20%
However, faculty who are interested in offering extra credit, the opportunity to drop the lowest grade in a category, or any other adjustment that would not necessarily apply to the full class will not find this functionality within the Canvas gradebook. In these instances we suggest faculty use an outside tool for grade calculations. (DLINQ staff are happy to consult on this topic.)
The team also continued to discuss a weekly communication plan and Anne decided that using announcements would work well. Rather than preparing weekly communications ahead of time, Anne would prepare a template and would write the contents of the message as the course proceeded. Anne felt that this would provide the most flexibility which would be helpful since it will be her first time teaching this course. The team agreed that being able to respond to unexpected inquiries and questions in the weekly announcements would be the best experience for the students and would increase the effectiveness of this modality. Canvas would still allow us to set up multiple announcement messages ahead of time (based on the template) that could be adjusted (but not need to be created) on a week by week basis.
In the next week the team planned to collaborate on a Zoom testing session that would allow Anne to test out different functionalities that she hoped to use as a part of her synchronous sessions. Heather planned to incorporate the outline for this testing plan into a template that is being designed to help structure the development of hybrid course spaces. Some of the items to test included:
This is the 6th in a series of blog posts outlining the collaborative process of designing an online course for the first time from scratch. You can read the other posts here.
At this point in the course development process the instructional designer role (Heather) had shifted to providing more general guidance and support while the faculty member (Anne) focused more intently on loading content into the Canvas course site. As such, Heather adjusted to follow the faculty member’s lead in terms of when the pair meant face-to-face via Zoom and what work took place asynchronously via email.
Anne shared some grade scheme adjustments that needed to be made that the Heather planned to add to the course site after a few clarifying questions were answered. Questions had to do with how participation grades would be calculated on a weekly basis to clarify what items would be graded in Canvas vs. what items would be manually entered in the Canvas gradebook. View more information about how the Canvas gradebook works here.
In addition, Heather suggested coming up with a weekly communications plan that could actually be drafted prior to the start of the class. This concept had been discussed earlier in the development process, but the more extensive content creation provided a better mechanism for following through on this topic. The intention of the weekly communication would be to set up and reinforce the weekly course structure outlined in Canvas to try to avoid any confusion that might surface as the class schedule filled with assignments.
Anne also expressed a need to share assignment details much earlier than originally planned to help the students put all the pieces together — which resulted in some content reorganization. The faculty member was very comfortable with Canvas and completed all of the content edits for the week. Heather found that her time was being spent in a more advisory/clarification role at this point in the process vs. at the start of the project when design skills were most regularly used.
Moving forward the team anticipated meeting on a face-to-face basis more sparingly as needed and increasing the frequency of email or asynchronous communications moving forward so that we could use our time most efficiency.
This is the 5th in a series of blog posts outlining the collaborative process of designing an online course for the first time from scratch. You can read the other posts here.
This meeting occurred after the winter break so Anne had added a lot of materials to the course Canvas site which allowed me to review the sequencing and organization and provide feedback. My suggestions included adding sub headings to the modules page to delineate different groupings of activities and readings within each week. In addition, links to readings were embedded directly in the module page in addition to being embedded in a weekly overview page to both provide students with context for the readings and enable them to access them with fewer clicks in return viewings of the material.
Getting familiar with Zoom
The team also discussed scheduling a Zoom testing session to allow Anne to test out different functionalities in Zoom that would be used during the weekly in-person meetings including breakout rooms and screen sharing. The testing session was scheduled with members of the DLINQ team.
Video editing assistance
Lastly, we discussed Anne’s request to have assistance with video editing from a member of the DLINQ team. This request was submitted to the DLINQ leadership team for review and was approved. Heather suggested that the faculty member discuss captioning options with the media specialist to determine the best and most efficient workflow.
Working with the Library
Lastly, Anne found her collaborative work with the library essential to helping her to put together readings for her students. Staff members were able to help her determine the best way to provide access to materials available in the collection.
Friday & Saturday – Complete assignments to be submitted by 11:59pm Sunday evening.
This information was included on a page titled “About this Course” in the Canvas site under the heading “Structure and Time Commitment”. The professor was also able to share the grading scheme prior to the meeting which allowed me to incorporate this information into the About the Course page as well as create assignment groups to correspond with the different grading category percentages.
It was determined that the synchronous sessions would provide a time when the faculty member could address various topics in a more flexible format that would allow her to adjust and respond to student feedback that occurs earlier in the week through discussion forums, activities, and entrance tickets. The team also formalized the integration of the Zoom room into the Canvas site and discussed setting up a test scenario during j-term that would allow the faculty member to practice using breakout rooms and other Zoom room functionality.
Course content was not yet ready to share so the team decided to focus their work on getting as much of the course structure and repeatable components in place prior to the end of the year so that content could be loaded into the course relatively easily. This shifted the heavier time burden from the end of the year to the beginning of the year. After looking at my projected future workload, I explained that I would still be available to support Anne but since time was budgeted to be more heavily used in 2018, I could not ensure that other priorities might come online at the start of 2019. This conversation highlighted the importance of planning, time-lining, consistent communication, and expectation-setting when working collaboratively on course development projects. In the end, workload did not pose any problems moving forward, but given the unpredictability of each semester – it was important to have this conversation early so there were no surprises.
Anne planned out extensive curriculum development and loading over the course of the month of January and meeting times were set and confirmed. No outstanding action items were set for Heather as most of the outstanding work was to collect course content before additional design work could begin.
This is the 3rd in a series of blog posts outlining the collaborative process of designing an online course for the first time from scratch. You can read the other posts here.
Prior to the meeting Professor Anne Campbell was able to share an outline for the course which broke out course content into weekly modules with different content focuses. Based on this information I focused on pulling apart module 1 and trying to reconfigure the content using online learning components. This resulted in a group of ideas and questions that would serve as the focus of meeting 3. The agenda for meeting 3 was:
Home page view options – Learn more here. We decided to use the pages home page option with a link to weekly module format
Academic honesty guidelines- We created an academic honesty quiz with references to policies at the institute. The Academic Integrity Tutorial is another option designed for Middlebury College undergraduate students.
Support available to students – we built pages for library and technical support into the Canvas template for the course.
Communication plan – we began to brainstorm a communication plan that used a set pattern from week to week
II. Build Out Brainstorm of Module 1
Heather shared ideas and solicited feedback about potential design
During the conversation the concept of entrance and exit tickets came up as a way to manage both formative and summative assessment based on weekly activities. We also discussed having assignments and activities build on one another so that students are given opportunities to refine their ideas and work in the course as they learn more.
Action items for the next meeting included:
Adding a introduction discussion forum to week 1 (Heather)