Main Page
Jump to navigation
Jump to search
SPARQL
Wikidata Query Service/User Manual
Reconciliation service for Wikibase (KB example)
https://github.com/KBNLresearch/OpenRefine-Wikibase
- Recon service o.b.v. Docker: https://openrefine-wikibase.readthedocs.io/en/latest/install.html
- Example config file: https://github.com/KBNLresearch/OpenRefine-Wikibase/blob/main/config.py
- Configuration of OpenRefine: add URLs of recon service and manifest to OpenRefine
- Example manifest: https://github.com/KBNLresearch/OpenRefine-Wikibase/blob/main/kb-test-wikibase-cloud-manifest.json
Wikibase.cloud
Wikibase.cloud documenation Wikibase.cloud project updates
Tasks
Reconciliation service for Wikibase (KB example)
https://github.com/KBNLresearch/OpenRefine-Wikibase
- Recon service o.b.v. Docker: https://openrefine-wikibase.readthedocs.io/en/latest/install.html
- Example config file: https://github.com/KBNLresearch/OpenRefine-Wikibase/blob/main/config.py
- Configuration of OpenRefine: add URLs of recon service and manifest to OpenRefine
- Example manifest: https://github.com/KBNLresearch/OpenRefine-Wikibase/blob/main/kb-test-wikibase-cloud-manifest.json
Sorted properties
ISSUE: When adding statements to a Q-item such as Theun de Vries, by default the statements are (and remain) displayed in the same order as you originally added them. This is different from Wikidata, where in the corresponding Wikidata item about Theun de Vries the statements are displayed in a custom, fixed order, with "Instance of" and "Image" on top, and a list of external identifiers at the bottom of the page, irrespective of the exacty order these statements were originally added to this Wikidata item.
- SOLUTION: This issue was solved by adding the page MediaWiki:Wikibase-SortedProperties to the Wikibase, in which the custom order of statements can be specified. This is the same as in Wikidata, see MediaWiki:Wikibase-SortedProperties and the manual on Wikidata. Please note that the required page cache purging needed for this functionality to kick in can be actively triggered via Special:Purge.