UCSD Libraries Policy for Using Relator Terms and Codes
Written by Brad Westbrook and Ryan Finnerty
Approved by Cataloging Committee, May 13, 2008

Special File Headings for Names:

Relator terms and codes are devices used to show a particular relationship that a name has to a work.  Through the use of these devices, a repository, often a special collections repository, can construct “special files” of printers, booksellers, former owners, etc.  These special file headings can be of immense value to researchers, as well as collection developers.
 
Relator terms and codes are typically either copy specific or not.  For example, the relator term “former owner” signifies the relationship between a specific name and a single copy of a work, whereas the relator term “translator” indicates the relationship between a specific name and all copies of a particular instance of the work.
 
The relator term is encoded in $e in a 100/600/700 or 110/610/710 name heading.  In contrast, the relator code is encoded in a $4 of the same fields.  The UC San Diego Libraries supports the thoughtful and measured application of both encodings in its catalog.

UCSD Libraries Policy for Using Relator Terms and Codes:

The UCSD Libraries supports the use of relator terms and codes in its catalogs according to the following guidelines:

• Catalogers should only use relator codes from the MARC Code Lists for Relators, Sources, Description Conventions
  
  
• Catalogers should only use relator terms from Relator Terms for Use in Rare Book and Special Collections Cataloging published by the ACRL RBMS and the Art and Architecture Thesaurus published by the Getty Research Institute. Natural language terms from MARC Code Lists for Relators, Sources, Description Conventions may also be used according to LCRI 21.0D.
  
  
• If catalogers need to use relator terms from another list, then they should consult with Cataloging Committee.
  
  
• Old pre-AACR2 terms such as “jt. author” still exist in WorldCat records and sometimes find their way into Roger. We will do periodic clean-up to remove such terms.
  
  
• Catalogers may use either the code or the term, but they are strongly encouraged to use one or the other for the same relator term, that is encode “former owner” always as “former owner”  or as “fmo” but not sometimes as “former owner” and sometimes as “fmo”.
  
  
• Catalogers should determine if the relator term or code is copy specific or not and encode it in the bibliographic record according to the instructions immediately below.

Encoding relator terms and codes that are not copy specific:

For relator terms/codes that are not copy specific, encode them in subfield e or 4 of the appropriate 100/600/700 or 110/610/710 name heading. These headings should be retained in the OCLC master record, where they can be available to other cataloging agencies.

Examples: 
100     1_        Galilei, Galileo, $d 1564-1642, $e defendant
700     1_        Spahr, Juliana, $e blurb writer
700     1_        Brainard, Joe, $e ill. 
700     1_        Cage, John. $4 cnd
700     1_        Crumb, George. $4 prf
700     1_        Drucker, Johanna. $4 bkd710

710     2_        Peter Pauper Press, $e publisher

Encoding relator terms and codes that are copy specific:

If the relator term/code is copy specific, use a local name entry, 790 for personal names and 791 for corporate names. Since these are coded as local headings, they will not be retained in the OCLC master record.  Indeed, it is assumed that other cataloging agencies will have no use for these headings since they apply only to UCSD copies of works.

Examples:
790     1_        Brooke, Jocelyn, $e former owner
790     1_        Oppen, George, $e annotator