Comment 5 for bug 1424815

As I alluded to above, in the current implementation, an Evergreen site can determine on a field-by-field basis how many characters should display, but I would like to move that setting into one setting in config.tt2 that governs the maximum character count for all notes. Generally, this setting will be global for the Evergreen instance, but sites that provide different subdomains for individual libraries can change this setting on a library-by-library basis.

However, I'm still on the fence about this approach and have probably shifted to the side of exploring alternatives since posting this branch. When testing this code on real bib records, I found that using an anchor leads to a lot of jumpiness when clicking the Read More link. I plan to look at it a little more closely when tuits free up again.