As you all know from Monica's message yesterday, we're having problems with eLogs. That'll be resolved soon and I'll let you know when you can get back on.
But we have a bigger issue here. As some of you know, eLogs was created in house years ago, and then significantly altered later by a second in-house person. It has developed many complexities, redundancies, errors, and problems over time, and since we lost our full-time database administrator (Kevin Salazar, who some of you knew), it has been ever harder to keep it going. We have been advertising for a replacement for Kevin but have been having little luck finding someone qualified to fill the position. At the same time, the question arises whether we want to use up a staff position for someone to keep an in-house product going if it may not even be the best tool for us to use.
So I'd like us to begin a conversation about eLogs and the possibility of eliminating it. (Please do not freak out on me, eLogs users!) I know that some of you use eLogs extensively, and many ELI staff do as well. So I need to hear from you about what specifically you use it FOR and how much you do each of those things. ELI staff will be giving me the same information. Once I have a full assessment of its uses, I can begin to effectively explore what software alternatives we could use to allow you to perform those same functions without all of us encountering all the problems and hassles we have with eLogs. Maybe that product doesn't exist, and the answer will be to stay with eLogs. But maybe we can accomplish our tasks with something better and eliminate a lot of headaches.
So please post a comment--what do you use eLogs for and how much? And if anyone has experiences at other colleges or in the private sector with software you think might be useful for these tasks, please post that as well!