Skip to content

Research reporting options for ARGUS analytics #45

@BytecodeBrewer

Description

@BytecodeBrewer

Goal

Research how ARGUS should generate analytics reports from market data, metrics and charts.

Why

ARGUS should not only display analytics in a dashboard, but also create reusable reports that summarize data, metrics and insights.

Before implementing reporting, the project should compare practical reporting options and decide what fits the current architecture.

Research questions

  • What should an ARGUS report contain?
    • selected currency pair or asset
    • date range
    • data source
    • cumulative return
    • strongest / weakest movement
    • rolling volatility
    • charts
    • short interpretation notes
  • Which report formats are useful?
    • Markdown
    • HTML
    • PDF
    • CSV/Excel export
    • Power BI connection later
  • Which tools or frameworks fit best?
    • Markdown templates
    • Jinja2
    • pandas export
    • Plotly/NiceGUI export options
    • Power BI / external BI later
  • Should reports be generated from live data, stored data or both?
  • How could reports later connect to AI-assisted summaries?

Acceptance criteria

  • Report content structure is proposed
  • At least three report/export formats are compared
  • Recommended first report format is selected
  • Required data inputs are documented
  • Relationship to NiceGUI and database/storage is explained
  • Future Power BI or AI-summary options are discussed
  • No production report implementation is required in this ticket

Note

Priority: Should

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions