I'm sorry, a correction is needed: when I said "terms of address indicating a person's occupation", I meant "descriptive phrases indicating a person's occupation". RDA does not currently allow terms of address, and this is not what I meant. 
 

From: Moore, Richard
Sent: 02 April 2012 09:11
To: 'Program for Cooperative Cataloging'
Subject: RE: [PCCLIST] Undifferentiated personal names: call for community discussion

I agree completely with the approach outlined by Gary, to add the content of 670 to $c of access points in newly-split records, and to flag them for review as part of the RDA conversion process.
 
Concerning Mary Charles's recommendation, the BL already avoids undifferentiation by creating RDA records using RDA qualifiers, but then we have some RDA-trained cataloguers. Institutions that are still exclusively contributing AACR2 NACO records might have a training issue with this, as RDA qualifiers (unlike the new 37X MARC fields) can't be added to AACR2 access points. 
 
I know the LCRIs are now frozen, but perhaps PCC might consider issuing a guideline expanding LCRI 22.19, and allowing the addition of terms of address indicating a person's occupation, to an AACR2 heading for a contemporary author (<cough> these aren't exactly uncommon on the file as it is...) .
 
It's food for thought, and I think I will move from encouraging our cataloguers not to add authors to undifferentiated records, to insisting that cases are referred to RDA-trained cataloguers, to apply an RDA qualifier. It's my view that we should be able to create unique access points for almost all persons by applying a qualifier for "Profession or Occupation", especially if we take a relaxed view on the definition of "Occupation".
 
It looks increasingly likely that the RDA transition of the authority file could provide the opportunity, finally, to eliminate the practice of undifferentiated records (while noting that RDA allows them).
 
 
Regards
Richard
_________________________
Richard Moore
Authority Control Team Manager
The British Library
                                                                       
Tel.: +44 (0)1937 546806                               
E-mail: [log in to unmask]                           

 



From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Gary L Strawn
Sent: 01 April 2012 16:37
To: [log in to unmask]
Subject: Re: [PCCLIST] Undifferentiated personal names: call for community discussion

Here's the list I came up with of records having 008/32='b' but fewer than 2 "author of" 670 fields.  (Note that this list is based on the local copy of the LC/NACO file, so it's possible that there will be the odd difference between this list and what you see in OCLC.)  The records in this list can be inspected and modified to our mutual advantage at any time; those interested please coordinate amongst yourselves.  As I hinted earlier, there are no doubt additional records with other categorical problems that can be identified and worked through in the future.

 

Gary L. Strawn, Authorities Librarian, etc.

Northwestern University Library, 1970 Campus Drive, Evanston IL 60208-2300

e-mail: [log in to unmask]   voice: 847/491-2788   fax: 847/491-8306

Forsan et haec olim meminisse iuvabit.         BatchCat version: 2007.22.416

 

From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Patricia A. Williams
Sent: Saturday, March 31, 2012 4:52 PM
To: [log in to unmask]
Subject: Re: [PCCLIST] Undifferentiated personal names: call for community discussion

 

I agree with Mary Charles' recommendation, that PCC should put an immediate moratorium on the creation of new undifferentiated name headings, and also on the addition of new entities to existing undifferentiated names.   Instead, PCC should encourage catalogers to add RDA qualifiers to headings, if no other distinguishing information is available, even if the bibliographic record for which the name is being used is coded AACR2.  If the intention is to re-code all AACR2 authority headings as RDA eventually, what difference will it make in the long run that RDA auths are being created for AACR2 bibs? 

 

I also like Gary's temporary solution, to use the titles in the 670 fields  to differentiate headings until the heading can be evaluated for RDA use.  I think this is a good practical solution and would be more helpful to us cataloging practitioners in the short run.  The recommendations in the discussion paper may be a good future way of handling authority data, but we need more immediate practical solutions.  I too would volunteer to help review undifferentiated names, since my institution is already applying RDA to almost all of our original cataloging.

 

 

Pat Williams

