Odd Jobs

As I said in my first post on this blog, I work both as a systems librarian and an archivist. The combination sometimes makes for strange weeks, but both duties are enjoyable and rewarding in different ways. This seems particularly evident to me as I reflect on the last week of work.

Last week, I had one of the most enjoyable days of my fledgling career. In one day, I helped a patron identify exactly which 1589 Geneva Bible he had inherited; I worked with another exceptionally rare Bible; I held the first book that ever entered our library; I helped one of our patrons find a much needed resource that he had been unable to find; and I aided a researcher in using a set of Baptist associational minutes which turned out to have a heretofore unreferenced circular letter by the second president of the Southern Baptist Convention. That was a great day!

Yesterday, I had a different kind of day. I sent another librarian several HTML files that would enable her to do something her library director wanted on their website. I changed out a SCSI card. I replaced the computer that was wired to our microfilm scanner. I installed the software that went along with said scanner. I worked with another systems librarian to help identify why our MetaLib and SFX server wasn’t working. I made a really, really long Ethernet cable.

It’s odd. Four years ago I would not have seen myself doing either of these things for a career. Now, I work in two disparate fields in the same job, and I seem to enjoy both in different ways for different reasons. As an archivist, I work one on one with people, pointing them to the resources they need. It’s very rewarding in tangible ways. Patrons generally love you if you are an archivist. I even occasionally get thanked in the front-matter of books.

As a systems librarian, I get the feeling of accomplishment as I make things work using my own ingenuity. No one ever taught me how to change a SCSI card. No one told me how to install software. And probably, no patron is ever going to thank me for what I do with systems (aside from other staff.) And that’s ok. I don’t do my job for thanks. Thanks is nice, but I do what I do for three reasons.

First, God has placed me where I am to do what I do for his glory. When I point researchers to the right resources, God is glorified. When I change a SCSI card so researchers can use microfilm, God is glorified. Second, I do what I do because I like doing it. I enjoy meeting the needs of researchers. I enjoy working with computers and computer systems. Third, I do what I do because I get paid. What can I say? I like to eat!

Despite the fact that these duties are disparate, they do share one commonality. Without someone doing them, no one would get to the resources they need. When our system is running, patrons can find what they need. When I create finding aids, I help patrons find what they need. And maybe that’s the tie that binds the odd jobs I enjoy.