Budget management functionality that FOLIO needs to stay competitive (UXPROD-3442)

[UXPROD-924] See materials paid for by more than one Fund Created: 13/Jun/18  Updated: 09/Dec/21

Status: Draft
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, appreport, crossrmapps, inventory, orders
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to UXPROD-867 Reporting: In-App Reports Open
relates to UXPROD-1144 Managing Ledgers, Funds, Budgets, Fis... Closed
Epic Link: Budget management functionality that FOLIO needs to stay competitive
Analysis Estimate: Very Small (VS) < 1day
Front End Estimate: Small < 3 days
Back End Estimate: Medium < 5 days
Development Team: Thunderjet
Report ID (pre-May 2019): ID214
Report Contact(s):
Sharon Beltaine
Report Functional Area(s):
Resource Management
PO Rank: 32
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R5
Rank: Cornell (Full Sum 2021): R5
Rank: Duke (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R3
Rank: FLO (MVP Sum 2020): R4
Rank: GBV (MVP Sum 2020): R4
Rank: Grand Valley (Full Sum 2021): R4
Rank: hbz (TBD): R4
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R4
Rank: Leipzig (Full TBD): R4
Rank: Leipzig (ERM Aut 2019): R4
Rank: TAMU (MVP Jan 2021): R4
Rank: U of AL (MVP Oct 2020): R4

 Description   

This is an app report that details the contribution of multiple funds to specific resources. In order to identify how many resources where acquired by joint purchases.

Note: Discussed once again with the ACQs group and were not able to identify clear use cases for incorporating this as an in-app report. Members will reach out to others in their institutions to confirm (May 7, 2020). If we decide to close we will need to report back to Reporting SIG.

Use Cases:



 Comments   
Comment by Jesse Koennecke [ 09/Apr/19 ]

The original description for this makes sense for a required, Go Live feature. The revised description looks like a different feature that may not be Go Live priority.

Comment by Holly Mistlebauer [ 16/Apr/19 ]

Dennis Bridges, the ID number for the related report has been changed so I updated the Summary for this issue.

Comment by Dennis Bridges [ 11/May/20 ]

Sharon Beltaine The group has been discussing this issue further and it seems for all that have chimed in this issue could be served adequately by a standard report rather than an in-app report. I'm hesitant to close the feature, but I'd like to clean up our queue as much as possible. Could you raise it with reporting folks and see if we can reasonably remove this from the in-app report list. Thx!

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