Add effective and end dates for mitigation and policy actions

[william-wash]

To better understand the impact of certain factors with the timeline it would be great to understand when these actions or policies were put in place and also lifted.

I saw a graphic that showed the dates and how shelter in place in SF and CA flattened the curve, wondering how effective other policies might be.

[extrospective]

Ultimately the data on restrictions is not terribly useful to end users if it is only point-in-time.

The timelines are available here: https://www.kff.org/report-section/state-data-and-policy-actions-to-address-coronavirus-sources/, although I have not verified that every entry in the table is supported in this source page.

[tfoldi]

Effective date is something we might able to add to the dataset (from the sources link you shared), but I don't know how can we capture the end dates other than read all the source documents and input them manually.

Is there any use case you can share? To understand what might be sufficient and what value can it bring.

At a minimum, we can store the changes in the table (like what the table at KFF contains at a given day), but I am not sure if that helps.

[apb3471]

I'd be interested in a change log style table for this information. That way changes and when they became effective could be mapped to changes in other activity. Having effective date as part of the key would also allow for multiple changes to be recorded (ex. if a mitigation measure was loosened, then strengthened, then loosened again, that could still be analyzed).

It'd also be useful to have that at the county level, but that would require additional sources (the KFF doc didn't have it). For organizations with members across the country/world, it would be very useful to know what policies apply to their members (when will they be able to travel, what services are available to them, etc.).