Library Hat Rotating Header Image

IT

Three Recent Talks of Mine on UX, Data Visualization, and IT Management

I have been swamped at work and pretty quiet here in my blog. But I gave a few talks recently. So I wanted to share those at least.

I presented about how to turn the traditional library IT department and its operation that is usually behind the scene into a more patron-facing unit at the recent American Library Association Midwinter Meeting back in January. This program was organized by the LITA Heads of IT Interest Group. In March, I gave a short lightning talk at the 2016 Code4Lib Conference about the data visualization project of library data at my library. I was also invited to speak at the USMAI (University System of Maryland and Affiliated Institutions) UX Unconference and gave a talk about user experience, personas, and the idea of applying library personas to library strategic planning.

Here are those three presentation slides for those interested!

Strategically UX Oriented with Personas from Bohyun Kim

Library and IT – Synergy or Distrust?

In my previous blog post, I asked why libraries are not actively encouraging those who are novice coders among library staff to further develop their coding skills.

I was surprised to see so many comments. I was even more surprised to see that the question was sometimes completely misunderstood. For example, I never argued that ‘all’ librarians should learn how to code (!).  Those who I had in mind were the novice coders/librarians who already know one or two programming languages and struggle to teach themselves to build something simple but useful for practical purposes.

On the other hand, all comments were very illuminating particularly in showing the contrasts between librarians’ and programmers/IT professionals’ thoughts on my question. Below are some of the most interesting contrasts I saw. (All have been paraphrased.)

Librarian (L)
– I am interested in learning how to code but I lack time. Most of all, it is hard to find guidance.

Programmer/IT professional (P)
– There are lots of resources online. Don’t make excuses and plunge in.

L is lost in learning how to code while P thinks everything needed can be found online! Interesting, isn’t it? Ls and Ps are likely to be coming from two completely opposite backgrounds (humanities vs. sciences) and cultures (committee and consensus-driven vs. meritocratic and competitive).

Librarian (L)
– IT distrusts the library staff and doesn’t even allow admin privileges to the staff PCs.
– IT people are overprotective over their knowledge. Not all but many IT tasks are relatively straightforward and can be learned by librarians.

Programmer/IT professional (P)
– Librarians require an MLS for even technology positions. That is crazy!
– You are arguing that librarians can learn how to properly program in their spare time without gaining the proper theoretical understanding of computer science and training in software engineering. That is crazy!

L thinks P should recognize that library staff do work in technology just as IT does and wants P to be more open and sharing instead of being mysterious.  On the other hand, P wants to see L value programmers and IT for their expertise and thinks that an MLS is an unreasonable requirement for a technology position at libraries. I think both parties make excellent points. About the over-protectiveness, I think perhaps it is half true but half likely to be a communication issue.

And here are some of the most valuable comments:

  • Librarians tend to miss that there can be an overlap in the role of IT and that of librarians and regard them as completely separate ones.
  • The management buy-in is important in promoting technology in a library. A nurturing environment for staff development can be quite helpful for the library staff.

I think these two comments are very close to answering my question of why libraries don’t actively encourage and support those among the library staff who know how to code albeit in a rudimentary manner to further develop their skills and apply them to the library context. Although almost all libraries today emphasize the importance of technology, the role of librarians and that of IT, librarianship and technology are often viewed as completely separate from each other. Even when there is an interest in incorporating technology into librarianship, both libraries and LIS schools seem to be puzzled over how to do so.

It is no doubt a tough problem to crack. But it explains up to a certain degree why there is not much collaboration found between librarians and programmers (or IT in a wider sense) at most libraries. Why don’t the library and the IT at a college/university, for example, form a closely-knit educational/instructional technology center?  While reading the comments, I kept thinking about the story I heard from my friend.

My friend works at a large academic library, and the university s/he works at decided to merge the university IT and the university library into one organization to foster collaboration and make the two departments’ operation more efficient. Two departments came to reside in the same building as a result. However, there was so much difference in culture that the expected collaboration did not occur. Instead, the library and the IT worked as they had done before as completely separate entities.

The university administrators may have had the insight that there is an overlapping role between the library and the IT and seen the potential synergy from merging the two units together. But without the library and the IT buying into that vision, the experiment cannot succeed. Even where a library has its own IT department, the cultural difference may hinder the collaboration between the library IT and the rest of the library staff.

How can the gap between librarianship and IT be bridged? As I have already said, I don’t think that the problem is to be solved by ‘all’ librarians becoming coders or IT professionals. That would be implausible, unnecessary, and downright strange.

However, I believe that all libraries would significantly benefit by having ‘some’ library staff who understand how programming works and so all libraries should support and encourage their staff who are already pursuing their interests in coding to further develop their skills and deepen their knowledge. (This is no different than what libraries are already doing regarding their paraprofessionals who want to pursue a MLS degree!)  Even when those staff are not themselves capable of developing a complicated, production-ready software system, they can easily automate simple processes at libraries, solve certain problems, and collaborate with professional programmers in troubleshooting and developing better library systems.

So, my question was not so much about librarians as individuals as about the strategic direction of libraries whose primary concern is providing, packaging, disseminating, and maintaining information, resources, and data. And I am glad I asked my half-baked question. You never know what you will learn until you ask.

Why Not Grow Coders from the inside of Libraries?

