2014-01-17 3:06PM EST update: For the original article, please see here.
Dean Gentry, Registrar Olszewski, and Dean McKinley made time in their busy shopping-week schedules to meet with us, and we now have a much clearer view of what's going on.
We can propose changes to Yale's policies through a formal procedure. We intend to bring CourseTable through this procedure. Several Yale offices did mishandle the situation, but that's behind us. We cannot guarantee that CourseTable will ever be back up in any form, but we continue to believe that it's a useful tool that students deserve to access.
Despite the actions of the Dean's, Registrar's, and Legal Counsel office, this experience has proven to us that Yalies do care about technology. We've received private and public support from professors in the sciences and humanities.
Harry and I have both learned a lot about how universities function, but we feel that universities can learn from this experience as well.
We're now working with Yale to encourage Yale to:
Make decisions pragmatically, rather than based on just rules.
Yale should have kept CourseTable up until the end of shopping week. While there was a faculty agreement, Yale should have realized that letting the site be until the end of shopping period wouldn't hurt. When rules and stakeholders' (students' and faculty's) wishes conflict, Yale should realize that rules are only there to protect stakeholders. If faculty and students probably wouldn't mind that much, just let it be!
Listen to and communicate with its students.
If we had known about the faculty agreement earlier on, and knew why they were making the decisions they did, we would have been a lot less frustrated. Yale staff are particularly busy this week, but this doesn't mean they can't take 15 minutes and write a statement for us. Likewise, emails to us could say more than "we're looking into it," and rather say "unfortunately, we'd like you to shut down now because of this pre-existing agreement, whose text we've attached." Moreover, Yale said they decided shutting it down wasn't a problem because it only impacted a third of students. That's a third too many for us.
Never block non-malware websites like this.
If there's anything that we hated in this whole episode, it was how Yale blocked CourseTable's IP address and domain without warning. This kind of blocking doesn't work (you can just go to the local coffeeshop), and is very worrying. We hope that Yale will make clear policies, similar to the 1975 Woodward Report, ensuring that network blocks on Yale's network are never used like this again and are only used to protect against malware.
Make it easier to get data and permission.
We had no idea how to get permission to use course data. We knew vaguely that we had to contact some departments somewhere, but which departments? Apparently, for course data, the Dean's Office owns the data, ITS and the Registrar run the systems, and the General Counsel handles the legal aspects. Different people were in charge of copyright and trademark licensing. Getting permission takes weeks, if not months. Yale should embrace open data. We're sympathetic and know that Yale's held back by legacy technology, but we don't need an API to have an open data policy for students!
Inform students how the university works so that students know who to approach and what to expect.
ITS, the Dean's office, Faculty, YCC, and students are all different groups. For example, as mentioned farther down, Yale recommended that we go through the Teaching and Learning Committee and the YCC, which have student representation and direct ties. We didn't know that. A quick web page pointing people to the right parts of Yale to contact and how they all tie together would have been very helpful.
Overall, we hope that Yale will listen to its students. Yale has not guaranteed any results, but we would be very disappointed if Yale does not give authorization to CourseTable, an immensely useful tool, or if Yale doesn't end up better as a result.
In 2001, course evaluations were shown only to professors to improve their teaching. When OCI came out, the faculty agreed to put evaluations online for students, but also agreed on a specific format for them. We still don't know the details, but it seems to forbid displaying averages right with the course title and description. We've asked them for the specific text.
Yale asked us last Friday (January 10) to shut down immediately because we violated this agreement with faculty (of which we were unaware until recently), and they thought there would be minimal impact because only a part of campus was using it. At the time, they said nothing about blocking the site's servers. We said we would comply and shut down. But after looking back at how Yale Bluebook was tolerated and then bought, and the number of users, we also said that we would rather work with them to find a solution.
Apparently, though, the process is supposed to take a while, and involves going through the Teaching, Learning, and Advising Committee, which recommends action after consulting with faculty. Yale then decided that they had to follow the earlier faculty agreement, even considering the student impact, and decided to block and then shut down the website.
Thank you, Yale students and everyone who contacted us with kind words, for your support over the past few days!
For further comment, please email Peter Xu and Harry Yu at firstname.lastname@example.org