Overview of using the call_no_type field in the MFHD_MASTER table in Voyager Prepackaged Access Reports

Question

Overview of using the call_no_type field in the MFHD_MASTER table in Voyager Prepackaged Access Reports.

Answer

• Call_no_type is usually the same as the 852 first indicator, but there are the following exceptions:
  • If there’s no 852$h, call_no_type will be blank.
  • If the indicator shows that the call number should be LC, Dewey, SuDoc, or NLM, but the call number in 852$h cannot be parsed by Voyager according to its rules for the class scheme, then call_no_type will be set to 8.
  • If the 852 first indicator is 7 and subfield $2 is not a classification scheme that Voyager recognizes, then call_no_type will be set to 8.
  • If the 852 first indicator is 7 and subfield $2 is empty, then call_no_type will be set to blank.  
  • The value of display_call_no is NULL when there is no 852$h.
  • The value of normalized_call_no is NULL when 1) there is no 852$h, or 2) there is an 852$h but it’s empty, or 3) 852 Ind1=blank, or 4) 852$h cannot be parsed by Voyager according to the rules for the classification indicated by Ind1.
  • Generally, call numbers are sorted by normalized_call_no. However, note that in staff client searches with location limiting, the sort is by display_call_no.

• Article last edited: 19-Oct-2020