Uniform Title - Main Entry and Added Entry

This tip is a quick review of a couple concepts introduced in my cataloging workshops.  Or rather, one concept used in two related ways.  The concept is the "uniform title" or "preferred title" as it is now also called.   This is the concept -- which actually predates RDA! -- that in some situations, a title may be used as an authority entry, like a subject heading or an author name.

 

In terms of RDA cataloging, the reason for doing so is to identify a "work" (creation) that has been "expressed" (adapted/interpreted) or "manifested" (given physical form) in various ways, all of which share an underlying similarity (i.e. the print book and audio book have the same plot.)

 

However, in the MARC record itself, we distinguish between two types of uniform title: Uniform title as main "entry" (search access point), and uniform title as added entry/access point. Ordinarily, the main entry is the author name; however, it is possible for a resource to have BOTH an author name as the main entry, and a uniform title as an added entry.  It is only when there is no clearly identifiable "creator," and/or when the resource was created by multiple people, that it becomes valid to use a uniform title main entry.

 

Therefore, MARC uses two different fields to distinguish these two uses of the uniform title.  Field 130 is for a uniform title main entry in the absence of an author main entry (e.g. motion pictures).  Field 240 is for a uniform title added entry, when there exists an identifiable author or "creator," along with one or more added authors, or "contributors,"  who have modified the "prior work."  

Here are two examples of a uniform title access point for the same resource.  Which is correct?

Example A:

=100 1\$aPinkney, Jerry.
=130 0\$aAesop's fables.$kSelections.$lEnglish.$f2000.
=245 10$aAesop's fables /$cJerry Pinkney.

Example B:

=130 0\$aAesop's fables.$kSelections.$lEnglish.$f2000.
=245 10$aAesop's fables /$cJerry Pinkney.

=700 1\$aPinkney, Jerry.

 

The answer is: NEITHER of these two examples are correct!  

 

"Who wrote Aesop's fables?" is like asking "Who's buried in Grant's tomb?"   And sure enough, checking the LC Authorities website reveals that "Aesop" is a valid name authority... like "Homer," in that historians may not be quite sure who he was, or even if he really existed, but the Library of Congress considers that name to be valid for use as a cataloging access point.

 

Therefore, we identify Aesop as the creator of the "prior work" and Jerry Pinkney, who retells the stories, as a contributor or "added author."  So although Pinkney's name belongs in Field 700 rather than Field 100,  this record still requires a Field 100 -- to identify Aesop, whoever he may have been, as the original author.  And that in turn means that Field 130 is not the correct choice!  

So the main access point and uniform title entry for this resource are correctly written in MARC format like this:

=100 0\$aAesop.
=240 0\$aFables.$kSelections.$lEnglish.$f2000.
=245 10$aAesop's fables /$cJerry Pinkney.

 

=700 1\$aPinkney, Jerry.

 

Points of interest:

  • Note that in Field 100, first indicator value is "0" instead of "1".   This indicates a "first-name-only" entry, as opposed to a "last-name-first" entry.  
  • Subfields $k, $l and $f may be used in either field 240 or field 130 to distinguish this particular resource, on the basis of language, form and/or date, from other, similar resources that are also expressions of the same prior work.
  • As always, the statement of responsibility (245 $c) is taken directly from the title page of the book, which indeed has only Pinkney's name listed.  It is not actually necessary to add "[adapted by]" to 245 $c, although catalogers may choose to.   The presence of Field 240 itself identifies this resource as an adaptation; the correct entries in Fields 100 and 700 identify the the creator whose work is adapted and the contributor who does the adapting.

Add new comment

Filtered HTML

  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <dl> <dt> <dd> <img>
  • Lines and paragraphs break automatically.

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
CAPTCHA
This question is for testing whether or not you are a human visitor and to prevent automated spam submissions.