Skip to main content

Finding and merging duplicate people

This article describes how to identify, check and merge duplicate people in Converia. It also explains how to handle uncertain cases and how deduplication affects existing data.

Overview

In Converia, multiple person accounts can be created for the same person, for example when people are added by third parties or register themselves more than once. Converia automatically detects these potential duplicates when the email address, given name and family name largely match, with only minor differences, for example due to umlauts, accents or typing errors.

Deduplication allows you to check these person accounts and merge them when they clearly belong to the same person.

Important: Only merge people when you are certain that the records belong to the same person. Separating incorrectly merged people requires considerable effort, and incorrect merges can lead to data protection issues.


Prerequisites

  • Access to Management → Person administration → Deduplication

  • You have access to the affected conferences. Back office users can only merge duplicates from conferences they are authorised to access. Person records from other conferences can only be merged by administrators.


Configuration / Procedure

  1. Open Management → Person administration → Deduplication.

  2. Narrow down the displayed duplicates if needed. You can restrict the view to the current conference, search by person name or filter by roles.

  3. Carefully check the two suggested person records. Converia displays their data side by side.

  4. Note the colour coding in the result column:

    • Fields highlighted in orange contain different values.

    • Fields highlighted in green contain identical values.

  5. Check whether both records actually belong to the same person. Pay particular attention to:

    • the same email address

    • a matching institution or organisation

    • possible confusion between people with common names

  6. Do not merge the people if you have any doubts. In this case, use:

    • Saving without synchronizing if the pair of records should be checked again later

    • Mark as not synchronizable if the pair of records should no longer be treated as duplicates

  7. If the records clearly match, select the appropriate value for the result column for each field highlighted in orange. Use the > button to do this.

  8. Then start deduplication to merge the pair of records.

  9. Before completing the process, check the bookings and papers for both people listed at the bottom of the page. This shows you which links will be retained from both records.


Notes

  • Be particularly careful when email addresses differ, names are similar or common, or institutions differ. In these cases, the records may belong to different people.

  • When a person is created by a third party, Converia assigns an automatically generated username. This consists of the email address and a suffix, usually _g or _x_g. During deduplication, you should prefer usernames chosen by the person over automatically generated ones.

  • When selecting the values to retain:

    • Prefer more recent data based on the registration date.

    • For email addresses, prefer the information provided by the person themselves.

    • Wherever possible, take the complete address data from one side to keep the address consistent.

  • Deduplication creates a new person that combines the functions of both original people, such as bookings and papers. The original person accounts are deleted. Their login credentials remain valid and lead to the new person account.

  • In the activity overview, you can only see details from conferences you are authorised to access.

  • If Converia does not automatically recognise two person records belonging to the same real person, you can also create duplicate pairs manually via Person details → Duplicates → Add duplicate.


FAQs

When should I avoid merging two people?

Do not merge people if you have any doubts about whether both records actually belong to the same person. This applies particularly when email addresses differ, names are common or institutions differ.

What is the difference between Saving without synchronizing and Mark as not synchronizable?

With Saving without synchronizing, the pair of records is retained for a later review and will be suggested again. With Mark as not synchronizable, the pair of records is no longer treated as duplicates.

What happens to bookings, papers and login credentials?

The newly merged person combines the functions of both original people. The original person accounts are deleted. However, existing login credentials remain valid and will lead to the new person account.

Can I merge all duplicates across conferences myself?

No. Back office users can only merge duplicates from conferences they are authorised to access. People from other conferences can only be merged by administrators.

What can I do if a duplicate was not detected automatically?

You can also create duplicate pairs manually via Person details → Duplicates → Add duplicate.

Did this answer your question?