Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    Unlinked (old) and new headings have the same filing_text

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

    Description:
    The OCLC loader merged incoming OCLC record with existing ALEPH bib.
    As a result: the unlinked (old) heading remained in the database and a new heading was created.

    Unlinked (old) and new headings have the same filing_text.
    Shouldn't the system maintain a single z01 record instead of creating a new one?

    Old heading =>
    acc_code ..............TIT
    alpha .................L
    filing_text ...........ROSE HAS NO TEETH BRUCE NAUMAN IN THE 00019
    filing_sequence .......00002
    z01_acc_sequence ........002065967
    ...
    z01_normalized_text .....$$-rose has no teeth bruce nauman in the 196
    z01_display_text ........$$aROSE HAS NO TEETH : BRUCE NAUMAN IN THE 1


    New heading =>
    z01_rec_key \
    acc_code ..............TIT
    alpha .................L
    filing_text ...........ROSE HAS NO TEETH BRUCE NAUMAN IN THE 00019
    filing_sequence .......00001
    z01_acc_sequence ........002417859
    .....
    z01_normalized_text .....$$-rose has no teeth$$-bruce nauman in the 1
    z01_display_text ........$$aA rose has no teeth $$bBruce Nauman in th

    Resolution:
    It is not enough for the z01_filing_text to be the same. The z01_display_text (and z01_normalized_text) must also be the same.

    Comparing the first z01:

    z01_normalized_text .....$$-rose has no teeth bruce nauman in the 196
    z01_display_text ........$$aROSE HAS NO TEETH : BRUCE NAUMAN IN THE 1

    to the second:

    z01_normalized_text .....$$-rose has no teeth$$-bruce nauman in the 1
    z01_display_text ........$$aA rose has no teeth $$bBruce Nauman in th

    We see that they are *not* the same. The second has a subfield b, while the first lacks it.


    • Article last edited: 10/8/2013