Duplicates
If two participants have exactly the same first and last name, fepli shows them as a possible duplicate. The team decides whether it is the same person.
The page has no entry of its own in the sidebar. Under Participants you open it with “{count} possible duplicates →” next to the title, with the flag Duplicate? of a row or from the participant's side panel. Global admins who look after several instances see duplicates only in the instance of their own account.
Deciding
For every pair, you select one of three decisions.
- Both records stay.
- The pair leaves the list.
- Both records stay.
- Their registrations count together, also for the registration limit.
- One stays and takes over registrations, notes and consents.
- The other is deleted. Cannot be undone.
| Action | When | Effect |
|---|---|---|
| Not a duplicate | Different people | The pair leaves the list. Both records remain independent. |
| Keep both | The same person, both records should stay | The pair moves to the group Keep both. Both records' registrations count together, also for the registration limit. The admin panel shows them together. |
| Merge | The same person, created twice | One record stays and takes over everything. The other is deleted. Cannot be undone (Merging). |
| Element | Meaning |
|---|---|
| Pair | 2 records with exactly the same name. A table compares date of birth, email address, account and registrations and states same, different or not comparable for each. |
| Groups | To check, newest pairs first, and Keep both |
| Search | Finds names in both groups. |
| Check again | Appears for pairs in Keep both and brings them back to To check. |
After Not a duplicate and Keep both, the message offers Undo.
Merging
Merge opens a dialog. Under Which record stays? you select which of the two stays. Each choice shows account, number of registrations, date of birth and email address.
The record that stays takes over from the other:
- registrations, notes and consents
- status changes, friend codes, access codes and objections
- the entries in the log
The other record is deleted with date of birth, contact details and the link to the account. For the record that stays, the log notes Records merged.
| Case | What the dialog shows |
|---|---|
| Both are registered for the same offer | A red message. Merge is missing. If it is the same person, select Keep both. |
| The processing of one record is restricted | A red message. Merge is missing until the restriction is lifted under Data subject rights. |
| The records belong to different accounts | A yellow note: the account that stays then also sees the other's registrations and consents. You confirm with a tick that both accounts belong to the same family. |
| Both in the same account, or one without an account | No note. Merge takes effect at once. |
Restricted processing means: the person has asked that their data not be used further for the time being (Art. 18 GDPR).
With encrypted names
For an instance with encryption, the server does not know the names (Encrypted data). Then the team's browser finds the pairs.
- When someone from the team opens the page in an unlocked browser, the browser compares every record it can open. It tells the server only which records form a pair.
- Two records form a pair if the names are equal and the dates of birth do not differ. Upper and lower case, accents, ß and hyphens do not count. If one side has no date of birth, it counts as equal.
- fepli stores new pairs as open. If the browser no longer finds a stored pair, for example after a name was corrected, fepli deletes it. Not a duplicate and Keep both remain.
- The browser decrypts names, dates of birth and accounts on the page. same or different for the date of birth appears as soon as both values are decrypted.
- Until the next comparison, the number next to the title of the list and Duplicate? show the pairs stored last.
- The search filters in the browser. What you search for does not reach the server.
- Check again stores the pair as open again.
Messages
| Message | Meaning |
|---|---|
| “{name}: marked as two different people.” | You selected Not a duplicate. |
| “{name}: both records stay.” | You selected Keep both. |
| “Both records are registered for {offers}. …” | Merging is not possible. If it is the same person, select Keep both. |
| “Processing of {names} is restricted (Art. 18 GDPR). …” | Lift the restriction under Data subject rights to merge. |
| “Please confirm that both accounts belong to the same family.” | The tick for different accounts is missing. |
| “Comparing names …” | The browser is comparing encrypted names. |
| “The names could not be compared.” | The comparison in the browser failed. |