Not only is this belittling and embarrassing, it also does not recognize the fact that the present setup was thought to be the right decision at the time it was implemented. A laughably bad automation system is usually not the result of bad decisions, but of good, courageous and far-thinking decisions made a long time ago. Once you have looked at the other departments, it is time to take a look at yours. Position says a lot about how the organization perceives the role of systems in the library and gives you some advance notice of where your boundaries may be. Historically, the systems function often resided in the technical services area, the site of many of the first library automation efforts.
Some libraries put systems in public services in order to focus on public access issues.
A library that gives systems an independent status is more likely to recognize that systems affects and integrates all aspects of the library s operations. If the systems department itself is new, you may be in the enviable position of being able to define its role in the organization and its place on the chart. However, it is likely that many of the systems tasks were performed by others in the organization before your department was created. Rather than being intimidated by this interest, take advantage of it. Use their advice to add to your store of knowledge, and their enthusiasm to energize committees.