Common Craft: Explanations in Plain English

I’m very fond of the Common Craft videos.  They take complex ideas on a variety of Web2.0 concepts and applications (RSS, Wikis, Social Networking, Social Bookmarking, Blogs, Online Photo Sharing, Twitter, Podcasting) and make them easy for anyone to understand.

As we gain expertise in a particular area of knowledge, it becomes difficult to provide a basic explanation of these technologies, especially to newbies.  These videos are just a few minutes long (usually between two and five minutes) and have a distinctive style that is quite entertaining.

Lee and Sachi LeFever are Common Craft, a husband-and-wife company.  Lee LeFever was interviewed by Jon Udell (Interviews with Innovators as part of the IT Converstaions Network). The 26 minute interview is almost longer than the dozen Common Craft videos that have been produced so far, but there are many insights that make this interview worth a listen.

As Albert Einstein stated: “Everything should be made as simple as possible, but not one bit simpler.”  The efforts in paring these videos down to just what is needed really shows, however, LeFever says that with the success of the videos, he has been overwhelmed with requests for videos for various topics and applications.  Many assume these short videos only take a short time to produce, but LeFever notes that several of the videos took forty and sometimes even more than eighty hours to complete.

Going by the statistics on these Common Craft videos that have been uploaded to YouTube, they are proving to be quite successful.  Whether a newbie to these Web2.0 or an expert teaching newbies, the Common Craft site is a terrific resources for all – Twitter it, Blog it, and Social Bookmark it now!

Library-related API’s

Thanks to Roy Tennant for compiling a list of Library-related API’s.  From a variety of services that can validate and be used to leverage additional information to a number of tools and specifications, this is a handy list of a number of essential API’s that can be used by many Libraries.

For those not familiar with them, an application programming interface (or API) is a set of functions, procedures, methods or classes that an operating system, library or service provides to support requests made by computer programs.  Submit a chunk of data like an ISBN and an API can return a title and perhaps other related data.  This is an oversimplication as many services like Amazon Web Services (AWS) API can handle many different types of data and respond handily with standardized output.  Submission interfaces are often avoided with API’s and data is returned in a format like XML that can be more easily repurposed than an HTML results page.  API’s have become quite fasionable with major Internet players like Google and Amazon and Facebook making their API’s widely available to developers.  As indicated by part of the list compiled by Roy, there are many Library-oriented API’s based on standards like Z39.50 or OAI that have been developed by Libraries and are often forgotten with all the big Internet players.

Book Burro

Book BurroStop searching after you find a book – let your browser do [locate] it for you:

Book Burro is an extension for the Firefox and Flock web browsers that tries to save you time and money when you find a book you want.

When Book Burro senses you are viewing a book, it will add a small panel to the upper right corner.

Clicking the panel will trigger the agent to go query for prices at other book sites and check your local libraries for availability.

Found a book on Amazon and want to see if a local library has it or another book seller has it at a better price?  Book Burro is the extension to use.  Configure Book Burro with your postal or zip code, check the appropriate libraries, and check/uncheck the relevant book vendors you want to search by default.  Book Burro often senses when you’re on a page viewing a book, but if it doesn’t, just highlighting and right clicking on an ISBN (ISBN-10 or ISBN-13) and selecting “Book Burro Search…” will bring up the Book Burro search box as it searches libraries and book vendors.  There’s a fair selection of public libraries in North America (it had Winnipeg Public, at least), but there’s obviously many more libraries that could be added.  Thankfully, there are many libraries that are searched by configuring your postal/zip code since Book Burro uses OCLC’s Open WorldCat and xISBN functionality to facilitate locating books.  In 2006, Jesse Andrews was runner-up with Book Burro in OCLC’s annual Research Software Contest.

