Look more into howThe way properties vsand values are defined and entered into the interface,into the existing query service is not clear to beginner users. how qualifiers are defined and entered etc.Also would be useful to be able to define qualifiers as part of the query.
During our federated wikibases workshop we discussed a few other existing examples for query builder interfaces.
- WMFlabs query builder https://tools.wmflabs.org/wd-query-builder/
- tag based system based on example from http://sparql-playground.nextprot.org/, Possible other examples of interfaces to consider include WMFlabs query builder or a madlib style tag based system based on example from http://sparql-playground.nextprot.org/ or thewhich provides more context to example queries, but the ability to also modify examples via a madlib style filling in of values into the examples can also be helpf
- blocky sparql searches as exemplified in http://www.infomus.org/Events/proceedings/CHItaly2015/CHItaly2015/p86-bottoni.pdf
There maybe other good UI references out there.. this is just the beginning point for a discussion to improve the UX of the "query helper" towards more of a "query builder". - also this example from the cultural heritage context which works towards a more "natural language" approach to the query building process https://public.researchspace.org/resource/Start