Posts Tagged ‘Amherst’

When a group of Higher Ed CIOs gather, what do we talk about?

Another academic year is coming to an end and these are mostly happy times. Our commencement is still a few days away, but, when I noticed that a friend was off to his son’s graduation at Penn State last weekend, it dawned on me that we are in that season already! I am sure that all those first years who made their college choices are the happiest bunch, dreaming about the college while preparing for high school graduation. I remember those days vividly though it has been a while with our two boys. It is pretty hard for me to believe that this is the third summer for me at Wellesley. Sometimes I feel like I am still settling in – people still have to explain to me certain terms and traditions 🙂

I was invited to go to a gathering of Higher Ed CIOs organized by a company called Consero. I was pretty skeptical about the whole thing. In the end, it was fun and useful. We met for a couple of days in San Diego to discuss various topics that the Higher Ed CIOs are interested in. In many cases, this turned out to be what many Higher Ed CIOs are worried about. Of course there are some who worry more than the others and the worry spectrum is highly influenced by local issues and the type of person the CIO is.

Frankly, though there are some common thread to discussions, the term “Higher Ed” is increasingly appearing to be as challenging as the term “American People”. Private College issues are different from public, large universities are different from small ones, liberal arts colleges seem to worry about completely different things than the rest, so on and so forth. In fact, someone even began making a distinction amongst the liberal arts colleges based on the endowment! The challenge therefore is to pick and choose ways in which you can benefit from these discussions as well as contribute to them in ways that they don’t appear to come from the CIO from a “wealthy”, highly selective, women’s liberal arts college from the state of Massachusetts (and therefore not applicable to the others). Despite all these challenges, we all had one thing in common – we had a lot of fun!

(more…)

We are on Drupal!

Our Drupal installation went live on March 29. Drupal is replacing a web content management system called Bluenog. I made a determination when I began at Wellesley that this is yet another technology where we had to make a decision on what is best for us. The choice was either to stick with Bluenog and adapt ourselves and our needs to what the product demands or find a solution that better matches our needs. No single technology ever matches ALL of our needs, so the criteria was to choose something that covers MOST of our needs. We took a look at whether the current CMS is satisfying the needs of the College and it became apparent that in many areas, which I won’t go into detail here, we were struggling.

I had gone through the same exercise at Wesleyan and Pace in the recent past. At Wesleyan, we were very close to going with Drupal, except, it was not as mature four years ago as it is now. To the disappointment of a few open source fans, we chose a product called Cascade, which is still in use there. At Pace, the product in use was Hot Banana (I have no idea how they pick these names) which everyone was struggling with. Once, the product failed and the site was down. We called support in Canada and we were told that we will receive help for the next 10 minutes and if problem cannot be solved by then, we have to wait for the next morning! And at exactly 5 PM their time, the person said bye and hung up the phone! There was no Hot Banana “community” to seek help from. Thankfully, the company announced that they are stopping further development on Hot Banana (it generally means – “it is being put on life support and is being prepared for a slow death”). We looked at Drupal, WordPress and Joomla  and after a careful evaluation, chose Drupal.

I used that evaluation as the basis for recommending that we move to Drupal for Wellesley. I should say that we received support from almost all quarters fairly quickly. We then began an implementation plan.

(more…)