Gordon, Rachel Singer. The Accidental Systems Librarian, Medford, NJ: Information Today, Inc., 2003.
Rachel Singer Gordon’s The Accidental Systems Librarian, is intended to be a basic guide to the various duties that systems librarians undertake. The title of the book comes from the fact that many librarians find themselves taking on systems duties without any formal training. Gordon begins her treatment by listing many of the duties that systems librarians might undertake. These can involve anything from installing hardware to networking to dealing with vendors to being the point person for digitization projects. Because of these varied duties, selecting a title for a systems librarian can be difficult, and the titles for systems librarians are often varied. She notes that the technical aspects involved in systems librarianship tempt some to leave the systems element to those who have an IT background rather than librarians. She says this is a bad idea because librarians understand the needs and vocabulary of other librarians. The librarian does not learn the IT vocabulary naturally, but it is usually easier for librarians to pick up systems language than vis versa. In essence, the systems librarian becomes a liasion between the library, the library administrator, new staff, and the IT department. Gordon also suggests that systems staff should develop documentation of systems tasks and that libraries develop a set of competencies for the systems libararian, and a set of competencies for the library staff. The New Jersey Library Association offers one example of such competencies.
Gordon provides a good overview for the categories of computer knowledge a systems librarian may need. These include an understanding of Microsoft software, Macintosh, Open Source software, networking, web design, intergrated library systems management, troubleshooting, programming, security, and antivirus. She also suggests that a systems librarian should be active in organizing knowledge. Organizing knowledge involves such things as inventorying computer equipment, compiling various types of statistics for the library, and keeping up with licensing, support information, and systems documentation.
Gordon also says that a librarian’s background provides a good background for library systems work in yet another way; the librarian is familiar with methods for researching. This ability helps in systems work because almost every problem systems librarians encounter requires them to look for an answer. At times, this requires a librarian to look in multiple places. This method applies to repairs, troubleshooting, and purchasing. Likewise, librarians are used to having to ferret out the exact piece of information that patrons want. This should enable them to help customer service representatives know exactly how to help them. They should be prepared with detailed information regarding the issue that necessitated their call.
Gordon encourages systems librarians to pursue numerous avenues of social networking to assist them in their work. These avenues include listservs, associations, conferences, informal networks, and collaborative projects. Developing such contacts will be useful when troubleshooting problems or evaluating products. It also gives the systems librarian a chance to assist other librarians in their work.
Gordon’s chapter on instruction techniques offers several helpful tips. First, she points out that systems librarians often are responsible for instructing both staff and patrons to use technology. For patrons, this can include instruction on how to use Microsoft Office products, the OPAC, databases, or any number of other technologies. For staff, the list can include all of these plus any software used in the course of work in the library. Gordon says that any instruction should be brief, simple, applicable, and to the point. Whether one is instructing patrons or staff, the practical advantages to learning the lesson should be patently obvious. Classes can be formal if the library has a computer lab, but may need to be informal if it does not. Systems librarians should take whatever opportunities they have, even if they are one on one, to offer technology instruction. Gordon takes a similar tack with education for systems librarians. She notes that often libraries are on a tight budget and do not have the financial ability to provide formal education for systems librarians. In such cases, systems librarians may have to look at alternative methods for education, including conferences, workshops, books, and web based training. The final two chapters offer helpful suggestions on how one can plan for various technology changes and how one can proceed in his or her systems librarian career.
The Accidental Systems Librarian is an invaluable (at least for me, at this time in my career) work for anyone who finds themselves in such a position. Gordon’s book is not just a basic overview of the systems librarian position. It is a resource builder. The websites, articles, and books she cites within the book serve as a veritable toolbox for the librarian with systems responsibilities.