When & When NOT to Code an Original Bib Record as PCC (draft)

REMINDER: YUL is not authorized to create pcc records for serials, non-print formats, and mixed material, so these guidelines only apply to book format. For non-authorized formats, do original cataloging following RDA/LC PCC Policy Statements, and enter ‡e rda in 040, but do not code the bib record as pcc.

BOOKS and MICROFILM (of books). Generally catalog and code original cataloging for books as rda and pcc (008 Source c and 042 pcc). Microfilm of books may be coded as pcc; follow the LC PCC Policy Statement practice for reproductions.

Do not code bib records for books as pcc if any of the following conditions apply to your bib record:

1. Not all of your AAPs are backed up by an RDA NAR.
   • If there is an AACR2 NAR, generally code it to RDA in the NAF if the AAP is consistent with RDA. Count as an update in statistics even if this was the only change made to the NAR.
   • EXCEPTION: If the NAR has extensive references requiring review, use judgment in deciding whether to recode the NAR to RDA even if the AAP is RDA compliant. If the decision is to not recode, do not code the bib record as pcc.
   • Use judgment with regard to 3xxs, none of which are mandatory at this time. Add 046 if readily available (from the 670s, including the 670 for the book being cataloged if the information is new)
   • Use judgment to decide whether to make new NARs in order to authenticate your record as pcc.
   • If the NAR has a 667, review and revise the NAR to RDA form. If the AAP on the AACR2 NAR is consistent with RDA, re-code it to RDA and remove the 667 even if extensive references need review.
      
2. Your record lacks 050 _4 ‡a.
   • Reminder: 050 _4 should never include local practices (folio, oversize, "(LC)" etc.)
   • EXCEPTION. For rare book cataloging, if your 040 has ‡e rda ‡e dcrmb it can be coded as pcc as long as none of the other non-pcc compliant conditions on this list apply.
      
3. Your bib record has a 130 field without an AR, or the AR is not coded as RDA.
   • Do not update an AACR2 AR if it exists, unless the AACR2 AAP conflicts with RDA/PCC instructions
   • Do not create an AR if no AR exists.
   • On the bib record, follow RDA & PS's when formulating the 130.
   • Remember that a 130 is made for conflicting monograph titles proper as well as for serials.
   • EXCEPTION: Specialist units may routinely make or update NARs for music, laws, and sacred scriptures, following the specific instructions in RDA and the LC PCC Policy Statements.

1. Your bib record has a 240 or a 700 author/title analytic without an author/title RDA AR for the work/expression.
   • Do not update an AACR2 AR if one exists unless it conflicts with RDA form
   • Do not create an author/title AR if none exists
   • EXCEPTION: Specialist units can routinely make or update NARs for music, laws, and sacred scriptures, following the specific instructions in RDA and the LC PCC Policy Statements.
      
2. Your bib record has a 111/711 or 110/710 with ‡b where an AR has not been created for the individual conference.
   • Do not make an AR for the individual conference.
   • If there is a NAR for the ongoing conference, and the RDA 1xx/7xx on your bib record does not conflict with it, leave the NAR as is.
   • EXCEPTION. If the NAR conflicts with the RDA form, update the NAR to RDA form and make a NAR for the individual conference (to avoid a possible flip by Backstage). If the other AAPs are backed up with RDA ARs, code the bib record as pcc.
      
3. A series added entry (8xx) is not backed up an SAR.
   • YUL conditions for when to make an SAR still apply; make the SAR following PCC RDA guidelines; if all other PCC conditions are met, code the record as pcc
   • If YUL conditions do not apply and the cataloger decides not to trace (490 0) and if all other PCC conditions are met, code the record as pcc
   • If YUL policies do not require an SAR, and the cataloger decides to trace (490 1) without making an SAR, do not code as PCC even if all other PCC conditions apply
      

Issued: 10/22/2013