Budget management functionality that FOLIO needs to stay competitive
(UXPROD-3442)
|
|
| Status: | Analysis Complete |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Budget management functionality that FOLIO needs to stay competitive |
| Type: | New Feature | Priority: | P4 |
| Reporter: | Dennis Bridges | Assignee: | Dennis Bridges |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | acquisitions, finances, needs-ranking, needs-rmsigreview, round_iv | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue links: |
|
||||||||
| Epic Link: | Budget management functionality that FOLIO needs to stay competitive | ||||||||
| Front End Estimate: | Large < 10 days | ||||||||
| Front-End Confidence factor: | Low | ||||||||
| Back End Estimate: | Large < 10 days | ||||||||
| Development Team: | Thunderjet | ||||||||
| PO Rank: | 33.1 | ||||||||
| Rank: Chicago (MVP Sum 2020): | R4 | ||||||||
| Rank: Cornell (Full Sum 2021): | R2 | ||||||||
| Rank: Duke (Full Sum 2021): | R4 | ||||||||
| Rank: 5Colleges (Full Jul 2021): | R4 | ||||||||
| Rank: GBV (MVP Sum 2020): | R1 | ||||||||
| Rank: Grand Valley (Full Sum 2021): | R4 | ||||||||
| Rank: MI State-Lib of MI (Sum 2021): | R5 | ||||||||
| Rank: MO State (MVP June 2020): | R4 | ||||||||
| Rank: TAMU (MVP Jan 2021): | R2 | ||||||||
| Rank: U of AL (MVP Oct 2020): | R3 | ||||||||
| Description |
|
Problem: Allocating money to each individual Fund can be time-consuming for an administrator. When using shared pools there are no restrictions/limits on spending by expense class. One group could spend all money before others have a chance too. Use cases:
Requirements:
Questions:
|
| Comments |
| Comment by Dennis Bridges [ 21/Sep/20 ] |
|
As the community priority for this feature is increasing, I have updated the PO rank as well. Expense class functionality was enhanced in as a result of UAT and this extension of that functionality will add a lot of value to the feature set. Potentially changing the way users choose to setup their Fund structures. |
| Comment by Anya [ 25/Sep/20 ] |
|
Will this fundamentally change the functionality of the system ... away from an in-app reporting tool to database structure/design .. ie critical to the workflow ... do we have to mandate the use of expenses classes or can it be optional? tagging Dennis Bridges |
| Comment by Dennis Bridges [ 25/Sep/20 ] |
|
Hi Anya the expense classes are in every way optional. Their intention is to allow libraries to track and manage expenditure at increasing levels of detail without having to allocate money at increasing levels of detail. This feature is an extension that would allow users, not just to track expenditure, but to choose to limit expenditure against some or all expense classes for any given fund. It would still not be necessary to use expense classes nor would it be necessary to limit expenditure for expense classes IF you were using expense classes. |
| Comment by Anya [ 25/Sep/20 ] |
|
Tagging Former user please see the above |