Requests
(UXPROD-790)
|
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Requests |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Stephanie Buck | Assignee: | julie.bickle |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | resourceaccess, title, title_level_requests | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
| Release: | Not Scheduled |
| Epic Link: | Requests |
| Development Team: | Volaris |
| PO Rank: | 0 |
| Rank: Cornell (Full Sum 2021): | R1 |
| Description |
|
This is a placeholder until details can be added. Current situation or problem: To either integrate TLR with circulation rules OR make this (see attachment) configuration more granular In scope Out of scope Use case(s) Proposed solution/stories Links to additional info Questions |
| Comments |
| Comment by Thomas Trutt [ 14/Jul/22 ] |
|
My preference would be to have this integrated with circulation rules so that different notice packages could be sent based on patron type, material type, loan type and/or location.
– Use case. We are planning to use TLR for equipment wait lists. Because these items will have a different hold shelf expiration time we would like our available for pickup notices to reflect that. |