Skip to main content
ExLibris
  • Subscribe by RSS
  • ExLibris Dev

    Errors in authority record loads run through p_manage_22

    • Article Type: General
    • Product: Aleph
    • Product Version: 20

    Description:
    We are loading weekly authority files to our ABC10 library. We run them through p_file_01 > p_file_02 > p_manage_22 > p_manage_31. In the p_manage_22 step we are seeing many character conversion errors. We are using the conversion MARC8_TO_UTF. Are these errors something we should be concerned about or just ignore them? Here is what we are seeing in the p_manage_22 log:

    1 START READING AT 13:28:28
    ...
    Error: character X"4b" is not defined in marc8_ext_rus_to_unicode.
    1002 READING LINE AT 13:28:29
    ...
    Error: character X"53" is not defined in marc8_ext_ara_to_unicode.
    Error: character X"8e" is not defined in marc8_lat_to_unicode.
    Error: character X"8e" is not defined in marc8_lat_to_unicode.
    Error: character X"8e" is not defined in marc8_lat_to_unicode.
    Error: character X"58" is not defined in marc8_ext_ara_to_unicode.
    Error: character X"8e" is not defined in marc8_lat_to_unicode.
    2003 READING LINE AT 13:28:29
    Error: character X"4d" is not defined in marc8_ext_rus_to_unicode.
    Error: character X"46" is not defined in marc8_ext_rus_to_unicode.
    Error: character X"4d" is not defined in marc8_ext_rus_to_unicode.
    Error: character X"46" is not defined in marc8_ext_rus_to_unicode.
    Load: /exlibris/aleph/u20_3/alephe/unicode/marc8_greek_to_unicode
    Error: character X"4d" is not defined in marc8_ext_rus_to_unicode.
    Error: character X"46" is not defined in marc8_ext_rus_to_unicode.
    Error: character X"4d" is not defined in marc8_ext_rus_to_unicode.
    Error: character X"46" is not defined in marc8_ext_rus_to_unicode.
    3004 READING LINE AT 13:28:29
    Error: character X"34" is not defined in marc8_ext_ara_to_unicode.
    Error: character X"58" is not defined in marc8_ext_ara_to_unicode.
    Error: character X"24" is not defined in marc8_ext_ara_to_unicode.
    4005 READING LINE AT 13:28:29
    Error: character X"46" is not defined in marc8_ext_rus_to_unicode.
    Error: character X"46" is not defined in marc8_ext_rus_to_unicode.

    And many more similar errors.

    Resolution:
    [As in KB 16384-29489, I have changed the LINE-INPUT-COUNT to make each input record number display.]

    I find that the records getting these errors:

    Error: character X"xx" is not defined in marc8_ext_ara_to_unicode.
    Error: character X"xx" is not defined in marc8_ext_rus_to_unicode.
    Error: character X"xx" is not defined in marc8_lat_to_unicode.

    contain the following input fields:

    000000090 667 L $$aMachine-derived non-Latin script reference project.
    000000090 667 L $$aNon-Latin script references not evaluated.


    This message is described at the following LC website:
    http://www.google.com/url?sa=t&source=web&cd=1&ved=0CB0QFjAA&url=http%3A%2F%2Fwww.loc.gov%2Fcatdir%2Fcpso%2Fnonlatinfaq.html&rct=j&q=%22Non-Latin%20script%20reference%20not%20evaluated%22&ei=_2yHTpPECIiltwf0xK0v&usg=AFQjCNF3pXMNZvGPBwP3auPieCxU6uuRLw&cad=rja

    v21 rep_change 69 has been created to address this:

    Description: Character Conversion (manage-22) - when converting from MARC8, if the MARC8 character set is Extended Arabic or Extended Cyrillic, characters from the "regular" Arabic or Cyrillic tables were missing.
    In addition, two characters were missing from the MARC8 latin table , and two characters from the MARC8 East Asian table.
    Solution: The missing characters have been added.

    Note: characters 5E, 76 and 77 (in Arabic), which appeared in the log as "not defined", were *not* added to marc8_ext_ara_to_unicode because Ex Libris staff were unable to find them in the MARC STANDARDS tables.


    • Article last edited: 10/8/2013
    //doorbell.io feedback widged