-
Notifications
You must be signed in to change notification settings - Fork 79
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
Write script to update all data for Scribe updates #95
Comments
The script written to complete this issue should also produce a .txt/.json file that has the differences in data for the most recent run. The structure of this file should allow it to be directly pasted into CHANGELOG.md, thus turning the data update process into two steps (run script and paste results). |
It looks like WikidataIntegrator would be an appropriate tool to complete the SPARQL query portion of this task, as shown in this Jupyter notebook. |
Current progress is a script that can find the necessary queries, picks the first to run, formats it for use with WikidataIntegrator, runs the query and prints the results of the query. Next steps:
|
Labels for properties do not appear to be being queried with WikidataIntegrator, but this can be checked for in formatting scripts where the string will start with Example: |
The final step is to allow the individual formatting files to detect when they're being ran by Scribe-Data/data/update_data.py by checking the Python paths via |
Note that the result of this issue is now scribe_data/load/update_data.py, and all referenced files have been moved to Scribe-Data. |
Currently updating Scribe's data for a release is time consuming, with this process being one that could easily be converted to a single Python script. The goal of this issue is to make a script that uses a Wikidata tool to run all of the
query*.sparql
scripts in the Scribe-Data/data directory, and then runs all theformat_*.py
scripts to put the new information into the respectiveData
directories for the keyboards. The script would be placed in the root of Scribe-Data/data.Another positive is that this feature will provide many good first issues for the future where someone can update the data and thus be integrated into the contribution process.
The text was updated successfully, but these errors were encountered: