Demo - Add demo CSVs or data for service areas and providers

[ericboucher]

Add a button to load the app with demo data, maybe Fresno and Fresno providers?

The idea is to make it easier for people to debug the primary functionalities of the app. It would also make it easier to share the link externally.

Two options:

1. Have a button to download two csvs that can then be used with the app
2. Have a button to autoload a state with the corresponding data

@viviandien @bcherny thoughts on the above?

[bcherny]

2 thoughts:

1. If users need to control this, a button sounds like a great idea.
2. If it's just for engineers to debug more quickly, we already have the withDemo decorator that you can enable with 1 line of code (link).

[viviandien]

I think having a default CSV would be great for easy onboarding for anybody. For providers, we should use a list of providers/clinics that are publicly available, like on the HRSA website here: https://datawarehouse.hrsa.gov/Data/datadownload.aspx

Particularly, I'm interested in plotting the Health Center Service Delivery and Look-Alike Sites -- which are federally funded service centers that serve low-income, uninsured, and Medicaid beneficiaries.

I tried uploading a CSV of the above mentioned data by filtering out for only CA sites. Then I was prompted with errors about not having NPI or Specialty fields in the CSV. Can we adjust these requirements so that the tools can more flexibly measure adequacy to clinics instead of individual providers?

What do you guys think?

[bcherny]

@viviandien Frontend work to fix uploading Health Center Service Delivery is in https://github.com/bayesimpact/tds-frontend/pull/95. Note that there are a bunch of rows with empty zip code and/or address fields that you'll have to delete first (should we look up missing Zip codes by address?).

Backend seems to have issues with the data too:

[viviandien]

Hm, interesting-- looks like this file has two sets of addresses, but I'm guessing we would want to use the "Site Address" and "Site Postal Code" fields-- which I believe are all filled out. I think mostly this file just needs some cleaning before inputing into the app.

I'm not sure how common it will be to have empty ZIP code fields, so no need to do extra lookups. Seems like the bigger problem down the road will be field management and how to detect the right columns of data to parse/geocode.

[ericboucher]

Geocoding was probably deactivated ;)

[ericboucher]

@viviandien @bcherny alternatively we could switch to simply using an 'address' column, expect it to have all the info and geocode with this instead?

[viviandien]

I don't think this will be an issue when we have our demo files pre-selected.

[viviandien]

this can be closed since pre-loaded datasets is a feature for public launch