Content Translation supports the definition of campaigns in order to identify how many people reach the tool coming from a specific event, communication campaign, or external tool. In addition, the link generated for a campaign enables the Content Translation beta feature automatically in order to provide a simpler and more direct access to participants in the campaign. People responsible for the campaign can get a convenient link to share with participants, and obtain information about the impact of their event/tool/etc...
Campaigns are defined in a configuration file inside Content Translation. Once the campaign is defined, constructing the special link to Content Translation for the campaign just require to include the campaign=<campaign-name> parameter in the URL. For example, Gap Finder, an external tool to find articles to translate, redirects users to Content Translation including campaign=article-recommender-1 in the url (example).
As it is available now, this mechanism does not provide communities with much visibility of the content that was created as a result of such campaigns. It would be desirable to extend the campaign configuration process to allow content created by the campaign to be marked as such.
Proposed solution
Extend the campaign configuration to include:
- Optional edit tag to use. Specifying an edit tag to be added to the published articles that were started as part of this campaign. This is an optional parameter, not all campaigns need to track the published edits.
- Default Machine Translation service to use. Specifying the preferred translation service to be used can be useful for events that are associated with the activities of a particular engine (e.g., a hackathon organized by Apertium). This should be optional, affect the default MT only for the articles started in the context of the campaign, do not prevent users from switching to a different service, and not to fail if such service is not available for the user selected language pair.
Additional remarks:
- If this is not trivial to support for both version 1 and version 2 of Content Translation, it is perfectly ok to support it only on version 2, and force the use of such version regardless of the user current default when accessing the tool from a campaign that includes the above parameters.
- We may want to consider how this can be generalized so that other tools such as Visual Editor could benefit from these campaigns (i.e., a user accessing VE with a campaign parameter gets the edit tag automatically added too).
(More details to be discussed and detailed)
Related ticket: T123529: Add support for hashtags (URL parameter -> edit summary) in VisualEditor, WikiEditor, and ?? other editors
