Inventory (UXPROD-785)

[UXPROD-1984] Ability to filter Inventory by publication date (range) Created: 12/Aug/19  Updated: 13/Nov/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: Trillium (R1 2025)
Parent: Inventory

Type: New Feature Priority: P3
Reporter: Charlotte Whitt Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: LC4, inventory, loc, metadatamanagement, po-mvp, round_iv, search, search_enhancements
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: 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ærmbillede 2019-03-28 kl. 18.51.14.png     PNG File screenshot-1.png    
Issue links:
Defines
is defined by UIIN-476 Search by Publication year (range) Draft
Requires
is required by UXPROD-4194 Inventory & Authority Search enhancem... Draft
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: Spitfire
Kiwi Planning Points (DO NOT CHANGE): 5
PO Rank: 74
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): R1
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R2
Rank: GBV (MVP Sum 2020): R1
Rank: Grand Valley (Full Sum 2021): R4
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

A component that supports the ability to filter results by <<YYYY>> only
For inventory app will be used to filter (instance, holdings, item and container) results by <<Publication YYYY>> only

Need to have developed a stripes component. which support a Year only filter.
A component very much similar to: STCOM-451 Closed Search & Filter Pane: Create a date range filter component

Screenshot



 Comments   
Comment by Rasmus Wølk [ 20/Aug/19 ]

I estimate this task to: "Medium < 5 days"

This component could work in a similar way as the <Timepicker> component:
https://ux.folio.org/storybook/?selectedKind=Timepicker

Things to consider:

  • Accessibility
  • Option to choose either a single year or a range (from/to year)
  • Making the component work with (and without) react-final-form
  • Should maybe include a prop for limiting the number of "year" options (e.g. "startYear" and "endYear"-props
  • It should probably sort out years before the chosen "from"-input when choosing "to" so that a user only can select years after the chosen "from"-year
Comment by Khalilah Gambrell [ 11/Sep/19 ]

Charlotte Whitt will the fields that are proposed to support this filter contain just <<YYYY>>?

Comment by Charlotte Whitt [ 11/Sep/19 ]

Hi Khalilah Gambrell - no not necessarily - it can be e.g.:

  • c2008
  • cop. 2008
  • copyright 2008
  • (c)2008

See e.g.: https://bugfest.folio.ebsco.com/inventory/view/b180cb4c-87a0-4258-b6a9-d098732a5143?query=semantic&sort=Title (folio/folio)

Comment by Khalilah Gambrell [ 11/Sep/19 ]

Charlotte Whitt - how would you expect a filter by publication date would work if a user can enter in that field the following values?
c2008
cop. 2008
copyright 2008
(c)2008
or possibly - 2008 -2018
or possibly 2008 - present
or possibly 2008 - 2010, 2014 - present

I guess my questions are tied to what are the rules that validates publication date values? and what are the expectations for the backend/frontend to support filtering based on the above ways one may enter a publication date?

Comment by Charlotte Whitt [ 11/Sep/19 ]

Hi Khalilah Gambrell - the user would expect to be able to search e.g. year range 2001-2004.
The user would not know if the Publication date was entered as: c2001, cop. 2001, copyright 2001, (c)2001.

Maybe we should have developers should be looped in and take a stab on how best possible to identify YYYY-numbers.

Comment by Holly Mistlebauer [ 17/Jun/20 ]

Chicago comment from Round IV Outliers spreadsheet: There's no workaround for this, and it is used by a lot of staff in regular work. -Tod Olson

Comment by Khalilah Gambrell [ 15/Jul/20 ]

Hi Charlotte Whitt, should the component support

  1. Select one year
  2. Select start year and end year

cc: Rasmus Wølk

Comment by Charlotte Whitt [ 15/Jul/20 ]

Hi Khalilah Gambrell - yes, we'd need the possibility to search a year range. I added this in the summary line.

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