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: | 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: |
|
||||||||||||||||
| Issue links: |
|
||||||||||||||||
| 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:
This feature is split out of
The cap.plan team has asked for getting the different improvements split into their own feature:
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. Notes: Usecase: Out of scope: Documentation:
|
| Comments |
| Comment by Marc Johnson [ 21/Sep/20 ] |
|
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! |