Comment 9 for bug 1562061

For background (and, I don't think this should stop the fix here going in), Long Overdue was originally designed as a sort of "soft lost" on the way to declaring complete Lost-ness. This comes from a (IIRC) PINES workflow where an item would go Long Overdue after 90 days, and then Lost after 180. There would be different fees assessed at each step. Obviously the feature(s) have grown in use cases since then, but I wanted to give the history. Software is a living document... :)