Comment 13 for bug 1235497

Ben noted in IRC that these changes caused a lot of bloat in the search tables (metabib.title_field_entry, specifically). This surprised me, because I wouldn't expect a config with search_field = false to end up in that table.

It looks like this issue traces back to a change made in commit 6205d9b43d60. I am thinking we need to simply remove the 'OR ind_data.browse_field' part of that change. After all, if anyone wants the behavior described, I would expect search_field to be true as well (in other words, it isn't either/or).

Will push an update to the branch to address this, but in the meantime, more feedback is welcome!