-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider extracting exporter to Python package #184
Labels
Comments
Re: exporting data from Kingfisher Process, it's only needed by the data registry, so I think it's fine to leave the logic here. We can extract it later if we find a use case. viz #314 #292 and #304, we're not sure if we'll forever have Kingfisher Process as the source of exports. So, it is also premature to extract this logic. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
e.g. Kingfisher Export ("Exports OCDS data as JSON dumps from Kingfisher Process").
It can implement the two workers (export, wipe) and otherwise offer functions to interact with the filesystem. At a later date, we can consider pre-computed Spoonbill exports (at least CSV for large datasets) and other export formats (like SQLite, pg_dump, etc.).
The text was updated successfully, but these errors were encountered: