• The Assumption: By showing a warning to the user in the UI, we could nudge them to not continue the query on the WDQS but to read about other more appropriate data access methods
• Experiment Design:
  • • Use the classification for simple/small queries from https://phabricator.wikimedia.org/T386342 to trigger a warning in the frontend
    • When a user writes a simple query in the UI and clicks the play button, a pop-up/overlay shows up informing the user that such queries should be run outside the WDQS with two CTA (call-to-action) buttons, "Run anyway" vs "Dev portal button" [wording and design TBD]. The pop-up/overlay cannot be ignored unless one of the two buttons are chosen.
  • Not affecting the API or the simple query examples in the WDQS

• Key Metrics :
  • Baselines (all needed)
    • No. of visitors to WDQS UI per day
    • No. of queries to the WDQS UI per day excluding the examples
    • No. of simple queries per day in the last month
  • Success/Impact
    • • Query is not run after warning is shown -“Run anyway” [final wording TBD] tracking (to be added!)
      • # of simple queries decreased in the UI
      • Clicks on the link/button on the pop-up = Views to the dev portal immediately after the query service page
    • How often the warning is triggered by the frontend

In addition, we'll keep an eye our for qualitative feedback on the various channels (telegram, talk pages, email lists)