Why this needs a plan
Every large call collects a few submissions that should not be there: an author who submitted twice because the first attempt seemed to fail, the same study sent once as a talk and once as a poster, your own test submissions from before the call opened. These must not reach the reviewers, and they must not receive a decision mail.
Sessions cannot be deleted in run.events, so you do not remove them. You find them and move them into a bucket of their own, where nobody works with them.
Step 1: Prepare a bucket for them
A bucket is a group of sessions with a status, such as In Evaluation, Accepted or Declined.
- Open Content And Speakers and, under Configure, choose Buckets.
- Choose Add new.
- Name the bucket, for example "Set aside: duplicates and tests".
- Choose a Bucket Type of the kind Declined.
- Save.
Step 2: Find the duplicates
Nothing checks for duplicates when an author submits, so you look for them.
- By search: open Sessions and use Search for a title or an author's name. Two sessions with the same title by the same author are the usual case.
- By asking Amal: Amal, the AI assistant of run.events, answers questions about your sessions in plain words. Ask it, for example, for sessions with the same or a very similar title by the same author, and check each pair it names.
- With the content review: if your organizer ran earlier editions of the congress in run.events, open Report, then Content review, and run it. Its chapter on overlaps lists Overlapping pairs with a verdict such as "Same talk", "Adjusted version" or "Strong overlap", including pairs within this year's call.
Good to know: the content review needs at least one earlier event of the same organizer to compare with. For a first edition, it cannot be run, and you rely on search and Amal.
Step 3: Decide with the author
Before you set a duplicate aside, be sure which of the two the author wants to keep. Often the second submission is the corrected one. If in doubt, write to the author. An author who wants a submission removed can also withdraw it from their speaker dashboard with Withdraw session.
Step 4: Move them into the bucket
- On Sessions, tick the sessions to set aside.
- In the selection bar, choose Move to bucket, and choose your bucket.
- Confirm.
Step 5: Keep the bucket out of the way
- Never use Inform Speakers on this bucket, so that no decision mail is sent to the authors of these sessions.
- To hide the bucket from the Content Organizer, close it with Close Bucket in its menu.
Good to know: sessions set aside still count in the reports, as declined sessions. Bear this in mind when you report acceptance rates.
Related articles