The Cataloging and Metadata Management Section (CaMMS) Forum on the Bibliographic Framework Initiative (BIBFRAME) was held on Sunday, January 26 from 1 to 2:30 p.m., and featured three speakers who each addressed a different aspect of transitioning to a BIBFRAME environment.

Sally McCallum, Library of Congress, focused on relating BIBFRAME vocabulary to its MARC equivalent. BIBFRAME classes are similar to MARC tags and BIBFRAME properties are similar to MARC subfields. The four primary classes in BIBFRAME are: work, instance, authority, and annotations. Work includes RDA’s work and expressions, as well as MARC uniform title. Instance consists of RDA’s manifestations and approximates MARC bibliographic descriptions. Authority currently includes names and subjects, but other possibilities, such as publisher information, will be explored in the future. Annotations are like items in RDA, and include summaries, tables of contents, and reviews.

McCallum gave several examples related to title. instanceTitle equates to MARC 245 field and workTitle is similar to MARC 240 field. She stated that multiple title property options are required because of variations in cataloging rules and resource types. For example, simple title accommodates Dublin Core, titleStatement accommodates ISBD, abbreviatedTitle represents MARC 210, keyTitle parallels MARC 222, titleVariations pairs with MARC 246 and authority 4XX, and so on.

Two types of title-to-title relationships were discussed: general and specific. General relationships consist of work-to-work, work-to-instance, and work-to-expression relationships. Approximately 40 specific relationships exist, and they include information such as parts, supplements, translations, and reproductions. Further exploration into handling specific relationships is required.

More information on BIBFRAME from Library of Congress can be found at:

Michael Colby, University of California, Davis presented on BIBFLOW (formally titled Reinventing Cataloging: Models for the Future of Library Operations), an Institute of Museum and Library Services grant-funded project being undertaken at his institution. BIBFLOW is an effort to understand what BIBFRAME means for technical services workflows in an academic library, and attempts to address how existing systems and processes inhibit adopting new standards, how workflows impact other areas of the library, feasibility of incremental adoptions, and what types of investment are required and when.

Over a two-year period, this project will collect and map data, explore conversion, develop and test a prototype discovery system, and evaluate workflows in all areas of technical services.

More information on BIBFLOW can be found at:

Eric Miller, Zepheira, demonstrated how BIBFRAME and Linked Data will change the user experience with information input and retrieval. Miller described BIBFRAME as a way to begin utilizing the full potential of the infrastructure of the Web because it is a native Web model. He provided 2 examples of the user experience in a BIBFRAME environment: BIBFRAME Editor and Viewshare.

A demo of BIBFRAME Editor illustrated a dynamic interface, in which users select an item type (such as image, electronic article or paperback book), and enter information into the BIBFRAME Editor form. As the user enters properties, like subject, artist, author, or language, a dropdown list appears and the user can choose the desired description, in a way that is visually the same as what we have become used to seeing as we type search terms in a search engine. Images, such as cover art for an album, can be dragged and dropped into the BIBFRAME Editor as well. Once completed, that record can be saved and exported.

Viewshare is a platform that allows Linked Data to be presented to users in the format that they prefer or that is most useful to them. Rather than the creator of that data dictating how a user experiences it, as libraries do with OPACs (think static MARC record displays), Viewshare lets the user sort, create graphic displays based on the data, view maps associated with that data, or otherwise manipulate it. Miller used the example of a collection of albums. Using Viewshare, a user could narrow that entire collection by choosing musicians from a certain country, could then view a map showing which cities those musicians are from, and could create a timeline of release dates for those albums, using only a couple of mouse clicks. This would be a very dynamic, customizable user experience, made possible by BIBFRAME and the Linked Data model.

—Rebecca Nous, University at Albany, State University of New York