Develop with a local wikibase docker setup:
- set up a default one using this guide (should be fine with just the minimal install)
- set up a custom GraphIT configuration using the private repo
- insert (test) data
- for development use:
npm start
(uses http-server)- or smth like the vs-code extension "Live Server" (for automatic reload)
- (and start your docker container, of course)
- create a
custom-config.js
file and override the necessary settings, with something like this:
{
"api": {
"sparql": {
"uri": "http://localhost:8834/proxy/wdqs/bigdata/namespace/wdq/sparql"
},
"wikibase": {
"uri": "http://localhost:80/w/api.php"
}
}
}
- NOTE: can cause issues with CORS. So you can try adding
$wgCrossSiteAJAXdomains = ['*', "optional:your-local-url"];
to theLocalSettings.php
of your local wikibase docker setup (don't push this change!) - NOTE: with
npm start
it can happen that changes to the code don't show up when running the server. Deleting your cache forlocalhost
might help.
- handled in the private GraphIT docker repo
- but basically:
- create a separate folder for the gui
- add all files, as seen in the official build-folder of the frontend (you don't need the README)
- customize the Dockerfile of the wikibase-release-pipeline
- use the same images they use (see the variables.env)
- git clone the fork instead of the official repo (see the Dockerfile)
- don't checkout that commit (after the git clone)
- inject that image into the docker-compose.yaml, by setting the build option to the gui folder instead of using the pre build image
- adjust as necessary
- for further reference, see the wikibase-release-pipeline
- for the future:
- handle deployment here
- build docker image (see above) and push to registry
- then simply pull in the docker-compose.yaml of the GraphIT docker instance
Added support for colors for multiple columns
?node_w_rgb1 ?rgb1 ?node_w_rgb2 ?rgb2
BIND("F68C13" as ?rgb1)
in Query body
Added support for shapes for multiple columns
- works like
?rgb
- uses visjs shapes: ellipse, circle, database, box, text, circularImage, diamond, dot, star, triangle
BIND("star" as ?shape1)
Added support for setting rgb
and shape
via comment parameters
- works similar to
#defaultview:Graph
- use outside (or before) the graph-query
- syntax:
#set:<var_name>;rgb=<hex_code>;shape=<visjs_shape>
- example:
#set:item;rgb=F68C13;shape=star
for variable?item
- evtl:
#?item:rgb=F68C13;shape=star
for variable?item
(not implemented) - might cause some issues with unstyled items
- example:
A chart that takes the stacked points of a scatter chart and rearranges them in a circular pattern, to show the otherwise hidden points.
- set as default view using:
#defaultView:SwarmScatterChart
in the SPARQL query or select in the dropdown. - NOTE: to create a new graph, such as this load the file with the code in both index.html and embed.html using the
<script>
-tag
- 🔍-icon in the table-view:
- Now opens a SPARQL query showing the learning path to the item
- only works in the live instance as setting the GraphIT-prefixes is necessary for the query
- ?var and ?varLabel now merges into a single cell if they are both queried
- i.e.:
SELECT ?item ?itemLabel {...}
returns the item's label as hyperlink to the wiki page
- i.e.:
- (currently abandoned) specified columns are turned into working checkboxes to mark items as "interested in" and "completed" from inside a query
see the official information down below
This repository contains the GUI for the Wikidata Query Service.
Please see more details about the service in the User Manual.
Clone git repo, go into created folder and then pull all dependencies via npm package manager.
$ git clone https://gerrit.wikimedia.org/r/wikidata/query/gui
$ cd gui
$ npm install
Alternatively, use npm install
.
npm install wikidata-query-gui
Per default the Wikibase Query Service GUI is configured to be used as a local development test instance. It can be customized by creating a custom-config.json
in the repository's root dir. This file can be used to override any of the default settings obtained from default-config.json
.
Run JSHint, JSCS and QUnit tests.
$ npm test
Start a test server for local debugging. Do not use it in production.
$ npm start
Create a build with bundled and minified files.
$ npm run build
To deploy the GUI, trigger a new build of the deploy repo on Jenkins.
This creates a new open change in the deploy repository: https://gerrit.wikimedia.org/r/q/project:wikidata/query/gui-deploy+status:open
That change will be based on the latest commit in the master branch, and thus it will include all previous commits.
Optionally, you can edit the commit message in the Gerrit UI to include the Bug: Txxxxx
line, to emphasize to which task the change belongs.
You can clone that repository and check out the change locally to test and verify it.
As that repository does not have any CI, you need to manually merge the change. That means, giving +2 to both the Code Review as well as the Verified label, and then clicking the "Submit" button.
The site will be deployed with the next puppet run, which should happen after at most 30 minutes.
See also: https://wikitech.wikimedia.org/wiki/Wikidata_Query_Service#GUI_deployment_general_notes
A CodeMirror based SPARQL editor with code completion (ctrl+space) and tooltips (hover).
var editor = new wikibase.queryService.ui.editor.Editor();
editor.fromTextArea( $( '.editor' )[0] );
See examples/editor.html
.
A dialog that allows browsing of SPARQL examples.
new wikibase.queryService.ui.dialog.QueryExampleDialog( $element, querySamplesApi, callback, previewUrl );
See examples/dialog.html
.
var api = new wikibase.queryService.api.Sparql();
api.query( query ).done( function() {
var json = JSON.parse( api.getResultAsJson() );
} );
See examples/sparql.html
.
JSFiddle.net
Views that allow rendering SPARQL results (see documentation).
var api = new wikibase.queryService.api.Sparql();
api.query( query ).done(function() {
var result = new wikibase.queryService.ui.resultBrowser.CoordinateResultBrowser();
result.setResult( api.getResultRawData() );
result.draw( element );
} );
See examples/result.html
.
JSFiddle.net
Unfortunately there are no releases and the provided code and interfaces are not considered to be stable. Also the dist/ folder contains a build that may not reflect the current code on master branch.