Our institution currently conducts course evaluations at the end of the summer semester. If your institution has multiple summer sessions (e.g. 2 summer sessions), how do you handle course evolutions and planning?
Do you conduct course evaluations at the end of each session?
When do you start planning?
Do you create multiple projects, or do you create specific times for each set of courses?
We conduct course evaluations under one summer project using the course level dates option to account for all the various start/end course dates. This way the evaluations are done when the course is ending. However, we do not have results available until the end of the semester for all courses. (This last summer semester we had 17 different terms.)
We start planning for the summer semester in April. We set up our administration calendar according to the various term start/end dates. We import the semester data from Blackboard around mid-April. The dates imported from Blackboard for our university need to be edited. Therefore, we adjust the CES start/end dates to the scheduled administration dates.
We do this procedure for all semesters. We do need to manually adjust data. But we chose this method rather than having multiple projects for one semester.
We have two summer sessions, and we create a separate project for each one, for example, Summer XX Nursing Session I and Summer XX Nursing Session II.
Our process is to build each project after the session begins. Once the add/drop period has ended and enrollment has stabilized, we import the course list into the project. The survey is then scheduled to open approximately one and a half weeks before final exams. This timing helps ensure students complete the survey based on their overall course experience rather than on the grade they may ultimately receive in the course.
As a result, Session I and Session II are planned, built, and populated independently based on their respective start dates, add/drop periods, and survey schedules.
We have done it both ways, one project for each summer term and one for all summer terms. Currently, we are doing one for all summer terms, except for our PhD and Study Abroad evaluations. Most of our summer terms are 8 weeks. We don't have a direct connection with Canvas, but run our data through syntax to clean it up, which we do three weeks before each term ends. If the summer term is less than 4 weeks, or if they are internships or co-ops, we do not survey them. Hope that helps.
We don't have too many off-schedule summer term courses (this year it was around 30), so we just manage those with the course level dates. We manually upload the course, instructor, TA, and student data out of our SIS, so it just means a few extra data uploads during the summer term.
For summer semester, we have minimester, summer I, summer II, and full summer. Trimester has term A, term B, and full term. Course evaluations are conducted at the end of each part-of-term, but we only use one project for each calendar (semester and trimester). Since military and law have their own calendars, they have separate projects as well. We use the course dates for each summer part-of-term and open results at the end of the summer term.
We start planning the summer schedule in March because early April is busy with final changes before spring evaluations are uploaded to CES. For summer courses, we usually run on a month long cycle from the time courses are downloaded from Banner until they are uploaded to CES. However, since minimester is only two-weeks long, we usually pull minimester data from Banner at the end of April before the minimester part-of-term starts. This gives us time to send out instructor notices in case there are any instructor errors in Banner that need to be corrected before evaluations open.
Comments
We conduct course evaluations under one summer project using the course level dates option to account for all the various start/end course dates. This way the evaluations are done when the course is ending. However, we do not have results available until the end of the semester for all courses. (This last summer semester we had 17 different terms.)
We start planning for the summer semester in April. We set up our administration calendar according to the various term start/end dates. We import the semester data from Blackboard around mid-April. The dates imported from Blackboard for our university need to be edited. Therefore, we adjust the CES start/end dates to the scheduled administration dates.
We do this procedure for all semesters. We do need to manually adjust data. But we chose this method rather than having multiple projects for one semester.
Hey Chris,
We have two summer sessions, and we create a separate project for each one, for example, Summer XX Nursing Session I and Summer XX Nursing Session II.
Our process is to build each project after the session begins. Once the add/drop period has ended and enrollment has stabilized, we import the course list into the project. The survey is then scheduled to open approximately one and a half weeks before final exams. This timing helps ensure students complete the survey based on their overall course experience rather than on the grade they may ultimately receive in the course.
As a result, Session I and Session II are planned, built, and populated independently based on their respective start dates, add/drop periods, and survey schedules.
Jon
Hi Chris,
We have done it both ways, one project for each summer term and one for all summer terms. Currently, we are doing one for all summer terms, except for our PhD and Study Abroad evaluations. Most of our summer terms are 8 weeks. We don't have a direct connection with Canvas, but run our data through syntax to clean it up, which we do three weeks before each term ends. If the summer term is less than 4 weeks, or if they are internships or co-ops, we do not survey them. Hope that helps.
Hi Chris,
We don't have too many off-schedule summer term courses (this year it was around 30), so we just manage those with the course level dates. We manually upload the course, instructor, TA, and student data out of our SIS, so it just means a few extra data uploads during the summer term.
Thanks,
Greg
For summer semester, we have minimester, summer I, summer II, and full summer. Trimester has term A, term B, and full term. Course evaluations are conducted at the end of each part-of-term, but we only use one project for each calendar (semester and trimester). Since military and law have their own calendars, they have separate projects as well. We use the course dates for each summer part-of-term and open results at the end of the summer term.
We start planning the summer schedule in March because early April is busy with final changes before spring evaluations are uploaded to CES. For summer courses, we usually run on a month long cycle from the time courses are downloaded from Banner until they are uploaded to CES. However, since minimester is only two-weeks long, we usually pull minimester data from Banner at the end of April before the minimester part-of-term starts. This gives us time to send out instructor notices in case there are any instructor errors in Banner that need to be corrected before evaluations open.
Please sign in to leave a comment.