At the American Library Association meeting in Chicago last month I gave a 20 minute presentation that was a combination of an overview of interoperability and standards plus a brief overview of the ResourceSync activity for the NISO Update session. Included below are my slides with a synchronized audio track.
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 the “very meta” category, this morning I gave a lightning talk about lightning talks to a crowd of about 150 at the LITA Lightning Talks session. More specifically, it was a brief presentation on how Code4Lib uses Google Hangouts-on-Air for its Virtual Lightning Talks. The slides and links from the slides are included below.
URLs from the presentation
As promised, here are the URLs from the presentation.
- Host must have a “Verified” YouTube account: https://www.youtube.com/verify
- Host and Presenters must install the Hangouts plugin: https://tools.google.com/dlpage/hangoutplugin/
- “Hangouts-on-Air” Documentation: https://support.google.com/plus/answer/2553119
- Presenters share their entire screen or just a window https://support.google.com/plus/answer/1660627
Earlier this month published ‘reposervice’ to GitHub. Reposervice is a “self-contained” Islandora installation source tree that is intended to smooth the LYRASIS deployment of repository services between development servers, a staging server and production servers. It is a bit of a work-in-progress at the moment, but others might find it useful as well.
(By the way, if you had looked at Reposervice prior to June 18th, you may have noticed a missing critical element — the Drupal submodule. Not because you couldn’t add Drupal yourself but because the Reposervice clone has relative soft symlinks to the Islandora modules positioned in the top level Reposervice directory.)
Issue #20 of the Code4Lib Journal was just published, and I had the honor of being the coordinating editor for the issue. Being on the editorial committee of the Journal has been a heck of an experience, and I think I’ve had just a taste of what journal editors and publishers must go through to produce quality content.
My editorial focused on an issue that has banged around in my head for a while and has come up in multiple venues in recent years — how do we grow as a community while remaining responsive to the community and true to its roots. I suggest that there is a merit-based way to approach this, and I lay out my thoughts in that article.