Page MenuHomePhabricator

Collections discovery investigation
Closed, ResolvedPublic4 Estimated Story PointsSpike

Description

This investigation aims to find ways to provide more visibility to collections, guided by the following hypothesis:

If we highlight collections of articles that include vital topics in relevant parts of the translation workflow, more translations of vital contents will be created.

In team meetings we talked about what is the definition of vital topics in this context, and while this is an on-going conversation, for the purpose of this investigation we concluded vital topic is whatever the community decides is vital. This introduces the concept of a 'local featured collection'.

Local featured collection

Currently collections are only shown under the more filters dialog, at least one or two clicks away. The idea of a featured collection is essentially a collection directly specified by the community, a signal that we can use to surface and highlight collections accordingly.

For this investigation I explored the CommunityConfiguration extension to provide a channel for admin users to set an existing collection as featured. Using this extension we can leverage its built-in safety measures to introduce a community configuration in the ContentTranslation code [1]. For demo purposes, I used this config to surface featured collections in what's probably a low hanging fruit opportunity: directly in the ContentTranslation dashboard, under the filter suggestions header [2]. I left it as displayed but unselected, if we wanted to be more aggressive it could be selected already.

The exploration code is available at https://gerrit.wikimedia.org/r/c/mediawiki/extensions/ContentTranslation/+/1193885

Other opportunities to consider exploring are: surfacing them while using the search feature, reordering/highlighting them in the suggestions dialog, etc.

Effort

  • Community engagement may be best for testing and understanding how they could make best use of this.
  • UI/UX exploration is needed to understand where to best surface and highlight the collections with vital content.

Impact

  • Collections will gain a higher priority in the translation workflow, which means and increased priority gained by the community that creates the collections
  • The desired final impact of an improved collection discovery is to translate more vital content and therefore increase the size of existing vital content

Measurements

  • We can track the number of translations started from the new highlighted collection suggestions. This can be compared with the number of translations started from current placement of collections (suggestion filters dialog)

[1]

image.png (1×2 px, 333 KB)
image.png (1×2 px, 235 KB)

[2]

image.png (1×2 px, 455 KB)

Event Timeline

eamedina updated the task description. (Show Details)
SBisson subscribed.

I think this is resolved. The patch showing how CommunityConfiguration can be used remains available as a promising way to configure important collections by a community.

Nikerabbit set the point value for this task to 4.

Change #1193885 had a related patch set uploaded (by Eamedina; author: Eamedina):

[mediawiki/extensions/ContentTranslation@master] Collection discovery investigation

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

Change #1193885 abandoned by Eamedina:

[mediawiki/extensions/ContentTranslation@master] Collection discovery investigation

Reason:

spike completed

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

The link between gerrit and phab was missing, just added it for documenting purpose. Patch has been abandoned.