After 12 years working in libraries I was unable to advance so I
went to library school and got my degree. That was a year ago. I am now
going to school to get a MS in designing databases and systems analysis.
I think what skills you will need as a "Librarian" will depend on
where you work, who you work for, and where you want to end up. I do not
understand how anyone can say "Librarians simply aren't going to be
_doing_ that sort of thing [database design, programming]." How does s/he
know?? In my current position I need SQL to understand the
relational database behind my catalog (Horizon). And I occasionally use
SQL to do more efficiently what I could use the catalog software to do, or
ask the vendor to do. And when I worked for an academic library, I used
MS Access (only b/c Oracle wasn't available) and XML/CSS to publish
records of a collection available in the library. The web page was linked
to a MARC record within the school's catalog.
For some of us, understanding the technologies truly enriches our
performance. For others, designing and programming are already apart of
the job (whether we get the $$ or recognition for it). For others, most
of this has nothing to do with our job. Our competencies are ever changing.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
(My opinion and my opinion alone. Opinions should not be attributed to
the CEAH Library or USDA.)
Cindy Rankin
CEAH Library, USDA-APHIS-VS-CEAH
(email) Cindy.L.Rankin_at_aphis.usda.gov
(catalog) http://ceah.ipac.dynixasp.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> From: Eric Lease Morgan <emorgan_at_ND.EDU>
Most of us couldn't design a relational database if we had to,
and most of us are unable to distinguish the difference between a
database and an index. I'm certainly not saying that understanding
these technologies are the only issues in the creation of "next
generation" library catalog...
>From Heather Yager <heather.yager_at_GMAIL.COM>
...I am currently in library school and receive mixed
messages from advisors and professors on the topic of studying
database design/theory and programming... I hear other
professors saying things like "I don't know why this is even being
taught... Librarians simply aren't going to be _doing_ that sort of
thing [database design, programming]." Meanwhile, I am convinced that the
only way we are going to survive as
a profession and possibly move to the (gasp!) forefront in the
development of information organization tools is if we _do_ learn
these "sort of things", teach these things, design and generally
accept these things...knowledge of database design and programming is
going to be necessary...the contribution of a librarian who
understands computing is invaluable, whether she is directly designing
software or not.
>From Jeremy Dunck <jdunck_at_GMAIL.COM>
...My most enjoyable and productive development has been spent working
with customers who knew
what sorts of problems computers were good for and how to clearly
communicate their needs.You may not really need to get down to writing SQL
to gain that
perspective, ... if you want to start coding, good for you. :)
Received on Wed Jul 05 2006 - 17:36:14 EDT