Comment 1 for bug 1434211

Bug 1010671 provides some historical context.

Gut reaction: I'd argue that in some circumstances, it's OK for SIP2 clients to treat the barred status differently from the deleted condition. In particular, if a patron is using a self-checkout device in the library, having it be able to tell the patron that their library privileges have been suspended would be useful.

I also think it's reasonable to treat SIP2 requests for eresource authentication differently.

So to continue my gut reaction: this smells like a reason to add a new SIP config option to specify whether or not SIP2 requests treat barred patrons as if they exist or not, allowing for a library to treat self-check devices one way and resource authentication another.