matomo-org/matomo

Segments | Improve geographical segmentations: Continent & Regions segment are not clear

Open

#11,261 opened on Jan 23, 2017

View on GitHub
 (4 comments) (0 reactions) (0 assignees)PHP (2,847 forks)batch import
Help wantedc: Segmentsc: Usability

Repository metrics

Stars
 (21,513 stars)
PR merge metrics
 (Avg merge 8d 11h) (106 merged PRs in 30d)

Description

At this time the suggestions for geographical segmentations need some hands on to be useable:

  1. CONTINENT at this time some aberrations are show. Imho showing full names of countries is much more userfriendly. e.g. Europe what do you think of working with a list of 7 continents? see https://en.wikipedia.org/wiki/Continent#Number

  2. COUNTRY at this time only country codes are shown. Imho showing full names of countries is much more userfriendly. What do you think of helping users with some additional info to find the right one? ok e.g. Germany (Europe) is pretty easy. but what about e.g. Comoros (Africa)?

  3. REGION looks pretty broken. See also https://github.com/piwik/piwik/issues/7428 What do you think of helping user with some additional info to find the right one? e.g. Niedersachsen (Germany, Europe)

  4. CITY how are cities with same name but within different countries/regiens handled? e.g. Hannover => should one always need to apply a second filter? or should one show city name several times but with an addition following scheme from above like e.g. "Hannover (Niedersachsen, Germany, Europe)"

This is how it looks like in Piwik 3.0.2b1: 2017-01-23_11h23_00 2017-01-23_11h24_39 2017-01-23_11h54_56 2017-01-23_11h25_52

Contributor guide

Research direction
Investigate how Matomo currently retrieves geographical data (continent, country, region, city) in the backend and displays it in the frontend segmentation UI. Focus on understanding the API calls and the rendering logic. Then propose a solution to show full names and hierarchical context (e.g., 'Germany (Europe)') instead of codes.
Tech stack
php
Domain
frontendanalytics
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitPHP
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70