Cannot find Instance by Item call number using asterisk at the beginning of the query

Description

Overview: Cannot find Instance by Item call number using asterisk at the beginning of the query. Also, cannot find Instance by Item call number using "Contains all" option in Advanced search if query has one or several first characters of call number omitted

Steps to Reproduce:

  1. Login to Snapshot as user with "Inventory: All permissions" permission

  2. Open "Inventory" app

  3. Add Holdings with Item to any existing Instance:

    1. Click "Add holdings" button in Instance detail view

    2. Fill call number field ("YCN123456987")

    3. Fill all required fields

    4. Click "Save & close" button

    5. Click "Add item" button in added Holdings line in Instance detail view

    6. Fill all required fields (do not fill "Call number")

    7. Click "Save & close" button

  4. Add Holdings with Item to another existing Instance:

    1. Click "Add holdings" button in Instance detail view

    2. Fill all required fields  (do not fill "Call number")

    3. Click "Save & close" button

    4. Click "Add item" button in added Holdings line in Instance detail view

    5. Fill call number field ("001MYCN2225858881")

    6. Fill all required fields

    7. Click "Save & close" button

  5. Select "Item" toggle in first pane

  6. Select "Effective call number (item), normalized" search option

  7. Fill search input field with "*01MYCN2225858881" → Click "Search"

  8. Fill search input field with "*CN123456987" → Click "Search"

  9. Select "Holdings" toggle in first pane

  10. Select "Call number, normalized" search option

  11. Fill search input field with "*CN123456987" → Click "Search"

Expected Results: 

  • Step 7 - Instance from Step 4 is shown in second pane

  • Step 8 - Instance from Step 3 is shown in second pane

  • Step 11 - Instance from Step 4 is shown in second pane

Actual Results: No results found at Steps 7, 8, 11

Additional Information:
See attached screencasts:

  •  

Interested parties:

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

5

Checklist

hide

TestRail: Results

Activity

Show:

Yauhen Viazau July 27, 2023 at 11:36 AM

As per discussion PO and the rest of the team - such search scenario is not supported and and this is expected. Closing the ticket.

- please provide a list of fields for which this type of truncation is not supported now for POs and QAs to be able to use as a reference

Khalilah Gambrell July 26, 2023 at 1:37 PM

Hey   - we have FOLIO libraries that want to conduct left truncation searches. More work is planned in this area over the next couple of releases. 

cc: and  

Pavlo Smahin July 26, 2023 at 9:08 AM

, , this search option doesn't support this type of truncation. Please see the initial requirements in

Julian Ladisch July 25, 2023 at 6:14 PM

Standard indexes support truncation at the end. To support truncation at the beginning more advanced indexes are needed.

Do we really need item call number left truncation search?

 

Dmytro Melnyshyn July 25, 2023 at 3:08 PM

Hi , looks like BE doesn't support an asterisk at the beginning for "Effective call number (item), normalized". Please take a look at the message above.

Won't Do

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Spitfire

RCA Group

Not a bug

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created July 19, 2023 at 3:22 PM
Updated August 11, 2023 at 11:39 AM
Resolved July 27, 2023 at 11:36 AM
TestRail: Cases
TestRail: Runs