Saturday, November 1, 2008

Educause Notes - Part II

Another interesting session I attended was about student email - specifically, what other colleges were doing in terms of providing email for students. Based upon what I heard here as well as during the Zimbra advisory panel, it seems that many schools are or have been using the open-source Cyrus IMAP along with another open-source package - Horde - for webmail. During this session, representatives from Indiana University, Eastern Michigan University, Reed College and the University of Idaho discussed where they are in terms of student email.

Indiana University decided to allow students to choose which email service they preferred - Google or Microsoft. As of the time the data for this presentation was gathered, 65% of students preferred Google while the remaining 35% preferred Microsoft. In addition, only new students have a choice; existing students have a mailbox on the existing messaging system that they can opt to have migrated. Furthermore, IU's legal counsel examined the contract between Google and the university and concluded that it was only suitable for student mail, not for faculty and staff. Another issue that came up was FERPA - the Family Educational Rights and Privacy Act. New regulations are causing schools to re-evaluate contracts. One thing I found interesting when listening to the gentleman from IU was that IU students are indifferent when it comes to email. I suppose that on a larger level, students at the university where I work might have a similar outlook (note that I have no idea whether this is true or not; I'm just speculating). On a side note, I wonder what differences we might be discern in the attitude towards university/school IT services/systems amongst undergraduate students is versus graduate students. However, based upon my experiences in administering our email system, I am absolutely certain that students at our school do not feel this way. Email is an absolutely critical component in the communications toolkit of all of our constituencies and any extended outages or issues reflect poorly on our department and helps raise the ire of our students.

Someone from Reed College, a small, liberal arts college in Portland, Oregon, spoke about what approach they took to student mail. The only noteworthy thing that this gentleman mentioned was that after doing a cost-benefit analysis of migrating students to another service, they found that the relative costs of doing the migration were pretty low but also that the benefits that they would see would be marginal and because of these facts, they've decided to go with what they have in place (Cyrus IMAP). They are also working on unified communications at Reed, though nothing has been rolled out as yet. In addition, the powers that be at Reed College are open to outsourcing when outsourcing is the right approach for them to take. Finally, Reed College is another school whose legal counsel strongly prefers to keep employee mail in-house.

Eastern Michigan University has decided to go with hosted Zimbra (Zimbra is not doing the hosting though - Merit Networks, based in Michigan, is the hosting service). The choice was made by a committee that was convened for the purpose of choosing a new email system that was scalable, highly available, secure and full-featured. The committee - which was comprised of members of key constituencies across the Eastern Michigan campus - was given a lot of leeway to find solutions. They considered the following options:

1. Google Apps for Education
2. Microsoft Live@EDU
3. Microsoft Exchange
4. Zimbra Collaboration Suite
5. Groupwise

Zimbra was the unanimous selection of the committee. After choosing Zimbra and moving to it, they have found that members of the Eastern Michigan community have liked it very much.

The final presenter was the representative from the University of Idaho. They have a pretty restrictive policy on student mail - students are not allowed to forward their mail and the university has mandated that only the university's email system may be used for official communications. They decided to go with Microsoft Live@EDU since its roadmap met the university's needs for future integration with Exchange. They were able to migrate student accounts successfully with a few minor hiccups along the way. However, they also have some ongoing concerns which, in my opinion, sound pretty major. These include the following:

1. Password synchronization - students have two usernames and passwords for university systems and email
2. Integration with Exchange does not work as had been promoted
3. They've found that renaming accounts destroys mailboxes in some cases
4. Microsoft Premier support is not responsive to the university's needs
5. There are no reporting tools available

Overall, I found this to be an interesting session and found myself curious to find out what the student body at the University of Idaho thinks about the email system provided to them by the university. This is entirely speculative, but I would imagine that the university's email system for students isn't held in high regard. Of course, if the students at the University of Idaho share the same opinion of email as a communications tool with the students at Indiana University, then I suppose that the issues that IT has run into aren't that bad from their perspective. Finally, I thought that forming a committee and populating it with members of key constituencies at the university when making a major decision with respect to services that affect a large number of a university's community is a great decision and, in my opinion, ought to be a no-brainer. From my experience, however, this "no-brainer" is far from a "no-brainer" - I've witnessed situations where decisions that affect a large number of our users have been made with no input from the community when such input was warranted. I wonder how the external perception of our department fares when such decisions are made; I assume that we are not exactly held in the highest regard.

No comments: