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

Import Twitter ToS history #148

Open
clementbiron opened this issue Jul 20, 2021 · 4 comments
Open

Import Twitter ToS history #148

clementbiron opened this issue Jul 20, 2021 · 4 comments

Comments

@clementbiron
Copy link
Member

Twitter publishes its previous ToS https://twitter.com/fr/tos/previous and it will be interesting to add them in the OTA history.

@MattiSG MattiSG changed the title Twitter - add previous ToS Import Twitter ToS history Jan 8, 2022
@MattiSG
Copy link
Member

MattiSG commented Jan 27, 2022

Hopefully this will be done in April through our upcoming partnership with PGA 😃

@ckatzenbach
Copy link

Yes, once we are fully on board, we are happy to contribute this. Our Twitter archive goes back to 2006 (www.pga.hiig.de – full archive soon at https://github.com/PlatformGovernanceArchive). I think it makes sense that we get first fully on board with regard to the current OTA scraping process, then try to understand its peculiarities and also compare the results with our PGA method, before we bulk import our data. I'd like to understand the differences and commonalities first, otherwise the dataset might get a bit "dirty".

@MattiSG
Copy link
Member

MattiSG commented Apr 24, 2023

This issue is not related to the engine, but to specific collections.
Currently, the PGA collection is the reference for Twitter. Moving to PGA, whose team can then decide to handle however they see fit 🙂

@MattiSG MattiSG transferred this issue from OpenTermsArchive/engine Apr 24, 2023
@ckatzenbach
Copy link

Thanks, Matti – yes. We still need to find a way to merge history PGA data with the current and ongoing PGA/OTA data. We do not want to just merge without having a proper idea of the side /output effects of the two different collections methods. This is on our roadmap for this year.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants