GSoC 2022: Redo Legacy UI Cohort Builder - Project Updates

Community GSoC
61

Personally, I think it belongs in the App Switcher, but with some kind of privilege guard around it (the UserHasAccess component). To my mind, this is less to do with how it’s used than how easily discoverable we need the feature to be.

2 Likes
62

Thank you! @zacbutko @ibacher for your input. @grace @slubwama @jdick What do you think?

1 Like
63

Well said Ian. However in this particular example - let’s think about the workflow:

  • Who needs the cohort builder tooling? People with Admin access.
  • How do those people usually find the tools? In the System Administration menu.
  • How do those people usually find the cohort builder? In the relevant section of the Sys Admin page, eg here:

image

Thus, executive decision here: we should keep the User Experience consistent and continue linking to the Cohort Builder UI from that same place. It just means that when you click on the thing in the old Admin Page UI, it takes you to the new Cohort Builder UI instead of the old one. Is that technically feasible for you to do @anjisvj?

(Otherwise, the App Switcher menu will grow crazy long over time and get increasingly difficult for Admins to find what they need.)

1 Like
64

That makes sense @grace. But before replacing the old one it’s better to do some testing and ensure it’s stable. @tanderson said that they are willing to help with testing. But in dev3 cohort builder seems to be not working. It does work locally. I will check what’s the issue there.

65

In terms of usage, we at PIH-Rwanda use it in 3 ways.

  1. Indicators at the coordinator level. (This is used very frequently in Rwanda for PIH sites by the coordinators and by the IT’s at MOH supported hospitals)
  2. Data pulls by the coordinators using Data Export from the Admin page using saved cohorts from Cohort builder
  3. The creation of saved cohorts that are the initial basis of what mUzima pulls (I don’t totally understand this as it feels like MySQL is part of the pull as well)

#'s 2 and 3 are naturally administrative actions. #1 is is done only by people who have access to the admin page, but it hasn’t felt as adminny. We have historically had access through a header menu along with ‘dictionary’ which was natural for use #1.

Admin fits fine for us, this is just the broader context for PIH-Rwanda.

1 Like
66

Please review and merge this, @jayasanka

67

Please review and merge this, @jayasanka