Requests (UXPROD-790)

[UXPROD-1653] Move Requests from One Item to Another Created: 16/Apr/19  Updated: 04/Feb/21  Resolved: 19/Aug/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q3 2019
Parent: Requests

Type: New Feature Priority: P3
Reporter: Cate Boerema (Inactive) Assignee: Cate Boerema (Inactive)
Resolution: Done Votes: 0
Labels: cap-mvp, po-mvp, q2-2019-spillover, q3.1-2019
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by CIRC-316 Move Recalls to Checked Out Items whi... Closed
is defined by CIRC-333 Change Paged Item's Status To Availab... Closed
is defined by CIRC-395 UIREQ-269: Backend for Request Queue ... Closed
is defined by CIRC-411 Checked out item status changes when ... Closed
is defined by CIRC-416 UIREQ-303: Backend for preventing mov... Closed
is defined by UIREQ-269 Move Requests from One Item to Another Closed
is defined by UIREQ-303 Prevent move above page Closed
is defined by UIREQ-315 Permissions - Requests: Move to new item Closed
is defined by CIRC-399 UIREQ-294: Enhance validation error r... Closed
is defined by UIREQ-294 Request Move: Allow Type Change When ... Closed
Relates
relates to UXPROD-1921 Support moving request above page Draft
Epic Link: Requests
Front End Estimate: Large < 10 days
Front End Estimator: Michal Kuklis
Back End Estimate: XXL < 30 days
Back End Estimator: Marc Johnson
Estimation Notes and Assumptions: Comment from Marc in Slack: The basic move is likely not that hard, the changes to the re-validation is the biggest part of that work (and how we deal with how long that might take)
Development Team: Prokopovych
PO Rank: 130.1
PO Ranking Note: 2019-07-12: Bumped rank way up because this is in progress and targeted for completion in Q3.1
Rank: Chalmers (Impl Aut 2019): R1
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R2
Rank: 5Colleges (Full Jul 2021): R2
Rank: FLO (MVP Sum 2020): R2
Rank: GBV (MVP Sum 2020): R2
Rank: hbz (TBD): R1
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R1
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): R2

 Description   

This feature would allow moving (maybe in bulk) of requests from one item to another to support use cases like this:

  1. Item goes missing - reassign the requests to another copy/copies of same title
  2. New copy is acquired - reassign requests from an old copy to a new one

Initial thoughts on design (needs discussion with SIG):

  • Ability to select one, many or all requests associated with a given item and reassign to another item (may just start with moving one by one if that's simpler - queues are not usually very long and you may want to spread items across multiple copies anyway)
  • Should be able to see the length of the request queue on the other copies (items) so you can choose the best one for reassignment
  • Shouldn't be able to move any requests for which fulfillment has already begun (patron notice has been sent etc)
  • Shouldn't be able to move any requests to items where the request isn't allowed per request policy
  • Might offer user the ability to choose whether the requests go to the bottom or top of the queue when moved (though they can't displace the item at the very top of the destination queue if fulfillment of that request has already begun). Might auto-sort with oldest at top of queue. Requests will also be manually re-orderable after the fact once we have implemented UXPROD-1242 Closed

Mockups: https://drive.google.com/drive/folders/1ADrLDD09Ub9AKL7Vu704viS8EVPSB8xv



 Comments   
Comment by Cate Boerema (Inactive) [ 16/Apr/19 ]

Marc Johnson I'd like a tshirt estimate on this feature. Can you do it or recommend someone who can? There is ui to it, as well, so we'll need a frontend dev too. Thanks!

Comment by Cate Boerema (Inactive) [ 17/Apr/19 ]

Michal Kuklis, I know this feature is very high-level, but I would like to get a rough tshirt estimate on it so we can evaluate some different options. Would you add a frontend estimate when you have a moment?

Comment by Michal Kuklis [ 17/Apr/19 ]

Cate Boerema I added my estimate. The estimate may be different after we review the mockups for this story.

Comment by Cate Boerema (Inactive) [ 17/Apr/19 ]

Thanks Michal Kuklis!

Comment by Cate Boerema (Inactive) [ 17/Apr/19 ]

Thanks Michal Kuklis!

Comment by Cate Boerema (Inactive) [ 14/Jun/19 ]

This feature didn't make it in time for the Q2 2019 release so I changed the fix version to Q3 2019 and added the q2-2019-spillover tag. The estimates should probably be reduced for work to be done in Q3, as I would expect much of this will actually be dev complete before that development period begins. I'll hold off on that for now, though, as I have yet to see any of this working.

Generated at Fri Feb 09 00:17:21 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.