Full formatted contents note no longer displays

Kathy, could you send the MARC contents (from the HTML display, or maybe screenshots of either the MARC editor or flat editor), or links to the records in a system? It likely is just a simple index definition adjustment. Of course, a partial reingest will be needed, but we can do just the one definition, IIRC.

I've pasted the MARC record from the public view here - https://pastebin.com/CBJGzDc4

After upgrading to 3.1.8 we are seeing a similar if not the same issue. We are seeing only one 505 field display. All the subfields of the single 505 display, but not the additional 505 fields.

The fix is to update config.display_field_map for field 42 "toc" to multi = TRUE. Also field 41 "abstract" should be set to multi = TRUE. A restart of Evergreen was needed but no reingest.

These were both set to FALSE in upgrade script 1100.

To note for people who work on this, the upgrade script sets that value to FALSE because the default value in stock Evergreen per 950.data.seed-values.sql also says they are FALSE.

If it's intended for these fields to be set to TRUE to show the extra field information, then we need to change the default values as well for future Evergreen installations and then provide a new upgrade script.

Just confirming that we are seeing this in 3.1 here in SCLENDS. Example attached: as you can see, it can get pretty difficult to read when the subject headings are complex.

Here's the flat-text copy-paste that corresponds to the screenshot:

=650 \0$aRoads$xEconomic aspects$zUnited States$xHistory.
=650 \0$aRoads$xGovernment policy$zUnited States$xHistory.
=650 \0$aRoads$zUnited States$xMaintenance and repair$xHistory.
=650 \0$aRoads$zUnited States$xHistory.
=650 \0$aInterstate Highway System$xHistory.
=650 \0$aInfrastructure (Economics)$zUnited States$xHistory.
=651 \0$aUnited States$xEconomic conditions$y1945-$0(SC LENDS)495976
=650 \7$aTECHNOLOGY & ENGINEERING$xHistory.$2bisacsh
=650 \7$aPOLITICAL SCIENCE$xPublic Policy$xGeneral.$2bisacsh

Apologies-- my comment #5 was intended for a different bug.

It is Monday.