Open jonobrien opened 7 years ago
We might make some major changes to how tournaments data is saved and served. So currently those endpoints are ignored on purpose, but we definitely will migrate those once we figure out a plan.
AT is approaching, any updates regarding ESI migration/schema?
The work that's going into the new killmail system is intended to be extended to a new tournament recording system as well. That won't be happening before this years AT though.
I will be statically scraping all the old AT data and it will be integrated into ESI as some kind of "historical tournaments" endpoint. Either during or after the tournament this static scrape will be updated to include this years tournament data, as the mechanisms for generating it will be kept around long enough to handle this years tournament.
However, during this years tournament there will be no 30 second delayed data feed to third party developers.
edit 24/05/2018: I just now noticed that I was missing the critical word "no" in this comment headdesk
Update from Bartender,
Me: … any update on that? And will it be updated with matches from this AT?
Bartender: I've got a complete scrape of the old data sitting on my drive, I just need to get around to cleaning it and putting it behind a spec updated in real time no, but probably bulk-rescraped every so often during the process of the tournament
It'd be beneficial to see a dev or legacy endpoint for tournaments to at least be able to test things before matches start, but CCPlease.
Maybe I'm missing something, but I don't see any mention of the tournament data anywhere, release date, or otherwise. Is this CREST data being migrated to ESI as well?