Page MenuHomePhabricator

intro text for expectation setting
Closed, ResolvedPublic1 Estimated Story Points

Assigned To
Authored By
Lydia_Pintscher
Oct 12 2020, 7:42 AM
Referenced Files
F33918418: image.png
Nov 18 2020, 4:04 PM
F33918412: image.png
Nov 18 2020, 4:03 PM
F33918404: image.png
Nov 18 2020, 4:03 PM
F33918406: image.png
Nov 18 2020, 4:03 PM
F33918415: image.png
Nov 18 2020, 4:03 PM

Description

As a new query builder user I want to understand the context I am in and understand the limitations of the query builder in order to not be disappointed if it can't yet do what I expect it to do.

Problem:
The query builder is currently very limited and it will never be able to cover the full power of SPARQL. We need to be transparent about this.
Currently we have a placeholder text that needs to be replaced.

New text:
The Wikidata Query Builder provides a visual interface for building a simple Wikidata query. It is ideal for users with little or no experience in SPARQL, the powerful query language. The Query Builder doesn't offer SPARQL's full functionality, but you can always open your query in the Query Service, where you can view, edit or expand it via the link above the results.

Acceptance criteria:

  • placeholder text is replaced with proper intro text

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript
Lydia_Pintscher renamed this task from intro text for expectation setting to (MS 1) intro text for expectation setting.Oct 20 2020, 10:06 AM

This looks good as a text for the "final" Query Builder. My proposal (cf Mattermost channel) was for the SQB test system on https://query-builder-test.toolforge.org/ : "Welcome to the test system of the Simple Query Builder. Please note that this is a work in progress, not all features are included, and it can sometimes be broken. Feedback is welcome here." Thanks for adding it :)

Lydia_Pintscher renamed this task from (MS 1) intro text for expectation setting to intro text for expectation setting.Nov 11 2020, 1:46 PM

needs a decision on how to proceed.

  1. final text replaces temporary text at the end of the last milestone
  2. final text and temporary text are both displayed during the testing phase
  3. final text replaces temporary text immediately, but we add the feedback link
  4. final text replaces temporary text immediately and temporary text gets displayed as an alert message during the testing phase

Just one thing: We really should link to the source code somewhere (I thought it's even part of ToS of Toolforge but I was wrong)

Just one thing: We really should link to the source code somewhere (I thought it's even part of ToS of Toolforge but I was wrong)

can you explain why we should be linking to the source code directly from the Query Builder page, instead of from a help page for example?

Just one thing: We really should link to the source code somewhere (I thought it's even part of ToS of Toolforge but I was wrong)

can you explain why we should be linking to the source code directly from the Query Builder page, instead of from a help page for example?

It is de facto standard for services in the cloud:

image.png (61×686 px, 35 KB)

image.png (75×576 px, 14 KB)

image.png (68×606 px, 7 KB)

image.png (52×356 px, 6 KB)

image.png (76×513 px, 9 KB)

(I have many more)

So I expect users would look in the page to find the source code

needs a decision on how to proceed.

  1. final text replaces temporary text at the end of the last milestone
  2. final text and temporary text are both displayed during the testing phase
  3. final text replaces temporary text immediately, but we add the feedback link
  4. final text replaces temporary text immediately and temporary text gets displayed as an alert message during the testing phase

Let's go with 3.