Radmin‎ > ‎Events‎ > ‎

Approving Events in Your Pending Queue

The Pending Queue contains new events which require approval before being made live on the site. Because hundreds of new events enter most metros' Pending Queues on a daily basis, it's important to work through the queue efficiently, while still maintaining a meticulous attention to detail. Generally, you'll want to spend about 6 minutes for each page of 50 events - though you'll want to spend more time with events on the first page, and less time with events on subsequent pages.

The events in the pending queue are sorted in order of popularity by default. This means that, in general, the most popular and buzzworthy shows will be at the very top of the queue. In addition to working through the entire queue every day (if possible), you'll also want to check back every few hours throughout your work day to make sure that any new high-profile shows are approved as quickly as possible so you can get band notification emails out the door in a timely manner.

Band Notification Emails

Band Notification Emails are automatically sent every three hours to any followers of artists who have been added to new or existing shows. The emails look like this...

... and are often the first way that most fans find out about their favorite artists' new shows. 

Each user will receive a maximum of one email every three hours, containing all the artists who have been 'announced' since the last round of emails was sent three hours prior.

These emails can be triggered by approving events in the pending queue, approving events in the duplicates queue, making updates to events in the duplicates queue, manually creating events, and manually adding artists to existing events.

It's important to be mindful of the functionality around Band Notification Emails when working in your queues.

Working In The Pending Queue

When working in the pending queue, you'll want to start at the top of the queue and work your way downward. For each event, you'll want to focus on the following:
  • Title and Presented By
    • All events have Titles. If you're unsure how to format the title of your event, we recommend listing the artists performing at the event, with headliners first and commas separating them (eg "Band 1, Band 2, Band 3 & More").
    • Not all events have Presented By info. You only need to add this if it's appropriate.
    • Both the Title and Presented By fields are in-line editable. If you want to modify them, click into them to start editing.
      • Pro tip for Mac users: Hit control + enter to quickly save after editing any in-line text in the queues.
    • When checking Titles and Presented By info in the pending queue, you'll want to fix any typos, misspellings or other incorrect information that you find. Feel free to also clean up less-desirable presentations - but you should always be mindful of how many eyes will see the particular event you're working on. You want to only spend 6 minutes per 50 events in the queue - so you'll want to move quickly and not get caught up nitpicking details on events that very few people will see.
  • Artists
    • A majority of your time in the pending queue will be spent editing artist records, as these are the hardest things for our scrapers to nail automatically.
    • Hit 'X' on artists to delete them from events, add artists that are missing using the 'Add Band' field, and drag artists around to ensure that they're listed in the proper order with the headliner first. 
    • A reminder that once an event is approved, show announcement emails will fire off for the artists tagged on it. So, you want to make sure that the right artists are tagged - and you want to be extra careful not to include incorrect (and/or deceased) artists who may have thousands of followers on shows they're not actually playing. The Rolling Stones should not be tagged for the concert of a Rolling Stones tribute band, Jimi Hendrix should never be tagged, etc. Original bands should NEVER be tagged on shows for cover bands.
  • Category
    • Your events will be brought into the pending queue with a default category. Click on the category name to change it when appropriate.
    • Pro Tip: Not only can you assign a default category to each of your scrapers, but you can also request that certain categories be assigned to certain events within those scrapers based on their titles or information. Feel free to request a fix on any relevant scrapers for this.

  • Ticket Info
    • Depending on your site design, only a dozen or so of your ticket info's characters may display on the front end event pages. The rest may be truncated. So, you'll want to list your ticket info as concisely as possible (especially on pages people will actually see) - while also being cognizant not to spend too much time editing ticket info on less popular events.

  • Voting
    • Often, you'll find an event in the pending queue that you want to add to a user list once approved, such as Top Events or Just Announced. To do this directly in the pending queue, you can click the cogwheel to the right of the event, select 'Voting' and then enter the user to whom you'd like to add this event.

Approving Events:

You can click the checkbox next to any single event to approve it and make it live on your site...

... but, in general, you should avoid approving events individually and, instead, work your way through all of the events on the page, make any desired edits to them and then hit 'Approve All' to approve the page's events en masse:

'Approving All' will save you time compared to approving the events one-at-a-time. That action is best left for the occasions when you briefly check the pending queue for any just-announced high-profile events and want to approve them as quickly as possible before moving on to other work.

Deleting Events:

You may occasionally need to delete events from the pending queue. Examples of events you'll want to delete are:
  • When a venue is closed for a private event but still has a listing for that event
  • When a venue that generally brings in desirable events pulls in off-brand or irrelevant ones
  • When an event is a duplicate of an existing event
To delete an event, hit the trashcan to the right of the event:

If you find yourself deleting a notable amount of events from a particular scraper, then that is a sign that the scraper should be edited in some way. Please reach out to Support if you would like any guidance about what to do in such a situation.

Please also note that, once an event is deleted, it will never come back into the queues, even if updates have been made to it on the site you're scraping.

Editing Events:

You may occasionally want to edit the more particular details of an event (or, for instance, its images) before it is approved - especially if you know the show will trigger a lot of buzz and/or advertising dollars. This should be reserved for special situations only, otherwise it will take far too long to complete your queue.

Hold command + N, and then click the pencil to edit an event in a new window before it's approved:

Pro Tip: There will also be times that you'll also want to bookmark an event for future use - and the Radmin URL for an event will not change once it's approved from the pending queue, so you can click the edit pencil to open an event in a new tab for future use, approve it and come back to it later.

Filtering Events:

You can filter the pending queue by any event title, venue, start date or scraper name.

This can be helpful, for instance, when you need to quickly approve a certain client's events or a particular event. It can also be helpful if an erroneous scraper brought unwanted editions of events in the queue. If that happens, you should:
  • Pause the scraper and request a fix (via the Scraper's page within Radmin -> Events -> Scrapers)
  • Filter by the scraper name / venue time to reveal the erroneous events
  • Click the 'Flush Page' button to remove those events from the queue
  • Once our script writers have fixed the scraper, it will run again and bring the proper events back in the queues.

Deleting vs. Flushing:

Deleting is permanent. Flushing is temporary. When an event is deleted from the pending queue, it will never return (make sure your interns know this). Flushing events removes them from your queues - but has no lasting impact on the event records. Any events that you flush from the queues will be brought back in the next time their scraper runs (assuming they're still future events and not dupes).

Scraper Logic

Here is an outline of how scrapers decide where to put incoming events that they find on URLs they're scraping:

New Events.png

This workflow should inform your logic as you work through the queues. One important thing to note is that since scrapers do not check incoming events against pending events, untended pending queues can cause issues with duplicate events. It's best to bring your pending queue down to 0 as frequently as you can, to prevent duplicates from entering the queue -- and also for your own sanity.

Now that you're a master of the Pending Queue, it's time to learn all about Working in Your Duplicates Queue.