Venue Data Sourcing

Connecting with uTour

The primary origin source for venue data into Auth Data stems from uTour. To maintain a connection between Auth Data and uTour, each uTour venue is mapped to its corresponding entity in Auth Data. The DMO will add the venue's uTour Id(s) as an ExternalRecord for each Auth Data venue.

If no entry exists in uTour, the DMO will create a venue in uTour and then link it to the Auth Data instance of that venue.

The DMO team will populate venues into Auth Data using a manually curated list of venue originating from uTour. Venues on this list are validated and de-duped through a case-by-case investigation of each proposed venue.

Mapping Venues

External Records

It will not be uncommon for multiple instances of the same venue to exist within uTour, either under the same name or variations of the name. The DMO will link each of these instances as an ExternalRecord to the single Auth Data instance. In general, the uTour id with the largest event count will be set as the primary ExternalRecord venue while the other(s) will be set as additional, non-primary ExternalRecords.

Names

Relevant names used by duplicate venues in uTour are entered as alias names for the primary venue in Auth Data.

Merging uTour entities

The DMO will merge duplicate records within uTour subject only to user review and approval.

Linking Parent venues and Subvenues

Each uTour id can only be associated to one venue within Auth Data. Venue entries in uTour that specifically reference a child venue are linked with the subvenue in Auth Data. Entries that only name a parent venue (without reference to a subvenue name) are mapped to parent venue in Auth Data.

When migrating venues, the DMO will create corresponding parent and child entities within uTour if none currently exist.

Linking Events

Events, such as music festivals, are often listed as venues within uTour. In cases where an event is uniquely held at a venue, such as how Worthy Farm only hosts the Glastonbury Festival, the uTour event will be linked to correct venue (“Worthy Farm”) in Auth Data.

Venue Request Form

Frontline teams can request modifications and additions to Auth Data venues using ServiceNow tickets through the Venue Request Form.

Ambiguous Requests

The DMO will make a best effort to identify and validate venue information submitted through the venue request form. For requests where the venue can not be confidently identified, it is the policy of the DMO to first reach out to the requesting party either through email or slack for more information before closing a ticket without action.

Under no case will the DMO log partial, incomplete, or unvalidated information into Auth Data related to requests with ambiguous or nebulous information.

Third-Party Data Sourcing

Primary Sources

Primary sources include all sources originating directly from the venue. These include all publicly available information such as information posted within venue websites, technical specification documents, in press releases or social media accounts. If specific attributes about the venue are unavailable (such as venue capacity) in primary sources, alternate secondary sources can be used.

Venue technical specifications

The DMO stores all available documents with technical specifications for venues within the team Box folder.

Secondary Sources

The DMO may use secondary sources such as those listed below to augment data sourced from primary sources.

• Wikipedia
• Eventective
• Perplexity
  • Note that with any AI source, data should not be used without verifying cited sources

Data derived from secondary sources must be confirmed by the DMO across at least 2 sites.

If an attribute about a venue can not be sourced for either primary or secondary sources, the DMO will omit data if no such source exists.