Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tournament related endpoints #296

Open
jonobrien opened this issue Mar 1, 2017 · 5 comments
Open

Tournament related endpoints #296

jonobrien opened this issue Mar 1, 2017 · 5 comments

Comments

@jonobrien
Copy link

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?

@aquarhead aquarhead added the New label Mar 1, 2017
@aquarhead
Copy link

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.

@jonobrien
Copy link
Author

AT is approaching, any updates regarding ESI migration/schema?

@aquarhead aquarhead removed the New label Aug 29, 2017
@aquarhead aquarhead added the TODO label Sep 13, 2017
@aquarhead aquarhead changed the title tournaments? Tournament related endpoints Sep 13, 2017
@ghost
Copy link

ghost commented Apr 25, 2018

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

@CarbonAlabel CarbonAlabel added in-backlog Issue has been accepted, but is considered low priority. and removed TODO labels May 22, 2018
@rawrafox
Copy link
Member

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

@jonobrien
Copy link
Author

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.

@steven-noorbergen steven-noorbergen removed the in-backlog Issue has been accepted, but is considered low priority. label Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants