⭐ functionality to automate the ONA data update... #12
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
prep_geonames had bug where geocolumns were not matching uniquely so there were issues where geonames without any issues were flagged as with issue.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @DemevengDerrick
In this pull request, I managed to implement the
update_ona_datafunction to automate downloading, updating, and logging of data from specified ONA form IDs. This function utilizes the last_edited column along with log dates to identify new data that requires downloading. Please test this out on your end. Bear in mind thatupdate_ona_datahandles many form IDs, similar to get_multi_ona_data, which I will need to revisit at some point.