I just realised I forgot something in the plan above. We also need to store which service the suggestion came from ("Google Vision" or "Metadata-to-Concept Module")

In T312949#8087024, @Eugene233 wrote:

perhaps better to use integer codes instead? 0=rejected, 1=accepted)

Or possibly a boolean option?

No, the plan was to have a specific mechanism for rejecting a statement although there is nothing in the UI yet for the initial test version. It should be something like a 🚫 icon on the actual suggestion.

Hi all,
Just to let you know this issue is solved :) but I'll need to finish off a patch today. So hopefully a few days to deployment after review is complete.
Many thanks to @Astinson for the suggestions! there were actually a couple of viable methods there, but the easiest one to implement for now is to use the following URL syntax:

That's amazing news! Thanks so much for all the help @abi_, you're a star :)

Hi @Nikerabbit, we've just deployed some changes to the i18n setup, and cleaned up old unused things from the previous setup: T265795: Move client side translations to the server