Inventory (UXPROD-785)

[UXPROD-1632] New Stripes Component | Hierarchical display of terms filter Created: 27/Mar/19  Updated: 23/Aug/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: inventory, metadatamanagement, po-mvp, round_iv, search_enhancements
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File Inventory Container record (2).png     PNG File Screenshot 2023-08-23 at 23.38.37.png     PNG File Skärmavbild 2019-03-29 kl. 10.46.03.png     PNG File Skärmavbild 2019-03-29 kl. 10.46.14.png     PNG File Skärmavbild 2019-07-19 kl. 14.32.57.png     PNG File Skærmbillede 2019-03-28 kl. 18.51.14.png     PNG File screenshot-1.png    
Issue links:
Relates
relates to UXPROD-1894 Settings > Inventory > Instance: Impl... Closed
relates to UXPROD-1923 Settings > Inventory > Item: Implemen... Open
Epic Link: Inventory
Analysis Estimate: Small < 3 days
Analysis Estimator: Charlotte Whitt
Front End Estimate: Medium < 5 days
Front End Estimator: Rasmus Wølk
Front-End Confidence factor: Low
Back End Estimate: Small < 3 days
Back End Estimator: Niels Erik Nielsen
Development Team: Stripes Force
Kiwi Planning Points (DO NOT CHANGE): 1
PO Rank: 64
PO Ranking Note: CW: Filter improvements. In process (discussed with Khalilah, and John Coburn)
Rank: Chalmers (Impl Aut 2019): R4
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R2
Rank: GBV (MVP Sum 2020): R2
Rank: hbz (TBD): R1
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R2
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): R2

 Description   

Feature Description

Ability to filter hierarchical display of terms, e.g. Format and Material type, which both have a category, and terms associated with a given category

Screenshot (see Format and Material types filters)



 Comments   
Comment by Charlotte Whitt [ 28/Mar/19 ]

Note to self: STCOM-451 Closed is about search on date range. A similar feature for a component for search range by year is to be created.

Comment by Khalilah Gambrell [ 29/Mar/19 ]

Charlotte Whitt - would the range by year filter be based on this field in the instance record?

I ask because to do this filter, you need a field(s) that indicates begin and end dates in a consistent manner.

Comment by Charlotte Whitt [ 29/Mar/19 ]

Khalilah Gambrell - the range would be a combined search using the Date of publication element in the Instance record

So e.g. all records where the Date of publication is 2010 ≤ 2019 so that would be 2010, 2011, 2012 ... 2019.

What makes the query a little bit more difficult is, that in the element Date of publication, it also can be: cop. 1994, copyright 1994, or even (c) 1994

CC: Niels Erik Nielsen Jakub Skoczen

Comment by Khalilah Gambrell [ 29/Mar/19 ]

Thanks for the info. I think it makes implementing a year range filter very tricky because it's textbox but I'm curious as to what Niels Erik and Jakub suggest.

Comment by Charlotte Whitt [ 01/Apr/19 ]

Other systems can search on a range of Date of publication (year), so one would expect, that FOLIO also can support that.
BUT that said, we might need to implement a shadow element for the 'Date of publication' element, which is striped for cop., copyright, (c) and other data in the string, and only contains YYYY.

Comment by Khalilah Gambrell [ 16/May/19 ]

Hey Charlotte Whitt
I think #1 is done. I believe you can write a user story right now to collapse filters by default and assign it to Core: Functional because it needs to be done at the app level. Unless this is a request to show first couple of filter options and then a show more link under the filter. In that case then, that is something someone from stripes-force can estimate.
I do not know about #2 but we can probably ask John Coburn to provide a high level estimate for the frontend work.
As far as #3, we have a stripes component for filter by date range. When the data is available to support this field then we can see if the we need to create a new component or just extend the component to support just YYYY. My guess is this can be a safe Medium frontend effort.

Comment by Charlotte Whitt [ 16/May/19 ]

Hi Khalilah Gambrell -

  • yes #1 is done. I marked it with in the description.
  • It would be great if John Coburn can provide a high-level estimate of # 2 re. hierarchical display of terms, e.g. Format and Material type
    Unable to render embedded object: File (Skärmavbild 2019-03-27 kl. 20.58.40.png) not found.
  • And medium effort for # 3 reusing the existing date range component - sounds all good
Comment by Khalilah Gambrell [ 19/Jul/19 ]

Charlotte Whitt, can you link the backend stories that support this feature? Also I want to confirm what this feature represents the following work for Stripes-Force:

  • Hierarchical filter component
  • Date range component that supports filtering results by YYYY

Also please note that ability to filter long localization list will be handled by Core:Functional along with updates to the default display of filters on the Search and Filter pane.

If I am correct, can we update the feature title to Additional Inventory Filters: Year Date Range Filter AND Multi-level resource and material type filter? And move the ability to filter long localization list to another feature that will be worked on by Core: Functional?

Comment by Charlotte Whitt [ 19/Jul/19 ]

Hi Khalilah Gambrell - this feature is to cover, what you, John Coburn, Niels Erik Nielsen and I talked about at our meeting two weeks ago.
So besides what you listed, then it will also be:

  • Collapsable filters
  • The 'Show more' functionality
Comment by Khalilah Gambrell [ 19/Jul/19 ]

Charlotte Whitt - some of that work is Core: Functional. Is it possible to have two features: 1.) Core Functional work and 2.) Stripes-force? It will be easier for me to manage stripes-force work if the features were split. This is what we discussed two weeks ago as far as work breakdown

Core functional work that can be done now - use render filters same as Orders App.

  • Collapse filters
  • Language checkbox list becomes a dropdown
  • Reorder Inventory Search Filter
  • Resource Types Checkbox filter list
      • support Show first 5 options
      • Then show more link
      • Click show more displays inline

Stripes-Force

  • Create hierarchical checkbox filter component
  • Niels will hash out backend for hierarchy levels and confirm with Zak and John
    In addition both hierarchical checkbox filter component and the YYYY date range component require backend work before we proceed.
Comment by Charlotte Whitt [ 23/Aug/23 ]

This feature could most likely benefit from the use of the new filter builder work implemented in e.g. the Open Access app.

CC: Raegan Wiechert Felix Hemme lew235 Ann-Marie Breaux

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