Splitted Class Management — Equipe Extension

Groups two halves of a splitted class into a single ranked list and writes the qualified riders into an Equipe list.

1. What it does

When a class is too big it is split into two competitions (Group 1 / Group 2) that run in parallel and are ranked separately. The qualified riders for the next round have to come from both groups, merged fairly.

The extension:

1. reads the results of the two group competitions,
2. interleaves them — 1st of Group 1, 1st of Group 2, 2nd of Group 1, 2nd of Group 2, and so on,
3. removes riders who have no result yet, and removes duplicate horse numbers,
4. shows the merged list for checking,
5. on confirmation, empties the destination list in Equipe and re-creates it with the merged order.

Interleaving is what makes the merge fair: it preserves the rank inside each group instead of comparing times or faults across two different judgings.

2. Requirements

The extension is launched by Equipe with a signed token:

splitted_get.php?token=<JWT>

The token payload must contain meeting_url, target (modal or browser), style_url, and the top-level api_key.

3. Using the extension

Step 1 — Open it

Launch the extension from the Equipe show. Three drop-downs and two buttons appear.

Step 2 — Select the sources

The destination list must exist in Equipe before running the extension. Only lists without an FEI identifier are offered, so an official FEI class can never be overwritten by mistake.

Step 3 — Generate

Click Generate Qualified riders list. A table is displayed:

# · Horse # · Rider Name · Horse · Nation · Result Preview · From

The From badge shows whether the line comes from Group 1 or Group 2. Check the order and the count before importing — nothing has been written to Equipe at this point.

Step 4 — Import

Click Import Qualified riders to Equipe. A spinner runs while the extension:

1. deletes all existing starts in the destination list,
2. creates one start per rider of the merged list,
3. updates each start with its horse number, its starting order and the result preview.

Then reopen the list in Equipe to verify.

⚠️ The import is destructive. Everything already present in the destination list is deleted first. Always point the import at a list dedicated to this purpose.

4. Selection rules

A rider from a group is kept only if:

• result_preview is not empty — riders who have not started, or who have no published result, are dropped;
• the horse number (hnr) has not already been used by an earlier line — the first occurrence wins. This protects against the same horse appearing in both groups (same horse number, different rider).

Numbering (compteur) is assigned during the merge and becomes the starting order (st) in Equipe.

5. Data flow

Equipe ──JWT──> splitted_get.php ──GET /competitions.json──> Equipe
                       │
        user selects Q1 / Q2 / destination
                       │
                       ├─GET splitted_class.php?id1&id2&url&apikey
                       │      └─GET /competitions/{id}/results.json  (×2)
                       │      └─merge + filter  ──> JSON to the browser
                       │
                       └─POST splitted_import.php (destination, JsonData)
                              ├─GET    /competitions/{id}/starts.json
                              ├─DELETE /competitions/{id}/starts
                              ├─POST   /competitions/{id}/starts        (×N)
                              └─PATCH  /competitions/{id}/starts/updates

Fields read from results.json

Fields written to the destination list

6. Troubleshooting

Errors from the AJAX calls are written to the browser console (F12), not to the page.

7. Known limitations

These are current behaviours of the code, worth knowing before relying on it in production:

• Only two groups. A class split into three or more cannot be merged.
• Start creation is incomplete. In splitted_import.php, the creation loop posts empty start records: the variable $cavalier is never assigned (the loop uses $i), so rider_name and hnr are sent blank and only filled by the later PATCH pass, matched by position. Any mismatch between created and patched records shifts the whole list.
• Off-by-one. The loop runs $i <= $counter, creating one start too many.
• Hardcoded API key. The POST .../starts command carries a literal X-API-KEY instead of the key received in the request — the import fails on any other show.
• shell_exec + curl. The import shells out with values coming from the request; they are not escaped. Rewriting these calls with PHP cURL (as already done in splitted_get.php) removes both the injection risk and the dependency on the curl binary.
• No user-visible confirmation. The success response of the import is not displayed; only the spinner stops.
• No undo. The deletion of the destination list is not snapshotted.