Surface downloadable CSVs

In order to make our CSVs more accessible, let’s:

• Update the preamble of the data page:

We update all the data each day between 4pm and 5pm EDT. You can also get the dataset as a spreadsheet, CSV files, and an API.

• Add a link to /data/download in the preamble of the /api page

Create a new page at /data/download that:

• Shows similar information about caveats that we use in the API page.
• Lists US and state download links
• Displays all the fields, along with descriptions, like we do with the API page

Page structure:

• US history
  • Download all history data
  • Field descriptions (collapsible)
• State history
  • Download State data
    • Field descriptions (collapsible)
    • Download all states (/api/v1/states/daily.csv)
    • Download single state (collapsible)
      • List all state files (/api/v1/states/[state]/daily.csv)

Discussion:

I think the API explorer could still work well for downloadable CSV files, but I could be wrong. FYI all the fields and descriptions are defined by the API and automagically available, so reformatting the display is easy.

We could provide a list of all the downloadable CSV files by state (the daily history). I don’t think linking off to the api/v1/states/[state]/[date].csv files makes sense.

[kissane]

Maaaaaybe

We update all the data each day between 4pm and 5pm EDT. You can also see the dataset as a spreadsheet, download CSV files for everything we track, or use an API.

[kevee]

All the fields in there are automatically updated when our API changes.