Research: Reports improvements for v2

[Nkdiaz]

As part of an ongoing conversation between stakeholders, the GTFS Quality Reports that are generated monthly and emailed out to clients will benefit from a restructuring.

Question:

How can we improve the monthly GTFS Quality Reports:

On the backend

• How can we query the data more efficiently?
• Do we need to use the jupyter notebook intermediary step? What could we use instead?
• How can we improve the cumbersome and slow build processes? please see: Current tickets that clarify the build process
• Can we restructure the data so it is easier to query multiple agencies or multiple months?

  On the frontend

• What UI changes can we add that will make the reports more interactive?

  Emails

• Can we track user engagement better with google analytics?
• Can we have more agency specific email content?

  Metabase

• Can we clarify the use of the GTFS Quality reports vs. the Metabase dashboards? Do we direct users to the dashboards in the report body?

  GTFS-RT

• How can we include the GTFS-RT data in the monthly emailed out reports? What data structures need to be in place for this to happen?
• What validation errors/guidelines would be most useful for agencies to see for their GTFS-RT data?

[Nkdiaz]

There are already some tickets with potential updates here:

66 Cumbersome and slow build process

36 Swap in new dimension / fact tables for GTFS Reports

35 Data Quality Reports: feedback on v1

26 Generate reports for feeds with no feed_info