Inventory
(UXPROD-785)
|
|
| 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: |
|
||||||||||||
| 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: | 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 |
| Comments |
| Comment by Charlotte Whitt [ 28/Mar/19 ] |
|
Note to self:
|
| 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 |
| 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. |
| Comment by Khalilah Gambrell [ 16/May/19 ] |
|
Hey Charlotte Whitt |
| Comment by Charlotte Whitt [ 16/May/19 ] |
|
Hi Khalilah Gambrell -
|
| 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:
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. |
| 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.
Stripes-Force
|
| 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. |