Inventory (UXPROD-785)

[UXPROD-2669] Inventory. Result list. Refined display rules MCL. Adding resource type Created: 18/Sep/20  Updated: 26/Sep/23

Status: Open
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: 0
Labels: delegate_candidate, metadatamanagement, po-mvp, round_iv, search_result, short_term_solution
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File Skærmbillede 2020-11-17 kl. 14.01.49.png     PNG File screenshot-1.png    
Issue links:
Defines
is defined by UIIN-1263 Inventory. Instance sorting. Adding r... Draft
Relates
relates to UX-449 UX: Sort by values for updated invent... Open
Epic Link: Inventory
Analysis Estimator: Charlotte Whitt
Front End Estimate: Small < 3 days
Front End Estimator: Michal Kuklis
Front-End Confidence factor: Medium
Back End Estimate: Large < 10 days
Back End Estimator: Marc Johnson
Estimation Notes and Assumptions: Need to figure out how to sort on resource type which is implemented as a reference to a record. Would this require either a join (which we think might affect count accuracy) or need to copy (and synchronise) the resource type name onto each instance
Development Team: Spitfire
Kiwi Planning Points (DO NOT CHANGE): 2
PO Rank: 106
Rank: Chalmers (Impl Aut 2019): R4
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R3
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R1
Rank: FLO (MVP Sum 2020): R1
Rank: GBV (MVP Sum 2020): R4
Rank: Grand Valley (Full Sum 2021): R1
Rank: hbz (TBD): R1
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R1
Rank: MO State (MVP June 2020): R2
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R1

 Description   

Laura Daniels:
MM SMEs have expressed a desire, that is, to focus on the longer-term goals rather than interim goals if they can't be built on directly. The lack, for instance, of call number in the search results display of the holdings segment, would not be addressed by the improvements in the JIRA features listed below. So I agree with you, @charlotte, that putting resources toward the hierarchical display instead ( UXPROD-491 Analysis Complete ), if at all possible, is in our best interest.
Charlotte Whitt: See more comments added 2/23/2020 in UXPROD-491 Analysis Complete .
 

  • - - - - - - - - - - - - - - 
     

This feature is split out of UXPROD-1634 Closed - the library ranking is kept from the original feature, which previously included all relevant refinements of the result list for the MVP.

The cap.plan team has asked for getting the different improvements split into their own feature:

  1. UXPROD-1634 Closed (index title/title)
  2. UXPROD-2667 Open (sort on contributor, when more than one contributor is listed)
  3. UXPROD-2668 Open (Adding instance HRID)
  4. UXPROD-2669 (Adding resource type)
  5. UXPROD-2670 Draft (Adding format)
  6. UXPROD-2671 Open (Adding edition)
  7. UXPROD-2703 Draft (Adding publication date)

Overview: There is not enough information available in the current display of the result list to be able to distinguish between instances with identical information; e.g. solve the problem exemplified in this screen shot.

Adding instance HRID, resource type, format and edition to the result lists would solve this issue.

Notes:
This is critical for the everyday use of Inventory. Especially journal title can be very similar/identical and therefor impossible to select the right one.

Usecase:
As a librarian who is searching in Inventory.
I want the search results to display the resource type to help better distinct identical titles.

Out of scope:
Future need: customizable results lists (tenant level and user level)

Documentation:

  1. Slide deck reviewed by MM-SIG 10/1/2020 and 10/8/2020 - https://docs.google.com/presentation/d/1kDumWwhNfP7Mq9hZ5q4O1cnbg_BY4ILgKbjBWOO4Xso/edit#slide=id.p
  2. Survey send out on the #metadata-management channel 10/7/2020 - https://docs.google.com/presentation/d/13Dt-Tkr_nzgU2Oxb044J4d3RSxxk4R-0lq-AlKXIItg/edit#slide=id.g9998cb799b_2_0


 Comments   
Comment by Marc Johnson [ 21/Sep/20 ]

Charlotte Whitt Cate Boerema

Can the user sort the instances by resource type?

Comment by Charlotte Whitt [ 21/Sep/20 ]

Hi Marc Johnson - yes, having the columns in the result list to be sortable is a general FOLIO wide UX for display of a result list - see e.g. Orders (https://folio-snapshot.dev.folio.org/orders/lines?qindex=titleOrPackage&query=the%20city%20post-modernity&sorting=vendorDetail.refNumber&sortingDirection=ascending) and Request (https://folio-snapshot.dev.folio.org/requests?filters=requestType.Hold&sort=requestStatus%2CrequestDate)

Comment by Cate Boerema (Inactive) [ 24/Sep/20 ]

Michal Kuklis, could you please add a frontend estimate for this feature? Thanks much!

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