Changes
In the Cost step below the list of costs we should add an additional question:
"How will these costs be covered?"
The answer here is supposed to be general, and not item specific.
As an answer the user should be able to have some helpful autocomplete propositions:
"included in project costs",
"covered by ... according to the cooperation agreement",
"covered by the institutes/groups annual budget"
Finally this textfield/information should be exported in the export templates as a paragraph “Coverage of costs” underneath the additional description of costs.
Additional notes
This Task might seem trivial at first, but it spans across all elements of the application from frontend to backend:
frontend, resource text, Data transfer objects, mapping to entities, adding a database column, and adding it to the export functions and the export word templates.
Acceptance Criteria
The text field needs to be editable, saved, loaded and exportable.
(Optional) Ideally we should also add this interaction to the existing e2e test that goes through the entire DMP, This way local testing will also be facilitated.
Risks? (optional)
Care that it can only work with an equivalent change on the damap backend. both need to be developed together and merged together.
Editing the word templates is never a comfortable activity, as they are not supported by GITs features. We can only replace the entire file, so it is important to be mindful if there are other tasks that have to edit this file, as they will simply overwrite each others changes.
ChristianeStork
commented
11 months ago
Changes In the Cost step below the list of costs we should add an additional question: "How will these costs be covered?"
The answer here is supposed to be general, and not item specific. As an answer the user should be able to have some helpful autocomplete propositions: "included in project costs", "covered by ... according to the cooperation agreement", "covered by the institutes/groups annual budget"
Finally this textfield/information should be exported in the export templates as a paragraph “Coverage of costs” underneath the additional description of costs.
Additional notes This Task might seem trivial at first, but it spans across all elements of the application from frontend to backend: frontend, resource text, Data transfer objects, mapping to entities, adding a database column, and adding it to the export functions and the export word templates.
Acceptance Criteria The text field needs to be editable, saved, loaded and exportable. (Optional) Ideally we should also add this interaction to the existing e2e test that goes through the entire DMP, This way local testing will also be facilitated.
Risks? (optional) Care that it can only work with an equivalent change on the damap backend. both need to be developed together and merged together. Editing the word templates is never a comfortable activity, as they are not supported by GITs features. We can only replace the entire file, so it is important to be mindful if there are other tasks that have to edit this file, as they will simply overwrite each others changes.