Data checks

The administrator Data checks page (/admin/checks) exposes source disagreements and stale cards. Catalog comparisons help inspect differences; they do not prove that either source is correct.

Source differences

Primary data is kept by default. Secondary sources fill gaps and record disagreements where both sources have differing nonempty values. Comparison normalizes some case, accents, punctuation and word ordering, depending on the field.

Filter differences by game, source, field and open/resolved state. Inspect the printing or set and compare upstream evidence before deciding.

Available choices are:

• Primary: preserve the primary source's value.
• Secondary: prefer the secondary value for a writable field.
• Custom: enter an administrator value for a writable field.
• Reopen: clear the arbitration so it is open again.

Reviewed writable fields are card name, rarity, set name, release date and card count. Other differences cannot necessarily be written back. Values are validated by the resolution service; for example dates and counts must have valid formats.

Saved choices are reapplied after catalog synchronization. They are server-wide catalog changes and affect every user's view of that data.

Standing field rules

A rule identifies a game, source and field and chooses primary or secondary. It applies to current differences and future synchronization. This is broader than resolving one printing. Removing a rule reopens differences resolved by that rule; it is not a snapshot restoration of all previously overwritten database fields.

Stale cards

The stale view identifies cards missed by the last catalog sync, without images or without card details. Select a card to inspect it and use its refresh action where supported. A source can legitimately remove a card or lack a localized image; repeated refreshes may not change the result.

Normal card-page viewing can also request a throttled refresh. The worker's refresh job handles supported stale/incomplete cards in the background.

Diagnose before a reset

1. Check the game's latest successful catalog run and its counters.
2. Inspect whether the problem is one card, one set or the whole catalog.
3. Check quotas, credentials and upstream availability.
4. Try a targeted refresh for an isolated stale card.
5. Reserve catalog reset for a confirmed broader issue and take a backup first.

Implementation references

• backend/app/api/admin.py
• backend/app/services/crosscheck.py
• web/src/pages/admin/Checks.tsx