Wednesday, November 01, 2006

WLA 2006: Cataloging Changes on the Horizon: FRBR & RDA

Wednesday 9am-10:15

Steven Miller gave a general overview of FRBR, RDA, and the New Statement on International Cataloging Principles.

FRBR= Functional Requirements for Bibliographic Data
RDA= Resource Description and Access

New statement on Internation cataloging principles
Revision of Paris Principles

There are various metadata standards
  • structure standards...schemes or element sets (ex dublin core, marc)
  • content standards - rules for element content
  • value standards...controlled vocab for values of elements
  • encoding standards...machine read, communication, and exchange (xml, MARC)
  • presentation standards...opac, css
FRBR is NOT new catalogging rules or a set of instructions for restructuring OPAC

FRBR designed to address the problem of multiple versions-- AKA "content vs carrier"

For example, text is not only printed page, it also includes: html, pdf, microfilm, microfiche, image

How to arrange logically? This is FRBR's goal.

Users need to find resources--need enough info in record so they can differentiate editions, format, etc.
User Tasks: Find, Identify, Select, Obtain ...... Navigate (not strictly FRBR, but in ISoCP)

Group1 - products of content--
works, expressions, manifestation, item
Group2- those responsible--person, corporate author
Group3- Subjects of works--Groups 1&2, plus concept

In 80% of resources, cataloged works, expressions & manifestations are identical...don't need to distinguish.

Example of FRBR applied to Shakespeare's Hamlet
Work - Hamlet
Expression - 2006 English Edition
Manifestation - E-book
Item - specific copy on my listening device

FRBR mirrors what happens in real life--groups things together in larger ways

Currently we catalog mostly at manifestation level -- expression-level will probably be cataloged at authority level

Expression includes: title, edition statement, notes, access point (ex different orchestras performances)
Manifestation includes: isbn, title & statement of responsibility, publication info, Physical description, some notes, Access points (ex CD or cassette).

Most FRBR will be at software level. We are fairly dependent on our ILS vendors to support FRBR.

A few experimentations:
  • RedLightGreen -- OCLC's FRBR-ish experiment.
  • NSCU -- using Endeca to come close, but still a workaround.
RDA=Resource Description and Access
  • Successor to AACR2
  • Drafts available for input from cat and metadata communities--looking for input!
  • Intended pub date 2008
Why not AACR3?
  • based on cat CARDs
  • print centered
  • not suited to digital resources
  • Inconsistent concepts and terms for multiple versions
  • mixes data elements and content rules with data presentation (ISBD)
Data that is readily adaptable to new and existing database structure
Want to make compatible with existing records in OPAC

  • intended for use in digital world
  • focuses on principles, use cataloger judgement
  • incorpates FRBR
  • integrate all types of content
  • separate data from display
  • parallels Int'nl Statement on Cataloging Principles
  • built on foundations of AACR2
  • intended for libraries, BUT also intended for wider use
challenges include:
  • separation of bibliographic elements from ISBD areas
  • changes in terminology
  • crosses all material types in AACR2 part 1
RDA will be web-based resource (but also loose-leaf pub)

Important to keep RDA and MARC separate
RDA=content standard
MARC=encoding standard

ISBD punctuation isn't required anymore in RDA--optional.

RDA impact on existing records? Minimal.

There is RDA outreach group which is notifying vendors of RDA developments, but still vendor dependent.

Summary: all is still abstract, but on the horizon...

Q: Will it make it easier to catalog? Will it save time for catalogers?
A: At is supposed to. Smaller subset of mandatory elements, but room for more.

Slides will be on WLA website.

No comments: