Email list hosting service & mailing list manager

$i is required in linking entry fields? Kay Teel (22 May 2013 19:45 UTC)
Re: $i is required in linking entry fields? Mike Saunders (22 May 2013 20:00 UTC)
Re: $i is required in linking entry fields? Kevin M Randall (22 May 2013 20:39 UTC)
Re: $i is required in linking entry fields? Mike Saunders (23 May 2013 12:58 UTC)
Re: $i is required in linking entry fields? Tarango, Adolfo (23 May 2013 14:54 UTC)

$i is required in linking entry fields? Kay Teel 22 May 2013 19:45 UTC

In the newly released PCC guidelines for relationship designators
http://www.loc.gov/aba/pcc/rda/PCC%20RDA%20guidelines/Relat-Desig-Guidelines.docx),
Guideline 14 says: "If a cataloger wishes to indicate a known
relationship to a known resource, and the $i relationship information
subfield is defined for the  MARC 7XX field being used, provide a
relationship designator. Do so even if the field coding otherwise
already expresses a relationship."

This sounds like it is now required of PCC (CONSER) records to include
$i in 76x-78x linking fields, for example:
780 00 $i Continues (work): $t Regional trends (London, England)
785 00 $i Continued by (work): $t Region and country profiles

Are mergers coded as:
785 00 $i Merged with: $t American electrician
785 00 $i To form: $t Electrical world (New York, N.Y. : 1906) ?

We wanted to confirm that this is now required and to be implemented
immediately. Although my library doesn't participate in CONSER, we
generally follow CONSER cataloging standards.

Kay Teel
Metadata Librarian for Serials and Arts Resources
Stanford University Libraries
Stanford, California
kteel@stanford.edu

***********************************************
* You are subscribed to the SERIALST listserv (Serials in Libraries discussion forum)
* For additional information, see  the SERIALST Scope, Purpose and Usage Guidelines <http://www.uvm.edu/~bmaclenn/serialst.html>
***********************************************