Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Voyager

     

    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Voyager
    3. Knowledge Articles
    4. Importing record from OCLC into Voyager receive "Record 1 in import file failed the Unicode conversion. Unable to display the record."

    Importing record from OCLC into Voyager receive "Record 1 in import file failed the Unicode conversion. Unable to display the record."

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    1. Question
    2. Answer
    • Product: Voyager
    • Product Version: 8
    • Relevant for Installation Type: Multi-Tenant Direct, Dedicated-Direct, Local, TotalCare

     

    Question

    Received this error when attempting to import OCLC record into Voyager Cataloging Client:

    Record #1 in import file failed the Unicode conversion. Unable to display the record.

    Answer

    The message that you're seeing indicates that Voyager is not able to successfully convert the character encoding using the Expected Character Set as configured in your cataloging client preferences.

    That could mean a couple of things:

    1. The records are not actually in the Expected Character set ; or
    2. There is a character or characters in the records that Voyager cannot interpret.


    When we see this message, it's usually #1, and there's a couple of ways to resolve it:

    1. Try changing the Expected Character Set of Imported Records in Cataloging > Options > Preferences > Mapping and see if the client is able to convert the record then.
      • For example, try: "MARC21 MARC-8 (non-Unicode)"
    2. If your OCLC client is configured so that the record's character set is converted to something other than the OCLC character set when it's saved to a file, change this so that it saves the records with the original character set.

     


    • Article last edited: 17-Sep-2019
    View article in the Exlibris Knowledge Center
    1. Back to top
      • IMPORT:Bi-directional merge not working of 040a at top of hierarchy
      • In AUTH_HEADING table, what is HEADING_ID_POINTER and the HEADING_ID_POINTEE?
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Voyager
    2. Tags
      This page has no tags.
    1. © Copyright 2025 Ex Libris Knowledge Center
    2. Powered by CXone Expert ®
    • Term of Use
    • Privacy Policy
    • Contact Us
    2025 Ex Libris. All rights reserved