Comment 10 for bug 1562061

I can't speak to the original intentions of the development of Long Overdue, but in PINES we basically use it as an automated form of Lost. If someone tells us that they lost an item or if they claim they've returned it but we can't find it after a set amount of time, we will manually mark an item Lost. If they simply don't return it, it automatically gets marked Long Overdue at 180 days.

In both cases, we bill the full item price plus processing fee and we generate an automated notice via action triggers. (And in most cases, the patron is blocked because they'll exceed the fine threshold.)

We direct our libraries not to change the status from Long Overdue to Lost, but if we could do so without triggering a double-billing or triggering another action trigger notification or triggering something else I haven't considered, then I could see it being useful.