JSON datasets should not show up in the Explore page “Add a column” modal

zarino commented 7 months ago

There are a number of datasets which show up in the "Add a column" modal, but result in a column of JSON gibberish if you add them, eg:

constituency_christian_aid_groups
rspb_reserves
constituency_wi_groups
tcc_open_letter_signatories
constituency_foe_groups
power_postcodes

Aside: Generally, "Number of…" datasets work fine, but confusingly, some datasets without "Number of…" at the start of their name also work fine (eg: tearfund_churches). We should standardise this. Either drop "Number of…" from all the datasets, or make sure they’ve all got it.

zarino commented 7 months ago

Related: #490, which is about making these JSON-type datasets filterable – but we probably still don’t want them to show up as columns of raw JSON via the “Add a column” feature.

zarino commented 4 months ago

I was reminded of this bug when @juliacush accidentally triggered this, in a demo last week. Very easy to do. I expect it looks broken to anyone who doesn’t recognise JSON.

mysociety / local-intelligence-hub

JSON datasets should not show up in the Explore page “Add a column” modal #496