trailing spaces not trimmed from barcode pastes in item status

Bug #1334689 reported by Jim Keenan on 2014-06-26
This bug affects 4 people
Affects Status Importance Assigned to Milestone

Bug Description

Evergreen 2.5.5

When copying and pasting a barcode from the public OPAC into the barcode field of the staff client Item Status screen, staff may inadvertently pick up an extra, invisible character at the end of the barcode. Example (in hex)

3 8 1 2 5 0 0 0 5 3 6 3 8 4
33 38 31 32 35 30 30 30 35 33 36 33 38 34 09

This copy has picked up the horizontal tab character (09) from the OPAC.

When pasted into the Item Status screen, this will result in the error "was either mis-scanned or is not cataloged" because the trailing 09 character was not trimmed.

Terran McCanna (tmccanna) wrote :

This is an issue with a lot of fields on a lot of screens. I'm having trouble thinking of any field where we would actually want a leading or trailing space to be stored in a field - should there be a standard of trimming all leading/trailing spaces everywhere? Are there reasons we would not want that?

Changed in evergreen:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers