Closed davidpomerenke closed 7 months ago
Correct, there is no way to access the historical data until we re-ingest it. We are a small team with limited resources and couldn't maintain and keep running the monolithic legacy system any more -- it was breaking under it's own weight. The new system is built around more sustainable assumptions, and we are working to re-ingest historical data. If you have capacity to contribute with code or funds please do.
The new API client is available on PyPI, with updated notebook samples too.
Thank you for explaining – and sorry for my presumptuous question. Now I understand that it was not your active decision to terminate the old API in favour of a new one, but rather the technical problems that made this necessary.
The new Python library is great, and I really appreciate around your work around building a more sustainable system, and generally your work on Media Cloud. ❤️
I cannot contribute with significant funds, but I can point you to the Sovereign Tech Fund, a new program that funds critical open source projects, where you might qualify. They will reopen their applications in spring. Perhaps my team will have capacity to contribute code within an upcoming project where we want to use Media Cloud, in that case I will come back to you.
To be honest, that is really annoying – why switch off the old system before the new one is running? 😥
Any chance that you can switch on v2 of the API again? Or any other way to use MediaCloud until the new version is up?
Currently the new version does technically work for me, but only contains data starting from late 2023. The value of MediaCloud is in its historical data, and I don't see any way to access it now.