WebJunction

In my role as Technology Consultant for the Northeast Texas Library System, I answer a lot of questions regarding the difficulty in maintaining a library network of desktop computers. Many librarians lament that there isn't enough time to react to the constant process of applying critical updates to their Windows™ desktop computers. In most cases, libraries are too small to afford a full-time employee dedicated to the maintenance of the network. Usually one or two librarians must take on the job of maintaining the library network as time permits. Typically, librarians must visit each computer separately to apply the latest update. Although there are software solutions for automating the update process, most libraries are unable to afford them or do not have the knowledge to implement them. Large libraries feel the pinch in their technology budgets just as small libraries do. IT departments must strive to do more work with less staff. Librarians who work with computer networks may wonder: is there another way? I would like to suggest to librarians who find themselves in this situation, that this type of network is simply the wrong type for many public libraries.

First, it’s important to understand that early library computer networks were designed around a host-terminal model. Typically, a server computer did all the work and terminals gave each user access to an electronic library catalog or other resources. The disadvantage was that the user had to learn a menu system that included the proper commands and the system was not always user friendly. The advantage for the maintenance crew was that all maintenance was performed in one place: on the server. As computers became more powerful and readily available, the client-server model became popular.

The client-server model was an attractive alternative and usually included an early version of Windows™. Library users had a more powerful computer at their disposal that was easier to use. The automation vendors began developing for this platform and many libraries chose to move to the new client-server platform. One of the benefits of this platform was that the processing was distributed throughout the network in an attempt to relieve any potential bottlenecks at the server. However, not only was the processing power distributed out to each desktop computer, but also the maintenance was spread out to each desktop. Computer network technicians or librarians, in most cases, discovered that they had to update each desktop computer separately, as well as the server. At first this did not seem like a problem. However, the updating process adds a great deal of cost to the maintenance or cost of ownership.

The alternative to the client-server model and the distributed maintenance that comes with it is referred to as a thin-clients solution. Thin-clients may seem like a throw back to the old days but will actually provide a graphical user interface (GUI) that looks and acts like a modern GUI and give access to all the software and resources you may require, including the electronic library catalog. Simply put, thin-clients involve a host server that is connected to your network of GUI Windows™ terminals. The terminals can be old PC’s that were thought to be outdated and un-useable. If your favorite vendor is Microsoft, you may already have access to a terminal server. Windows™ 2000 includes the Terminal Server software as part of the operating system. Citrix™ is another company that can provide a thin-client solution with any client interface you prefer. There are many vendors that are capable of implementing such a network.

In case you are not convinced, there are several reasons librarians might want to consider a thin-client network.

• When considering technology planning, those old desktop computers do not need to be replaced. They can be used as thin-clients or Windows™ terminals on your new network. Windows™ Terminal Services can be used to provide a modern windows interface to old desktop computers. Desktop computers that formerly ran Windows 98™ could now have a Windows 2000™ interface.
• It may not be necessary to purchase a new host server. An existing server can be upgraded and enhanced with extra memory that appropriately corresponds to the number of thin-clients connected to it.
• If a new server is required, remember a heavy duty server can be purchased for as much as or less than the cost of replacing all those desktop computers. Central administration: Any updates or maintenance occurs at the server, not the thin-client. No more running around to each computer to install the latest critical update. The host/thin-client network can be implemented one piece at a time. For example: libraries with limited budgets can implement the public network first. Then as funds permit, implement another thin client network for the staff instead of replacing desktop workstations.
• Librarians who want to consider the thin-client network, should also discuss these options with their automation vendor. If your vendor does not seem to offer a thin-client solution, tell them that your new long-range technology plan is built around a next-generation automation system that must integrate with a thin-client network. Most automation vendors that are serious about quality service will be happy to work with you.

At the very least, the librarians planning for technology should ask the question: are full desktop computers with a full operating system absolutely necessary for public workstations? I would say not. In most cases, having a fully loaded operating system on a desktop computer is like wearing 14th century armor to squash an ant. Thin-client networks can offer all the functionality found on any desktop computer, including Microsoft™ Office type software, but at a lower cost of ownership.

I don’t know how many libraries will implement thin-client networks in the future. I do know that libraries must use their shrinking automation budgets to fund the development and maintenance of their next-generation library networks. I also know that desktop operating systems, like any consumer product, will continue to be aggressively marketed, replaced and upgraded over time and librarians will continue to deal with these challenges with fewer dollars. It’s something to think about, especially considering the current economic conditions in our country. It may be time for your library technology planning committee to consider an alternative.

Jerry McCulley is a Technology Consultant for the Northeast Texas Library System.   You can reach him at jmcculley@netls.org

This work is licensed under a Creative Commons License.