We're Disrupted, We're Librarians, and We're Not Going to Take It Anymore
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.
Below is my report of the DPLA AppFest last month. This post is the raw input of an article on the IMLS blog that was co-written with Mary Barnett, Social Media Coordinator at the Chattanooga Public Library. I also attended yesterday’s DPLA Audience and Participation workstream meeting at George Mason University, and hope to have a similar trip report posted soon.
The Digital Public Library of America held an AppFest gathering at the Chattanooga Public Library on November 8-9, 2012 for a full day of designing, developing and discussion. About 40 people attended from a wide range of backgrounds:
This is a preview of Trip Report of DPLA Chattanooga Appfest: Project Shows Signs of Life. Read the full post (781 words, 1 image, 3:07 minutes estimated reading time)
In September, Carl Grant wrote a blog post on the ownership of library data (“We have a problem… another vendor appearing to need education about exactly WHO owns library data“) that has been rolling around my own thoughts for, well, months. The spark of Carl’s post was a Twitter conversation where a major library system vendor appeared to be taking steps to limit what library/customers can do with their own data.
SerialsSolutions sez: we own the data you entered into 360. You can’t share it with a competing Discovery vendor.#VendorLove
Should librarians be learning to how to develop software? This theme has come up in the past few years1 and I think it is a good thing. I once had a boss that told his group “I want you guys to automate yourself out of your job because there are far more interesting things you could be working on.” I think that is an empowering philosophy for staff of any type.
This is a preview of The Security Implications of Teaching Librarians to Program. Read the full post (996 words, 3:59 minutes estimated reading time)
Earlier this month I found myself apologizing for some errant tweets that ended up in my Twitter stream1, and realizing that I had fallen into a pattern of sorts thought it would be useful to document. (This post, too, will be a good one to use as the ‘website’ link on my Twitter profile.) So here it goes. If you are following me on Twitter, these are the things you’ll see, in order of probability — from most likely to least likely.
This is a preview of What You’ll Find in My Twitter Stream. Read the full post (773 words, 3:06 minutes estimated reading time)
