Viewing the Invalid Audit Log

Bib records should not be attached to invalid authority records. To verify that bib records are attached to valid authority records, Horizon checks these records:

Existing bib records
“New” records

If a change needs to be made to maintain the integrity of the database, Horizon makes the change and records it in the invalid audit log. You can open this log to verify that the changes Horizon makes are correct for your library.

Horizon logs errors in the invalid audit log during these circumstances:

When Horizon makes changes to existing records or to incoming bib or authority records, such as attaching a bib record from an invalid authority to a valid authority, or changing a See reference to a See Also reference.
When your library staff creates a uniform title and certain conditions do not exist. (For more information, see “Creating a Combined Authority Record” in the “Working with Uniform Titles” section of the “Authority Records” chapter of the Cataloging Guide.)

These are the types of entries that could be logged in the invalid audit log table:

Entry_type code

Short Description

Long Description

0

Simple

Simple Bib change. Invalid Auth found with only one valid form.

1

Complex

Complex Bib change. Invalid Auth found with multiple valid forms.

2

AuthChange

Auth Change. Sysgen valid Auth now invalid. Bibs linked are moved to valid form.

3

BibChange

Bib change as a result of Auth change from valid to invalid.

4

SeetoSeeAlso

Auth See reference changed to See Also reference.

5

SeeAlsotoSee

Auth See Also reference changed to See reference.

6

CompDupSubf

Compound and co-tags have duplicate subfields.

7

CompMissReqSubf

Compound or co-tag is missing required subfields.

8

ValidInvalidInversion

Authority Valid/Invalid relationship inverted by Text Match.

9

ValidInvalidDup

Duplicate valid and invalid heading created by Text Match.

10

Link On Match

Bib heading was left unlinked due to a “Link On Match” auth link type setting.

11

Link Never

Bib heading was left unlinked due to a “Link Never” auth link type setting.

 

When you open the bib_auth_invalid_audit view, Horizon loads all of the rows. To limit the rows that display, you can select a column, such as the date, to limit by. To limit further, you can press SHIFT+F2 and enter a “where” clause.

For example, to select all type “2” entries that changed while John was logged on that have not yet been resolved, press SHIFT+F2 and enter this command:

horizon_user_id = “john” and entry_type = 2 and resolved = 0

To view the invalid audit log

1 Open the bib_auth_invalid_audit view in the Table Editor.
2 Choose the log entry you want to view.
3 Click Edit.

Horizon displays the Edit Invalid Bib Auth Audit Log.

4 Do one of these options:
If you are working with authority headings, verify that the text in the New Text field is the correct valid authority heading. If it is not, you can manually change the text in the MARC Editor. (This field may be blank if the entry type does not require a new heading.)
If you are working with uniform title tags, verify what subfields are missing or duplicated (displayed in the New Text field) and open the bib record in the MARC Editor to resolve the problem.

Note: You can copy and paste the text from these fields into MARC records. You can also print the list screen or a subset of the list screen.

 


© 1998-2017 Sirsi Corporation