LISTSERV mailing list manager LISTSERV 16.0

Help for PCCLIST Archives


PCCLIST Archives

PCCLIST Archives


PCCLIST@LISTSERV.LOC.GOV


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

PCCLIST Home

PCCLIST Home

PCCLIST  December 2016

PCCLIST December 2016

Subject:

Re: AACR2 multiple language title AAPs to RDA AAPs

From:

"Theroux, Manon" <[log in to unmask]>

Reply-To:

Program for Cooperative Cataloging <[log in to unmask]>

Date:

Thu, 22 Dec 2016 12:59:02 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (1 lines)

"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



Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000
October 2000
September 2000
August 2000
July 2000
June 2000
May 2000
April 2000
March 2000
February 2000
January 2000
December 1999
November 1999
October 1999
September 1999
August 1999
July 1999
June 1999
May 1999
April 1999
March 1999
February 1999
January 1999
December 1998
November 1998
October 1998
September 1998
August 1998
July 1998
June 1998
May 1998
April 1998
March 1998
February 1998
January 1998
December 1997
November 1997
October 1997

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager