Page MenuHomePhabricator

[BUG] Recommendation endpoint pulls out articles that do not have description in source wiki
Open, HighPublicBUG REPORT

Description

https://www.wikidata.org/api/rest_v1/data/recommendation/description/translation/from/en/to/es

The endpoint should find articles that have a description from the source wiki (e.g. en wiki in this example)

But somehow the page/summary will not give us the article's description when requesting the same title from the output that recommendation/description/translation gives us.

For example:

In enwiki:

Title: Centralized traffic control will have a description signalling block system that we can find in the recommendation/description/translation endpoint

descriptions":{
    "en":{
            "language":"en",
            "value":"signalling block system"
    }
}

From the /page/summary endpoint, it does not show the description:
https://en.wikipedia.org/api/rest_v1/page/summary/Centralized_traffic_control

Event Timeline

Restricted Application changed the subtype of this task from "Task" to "Bug Report". · View Herald TranscriptOct 21 2020, 9:37 PM
Restricted Application added a subscriber: Aklapper. · View Herald Transcript
cooltey triaged this task as High priority.Oct 21 2020, 9:37 PM
cooltey updated the task description. (Show Details)

@cooltey: Assuming this task is about the Recommendation-API code project, hence adding that project tag so other people who don't know or don't care about team tags can also find this task when searching via projects. Please set appropriate project tags when possible. Thanks!

As a 10% time effort I'd like to revive the CirrusSearch-based description and caption recommendations (T220282) and see if that approach can be made viable. I think it was a much more robust solution overall, and we now have a random sort order in CirrusSearch (which was implemented shortly after the CirrusSearch approach was rejected by the Android team before) which turns out to actually be pretty fast. T220282#5377975

This would also have the happy side effect of allowing us to sunset and remove the Recommendation-API -based endpoints, which have been a problem for us because Recommendation-API has seen some lapses in technical stewardship.

What @Mholloway described is a feasible effort we could work on, but I believe that this ticket needs to be discussed on a product management level. How do you want to approach that? cc/ @JTannerWMF and @MattCleinman

Aklapper added a subscriber: MSantos.

@MSantos: Removing task assignee as this open task has been assigned for more than two years - See the email sent to task assignee on Feburary 22nd, 2023.
Please assign this task to yourself again if you still realistically [plan to] work on this task - it would be welcome! :)
If this task has been resolved in the meantime, or should not be worked on by anybody ("declined"), please update its task status via "Add Action… 🡒 Change Status".
Also see https://www.mediawiki.org/wiki/Bug_management/Assignee_cleanup for tips how to best manage your individual work in Phabricator. Thanks!