[UXPROD-4546] Strip leading and trailing white spaces Created: 10/Nov/23  Updated: 10/Nov/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: None

Type: Umbrella Priority: TBD
Reporter: Martina.Schildt Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: crossapp, search
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to UXPROD-3473 Inventory: Strip leading, trailing, a... Draft
Development Team: None
Report Functional Area(s):
Import and Export, Metadata Management, Resource Access, Resource Management, User Management
PO Rank: 0
RCA Group: TBD

 Description   

Current situation or problem:

Leading or trailing white spaces are handled differently across FOLIO apps - e.g.:

  • search behaves differently across apps: leading/trailing white spaces are sometimes eliminated, sometimes they are included in search
  • data is saved with or without leading or trailing white spaces.

Example: In Inventory 'extra' spaces are eliminated, while in Orders they can exist and impact search & retrieval.

Use case(s)

1. Use case:

  • From Orders: "Newspaper  of  extra  spaces"  becomes "Newspaper of extra spaces" in Inventory. If you copy Newspaper of extra spaces from Inventory to search in Orders by Orders Lines, you retrieve nothing, until you add the spaces back.

2. Use case:

  • In Receiving app - when receiving a title: a user adds a barcode or call number and by mistake includes a leading or trailing white space
  • When a spine label is created based on the data entered in Receiving app: errors occur in spine labelling

Proposed solution/stories

White spaces should be handled consistently across FOLIO apps.

  1. When performing a search: leading and trailing white spaces should be eliminated.
  2. When saving data: leading and trailing white spaces should not be saved.

Links to additional info

  1. Search expectations across apps
  2. 2023-08-24 WOLFConMeeting notes: cross-app search

 


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