User oddities script output

[eljhkrr]

Link to the user oddities script

[eljhkrr]

Next steps:

• Breakdown what the script does
• Identify different project contexts
• Implement the script for all projects
• Create a cron job to run the script regularly
• Consider a SQL solution

[eljhkrr]

Checks that detect-user-oddities.js performs for the Muso project:

• All user docs in _users db have a corresponding doc in medic db
• Facility id's in _users and medic db's should match
• Facility and contact documents exist for all users
• CHW users should have 'chw' role
• Non-chw users should not have 'chw_uhc' role
• Supervisor users should have 'supervisor' role
• Supervisor users should not have chw-related roles
• Inconsistent roles across user doc & contact

There are global checks that should be performed across all projects and there are checks that are specific to a project's context. Next step is to categorize the checks and collect information on project specific checks.

[eljhkrr]

Tracking global checks in this issue:

• All _users entries should have a corresponding entry in medic database
• Facility, contact & role details should match in _users & medic db's
• Facility & contact documents should exist
• Contact type should match actual hierarchy setup in contact vs app settings definition

Project specific checks following up in https://github.com/medic/app-services-team/issues/558

[kennsippell]

On holiday for the rest of August. I'm not going to be able to get to this by end of week so bumping to Sept

[eljhkrr]

Split into different use-cases: MoH Togo, MoH Nepal, MoH Kenya