Head, Monographic Original Cataloging

University of Chicago Library

 

 


From: Program for Cooperative Cataloging [[log in to unmask]] On Behalf Of Lasater, Mary Charles [[log in to unmask]]
Sent: Saturday, March 31, 2012 4:06 PM
To: [log in to unmask]
Subject: Re: [PCCLIST] Undifferentiated personal names: call for community discussion

Thank you Gary. I knew you could do this and I will be more than happy to undertake the review of some of the 3, 194 records that do not have 2 670 fields and require manual review. I hope we can start ASAP. I know that various ‘clean up’ for RDA has already begun.  Perhaps a sample ‘acceptable’ record could be prepared and then the 3, 194 records divided among volunteers.

 

I also think the current practice should cease immediately and any work on undifferentiated personal names could begin the process of splitting these apart instead of adding to the 59,659 records. If I’m viewing RDA appropriately, we will be able to qualify many more names. Hopefully the RDA NACO training will be available soon.

 

Mary Charles

 

 

From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Gary L Strawn
Sent: Saturday, March 31, 2012 3:34 PM
To: [log in to unmask]
Subject: Re: [PCCLIST] Undifferentiated personal names: call for community discussion

 

Indeed.  Since records susceptible to being split must contain at least two "Author of" (or similar) 670 fields, why not use the contents of those fields as $c in the 1XX field, and mark the new records as "requires review before able to be used under RDA"?  That would allow the split-up records to work well enough in current systems, and allow for something to be done more calmly in the future.  Subfield $0 could still be used in bibliographic records.  The meaning of 008/32 could be left alone for now, and the definition enhanced (or the position made obsolete) as the future becomes less murky.

 

I find 59,659 name records with 008/32='b' in the local copy of the LC/NACO authority file.  Of these, a surprising 3,194 do not have at least 2 670 fields that begin with a left square bracket, suggesting that they are not well-formed records; whether the error is in 008/32 or the 670s varies.  (Here are a few examples: n 00044405, n 78039508, no2003127114.  For this quick pass I did not also look for records that have 2 or more appropriate 670s, and yet have at least one 670 field before the first bracketed 670; bound to be some.)  No matter what fate befalls records with 008/32=b, the cleanup of ostensibly malformed records with 008/32='b' is a necessary project just waiting for someone.

 

I don't find any mention in the document of handling for authority records for name/title headings whose name portion is labeled undifferentiated.  If new headings are created (by sticking on $c) as undifferentiated records are teased apart, I assume that these name/title records would require individual review.  I find 2670 name/title records whose name part matches the 100 field in an authority record with 008/32='b'.  Not surprisingly, the correspondence of the titles between the two is not always obvious.

 

                670 fields:

[Added entry of Huntington library ...]

[Author of The truth about smoking]

                100 $t:

                                Young Indiana Jones and the circle of death

 

                670 fields:

[Author of The rebels]

[Co-editor of The Queensland house]

                100 $t:

                                Man who lost China

 

                670 fields:

[Author of Ku wan chih nan]

[Author of Shi guo feng tong jia zi kao]

                100 $t:

                                Gu wan zhi nan

 

