@Aklapper, I've been reviewing the data with my colleague Santiago Dueñas and we discovered that the name we are showing in some tables is random when you have more than one identity. That means that:
#1 you did it well
#2 data is already aggregated
#3 the information about matma on the left table shows the aggregated data for the two accounts
#4 the information about Bartosz on the right table shows the aggregated data for the two accounts
#5 we have a bug in our queries, that should return the same name always

@Aklapper the data on korma is already updated

@Aklapper not sure about the impact of this changes, I mean, everything work but makes a bit difficult the maintenance of newer versions of the product. In any case, we're starting the dash from scratch so I guess we can live with this for the following months. We hope to have a newer version by FOSDEM/OSCON

@Aklapper your changes were merged. I do think it is a good approach.

I need your github user.

@Luiscanasdiaz: https://github.com/aklapper

Oupss, I made a mistake with the ticket. See my comment at https://phabricator.wikimedia.org/T60585#1734723

Hi @Aklapper, we've just included some changes in our affiliation process. Before starting to match identities we get a JSON file that you can modify in a private repo. After sortinghat (the tool who handles the identities imports this data and get the new people) finishes we export again that file to the private repo. In order to give you access to that file, please send me via email your github user.