Patron Notices
(UXPROD-18)
|
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Patron Notices |
| Type: | New Feature | Priority: | P4 |
| Reporter: | julie.bickle | Assignee: | julie.bickle |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | notice_multiples, patron_notice | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||
| Epic Link: | Patron Notices | ||||||||||||||||
| Development Team: | None | ||||||||||||||||
| Report Functional Area(s): |
Resource Access
|
||||||||||||||||
| PO Rank: | 0 | ||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R1 | ||||||||||||||||
| Description |
|
Current situation or problem: In scope Out of scope Use case(s) Proposed solution/stories Links to additional info Questions |
| Comments |
| Comment by julie.bickle [ 22/Feb/22 ] |
|
Note for when I start work on this: See Zak's comment "I disagree with the suggestion, outlined here and in UICIRC-741, to handle renewal of multiple items in parallel." here: CIRC-1425 And from Steph: "Renewal has to happen in sequence because you need to check loan rules etc., so they cannot be done asynchronously as suggested." |