(Yes, I understand full well what's going on in the last example.  *You* can do the programming for that one!)

 

Gary L. Strawn, Authorities Librarian, etc.

Northwestern University Library, 1970 Campus Drive, Evanston IL 60208-2300

e-mail: [log in to unmask]   voice: 847/491-2788   fax: 847/491-8306

Forsan et haec olim meminisse iuvabit.         BatchCat version: 2007.22.416

 

From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Lasater, Mary Charles
Sent: Saturday, March 31, 2012 10:14 AM
To: [log in to unmask]
Subject: Re: [PCCLIST] Undifferentiated personal names: call for community discussion

 

All,

 

I must admit that my first reaction to this is disappointment. Again the cataloging community seems to be looking to the future, instead of implementing something that will work with our current systems, ASAP. I have been pushing for eliminating ‘undifferentiated authority records’ much longer than nine years, but what I am seeing in this paper would require new systems and new technology that again costs money. I’m concerned that by the time these suggestions are implemented we will all be retired or dead and authority control will be ‘history’.

 

We should allow for qualifiers that make each name (including geographic)  unique and we should not require libraries to invest in new technology.

 

My 2 cents,

 

Mary Charles Lasater

Authorities Coordinator (23+years)

Vanderbilt University  

From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Barnhart, Linda
Sent: Thursday, March 29, 2012 2:44 PM
To: [log in to unmask]
Subject: [PCCLIST] Undifferentiated personal names: call for community discussion

 

The Program for Cooperative Cataloging Policy Committee (PoCo) has been monitoring the discussion on various cataloging email lists over the past months and noticed a recurring topic of (and frustration with) authority records for undifferentiated personal names.  We wondered whether this was a problem that we should tackle now, in conjunction with the imminent changes to the LC/NACO authority file to align it with RDA implementation.  Even though this is not an RDA issue, we decided yes.

 

Two PoCo leaders, Philip Schreur and John Riemer, volunteered to prepare a discussion paper, which is attached to this message and is posted on the PCC web site.  We invite community comment on this discussion paper beginning now through June 22, 2012.  The discussion will continue in person at the PCC Participants Meeting at the ALA Annual Conference in Anaheim.  There are several options for you to provide input, and the PCC Secretariat has agreed to compile the issues for the discussion.  To participate in this discussion, you may:  (1)  send your comments privately to the PCC Secretariat at [log in to unmask]; (2) post your comments publicly to one of the cataloging email lists, preferably PCCLIST, with a cc to [log in to unmask]; (3) voice your comments in person at the PCC Participants Meeting at the ALA Annual Conference in Anaheim in June.  While PoCo members will be reading the comments, we will not be able to respond to each comment.

 

We expect that the community comments in the coming months will help us prepare for and design the public forum on this topic at the PCC Participants Meeting, and will enable those unable to attend that meeting to participate.   We are particularly interested in hearing from authorities and ILS vendors, and hope that providing this discussion paper now gives them time to think and react.  We also welcome reactions from the international community, especially from CEAL, where we know this topic has particular impact. 

 

Following the PCC Participants Meeting at ALA Annual, PoCo will reach a decision about the next steps in this process.  We look forward to your input on this substantive issue. --  Linda

 

Linda Barnhart

Head, Metadata Services Department and

     Chair, Program for Cooperative Cataloging, 2011-12

UC San Diego Libraries

[log in to unmask]

858-534-6759

 

 

 
https://listserv.loc.gov/cgi-bin/wa?A3=ind1204&L=PCCLIST&E=quoted-printable&P=123404&B=------_%3D_NextPart_001_01CD10A9.2C4E1D7A&T=text%2Fhtml;%20charset=us-ascii&pending=
listserv.loc.gov
crawl=CC-MAIN-2022-33
36789
application/http; msgtype=response
sha1:XWNZDBBHB5TRTRAB4JP6FYAYUVCUNLZ7
<urn:uuid:800ff32c-e7c3-40f4-b22c-18e1d3a0865d>
2022-08-14T00:14:14Z
140.147.239.86
text/html
sha1:Q4G22H5DNQAXPVI5RIL7KAOQBRUOQVS5
<urn:uuid:6022f612-b528-4338-b525-c8f2abfcaeeb>
https://listserv.loc.gov/cgi-bin/wa?A3=ind1204&L=PCCLIST&E=quoted-printable&P=123404&B=------_%3D_NextPart_001_01CD10A9.2C4E1D7A&T=text%2Fhtml;%20charset=us-ascii&pending=
response
<urn:uuid:85dbe373-d00f-413d-9b05-43273cf35030>
isPartOf: CC-MAIN-2022-33
publisher: Common Crawl
description: Wide crawl of the web for August 2022
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-172
software: Apache Nutch 1.18 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.4-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/