Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Canned Reports][Activity] User friendly columns and address filter #850

Open
Tracked by #1688
mahalakshme opened this issue Jan 13, 2025 · 4 comments
Open
Tracked by #1688
Assignees

Comments

@mahalakshme
Copy link
Contributor

mahalakshme commented Jan 13, 2025

AC:

  1. Lets say, the location hierarchy of the organisation is set as 'Village' -> 'Block' -> 'District'. Then in the Activities dashboard, Village, Block and District filters should get displayed.
  2. When an individual say Rita, is registered in a village say 'V' which is present in Block B and District D. When D is selected in the district filter or when B is selected in the Block filter or when V is selected, the chart should include Rita if registered or enrolled in the applicable program.
  3. When trying to drill thru the records, registrations data should have only, the id, uuid, subject type name(not id),individual uuid, First name, Last name, Middle name, date of birth, gender(not id - by joining with gender table), address columns(not just address id, name of the Village, Block and District, address uuid in the above case - also needed to fulfil the 1st AC), registration_date_time, created_date_time, last_modified_date_time
  4. When trying to drill thru the records, Enrolment data should have only, the id, uuid, program name(not id), individual uuid, first name and last name of individual, enrolment_date_time, Address columns(not just address id), created_date_time and last_modified_date_time

Technical suggestions:

  • The 3rd and 4th AC can be achieved by having the starting data as another SQL query question. Can be achieved like this in UI, should be possible via API as well.
  • To get an idea about address filters check this report screenshot
  • sample screenshot of dashboard: just representative - Until the ACs are implemented the below doesn't matter.
Image
@mahalakshme mahalakshme converted this from a draft issue Jan 13, 2025
@mahalakshme mahalakshme changed the title [Canned Reports] Add address filters and remove observation column [Canned Reports] User friendly columns and filters Jan 13, 2025
@mahalakshme mahalakshme changed the title [Canned Reports] User friendly columns and filters [Canned Reports] User friendly columns and address filter Jan 13, 2025
@mahalakshme mahalakshme moved this from In Analysis to Ready in Avni Product Jan 13, 2025
@mahalakshme mahalakshme changed the title [Canned Reports] User friendly columns and address filter [Canned Reports][Activity] User friendly columns and address filter Jan 13, 2025
@petmongrels petmongrels moved this from Ready to In Progress in Avni Product Jan 14, 2025
@petmongrels petmongrels moved this from In Progress to Ready in Avni Product Jan 14, 2025
@himeshr himeshr self-assigned this Jan 16, 2025
@himeshr himeshr moved this from Ready to In Progress in Avni Product Jan 16, 2025
@mahalakshme
Copy link
Contributor Author

@himeshr Came to know from @ombhardwajj that the below issue is already mostly fixed as part of working on your card. It needs to be pushed for the showcase.

env: staging, org: JNPCT

Image

@ombhardwajj you can confirm on the same.

himeshr added a commit that referenced this issue Jan 21, 2025
himeshr added a commit that referenced this issue Jan 21, 2025
himeshr added a commit that referenced this issue Jan 21, 2025
himeshr added a commit that referenced this issue Jan 21, 2025
@himeshr
Copy link
Contributor

himeshr commented Jan 28, 2025

Partial code changes to consolidate and create a joined table card as per AC Nos. 3 and 4 was done as part of commit
avniproject/avni-server#850 | Introduce code to join and create individual and enrolment data across all types in avni-server canned-850-dev branch.

Pending work from above commit, was to show only select columns as per AC Nos. 3 and 4

@himeshr himeshr moved this from In Progress to Ready in Avni Product Jan 28, 2025
@himeshr himeshr moved this from Ready to Hold in Avni Product Feb 10, 2025
@himeshr himeshr moved this from Hold to In Progress in Avni Product Feb 10, 2025
@himeshr himeshr moved this from In Progress to Hold in Avni Product Feb 11, 2025
@himeshr himeshr moved this from Hold to In Progress in Avni Product Feb 11, 2025
@ombhardwajj
Copy link
Contributor

All ACs have been met except the fact that specfic columns can not be shown when we make pie charts!

@ombhardwajj ombhardwajj moved this from In Progress to Code Review Ready in Avni Product Feb 14, 2025
@mahalakshme
Copy link
Contributor Author

mahalakshme commented Feb 14, 2025

@petmongrels @1t5j0y Himesh and Om suggested, doing joins on Metabase via API is complex and preprocessing it via ETL will make the work a lot simple.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Code Review Ready
Development

No branches or pull requests

4 participants