Comment 19 for bug 1798187

I'm in favor of documenting standards for barcodes in Evergreen.

I'm also in favor of stripping all the characters Josh mentions in comment #14 as in the xul method.

However, the xul client never handled files of barcodes with spaces between the barcode characters well. When uploading, the xul client would see:

1234 567 2344

as three distinct barcodes:

1234
567
2344

I am also seeing problems uploading a file of barcodes with spaces between characters in the current web client. It fails silently.

So in addition to handling trailing and leading characters in the uploaded file, the web client should handle spaces between characters in barcodes better than it does now.

This may not be practical, but I'll throw it out here. Ideally I would like to see all whitespace characters stripped from barcodes before saving to the database and all whitespace characters stripped from barcodes entered into the client. If others agree, I'll gladly open a separate bug.