The FRBR Vector
For information applicable to Primo VE, see Understanding the Dedup and FRBR Processes (Primo VE).
Introduction
The FRBR section in the PNX contains the FRBR vector, which has the following parts:
-
Type (T) – The type can be used to FRBRize sets of records using different FRBR algorithms. Currently, there is a single type (1), which is based on creating and matching author-title keys.
If you would like to skip FRBRization for individual records, you can set this field to 99 in the normalization rules.
-
Keys (Kn) – The keys are created from specified fields of the source record that can be used to identify the group it represents. The keys are checked in order starting from K1, and the data is normalized. There can be several types of keys, each with multiple occurrences.
Every key has the following subfields:
-
$$K – contains the values from the MARC21 fields/subfields in the source records.
-
$$A – contains the following key types, which specify the FRBR algorithm:
-
A – The author part keys are combined with title part keys to create a key (K1) that represents the work.
-
T – The title part keys are combined with author part keys to create a key (K3) that represents the work.
-
TO – Title only keys are title keys that are not combined with authors. This key (K2) is created only from titles that can be used to identify the work on their own. The MARC 130 (uniform title) tag is an example of such a field.
-
-
For example:
<frbr>
<t>1</t>
<k1>$$Kshakespeare william 1564 1616$$AA</k1>
<k3>$$Khamlet$$AT</k3>
</frbr>
FRBR Algorithm (Type 1)
In the FRBR algorithm, the keys are created by joining the author and title parts using all possible combinations, unless the key part type is TO. This type of title part key is not joined with author keys. With the exception of a TO part, the keys must be created from an author and title part. If one part does not exist, the key is not created.
In the FRBRization process, the keys are compared. If a record has a matching key with another record, it is added to the same FRBR group. Once a match is found, the system does not continue searching for matches since a record can belong to one FRBR group only.
The following table describes how the FRBR vectors are created from the MARC 21 source records:
Field | Source (Value of $$K in Key Field) | Value Used for $$A in Key Field | Note |
---|---|---|---|
T |
Always 1 |
|
|
K1 (author part key) |
100 or 110 or 111 OR 700, 710, 711 |
A |
Single occurrence of 100, 110, 111; multiple occurrences of 700, 710, 711 Take subfields a, b, c, d, q and n for 111 |
K2 (title only key) |
130 |
TO |
Subfields a, d, m, n, p, r, s |
K3 (title part key) |
240 |
T |
Subfields a, d, m, n, p, r, s |
And (if 240 exists and format is not SE) 245 |
Subfields a, b, e, f, g, n, p |
||
OR (if 240 does not exist and format is SE) 245 |
Subfields a, b, e, f, g, n, p |
||
OR 242 |
Subfields a, b, f, g, n, p |
||
OR 246, 247 |
Subfields a, b, f, g, n, p |
||
OR 740 |
Subfield a, n, p |
To normalize the Author part of the keys, the FRBR algorithm performs the following:
-
deletes the following characters:| [ ] '
-
replaces the following characters with a space: $~'^%*/\?@.:;<>{}}-()"!¿¡
-
converts characters using the NACO_diacritics character conversion table
-
changes all characters to lowercase characters
To normalize the Title part of the keys, the FRBR algorithm performs the following:
-
removes non-filing characters
-
drops the initial text using a non-filing indicator
-
deletes the following characters: | [ ] '
-
replaces the following characters with a space: $~'^%*/\?@.:;<>{}}-()"!¿¡
-
converts characters using the NACO_diacritics character conversion table
-
changes all characters to lowercase characters
Examples
In the following example, the two records match because there is matching FRBR key:
# | Record | Vector and keys |
---|---|---|
1 |
100 1_ |a Carroll, Lewis, |d 1832-1898. 240 10 |a Alice's adventures in Wonderland 245 10 |a Alice in Wonderland. 260 __ |a New York : |b H.N. Abrams, |c 1988. 300 __ |a [62] p. : |b ill. (some col.) ; |c 28 cm. |
T 1 K1 carroll lewis 1832-1898 K3 alice's adventures in wonderland K3 alice in wonderland The following keys are created:
|
2 |
100 1_ |a Carroll, Lewis, |d 1832-1898. 240 10 |a Alice's adventures in wonderland. |l Telugu 245 10 |a Alli?billi?lo?kam?lo? amma?yikatha |h [microform] = |b Alice in wonderland / |c mu?l?am?, Lu?yi? Kero?l ; anukaran?am?, Va. Durga?prasa?dara?vu. 246 31 |a Alice in wonderland 260 __ |a Madara?su : |b A?ndhragranthama?la, |c [1951] |
T 1 K1 carroll lewis 1832-1898 K3 alice's adventures in wonderland K3 alli billi lo kam lo amma yikatha alice in wonderland The following keys are created:
|
In the following example, the two records do not match because there are no matching FRBR keys:
# | Record | Vector and keys |
---|---|---|
1 |
100 1_ |a Chorpenning, Charlotte B. |q (Charlotte Barrows) 245 10 |a Alice in Wonderland, |c dramatized by Charlotte B. Chorpenning, a play from the library of the Association of the Junior Leagues of America, inc. 260 __ |a Chicago, |b The Dramatic Publishing Company |c [1946] 700 1_ |a Carroll, Lewis, |d 1832-1898. |t Alice's adventures in Wonderland |
T 1 K1 chorpenning charlotte b K3 alice in wonderland The following key is created:
|
2 |
050 00 |a VXB 0196-0197 (viewing copy) 245 00 |a Alice in Wonderland. 260 __ |c 1999. 300 __ |a 2 videocassettes of 2 : |b sd., col. ; |c 1/2 in. viewing copy. 710 2_ |a Copyright Collection (Library of Congress) |
T 1 K1 copyright collection library of congress K3 alice in wonderland The following key is created:
|