Unauthorized headings are displaying in all lower case and is missing important punctuation

Bug #1307581 reported by Kathy Lussier
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Evergreen
Invalid
Medium
Unassigned

Bug Description

Evergreen version: 2.5.3

Unauthorized authority headings that display in the browse search appear to be normalized so that they are displaying as all lowercase with key punctuation, like hyphens, missing.

For example, if you look at the authority record for Nikki Poppen at http://www.screencast.com/t/JWWfzcygfuN, you will see that the first 400 entry is for Poppen-Eagen, Nikki 1967-.

However, in the browse list, this name displays as:

poppen eagen, nikki 1967

http://www.screencast.com/t/ccq10O9D

The names should be properly capitalized in the browse list, and there should be a hyphen between Poppen and Eagen and another hyphen after 1967.

Revision history for this message
Kathy Lussier (klussier) wrote :
Revision history for this message
Mike Rylander (mrylander) wrote :

This symptom is indicative of the need for an authority reingest. When performing that reingest, though, it's important to turn off the 'ingest.reingest.force_on_same_marc' internal flag.

Revision history for this message
Mike Rylander (mrylander) wrote :

ARG! Please ignore my previous comment.

You need to turn that flag ('ingest.reingest.force_on_same_marc') ON, not off. ALSO(!) you need to turn ON the 'ingest.disable_authority_auto_update' and 'ingest.disable_authority_linking' flags, to avoid updating bibs needlessly.

Sorry for the noise.

Revision history for this message
Srey Seng (sreyseng) wrote :

I was unable to replicate this issue on stock 2.5.3.

I did the following:
(1) imported the auth for Poppen, Nikki, as well as the auth for Scott, Bronwyn
(2) import books by both of these authors
(3) ran auth-auth linking
(4) ran bib-auth linking

Records obtained from LC.
Screencast of results: http://www.screencast.com/t/sYsTmXRe3d

Revision history for this message
Kathy Lussier (klussier) wrote :

I'm setting this bug to invalid since we were able to fix these issues after Truncating the metabib.browse_entry table
and Reingesting authorities.

Changed in evergreen:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.