PCC CATALOGING AT VANDERBILT
INTRODUCTION
Vanderbilt is a member of BIBCO, the monograph cataloging component of the Program for Cooperative Cataloging, and thus can code monograph records for books as “pcc” to proclaim to other libraries that the records are constructed according to the rules and all access points have corresponding authority records.
This does not mean, however, that we code all our original records for books as “pcc,” much less that our original catalogers upgrade any existing record we use to “pcc.” We do it when we are quite sure that our record is complete and accurate. If we upgrade an existing record and are not that sure about its completeness and accuracy, we don't authenticate it as a PCC record—we just enhance it.
It is helpful to consider the purposes for coding a record “pcc.” Are we offering to other libraries a record they are likely to use? Currency may be a factor—PCC cataloging for very old, obscure items may be a waste of time, especially if we are the first library to catalog it on OCLC or an existing record shows very few holding libraries. In such a case we may choose to do regular I-level original cataloging.
REQUIREMENTS
Generally we catalog our PCC records at full-level, rather than core-level—Vanderbilt has never gotten on the core-level bandwagon—but the records must meet at least core-level standards to be coded “pcc.” The following is a link to the BIBCO core record standard for books:
http://www.loc.gov/catdir/pcc/bibco/corebook.html
Note that “M” in this chart means “mandatory” and “MA” means “mandatory when applicable.” The chart also links at many points to “Combined Notes for PCC Core Records,” which explains the standards in more detail.
The core standard is understood to be a “floor” standard, and libraries are encouraged to add requirements to it as their needs dictate. As Vanderbilt has generally stuck to full-level cataloging, we have not gotten around to a formalized local interpretation of the core level. There is no rule against our using it, though. Do not label a record “core” (i.e., don't give it encoding level 4) because you just think there might be something slightly wrong with it—that's not what “core” is for. Code it as “I” or possibly “K” instead.
If you make a full -level PCC record, make the encoding level “blank,” not 4 as prescribed in the core standard.
We have only done PCC cataloging for printed books, but it may very well be that we could do it for an electronic text cataloged in the book format—we haven't tried that yet. If you want to try it, tell the cataloging team leader, because we'll all be curious!
AUTHORITY WORK REQUIRED FOR CODING RECORDS AS PCC
Let's say you're cataloging a book and you think you have a pretty good handle on it and can make a good record. Should you code it “pcc?” The descriptive portion of the record (i.e., everything but the access points) isn't much of an issue. Catalog according to AACR2, as we always try to do, and you should be fine. The main thing you need to think about is the access points. LC cataloging practice, which in essence is also PCC cataloging practice, requires that most types of access points have accompanying authority records. When making a PCC record we treat this as law.
NAME AND SUBJECT HEADINGS : Ordinary name (that is, not name-title) and subject headings must definitely be backed up by authority records. If one is not and you don't want to make an authority record, definitely do NOT code your record “pcc.”
SERIES HEADINGS : Traced series headings must be backed up by NACO authority records. Construct the caption and the number according to the practice shown on the NACO series authority record, not our local version of it. (If we do something slightly different in the $v, save that for our local version of the record.)
If you are creating a core record, you may leave a series untraced (490:0 :) if there is no existing NACO authority record for the series, or if an existing authority record says not to trace it (which is uncommon). If your record is full-level, you must trace the series and create a NACO authority record for it. If you are shy about creating an authority record for a series, don't code the record “pcc.” (As we try to have authority records in Acorn for all traced series, and we try not to leave series untraced for no good reason, you may want to see about creating an authority record locally. Alternatively, you may consider whether leaving the series untraced will be acceptable in this case.)
UNIFORM TITLES : These (including 7xx name-title access points) are where it gets complicated, because LC's interpretation of the cataloging rules does not require that authority records be made for all uniform titles, and where LC doesn't require them, PCC obviously doesn't require them either. NACO has an FAQ on uniform titles that may be helpful:
http://www.loc.gov/catdir/pcc/naco/utfaq.html#1
Taken from that document, here are some uniform title situations that do not require the creation of an authority record, according to LC/PCC practice:
1. If the $a portion of a 240 uniform title is the same as the title proper of the work—this happens in the case of translations—then generally you don't have to make an authority record. For example:
100:1 : $a Utrecht , Luuk.
240:10: $a Rudi van Dantzig. $l English
245:10: $a Rudi van Dantzig : $b a controversial idealist in ballet / $c Luuk Utrecht.
2. NACO's FAQ on uniform titles says this: If the item being cataloged is entered under a uniform title (thus, a 130), then generally you don't have to make an authority record. For example:
130:0 : $a Chicken soup for the teenage soul. $l Spanish
245:10: $a Sopa de pollo para el alma adolescente / …
NACO says, “This is because the bibliographic record provides all the access necessary via the 130 and the 245.” Oddly enough, there is an authority record in the NACO file for this very case! It would probably not be “wrong” to make one, but apparently LC and NACO say we don't have to. (Now, if this was a 730 rather than a 130, meaning that there was no corresponding 245, then an authority record would be required.)
3. Analytic added entries (i.e., added entries for works contained within the item being cataloged—these could be either 7xx name-title entries or 730's) generally do not require matching authority records. See question 15 in the FAQ linked above. The FAQ does say, “However, it must be noted that if any of these titles had been previously published with different titles, etc., a UT NAR would be made to record the variant title(s).” If your analytic added entry is for a translation of a previously published work, you will need to make an authority record for the translation (using a $l qualifier).
4. Related work added entries: As we understand it, if there is a bibliographic record for the related work in the LC database, you do not need to make an authority record. If, however, there is no separate bibliographic record for that work, you need to create an authority record as a “placeholder” for the nonexistent bibliographic record (see question 1 in the above-linked FAQ).
Here are some red flags that you will need to make an authority record:
1. A 240 collective uniform title (“Works,” “Poems,” “Selections,” etc.)
2. A uniform title with “Selections” at the end of it.
3. Most of the time, when you have a work previously published in another language and having a different title in its translation. (See part 2 in the previous sequence for an exception.)
Remember that we do not include nearly as many authority records for uniform titles in Vanderbilt's catalog, and they are not required nearly as often for local purposes. If you feel shy about making an authority record in a particular situation, you may want to catalog at regular “I” level.
CODING RECORDS AS PCC
The “big four” elements to remember, as Don Jones likes to call them, are these:
Enc lvl: This field should be blank if the record is full-level, or 4 if it is core-level. We use these codes only when making PCC records—otherwise we use “I” or “K.”
Source: This fixed field should be “c,” unless you are upgrading a previously existing record with source “blank,” most commonly a UKM record. In that case the field stays “blank.”
042: pcc
Always put your call number in an 050: 4: field.
Other than this, you just code as you would any other record (if a bit more carefully!).
P. Wilson 4/6/2006