Bulk Edit
(UXPROD-868)
|
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Sunflower (R3 2024) | Parent: | Bulk Edit |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Magda Zacharska | Assignee: | Magda Zacharska |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | LC1, consortia-ebsco, firebird-po-share, loc, volaris-candidate | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||
| Release: | Sunflower (R3 2024) | ||||||||||||||||
| Epic Link: | Bulk Edit | ||||||||||||||||
| Front End Estimate: | XL < 15 days | ||||||||||||||||
| Front End Estimator: | Magda Zacharska | ||||||||||||||||
| Front-End Confidence factor: | 20% | ||||||||||||||||
| Back End Estimate: | XXL < 30 days | ||||||||||||||||
| Back End Estimator: | Magda Zacharska | ||||||||||||||||
| Back-End Confidence factor: | 20% | ||||||||||||||||
| Development Team: | Volaris | ||||||||||||||||
| PO Rank: | 0 | ||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R4 | ||||||||||||||||
| Description |
|
Current situation or problem In scope
The flow should be the same as already implemented for users and item records ([in app approach|https://drive.google.com/file/d/1lw3W4PUgcoUUBsCBbgmpPr2-nW8GGN_T/view?usp=sharing). Out of scope
Use case(s)
Additional use cases: https://folio-org.atlassian.net/wiki/display/BULKEDIT/Bulk+Edit+Use+Cases Questions
|
| Comments |
| Comment by Erin Nettifee [ 23/Sep/22 ] |
|
Hi Magda:
We'll want user UUIDs and user barcodes (not sure what User ID means in this list.) Both user UUID and user barcode are on the request schema. In terms of columns, you could definitely eliminate proxy from showing automatically. I think you would want to add pickup service point as a column (that doesn't show currently in the Requests app, but we have been talking about adding it.)
To be clear on functionality - the hold shelf expiration date is empty when a request is created. It's populate when a request moves to Open - Awaiting Pickup, based on the value in the associated service point configuration. The hold shelf expiration date is not populated when a request goes to Open - Awaiting Delivery, because the request is not going on the hold shelf, it's getting delivered. Once a request is in Open - Awaiting Pickup, the request expiration date doesn't serve any workflow function anymore, so it can be ignored. The only request status that this particular feature applies to is Open - Awaiting Pickup. All three types of requests (pages, holds, recalls) can move to Open - Awaiting Pickup, so all of them need to be included in this feature. |
| Comment by Magda Zacharska [ 08/May/23 ] |
|
Moving LC1 label from epic to defining features with Caitlin Stewart permission. |