Domo Group Help: Navigating to Score Components in Domo
Hey Domo Group!
I'm working with an Excel file that tracks student proficiency. It has a single column for "Overall Proficiency Level" and separate columns for individual subject proficiency levels (Listening, Speaking, Reading, Writing, Comprehension, Oral, and Literacy).
Here's the challenge: I want to easily navigate from the overall score to see the breakdown for each subject. Ideally, I'd like to be able to filter or drill down to specific overall proficiency levels and then view the corresponding subject proficiency levels.
Has anyone encountered this scenario before?
I'm looking to explore any efficient navigation methods,
Any tips or suggestions from the Domo community would be greatly appreciated!
Note: The data resides in a single Excel file.
Thanks in advance for your insights!
Best Answer
-
There are a lot of approaches you could use to do this. I can't tell what level of aggregation you'd like, so if all you're looking for is just overall proficiency by subject, you could create a handful of summary number cards that averages each of those.
If you want the ability to summarize by different levels of aggregation (average by demographic group, by school, by school level, etc.), then an approach I like it using two variables, one that controls the metric to be displayed and the other to control the aggregation level. With those two controls, I really only need a couple cards, and the user can still slice the data in dozens of different ways. Your metric variable could allow them to switch between "overall" and different "subject level" performance measures.
Here's a few snips of that approach, showing the different options.
Please 💡/💖/👍/😊 this post if you read it and found it helpful.
Please accept the answer if it solved your problem.
2
Answers
-
I used to work for a large school district. I've done that type of thing before using SQL. I'd just apply the same strategies to creating it in Domo. My initial attempt would be to create a Magic ETL because of the speed of execution. When you talk about schools and "levels", you can get into all kinds categories and breakdowns. You have grades in current courses. Six weeks or semesters. Assessments and state tests. It seems never ending.
The thumbnail below is one of the reports I created. Each row was an individual student. The filters at the top were to limit the dataset to school year, school, grade, classroom, etc. Each of the colored areas represented the main subject area test scores. Such as Math, English Reading, English Writing, Science, etc. My report showed the semesters, and allowed educators to look at a current point in time and compare to past years. In that way, a counselor could focus on a specific student to evaluate how they were doing. Or, the principal could focus in on a teacher to see how that teacher's students were doing prior to their handling the student or after. Or the super could evaluate the school.
The rainbow area you see were the demographic identifiers. Race, gender, etc.That's a lot to digest in one dataflow. So I suspect I would break it up in gathering classroom scores, assessment score, test scores. Then join everything back together on the identifiers such as year, student id, school, etc.
It also included checkboxes for…geez I can't recall the term….campus college readiness? Did the student have JROTC, did they check off right whatever to show they were prepared.
In this way, I could give access to the teachers to see only their students, the principals to see only their school (past or present students), super to see everyone.** Was this post helpful? Click Agree or Like below. **
** Did this solve your problem? Accept it as a solution! **0 -
Thank you for your response. Im looking for how to help the end user navigate to the different score components.
0 -
Review the different ways in Domo to drill down from summary to detail records. Including how pfilters work. But you have to have the level of detail you want in a dataset. There are numerous forum conversions and documentation pages.
** Was this post helpful? Click Agree or Like below. **
** Did this solve your problem? Accept it as a solution! **0 -
There are a lot of approaches you could use to do this. I can't tell what level of aggregation you'd like, so if all you're looking for is just overall proficiency by subject, you could create a handful of summary number cards that averages each of those.
If you want the ability to summarize by different levels of aggregation (average by demographic group, by school, by school level, etc.), then an approach I like it using two variables, one that controls the metric to be displayed and the other to control the aggregation level. With those two controls, I really only need a couple cards, and the user can still slice the data in dozens of different ways. Your metric variable could allow them to switch between "overall" and different "subject level" performance measures.
Here's a few snips of that approach, showing the different options.
Please 💡/💖/👍/😊 this post if you read it and found it helpful.
Please accept the answer if it solved your problem.
2 -
Thanks for the solution that i think is my best approach. Ideally, the measuring drop down (from the example) could be the column headings i need (Listening, Speaking, Reading, etc.) to select the metrics. The grouped by drop down could be the entity and grade, similar to filters?
Is there a video showing how this is accomplished?
0 -
I would start with the documentation for variables, which does have a video:
The variables controls are similar to filters, in that they enable users to manipulate how the data is presented. They are different in that they are not changing which rows of data are being presented, but in my example, in what columns are being presented, or how the data is grouped. (You could tie variables or BeastModes that do affect which rows are displayed, but I'm not doing that in the example above).
The approach to this would be to create two variables, let's say
Metric Variable
andGrouping Variable
. The options for theMetrics Variable
would be Listening, Speaking, Reading. The options for theGrouping Variable
would Entity and Grade.Then you also need two BeastModes that use those variables. Let's call them
Metric
andGroup
.Metric
could be:CASE
WHEN
Metric Variable
= 'Listening' thenListening
WHEN
Metric Variable
= 'Reading' thenReading
WHEN
Metric Variable
= 'Speaking' thenSpeaking
END
Group
could beCASE
WHEN
Grouping Variable
= 'Entity' thenEntity
when
Grouping Variable
= 'Grade' thenGrade
END
Note that in the BeastModes, you are checking if the variable is equal to a string (single quotes), and if so, then returning a column (back ticks).
Use
Metric
as your value axis andGroup
as your category axis.Please 💡/💖/👍/😊 this post if you read it and found it helpful.
Please accept the answer if it solved your problem.
1 -
THANK YOU SO MUCH!!! I appreciate your help.
0
Categories
- All Categories
- 1.8K Product Ideas
- 1.8K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 300 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 2.9K Transform
- 100 SQL DataFlows
- 620 Datasets
- 2.2K Magic ETL
- 3.9K Visualize
- 2.5K Charting
- 742 Beast Mode
- 58 App Studio
- 41 Variables
- 686 Automate
- 176 Apps
- 453 APIs & Domo Developer
- 47 Workflows
- 10 DomoAI
- 36 Predict
- 15 Jupyter Workspaces
- 21 R & Python Tiles
- 395 Distribute
- 113 Domo Everywhere
- 276 Scheduled Reports
- 6 Software Integrations
- 124 Manage
- 121 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 10 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 108 Community Announcements
- 4.8K Archive