Radmin‎ > ‎Events‎ > ‎

Working in Your Duplicates Queue

Note: this article assumes that you've read this article on the pending queue. If you haven't read that yet, DO it!

The duplicates queue contains events that match the same date and venue as existing events. For this reason, the queue will contain:
  • updates to existing events (such as when a new band is added to an existing bill)
  • new events (for venues that have multiple shows in a given day)
  • unwanted editions of existing events
When you load up the dupe queue, you will see a stream of new events matched to existing duplicates:

The events in red are the new editions of events. They are not yet live on your site, and nothing will happen with them until you do something with them.

Below each new event in red will be at least one existing event. This will be the event (or events) that are already live on the site and take place on the same date and at the same venue as the new event.

Working Through Your Queue

Your goal as the master of the duplicates queue is to decide to do with each new event. Here are your options, in order of likelihood.

1. You can update an existing event to have the same presented by, title, bands, category, venue, date, time and ticket info as the new event.

That's what you'll want to do in the case of this Ladyhawke show, since all the details of the event are the same except for the fact that the new event has an updated band list.

When you hit this 'update' button, the existing event will inherit the presented by, title, bands, category, venue, date, time and ticket info of the new event. You're welcome to edit this information on the new event before you hit the button, similarly to the way you fix up events in the pending queue before you make them live on the site.

"Wait!" you may say. "What if I approve an event from the pending queue, give it a really nice new description and cover photo, then add a giveaway and a featured event to it? Will updating that event from the dupes delete that work?" And the answer is no! The only information that will change when updating an event from the duplicates queue are the presented by, title, bands, category, venue, date, time and ticket info - plus the idea of being 'sold out'. All of the other information will remain the same.

2. You can approve the new event and leave the original events unchanged.

Sometimes, the new event will be a completely different event than the event(s) below it. This happens frequently with venues that present multiple shows on a given date. Again, you're encouraged to check (and edit) the presented by, title, band, category and ticket info before approving the new event, in the same way you would do in the pending queue. You can also click on the COG wheel to the right of the event to 'vote' on it for a user such as Top Events or Just Announced.

Approving the new event in this circumstance will have no effect on the existing event(s).

3. You can delete the new event.

Sometimes you won't want the new event at all. The new event may be a private event, a show you already know has been cancelled, or an unwanted edition of an existing event. If this is the case, click the trash icon next to the new event to delete it.

Please note that there are also trash icons next to the existing events - and while you can delete them directly from the duplicates queue, we highly recommend that you instead open Radmin -> Events -> Search in a new tab and merge the unwanted event into another existing event. The reason for this is to prevent broken links / pages not found on your site.

Filtering The Dupes (Highly Recommended)

While working in the dupes queue, you may often find it best to filter the dupes by 'Venue' and tackle one venue's dupes at a time. The reasons for this are three-fold:
  • You will often need to cross-reference a venue's website (or ticketing site) while you process their dupes
  • Processing one venue's worth of dupes at a time allows you to tackle the dupes in bite-sized chunks
  • This will allow you to give extra attention to the venues whose events will receive the most traffic

You may also want to apply a similar logic when filtering by date to quickly check events happening today, this weekend, or throughout the week ahead.

We recommend having a repeating Asana task set for every day that determines which duplicates you'll tackle.

If you have any questions with the duplicates queue or would like to see any additional items addressed in this article, please reach out to Support!