Error during command authentication.

Error - unable to initiate communication with LISTSERV (errno=111). The server is probably not started. LISTSERV 16.0 - PCCLIST Archives

Print

Print


If it's anything like CONSER practice, the "premarc" code should be retained, with "pcc" given as an additional code. However, it will be interesting to see the official word from LC.

 

Kevin M. Randall

Principal Serials Cataloger

Northwestern University Libraries

Northwestern University

www.library.northwestern.edu

[log in to unmask]

847.491.2939

 

Proudly wearing the sensible shoes since 1978!

 

From: Program for Cooperative Cataloging <[log in to unmask]> On Behalf Of Adam L Schiff
Sent: Tuesday, October 29, 2019 2:48 PM
To: [log in to unmask]
Subject: Re: [PCCLIST] premarc question

 

I would probably just add another $a to the 042 with code pcc, along with the changes required to fixed fields to identify the record as BIBCO.  In the LC catalog, their record is still going to just have the 042 premarc code.  Perhaps that’s a good argument for removing the premarc code and replacing it with pcc, since either way, the records won’t be in synch anymore.  Perhaps someone from LC PTCP will let us know what they think the most correct action is. 

 

Adam Schiff

University of Washington Libraries

 

From: Program for Cooperative Cataloging <[log in to unmask]> On Behalf Of Salisbury, Preston
Sent: Tuesday, October 29, 2019 11:19 AM
To: [log in to unmask]
Subject: premarc question

 

If I encounter a record such as OCLC# 687219 (LCCN 17013589) which is a DLC record with 042 code premarc, and I wish to bring it up to current cataloging standards, what would be the proper procedure to follow? Do I just update the record and leave the 042 in place? Delete the 042 after updating the record and change the encoding level to blank? Or something else?

 

Thanks for any guidance on this.

 

Preston Salisbury

Assistant Professor and Monographic Cataloger

Mississippi State University

662.325.4618

[log in to unmask]