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

    Auth validation doesn't acknowledge created auths for 110/240

    • Article Type: General
    • Product: Voyager
    • Product Version: 7.1.0

    Description:
    Bug Report Form for Issue 16384-8369
    Module(s): Cataloging
    Server platform(s) affected: Solaris/all
    PC OS (if applicable): n/a
    Browser & version (if applicable): n/a

    Release(s) replicated in: 7.0.4-7.1.1
    Last version without bug (if applicable): 7.0.1

    Expected results:
    When an authority record, is created for a 100/240 field, the Authority Validation screen should acknowledge the validated heading the next time that screen is brought up.

    Each time “create Auth” is selected for a 100/240 field, the authority is created, but the next time the Authority Validated screen pops up it will list the 100/240 field as a “Nonexistent Heading” under the Validation column.

    Workflow implications: Customers may believe that the authority records are not saving to the database.

    Replication steps:
    Open Cataloging in 7.0.4-7.1.1.

    Import a record that has a 100/240 field (attached to the Issue is a file of records that can be used).
    Make sure that in Options>Preferences>Validation, “Bypass Authority Control Validation” is unchecked.
    Click the “Save to db” button for the imported record.
    The Authority Validation window will pop up. Scroll down to the 100/240 field information. It will read “Nonexistent Heading.”
    Create Auth for that field. Save the authority record to the database. Note the Authority ID number.
    Save the bib to the database again.
    The Authority Validation window will pop up. Scroll down to the 100/240 field information. It will still read “Nonexistent Heading.”
    Go to Record>Retrieve by record ID> Authority. Type in the Authority ID number from the earlier saved authority.
    That authority record will display.

    Resolution:


    • Article last edited: 3/19/2015
    //doorbell.io feedback widged