Uniform titles (or preferred titles) serve an important collocation function in the library catalog. In a keyword environment, the presence of uniform titles increases the relevancy ranking of desired titles, thus improving discoverability. This presentation provides context for why catalogers create uniform titles, explains how uniform titles are encoded in MARC21 Bibliographic and Authority formats, and introduces RDA rules for preferred titles and conventional collective titles.
The Art Pastor's Guide to Sabbath | Steve Thomason
'Weird' titles in RDA and MARC: Preferred titles, collective titles, and conventional collective titles
1. ‘Weird’ titles
in RDA and MARC
Workshop for Indiana University Libraries’ Database
Management Section, 30 March 2016
Preferred titles, collective titles,
and conventional collective titles
8. 8
100 1# Shakespeare, William, ǂd 1564-
1616.
240 10 Macbeth
245 10 Shakespeare's The tragedie of
Macbeth : ǂb printed from the folio of
1623.
A bibliographic record for Macbeth
9. 9
100 1# Shakespeare, William, ǂd 1564-1616. ǂt Macbeth
400 1# Shakespeare, William, ǂd 1564-1616. ǂt Illustrated Macbeth
400 1# Shakespeare, William, ǂd 1564-1616. ǂt Macbeth for young people
400 1# Shakespeare, William, ǂd 1564-1616. ǂt Shakespeare's Macbeth
400 1# Shakespeare, William, ǂd 1564-1616. ǂt Shakespeare's The tragedie of
Macbeth
400 1# Shakespeare, William, ǂd 1564-1616. ǂt Shakespeare's tragedy of Macbeth
400 1# Shakespeare, William, ǂd 1564-1616. ǂt Tragedie of Macbeth
400 1# Shakespeare, William, ǂd 1564-1616. ǂt Tragedy of Macbeth
400 1# Shakespeare, William, ǂd 1564-1616. ǂt William Shakespeare's Macbeth
An authority record collocating Macbeth(s)
10. 10
100 1# Shakespeare, William, ǂd 1564-
1616.
240 10 Macbeth. ǂl Irish
245 10 Traigéide Mhic Bheatha / ǂc
William Shakespeare, a chum [...]
A bibliographic record for a translation of Macbeth
15. Preferred Title
15
RDA Glossary: The title or form of title chosen to
identify the work.
The preferred title is the title that gets sorted
neatly into the title index.
17. Preferred Title
17
...and preferred titles are given to works
that require what AACR2 called a
“uniform title”
100 Shakespeare, William, ǂd 1564-1616.
240 Macbeth
245 The tragedie of Macbeth
18. Preferred Title
18
… and preferred titles are given to compilations of
works.
100 Shakespeare, William, ǂd 1564-1616.
240 Plays. ǂk Selections
245 Four great tragedies : ǂb Hamlet, Macbeth,
Othello, and Romeo and Juliet / ǂc William
Shakespeare.
21. Conventional
Collective Title
21
A title used as the preferred title for a compilation
containing two or more works by one person,
family, or corporate body, or two or more parts of
a work (e.g., Works, Poems, Selections) RDA
Glossary
22. Conventional
Collective Title
22
Conventional collective titles use a generic
descriptor to refer to all of the works represented in
a single piece in hand
◉Works. RDA 6.2.2.10.1
◉Works. Selections. RDA 6.2.2.10.3 Alt
◉Works. Selections. Spanish. RDA 3.11.1.3
23. 23
Conventional Collective Title Examples
100 Carroll, Lewis, ǂd 1832-1898. ǂt Works. ǂf 2015
100 Carroll, Lewis, ǂd 1832-1898. ǂt Works. ǂk Selections (2014)
100 Carroll, Lewis, ǂd 1832-1898. ǂt Works. ǂk Selections. ǂl Spanish. ǂf 2015
These examples illustrate very common preferred titles for works that have
transcribed titles like, “Complete works of …” or “Selected works of …”
24. Conventional
Collective Title
24
Conventional collective titles may use a form
descriptor to refer to all of the works represented in
a single piece in hand
◉Poems. RDA 6.2.2.10.2
◉Poems. Selections. RDA 6.2.2.10.3 Alt
◉Poems. Selections. Spanish. RDA 6.11.1.3
25. 25
Conventional Collective Title Examples
100 Carroll, Lewis, ǂd 1832-1898. ǂt Poems
100 Carroll, Lewis, ǂd 1832-1898. ǂt Stories
100 Carroll, Lewis, ǂd 1832-1898. ǂt Stories. ǂk Selections. ǂl Spanish
100 Carroll, Lewis, ǂd 1832-1898. ǂt Correspondence. ǂk Selections
These examples illustrate very common preferred titles for works that
have transcribed titles like, “Collected [verse, short stories, etc.] of …” or “A
selection from the letters of …”
26. … and then
it all goes
WRONG
or, FRBR: a love song
3
26
27. FRBR & MARC
& Punctuation
27
Enclose these elements in ( )
◉Form of work
◉Date of work
◉Place of origin of work
◉Other distinguishing
characteristics of work
◉Other distinguishing
characteristics of
expression
Precede these elements by
full stop and a space
◉Content type
◉Date of expression
◉Language of expression
RDA E.1.2.5
28. FRBR & MARC
& Punctuation
28
Enclose these elements in ( )
◉Form of work
◉Date of work
◉Place of origin of work
◉Other distinguishing
characteristics of work
◉Other distinguishing
characteristics of
expression
Precede these elements by
full stop and a space
◉Content type
◉Date of expression
◉Language of expression
RDA E.1.2.5
29. 29
RDA titles (now with 100% more FRBR!)
These are examples of FRBR Work titles:
100 Carroll, Lewis, ǂd 1832-1898. ǂt Works. ǂf 2015
100 Carroll, Lewis, ǂd 1832-1898. ǂt Works. ǂk Selections (2014)
This is an example of a FRBR Expression title:
100 Carroll, Lewis, ǂd 1832-1898. ǂt Works. ǂk Selections. ǂl Spanish. ǂf 2015
30. 30
RDA titles (now with 100% more FRBR!)
These are examples of FRBR Work titles:
100 Carroll, Lewis, ǂd 1832-1898. ǂt Works. ǂf 2015
100 Carroll, Lewis, ǂd 1832-1898. ǂt Works. ǂk Selections (2014)
This is an example of a FRBR Expression title:
100 Carroll, Lewis, ǂd 1832-1898. ǂt Works. ǂk Selections. ǂl Spanish. ǂf 2015
Why doesn’t
this date get a
period space
ǂf and the date
below does??
FRBR.
34. Thou shalt not...
...create a preferred title (uniform title) for a
language translation when the translated title (or
the translated title’s Romanized form) exactly
matches the title of the original work.
34
35. (Doing it wrong)
35
010 no2014111348
040 InU ǂb eng ǂe rda ǂc InU
100 Goncharov, Ivan Aleksandrovich, ǂd 1812-1891. ǂt Oblomov. ǂl
Romanian
400 Goncharov, Ivan Aleksandrovich, ǂd 1812-1891. ǂt Oblomov
670 Goncharov, Ivan Aleksandrovich. Oblomov, 1973.
36. (Doing it wrong)
36
010 no2014111348
040 InU ǂb eng ǂe rda ǂc InU
100 Goncharov, Ivan Aleksandrovich, ǂd 1812-1891. ǂt Oblomov. ǂl
Romanian
400 Goncharov, Ivan Aleksandrovich, ǂd 1812-1891. ǂt Oblomov
670 Goncharov, Ivan Aleksandrovich. Oblomov, 1973.
38. Image Credits
38
Slide 3, 7 Students Using Card Catalog, Indiana University
Slide 13 Burrowing owl, kuhnmi
Slide 19 Burrowing Owl (tilting head left), Mike’s Birds
Slide 33 Burrowing Owl, Squeezyboy
39. Jennifer A. Liss
Head, Monographic Image Cataloging
Indiana University, Bloomington Libraries
jaliss@indiana.edu
0000-0003-3641-4427
Thanks!
39
This work is licensed under a Creative Commons
Attribution 4.0 International License.
Editor's Notes
Before we plunge into the gory details, I want to review a couple foundational concepts for why we use these “weird” titles. After all, you can look up the rules in RDA Toolkit at any time but the rules aren’t going to explain why users and machines need this information.
The notion of a title index has been with us for a long time. Generally, the title index aids users in finding known works by sorting titles alphabetically and by collocating like titles together.
Most books sort neatly into the title index. This is a screenshot of some recently released books—all have distinctive titles and are first-ever printings.
If this card file were to represent a title index, Bob’s Burgers burger book would sort right in alphabetically—there’s not much mystery here.
But what if the same work appears under different titles? Here are five examples of the work Macbeth—each with a different title proper.
Here I’ve transcribed the titles so that you read them. Without cataloger intervention, these titles would alphabetically sort all over the place—and if our users searched the card catalogue for “Macbeth” they would not find the authoritative text from the First Folio, which would have been be sorted under “Tragedie”.
To help the user, cataloging practice evolved to include authority control for titles, letting us collocate like works under authorized form (in this case, a name-title heading).
Regardless of what we transcribe as the title proper, all of the Macbeths are collocated in a single place: “Shakespeare, William, 1564-1616. Macbeth”.
This slide illustrates the transcribed title (the title proper) in the MARC 245 subfield a, as well as the collocating title (the AACR2 uniform title, which is highlighted) coded in the MARC 240 subfield a.
On the name-title authority record for Macbeth, you see the many titles under which Macbeth has been published (MARC 400 fields).
In this example, the piece being cataloged is a translation. The 240 field includes a subfield l, indicating the language of the piece in hand.
Here is a shortlist of authorized access points representing Macbeth in its many translations.
Let’s pause for a moment because you might be thinking “but Jen, we haven’t been in a browsable catalog environment since the implementation of our Blacklight discovery layer.” True. IUCAT search is based on keyword. The results you see are based on some mysterious relevancy ranking. However, inserting the uniform title into a record increases the keyword frequency for the words william, shakespeare, and macbeth--in theory, that would bump up the record higher in the search results.
Some of you probably already know that the IUCAT development team is working on enabling browse in IUCAT once again.
And without getting into great detail about linked data, trust me when I say that having work identifiers (i.e., name-title authority records) is critical for moving library data into structures that can be leveraged by new technology. YOUR WORK IS IMPORTANT!
Quick pause here--any questions?
Because RDA changed what we call things—and because all of us worked in an AACR2 environment for much longer than we’ve worked in a RDA environment—it’s necessary to review some vocabulary.
The notion of preferred title encompasses a few different kinds of titles...
In this example, the title proper (MARC 245 field) *is* the preferred title. We don’t add the 240 for the preferred title because it would duplicate the 245.
Preferred titles can be works that fall into the “Macbeth” category that we reviewed earlier. Here, the MARC 245 is the title proper (transcribed) and the 240 is the preferred title.
If you need to search for how to do uniform titles in RDA Toolkit, use the phrase “preferred title”.
Preferred titles also include the types of titles that we assign to compilations.
We’ll talk more about compilation titles but before we do...
… we’re going to take another quick adorable creature break. Are there any questions about preferred titles?
RDA makes a distinction between creating collective titles (RDA 2.3.2.6) and conventional collective titles; however, LC-PCC Policy Statements (for 6.2.2.9.2 and for 6.2.2.10.3) tell us to always create conventional collective titles, rather than create preferred titles for each work in a compilation. Since Indiana University Libraries follows the LC-PCC PS interpretations, I won’t talk about collective titles. today.
In the last example, the date is included to break (or anticipate breaking) a conflict with some other Spanish translation.
The form of work (e.g., “Poems,” “Stories,” or “Correspondence”) stands in for conventional term “Works”.
The following few slides can be filed under “You should hear this once”. You may forget this almost immediately but when this comes up again, alarm bells should sound...
RDA Appendix E contains instructions for the presentation of access points. RDA E.1.2.5 covers Access Points Representing Works and Expressions.
You’ll notice that much is made about whether an element represents an aspect of a work vs anaspect of an expression. This causes of trouble when catalogers formulate the authorized access point.
“Works. Selections” plus a date is always a FRBR work-level access point (2nd example). The third example shows a translation and in the FRBR world, translations are usually FRBR Expressions (see Slide 28).
Catalogers get this wrong. Often. Let’s correct these, shall we?
Since “Works. Selections” is a FBRB Work access point, the date is contained in parentheses and is NOT subfielded in MARC.
The 400 “see from” reference exactly matches the authorized access point (100) on name authority record (NAR) no2002003934.
If the cataloger really wanted to create a NAR for “Oblomov. Romanian” (and LC generally doesn’t recommend doing so when the translated title exactly matches the original title), then the cataloger should NOT create a *conflict* by adding the 400 that matches an AAP.
Personal aside: I don’t mind that the AAP for the Romanian translation was created. One could argue that the AAP will add value in a linked data environment.
I’ll close with this quote because the statement is perhaps more true now than when Cutter originally said it. RDA guidelines give catalogers lots of options and you will see every option in OCLC (and by extension, in our own database). The work of the Database Management Section has always been essential, but now that our database sources records through a variety of avenues (vendor batch loads, shelf ready, etc.) your work is critical.