Get LISNews via email! Enter Your Email Address:
I have a couple of long term projects. One I think is sort of funny... wireless for the library. Why is this funny? Well, half the people that come in the library to use the computers have no idea how to use them. How would they benefit from wireless? And people with laptops... they might like wireless internet, but still insist on plugging in their laptop's power cord, which is against policy.
The second long term project is time access management software.
I had a request to disable the "log off" function on the public access terminals. This leads to the, er, obvious problems. We do need to be able to log off. And we do need to be able to shutdown (and I'd rather have a librarian logging in every half hour than a patron turning the computers on and off, and still needing a librarian to log in anyway). I could enable ctrl-alt-delete on those boxes again, but I don't want every schmuch ctrl-alt-deleting when our network is slow.
The network, my nemesis. I still don't understand, exactly, how the network at the library works. We're networked to a T1 line. Evidently we are behind a firewall that Boston uses. Windows is our responsibility. But I'm thinking we must have a server machine somewhere, although my predecessor says we don't. So where is our filtering software? Also in Boston, because it has to operate in front of the firewall. I think I need to talk to someone and get the low down on exactly how this whole thing knits together, before I start even pondering too deeply the ramifications, good and bad, of time managment software.
We simply can't afford a kiosk or another computer to manage internet reservations, and even if I could somehow rig the print server to act as as server for this as well (I'm not entirely convinced I can't), I don't relish the idea of having the librarians and support staff have to log on to the server to make appointments. The key here is to save time. And a self-service station requires more hardware. If any new hardware comes in, well, it's going to the staff. Or the unfiltered terminal, which is pre-1997.
Client only should work, even though it won't entirely eliminate our handy dandy sign up sheet entirely. Try finding variety in client only systems. And I would like it to work with Horizon, without having to be tweaked in Boston. And I would like it to work on Macs. Tall order. If you know of anything, please, please drop me a line.
My wish list for wireless? Yeah. Well, I'll get to that, when I'm entirely convinced it's a good idea. The assistant director suggested it, and I'm not sure he's entirely convinced it's a good idea either. I would rather be a late adopter and get it right, at least on this, methinks.