Summary
Instrument Article Guidance topic matching to measure how long each search path takes and how often each path occurs.
Background
When a user types an article title in the Article Guidance search box, the system tries to find a matching Wikidata topic.
When T424641 is implemented, there will be three possible paths:
- Path A: User input → Wikidata search → results returned
- Path C: User input → Wikidata search → no match → MinT translates query → Wikidata search → results returned
- Path D: User input → Wikidata search → no match → MinT translates query → Wikidata search → no results
Goals
Being able to:
- Measure the total time from when the user submits a search to when results (or a no-results message) appear
- Break that time down by which path was taken
- Know how often each path happens
- Know how often users go through the full pipeline and still get no results (Path C)
Data to collect
For each topic matching attempt, log:
- Which path was taken. Example: wikidata_direct, mint_fallback_success, or mint_fallback_no_results [these may need refinement]
- Total time from search to result shown (ms)
- Time spent on the Wikidata request (ms)
- Time spent on the MinT request (ms), only applies to Path B and C
Questions this should answer
- How long does each path typically take?
- What share of searches take Path A vs B vs C?
- What share of searches end with no results at all?
Acceptance criteria
- Existing instrumentation reviewed and gaps identified
- Path and timing data logged per topic matching attempt
- There is a system to query this data
- A query exists showing path breakdown and wait times per wiki
Related
- T424641 (MinT fallback implementation)
