Inventory
(UXPROD-785)
|
|
| 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: |
|
||||||||||||||||
| Issue links: |
|
||||||||||||||||
| 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 DescriptionA component that supports the ability to filter results by <<YYYY>> only Need to have developed a stripes component. which support a Year only filter. 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: Things to consider:
|
| 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.:
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? 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. 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
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. |