Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Regression: No longer able to checkout items with whitespace in barcode

Description

Many FOLIO institutions have item records that have whitespace in them. This is often a legacy issue with barcode data that is not necessarily able to be easily fixed prior to a FOLIO adoption; that means that FOLIO circulation needs to be able to accept barcodes with whitespace in them and allow circulation to occur.

This problem was identified as part of Missouri State's adoption, and addressed in the Checkout app as part of https://folio-org.atlassian.net/browse/CIRC-284#icft=CIRC-284 and https://folio-org.atlassian.net/browse/UICHKOUT-506#icft=UICHKOUT-506

This has regressed - you can no longer checkout items with a space in the barcode. It fails with an error message that tells you it cannot find the barcode. Screenshot from Snapshot:

In addition, it doesn't appear that this behavior was ever addressed for SIP2 and NCIP scenarios (though perhaps it was considered implied by the resolution of https://folio-org.atlassian.net/browse/CIRC-284#icft=CIRC-284).

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

1
  • 06 Oct 2021, 01:14 PM

Checklist

hide

TestRail: Results

Activity

Show:

(OLD ACCOUNT) Erin Nettifee November 17, 2022 at 4:24 PM

I revisited this issue and tested in a Lotus environment today and was able to successfully do a check in and check out. Either something has changed since this was submitted related to a dependency I was unaware of, and that fixed the problem, or I was missing something when I reported the problem back in Fall 2021. In any case, I am going to resolve this as "Cannot reproduce."

Stephanie Buck July 6, 2022 at 3:06 PM

, I'm no longer sure what to do with this bug. It's very old, and it's blocked until the feature questions are resolved. Should it just hang out until then?

Stephanie Buck April 15, 2022 at 8:09 PM

Hi . Just checking in on this. Has any decision been made?

(OLD ACCOUNT) Erin Nettifee March 1, 2022 at 7:36 PM

Hi - I don't have an update yet. There is a ticket over in Inventory - https://folio-org.atlassian.net/browse/UXPROD-3473 - that is discussing how to handle this. In reading the comments, it looks like there has been no decision about it. What I don't want to have happen is for you all to do work to resolve this and then for the Inventory team to do work that causes a regression again.

What I'm going to do for now is block the jira on https://folio-org.atlassian.net/browse/UXPROD-3473#icft=UXPROD-3473 and comment over there to ask for/whether a decision has been made or what the next steps are on the inventory end. I will comment on the ticket and tag you.

Sherzod Nurjonov March 1, 2022 at 11:16 AM

Hi
Any update reproducing steps, expected/actual results?

thanks,

Cannot Reproduce

Details

Assignee

Reporter

Labels

Priority

Development Team

Vega

Parent

Release

Not Scheduled

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created October 6, 2021 at 1:16 PM
Updated November 17, 2022 at 4:24 PM
Resolved November 17, 2022 at 4:24 PM
TestRail: Cases
TestRail: Runs

Flag notifications