Script to re prepare submissions for export #599
Closed
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.
Issue
Some submissions have not been flagged for export even though they should have, see here for the details. We need to feed them again to the
prepare-submissions-for-export-service
for them to be flagged properly, once the fix is merged.Proposed solution
This is a half-automated solution. Here are the steps.
Copy them in the
form-data-uris.txt
file. I already put in there the URIs found on the current state of the database, but new URIs might land in this wrong state too before we deploy it.Run the script:
./run.sh <ip-of-prepare-submissions-for-export-container
Expected result
You can use the following query to monitor the submissions with multiple decision types that have not been flagged:
During my tests locally, on a copy of prod data, I went from 264 un-flagged submissions to 30 after running the script.
Relates to
prepare-submissions-for-export-service
here