Page MenuHomePhabricator

As a product manager, I'd like to know who is using our search API and how they're using it, so I can figure out how to prioritise tasks. (part 2)
Closed, ResolvedPublic8 Estimated Story Points

Description

Repeat the analysis done for our opensearch API in T99013 for our other APIs.

T100468 needs to be finished first.

  • Stakeholder: Product Manager, Search & Discovery
  • Benefit: Knowing usage information will enable Product Manager to make prioritisation decisions around API
  • Estimate: To be added by Data Analyst from Search & Discovery

Event Timeline

Deskana raised the priority of this task from to Medium.
Deskana updated the task description. (Show Details)
Deskana subscribed.

@Spage, I think this exercise might be useful to know which #dev.wikimedia.org documentation for 3rd party developers we want to prioritize.

Deskana set Security to None.
Deskana updated the task description. (Show Details)

This is related to T107211, but is distinct; T107211 is focussed specifically focussed on zero results, whereas this is more general.

Do we have any idea about who is doing these API queries, for which products, for which purposes?

Short answer, not really; as the report makes clear this is intentionally a high-level summary. We will dig into the sources more if and when we begin reforming how we expect users to format incoming search requests.

If you are interested in generalised reports on this sort of issue I would recommend putting a Phabricator card in the Research team's backlog.