Add vendor to OLV Temse #619
Open
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
This vendor has already published erediensten positions, but are not visible in the frontend because the vendor wasn't enabled.
Copy all discarded harvested data back to the temp-inserts graph, such that manual dispatching can be used to "heal" some data that is missing from certain organisations.
Remove the data for a couple specific positions from the organisations graphs.
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.
[DL-6280]
O.L.V. van Temse had duplicate entries for the 2 eredienst positions. One set of entries was entered in Loket, and the other set was harvested, but not correctly dispatched. The data was discarded because VDB was not enabled as a vendor for that bestuurseenheid. Only the first set was therefore shown in the frontend.
These migrations remove the entered-in-Loket entries, enable VDB as a vendor, and copy the discarded data to the graph that is used by the worship-position-dispatcher to restart the dispatching. This time, the vendor is correctly enabled, so the data for Temse should be correctly copied, replacing the removed entries.