Inventory
(UXPROD-785)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | R2 2021 | Parent: | Inventory |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Charlotte Whitt | Assignee: | Charlotte Whitt |
| Resolution: | Done | Votes: | 0 |
| Labels: | round_iv | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||||||||||||||||||||||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||||||||||
| Epic Link: | Inventory | ||||||||||||||||||||||||||||||||||||||||||||
| Analysis Estimate: | Very Small (VS) < 1day | ||||||||||||||||||||||||||||||||||||||||||||
| Front End Estimate: | Medium < 5 days | ||||||||||||||||||||||||||||||||||||||||||||
| Estimation Notes and Assumptions: | CW: Stories are all pointed except one. UI-only work | ||||||||||||||||||||||||||||||||||||||||||||
| Development Team: | Prokopovych | ||||||||||||||||||||||||||||||||||||||||||||
| UX Lead: | Filip Jakobsen | ||||||||||||||||||||||||||||||||||||||||||||
| PO Rank: | 139 | ||||||||||||||||||||||||||||||||||||||||||||
| Cap Plan Fix Version (DO NOT CHANGE): | R2 2021 | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R1 | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R4 | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R4 | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R4 | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R4 | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: Lehigh (MVP Summer 2020): | R1 | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: MO State (MVP June 2020): | R4 | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: TAMU (MVP Jan 2021): | R4 | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R2 | ||||||||||||||||||||||||||||||||||||||||||||
| Description |
| Comments |
| Comment by Cate Boerema (Inactive) [ 13/Sep/19 ] |
|
Marking stories associated with non-cap-mvp features P4 for now. |
| Comment by Holly Mistlebauer [ 17/Jun/20 ] |
|
Chicago comment from Round IV Outliers spreadsheet: There is no easy way to differentiate suppressed and suppressed records from the results list. An example from OLE of why this is important: we had a case last week where the GOBI API created many extra records. OLE had become very slow and was not responding within the expected timeout, so GOBI would assume the message was lost and re-send, up to 11 times. Without visual clues for which are suppressed, cleaning up the extra records would require looking into each and every full record display. -Tod Olson |
| Comment by Marc Johnson [ 17/Dec/20 ] |
|
It seems the user experience for this is to present warnings both at the top of the record and the top of the administrative section. I was wondering if you could help me understand why both are needed? And why we've chosen different presentation for each warning (e.g. different language, colour etc)? The UX mock ups in
Neither
cc: Zak Burke |
| Comment by Charlotte Whitt [ 17/Dec/20 ] |
|
Marc Johnson - re:
Yes - this is very indeed intended. The top of the record is displaying the warning message describing in text what to keep up for in the record. The use of icon you see as a visual in the Result list and in marking the holdings accordion and the item list in the top of the instance record. The UX mock ups inThat's also intended behavior, and it follows of the two stories right |
| Comment by Marc Johnson [ 21/Dec/20 ] |
I couldn't find a scenario in either of those stories which described the behaviour for a combined message. I may well have missed it, where is that behaviour described? |
| Comment by Charlotte Whitt [ 22/Dec/20 ] |
|
Added ticket:
|
| Comment by Charlotte Whitt [ 13/Jan/21 ] |
|
Hi Holly Mistlebauer - this feature is all Front End work. The feature is highly after sought by uChicago and other libraries going live by Summer 2021. The feature is Analysis complete and all stories ready to be pointed and picked up. |
| Comment by Holly Mistlebauer [ 13/Jan/21 ] |
|
Charlotte Whitt: I believe we have other features that are 'analysis complete' and desired by implementers, so we will need to take a good look before committing to any more new features from the Core: Functional Team for the R1 2021 release. We should know for sure after the Friday morning sprint planning meeting. Please plan on presenting the user stories for pointing at Friday's grooming meeting. This will take us one step closer. Thanks... |
| Comment by Charlotte Whitt [ 08/Feb/21 ] |
|
Hi Mike Gorrell - all the associated stories are all pointed. So all work is ready to go. |
| Comment by Holly Mistlebauer [ 29/Apr/21 ] |
|
Charlotte Whitt: All of the "defined by" user stories are completed. Does this mean we can close the UXPROD? If so, please close it. If not, please let me know what else needs to be done. Thanks much... |