Now on ScienceBlogs: Book Review: Don't be SUCH a Scientist

Seed Media Group

Collective Imagination

Christina's LIS Rant

This is my blog on library and information science.

Profile

Christina Pikas Christina K. Pikas is a science and engineering librarian in a special library as well as a doctoral student in information studies.
Any opinions expressed here may not even be her own and certainly do not represent those of any organization willing to be affiliated with her.

Search

Recent Posts

Recent Comments

Archives

Geography

Locations of visitors to this page

Where am I?

N 39 W 76

License

Creative Commons License
This work is licensed under a Creative Commons Attribution 3.0.

« COTS software are not off the shelf or turn-key | Main | OOI Science Community Workshop, Day 1 »

Innovating in infrastructure in a research organization

Category: Information Science
Posted on: November 8, 2009 8:01 PM, by Christina Pikas

How do you balance robust enterprise IT services with computer science as a research area?

This post has been floating around in my head for a while - I even had this started but lost the draft in a tragic overnight OIT loaner laptop reboot. I can't actually answer this question, and trying to has left this draft in my queue for way too long. So this is really some thoughts and more questions.

In a research organization that does CS research, you'll still have an IT department to keep the lights on, so to speak. They run the network, set up new machines, and all of the other typical things.  So you have a series of conflicts at lots of different levels. The CS researchers know how to administrate their own machines and also don't like a lot of imposed security things even if they are needed to keep the organization as a whole safe and, well, manageable. Uniformity is much easier to manage.

IT is inherently conservative. The culture of 'no' and all that. For any new thing, there's a matter of deciding it's worth attention, then gathering requirements, then laying out a project plan, doing the project, testing, etc.  Everything must have a return on investment. Have to baseline this, compare to peers, see what Gartner/Forrester/Burton Group thinks, talk to 3 different vendors. Then maybe in a couple of years a decision happens.  It's easier for the CS people do things themselves, but they're supposed to be working on other things.

The CS folks are more inclined to just build it themselves, but once they've built it, they're not necessarily about the mundane maintenance. According to some of the things I've heard in some of the discussions of software tools for scientists, they often develop these elaborate tools without considering usability and then stop developing them at the prototype stage when the money runs out.

some of the issues:

  • proof of concept vs. robust enterprise
  • functional vs. standards compliant
  • something cool and then move on vs. ongoing support and development

I give up trying to perfect this post, maybe I'll add more later.

Share this: Stumbleupon Reddit Email + More

TrackBacks

TrackBack URL for this entry: http://scienceblogs.com/mt/pings/124328

Comments

1

I love that you are thinking about this. There are so many layers to this issue--I guess what it comes down to is who wants to do the grunt work of keeping the lights on. IT ends up being thankless and depends heavily on tried and true--at the expense of innovation. Completely contrary to what I've always thought the purpose of information technology was.

Posted by: R Yang | November 8, 2009 8:37 PM

Post a Comment

(Email is required for authentication purposes only. On some blogs, comments are moderated for spam, so your comment may not appear immediately.)





ScienceBlogs

Search ScienceBlogs:

Go to:

Advertisement
Enter to win a free copy of The Monty Hall Problem
Visit the Collective Imagination blog
Advertisement
Collective Imagination

© 2006-2009 Seed Media Group LLC. ScienceBlogs is a registered trademark of Seed Media Group. All rights reserved.

Sites by Seed Media Group: Seed Media Group | ScienceBlogs | SEEDMAGAZINE.COM