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

export for QA chatbot on repology DB #2

Open
ghost opened this issue Sep 25, 2020 · 3 comments
Open

export for QA chatbot on repology DB #2

ghost opened this issue Sep 25, 2020 · 3 comments

Comments

@ghost
Copy link

ghost commented Sep 25, 2020

Hi guys,

Hope you are all well !

I want to create a project based on repology database and create a telegram chatbot for searching package or authors with a QA approach. I already did it with the arxiv abstracts (1.7M entries) with a telegram bot.

Refs.

Is it possible to dump the whole repology database with that script ?
Do you think that side project is interesting ?

Nb. It is really simple to do such task with haystack, just have to batch a set of documents json or txt ^^

Cheers,
X

@AMDmi3
Copy link
Member

AMDmi3 commented Sep 25, 2020

telegram chatbot for searching package or authors with a QA approach

Not quite sure what the usecase for this one would be, but why not. I've had distant plans on telegram bot which would inform users on package updates though.

Customized dumps are possible, I just need a desired format. Also note that dumps of whole Repology database are already available (https://dumps.repology.org/), but the format may not be convenient since these are PostgreSQL database dumps.

@ghost
Copy link
Author

ghost commented Sep 25, 2020

We can add this feature as I am building a multi-featured bot. No problem.

Format would be probably json but I wanted to ask your help on that point.
How can do a json dump with this export script ?

@AMDmi3
Copy link
Member

AMDmi3 commented Sep 25, 2020

This script is intended to run on Repology server and regularly produce dumps in consumer-specific format, it needs access to repology SQL database.

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

1 participant