March 31, 2010

Out of the box solutions...

Over the past several months it has become apparent that we need a system for tracking issues with electronic resources, i.e. which database is going down for maintenance, which one has a search interface that isn't working, etc. Problems were reported in a variety of ways - via e-mail or a screen shot dropped off on my desk or simply someone stopping by my desk and telling me what wasn't working. And, sometimes, it's the same problem being reported, because there was no central system to track these types of problems.

My first instinct was to use the Track Issues module of my ERM (implementation of which has proven to be klunky beyond my wildest imagination, but that's a different story). The back end interface was cumbersome and provided no way (at least not that I could see) to add updates to individual issues/problems. Also, it would have required the activation of the staff mode, which is not currently used and would most likely not have been embraced by users.

Fortunately, we are using Drupal for our new intranet site and it comes with a support ticket module. It's beautiful. It may not use terminology I would have picked (for example, client area for department), but I was able to basically figure this module out in less than a day. I tested it for a couple of weeks and officially rolled it out for use yesterday. We customized nothing.

I've implemented software in a previous life and understand the ramifications of over customizing applications. This module does the job. Maybe we would have changed a few words here and there, but in the end I didn't think it was worth it. It isn't always necessary to customize something. If it works, just use it and move on.

1 comment:

thesis factory said...

Hi...Nice blog. Really very interesting....!!!


Dissertation binding