Djoeke, the Community Manager for blinklist.com (a social bookmarking company), is doing a survey on social bookmarking, and thought it would be dandy if I linked to the survey. So here’s the link. They’re hoping for 1000 responses.
The important stuff:
“The VideoEgg publisher is a small website plug-in that makes it simple for end-users to capture, edit, encode, and post digital video online. A “universal adapter” that captures directly from hundreds of devices and reads dozens of formats, the VideoEgg Publisher allows users to painlessly publish videos that anyone can watch without worrying about player compatibilities, encoding settings, or extra software.”
And… it’s free
Now, only if Flickr would do something like this…
If I needed to sum up this year’s Internet Librarian conference in one word, it would be:
And the word would have a few different meanings attached:
In some libraries, and with some librarians, the change to the “Google era” (for lack of a better term) has either taken place, or has at least begun. Those librarians have embraced the “new world” of social networks, the read/write web, online interaction with customers, and tools that spring up every minute… and have used them to better their libraries for their customers. There were 1100 attendees to the Internet Librarian conference, for example – and many of those attendees came to learn something new.
But that’s only 1100 librarians out of hundreds of thousands (at the least). There are still many libraries/librarians who have not embraced the Google era:
Where are the children’s librarians, who could be learning about the social networks their patrons are using right now?
Where are the reference librarians, who could be learning how to integrate new content into the collection?
Where are the library directors, who need to understand this new Google era so they can translate that understanding into goals and next actions for the library?
[ok David, take a breath... in and out, in and out]
Obviously, not everyone can make one conference. But that’s not really my point. My point is that our profession – young and old – needs to embrace these changes… and we aren’t. In some cases (cough.cough.Gorman.cough.cough), we’re running the opposite way.
And that’s the wrong way to run.
Stephen’s presentations, articles, conversations, etc are always both highly entertaining and educationsl at the same time, and this one was no exception.
Here are his Top 10 strategies for libraries to remain relevant in the Google age:
1. know your market
2. know your customers better than Google
3. be where your customers are
4. target. searching for the target
5. support your culture
6. postition libraries where we excel
7. be wireless
8. get visual
10. take a risk
the last word – focus
John started off by showing two older versions of Ann Arbor’s website (via the Wayback Machine, I think) [Dave's aside - my but haven't we come far in 10 years!].
The previous version of their site used Userland/Frontier as a CMS. It was a proprietary, closed system.
Their current design started out with the library redesigning their whole network infrastructure. Cool. They decided to use open standards whenever possible.
Choosing a new CMS:
- made an informal list of requirements
- Wanted it to be LAMP based
- Extensive API
- Easily theme-able – in order to work with external web designers
- Blog-based technology
- 100% modular
- Excellent API – Drupal is an API-Centric Project
- Large user-base
- very active project
- taxonomy based organization
- bloggable – comments, rss, etc
They had over 2000 registered users (username/password) within the first couple of hours of releasing their new site.
- ability to cross-post blog entries inside multiple taxonomies
- configruable interwiki links to catalog items, wikipedia, wherever
- you can browse events by location, type (storytime, lectures), subject, and age
They have rss feeds of holds and checkouts in their my account page
Does this new apprpach work?
- teens love it!
- I asked later, and adults like it and leave comments, too – just not as muc as the kids.
III has a patron API – it returns patron info.
Catalog – taking it apart
- turned into a n applciation server
- all non-essential html was stripped from the screen files
- unnecessary options were removed
Client URL – allows software to communicate with many different types of servers using different protocols
- PHP has native libcurl support
Result – the Wrapper
- they can get and update patron information, run catalog queries,etc
- Then they integrated Drupal through API
His Beef: they shouldn’t have to do that! Automation vendors should supply APIs!
Gaming – they have an advertisement at the theater – it shows live scores at the theater from the gaming going on in the library. Amazing!