CALIFORNIA LUTHERAN UNIVERSITY
ONLINE COURSE EVALUATION TEAM
Date and Location: Monday, August 18, 2008
President’s Conference Room
Time:
11:00 a.m. – 12:15p.m.
Attendees: Cathy Alexander, Jillian Benson, Beth Cooper, Karissa Faulconer, Michael
Graham, Maria Kohnke, Halyna Kornuta, Sean Kreychik, Mindy Wright
Regrets:
Julius Bianchi, Patrick Schmidt
MINUTES
A. Status Review:
1. The team celebrated the Test Launch 
2. Survey Results
1. Karissa shared with us that this is the first time we have ever had a
response from every course offered that was evaluated.
2. Program directors have access to the results for 10 days.
i. Faculty cannot see the results until Friday, Augiust 29.
ii. We can use this information to help them.
iii. We could include in the next email to students some of the
comments they said during this pilot.
3. Survey Process
1. Sean and Michael were asked to share anything that needs to be
worked on. They shared that from their end in ISS, there is nothing that
needs to be worked on, as of now.
2. Maria suggested to send more reminders via email to students.
i. Halyna said that we should review this information regarding
response rate day by day, comparing the days that reminders
were sent out.
ii. We need to remember that these reminders only go to those who
have not responded, and that response rates are much higher on
days that reminder emails were sent.
iii. There were a few students who had trouble logging in. Sean said
that these problems should no long occur; the server has been
fixed.
iv. Freshman Seminar students will need much explanation about
the importance of course evaluations.
1. Maria suggested talking with their peer advisors to get
this communication started.
4. Review Test Group Comments
1. The team reviewed the comments from the CoursEval internal “test”.
2. It was noted that if the email stays on campus we can control it. We
can’t control if it goes off campus to other servers, e.g. gmail accounts.
3. We decided to use “email” instead of “e-mail” (without a hyphen) in our
language.
5. Communication with Laura:
1. We would like to ask about reporting options that are sent to Deans.
2. Check with Laura regarding short term courses, such as weekend.
3. The speed the emails are being sent out should be looked at and we
should check with Laura and CoursEval’s tech team on this.
6. Demo for Faculty and Students
1. Augsburg had a demonstration online that we would like to look into.
i. The team viewed Augsburg’s demonstration.
ii. The web address to get to Augsburg’s demonstration is:
www.augsburg.edu/ctl/evaldeoms/evalreport/evalrept.htm
iii. Sean shared that we have the program that runs this
demonstration, and we already have a license to use it.
iv. Their demo was only 60 seconds long at Augsburg, but for our
purposes it should be at and even faster pace.
v. The team agreed that we’d also like to have some audio
directions in ours.
vi. Sue Bauer will be working on this project.
2. Do we need something like this for students in addition to a faculty
demonstration?
i. There was some discussion regarding whether this would be
necessary.
ii. Maria noted that there are some graduate students who may
need something like this.
B. Next Launch Preparation:
a. Comments from the group:
i. Karissa had a great experience with Laura from CoursEval.
ii. The group agreed that the program did everything we wanted it to.
iii. We expect the deans will love the speed at which they received their
results.
iv. Sean noticed that it takes quite a while for these emails and
reminder emails to go out.
1. How are those emails being sent out from their server? Is the
speed on our end, or CoursEval’s?
a. The speed at which Sean noticed the emails are sent is,
3 emails every approximately 45 seconds.
v. Do we want to pull out the “special status” courses so that we can up
our response rate percentages?
vi. Maria said that there were students who came to her and said that it
was really easy and they appreciated this format.
To Dos:

Halyna to send faculty a request for students to use their CLU
email with instructions on how to forward to another email.


Ask Laura about reporting options that are sent to Deans.
Review results regarding response rate day-by-day,
comparing the days that reminders were sent out.













Check to see if there are any discrepancies within the
responses.
Check the system in all browsers: Safari, Firefox, Internet
Explorer, Opera
Create a demo for faculty and one for students.
Decide if there will be a time when instructors can put their
own questions in the CoursEval system? (e.g. Program
Objectives, etc.)
Link from the box that contains the ‘letter’ and ‘button’ for
CoursEval to be added to the actual email.
The filtering system is working strongly, and will need to be
turned a little lower. The word Assignment showed up as
***ignment.
The appropriate committees should be spoken with if there
are changes to the CoursEval questions. (Teaching and
Learning, etc.)
Can we get on their agenda
What if a student’s computer system crashes while they are
filling out the evaluation? Do they lose their work, can they
go back in?
Set up schedule for 11-week and Full-Semester courses for
Fall.
Check with Laura regarding short term courses, such as
weekend.
Check on system for Travel Courses. We do not want to
neglect these.
The speed the emails are being sent out should be looked at
and we should check with Laura and CoursEval’s tech team.
Pilot Schedule Parallel Dates for 11 week courses
July 9 – Directors email to Summer Term instructors
Mid July – Internal test pilot
July 28 – Email Invitation for students to participate
August 1 – Deploy survey; Rm 106 Humanities Computer Lab available
August 4 – Hard copy of instructions to students
August 8, 12 – Reminder email to students to complete survey
August 14 – Term ends / CoursEval ends @ midnight
August 15 – Grades open for Student Viewing
August 15 – 29 CoursEval results reviewed by Deans / Directors
August 18 – Review process. Decision about CoursEval as vendor
Fall 11 week Program Schedule
Sept 2 – Classes begin
Nov 17 –Term ends