Page MenuHomePhabricator

Rename metrics and reorganize them into more logical groups
Closed, ResolvedPublic

Description

Some metrics have suboptimal names, so we should rename them. We should also switch from underscores to spaces, so we don't have to transform to get nice human-readable names and so we can easily match region names to the forms in canonical_data.countries.

Right now, our metrics are divided into the following groups:

  • Content gap
  • Editing
  • Readers
  • Regional unique devices

The main effect of the grouping is which TSV file the metric lives in; after T359699, the Google spreadsheets will mirror this arrangement, so it will become more important.

Suggested groups:

  • Content (including content gap)
  • Contribution
  • Readership (including regional unique devices)

Details

TitleReferenceAuthorSource BranchDest Branch
Rename metrics and regroup metrics inside metrics folderrepos/movement-insights/movement-metrics!16hghanirenaming_metricsmain
Customize query in GitLab

Event Timeline

nshahquinn-wmf renamed this task from Reorganize metrics into more logical groups to Rename metrics and reorganize them into more logical groups.Apr 19 2024, 1:16 AM
nshahquinn-wmf updated the task description. (Show Details)

The proposed changes are in this spreadsheet.

The new groups are:

  • Content interactions
  • Unique devices
  • Editing
  • Content
  • Content gaps

The groups are not at similar levels (for example, readership metrics are split into content interactions and unique devices) but this is an attempt to bring the groups closer in size.

Made some changes to the proposal based on feedback; waiting until tomorrow for additional feedback before moving on to implementation.

The proposal is basically finished and agreed.

However, there are two remaining things:

  • I just realized that we are probably misusing the term "gender minorities", so I should propose a fix for that.
  • @Hghani will soon be have a MR with some extensive changes to the repo for T359695. To avoid merge conflicts (which will be particularly annoying to fix when they happen in Jupyter notebooks), we should just wait until that's done to implement this.