It seems odd to have two very specific account flags on patron accounts. We can accomplish the same task with patron restrictions (debarments). I would suggest we retire the patron account flags, and migrate any active flags to restrictions. Furthermore, we could create predefined restrictions, much like we have with predefined notes.
How does this idea affect the integrated systems connected via SIP2 or API? I think the lost flag prevents checkouts when using SIP2 but I'm not sure if restrictions do the same.
I don't currently have a SIP2 setup to test against, but I do believe restrictions do prevent checkouts. We use restrictions all the time. Blocking checkouts is the primary function of a restriction. I just tested both side by side on the staff interface, and they seem to function identically. If they differ via SIP2 or API, I am not aware, nor would I understand why.