Comment 4 for bug 1777698

We are encountering this issue in multiple SCLENDS systems (Evergreen 3.1.5).

The primary workaround our catalogers are using is to delete the "duplicate" barcode and re-scan the barcode: it seems to work on the second try (and not flag as a duplicate, as it did on the first go-round). This is using the same barcode both times: we don't have to switch to a new barcode to clear the error.

It does not happen consistently, and we cannot identify a pattern. It's a significant workflow issue for the catalogers.

This issue has been reported consistently since we went live on 3.1 on September 26th.