Inventory (UXPROD-785)

[UXPROD-491] Result list. Long term solution. Implement Refined UX-design for Inventory - hierarchical navigation structure (Instance, Holdings, Item) Created: 06/Apr/18  Updated: 04/Jul/23

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

Type: New Feature Priority: P3
Reporter: Charlotte Whitt Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: cornell-priority, elastic-search, inventory, long_term_solution, metadatamanagement, round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File Skärmavbild 2019-10-15 kl. 22.25.09.png     PNG File Skärmavbild 2019-10-15 kl. 22.25.27.png     PNG File Skärmavbild 2019-10-15 kl. 22.50.51.png    
Issue links:
Defines
is defined by UX-435 UX: Inventory. Hierarchical result li... Open
is defined by UX-447 UX: Updated holdings record on invent... Open
is defined by UX-448 UX: Updated item record on inventory ... Open
is defined by UX-449 UX: Sort by values for updated invent... Open
is defined by UX-446 UX: Updated instance record on invent... In Progress
is defined by UIIN-2321 In Inventory search, Item, for a Form... Draft
is defined by UX-450 UX: Hierarchical level navigation bar... Draft
is defined by UX-451 UX: Hierarchical level navigation. Ho... Draft
is defined by UX-452 UX: Hierarchical level navigation. It... Draft
Relates
relates to UIIN-1831 Bugfest. Holdings with more than 5000... Closed
relates to STRIPES-739 SPIKE: New Results List View with Hie... Closed
relates to UIIN-566 Basic search: Search by barcode. Refi... Closed
relates to UIIN-570 Item Count on Inventory Search Result... Closed
relates to UIIN-130 Detail page, 3rd pane. Hierarchical l... Draft
relates to UIIN-129 Result list. Hierarchical structure o... Blocked
relates to UIIN-133 Implement new icons for Instance, Hol... Closed
relates to STCOM-234 Hierarchical List (TreeView) component Draft
Epic Link: Inventory
Analysis Estimator: Charlotte Whitt
Development Team: Prokopovych
UX Lead: Kimie Kester
Kiwi Planning Points (DO NOT CHANGE): 45
PO Rank: 97
PO Ranking Note: CW: Implementing this feature for the mvp will address many of the view requirements from e.g. circulation staff (while waiting for UXPROD-1742)
Rank: Chalmers (Impl Aut 2019): R4
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R2
Rank: FLO (MVP Sum 2020): R1
Rank: GBV (MVP Sum 2020): R2
Rank: hbz (TBD): R1
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R2
Rank: Leipzig (Full TBD): R1
Rank: MO State (MVP June 2020): R3
Rank: TAMU (MVP Jan 2021): R2
Rank: Trinity College (Jun 2021): R2
Rank: U of AL (MVP Oct 2020): R2

 Description   

Current situation or Problem: The current use of MCL display in the second pane, displaying the search result as the Instance record, is not that useful, especially  when searching on data specific for Holdings and Item data. This work will require a Stripes component supporting card display of the hierarchical view ( STCOM-234 Draft ).

In scope: We need to replace the MCL display with a clear view of the instance record with associated holdings and item records, a display illustrating the hierarchical relationship for the given search/result.

Out of scope: Sorting of search result when displayed in hierarchical view in a card form. 

Use case(s):

  1. As a circ staff I search for a given title using the Keyword search option, and then want to find the available copies (item) - and ONLY the available items
  2. As a cataloger I search for holdings records with a given holding note

Proposed solution/stories: This level of refinement we need for all the go-live/in production libraries.

Implement Filip's redesign, and add more detailed information in the display, e.g. HRID, and for the instance record Resource type, Format and more.

 

Links to additional info: 

Questions [only if relevant]
 
 

 



 Comments   
Comment by Erin Nettifee [ 10/Jul/19 ]

UXPROD-1807 Closed would be a go-live for circ staff from almost all institutions - that may be change how you think about the approach, if the cataloging reps would not necessarily consider this as go-live.

Comment by Holly Mistlebauer [ 17/Jun/20 ]

Chicago comment from Round IV Outliers spreadsheet: Currently when we search Inventory we get an undifferentiated set of instances, holdings, and items. We cannot differentiate between them without opening up the records.With a data set our size, it is not feasible. It's not just edge cases. Anything that is not a known-item identifier search becomes a problem. This really affects things like "which holding statement do I add this newly-purchased volume to?" This really slows down work and increases the risk of mistakes.Note also that the lowest ranking is "can wait - up to a quarter" - this is critical for everyone. -Tod Olson

Comment by Jacquie Samples [ 23/Sep/20 ]

To be clear, this is not just an issue for RA, everyone who needs to identify specific items will have a problem as the UI currently exists. Moving, editing, accessing specific items by MM folks are also going to have a tough time doing daily operations efficiently. I would like to point out that the latest rank, in the old-style ranking scheme, was about a year ago.

Comment by Charlotte Whitt [ 23/Feb/21 ]

The current state is, that we use the multi column list (MCL component). Last year the MM-SIG SMEs expressed the wish for misc. improvements of the MCL display with more, and better data, and better sorting mechanism. This resulted in following new features: 

  • UXPROD-1634 (index title/title)
  • UXPROD-2667 (sort on contributor, when more than one contributor is listed)
  • UXPROD-2668 (Adding instance HRID)
  • UXPROD-2669 (Adding resource type)
  • UXPROD-2670 (Adding format)
  • UXPROD-2671 (Adding edition)
  • UXPROD-2703 (Adding publication date)

 
Adding these new columns and improving e.g. the title sort by using the index title etc. still does not solve the key problem: The MCL displays only the instance records. And in the 3rd pane you get the complete list of holdings and the associated instances to these holdings (displayed in the top of the instance record).
 
If you search on a given holdings, and/or item, then you only want to get the relevant information for that holdings/item.
 
The long term solution is the hierarchical display of search results as Filip Jakobsen envisioned. See: UXPROD-491
Implement Refined UX-design for Inventory - hierarchical navigation structure (Instance, Holdings, Item)
 
 
 

 

 

 
 
 
Hopefully Elastic Search can provide us with the needed precision here, and with a better supporting search tool, then doing the hierarchical navigation structure, is not too complicated to realize.
 
The UX-mock ups are some of Filip Jakobsens earlier work, and I this work needs to be revisited by a UX designer. The new UX work should incorporate the thinking of adding more data and improve sorting, e.g. skipping leading articles in the Title sort etc. etc. all described in:

  • UXPROD-1634 (index title/title)
  • UXPROD-2667 (sort on contributor, when more than one contributor is listed)
  • UXPROD-2668 (Adding instance HRID)
  • UXPROD-2669 (Adding resource type)
  • UXPROD-2670 (Adding format)
  • UXPROD-2671 (Adding edition)
  • UXPROD-2703 (Adding publication date)

In order to do a hierarchical structured navigation of records in inventory, we need to have developed a component, which support this. 
 
This work is drafted in: STCOM-234 Hierarchical List (TreeView) component
 

Comment by Jacquie Samples [ 11/Mar/21 ]

Thanks Charlotte Whitt !  I appreciate the clarification and updates which will make it easier for us to determine how to 'point' this Jira in the upcoming capacity planning process.

Comment by Holly Mistlebauer [ 05/Nov/21 ]

Must consider UIIN-1831 Closed in this solution.

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