DO NOT USE WEB BUGS IN OPACS. SRSLY PPL WTF.

Shared with Dropbox

Structured library data in the Evergreen open source integrated library system

Last week I had the fantastic experience of returning to the code4lib conference for the first time since 2008, and as a speaker to boot. The title of my talk was Structured data NOW: seeding schema.org in library systems. I had given two talks the prior week on a …

Innovative is happy to announce Polaris Release 6.0 is now in general release, offering libraries powerful new features, including enhancements to the PowerPAC and the Polaris Web Application.

Revisiting

'Bout time.

Good reports on Michigan's choice of discovery layer. Example for 644 final project plans.

Photo property of iStockPhoto.com.    The Orbis Cascade Alliance  last month did a very important service to the library community and th...

The content that a library owns or subscribes to should be discoverable in the way librarians want. However, this is not always the case when it comes to web-scale discovery systems.

Q2 What other industries can librarian/archivists work in? (example: us.blizzard.com/en-us/company/… ) via @ pnkrcklibrarian  #libchat  — J...

Aside from paying very little attention to visual design and not caring about the impact of horrible typography, the big problem with library catalogs is that they are not designed to help people accomplish library tasks. Instead, they’re designed to expose catalog records. Correct me if I’m wrong, but this is totally backward—prioritizing the collection, not people, results in a user-hostile interaction design and a poor user experience. Imagine the reverse: a tool that prioritizes helping people accomplish their tasks, whereby bibliographic data exists quietly in the background and is exposed only when useful.

On building library bookmarklets, and why APIless OPACs make it stupid hard.

There is a renaissance of interest in the catalog and catalog data. Yet it comes at a time when the catalog itself is being reconfigured in ways which