Page tree
Skip to end of metadata
Go to start of metadata

DLC and other exempt class records

  • No manual verification of name headings is required for 040 DLC|cDLC, 042 pcc, or 042 lccopycat records. Our authority processing vendor will verify headings in new bib records on a monthly basis. The cataloger should eyeball to make sure that the headings being traced on the record do belong to the item in hand and do not contain typographical errors. Pay particular attention to bibliographic record headings that are followed by the system verification message |?UNAUTHORIZED. Where 050 contains a series class number, the cataloger should check the series in 440/830 against the Unicorn authority file to check for local classification policy.

Contributed records

Personal and corporate headings

  • Generally, no manual verification is needed. Accept the form used on the contributed record. Follow RDA and departmental policy to evaluate whether a particular name should be traced. Follow steps listed under Original Cataloging below when adding headings not already on the record being worked on. Refer added headings to authority review when there appear to be variant forms of the name on the piece or name conflicts in reference sources consulted.

Conference headings

  • Search the name portion of the heading (the portion before the number, date and place of the conference) against the NCSU catalog using either WorkFlows or the OPAC.
  • If exact match on form of name is found, accept the name as is. Check the call number on earlier records to see if your title is part of a classed together meeting.
  • If the form on the record being worked on is slightly different from what appears in other catalog entries but the conference is believed to be the same, check the LC name authority file using LC Web authorities, the Browse authority wizard in Workflows, or OCLC for an authority record for the conference. If the form of name used on your title matches a 4xx of the NAF record, adjust the form on the bib record to match the NAF 1xx. If not, or if neither form of heading is represented in the NAF at all, refer your conference name to authority review to have an authority record with the cross-reference added. Check the call number on earlier records to see if your title is part of a classed together meeting.
  • If no match (exact or slightly different form of name) is found in the catalog, but the form used on the record is the same as what appears on the chief source of information, accept the name as is. If other forms of the conference name also appear on the piece, or if cross-references seem warranted, look up the name in the NAF, referring the work to authority review if no NAF heading matches.

Uniform titles

  • In general, no verification is needed for uniform titles entered under personal names (e.g., 100 with 240 or 700|a|t) or for uniform titles on periodical records where the 130 is simply the 245 with a qualifier such as date, publisher, language, or format ("Online").
  • For uniform titles traced as 130/630/730, search the Library of Congress authority file, WorkFlows Search authority wizard, or OCLC NAF for exact match (i.e., all components of the heading). If no authoritative form is found in the LC authority file, send the piece for authority review.


Make sure that the transcribed form (490) matches the information presented on the item itself. With the transcribed form:

  • Using the WorkFlows Search authority wizard, first search the local authority file (Index: LCNAME) for a match on authorized form (A) or a cross-ref (x). The Unicorn NAF is our repository of series policy decisions in terms of whether to analyze, class together, trace, etc. Local variations on LC practice will be flagged by the presence of |5NcRS in a particular field.
  • If exact match between piece and NAF 1xx found, this is your 490 and your 830.
  • If exact match between piece and NAF 4xx found, this is your 490 and NAF 1xx belongs in bib 830 or, far less commonly, an 800 or 810.
  • If no record is found in our local NAF, next search the LC name authority file using the LC authorities Web form or the OCLC authority file. If you have been trained to do so, create a new series authority record for the series in Unicorn. Place material with completed series work on the series question shelf for verification of policy decisions on tracing, classing together, etc.
  • If no matching authority record is available from any source, search bibliographic records in WorkFlows using the Browse series wizard or the OPAC using Series as search type:
  • If exact match found, accept form from copy and tag as 490 and 830
  • If no exact match found but believe the item in hand belongs to the same series:
  • Tag series on copy as 490 with first indicator value 1
  • Copy the form found in field 440 or 830 from the pre-existing catalog record to field 830 on new record.
  • Note: for steps a) and b) check also if the series is classed together. Hint: if the numbering designation in 4xx|v (e.g., v. 23) is used in the 050/090, it is likely to be a classed together series.
  • If no bib records with the series are found in any of the above sources, refer piece to series review shelf.

Original records

SPA catalogers:

Establish 1xx, 240, 4xx, 6xx, 7xx and 8xx using forms of names presented on the piece itself. Search for authoritative forms of names in one of the sources listed under Contributed records above.

  • If match found, use heading as is. Mark heading on printout with NAF.
  • If match not found, leave the form as it appears in the item. Mark heading on printout with °NAF
  • Route the piece with printout indicating authority work done to Authority Shelf if some headings marked as °NAF and x-refs are required; else place on Completion Shelf.

Completion, series review, and authority shelf catalogers:

  • Evaluate headings as part of the review process, following AACR2 guidelines
  • If no authority record is deemed necessary, OK headings and return item to the SPA cataloger
  • If authority record is needed, do needed reference work, create heading and cross-refs in WorkFlows and return item to the SPA cataloger.
  • Resolve any conflicts discovered in the catalog during the research leading up to authority record creation, delegating work if appropriate.

Revised 24 August 2009