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

Description:
Bug Report Form, 16384-19857

Date: 1 October 2012
Module(s): Cataloging
Release(s) replicated in: 7.0.1 - 8.1.1
Last version without bug (if applicable): n/a

Expected results: When validating name/title headings in a bib record, if no matching name/title authority, but matching name authority exists, the heading would show as Partially Validated.

Actual results: Name/title headings only partially validate if there are other name/title authority records for the name in the name/title heading (not for the name/title being validated).

Name/title headings for names where there are no other name/title authority records but a matching name authority show as Nonexistent headings.

Workflow implications: Authority validation for name/title headings is inconsistent and confusing.

Replication steps:
In Cataloging, find a record with name/title headings, i.e.,:
Heading A: 700 1 2 ‡a Giuffre, Jimmy. ‡t Pharaoh.
Heading B: 700 1 2 ‡a Giuffre, Jimmy. ‡t Suspensions.
Heading C: 700 1 2 ‡a Schuller, Gunther. ‡t Transformation.

Heading A has a name/title authority:

100 1 _ ‡a Giuffre, Jimmy. ‡t Pharaoh.

Heading B has the same subfield a as Heading A, and a name authority record.
Heading C has a name authority record.

In Options > Preferences, make sure that Bypass Authority Validation is not checked.
Click Save to DB
Review the Authority Validation screen and note the following:
Heading A shows Heading Validated. This is correct.
Heading B shows Partial Heading Validation. This is correct.
Heading C shows Nonexistent Heading. This is not correct. This heading should also show Partial Heading Validation, as there is a valid name authority record that matches 700 a.

If you delete the name/title authority record associated with Heading A, you will note that all of the headings now show as Nonexistent Heading, even though all of the name portions of the name/title heading are associated with valid name authority records.

Workaround: None.

Resolution:

• Article last edited: 3/5/2015