Data Corrections

Corrections are a normal part of running an event. This page is the approved way to do them, in roughly the order you would meet them.

1. A judge submitted a wrong vote

A judge's submission is locked by design (there is no edit button on their success page). The approved path:

1. A fresh token is issued for that judge; the old one stops working immediately. (That is one of the two reserved steps.)
2. The judge re-opens the scoring page with the new token (on any device), re-enters the correct votes, and publishes.
3. The ranking is re-run and, if it was already published, you Revoke and Publish again. The Revoke/Publish part you do yourself.

The record keeps each of these steps (when the token changed, when the re-submission happened, when the ranking was re-run), so a later query can be traced end to end.

2. A participant's name is wrong

1. In Participant Management, edit the name on the event page.
2. Re-open each affected competition and click Import Assigned Participants (or Save) so the grid and any saved scoresheet reflect the corrected name.
3. If results were already published, re-publish. Revocation is optional here; a name change does not change the ranking.

3. A couple is registered as two singles (or a single as a couple)

1. On the event page, use the Partner controls to link or unlink the dancers, and set the Pair role (Leader / Follower).
2. Re-import into the affected competitions.
3. For a couple competition that already has votes, the correction is more involved. The votes belong to the pairing, and splitting or joining a couple changes the grid. In that case the judges need fresh tokens and re-vote on the corrected grid. (A rare, last-resort path. Get it right at registration time if you can.)

4. A participant is in the wrong competition

1. Remove the assignment on the event page for the competition they should not be in.
2. Add the assignment for the competition they should be in.
3. Import Assigned Participants in both competitions so the grids match.
4. If either competition already has votes, treat it like scenario 1: the grid changed, so re-vote on the corrected grid, or knowingly accept it.

5. The scoring system or caps were set wrong before scoring started

• Before any votes are in: change Scoring System, Number of Yeses, Number of (Ranked) Maybes in the configuration and Save. The grid re-validates against the new caps.
• After votes are in: the existing votes stay there. If some now violate the new caps, they will be flagged the next time the ranking is re-run, and the affected judge will fix them. Prefer getting the caps right before scoring starts.

6. I published something I should not have

1. Revoke publication (Publication Controls → Revoke Publication → confirm). You can do this yourself. The public page returns to not published immediately.
2. Fix the underlying data (one of the above).
3. Re-run the ranking if it changed, and Publish the corrected version. The publish is a step you do yourself.

What you will never need to do

• Hand-edit the ranking or a judge's raw votes. Every correction above has a supported path, and the supported paths are what keep the record trustworthy.
• "Delete and recreate" the whole event. That is a last resort; the paths above are designed to do it for you.

The record is the safety net

Every correction above leaves a record: who, when, and what changed (token changes, re-submissions, re-runs, publication changes). The person behind the account keeps that record and can pull it if a question comes up. It is the authoritative account of what happened and when.

Related

• Judge errors and recovery
• Getting help