[Yulcat-l] Update to OCLC's Response to the Library of Congress Series Decision

[Steven Arakawa]

Just to make sure I understand this correctly re 1.-2.

1. If there is a non-LC record not coded as pcc in WorldCat with a 440 or 
490 1-830, and an LC record is loaded, the LC record will replace the 
non-LC record except for the series.

2. If there is a non-LC record coded as pcc in WorldCat it will not be 
replaced by the LC record, even if the LC record does not have a series.

Is this interpretation correct? While I don't have much a problem with #1, 
it's too bad the formula used for #1 could not be applied to #2. In the 
OCLC environment, that means the LC bibliographic record is lost to members 
in this scenario, even though a full/CIP LC record is preferable for 
FastCat workflow. (And is probably superior in quality to pcc records in 
some areas and is no worse than pcc records in the other areas, except for 
series, and only if you assume all series should be traced.)

--Steven

At 12:17 PM 7/10/2006, Joan Swanekamp wrote:
>Several people asked me about how OCLC was going to handle this situation 
>... here is the response.
>___________________________________________________________________________________
>On July, 9, 2006, OCLC installed the last of the software changes 
>announced to assist with the implementation of LC's decision on series. 
>Specific changes OCLC has implemented are--
>
>1. Changes were made to the software used to load Library of Congress 
>records into WorldCat so that, if the existing WorldCat record contains 
>controlled series access (either field 440 or fields 490, first indicator 
>'1,' and an 8XX field) and the incoming LC record contains only a series 
>statement (field 490, first indicator '0'), the controlled series access 
>will be retained. Implemented July 9, 2006.
>
>2. Since, as part of the change in series practice, the Library of 
>Congress has ceased to use the 042 code 'pcc' in records for monographs 
>and integrating resources, OCLC has also adjusted the hierarchy that 
>governs which record takes precedence when incoming records are compared 
>with existing WorldCat records to insure that a PCC record is not bumped 
>by a record not meeting PCC standards. Implemented June 11, 2006.
>
>3. OCLC has changed existing Database Enrichment capabilities ( 
>http://www.oclc.org/support/tips/worldcat/tip7.htm ) so that fields 440, 
>490, and 8XX can be added, changed or deleted by any user with a 
>full-level cataloging authorization. This allows cataloging users to, for 
>example, change series treatment in LC records to match existing authority 
>records. Users will receive a Database Enrichment credit for such changes. 
>Implemented July 9, 2006.
>
>The memo at 
><http://www.oclc.org/news/announcements/announcement191.htm>http://www.oclc.org/news/announcements/announcement191.htm 
>includes the full, updated OCLC response with additional commentary on 
>steps that have been or will be undertaken. We will be update 
>documentation in the next few months to reflect these changes.
>
>Rich Greene
>OCLC, Inc.
>6565 Frantz Road
>Dublin, OH 43017
>614-764-6154
>email: richard_greene at oclc.org
>
>_______________________________________________
>Yulcat-l mailing list
>Yulcat-l at mailman.yale.edu
>http://mailman.yale.edu/mailman/listinfo/yulcat-l

----------------------------------------------------------
Steven Arakawa
Catalog Librarian for Training & Documentation
Catalog Dept. Sterling Memorial Library. Yale University.
P.O. Box 208240 New Haven, CT 06520-8240
(203)432-8286 steven.arakawa at yale.edu
   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.yale.edu/pipermail/yulcat-l/attachments/20060710/babacef5/attachment.htm