Fees/Fines
(UXPROD-792)
|
|
| Status: | Draft |
| Project: | UX Product |
| Components: | Fees/Fines |
| Affects versions: | None |
| Fix versions: | None | Parent: | Fees/Fines |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Holly Mistlebauer | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | Unassigned-from-Holly, feesfines, resourceaccess | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||
| Potential Workaround: | Holly: This was always viewed as a future feature. No workaround is needed. | ||||||||||||
| Epic Link: | Fees/Fines | ||||||||||||
| Front End Estimate: | XL < 15 days | ||||||||||||
| Front End Estimator: | Holly Mistlebauer | ||||||||||||
| Front-End Confidence factor: | Low | ||||||||||||
| Back End Estimate: | XXL < 30 days | ||||||||||||
| Back End Estimator: | Holly Mistlebauer | ||||||||||||
| Development Team: | Vega | ||||||||||||
| PO Rank: | 0 | ||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R5 | ||||||||||||
| Rank: Chicago (MVP Sum 2020): | R4 | ||||||||||||
| Rank: Cornell (Full Sum 2021): | R4 | ||||||||||||
| Rank: Duke (Full Sum 2021): | R5 | ||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R4 | ||||||||||||
| Rank: FLO (MVP Sum 2020): | R4 | ||||||||||||
| Rank: GBV (MVP Sum 2020): | R5 | ||||||||||||
| Rank: Grand Valley (Full Sum 2021): | R5 | ||||||||||||
| Rank: hbz (TBD): | R5 | ||||||||||||
| Rank: Hungary (MVP End 2020): | R4 | ||||||||||||
| Rank: Lehigh (MVP Summer 2020): | R5 | ||||||||||||
| Rank: Leipzig (Full TBD): | R4 | ||||||||||||
| Rank: Leipzig (ERM Aut 2019): | R5 | ||||||||||||
| Rank: TAMU (MVP Jan 2021): | R5 | ||||||||||||
| Rank: U of AL (MVP Oct 2020): | R5 | ||||||||||||
| Description |
|
The RA SIG requested this post-implementation feature: Allow for the blocking of interlibrary loans in addition to borrowing, renewals, and requests. |
| Comments |
| Comment by Erin Nettifee [ 26/Mar/19 ] |
|
Can there be more information about what this would actually do? There is no ILL module currently planned for FOLIO, correct? Is there an assumption that there would be connections to ReShare or other ILL applications that might use integrations with FOLIO to manage patron access? |
| Comment by Erin Nettifee [ 05/Jan/23 ] |
|
With Holly's retirement, I would advocate for closing this as "Not do". There is so much variation as to what "ILL" means for libraries, including how they might define them in FOLIO, the systems they might integrate with, and when / how they might want a block to behave. I think that without having those details, there's not much use in leaving this ticket open. A new one can be created when the requirements are ready to be worked on. |