Project note, August 2026: This post draws on several production calendar reconciliation runs across Ticketmaster and SeatGeek data.
Two event records share a venue and start time. Are they duplicates?
At a single-stage club, probably. At a casino with several rooms or a festival with several stages, perhaps not. If one provider lists the headliner and another lists the full co-bill, title equality may be less useful than artist relationships.
Calendar deduplication is not a single matching formula. It is a sequence of increasingly editorial decisions.
Exact Matches Are The Easy Tier
Within one provider, identical titles, venue, and time can identify duplicate ticket tiers or accidental repeated records. Those cases can often be removed automatically while preserving one canonical event.
Cross-provider reconciliation is harder. Providers normalize names differently, choose different billing order, and create separate records for packages, openers, or reserved sections.
The calendar groups records so one real-world event can retain links and metadata from multiple providers without displaying duplicate listings.
Names Require Context
One production pass found AJJ in one source and Andrew Jackson Jihad in another. That is a band alias, not two performers.
Another pair described the same Vienna Royal Orchestra performance with effectively identical titles. Co-headlined events required recognizing that two names in a different order still represented one bill.
These are resolvable when artist identity, venue, time, and bill structure agree.
Time Matches Can Manufacture False Pairs
Multi-stage and multi-room venues create Cartesian artifacts. Several legitimate events can share a date and nominal start time at the same complex. A query that pairs every record from provider A with every record from provider B can produce apparent duplicates that never existed.
Ambiguous opener and co-bill records have the opposite problem. They may describe one event, but merging without enough evidence could hide a legitimate separate listing.
Those cases remain unmerged by design.
Preserve The Reasoning Boundary
The reconciliation workflow separates:
- Safe exact duplicates.
- Strong cross-provider matches.
- Alias and co-bill matches requiring contextual evidence.
- Ambiguous candidates requiring human review.
- Known multi-stage artifacts that should be ignored.
The goal is not a zero-candidate report. A small set of documented residuals is healthier than an aggressive merge process that silently destroys real events.
The final calendar is editorial output. Choosing whether two source records describe one public event changes what readers see, which ticket links survive, and how artists are represented. That judgment deserves more than a string-similarity threshold.