...

• payment layer through REST API - dedicated API for GePG (Government ePayment Gateway)

  • MUSE API exists (will not be changed) - fully based on modular version

  • GePG API exits in legacy

    • needs to be migrated to modular architecture

    Image Removed

    • (as a custom API)

  • Image Added

• capitation payment,

• commission

• Covered by Project: 2022.T1c Modularisation III :

  • GePG not covered for the implementation in TZ, but support in global components might be possible

  • 🧑‍🏭 mobile apps on REST API

  • 🧑‍🏭 specific reports : capitation payment, commission → migrate to ReportBro https://docs.google.com/spreadsheets/d/1ORCdW5qajBbDT4BaKmAKf6W7X4wbs2Rcd0EQNEVRRzQ/edit?usp=sharing

  • 🧑‍🏭 Download master data

    • list of beneficiaries

  • 🧑‍🏭 Funding

  • …

• capitation payment configuration in Product

• batch run

  • capitation payment SP

  • batch run SP

Custom Modifications in Cameroon

HIV

• 🧑‍🏭 report on migration needs done by STPH (-> Implementers) - covered in Project: Customization Cameroon

EDUCASH

• Cash-Transfer scheme => to be migrated to modular?

Custom Modifications in Gambia

• Cash-Transfer scheme is in progress of migration

...

• Impact: none

• doesn't work in legacy version, not used

• needs popping up but will have to be addressed as new features

MS-SQL Driver in Django

• Impact:

  • Custom Access to MS-SQL DB

  • affects JSON-B column access

  • hinders upgrade to Django 4

• Discussion:

  • only a problem as long as s.o. is using MS SQL

  • maybe there are new drivers

  • solved - there is an official MS driver for Django now

...

• Impact:

  • new installations (new, empty DB) not yet using all attributes

  • migration script need to know DB version to adjust to all scenarios

• Discussion:

  • Database compatibility PostgreSQL & MS SQL Server

  • done - DB - initialisation:

    • two separate INIT scripts for PostgreSQL & MS SQL available

  • done - legacy migration:

    • migration script for the legacy data available

  • done - future development will be against PostgreSQL

    • other DB will have to use Django Migration scripts to fork to their DB system (automatically through Django “make migration“ - might need manual adaptations)

  • documentation needed

    • most is done automatically at startup

    • create a link in each release note point at a migration path for that version with manual exceptions

    • testing of the documentation is needed

Reports

• List of reports: Wiki: Report module, migration status: https://docs.google.com/spreadsheets/d/1ORCdW5qajBbDT4BaKmAKf6W7X4wbs2Rcd0EQNEVRRzQ/edit?usp=sharing

• wip - which reports still need to be migrated? which ones are still used?

  • some reports don’t work

  • list of reports to all sites with feedback on what they are still using (no nice-to-haves!)

  • also have a look at https://www.metabase.com/start/oss/

...

Domain	Name (link)	Browser	Linux	Win	FOSS	Description
DB Admin	https://www.pgadmin.org/				🐧	Comfortable PostgreSQL DB Admin tool
SQL Client	https://dbeaver.io/				🐧	Comfortable Visual SQL client with ER diagrams
SQL Client	SQuirreL				🐧	simple SQL client
Server Monitoring	https://munin-monitoring.org/				🐧	Server statistics daily / weekly / monthly
Server Admin	https://cockpit-project.org/				🐧	web-based server administration
Explain Plan Analyser	http://tatiyants.com/pev/#/plans/new				🐧	Visualise query execution plans: Image Added