heb-naco  

Fw: [OCLC-NON-LATIN] OFFICIAL: Authorities LCCN indexing change

Heidi Lerner
Wed, 04 Jun 2008 07:40:49 -0700

Heidi G. Lerner
Hebraica/Judaica Cataloger
Catalog Dept.
Stanford University Libraries
Stanford, CA  94305-6004
ph: 650-725-9953
fax: 650-725-1120
e-mail: [EMAIL PROTECTED]
----- Original Message ----- 
From: Dean,Becky 
To: [EMAIL PROTECTED] 
Sent: Wednesday, June 04, 2008 5:54 AM
Subject: [OCLC-NON-LATIN] OFFICIAL: Authorities LCCN indexing change


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 ([EMAIL PROTECTED]) 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: 

 

  a.. Type year portion (2 or 4 digits) and control number, with or without the 
hyphen. 
  b.. Leading zeros in the control number portion are optional. 
  c.. 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.  

 

  a.. Type year portion (2 or 4 digits) and control number, with no hyphen.  
  b.. n  85204041 (two digit year + 1 character prefix: add two spaces 
following the 'n' prefix) 
  c.. nr 99012578 (two digit year + 2 character prefix: add one space following 
the 'nr' prefix) 
  d.. no2007016671 (four digit year + 2 character prefix: add zero spaces 
following the 'no' prefix) 
  e.. n 2005035179 (four digit year + 1 character prefix: add one space 
following the 'n' prefix)


Becky Dean
OCLC
6565 Kilgour Place 
Dublin, OH 43017
[EMAIL PROTECTED]
1-800-848-5878, ext. 5144

Luanne Goodson, NACO Coordinator 
OCLC Quality Control Section 
Phone: (800) 848-5878 x5274 
  • Fw: [OCLC-NON-LATIN] OFFICIAL: Authorities LCCN indexing change Heidi Lerner