In BIBFRAME, a "hub" is a BIBFRAME class that functions as an abstract resource, bridging two or more BIBFRAME Works. It represents a point of connection between different bibliographic entities, similar to how certain MARC authority and access point fields connect different parts of a catalog record. A hub is not a user-facing starting or ending point, but a connecting point "along the way" that facilitates relationships between resources.
Key functions of a BIBFRAME hub:
- Connects different Works: A hub acts as a bridge, linking two or more BIBFRAME Works together.
- Matures MARC concepts: It's the BIBFRAME equivalent of MARC's Title and Name-Title Authorities and uniform title/main entry combinations, acting as a central access point.
- Acts as an intermediary: It serves as a point of interest within a larger data structure, but not the ultimate destination or origin for the user.
- Supports different title variations: When used with a bf:mainTitle, a hub can incorporate the entire authorized access point, with other properties like bf:partNumber, bf:partName, and bf:subtitle potentially used to capture different parts of that access point.
In BIBFRAME, a Hub is an authoritative control point used to collocate and aggregate different creative Works that are all variations of the same core intellectual or artistic content.
It functions as an abstract, central linking mechanism that ties together related but distinct bibliographic resources in a linked data environment, much like a uniform title in the traditional MARC format.
Key Concepts
- Collocation: The main purpose of a Hub is to bring together related items, allowing users to discover all versions of a creative work in one place.
- Bridge between Works: While individual
bf:Workentries in BIBFRAME describe specific intellectual or artistic content (e.g., the English text vs. a specific Spanish translation), thebf:Hubsits above them to link them all as related expressions of a single underlying concept. - Authority Control: Hubs are often derived from existing name-title or title authority records, providing a consistent, machine-readable identifier (URI) for the idea of a work, ensuring consistency across different cataloging systems.
Examples
The Adventures of Tom Sawyer Example:
A
A
bf:Hub for Mark Twain's The Adventures of Tom Sawyer would be a single, authoritative URI that serves as the common denominator for all related Works. The Hub links the following individual
bf:Work descriptions:- Work 1: The original English text created by Mark Twain.
- Work 2: A Spanish translation of the text.
- Work 3: A film adaptation (moving image work).
- Work 4: A graphic novel adaptation.
- Work 5: An audiobook recording.
In this scenario, a library user or a search engine can access the main Tom Sawyer Hub and discover all related forms and translations, which would be difficult to connect automatically using traditional, siloed MARC records.
Musical Composition Example:
A
A
bf:Hub for Francisco Tárrega's Capricho árabe could link to: - Work 1: The original score for a solo guitar.
- Work 2: An arrangement for a string quartet.
- Work 3: Various sound recordings (Instances) of different performers playing the piece.
By using a Hub, the system can capture the relationship that all these distinct musical "works" and "instances" are expressions of the same underlying composition, enabling comprehensive discovery and navigation of the collection.
Creating a Hub in Marva
If a Hub is not found, and according to authority policies and practices, a title or name-title authority record would not be created for the access point, you can create a Hub “Stub” directly in Marva. This is new functionality as of February 2025 and will be improved over time.¹
References
