When to Use This
Use this when you change bucket assignment rules, the default bucket, or review teams, and you need existing submissions sorted with the new setup. Future submissions use the new setup automatically, but existing submissions keep their current placement until you reprocess the space.
If you only need a read-only view of progress for a round or bucket, see Monitor Review Progress and Reprocess Bucket Placement instead.
Prerequisites
- The space needs review settings before Rhythm has rules or a default bucket to use for placement.
- You need permission to configure review settings for the space before you can reprocess it.
When a Submission First Gets Its Bucket
When a member submits through the Portal form, Rhythm places the submission into its review bucket and starting round right away, as long as the submission passed eligibility and the space has review settings.
If you turn on bucket assignment rules after abstracts have already arrived, those abstracts stay in the buckets they received originally. The new rules apply only to future submissions until you reprocess the space.
Move Submissions Into the Right Buckets Without Editing Each One
After you add or change bucket assignment rules, reprocess the space to apply those rules to submissions that already exist. This is faster than opening each submission and changing its bucket by hand.
Editing a submission directly can also bring up workflow questions, such as an acceptance decision, that you do not need just to re-sort it. Reprocessing avoids those extra steps.
- Turn on Bucket Assignment Rules in the space's review settings, then define the criteria for each rule you need. This is also where you set up scoring criteria and recommendations, if you're changing those at the same time.
- Open the space, go to Setup, then Reviews, then Maintenance.
- Under Reprocess Bucket Assignments, select Reprocess Now, and confirm.
Result
Rhythm shows a message that the process has restarted and will take a few minutes. Every submission in the space goes back through bucket placement as though it had just arrived, and reviewer assignments update to match.
Reprocessing matters after any change to how review is configured, not only after changes to bucket assignment rules. If you change scoring criteria, recommendations, or bucket assignment rules, run Maintenance > Reprocess Bucket Assignments afterward so existing submissions pick up the new configuration. Without that step, the review assignments you expect may not appear right away.
Setting Up a New Routing Path, Such as Re-Audit
To route a group of submissions into a special path like re-audit, set it up in this order:
- Create a review team for the re-audit path.
- Create a bucket for that path, and associate it with the right team and round.
- Create a bucket assignment rule using the condition that should send a submission down this path, such as a score threshold.
- Run Maintenance > Reprocess Bucket Assignments so existing submissions are evaluated against the new rule.
If You're Working in a Cloned Event
If you're staying in an event you cloned and it inherited review buckets, teams, or rounds you don't want, you can create new review buckets in that cloned event. Then update your bucket assignment rules to target the new buckets, and run reprocessing to reassign submissions. Whether this fully works depends on how the original relationships were carried over during cloning, so check the results afterward rather than assuming every submission landed correctly.
Keep a Submission Where You Put It
If you placed a submission in a bucket by hand and do not want rules to move it again, suppress placement on that submission. When placement is suppressed, that submission keeps its current bucket during space reprocessing, while every other submission is re-sorted normally.
Warning
Reprocessing cannot be undone, and Rhythm does not show a progress indicator beyond the initial message. If you start it again while an earlier run is still working, the second run starts anyway, so avoid clicking repeatedly. Reprocessing can also replace reviewers who have not submitted yet when the new rules point a submission to a different bucket or team.