From: Karen Wilson <fnkmw1@uaf.edu>
Subject: [Fwd: [PCCLIST] OFFICIAL: Authorities LCCN indexing change]
Date: June 4th 2008

-------- Original Message --------
Subject: [PCCLIST] OFFICIAL: Authorities LCCN indexing change
Date: Wed, 4 Jun 2008 08:53:54 -0400
From: Dean,Becky <deanr@OCLC.ORG>
Reply-To: Program for Cooperative Cataloging <PCCLIST@loc.gov>
To: PCCLIST@sun8.LOC.GOV


The message below has been sent to multiple lists; apologies in advance for multiple postings.
 
In order to help catalogers more readily identify the history of personal names previously on undifferentiated authority records and subsequently established as a separate authority record, beginning on June 1 the Connexion LCCN authority index will retrieve records containing LCCNs found in the 667 field in authority records.  The goal of this indexing change is to enable users to more easily identify changes made to personal names using unique control numbers.
 

With the June 1 Connexion install, LCCNs found in the 667 fields of newly added and changed authority records are included in the Connexion LCCN index.  This was accomplished by using changes made to the LCCN indexing functionality to scan the 667 field for the word: "Undifferentiated" (allowing for both upper and lower case).  If the word “undifferentiated” is identified in a 667 field, the software will then look for an LCCN in the 667 field and updates applied to the LCCN index.  An example of the indexing changes can be seen using LCCN no95033823.

 

Records containing LCCNs in 667 fields will automatically be included in all LCCN retrieval results and cannot be excluded when searching.  Please note, no textual data from the 667 field is indexed, rather, the word ‘undifferentiated’ is only used by internal processes to identify candidate records. 

 

No verification was done between LCCNs found in 667 fields and the 010 fields; if an LCCN in a 667 field contains a typographical error, please feel free to contact OCLC's Quality Control staff (authfile@oclc.org) requesting corrective action.

 

SEARCHING

The same searching guidelines are applicable to searching LCCNs in 667 fields that are noted for searching LCCNs found in 010 fields.  These are:

 

  • Type year portion (2 or 4 digits) and control number, with or without the hyphen.
  • Leading zeros in the control number portion are optional.
  • Alphabetic prefix is optional to increase precision.

    78-5201 or 785201
    2001-12345 or 200112345
    82-000012 or 82000012
    82-12 or 8212
    n85-204041 or n85204041
    sh85-61704 or sh8561704

 

INPUTTING 667 fields

Because the 667 field is a text field, it would be helpful to ensure the following formatting was employed when adding LCCNs in 667 fields. 

 

  • Type year portion (2 or 4 digits) and control number, with no hyphen. 
  • n  85204041 (two digit year + 1 character prefix: add two spaces following the 'n' prefix)
  • nr 99012578 (two digit year + 2 character prefix: add one space following the 'nr' prefix)
  • no2007016671 (four digit year + 2 character prefix: add zero spaces following the 'no' prefix)
  • n 2005035179 (four digit year + 1 character prefix: add one space following the 'n' prefix)
 
 
Becky Dean
OCLC
6565 Kilgour Place
Dublin, OH 43017
1-800-848-5878, ext. 5144
 
Luanne Goodson, NACO Coordinator
OCLC Quality Control Section
Phone: (800) 848-5878 x5274

<< Previous: FW: [OCLC-CAT] New technical bulletin available: OCLC-MARC Format Update 2008

| Archive Index |

Next: AK cataloging training in August >>

(archive rss , atom )

this list's archives:


Cataloging Roundtable

Subscribe to Catalog List:

|

Powered by Dada Mail 2.10.10
Copyright © 1999-2006, Simoni Creative.