Hi @Khalilah Gambrell , long time not heard from this feature. I’ve added it to MM’s new Implementation Topics List and wanted to ask you if this is in scope for Trillium?

Not sure if this matters or not, but https://folio-org.atlassian.net/wiki/display/MM/2023-09-14+Metadata+Management+Meeting+notes could be added under the "Mentioned in" section above.

@Khalilah Gambrell and @Christine Schultz-Richert I was hoping that we could get this feature re-evaluated and hopefully prioritized for development. The one prior block for this issue was barcode data that Duke had, in that their barcodes legitimately contained trailing spaces. Even though that was a fringe case it would have greatly impacted them and created a showstopper. Since Duke will not be moving to FOLIO at this time, we were hoping this feature could be looked at again and implemented. 

We are having spine labeling and scanning issues in Inventory due to leading spaces. These spaces get introduced sometimes by our label maker when we're interacting with some irregular barcodes we use at MSU. (It basically wants to add spaces for barcodes that don't have the full amount of expected characters.) While we are working on a solution to the label maker issue (which of course turns out to be more nasty than expected), this was not a problem in Sierra because Sierra ignores/normalizes spaces altogether.

Also, outside of Inventory, we find the spaces are not an issue. So we assume other Folio modules have this capability. Hoping this can be replicated in Inventory as well.

@(OLD ACCOUNT) Erin Nettifee

Thank you for the follow up.

I'm fairly confident we could do the reprogramming, but if it didn't, either we would need that search to work or we would need some more meaningful error message than simply that the barcode wasn't found.

What kind of different error message would be wanted?

I'm asking because I'm unsure how we would differentiate once all of the spaces have been stripped from the data.