Off-topic? What automation librarians need to know
Francesco Giacanelli
md1251 at mclink.it
Tue Jan 13 16:17:43 EST 1998
Dear Web4libbers,
I've read with interests the list on the necessary knowledge an automation librarians must have in order to manage the library. The problem I'm actually involved in is the evaluating the software: are there some certain criteria for the evaluation, e.g., of the cataloguing software? Are there priorities in the consideration of the software? Could you advice useful reading (or Internet site about)?
I'm sorry if the question is too general. I would appreciate some consideration.
Thanks in advance
Francesco Giacanelli - Rome, Italy.
>Subject: Off-topic? What automation librarians need to know
>Author: "Lori A. Schwabenbauer; Camden County Library" <LORI at camden.lib.nj.us>
>at Internet
>Date: 1/9/98 1:51 PM
>
>
>This may be somewhat off-topic, but:
>
>At the request of a colleague, I just put together a list of things an
>automation librarian really needs to know. (Web software was included!)
>Anyone else have anything to add? I'd be curious on what you all think.
>Thanks.
>
>The things an automation librarian really should know, in no special order:
> 1. How to communicate library-ese to technical people and tech-ese to
>library people - to put things in laymen's terms
> 2. How to help tech people (and vendors) understand library priorities
> 3. How to get staff to be as self-supporting as possible - and not run
>to you every time any device with a plug is malfunctioning
> 4. How to plan projects to come up with realistic deadlines that take
>into account a sometimes convoluted purchasing process (especially in a public
>setting bound by government purchasing rules), vendor delays (commonplace),
>technical problems (guaranteed), lead time for staff training and an overall
>"comfort margin"
> 5. How to keep automation staff, library staff, customers and others
>informed of upcoming changes in a timely fashion
> 6. How to get buy-in from library staff and customers on proposed
>changes by: good PR and lots of it; getting staff involved in making choices;
>conducting user surveys; keeping a positive attitude
> 7. How to organize and conduct training for library staff on new
>equipment and software (and for customers, unless Reference or another
>department is responsible)
> 8. Technical knowledge: at a minimum, experience using Windows 95 (or
>MAC OS, if you're a Macintosh-only site), printers, modems, MS Office or
>comparable software, your library automation software, Netscape, Microsoft
>Exchange, ftp, telnet, email; experience doing various software installs and
>upgrades; experience with basic hardware troubleshooting; the more knowledge
>about your library automation software and server, the better; the more
>knowledge about networking, especially Windows NT, the better
> 9. How to keep up with trends and new information - how to stay
>connected and network with techies and peers
> 10. How to keep necessary information - documentation, manuals,
>network schematics, vendor catalogs, warranty and repair logs, equipment
>specifications, software and hardware use policies, procedures, instructions, a
>library system disaster recovery plan, emergency procedures and contacts in an
>organized fashion (and make sure you *have* all the above)
> 11. How to work with techies, staff, administration to write a formal
>plan for the future (say, the next 3 years), update it, and keep priorities in
>line while still being flexible
> 12. How to keep your head while all around you, others are losing
>theirs and blaming it on you (basically - how to keep a good perspective on
>things and lighten up - it's a tough job but a rewarding one!)
>
>*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
>Lori A. Schwabenbauer 609-772-1636 x3336
>Supervisor, Automation Services fax 609-772-6105
>Camden County Library lori at camden.lib.nj.us
>203 Laurel Road http://www.cyberenet.net/~ccl/
>Voorhees, NJ 08043 USA Opinions/ideas/gripes are mine.
>*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
>
>
More information about the Web4lib
mailing list