LISTSERV mailing list manager LISTSERV 16.0

Help for PCCLIST Archives


PCCLIST Archives

PCCLIST Archives


[email protected]


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  November 2014

PCCLIST November 2014

Subject:

Re: 667 for deletes

From:

"Bremer,Robert" <[log in to unmask]>

Reply-To:

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

Date:

Fri, 21 Nov 2014 15:42:48 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (61 lines)

Marking records as duplicates in field 667 or any other field is highly problematic.  The reason is that we do not work in one common file, but rather in copies where changed records are transmitted and added or replaced in the master copy at LC with a built-in time delay.  A cataloger working in OCLC at 10 in the morning, adds 667 to a record to be deleted and reports that record to LC at the same time.  At 2 in the afternoon, an LC staff member deletes the duplicate in the master file.  Quick turnaround time on lots of reported duplicates by LC staff is not uncommon.  Now a delete record is in queue to be distributed to all the NACO nodes, but a revised version of the very same record is in the OCLC contribution queue.  When that updated record arrives at LC the updated record is rejected.  Every rejected record requires manual follow-up on the part of OCLC staff to determine if the rejected record needs to be re-contributed or if it contains information that needs to be added to another authority record.  I presume the same is true for other NACO nodes.

If bibliographic access points are controlled to the record to be deleted in WorldCat, then changing coding in the corresponding to-be-deleted authority record plays havoc with the access point in the bibliographic record potentially causing it to be uncontrolled.  Currently, access points controlled to a deleted authority record are automatically re-controlled to the form of the authorized access point in the retained authority record when the LCCN of the deleted authority record is cross-referenced in 010 $z of the retained authority record.  Change the status of the to-be-deleted authority record ahead of its deletion and that automated updating potentially breaks.

The reasons for not doing all of this now are the same as outlined in this old message that Ryan Finnerty pointed out:

http://listserv.loc.gov/cgi-bin/wa?A2=ind0710&L=pcclist&T=0&P=3013

Robert Bremer
[log in to unmask]


-----Original Message-----
From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Frank, Paul
Sent: Friday, November 21, 2014 7:46 AM
To: [log in to unmask]
Subject: Re: [PCCLIST] 667 for deletes

Adam, 

These are the types of issues I will discuss with colleagues in the Policy and Standards Division, and I will take your suggestions as well for PSD's consideration. For now, though, please just let the 667 note serve as the delete notification-- your wording is fine, but as long as the field indicates that the record is being reported for deletion, other wording is ok, too. We will definitely add an example with suggested wording to the 667 instruction in DCM Z1 once the issue has been discussed and finalized. 

Paul

Paul Frank
Acting Coordinator, NACO and SACO Programs Cooperative Programs Section Cooperative and Instructional Programs Division Library of Congress
101 Independence Ave., SE
Washington, DC 20540-4230
202-707-1570
[log in to unmask]


 

-----Original Message-----
From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Adam L. Schiff
Sent: Thursday, November 20, 2014 8:03 PM
To: [log in to unmask]
Subject: [PCCLIST] 667 for deletes

I've informed our staff that I will start using the 667 for records to be deleted, and that they may see them on other records as well.  I think it might be nice to have some kind of standardized wording.  Something like this perhaps?:

667  Record reported for deletion. Use instead: <LCCN of record to use>

The one other thing that I would like to raise is whether there is some place else in the record where we can code the fact that the NAR is not to be used, so that catalogers using OCLC's control headings feature would not be able to control an access point that linked to the NAR about to be deleted?  There are undoubtedly many catalogers that simply control headings without actually viewing a name authority record.  If they don't view it, they won't see the 667 note.  Is there some code we can add (heck, we're already adding the 667 note now) that would prevent that NAR from being used by the control software?  Maybe changing 008/14 (Name use) from "a" to "b"?  Or 008/33 (Auth status) to "n"?

I realize that all of this would be optional, but if a cataloger wanted to code the record as invalid in addition to the 667, may they?

Adam Schiff

**************************************
* Adam L. Schiff                     * 
* Principal Cataloger                *
* University of Washington Libraries *
* Box 352900                         *
* Seattle, WA 98195-2900             *
* (206) 543-8409                     * 
* (206) 685-8782 fax                 *
* [log in to unmask]           * 
**************************************

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

March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
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