Page Comparison

3 months --> December 5 -- March

• Functional enhancements to Superset
  • Visualization
  • • Drilldown
    • Conditional formatting in tables
    • Annotations to bar charts
  Map-specific
  • • Drilldown
    • Pop-up with new indicator
    • Legend
    • Admin ability to upload shapefiles more easily
  Dashboard-level access controls
  • Row-level filtering
  • Exports
  • • Build a new user model specifically for OLMIS to make sure that within Superset the user model is queried instead of having the WHERE clause in the indicator
      • Not sure if WHERE clause is secure
      • Test whether someone with VIEW permissions can hack it and remove the WHERE class
      • Do we need to restrict someone's edit permissions to their current role?
      • Superset is built on FAB --> FAB doc'n talks about extending user model to collect other fields
  • SQL query mutator?
  • • PDF
    • Headers/footers/logos
    • Chart
    • --> modify CSS to dynamically display what dashboard should look like
    • XLSX
    • Add nice logos and headers to CSV
    • Specifically say what the column is supposed to be
    • Add footers (metadata of export)
  Modify CSS
  • • Make a dashboard responsive based on browser's size
    • Create a print layout --> media query --> when you press Print button you can define size of thing you want to print and specifically adjust layout to be formatted appropriately for the page
    • Align look and feel of Superset dashboards with OLMIS style guide
    • Visualization
    • Map-specific
    • Dashboard-level access controls
    • Row-level filtering
    • Exports
    • Modify CSS
  • Stock management reporting in Postgres for 3.6?
  • SSO
    • Improvement around when login occurs
  • Kafka
    • Develop a use case that plays to Kafka's strengths
    • Test it
    • Document it
  • Data pumps
  • Websub (streaming)
  • DHIS2
  • • Debezium - The reporting team uses the API and extracts it. This tool allows us to let the service owner define what gets sent to the reporting stack.
      • Instead of fetching the data, we would be able to receive it as it happens.
      • Can we fit this in with DHIS2?
  • DHIS2
    • Make reports available or post them to DHIS2
  • DevOps
    • Clearly identify DevOps requirements with Peter
    • Reporting stack we've built have been built for developer use, not production use
    • Persist data
    • Figure out how to upgrade each individual service in a way that retains the data and possibly migrates it
      • Biggest risk is upgrading NiFi
      • Kafka
    • NiFi
  autoload
  • • auto load sensitive values
    • Superset
  autoload
  • • auto load custom user roles
    • Superset
  autoload
  • • auto load dashboards + charts
  • Knowledge transfer to SolDevelo and JSI teams
    • In-person meeting
    • Define process for adding new microservices to reporting stack
  • NiFi registry and RBAC
  • Add a "retrieve all" token that returns all requisitions regardless of the user's permissions