A position announcement for a Computer Services Librarian we (the
University of Wisconsin) recently cross-posted to LAW-LIB and
TEKNOIDS generated several negative responses to the TEKNOIDS list.
These responses asked
(1) Why do you need a librarian to provide instruction and
computer assistance to faculty, staff and students? and
(2) Why should libraries be managing law school computer
services?
I am posting my reply to both lists and refer LAW-LIB colleagues
who missed the TEKNOIDS responses to the TEKNOIDS archive files on
the Cornell gopher.
Why a librarian?
We thought long and hard at Wisconsin about whether to require an
MLS for this position before launching the search. We ultimately
decided to require an MLS, because we want to stress the
information/reference service aspects of this position: this is
what librarians (as opposed to engineers, computer scientists,
lawyers, etc.) uniquely are trained to do. In particular, we want
someone who can conceptualize computer information services in a
broad context, and fully understand how they fit into a full array
of traditional and online information resources. We also want
someone who is familiar with bibliographic instruction pedagogy, is
sensitive to freedom of information issues and has a public service
orientation. As we fleshed out the job description for this
position, we decided that these aspects were critical, even though
we seek additional qualifications as well. I apologize if the
position announcement fails to make this clear, but I believe the
job description (which allocates 60% to reference and instruction)
may give a better picture of what we are after.
On a related note, this IS a new position: we are not trying to
force new duties into an existing position (as one person
suggested). We come to this search with some experience. We
started up our computer services with a non-librarian who did a
terrific job for us. But when he left, we decided to expand our
computer services and move on to another stage of development.
Thus, we created two new positions: a support technician and the
librarian position we are currently attempting to fill. (These are
in addition to our Automation Librarian who is primarily
responsible for library automated systems.) The support technician
(already filled), assisted by some very good student assistants,
manages most of the technical aspects of this area. The Computer
Services Librarian will oversee this technician (and his student
staff) and emphasize the training and reference aspects of computer
services, but we want someone "with substantial knowledge of and
aptitude for computer technology, particularly microcomputers and
networking," in order to appropriately understand the area he or
she will be responsible for managing. The computer OR law library
experience (which a JD can substitute for), is listed as desirable,
because we want someone who has a track record with some proven
familiarity in this area. A JD would be helpful for the
instructional and reference service aspects of this position, but -
- unlike the MLS -- it should not be misread as required.
Why manage law school computer services?
For a number of reasons, it makes good sense to us for the library
to manage the law school's computer services. First, we are more
dependent on computer services than any other part of the law
school. Our librarians rely on online systems, networks and
electronic information resources to do their work, while the use of
these systems is not much more than incidental to many others in
the law school community. Second, the information delivery
aspects of computer services mesh neatly with the other information
services we provide. As more and more information is delivered in
digital formats, it is helpful to have these two areas tied
together administratively. Third, as a matter of administrative
convenience, it makes good sense to put computer services within
the library, rather than starting up yet another Law School
department reporting to another dean or whatever. At Wisconsin,
for example, it certainly makes more sense to have computer
services within the library hierarchy than audio-visual services,
which is also under the library umbrella but is primarily an
instructional services department. Lastly, at Wisconsin at least,
the library has been the most aggressive developer computer
services and took major steps in this direction long before the
rest of the law school expressed much interest in the area.
We understand that some other institutions have developed computer
services quite successfully using different models. Much depends
on local cultures, individual talents and interests, reads on where
we might all be headed and the amount of budgetary resources that
can be allocated to this area. Our arrangement at Wisconsin seems
to work so far, and we think others should consider going the same
route.
Finally a comment on salaries. We listed a minimum of $29,352 for
this position, because that is the bottom of the range for an
academic librarian at the Wisconsin-Madison campus. We included
this figure, because we are tired of reading other position
announcements that merely state the salary and benefits will be
competitive, without giving any figure or range. Unfortunately,
the minimum figure of $29,352 is nationally competitive -- maybe
that's why other institutions don't generally give this information
at the outset. Under Wisconsin's pay structure, this minimum
certainly would not have been any higher had we decided to make
this a non-librarian position.
At any rate, the minimum salary is merely a minimum. We may pay
more given a candidate with credentials exceeding the basic
requirements, but budget limitations and internal equity
considerations will prevent us from paying as much as we think most
librarians are worth. We trust the listed minimum will at least
alert prospective candidates about what sort of salary range we are
talking about.
With all of this said, I hope this encourages good librarian
candidates to throw their hats into the ring. This truly is a key
position in our library and a terrific opportunity for the right
individual.
This archive was generated by hypermail 2b29 : 03/09/00 PST