You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 28, 2023. It is now read-only.
Load the Temperate database dump into a live local database.
Query for OrganizationActions that were NOT imported as part of "the Missy dataset". If you find any, export them as a CSV.
Context
"The Missy dataset" is a dataset of climate change adaptation actions taken by various cities that was compiled by a woman named Missy as part of her doctoral research. We imported the dataset into Temperate to provide cities with helpful examples. If cities using Temperate stored their own adaptation actions in Temperate, that could be a helpful dataset that we or one of our partners might want to make available publicly. However, we don't know whether this actually happened, so the first step is to look through the database and see if any actions exist that aren't part of the Missy dataset. If any do, then we should dump them as a CSV and let @smthome know.
I don't exactly know what it is, but there is a marker in the database that allows us to differentiate whether organizations (and therefore their associated actions) were imported from the Missy dataset, because there used to be a filter in the Django admin that allowed filtering by that criterion.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Context
"The Missy dataset" is a dataset of climate change adaptation actions taken by various cities that was compiled by a woman named Missy as part of her doctoral research. We imported the dataset into Temperate to provide cities with helpful examples. If cities using Temperate stored their own adaptation actions in Temperate, that could be a helpful dataset that we or one of our partners might want to make available publicly. However, we don't know whether this actually happened, so the first step is to look through the database and see if any actions exist that aren't part of the Missy dataset. If any do, then we should dump them as a CSV and let @smthome know.
I don't exactly know what it is, but there is a marker in the database that allows us to differentiate whether organizations (and therefore their associated actions) were imported from the Missy dataset, because there used to be a filter in the Django admin that allowed filtering by that criterion.
The text was updated successfully, but these errors were encountered: