Sparql query service approach

[harikrishnatp]

Contributor checklist

• This pull request is on a separate branch and not the main branch
• I have tested my code with the pytest command as directed in the testing section of the contributing guide

---

Description

Sparql service implementation with the universal query being https://w.wiki/FesH. and fallback query being https://w.wiki/FesZ. Also got rid of the duplicate query generation which was the main starting point of the issue.

Related issue

• Query generation is including the same query form in more than one query #617

[github-actions]

Thank you for the pull request! 💙

The Scribe-Data team will do our best to address your contribution as soon as we can. If you're not already a member of our public Matrix community, please consider joining! We'd suggest that you use the Element client as well as Element X for a mobile app, and definitely join the General and Data rooms once you're in. Also consider attending our bi-weekly Saturday dev syncs. It'd be great to meet you 😊

Note

Scribe uses Conventional Comments in reviews to make sure that communication is as clear as possible.

[github-actions]

Maintainer Checklist

The following is a checklist for maintainers to make sure this process goes as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :)

• The linting and formatting workflow within the PR checks do not indicate new errors in the files changed

• The CHANGELOG has been updated with a description of the changes for the upcoming release and the corresponding issue (if necessary)

[axif0]

Removing this file will effect on the /wikipedia/process_wiki.py

[axif0]

Is it ok to skip translations data-type ? By querying translations script none of them works for now.

[harikrishnatp]

Is it ok to skip translations data-type ? By querying translations script none of them works for now.

I thought about it too, some other data types are also like that. At first i didnt query them, just the main ones we used to query. But when i ran pytest, it showed that i needed to have those data types in the file structure. Thats why I decided to query them as well.

[andrewtavis]

note: We can add translations into the data types in the list file to make sure that the test passes without needing to have a query for it :)

[harikrishnatp]

data_type_metadata.json was also responsible for generation of all those data types. should be good to merge right ?

[axif0]

[Note: Priority Low] Can we consider by ignoring the changes in language_data_extraction ?

As the github action runs, then it creates PR, and then we can marge the sparql files ?

[andrewtavis]

I agree with @axif0 that we should just do the files for the workflow in this one. We can consider the current output files, I'll then revert their changes before merge, and then the three of us can investigate a PR from the run of the workflow 😊

[harikrishnatp]

The pre-commit hooks did its stuff but language_data_extraction is the one from the upstream. So, I'm assuming everything should be good ?

[andrewtavis]

I'll take a look later tonight and bring it in, @harikrishnatp! Assuming as well that it's fine 😊

[andrewtavis]

praise: Really amazing work here, @harikrishnatp! Really is so great that we've come to this point with Scribe-Data! Can't wait to see how the queries look once we run the workflow 😊 Thanks as well for your support in reviewing, @axif0, and thank you both of the countless calls and syncs to get here! We'll see how it works, but from here we should be good to tweak the process as needed :)

[andrewtavis]

note: As mentioned above, all changes to queries are formatting from pre-commit.