On December 6, 2012, the Audience and Participation workstream met at the Roy Rosenzweig Center for History and New Media at George Mason University. About two dozen colleagues participated in person and remotely via Google+ Hangout to talk about processes and strategies for getting content into the DPLA (the content hubs and service hubs strategy), brainstormed on the types of users and the types of uses for the DPLA, and outlined marketing and branding messages that aligned with the goals and technology of the DPLA while getting content contributors and application developers excited about what the DPLA represents. I’m happy to have been invited to take part in the meeting, am grateful to DPLA for funding my travel to attend in person, and came away excited and energized about the DPLA plans — if also with a few commitments to help move the project along.
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.
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
— Wally Grotophorst (@grotophorst) August 15, 2012
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.