GAME TEMPLATES SOFTWARE STATION: David Lee King

Monday, December 20, 2010

David Lee King

Delicious and other Services – Have a Backup Plan?

Posted: 20 Dec 2010 06:10 AM PST

So last week, some of you probably heard that the Delicious.com service was possibly being – their term – “sunset.” Then they announced that it wasn’t, and that they hope to find another home for the service outside of Yahoo.

My library doesn’t use Delicious for our website – but some libraries rely pretty heavily on the service for things like a linkroll. I know of more than one library who replaced in-house reference web link databases with the Delicious service. I’m guessing a couple of us were scrambling around, looking for alternatives (Diigo is one good one that I’m familiar with), and figuring out how to export their links out of Delicious.

Here’s what I’m interested in – how much do we depend on these third party services for essential parts of our website? Delicious is one example … what if Yahoo decided to do the same thing to Flickr, or if Google decided to do that to Youtube or even their Google Accounts (many organizations have switched their email/storage/messaging systems to Google from hosting them in-house)?

There are definitely alternatives to most of these services, and I’m not sure that dumping content into one primary service and one “just in case” backup service is worthy of our time (though I personally do that with my Flickr photos). And honestly, I’m not sure that people who read my blog would have that much trouble finding alternatives (I know my library wouldn’t, anyway).

But what about understaffed, or smaller libraries that don’t have dedicated web dudes? For example, Topeka could easily build a links database – we have those skills in-house. But many libraries and organizations don’t have those skillsets, which is one reason why they chose a 3rd party tool in the first place – free/cheap and easy. And 3rd party tools are great – I certainly don’t want to store and host all the videos Topeka creates on an in-house server.

I think one way to tackle this is to simply be vigilant:

stay up-to-date on web tools by trying them out, reading about them, etc
pick the best tool at the time – look for features and stability – ok, and awesomeness
switch services when the next, better tool comes around – instead of waiting until one service closes its doors