Comment 8 for bug 1307629

Tim, the next thing we need to look at is the contents of your config.metabib_field table, since now that the authority-side headings have been addressed we'll have to investigate the bib-side headings. It's likely that we'll need to look at the normalizations being applied to each field, as well, but those are stored across several tables and a little trickier to pull out, so let's start with just the definitions. If there are non-stock definitions for link-able bib fields, they're probably lacking some authority-important parts. Your mention of subdivisions, in particular, makes me lean in this direction.

Stepping back, there are two sources of browse headings: bibs and authorities. They each have separate extraction and normalization configuration tables, and they both need to be set up such that the output of each lines up with the other. That means making sure that the authority, browse and browse_sort xpath fields is set properly, that the joiners match, and that the set of bib-side normalizers will cause the same output to be generated from the bib side as will be generated from the simpler authority-size heading generation routine.

Obviously something in your configuration is misaligned, but we'll find the culprit.