Improve the database design for the impact pathways relations

[hernandcb]

Due to the initial requirements we designed a complex way to relate the ip elements with the program to which it belongs to (See database diagram attached).

Given that at the end we didn't need that complexity, it is needed to simplify it.

[hernandcb]

I have created a relation between the ip_element and the ip_program directly (see image)

However, before the deletion of the intermediate tables it is needed to adjust the backend code. This issue will remain open until the changes are applied and the intermediate tables are deleted.

[hernandcb]

Please keep in mind that the table ip_indicators also refers to the ip_program_elements table. I have already created a direct relation between the ip_indicator and the ip_element.

Therefore, the changes pending are:

• [x] Update the backend code to load the IP elements properly
• [x] Update the backend code to load the IP indicators properly
• [x] Remove the column program_element_id from the table ip_indicators
• [ ] Delete table ip_program_elements
• [ ] Delete table ip_program_element_rellation_types

[htobon]

@hernandcb Any update on this issue?

[hernandcb]

Yes, I have updated the list above. I'll come back to this issue once everything is done.

[htobon]

thks.

[htobon]

Should we move this issue for the next release?

[htobon]

MARLO will manage a different Impact Pathway.