Would it be possible to use this space for a short explanation, or would that make it too cluttered? How much copy do we have room for?

A few suggestions, to be edited:

"Write a new short caption."

"Write a short caption in your own words."

"Write a short caption in one or two sentences in your own words."

I think "new" really is enough to indicate that this is supposed to be something else than the description but it doesn't explain why we want a new caption. This really isn't obvious. Do we have a good way of explaining this? Have I missed plans we already have? Without contextualisation, we're basically asking people to write descriptions of files that already have descriptions, but not telling them why this is useful.

@Johan, great input and sounds good to me. Let me work on integrating your suggestions.

I would also love to get your input for the “Suggested edits“ support page, which is, let’s formulate it positively, pretty minimalistic right now. Feel free to edit the hell out of this page ;).

CC: @Charlotte and @alexhollender, who shared similar ideas in T223129.

@schoenbaechler Do you have any preference in mind here for items that do or don't have unstructured captions in the target language, or is that concern specific to the translations endpoint only?

Good question @Mholloway.

I suggest to display items that don’t have an unstructured caption in the target language. The Add image captions task will take care of “porting” unstructured to structured captions.

A related thought: Would it make sense to publish user translations to both structured and unstructured caption in the target language? Or is that a technical and legal nightmare? (CC’ing @Charlotte about the “legal nightmare” part). If this suggestion is too far away from being feasible (Hello reality distortion field), feel free to pretend that you haven’t read it ;).

In T224051#5223505, @schoenbaechler wrote:

Good question @Mholloway.

I suggest to display items that don’t have an unstructured caption in the target language. The Add image captions task will take care of “porting” unstructured to structured captions.

Just to be clear, did you mean to link to this ticket? The second sentence seems to contradict the first, so I'm wondering if you were actually talking about translating image captions in the first.

A related thought: Would it make sense to publish user translations to both structured and unstructured caption in the target language? Or is that a technical and legal nightmare? (CC’ing @Charlotte about the “legal nightmare” part). If this suggestion is too far away from being feasible (Hello reality distortion field), feel free to pretend that you haven’t read it ;).

I don't think SDC supports multiple captions per language.

In T224051#5223733, @Mholloway wrote:

In T224051#5223505, @schoenbaechler wrote:

A related thought: Would it make sense to publish user translations to both structured and unstructured caption in the target language? Or is that a technical and legal nightmare? (CC’ing @Charlotte about the “legal nightmare” part). If this suggestion is too far away from being feasible (Hello reality distortion field), feel free to pretend that you haven’t read it ;).

I don't think SDC supports multiple captions per language.

Ah, now I understand your proposal (after a few more gulps of coffee). ;) Yes, publishing to both structured and unstructured (where no unstructured caption yet exists) seems reasonable in principle. On the technical side, I'm not sure if there's an existing API for setting unstructured image metadata, and I kind of doubt it, but that's something I or one of the Android engineers can look into.

Or is that a technical and legal nightmare?

Yes. Let's please restrict editing to structured data for now.

@Mholloway

Just to be clear, did you mean to link to this ticket? The second sentence seems to contradict the first, so I'm wondering if you were actually talking about translating image captions in the first.

Yes, I’m talking about translating image captions in the first sentence.

(after a few more gulps of coffee). ;)

Very much relatable! 🙃

On the technical side, I'm not sure if there's an existing API for setting unstructured image metadata, and I kind of doubt it, but that's something I or one of the Android engineers can look into.

Sounds good! If you come to the conclusion that it’s feasible but it would lead lots of additional work, we need to talk to @Charlotte about timeline!

In T224051#5223754, @schoenbaechler wrote:

@Mholloway

On the technical side, I'm not sure if there's an existing API for setting unstructured image metadata, and I kind of doubt it, but that's something I or one of the Android engineers can look into.

Sounds good! If you come to the conclusion that it’s feasible but it would lead lots of additional work, we need to talk to @Charlotte about timeline!

I'm not sure what the user benefit would be to doing this, since we will be changing how we display captions in gallery? Agreed with @Dbrant that we should restrict editing to structured data for v1... and to consider editing unstructured data in the future, there will have to be a good argument in favour of doing the considerable work it would probably require. :)

Yeah, to be clear, I don't think it's worth investing time/effort into infrastructure to do that if it doesn't already exist.

@Mholloway

Yeah, to be clear, I don't think it's worth investing time/effort into infrastructure to do that if it doesn't already exist.

+1

@Charlotte

I'm not sure what the user benefit would be to doing this, since we will be changing how we display captions in gallery?

There is no user benefit, we would just complete the Commons database with unstructured descriptions. Kind of kill two birds with one stone. But if the future is structured captions anyway for all WMF products, then we shouldn’t bother.

I would also love to get your input for the “Suggested edits“ support page, which is, let’s formulate it positively, pretty minimalistic right now. Feel free to edit the hell out of this page ;).

As a start, I've suggested a couple of additions that explain what the feed is and does.

A related thought: Would it make sense to publish user translations to both structured and unstructured caption in the target language? Or is that a technical and legal nightmare

It would sort of undermine our argument that we want the user to think of captions in a different way than descriptions (e.g. shorter), wouldn't it?

@Johan

As a start, I've suggested a couple of additions that explain what the feed is and does.

Thanks!

It would sort of undermine our argument that we want the user to think of captions in a different way than descriptions (e.g. shorter), wouldn't it?

Haven’t thought of it that way but you’re absolutely right.

@schoenbaechler I would like to claim and work on this ticket. Is it available now?

Yes @cooltey, please go ahead!

Thanks for the work on this @cooltey. Moving the task to QA signoff as all the issues related to this task are listed in T225635, namely 07), 12), 13), 14), 15), 16), 17), 18), 19), 20), 21), 22), 23), 24), 27).

Looks good to me as an overall test on 2.7.50282-alpha-2019-06-18

Will continue to test in smaller tickets as well.