Of course there are a couple pitfalls that we should be reminded of with ISBN searches.  First, ISBN’s were only assigned to books starting in 1972 (so there’s still a great deal of literature prior to 1972 one may want to search).  Second, with ISBN searches there is typically a different ISBN for a particular title for different versions such as hardcover versus paperback (let alone different ISBN for different editions such as a 2nd or 3rd edition of a particular title).  While hardcover may be more desirable than a paperback version, it will require some thoroughness in making sure that nothing is missed or overlooked with an ISBN search.  Finally, one other obvious pitfall is that not all libraries add ISBN’s to their cataloguing records (though it’s much more common now to add ISBN’s than years ago) and those that do add ISBN’s often do not run validation checks (since there is a standard coding that can be checked) to make sure ISBN’s haven’t been entered wrong.  ISBN validation detects any single-digit error and any two-digit error resulting from transposing two digits, but many catalogues to not provide such error reports by default and building such checks are often not huge priority for many libraries.

Overall, however, Book Burro, is a good tool to add to your research tool box and another way the Firefox browser beats Micro$oft Internet Explorer.

Zotero

I’ve been using Zotero for more than a year now.  It’s a Firefox add-on that I can’t live without!  There’s some pretty nifty features including a capture or scraping function of citation information from Web pages.  For certain Web sites, it will recognize the type of citation – just as there’s a little symbol that appears in your address bar when you’re on an RSS feed page (to make it easier to add a page as an RSS feed), Zotero recognizes certain resource pages that have citations on them (most Library catalogues and aggregated subscription journal databases and Amazon) and provide a little widget in your address bar to make it easier to add one or more citations to Zotero.  It’s really quite neat and a bit more slick than the direct export method for aggreagated subscription journal databases to something like RefWorks.

Sadly, Zotero is only stored on your local system (currently), but is easily backed up as an RDF file or exported and an RIS file.  Zotero will really excel with some new features the Center for History and New Media at George Mason Univesity are looking to add including remote citation library backup, access to your citation library from anywhere via the Web, recommendation engine and RSS feeds, and shared collection….so much more accessible in a networked environment with Web 2.0 features.  Once Zotero gets to this stage, it will be much more comparable to RefWorks or Connotea…and perhaps even a little beyond.

If you haven’t, I’d say give Zotero a try!

(Originally posted to the OCUL RefWorks Canada list on April 30, 2008)

Word Up for Wordle.net

Old-school Librarians will recall those dusty reference tomes called concordances.  Such works were handy for providing a list of words used in a body of work, with their immediate contexts and frequencies of occurrence within a particular work or set of works such as one or more Shakespeare plays.

Of course, concordances are generally about as visually appealing as a phonebook (white pages…not that the yellow pages are all that great) and don’t lend a great deal of insight at a glance.  However, many new applications provide visualization with interpretive appeal.

Wordle (Wordle.net) is a toy for generating “word clouds” from text that you provide. The clouds give greater prominence to words that appear more frequently in the source text. You can tweak your clouds with different fonts, layouts, and color schemes. The images you create with Wordle are yours to use however you like. You can print them out, or save them to the Wordle gallery to share with your friends.

Word or tag clouds are certainly not a new invention in a Web2.0 world, but this application deserves extra points for the degree of customization that’s provided for the visualization.  Also, you can do a visualization from several sources — from raw text that you copy and paste into a form on the Wordle site, to submitting a URL for a Web page, to submitting a del.icio.us username.

Unfortunately, there’s no direct link (or drill down) between the word cloud and the text that you provide (like a hyperlink between your tags in del.icio.us and the related sites indexed with that tag), but again this is more of a visualization than a true concordance.  However, from marketing your words to gaining a greater introspection to the words in your text, Wordle is worth a look.

One feature, though, that’s particularly lacking with Wordle is a way to save or output the file as something useful such as an image file.  It’s easy enough to print to PDF and there’s lots of options for changing font type, colour scheme, and layout, but ScreenGrab! (an extension for Firefox) didn’t seem to catch anything from the Wordle Web page or the Wordle Java Applet that was opened (just a blank page).  There’s probably some way to grab the image with some screen capture version, but Wordle doesn’t make this feature readily available with the site.

You can save your Wordle visualization to the Gallery on the Wordle site, though, and embed it on your site (such as the one made below on August 6th, 2008 with my del.icio.us bookmarks):

Follow

Get every new post delivered to your Inbox.