Friday, July 28, 2006


Off topic. The Pandora music service now has a new feature, Backstage. It allows you to enter the name of a band and get some info about them and then click on to other related bands.

Tagging Podcast

This has already been covered in many places, but just in case you missed it, the new Takling with Talis podcast discusses tagging.
The Library 2.0 Folksonomy Gang

In this Library 2.0 Gang discussion, members talk about folksonomies and the role of user-generated tagging alongside more formal methods of classification such as the Library of Congress Subject Headings and Dewey.

Programme participants were drawn, as usual, from the full list of Gang members, and a forum is available for discussion of issues raised during the recording.

Participants in this edition of the Library 2.0 Gang were;
  • Casey Bisson, Library Information Technologist at Plymouth State University in New Hampshire, USA. Casey blogs at maisonbisson.
  • Ian Corns, Business Analyst at Talis. Ian contributes to the Source blog, and writes at The Wonderful World of Mr C.
  • Christina Pikas, librarian in a physics, astronomy, mathematics, computer science & engineering library. Christina blogs at Christina's LIS Rant.
  • Karen Schneider, Director of the Librarians' Internet Index. Karen blogs at Free Range Librarian.
  • Tim Spalding, founder of LibraryThing. Tim blogs at the LibraryThing blog and Thing-ology.
During the conversation, the following sites and resources were cited;
  • CiteULike
  • Connotea
  • FictionFinder
  • Flickr
  • LibraryThing
  • Librarians' Internet Index
  • PennTags
  • WPopac

Thursday, July 27, 2006

Creative Commons Metadata

For the Linux folks: Jaime Frutos Morales developed an extension for the the Epiphany web browser for the Gnome desktop which detects embedded license metadata. If license information is detected the extension adds a (CC) icon to the status bar. Clicking the icon opens the license deed in the browser.

Access Level Record for Serials

The Access Level Record for Serials 1: Working Group Final Report is now available.
Declining library budgets, competition from Internet search engines and information services, and the escalating costs of cataloging have caused libraries to emphasize ways to meet user needs while decreasing costs. The Access Level Record for Serials Working Group was formed to develop a single CONSER standard record that would apply to all formats (print as well as online2), replace existing multiple record levels, and reduce serials cataloging costs by requiring in serial records only those elements that are necessary to meet FRBR user tasks. Cost savings and user benefits could also be realized by recording the elements in a way that is more straightforward for the cataloger to provide and easier for the end user to understand. As the name of the record implies, the emphasis of this record is on access points rather than elaborate and often redundant description. The record is intended to be a “floor,” to which additional elements can be added if such elements are essential to meeting FRBR user tasks for a specific resource or to meet the needs of a particular institution.

Wednesday, July 26, 2006

Greesemonkey Script for unAPI

Alf Eaton has put together a Greasemonkey script for unAPI.
unAPI, the lightweight mechanism for retrieving objects or their metadata in different formats, reached version 1 a few weeks ago, and has been implemented in HubMed and other places already. While unAPI links are designed to be machine-usable, this Greasemonkey script makes them visible in the browser, showing all the different export formats available for an item. Try it on this page (click the unapi link to show the individual formats - needs a pretty drop-down menu really).

Monday, July 24, 2006

MODS Implementation Registry

A reminder to the MODS community about the MODS Implementation Registry. If you are using MODS in your institution or project, please submit an entry.

Please include:
  1. The MODS project name
  2. Name of the institution or organization implementing MODS
  3. A short description of the MODS project
  4. A URL to the MODS project web site (if available)
  5. Any web site notes
  6. Projected dates of implementation
  7. A URL to any available documentation or specifications developed for the MODS project
  8. Any notes about documentation
  9. A list of any MODS tools developed and or used as part of the MODS project
  10. The MODS version used in the project
  11. Contact name and e-mail address
  12. Any additional contact information.