TPAC - hide subfield 6 and 8 from record title display

Bug #1085554 reported by Ben Shum
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Medium
Unassigned

Bug Description

Evergreen master

We discovered that because of the way TPAC grabs all the subfields from MARC tag 245 to generate the full title string in record display, it can also unintentionally pull in the contents of subfields 6 and 8, if present. Subfield 6 refers to linkage with a tag 880 for vernacular script and subfield 8 refers to sequence related holdings. In any case, both of these subfields should probably be suppressed from the full record display.

Additionally, it might be noted that in search results we use the variable title while grabbing only subfields a,b,n, and p. Whereas we grab any subfield in title_extended which is used in record details.

An example situation we discovered with subfield 6 was this line from one of our bib records:

=245 00$6880-01$aSan qiang pai an jing qi$h[videorecording] /$cBeijing xin hua mian ying ye you xian gong si, Huan qiu dian ying (2009) huo ban you xian gong si chu ban ; jian zhi/chu pin ren Zhang Weiping, Jiang Zhiqiang, Gu Hao ; bian ju Xu Zhengchao, Shi Jianquan ; dao yan Zhang Yimo = A woman, a gun and a noodle shop / Beijing New Picture Film Co., Ltd, Film Partner (2009) International, Inc. present ; produced by Zhang Weiping, Bill Kong, Gu Hao ; screenplay by Xu Zhengchao, Shi Jianquan ; directed by Zhang Yimou.

Where the value "880-01" of subfield 6 showed up at the beginning of the title string in record details.

So, I'm going to include a working branch to hide subfields 6 and 8 to avoid having to deal with strange values showing up in the record details title for now.

I'm thinking we could also choose to make the title string match between results/record and target a very specific set of subfields, but there may be other subfields we're intentionally not showing in results vs. in record?

Revision history for this message
Ben Shum (bshum) wrote :
tags: added: tpac
Ben Shum (bshum)
tags: added: pullrequest
Changed in evergreen:
importance: Undecided → Medium
milestone: none → 2.4.0-alpha
status: New → Triaged
Revision history for this message
Ben Shum (bshum) wrote :

This bug will be fixed with the changes proposed in bug 1096511.

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

Ben,

You might want to keep this open for 2.3 and earlier. The fix in 1096511 is a new feature that I assume won't be applied until 2.4. In the meantime, I think libraries would appreciate it if the display were cleaned up in 2.3 and earlier.

Kathy

Changed in evergreen:
status: Triaged → Confirmed
Revision history for this message
Dan Scott (denials) wrote :

Signed off on Ben's commit and added one more commit to handle the same problem in series (along with a display problem) at user/dbs/tpac_filter_subfields in working. ONLY TO APPLY TO rel_2_3, else it will totally break bug 1096511. Or else somebody's going to be doing some mergery...

Revision history for this message
Dan Scott (denials) wrote :

Oh, I forgot to mention - the two versions of title in search results reflect the "Show More Details" / "Show Fewer Details" split in the search results view. I guess somebody didn't like the $c "statement of responsibility" showing up in the "fewer details" option, possibly because it ended up having longer titles than the old fixed-width layout supported, which explains why a,b,n,p were chosen. Perhaps.

Ben Shum (bshum)
Changed in evergreen:
milestone: 2.4.0-alpha → 2.3.3
Changed in evergreen:
milestone: 2.3.3 → 2.4.0-alpha
Revision history for this message
Ben Shum (bshum) wrote :

Reassigning target back to 2.3 only since 2.4 will have a different solution.

no longer affects: evergreen/2.3
Changed in evergreen:
milestone: 2.4.0-alpha → 2.3.4
Revision history for this message
Ben Shum (bshum) wrote :

Tested Dan's series fix and it works for me.

Pushed to rel_2_3 only.

Changed in evergreen:
status: Confirmed → Fix Committed
Ben Shum (bshum)
Changed in evergreen:
status: Fix Committed → Fix Released
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.