Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document the process of using OData endpoints for data visualisation #1778

Open
spwoodcock opened this issue Sep 11, 2024 · 0 comments
Open
Labels
docs Improvements or additions to documentation effort:low Likely a few hours enhancement New feature or request priority:high Should be addressed as a priority

Comments

@spwoodcock
Copy link
Member

spwoodcock commented Sep 11, 2024

Is your feature request related to a problem? Please describe.

Follow on from #1440

Describe the solution you'd like

  • We probably need some extra docs to help flesh out how this can be achieved (based on actual requirements from a mapping project):
    • Submission history for each enumerator
    • Custom date range filtering of submissions
    • Total submissions vs total number features surveyed
    • Filter submissions by tasks
    • Average submission time per enumerator
    • Expected number of submissions vs actual daily submissions
    • Leaderboard based on submission
  • Yes, PowerBI is proprietary, but it's free to use, very powerful, and user friendly. We need to be realistic and suggest the easiest solution that most end users will connect with. I would propose we document the process for PowerBI first.

Describe alternatives you've considered

  • We should also seriously consider the possibility of running Redash alongside FMTM.
  • Redash (open-source) could have the OData endpoints and authentication pre-loaded, then we can craft a few dashboards that are publicly accessible.
  • This would remove the requirement for table/graph visualisation in FMTM entirely, outsourcing to tools that are specifically made for this purpose.
@spwoodcock spwoodcock added docs Improvements or additions to documentation enhancement New feature or request priority:high Should be addressed as a priority effort:low Likely a few hours labels Sep 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Improvements or additions to documentation effort:low Likely a few hours enhancement New feature or request priority:high Should be addressed as a priority
Projects
Development

No branches or pull requests

1 participant