Inventory (UXPROD-785)

[UXPROD-2276] Extend the keyword index. Add barcode to Keyword search in Inventory. Display holdings and item record directly with exact match - Phase 1 Created: 18/Feb/20  Updated: 28/May/23  Resolved: 28/May/23

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

Type: New Feature Priority: P3
Reporter: Charlotte Whitt Assignee: Charlotte Whitt
Resolution: Done Votes: 0
Labels: elastic-search, metadatamanagement
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File Skärmavbild 2020-02-19 kl. 14.41.21.png     PNG File Skärmavbild 2020-02-19 kl. 14.43.51.png     PNG File Skärmavbild 2020-02-19 kl. 14.44.04.png     PNG File Skärmavbild 2022-05-09 kl. 7.55.28 em.png     PNG File Skärmavbild 2022-05-09 kl. 8.07.03 em.png    
Issue links:
Blocks
is blocked by UXPROD-2806 Create Elasticsearch indexes for Inve... Closed
Defines
is defined by UIIN-2036 Search on a given item record, displa... Closed
Relates
relates to MSEARCH-31 Item - keyword search by barcode Closed
relates to UXPROD-3513 Inventory Elastic Search (Morning Glo... Closed
Epic Link: Inventory
Development Team: Prokopovych
PO Rank: 56
Rank: Chalmers (Impl Aut 2019): R2
Rank: Chicago (MVP Sum 2020): R2
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R1
Rank: GBV (MVP Sum 2020): R2
Rank: hbz (TBD): R4
Rank: MO State (MVP June 2020): R1
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): R4

 Description   

Overview: Request from Chalmers:
When searching in Inventory I want to have the most common ways to search in the Keyword search. To find the item record for a specific copy (a common task in the circulation desk) the easiest way is to search using the barcode. After the Q4 release that requires more clicks than before and the staff has begun to complain.

Developer comments by Jakub Skoczen:
Extend the keyword index
This is a backend solution that would extend "keyword" index definition to also include "barcode". In this case the query remains keyword all "xxx" and it's possible to combine barcode searches with other searches e.g Harry Potter 1234. The drawback is that "barcode" would be matches according to the full-text rules, so if there are any spaces or special characters in the barcode (I don't think there are?) it might behave weird.

Instance segment:

Holdings segment:

Item segment:

Search on item barcode result in one item barcode. There is a user requirement to have the item record displayed directly, and users want to skip the display of the 2nd pane, and the instance with item detailed list in the top.
This is a breaking change to the general UX consistency, but similar display might be introduced in other apps; e.g. MARC authorities.

Tweak of current display:

Display when we have implemented the hierarchical display of the result list:



 Comments   
Comment by Julian Ladisch [ 26/Jun/20 ]

I disagree with the proposed solution (extend the back-end keyword index) for the reasons given in UIIN-1942 Closed .

Comment by Theodor Tolstoy (One-Group.se) [ 18/Sep/20 ]

Charlotte Whitt, what are the next steps for this ticket?

Comment by Lisa Sjögren [ 02/Nov/20 ]

Hi! How is work on this ticket going?

Comment by Charlotte Whitt [ 02/Nov/20 ]

Hi Lisa Sjögren This feature didn't get that high of a calculated total rank (as of today only 52 points). The work has not been prioritized by cap.mvp.

What I can do is assigning the feature the new label 'elastic-search'. If easy to fix when implementing Elastic Search in Inventory, then we might be able to loop in the work. But that will be a decision for Magda Zacharska and the Elastic Search development team.

Comment by Lisa Sjögren [ 02/Nov/20 ]

Thanks Charlotte Whitt!

Comment by Charlotte Whitt [ 08/Nov/21 ]

Holly Mistlebauer - this feature is a low hanging fruit to implement, now we have done UXPROD-3046 Closed (swap to use Elasticsearch instead of PostgreSQL) and the ES work has been done for the back end MSEARCH-31 Closed .

Maybe we could have the work squeezed in for Lotus?

Comment by Charlotte Whitt [ 19/Apr/22 ]

Comment to myself and Oleksiy_Lemeshko:

I'll move the remaining work to UXPROD-3513 Closed (one story: UIIN-1942 Closed ) -> Morning Glory.

Comment by Charlotte Whitt [ 19/Apr/22 ]

Remaining work moved to UXPROD-3513 Closed (Morning Glory)

Comment by Khalilah Gambrell [ 13/Feb/23 ]

Hey Charlotte Whitt if this feature requires mod-search work then it will need to move to another release. 

Comment by Charlotte Whitt [ 14/Feb/23 ]

Okay, I'll assign the ticket to Spitfire, np Khalilah Gambrell

Comment by Khalilah Gambrell [ 28/May/23 ]

New feature will be created for Phase 2

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