Configuration of Implementation Model

[gkahiu]

Fixes #76
Mapping of NCS pathways to implementation models in step two of setting up a scenario.

[github-actions]

Plugin zip package for the changes in this PR has been successfully built!.

Download the plugin zip file here https://github.com/kartoza/cplus-plugin/suites/14234184721/artifacts/799192264

[gkahiu]

@Samweli please see the near-final changes to step two, only thing remaining is defining the file names for the NCS pathway files here, could not update as am unable to download the ZIP files, will follow-up separately. Also, this will also be dependent on the settings work, specifically on the base data directory so that we can use this to build the absolute path for the NCS pathway layers using this snippet.

[Samweli]

@Samweli please see the near-final changes to step two, only thing remaining is defining the file names for the NCS pathway

Thanks @gkahiu, can you fix the PR conflicts then I can post my review and we can move forward from there, thanks.

[gkahiu]

@Samweli see the updated PR which resolves the comments that you raised.

On the use of sqlite, I debated on this as well. On one hand, its use is definitely relevant if we are storing multiple scenarios with each scenario being linked to the respective implementation models, which are then subsequently linked to the respective NCS pathways. However, since we, at least for the current implementation, are only dealing with one scenario at any one time then the level of effort vs. the comparative advantage would be a bit skewed. I also considered JSON as another data source/store and maybe we might need to implement some aspects of it in the next epic.

Other considerations included:

• Consistency in using one store for the application data. Hence, the settings approach seemed more appropriate;
• Ease of use in making direct changes - while the dbmanager could have been used for editing the NCS pathway properties, the current implementation of settings is much more easier since any text editor can be used to make changes.

That said, the implementation is flexible and can always revert to the original idea of adopting sqlite as the requirements evolve.

[Samweli]

@gkahiu thanks, the line above should now change to fetch the icon from the plugin icon directory right?

[gkahiu]

Hi @Samweli, thanks. The icon source is now fixed.