Open yuval-harpaz opened 3 years ago
How strange. (And in the update since, 2064 went down to 2063...) Since it's not quite clear what the mistake is, I think I'd rather it leave it unchanged, and faithful to the data presented by the API (assuming this is a mistake in past data, there's really no way to tell when it first happened...). If you are using this data, I think it shouldn't be too hard to manually/semi-automatically patch/edit it on your side, and I would rather not change the "ground truth" in this case. My simplest suggestion would be to throw out the three rows for Match 31st - it seems the problem might be specific to that day, and changes that happened from the 30th to the 31st were then reverted on April 1st.
Please take a look here if there is anything you can do