Skip to content

feat(nimbus): add results page button to export raw results_data json - #17253

Merged
jaredlockhart merged 2 commits into
mainfrom
17252
Sep 16, 2026
Merged

jaredlockhart merged 2 commits into
mainfrom
17252

Conversation

@jaredlockhart

Copy link
Copy Markdown
Collaborator

Because

  • The results page renders a curated view of results_data with no way to get the underlying payload out of the UI.
  • Retrieving the raw analysis JSON currently requires Django admin or database access.

This commit

  • Adds a ResultsExportView serving an experiment's results_data as a JSON file download.
  • Adds an Export JSON button to the results page Overview header.

Fixes #17252

@jaredlockhart

jaredlockhart commented Sep 10, 2026 •

Copy link
Copy Markdown
Collaborator Author

Local render of the new Export JSON button on the results page Overview header, against a dev stack with generated dummy data. The button now uses btn-primary, so it reads as a solid blue action matching the "Create Experiment" button in the page header rather than blending into the surrounding text.

Export JSON button in the results page Overview header

In context on the full results page:

Full results page showing the Export JSON button

The endpoint was also exercised against the running stack:

$ curl -sI http://localhost:7001/nimbus/devolved-multi-tasking-projection/results/export/
HTTP/1.1 200 OK
Content-Type: application/json
Content-Disposition: attachment; filename="devolved-multi-tasking-projection-results.json"

Because

* The results page renders a curated view of results_data with no way to get the underlying payload out of the UI.
* Retrieving the raw analysis JSON currently requires Django admin or database access.

This commit

* Adds a ResultsExportView serving an experiment's results_data as a JSON file download.
* Adds an Export JSON button to the results page Overview header.

Fixes #17252
@mikewilli

mikewilli commented Sep 15, 2026 •

Copy link
Copy Markdown
Contributor

Do you think it might be more useful to provide a query to get the data directly from BigQuery instead of downloading a (potentially large and confusing) JSON payload?

I guess a better question might be: who is this for?

@jaredlockhart

Copy link
Copy Markdown
Collaborator Author

@mikewilli I think we can do both! Here is just for the export, we can find ways to do the BQ side separately.

@jaredlockhart
jaredlockhart added this pull request to the merge queue Sep 16, 2026
Merged via the queue into main with commit 320beec Sep 16, 2026
32 checks passed
@jaredlockhart
jaredlockhart deleted the 17252 branch September 16, 2026 23:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add a button on the results page to export the raw results_data JSON

3 participants