[yul-naco] Fwd: PCC Reporting of Database Maintenance

[Manon Theroux]

Dear NACO catalogers,

Forwarding a reminder from LC about the proper 
channels to follow when you discover that an 
authority record needs to be modified or deleted. 
Please do not send requests to delete duplicate 
name authority records to OCLC or CPSO. Instead, 
send them to me and I will forward them along to 
our liaison on the LC Cooperative Cataloging 
Team. LC will delete the duplicate record and 
subsequently distribute the deletion to both utilities.

Let me know if you have any questions,

-Manon


>Date:         Tue, 15 Aug 2006 14:31:09 -0400
>Sender: Program for Cooperative Cataloging <PCCLIST at loc.gov>
>From: Antony Robert David Franks <afra at loc.gov>
>Subject: PCC Reporting of Database Maintenance
>
>We have had a recent rash of reporting 
>confusions among PCC members over reporting 
>database maintenance to OCLC, and/or LC--CPSO, 
>and/or LC--Coop Team. These confusions are 
>resulting in this work either not getting done, or in delays.
>
>PCC Members
>
>There are two types of database maintenance 
>which must be reported by member catalogers to 
>their institution's liaison for relaying to the 
>LC liaison. See the NACO Participant's 
>Manual  at http://www.loc.gov/catdir/pcc/naco/npm3rd.pdf
>
>1. Deletions of Name Authority Records (NARs) in 
>the LC/NACO Authority File and the annotation of 
>the 010 field with a $z field. Due to database 
>security, this work must be done at LC. These 
>changes are distributed on a regular basis to 
>the other copy holders of the authority file 
>(which includes OCLC) for further distribution or other use.
>
>Other revisions to records in the LC/NACO 
>Authority File, such as (but not limited to) 
>conflict resolution or typo correction are 
>within the abilities of independent NACO member institutions.
>
>2. Revisions to existing Library of Congress 
>Subject Heading authority records. The master 
>file for LCSH is a separate database to which 
>only a specific unit within LC has access. PCC 
>members must use the regular SACO procedures for 
>proposing changes of any kind  to subject 
>authority records. The guidelines for revisions 
>to subject authority headings, along with a web 
>form for making such proposals, are at 
>http://www.loc.gov/catdir/pcc/saco/saco.html
>
>There are three important points to make about this workflow:
>
>1. Sending messages to the appropriate LC 
>personnel avoids delays as communications of 
>this nature sent to either OCLC or CPSO by PCC 
>members are identified and relayed to the appropriate LC staff.
>
>2. Catalogers of member institutions should send 
>these needs to their institution's NACO liaison, 
>who will then send them to the LC liaison. The 
>individual e-mails from the combined catalogers 
>of 500+ PCC member institutions when condensed 
>into the in boxes of six Cooperative Program Specialists in LC doth chaos make.
>
>3. We trust independent members to make 
>revisions to authority records in the LC/NACO 
>Names Authority File. When one authority record 
>is to be deleted and another retained, member 
>catalogers should transfer the data needed from 
>one record to the other. Unfortunately, there is 
>no way to "merge" authority records.
>
>4.  There is no reason to make duplicate reprots to all three. Once is enough.
>
>Non-PCC Members
>
>Work of the above two types should be reported to CPSO at cpso at loc.gov
>
>
>Anthony R.D. Franks
>Team Leader, Cooperative Cataloging Team
>Library of Congress
>202-707-2822 (voice)
>202-252-2082 (fax)

____________________________________________

Manon Théroux
Authority Control Librarian/NACO Coordinator
Catalog Department
Yale University Library
P.O. Box 208240
New Haven, CT 06520-8240

203-432-8376 (tel)
203-432-7231 (fax)
manon.theroux at yale.edu 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.yale.edu/pipermail/yul-naco/attachments/20060815/fb007c05/attachment.htm