How fantastic would it be if every small library has an in-house developer? We will be all using open-source software with custom feature modules that would perfectly fit our vision and the needs of the community we serve. Libraries will then truly be the smart consumers of technology not at the mercy of clunky systems. Furthermore, it would re-position libraries as “contributors” to the technology that enables the public to access information and knowledge resources. I am sure no librarian will object to this vision. But at this time of ever-shrinking library budget, affording enough librarians itself is a challenge let alone hiring a developer.

But why should this be the case? Librarians are probably one of the most tech-savvy professionals after IT and science/ engineering/ marketing folks. So why aren’t there more librarians who code? Why don’t we see a surge of librarian coders? After all, we are living in times in which the web is the platform for almost all human activities and libraries are changing its name to something like learning and ‘technology’ center.

I don’t think that coding is too complicated or too much to learn for any librarian regardless of their background. Today’s libraries offer such a wide range of resources and services online and deploy and rely on so many systems from an ILS to a digital asset management system that libraries can benefit a great deal from those staff who have even a little bit of understanding in coding.

The problem is, I think, libraries do not proactively encourage nor strongly support their in-house library staff to become coders. I am not saying that all librarians / library staff should learn how to code like a wizard. But it is an undeniable fact that there are enough people in the library land who are seriously interested in coding and capable of becoming a coder. But chances are, these people will have no support from their own libraries. If they are working in non-technology-related areas, it will be completely up to them to pursue and pay for any type of learning opportunities. Until they prove themselves to be capable of a certain level of coding, they may not even be able to get hands-on experience of working in library technologies/systems/programming. And when they become capable, they may have to seek a new job if they are serious about putting to use their newly acquired programming skills.

It is puzzling to me why libraries neglect to make conscious efforts in supporting their staff who are interested in coding to further develop their skills while freely admitting that they would benefit from having a programmer on staff. Perhaps it is the libraries that are making the wrong distinction between library work and technology work. They are so much more closely intertwined than, say, a decade ago. Even library schools that are slow to change are responding and adding technology courses to their curriculum and teaching all LIS students basic HTML. But certainly libraries can use staff who want to move beyond HTML.

At the 2011 ALA Midwinter, I attended LITA Head of Library Technology Interest Group meeting. One of the issues discussed there was how to recruit and maintain the IT workforce within libraries. Some commented the challenge of recruting people from the IT industry, which often pays more than libraries do. Some mentioned how to quickly acclimate those new to libraries to the library culture and technology. Others discussed the difficulty of retaining IT professionals in libraries since libraries tend to promote only librarians with MLS degrees and tend to exclude non-librarians from the important decision-making process. Other culture differences between IT and libraries were also discussed.

These are all valid concerns and relevant discussion topics. But I was amazed by the fact that almost all assumed that the library IT people would come from the IT sector and outside from libraries. Some even remarked that they prefered to hire from the IT industry outside libraries when they fill a position. This discussion was not limited to programmers but inclusive of all IT professionals. Still, I think perhaps there is something wrong if libraries only plan to steal IT people from the outside without making any attempt to invest in growing some of those technology people inside themselves. IT professionals who come from the general IT industry may be great coders but they do not know about libraries. This is exactly the same kind of cause for inflexible library systems created by programmers who do not know enough about the library’s businesses and workflows.

So why don’t libraries work to change that?

One of the topics frequently discussed in librareis these days is open source software. At the recent 2011 Code4Lib conference, there was a breakout session about what kind of help would allow libraries to more actively adopt open source software adn systems. Those who have experience in working with open source software at the session unanimously agreed that adopting open-source is not cheap. There is a misconception that by adopting open source software, libraries will save money. But if so, at least that would not be the case in any short tem. Open-source requires growing knowledgeable technology staff in-house who would understand the software fully and able to take advantage of its flexibility to benefit the organization’s goals. It is not something you can buy cheap off the shelf and make it work by turning a key. While adopting open-source will provide freedom to libraries to experiment and improve their services and thereby empower lirbaries, those benefits will not come for free without investment.

Some may ask why not simply hire services from a third-party company that will support the open-source software or system that a library will adopt. But without the capability of understanding the source and of making changes as needed, how would libraries harness the real power of open-source unless the goal is just a friendier vendor-library relationship?

In his closing talk at the 2011 Code4Lib conference, Eric Hellman pointed out the fact that many library programmers are self-taught and often ‘fractional’ coders in the sense that they can afford to spend only a fraction of their time on coding. The fact that most library coders are fractional coders is all the more reason for having more coders in libraries, so that more time can be spent collectively on coding for libraries. Although enthusiastic, many novice coders are often lost about how certain programming languages or software tools are or can be applied to current library services and systems and need guidance about which coding skills are most relevant and can be used to produce immediately useful results in the library context. Many novice coders at librareis who often teach themselves programming skills by attending (community) college courses at night at their own expenses and scouring the web for resources and tutorials after work can certainly benefit from some support from their libraries.

Are you a novice or experienced coder working at libraries? Were/are you encouraged to further develop your skills? If a novice, what kind of support would you like to see from your libraries? If experienced, how did you get there? I am all ears. Please share your thoughts.

——————————

N.B. If you are a formally trained CS/E person, you may want to know that I am using the term ‘coding’ loosely in the library context, not in the context of software industry.  Please see this really helpful post “after @bohyunkim: talking across boundaries and the meaning of ‘coder'” by Andromeda Yelton which clarifies this. Will K’s two comments below also address the usage of this term in its intended sense much better than I did.  I tried to clarify a bit more what I meant below in my comments but feel free to comment/suggest a better term if you find this still problematic.  Thanks for sharing your thoughts! (2/22/2011)