People and person codes
One person, many records: person codes, duplicates and merging.
The same human being turns up several times. A stage manager might be crew for a supplier, on the guestlist for Saturday, and driving on with a parking pass — three records, one person.
EventNexus links those records to a single identity and gives that identity a person code: a short, unique identifier with a scannable QR behind it.
What a person code is for
The code answers a question no list can: what does this individual actually hold?
- At the collection desk, it finds someone instantly without spelling a surname
- At catering, it resolves what they are entitled to eat today
- On their own ticket, it is the fallback when a QR will not scan
Every signed-in user can see their own code in their profile menu, with a copy button and a link to their passes. The code page at /p/ followed by the code lists every live pass that person holds for the event.
A person's code does not change between events. Someone who worked last year keeps the same identity this year.
Returning people
When someone is added to a new edition of your festival with an email address that was confirmed at a previous one, they are recognised as the same person automatically. Their history follows them; nothing has to be re-entered.
Anything less certain is not guessed at. Instead it goes to a review queue.
Duplicates
Accreditation › Duplicates lists pairs that look like the same person. Reasons include an unconfirmed email match, a shared role address, the same person across two companies, or a straight duplicate inside one event.
Each pair is shown side by side. You pick which record to keep, and the other is merged into it — no history is lost, and every merge can be undone.
Some pairs should not be merged. Shared role addresses — info@, bookings@, production@ — are flagged precisely because several real people use them. Those are the ones to dismiss rather than merge.
Privacy
Nothing in this ever reveals that an email address exists at another festival. A duplicate is only ever surfaced to a team that already has access to both records.
Where to go next
- Passes and QR scanning — the credentials a person holds
- Collection on site — finding people by code at the desk