As part of the Mellon Foundation grant funding the start-up of LYRASIS Technology Services, LTS is to produce a series of tools that enable libraries to decide whether open source is right for their environments. The grant says:
Welcome to the Disruptive Library Technology Jester. From here you can browse the musings and visions of a library technologist as he walks the fine line between the best of the library profession on one side and the best of technology on the other.
You can navigate through DLTJ several ways. Your first stop might be the introductory material about this blog and the jester himself under the "about" heading to the left. Another way would be to pick a facet below to browse: "by cagetory" for a rough categorization of postings, "by tags" for a finer granularity of topics, or "by date" for a chronological view. Third, use the search box in the left column as a keyword approach to content in DLTJ. And last, recent postings by the Jester can be found below the faceted list.
I hope you enjoy your visit. Please feel free to leave comments where you'd like or contact me directly.
Recent Posts
Teaching Search Engine Literacy with A Google A Day
When this first came out I thought it was a stunningly good way to demonstrate the kinds of search skills that libraries teach patrons when demonstrating how to use the internet. So I sent a message to the generic service address and started a conversation with a product marketing manager at Google. After some back-and-forth with him and other librarians, it does seem like there is a possibility of a really neat collaboration. To start us off, Google put together the information below on how to embed the question in library websites (see below). On a conference call with other librarians we also talked about possibilities like a categorization of questions (so if you wanted a chemistry question or one that uses Google Street View you would be able to find it quickly) and “guest written” questions based off of real life reference interviews.
Seeking feedback on database design for an open source software registry
As part of the Mellon Foundation grant funding the start-up of LYRASIS Technology Services, LTS is establishing a registry to provide in-depth comparative, evaluative, and version information about open source products. This registry will be free for viewing and editing (all libraries, not just LYRASIS members, and any provider offering services for open source software in libraries). Drupal will be the underlying content system, and it will be hosted by LYRASIS.
I’m seeking input on a data model that is intended to answer these questions:
- What open source options exist to meet a particular need of my library?
Fixing a Bad SSH authorized_keys under Amazon EC2
I was doing some maintenance on the Amazon EC2 instance that underpins DLTJ and in the process managed to mess up the .ssh/authorized_keys file. (Specifically, I changed the permissions so it was group- and world-readable, which causes `sshd` to not allow users to log in using those private keys.) Unfortunately, there is only one user on this server, so effectively I just locked myself out of the box.
$ ssh -i .ssh/EC2-dltj.pem me@dltj.org Identity added: .ssh/EC2-dltj.pem (.ssh/EC2-dltj.pem) Permission denied (publickey).
After browsing the Amazon support forums I managed to puzzle this one out. Since I didn’t see this exact solution written up anywhere, I’m posting it here hoping that someone else will find it useful. And since you are reading this, you know that they worked.


