Open trugwaldsaenger opened 6 years ago
literarymachine
commented
6 years ago Example: A government funds a programm with 2 Million Euro. The money is being allocated to four projects, which each get 500.000 Euro.
We do have Program as a sub type of Project in our data model. It can already have a budget. Couldn't we just leave it that way?
karindr
commented
6 years ago Since we have "Budget" for "Program" and "Project" even now simply adding up the budgets for a country is not correct because the program could have a budget of 4 Million and gives this to its 4 projects each receiving 1 Million. Adding up to 8 Million would be wrong even now.
trugwaldsaenger
commented
5 years ago I think this not super urgent - setting it to P2.
For projects we have the field "budget", which allows to show with how much money a project is being funded and by whom.
Working on policies we seem to touch the other side of the medal here. Investment decisions are at the very core of what a policy is.
Example: A government funds a programm with 2 Million Euro. The money is being allocated to four projects, which each get 500.000 Euro.
So is the existing field "budget" the right field to be added to policies as well? I do not see this clearly yet, but I would assume no, because if we use the same field for both sides of the financing flow, things can easily being mixed up. If calculating the overall money spend for OER in the country, it could happen easily in this case that the result will be 4 Million Euro instead of 2 Million.
So maybe the solution here is not to use the data type "action.budget" but a corresponding new type "policy.budget".
I expect this question a bit tricky and therefore related it to the second iteration. If I´m wrong and it could be implemented easily, the ticket could be moved to the first iteration, because if we have a look at all collected policies anyway, it will be easy to include the budget as well, in case this information is given.