Inventory
(UXPROD-785)
|
|
| Status: | Analysis Complete |
| 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: | 1 |
| Labels: | cornell-priority, elastic-search, inventory, long_term_solution, metadatamanagement, round_iv | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Epic Link: | Inventory | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Analysis Estimator: | Charlotte Whitt | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Development Team: | Prokopovych | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| UX Lead: | Kimie Kester | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Kiwi Planning Points (DO NOT CHANGE): | 45 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PO Rank: | 97 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PO Ranking Note: | CW: Implementing this feature for the mvp will address many of the view requirements from e.g. circulation staff (while waiting for |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R4 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R2 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: FLO (MVP Sum 2020): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R2 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: hbz (TBD): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Hungary (MVP End 2020): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Lehigh (MVP Summer 2020): | R2 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Leipzig (Full TBD): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: MO State (MVP June 2020): | R3 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: TAMU (MVP Jan 2021): | R2 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Trinity College (Jun 2021): | R2 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R2 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Current situation or Problem: The current use of MCL display in the second pane, displaying the search result as the Instance record, is not that useful, especially when searching on data specific for Holdings and Item data. This work will require a Stripes component supporting card display of the hierarchical view (
In scope: We need to replace the MCL display with a clear view of the instance record with associated holdings and item records, a display illustrating the hierarchical relationship for the given search/result. Out of scope: Sorting of search result when displayed in hierarchical view in a card form. Use case(s):
Proposed solution/stories: This level of refinement we need for all the go-live/in production libraries. Implement Filip's redesign, and add more detailed information in the display, e.g. HRID, and for the instance record Resource type, Format and more.
Links to additional info:
Questions [only if relevant]
|
| Comments |
| Comment by Erin Nettifee [ 10/Jul/19 ] |
|
|
| Comment by Holly Mistlebauer [ 17/Jun/20 ] |
|
Chicago comment from Round IV Outliers spreadsheet: Currently when we search Inventory we get an undifferentiated set of instances, holdings, and items. We cannot differentiate between them without opening up the records.With a data set our size, it is not feasible. It's not just edge cases. Anything that is not a known-item identifier search becomes a problem. This really affects things like "which holding statement do I add this newly-purchased volume to?" This really slows down work and increases the risk of mistakes.Note also that the lowest ranking is "can wait - up to a quarter" - this is critical for everyone. -Tod Olson |
| Comment by Jacquie Samples [ 23/Sep/20 ] |
|
To be clear, this is not just an issue for RA, everyone who needs to identify specific items will have a problem as the UI currently exists. Moving, editing, accessing specific items by MM folks are also going to have a tough time doing daily operations efficiently. I would like to point out that the latest rank, in the old-style ranking scheme, was about a year ago. |
| Comment by Charlotte Whitt [ 23/Feb/21 ] |
|
The current state is, that we use the multi column list (MCL component). Last year the MM-SIG SMEs expressed the wish for misc. improvements of the MCL display with more, and better data, and better sorting mechanism. This resulted in following new features:
In order to do a hierarchical structured navigation of records in inventory, we need to have developed a component, which support this. |
| Comment by Jacquie Samples [ 11/Mar/21 ] |
|
Thanks Charlotte Whitt ! I appreciate the clarification and updates which will make it easier for us to determine how to 'point' this Jira in the upcoming capacity planning process. |
| Comment by Holly Mistlebauer [ 05/Nov/21 ] |
|
Must consider
|