Requests (UXPROD-790)

[UXPROD-3384] Add Optional "Fuzzy" Barcode Lookup and Item Disambiguation to Requests App Created: 25/Oct/21  Updated: 29/Sep/22  Resolved: 29/Sep/22

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: TBD
Parent: Requests

Type: New Feature Priority: P3
Reporter: Brooks Travis Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: front-end, requests, resourceaccess, ui-only, volaris-candidate
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File Screen Shot 2021-10-25 at 1.36.01 AM.png    
Issue links:
Defines
is defined by UIREQ-663 Perform Wildcard Item Lookup Before P... Closed
Relates
relates to UICIRC-712 Add Setting to Enable/Disable Wildcar... Closed
Epic Link: Requests
Development Team: Vega
PO Rank: 0
Rank: Cornell (Full Sum 2021): R5

 Description   

Current situation or problem:

Under some circumstances, items in FOLIO inventory may share a barcode, but FOLIO requires all item barcodes to be unique. One potential remedy in these situations is to add a suffix to the barcodes to make them unique WITHOUT updating the physical barcodes on the item. Another situation may arise when handling items from outside the local FOLIO inventory (eg. ILL, INN-Reach integration, etc.). We need a mechanism to disambiguate items under these circumstances when presented with an unaltered barcode.

In scope

  • Alternative workflow in ui-requests that performs a right-truncated wildcard search for an item by the entered barcode and presents a disambiguation UI
  • Settings to enable/disable (and possibly configure certain criteria for) this functionality

Out of scope

  • Similar functionality in ui-checkin

Use case(s)

  • Multiple libraries hosted in one FOLIO tenant that have duplicated barcodes in their physical collections and wish to utilize suffixes to distinguish items without altering their physical barcodes and be able to distinguish them when performing creating requests
  • Circulating items borrowed from other institutions (ILL or INN-Reach) where you do not control the barcodes and duplication is a possibility for which you need to account

Proposed solution/stories

To avoid inadvertently transacting with the incorrect item, it should be possible to perform a "fuzzy" or wildcard match on the entered barcode before populating item information in the request creation form. If more than one matching item record is returned, then a modal should be presented with a list of items (similar to the "move request" modal in ui-requests) to choose from. When an item is selected, that item's information should be used to populate the request transaction.

Links to additional info

Questions


Generated at Fri Feb 09 00:31:35 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.