RT @rudokemper: Floored and honored to have been invited to give a keynote for the #c4l21 #code4lib conference next Monday. I can't wait to share about our work building open-source tech for communities to map oral histories, and how my journey started in the library + archive space! @code4lib

RT @sf433: Really happy to share, “Dynamic Integration of Discogs Data within a Blacklight Catalog”

From now on I’m going to ask myself, “Can this talk be a poster?” #code4lib

Managing an institutional repository workflow with GitLab and a folder-based deposit system by Whitney R. Johnson-Freeman, @vphill, and Kristy K. Phillips

#code4lib Journal issue 50.

RT @kiru: I forgot to post the call earlier: The Code4Lib Journal () is looking for volunteers to join its editorial committee. Deadline: 12 Oct.
#code4lib

New issue of the The #Code4Lib Journal published. Some terrific looking papers, including a review of PIDs for heri…

RT @kiru: I am very happy to announce the publication of the @Code4Lib Journal issue #47: webscraping…

Librarians are among the strongest proponents of open source software. Paradoxically, libraries are also among the least likely to actively contribute their code to open source projects. This article identifies and discusses six main reasons this dichotomy exists and offers ways to get around them.

Libraries share a number of core values with the Open Source Software (OSS) movement, suggesting there should be a natural tendency toward library participation in OSS projects. However Dale Askey’s 2008 Code4Lib column entitled “We Love Open Source Software. No, You Can’t Have Our Code,” claims that while libraries are strong proponents of OSS, they are unlikely to actually contribute to OSS projects. He identifies, but does not empirically substantiate, six barriers that he believes contribute to this apparent inconsistency. In this study we empirically investigate not only Askey’s central claim but also the six barriers he proposes. In contrast to Askey’s assertion, we find that initiation of and contribution to OSS projects are, in fact, common practices in libraries. However, we also find that these practices are far from ubiquitous; as Askey suggests, many libraries do have opportunities to initiate OSS projects, but choose not to do so. Further, we find support for only four of Askey’s six OSS barriers. Thus, our results confirm many, but not all, of Askey’s assertions.

RT @kiru: The #Code4Lib Journal's issue 46 (2019/4) has been just published: . Worldcat Search API, Go…

RT @mjingle: Who's excited for the next #code4lib conference?! It will be in Pittsburgh, PA from March 8-11. Is your org interes…

When our grandchildren ask about the Great #code4lib IRC Battle of the Tisane, we will serve them both tea and coff…

We're hiring a Digital Technologies Development Librarian @ncsulibraries ! #job #libjobs #code4lib #dlf #libtech

3) All the men who want to preserve the idea of a #Code4Lib discussion space as one that's free of such topics as s…

Code4Lib Southeast happening today! Live stream starting at 9:30am eastern.

#code4libse2019 #code4lib

It occurs to me the #code4lib statement of support for Chris Bourg, , offers a better model…