Page MenuHomePhabricator

Section-Level Images: details dialog copy for suggestion "kind" values
Closed, ResolvedPublic

Description

User story & summary:

As a new editor, I want to understand why I'm receiving a particular image suggestion so that I can make an informed decision about whether the image should be added to an article

Background & research:

Growth should get all image suggestion types and rank by descending confidence score: in this way, intersection-based suggestions will likely come first, then other suggestions will be consumed later.

Example details dialog for "section alignment" suggestion:

AI-image-suggest-panel.png (323×488 px, 51 KB)

Cassandra kind column values:AKASingular CopyPlural copy
istype-section-topics'section topics-based suggestionImage is linked to a Wikidata item that may be relevant to this article section: [Wikidata_item_1].Image is linked to Wikidata items that may be relevant to this article section: [Wikidata_item_1], [Wikidata_item_2].
'istype-section-alignment'section alignment- based suggestionImage is used in an equivalent article section in $Lang1 Wikipedia.* If used in the same langage in 2 other languages: "Image is used in an equivalent article section in $Lang1 and $Lang2 Wikipedia." * If found in three other Wikipedias: "Image is used in an equivalent article section in $Lang1, $Lang2, and 1 other Wikipedia." * If found in four or more other Wikipedias: "Image is used in an equivalent article section in $Lang1, $Lang2, and $(TotalOther - 2) other Wikipedias.
'istype-section-alignment','istype-section-topics'intersection-based suggestionImage is used in an equivalent article section in $Lang1 Wikipedia, and relates to a Wikidata item that may be relevant to this article section: [Wikidata_item_1]Image is used in an equivalent article section in $Lang1 Wikipedia and $(TotalOther - 1) more languages, and relates to a Wikidata item that may be relevant to this article section: [Wikidata_item_1]
Design:

Figma designs

Acceptance Criteria:

Given [preconditions]
When [user action]
Then [outcome resulting from actions taken in the when clause]
All tasks should also meet the Growth Team’s task completion definition.

(If you find that you are adding several “Given/When/Then” statements, that is a potential indicator that the task should be split up into multiple tasks or parent task / subtasks.)

Event Timeline

Thank you @KStoller-WMF! What do you think of changing the first one to this?:

Image is linked to a Wikidata item that may be relevant to this article section.

On the third one, is "topic" related to Wikidata items? If so, I'd use Wikidata item there too.

Everything else sounds good to me. Feel free to disagree and/or chime in with thoughts!

@JFernandez-WMF OK, I've updated to use "Wikidata" rather than topic.

I recognize that the language is still a little awkward and we may need more plural version support, so anyone should feel free to suggest further improvements!

Can we adapt/reuse the same strings used in the article level images, where it is directly related?

This copy doc gives more context as to how the specific copy was determind in each case.

@RHo - Julieta and I reviewed the previous language, but it seemed like we couldn't reuse those strings exactly without losing some meaning. All of the strings I've suggested mention "section", which I think it important to highlight.
But if you or any engineers have suggestions for simplifying the copy or better adapting the strings we used previously, I'm in support of that. I mainly just want to be sure we are as specific as possible so newcomers know why the image is suggested.

@RHo - Julieta and I reviewed the previous language, but it seemed like we couldn't reuse those strings exactly without losing some meaning. All of the strings I've suggested mention "section", which I think it important to highlight.
But if you or any engineers have suggestions for simplifying the copy or better adapting the strings we used previously, I'm in support of that. I mainly just want to be sure we are as specific as possible so newcomers know why the image is suggested.

No worries, I posted these for reference for where the same terminology should be reused, eg referring to "Wikidata item", and I'd suggest "same article" is easier to understand than "equivalent article". Other more general content writing guidelines can be found here

The Add Image text does not start with "Image is" (it's things like Used in the same article in 2 other languages: Arabic and French.) so I'll adjust these to match. Please tell me if you'd prefer it the other way around.

Image is used in an equivalent article section in $Lang1 Wikipedia. is fine. For topic-based matches though, the API doesn't return what the topic is, so I'll cut off that part.

kostajh changed the task status from Open to In Progress.Jun 12 2023, 12:24 PM

Change 929341 had a related patch set uploaded (by Gergő Tisza; author: Gergő Tisza):

[mediawiki/extensions/GrowthExperiments@master] Section images: Display section-image specfic reasons

https://gerrit.wikimedia.org/r/929341

Change 929341 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] Section images: Display section-image specific reasons

https://gerrit.wikimedia.org/r/929341

Etonkovidova subscribed.

Checked on cswiki wmf.13 - the section-level specific phrasing is in place:

Screen Shot 2023-06-28 at 6.02.02 PM.png (910×1 px, 361 KB)
Screen Shot 2023-06-28 at 5.59.33 PM.png (814×1 px, 282 KB)