Comment 4 for bug 1399741

One note: right now, the XUL and Angularjs clients behave the same way when a user enters a deleted barcode into item status as when they enter a completely invalid barcode: it just gives the message "was either mis-scanned or not cataloged".

If this proposal moves forward (or maybe even if not), this message should probably be more specific when the user enters a deleted barcode. Note that this would require changing the underlying pcrud call in the item service.