UCSD NACO Contribution Policy

Original written by: Paul J. Weiss; approved by Section Heads, March 25, 2002
Revised by: Paul, November 28, 2006
Reviewed by the NACO Contributors Group, November 28, 2006
Approved by Cataloging Committee, December 12, 2006

 

General

Who

  • staff who have been trained in NACO and who perform original or OCLC Enhance cataloging

Types of headings eligible

  • personal names, except as authors only of dissertations
  • corporate names (including conference names)
  • those geographic names specified in rule and LCRI 23.1
  • uniform titles for which LC creates authority records (see DCM Z1, Introduction), except series

Types of contributions

  • new records
  • modifications to existing records
  • requests to delete records

Which contributions to make

  • generally all eligible contributions and required related contributions per NACO policy
    (currently described here = NACO - The name authority program component of the PCC on the NACO website), including new records with no cross references, except those which you deem will take an inordinate amount of time to research for which you do not have important expertise (such as for a non-Roman script)

 

Searching

Domain

authority records

  • UCSD
  • LC/NAF

bibliographic records

  • all cataloged records in Pactech (including slides records)
  • LC and PCC records
  • for specific conferences: OCLC, to see if it should be set up as a general conference
  • cataloger judgement: OCLC (non-LC, -PCC records)

other, as specified in NACO documentation, such as:

  • certain reference sources for specified nonverbal creators (rule and LCRI 22.1B)
  • GNIS for US place names (LCRI 23.2)
  • appropriate bibliographic sources to determine usage in a corporate body's language when your resource is not in the body's language (rule and LCRI 24.3A)
  • the Library and Archives Canada catalog for certain Canadian headings (DCM Z1 Appendix 2)
  • cataloger judgement: the Web, email, phone calls, etc.

What to search for

  • the entity that you are performing authority control on
  • the specific character strings you are using, and expected variants