Change Details

To minimally support creating a prototype for the apps Edit Actions Queue we need a simple endpoint which provide a title (or list of titles?) of articles which need a Wikidata description. IOW, if the wiki allows Wikidata description find articles that don't have descriptions. A few ideas: * Wikidata SPARQL query * A variant of the random/title endpoint that actually favors the ones without a description (better discards any articles with a description during the scoring process). Note: This endpoint should be performant enough so that this can be invoked per end user request (and is not cached) to avoid running into issues where multiple users get the same list of pages that need descriptions, which would lead to multiple users starting adding descriptions for the same article, which could be frustrating.

To minimally support creating a prototype for the apps Edit Actions Queue we need a simple endpoint which provide a title (or list of titles?) of articles which need a Wikidata description. IOW, if the wiki allows Wikidata description find articles that don't have descriptions. A few ideas: * Wikidata SPARQL query * A variant of the random/title endpoint that actually favors the ones without a description (better: discards any articles with a description during the scoring process). Note: This endpoint should be performant enough so that this can be invoked per end user request (and is not cached) to avoid running into issues where multiple users get the same list of pages that need descriptions, which would lead to multiple users starting adding descriptions for the same article, which could be frustrating.

To minimally support creating a prototype for the apps Edit Actions Queue we need a simple endpoint which provide a title (or list of titles?) of articles which need a Wikidata description. IOW, if the wiki allows Wikidata description find articles that don't have descriptions. A few ideas: * Wikidata SPARQL query * A variant of the random/title endpoint that actually favors the ones without a description (better: discards any articles with a description during the scoring process). Note: This endpoint should be performant enough so that this can be invoked per end user request (and is not cached) to avoid running into issues where multiple users get the same list of pages that need descriptions, which would lead to multiple users starting adding descriptions for the same article, which could be frustrating.