Hello, and welcome to my blog where I will chronicle my experiences with the South Carolina State Library. For this internship I was assigned to read a book entitled "Systems Librarian" by Thomas C. Wilson. Although the book was written more than a decade ago the points presented are still valid. How do we as professional librarians weight the organizational mores and the non-degreed technicians vantage points against our own expertise? For example, in the State Library's goal of digitalizing a portion of its holdings yet not all the librarian staff are aware of metadata standards applicable to the document itself or interoperability of these files to the database(s). As a special librarian or information worker of some definition, a systems librarian is a kissing cousin of sorts: they act, as one of a number of interpretations of the role, as liaisons between computer workers and technical staff... a generalist in many ways which must gain an appreciation for both technology and psychology, a 'wearer of multiple hats.'
A keen difference between a systems librarian and a special solo librarian is a system librarian is no soloist, and between training staff and projects that require people to sign off on the completion which might not share my goals. This might be a change from my comfort zone. In the past I felt I could find a creative solution and complete it myself with select consultation and when the project is near finished, simplify to make it communicable. Making my ideas communicable beforehand is the challenge.
I am happy learning how precise technologies function, like how the staff will scan the documents and ascribe standards. I am also exited for this is my first assistantship.
