A weblog following developments around the world in FRBR: Functional Requirements for Bibliographic Records.

Maintained by William Denton, Web Librarian at York University. Suggestions and comments welcome at wtd@pobox.com.


Confused? Try What Is FRBR? (2.8 MB PDF) by Barbara Tillett, or Jenn Riley's introduction. For more, see the basic reading list.

Books: FRBR: A Guide for the Perplexed by Robert Maxwell (ISBN 9780838909508) and Understanding FRBR: What It Is and How It Will Affect Our Retrieval Tools edited by Arlene Taylor (ISBN 9781591585091) (read my chapter FRBR and the History of Cataloging).

Calendar

March 2009
M T W T F S S
« Feb   Apr »
 1
2345678
9101112131415
16171819202122
23242526272829
3031  

What We Talk About When We Talk About FRBR

Posted by: William Denton, 6 March 2009 8:20 am
Categories: Conferences

Last week Jodi Schneider and I gave a talk at Code4Lib 2009 in Providence, RI: “What We Talk About When We Talk About FRBR.”

When vendors talk about FRBRization they usually mean grouping manifestations into works. When we talk about FRBR, we mean something far richer and rewarding. What FRBRization algorithms are available and in use now, how well do they work, and how do they present the relationships? We’ll look at the LC FRBR Display Tool, OCLC’s work-set algorithm, LibraryThing’s user-contributed groupings, and VTLS’s system. We’ll discuss their benefits, flaws, and what we need for the future.

In the talk we set out our ideas of weak, strong and complete FRBRization. Weak FRBRization is where we’re mostly at now, with work-set groupings. Strong FRBRization means that all the Group 1 entities (Work, Expression, Manifestation, and Item) are handled and their relationships fully described. Complete FRBRization means that all entities and their relationships are fully described and and all of this is described using standard vocabularies and expressed as linked data.

We ended by asking everyone to work on three things over the next year:

  1. Demand strong FRBRization.
  2. Build linked data.
  3. Create the algorithms.

Like all the talks it was recorded and a video will go up soon. I’ll link to it when it does. In the meantime, there are these:

Here are links to the entity-relationship diagrams we used to illustrate weak, strong, and complete FRBRization:

Jodi and I had never in person until Code4Lib, though we’ve known each other online for quite a while. We put our proposal together in half an hour, chatting in IRC while we edited a Google doc, three hours before the deadline. It all turned out very well and I was delighted to have her as a partner. The conference was great. I’ll be back next year.