| Time | Item | Who | Notes |
|---|
| Identify challenges and risks making such a big decision | | - How do we capture the complexity of the Ed-Fi Dashboards? Rosh Dhanawade wished she knew a lot more about the realities of customization when started down the dashboard path. There are good things there and it serves a good purpose but how do we convey the complexity and when it is a good fit vs. not
- Glynn Ligon (Unlicensed) can think of a few examples of where features were started to be implemented but abandoned, features that were added and very well adopted and features that are on the to-do list that may or may not work.
- Can we start by listing out what features we've seen work/not work and see if that guides the discussion
- Rosh Dhanawade and Itzel Torres what do we mean by features? Is it a use case or a specific technical detail or configuration of the specific dashboards? Clearly one of the biggest challenges is that when speaking of dashboards people have different levels of understanding and details in mind.
- Kimiko Rife when thinking/talking about dashboards I talk about buckets and where does what people need fall.
- Does it go in the ODS/data bucket, meaning the data is not in the ODS yet but we need to load it or find it.
- Is it a UI/Rendering/Showing bucket, we have the data but I want to see it differently or add it to the dashboards.
- We want to establish a common language so that when we talk about features, stories, use cases it is clear what we mean.
- Can we develop a guide/visual graphic that walks potential dashboard users/implementer to better understand the complexity of the customization/extensions once you move away from core implementations.
|
| How will we collaborate | | - We will share our thoughts via email, cc Itzel Torresso she can capture and document discussions and keep track of relevant information.
- We will agree to collaborate by putting initial ideas on paper and polishing by review/discussion with members of this group.
- As we see gaps in understanding or a missing view point, we will reach out to the community to validate assumptions before we proceed.
|
| How do we communicate to the rest of the community | Itzel Torres | - As we make progress, we will share with the community via blog/newlsetter post as a way to keep everyone in the loop in a more storytelling way. For detailed discussions and meeting notes they can dig into Tech Docs space.
|
| Next Steps |
| - Glynn Ligon (Unlicensed) will send out initial notes, feature list notes for feedback.
- Next week working session, we will dig into common language understanding of describing features and the technical architecture of the Ed-Fi Dashboards.
|