RVWG 2019-09-03 Meeting notes

Date

Attendees

Goals

  1. Ed-Fi Dashboards Overview:
    1. Version History
    2. Upgrade Paths
    3. Extension Framework
    4. What’s Next
  2. Other Technical Approaches
  3. Current Field Implementations
  4. Questions

Discussion items


TimeItemWhoNotes
Ed-Fi Dashboards Overview
  • Main goal is to give everyone a good overview to enable better discussions during our Summit working session.
  • Quick overview of the history and evolution of the Ed-Fi Dashboards and the extensible plugin architecture
    • v1.x → v1.3: Mainly focused on fixing bugs and generalizing some of the metrics and values from the TX implementation and start to implement extension patterns.
    • v1.4: Plugin architecture enhancements and first community plugin available for core implementations via Exchange (Dashboard Usage Plugin)
    • v2.x: Main goal was to address ETL performance issues, moved from SQL SSIS packages to the C# ETL architecture.
      • Metric Configuration Tool release to make it easier to manage/add metrics and configure assessment metrics.
    • v3.x: Compatibility with the v3.1 ODS model updates. Main updates required where in the ETL readers, minor updates to the Translators and no UI fixes.
  • For the Ed-Fi Dashboards there is no "easy" upgrade path, moving to a major version depends on how extensions were introduced. 
    • Prior to v2.x, it was extremely unlikely that implementations could merge core updates with SSIS packages being complex and hard to compare against core updates. 
    • New ETL architecture makes it easier to review and update only certain components.

Other Technical Approaches
  •  Technical Evaluation team considering a phased approach for growth. The design of each phase would be done with consideration of moving towards the next phase so that the community can start at the level that makes more sense:
    • Analytics Middle tier as the starting point with a set of core de-normalized views to make it easier for most to get started with data visualization quicker.
      • Approach would also benefit current Ed-Fi dashboard implementations as it would provide a middle tier that would hide changes to the ODS model. Potentially making it easier to remain compatible with ODS updates.
    • External Data Mart, next step in the evolution. This data mart could even come in multiple "flavors" for those not using MS SQL. Design would be done such that it could become part of a Data Warehouse in the future
    • Data Warehouse: More robust offering for those that want to start digging into predictive analytics and more complex data analysis.

Current Field Implementations
  • Slide 15 has an initial set of Ed-Fi Dashboard implementations:
    • No implementation to date as been a "core" implementation. All have customized the dashboard and touched all pieces of code (UI, ETL,  new metrics)
    • Earlier implementation costs might change with more cloud/hosting options.
    • Implementations vary widely in the level of customization and the number of districts and students they are serving. This makes it hard to get a quick comparison between them.

Questions
  • Is there a way for districts/users to modify the UI?
    • Not really, configuration in the dashboard is mainly for goals, thresholds and placement on metrics on the hierarchy but the look and feel stays pretty consistent between implementations.
    • There are ways to add branding/logos and update some stylesheets but not super easy to change the UI overall look and feel.

Action items

  •