Page Comparison

...

• topic for this discussion: cross-app consistency of search syntax - search behaviour is a separate topic
• truncation could be state 1 and wildcard state 2 of planning and development
• if user wants to search for a fragment (that is truncated in both directions) the user can do a phrase search in inverted commas

• Status
  colour Grey title agreed

  searches should NOT always be left anchored and truncated by default

• Status
  colour Grey title agreed

  searches should NOT be left anchored by default
  • we should not change any of the searches in Inventory because some data is normalized - don't want to loose anything that has been reached so far
• maybe some variation is okay, but we should try to minimize variation
• would advanced search be a solution here?
  • advanced search is available in Inventory
  • there was no discussion on advanced or expert search in ERM so far - in ERM for some filtering query builder are used
  • agreement: try to align in wildcards - advanced search or even query builder are too complicated = "one step after the other"

• Status
  colour Grey title agreed

  agreement: left anchored or not → should be a separate selection - via e.g. a checkbox or syntax

Wildcards

• Status
  colour Grey title agreed

  The following wildcards should be used across all FOLIO apps:
  1. * which matches 0, 1 or many characters 
  2. ? which matches a single character
• The above wildcards should be usable within strings.

Spaces handling

• spaces handling should be consistent
• there is already a ticket existing for Inventory
• white spaces handling should be consistent between Inventory and Orders - no matter how
• there might be IDs with spaces - spaces in between fragments are not concerned here
  • possibility: can search box provide different search options?
  • or quotes?
  • a good advanced search would work for different types of users
• there is a concern for barcodes and call numbers - leading and trailing white spaces can cause errors in spine labelling
•  Tim Darlington in chat: We had a few user records with leading or trailing spaces in the barcode field. Sierra ignored these, Folio doesn't which means the barcode search fails. We corrected the barcodes but it would make sense to strip leading or trailing spaces from data
• that's why agreement on:

• Status
  colour Grey title agreed

  Leading and trailing white spaces should be eliminated - no searching for leading and trailing white spaces

• Status
  colour Grey title agreed

  Leading and trailing white spaces should not be saved - no saving of leading and trailing white spaces

...