Comment 1 for bug 1235497

Ok, I am hijacking my own bug, because the problem goes a little deeper than this. Since the title browse is currently being populated from <titleNonfiling>, and the browse_sort_xpath can only narrow the main metabib_field xpath used for display, the current title browse sorting is including the non-filing characters. I am pretty sure that isn't what we want, since that kinda defeats the purpose of non-filing characters.

What it comes down to is that we cannot use a single metabib_field entry for both search and browse of titles, since we are purposely adding the non-filing characters in the <titleNonfiling> node in a non-separable way, yet we need to separate them off for the browse sorting.

In short, I think we need to properly re-add a 'Title Proper (Browse)' configuration to the default metabib_field entries, and have it configured for browse alone, and turn off the browse settings on 'Title Proper'. Doing so removes the need to change <titleNonfiling> as outlined above, since we can go back to the stock MODS title field, but I think we might want to take the above steps anyway to help out anyone using <titleNonfiling> for display (including our future selves).

Thoughts?