"Summary of Programmatic Changes to the LC/NACO Authority File: What LC-PCC RDA Catalogers need to know," issued during Phase 1-2 processing, has instructions on what to do with authority records containing an ampersand in $l (see p. 4): http://www.loc.gov/aba/rda/pdf/lcnaf_rdaphase.pdf >>>3. Authority records with 1XX fields that contain an ampersand in $l: Any AACR2 authority record with an ampersand in $l will be labeled with a 667 field as needing review under RDA (about 13,000 authority records). What an RDA cataloger should do: If an authority record with an ampersand in $l is encountered, create substitute RDA records for each language expression represented in $l if they don’t already exist (they often will) and report the authority record with the ampersand for deletion. Do not ‘re-use’ the authority record with an ampersand for a single language expression. That page also has instructions for records containing $l Polyglot: >>>2. Authority records with 1XX fields that contain Polyglot in subfield $l: Any AACR2 authority record with polyglot in $l will be labeled with a 667 field as needing review under RDA (fewer than 700 authority records). What an RDA cataloger should do: If an authority record with $l Polyglot is encountered, and the cataloger can determine which languages were covered by the ‘polyglot’ designation, create substitute RDA authority records for each required language expression covered by the ‘polyglot’ authority record if they don’t already exist (they often will) and report the authority record with $l Polyglot for deletion. If the cataloger can’t determine all of the languages covered by the ‘polyglot’ record, they should create only as many records as they need for the resource they are cataloging, if they don’t already exist. In this case, don’t report the original ‘polyglot’ record for deletion or remove the 667 field. The document is available on the PCC website on the "Post-RDA Implementation Guidelines and Standards" page: http://www.loc.gov/aba/pcc/rda/PCC%20RDA%20guidelines/Post-RDA-Implementation-Guidelines.html as well as via the NACO home page (Documentation & Updates section): http://www.loc.gov/aba/pcc/naco/ Deletion requests should be sent to [log in to unmask] Thanks, Manon -- Manon Théroux Cooperative Cataloging Program Specialist Cooperative and Instructional Programs Division Library of Congress [log in to unmask] -----Original Message----- From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Yang Wang Sent: Tuesday, December 20, 2016 3:54 PM To: [log in to unmask] Subject: Re: [PCCLIST] AACR2 multiple language title AAPs to RDA AAPs Bob, Thanks a lot for your kind guidance! I will leave the AACR2 heading alone and will create 2 AAPs for the expressions. Yes, it is best to qualify each expression with $s (BUR (Series). Classici antichi) in this case, considering many translators were involved in this name/title series, comprising a little over 20 volumes. Best regards, Yang -----Original Message----- From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Robert Maxwell Sent: Tuesday, December 20, 2016 1:14 PM To: [log in to unmask] Subject: Re: [PCCLIST] AACR2 multiple language title AAPs to RDA AAPs Yang, A work-level authority record for this work already exists: 010 n 79031980 1000 Plutarch. ǂt Lives The AACR2 "... $l [Language] & {Language]" authorized access points are simply not valid in RDA and in my opinion we're better off just ignoring the NARs that contain them. We definitely shouldn't "update" them. If you like, report them for deletion after you've created new expression level records. But I hope they'll eventually just get zapped from the authority file, so although I used to report them for deletion, currently I'm pretty much just ignoring them and creating new records representing the expressions as needed. What you should do in this case is what we need to do with any expression: 1. Start with the authorized access point for the work: Plutarch. Lives 2. Add one or more identifying elements to specify the expression. In this case, if you're going to specify both expressions, you need two new NARs. For the Italian expression: 100 0 Plutarch. $t Lives. $l Italian $s ([whatever you decided to use to qualify]) , e.g.: 100 0 Plutarch. $t Lives. $l Italian $s (BUR (Series). Classici antichi) I suggest qualifying by the name of the series because (I assume) there are several translators. If there are just one or two, I'd qualify by the surname(s) of the translator. You could also include a variant access point based on the Italian title: 400 0 Plutarch. $t Vite parallele $s ((BUR (Series). Classici antichi) Then add in *expression* elements (not work-level elements, this is an expression record), including language (377), content type (336) date of expression (046), other distinguishing characteristic of the expression (381--this might include the information about series/multipart monograph, the name of the publisher, etc., coded below in 373 and 380), possibly 500s for the translators, or other relationships you'd like to bring out. For the Greek, LC would simply use the authorized access point for the work (Plutarch. Lives). I would make an authorized access point for the specific Greek expression: 100 0 Plutarch. $t Lives. $l Italian $s (BUR (Series). Classici antichi) And add whatever else to the expression record as suggested above. The point is, don't reuse or update a NAR for a bilingual AACR2 heading, always create new records; and the authorized access point for the expression is based on the authorized access point for the work, so it doesn't include the Italian title of the work. Bob Robert L. Maxwell Ancient Languages and Special Collections Librarian 6728 Harold B. Lee Library Brigham Young University Provo, UT 84602 (801)422-5568 "We should set an example for all the world, rather than confine ourselves to the course which has been heretofore pursued"--Eliza R. Snow, 1842. -----Original Message----- From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Yang Wang Sent: Tuesday, December 20, 2016 9:49 AM To: [log in to unmask] Subject: Re: AACR2 multiple language title AAPs to RDA AAPs Here's a related case I have to deal with right now (speaking of the d----). I need to update this existing Name/Title series record (NAF no2001054471 = ARN05531286): 100 0 Plutarch. ‡t Lives. ‡l Italian & Greek (Rizzoli editore) 400 0 Plutarch. ‡t Vite parallele 430 0 Vite parallele 643 Milano ‡b Biblioteca universale Rizzoli . . . . . 667 THIS 1XX FIELD CANNOT BE USED UNDER RDA UNTIL THIS RECORD HAS BEEN REVIEWED AND/OR UPDATED 670 Plutarch. Pelopida, 1998: ‡b ser. t.p. (Vite parallele) To update it to a work-level RDA record, the language expression " Italian & Greek" would have to go. I am thinking of updating it like this: 100 0 Plutarch. ‡t Vite parallele (Rizzoli editore) 373 Rizzoli editore ǂ2 naf 380 Series (Publications) ǂ2 lcsh 380 Multipart monograph 381 Rizzoli editore 400 0 Plutarch. ‡t Lives. ‡l Italian & Greek (Rizzoli editore) ‡w nnea 430 0 Vite parallele (Rizzoli editore) 430 0 Vite parallele in BUR 530 0 ‡w r ‡i In series: BUR (Series). ‡p Classici antichi . . . . . . 670 Plutarch. Pelopida, 1998: ‡b ser. t.p. (Vite parallele) 670 Plutarch. Coriolano, 2010: ǂb title page (Vite parallele) series title page (Vite parallele in BUR) title page verso (BUR Classici greci e latini) I am wondering if the 1st 400 (Plutarch. ‡t Lives. ‡l Italian & Greek (Rizzoli editore) ‡w nnea) is appropriate here, since it's an expression-level reference and perhaps shouldn't be mixed with the work-level record. Without it, would it be possible to make a machine generated "global" change to all the existing bibs that contain "800 1 Plutarch. ‡t Lives. ‡l Italian & Greek (Rizzoli editore)"? I need collective wisdom on this. Your advice, recommendation, and correction are most welcome. Thanks! Yang -----Original Message----- From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Ehlert, Mark K. Sent: Monday, December 19, 2016 2:56 PM To: [log in to unmask] Subject: Re: [PCCLIST] AACR2 multiple language title AAPs to RDA AAPs From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Gene Fieg Sent: Monday, December 19, 2016 1:45 PM > > In the light of the information that I have seen on various listservs > that inform me that Phase 3 probably will not split the languages on > multiple language title AAPs... A PCC task group in late 2014 (!) posted a Phase 3 recommendation for handling records that represent multiple language expressions here: http://www.loc.gov/aba/pcc/rda/RDA%20Task%20Groups.html Bottom line: delete the records. Since I'm out of the loop these days, I pose the question: Is this recommendation still being considered, or no? -- Mark K. Ehlert O'Shaughnessy-Frey Library Cataloging and Metadata University of St. Thomas Librarian 2115 Summit Avenue Phone: 651-962-5488 St. Paul, MN 55105 <http://www.stthomas.edu/libraries/> "Experience is by industry achieved // And perfected by the swift course of time"--Shakespeare, "Two Gentlemen of Verona," Act I, Scene iii